Implement key deprecation and successor designation in creator key contract

[Chucks1093]

Summary

Add deprecation functionality to the creator key contract allowing creators to mark a key as deprecated, optionally designate a successor key, and block new buys on deprecated keys.

Scope

• deprecate_key(key_id, reason, successor_key_id?) — creator-only
• New buy transactions rejected on deprecated keys
• Sell and transfer still permitted post-deprecation
• get_deprecation_status(key_id) — returns status, reason, successor, timestamp
• KeyDeprecated event emitted on deprecation

Acceptance Criteria

• Deprecation blocked for non-creator callers
• Buy rejected with DeprecatedKey error after deprecation
• Sell and transfer succeed on deprecated keys
• get_deprecation_status returns all fields correctly
• KeyDeprecated event includes reason and successor key ID

ETA

24 hours

[Okorie2000-code]

The issue description is clear, Maintainer I would love to work on this issue

[guptakumarranjeet150]

Hi there,

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

• Implement Implement key deprecation and successor designation in creator key contract with explicit require_auth checks, secure state storage, and gas optimization.
• Cover contract calls with hermetic unit tests verifying events and token balances.

Ready to deliver a clean, tested PR within 12–24 hours. Please assign!

[Eeboade]

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

Hi, kindly assign, i would love to fix

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

[hmhidey111-collab]

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

Hello, I'd like to pick this issue up.

I'm a software engineer with strong experience in JavaScript and building scalable web applications. I'm comfortable working across the stack, writing clean, maintainable code, and collaborating in open source environments.

I've reviewed the issue and I'm confident I can implement a solid solution while following the project's conventions.

I'd love the opportunity to work on this — please consider assigning it to me.

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

[oscarj007]

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

Please assign me

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

[funds0033-cmyk]

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

Pls assign

ℹ️ Repo Maintainers: To accept this application, review their application or assign @funds0033-cmyk 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.

[shinorh247]

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

Hi maintainer I would like to work on this issue

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

[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.

[mysterio123865]

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

Pls assign

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

[drips-wave]

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

🧑‍💻 @mysterio123865: 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 🌊