feat: implement rate limiting and anti-spam for bets and events

[greatest0fallt1me]

Description:

Implement configurable rate limiting (e.g., max bets per user per time window, max events per admin) to reduce spam and abuse.

Requirements and Context:

• Must be secure, tested, and documented
• Should allow admin to set rate limits (e.g., per user per event or global)
• Should enforce limits in place_bet and optionally in create_event
• Should use time windows (e.g., last N ledger closes or seconds)
• Should emit clear error when limit exceeded
• Must not block legitimate high-volume use with reasonable limits

Suggested Execution:

1. Fork the repo and create a branch

   git checkout -b feature/rate-limiting

2. Implement changes

   • Write contract: src/lib.rs (rate limit checks)
   • Add rate_limiter module: src/rate_limiter.rs
   • Update storage and validation; add documentation and NatSpec-style comments

3. Test and commit

   • Run tests; cover at limit, over limit, window expiry
   • Include test output and security notes

Example Commit Message:

feat: implement rate limiting and anti-spam for bets and events

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 it perfectly. Please help assign it to me.

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

[precious-akpan]

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

Hello Predictify Team,

I am interested in taking on this task. As a software engineer with a strong background in TypeScript/JavaScript and experience working with smart contracts, I am well-prepared to implement a robust rate-limiting solution for the Predictify protocol.

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

[drips-wave]

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

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

[precious-akpan]

Hi Team, I realised the Drips Wave just concluded, but I was assigned this task right before the cutoff.

I’ve already started the implementation—would you still like me to submit a PR for review?

I’m still keen on contributing to the protocol.