Add Rate Limiting

[SudiptaPaul-31]

⚡ Feature: Add Rate Limiting

📖 Description

Introduce rate limiting to prevent spam messages being sent from the same wallet. This ensures a smoother chat experience and protects against abuse.

Expected Behavior

• Each wallet should have a message send limit within a defined time window.
• If the limit is exceeded, further messages should be temporarily blocked.
• Provide user feedback (e.g., “You are sending messages too quickly. Please wait.”).
• Limits should reset automatically after the cooldown period.

🛠 Technical Notes

• Implement rate limiting logic at the SDK/service layer to ensure consistency.
• Consider configurable thresholds (e.g., X messages per Y seconds).
• Ensure compatibility with existing real-time rendering and typing indicator features.
• Maintain responsive UI without breaking layout or wallet functionality.

✅ Verification

• Spam attempts from a single wallet are blocked after exceeding the threshold.
• Cooldown period restores normal functionality.
• Works consistently across browsers and devices.
• npm run lint and npm run build succeed.
• No regression in message rendering, typing indicator, or wallet integration.

[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

[Chucks1093]

@Chucks1093 has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

I can start working on this issue immediately as I have strong experience with rate limiting api request to avoid api spamming in backend systems

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

[Nexha-dev]

@Nexha-dev has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

Hi Maintainer Can I work on this issue

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

[drips-wave]

Congratulations, @Nexha-dev! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on February 26, 2026.

🧑‍💻 @Nexha-dev: 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 🌊

[Nexha-dev]

@SudiptaPaul-31 merge pr