Smart Contract Enhancement: Add structured events for Rate Limiting triggers

[p3ris0n]

Category: Blockchain / Smart Contract Development

Objective: Implement Add structured events for Rate Limiting triggers in the core contracts.

Detailed Description: Enhance the contract capabilities by implementing: Add structured events for Rate Limiting triggers. Ensure it adheres to the existing crate structure and includes necessary event emissions.

Acceptance Criteria:

• Code must compile with cargo build --target wasm32-unknown-unknown.
• Must pass cargo clippy without warnings.
• Must include unit tests.

Technical Requirements: Rust, Soroban SDK

Deliverables:

• Contract source code updates
• Tests for the new feature

Testing Requirements:

• Run cargo test and cargo fmt.
• Deploy to Testnet locally and verify invocation.

Estimated Difficulty: Advanced

Points: 200

[godwinedemodu]

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

I want to work on this because rate limiting without structured events is essentially invisible — off-chain tools, indexers, and monitoring systems have no way to react to or audit when rate limits are triggered. Adding structured events for these triggers makes the contract's behavior fully observable and is the right pattern for any production-grade contract. I'm comfortable working within an existing crate structure and meeting the cargo build and clippy requirements.

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

[EmeditWeb]

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

Hi maintainer , i'd love to fix this

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

[drips-wave]

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

🧑‍💻 @EmeditWeb: 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 @EmeditWeb as part of the Stellar Wave Program's 6th Wave 🥳

Moderator's reason: [Auto-assessed] The contributor successfully implemented the requested structured events for rate limiting and provided comprehensive unit tests with snapshots. PR #374 directly addresses the requirements of Issue #326, and also includes a relevant bug fix in the admin module and additional contract upgrade logic, showing high-quality work without any maintainer objections.

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

[drips-wave]

This issue has been removed from the Stellar Wave Program by the repository maintainers.

@EmeditWeb, you have been unassigned from this issue. If you have any questions, please reach out to the repo maintainers.