Add regression test for holder count unchanged after a failed buy due to supply cap exceeded

[Chucks1093]

Summary

When a buy reverts because it would exceed the creator's supply cap, the holder count must remain unchanged. A new wallet that did not previously hold keys should not be added to the holder count just because a buy attempt was made and reverted.

Scope

• Register a creator with a supply cap of 10
• Buy 10 keys to reach the cap with one wallet
• Attempt a buy from a second wallet and assert it reverts with SupplyCapExceeded
• Assert holder count is still 1 (only the first wallet)

Acceptance Criteria

• Holder count unchanged after failed buy due to supply cap
• Second wallet not added to holders after failed attempt
• Total supply unchanged after the revert

ETA: 12 hours

---

Coordinate on Telegram

[kodinaka30-ship-it]

@kodinaka30-ship-it has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hello Maintainer,
I would like to work on this issue because I have experience writing regression tests for revert scenarios in smart contracts. I can implement the full test sequence registering a creator with a supply cap of 10, filling it with one wallet, asserting the second wallet's buy reverts with SupplyCapExceeded, and verifying holder count and total supply remain unchanged.
Please kindly assign.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @kodinaka30-ship-it to this issue.

[Kaycee276]

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

Hi maintainer, can i work on this issue?

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

[harystyleseze]

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

Hi, I would like to work on this

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

[gloskull]

Hi, I’d love to work on this issue. I have 4 years of experience across backend, frontend, full-stack, and smart contract development. I understand the task clearly and can deliver a clean, efficient, well-tested solution on time, with strong focus on code quality and maintainability. My PR will be submitted in under 10 hours.

[drips-wave]

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

🧑‍💻 @harystyleseze: 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]

🦊 GrantFox — @harystyleseze has been assigned to this issue as part of the Official Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #476)
2. Your PR will be reviewed by the accesslayerorg maintainers

Good luck! Track your progress on GrantFox.