Detect Redundant Soroban Events

[mijinummi]

🧠 Concept

Detect duplicate event emissions within the same execution path.

⚠️ Problem

Repeated events can increase resource consumption without providing additional information.

📁 Implementation Scope

• packages/rules/soroban/events/
• packages/analyzers/soroban/events/

✅ Requirements

• Track emitted events
• Compare topics and payloads
• Detect duplicate emissions
• Suggest safe consolidation

🎯 Acceptance Criteria

• Duplicate events detected
• Event payloads compared
• Safe suggestions generated
• Tests added

[glendell03]

I'd like to work on this. Based on the scope described, I'd implement the detector under packages/analyzers/soroban/events/ to walk each execution path, record env.events().publish(topics, data) call sites in order, and flag calls where topics and payload are structurally equal (or a strict subset) to a prior emission with no state mutation in between. The corresponding rule under packages/rules/soroban/events/ would report the duplicate site and suggest either hoisting the event out of a loop/branch or removing the redundant call.

One design question worth agreeing on first: how strict should the "duplicate" comparison be — exact topic+payload equality only, or also flag cases where payload differs but topics match and the emission is clearly redundant (e.g., inside a loop with unchanged state)? I'd lean toward starting with exact equality to avoid false positives, then extending. I'd also add path-sensitivity tests (loops, branches, early returns) as part of the test suite requirement.

Happy to take this if it's unassigned.

[shobhamerabacha-star]

Hello @maintainers,

I can tackle Detect Redundant Soroban Events. Proposed implementation roadmap:

• Analysis: Inspect current behavior and edge cases in MDTechLabs/GasGuard
• Implementation: Implement Detect Redundant Soroban Events with explicit require_auth checks, clean storage layouts, and robust Soroban contract logic.
• Testing: Add comprehensive unit tests verifying both happy-path invocations and unauthorized revert scenarios.
• PR: Atomic commit with clean git hygiene and passing CI

Ready to deliver a clean, tested PR within 12–24 hours. Please assign!

[Kleo-Crypt]

@Kleo-Crypt has applied to work on this issue as part of the Stellar Wave Program's 9th wave.

Hi maintainer, I would love to work on this. Please assign. Thank you

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

[oraimoitel]

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

Let me complete this issue professionally sir!

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

[drips-wave]

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

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

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox!

@oraimoitel's PR #954 was approved and merged by @mijinummi.

🏆 @oraimoitel: You earned 40 FoxPoints for this contribution! Your current tier: Builder (1,139 total points). Track your full progress on GrantFox.

👏 Great work, @oraimoitel! Keep contributing to MDTechLabs.

[drips-wave]

This issue has been completed by @oraimoitel as part of the Stellar Wave Program's 9th Wave 🥳

😎 @oraimoitel: 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. You can also Leave a review to share your experience working on this issue.

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