Implement on-chain metadata display on key detail page from contract storage

[Chucks1093]

Summary

Fetch and display creator key metadata directly from the on-chain contract storage on the key detail page, ensuring name, symbol, description, and image are always the canonical on-chain values.

Scope

• Metadata fetched from get_metadata contract call on key detail load
• Name and symbol shown in page header from on-chain source
• Description rendered in about section
• Image loaded from IPFS CID stored in metadata
• Fallback to API metadata if on-chain call fails with stale indicator

Acceptance Criteria

• Metadata fetched from contract and rendered correctly
• Image loaded from IPFS CID with loading skeleton
• Fallback to API metadata on contract call failure
• Stale indicator shown when fallback is active
• Metadata refreshed on creator update event

ETA

12 hours

[guptakumarranjeet150]

Hi there,

I would love to take this on. My planned approach:

• Implement Implement on-chain metadata display on key detail page from contract storage with thorough authorization verification and clean data structures.
• Cover contract calls with hermetic unit tests verifying events and token balances.

I can start working on this right away. Please assign!

[guptakumarranjeet150]

Hi maintainers,

I can tackle Implement on-chain metadata display on key detail page from contract storage. Proposed implementation roadmap:

• Analysis: Inspect current behavior and edge cases in accesslayerorg/accesslayer-client
• Core Implementation: Implement Implement on-chain metadata display on key detail page from contract storage with explicit require_auth checks, secure state storage, and gas optimization.
• Quality Assurance: Ensure contract compiles cleanly and passes all cargo tests without warnings.

Happy to pick this up today—please assign to me!

[Ahbiz]

@Ahbiz has applied to work on this issue as part of the Stellar Wave Program's 9th wave.

Hi, I’m interested in working on this issue. I’ve reviewed the details and would like to take responsibility for the implementation. Please assign it to me, and I’ll get started.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Ahbiz to this issue.

[moveecoder]

@moveecoder has applied to work on this issue as part of the Stellar Wave Program's 9th wave.

I will like to work on this

ℹ️ Repo Maintainers: To accept this application, review their application or assign @moveecoder to this issue.

[somotochukwu-dev]

@somotochukwu-dev has applied to work on this issue as part of the Stellar Wave Program's 9th wave.

Hi
Please assign this issue to me
Thanks

ℹ️ Repo Maintainers: To accept this application, review their application or assign @somotochukwu-dev to this issue.

[actvabdulrahman]

@actvabdulrahman has applied to work on this issue as part of the Stellar Wave Program's 9th wave.

Hello Maintainer,
I have vast experience in solving GitHub issues. Please do well to assign me this to get it done for you
Thank you.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @actvabdulrahman to this issue.

[VictorEzenma]

@VictorEzenma has applied to work on this issue as part of the Stellar Wave Program's 9th wave.

I can solve this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @VictorEzenma to this issue.

[JerryOJJ]

@JerryOJJ has applied to work on this issue as part of the Stellar Wave Program's 9th wave.

I would like to work on this

ℹ️ Repo Maintainers: To accept this application, review their application or assign @JerryOJJ to this issue.

[drips-wave]

Congratulations, @VictorEzenma! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on September 30, 2026.

🧑‍💻 @VictorEzenma: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊