[Contract] — Invite Code Expiry and Usage Caps

[Olowodarey]

Labels: contract, enhancement, invite

Problem

Invite codes never expire and can be reused an unlimited number of times, undermining any referral or access-control scheme built on top of them.

Requirements

1. Store an optional expiry ledger timestamp per invite code.
2. Store a maximum-uses counter and increment on each redemption.
3. Reject redemption of expired or exhausted codes.
4. Expose a read function returning remaining uses and expiry.

Acceptance Criteria

• Redemption reverts once the code is expired or use cap is reached.
• Remaining uses decrement correctly and never go negative.
• Read function returns accurate remaining uses and expiry.
• Tests cover expiry, exhaustion, and valid redemption.

Files

contracts/open-market/src/invite.rs, contracts/open-market/src/storage_types.rs, contracts/open-market/src/errors.rs

[senmalong]

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

hi,

This issue aligns well with my experience as a Web3 builder. I’ve worked on Celo-based applications with a focus on usability, smart contracts, stablecoin payments, and real-world adoption.

I also have contribution experience through OnlyDust, Drips Waves 1–5, and the GrantFox beta campaign. I’m confident I can deliver a clean and well-tested solution within 24 hours.

I’d be excited to contribute to this.

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

[OmniZlatoon]

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

Good day sir, Ready to deliver the task A.S.A.P. Gone through the issue and to be honest, i can work the task with the right tools at hand. please assign me maintainer . My eta is 5 hours

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

[fati-Onchain]

@fati-Onchain has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hi. I have reviewed this issue and would like to work on it.

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

[drips-wave]

Congratulations, @fati-Onchain! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on July 30, 2026.

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

[drips-wave]

This issue has been completed by @fati-Onchain as part of the Stellar Wave Program's 7th Wave 🥳

😎 @fati-Onchain: You earned 200 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.