[Bot] Implement per-user rate limiting for Bot Commands

[Solomonsolomonsolomon]

Add internal rate limiting to the @chenpilot-experimental/bot package to prevent individual users from flooding the bot.nn- Priority: Medium

[She-ge]

Please let me work on this

[kingfavourjudah]

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

Can I work on this?

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

[Henrichy]

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

I’d like to implement per-user rate limiting for bot commands to prevent abuse and ensure fair usage across all users. I have experience designing middleware and request control systems in Node.js environments.

My approach will track requests per user (e.g., by user ID) and enforce limits using a sliding window or token bucket strategy for accuracy and flexibility. I’ll integrate this directly into the bot command handling layer so it applies consistently across all commands.

I’ll include tests to validate rate enforcement and edge cases like bursts or retries.

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

[Reedahbosslady]

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

Please i would like to work on this issue

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

[gelluisaac]

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

I’m interested in tackling this! I have a strong background in smart contract development and full-stack systems, so I'm well-equipped to handle the requirements here. Could you please assign this to me?

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

[drips-wave]

Congratulations, @gelluisaac! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on April 29, 2026.

🧑‍💻 @gelluisaac: 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 marked as completed by a Drips Wave moderator for @gelluisaac as part of the Stellar Wave Program's 4th Wave 🥳

Moderator's reason: [Auto-assessed] The PR #317 was successfully merged and addresses the issue by implementing a sliding window rate limiter module and integrating it into both Discord and Telegram adapters. Although the issue remains open, the merge of the PR indicates the contribution was accepted by the maintainers.

😎 @gelluisaac: 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.

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

ℹ️ Note: This issue was marked complete via moderation. Points were issued even though the GitHub issue remains open.