Prevent Redundant Upgrade Governance Collisions

[hman38705]

issues : 42

Great issue: Prevent Redundant Upgrade Governance Collisions

Description
The system currently allows starting a second upgrade vote for a WASM hash that is already pending or even recently rejected. This allows a malicious or confused Guardian to flood the governance queue with repetitive requests, causing community burnout and operational confusion.

Requirements and context

• Block initiate_upgrade if an upgrade for the same hash is already Pending.
• Implement a 7-day "Cool-down" period for hashes that have been rejected by a vote.

Suggested execution

• Fork the repo and create a branch: git checkout -b fix/issue-42-governance-collision
• Add collision and cool-down checks to the upgrade initiation flow.

Implementation changes

• Modify lib.rs (around line 210) to validate the status of the proposed WASM hash.

Test and commit

• Verify that an attempt to re-initiate a pending upgrade results in a specific error.

Example commit message
fix: prevent redundant upgrade votes and implement hash cool-down

Guidelines

• Operational efficiency in decentralized governance.
• Timeframe: 24 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

[dreamgene]

@dreamgene has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

dreamgene here. kindly assign

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

[drips-wave]

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

🧑‍💻 @dreamgene: 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 completed by @dreamgene as part of the Stellar Wave Program's 3rd Wave 🥳

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