feat: implement whitelist and blacklist for events and users

[greatest0fallt1me]

Description:

Allow admin to maintain whitelists/blacklists (e.g., allowed/blocked users for betting, or allowed/blocked event creators) and enforce them in place_bet and create_event.

Requirements and Context:

• Must be secure, tested, and documented
• Should support user whitelist (only listed users can bet) or blacklist (listed users cannot bet)
• Should support event-level or global list
• Should allow admin to add/remove addresses
• Should enforce in contract logic and emit clear errors
• Must not break existing behavior when lists are empty/disabled

Suggested Execution:

1. Fork the repo and create a branch

   git checkout -b feature/whitelist-blacklist

2. Implement changes

   • Write contract: src/lib.rs (check list in place_bet/create_event)
   • Add list module: src/lists.rs (or storage helpers)
   • Update storage and events; add documentation and NatSpec-style comments

3. Test and commit

   • Run tests; cover whitelist-only, blacklist-only, add/remove
   • Include test output and security notes

Example Commit Message:

feat: implement whitelist and blacklist for events and users

Guidelines:

• Minimum 95 percent test coverage
• Clear documentation
• Timeframe: 72 hours

[drips-wave]

This issue has been added to the Stellar Wave Program and is worth 200 Points.

🧑‍💻 Interested in contributing? Apply to work on this issue on Drips Wave, earn points, and receive rewards.

Warning

Only applications submitted via the apply link above will be considered. Please do not apply by commenting on the issue or opening a PR directly.

🤠 Repo maintainers: You can manage this issue's Points and Complexity on your Maintainer Dashboard here. Please keep an eye on applications and respond quickly 💙

ℹ️ Learn more about Drips Wave

[Georgechisom]

@Georgechisom has applied to work on this issue as part of the Stellar Wave Program's 1st wave.

Hi, I love to work on this issue and deliver an excellent result, please help assign it to me.

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

[Haroldwonder]

@Haroldwonder has applied to work on this issue as part of the Stellar Wave Program's 1st wave.

Let me work on this

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

[MerlinTheWhiz]

@MerlinTheWhiz has applied to work on this issue as part of the Stellar Wave Program's 1st wave.

Let me handle this please. I'll deliver quickly

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

[drips-wave]

Congratulations, @MerlinTheWhiz! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on January 31, 2026.

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