Add configurable supply cap enforcement to creator key contract

[Chucks1093]

Summary

Allow creators to set a hard supply cap on their key at deployment, with the bonding curve buy function rejecting purchases that would push total supply beyond the cap.

Scope

• supply_cap stored per key in config at deployment, optional
• buy function checks post-trade supply against cap before execution
• get_supply_info(key_id) — returns current supply, cap, and remaining
• SupplyCapReached event emitted when supply hits cap exactly
• Cap of 0 treated as unlimited

Acceptance Criteria

• Buy blocked when post-trade supply would exceed cap
• Buy succeeds for partial fill that exactly reaches cap
• get_supply_info returns correct values at all supply levels
• SupplyCapReached event emitted exactly once when cap hit
• Cap of 0 allows unlimited supply growth

ETA

24 hours

[Muyideen-js]

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

Hi, I can fix this

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

[Horpeyehmi]

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

I would love to work on this issue
Please assign it to me

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

[DanbabaJr]

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

Hi, I’d love the opportunity to work on this issue. I’m committed to getting a clean PR submitted within 12 hours, with CI passing and the changes properly tested. Looking forward to working together on this wave 🤲

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

[drips-wave]

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

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

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox!

@DanbabaJr's PR #1005 was approved and merged by @Chucks1093.

🏆 @DanbabaJr: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (140 total points). Track your full progress on GrantFox.

👏 Great work, @DanbabaJr! Keep contributing to accesslayerorg.

[drips-wave]

This issue has been completed by @DanbabaJr as part of the Stellar Wave Program's 9th Wave 🥳

😎 @DanbabaJr: You earned 150 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.