Repository navigation
design(contracts): Specify timelock emergency governance controls #311
Description
Problem
The timelock already lets a guardian cancel a queued proposal. Additional multisignature, rate-limit or pause controls require a governance threat model.
Scope
Document the gap in existing veto controls and evaluate an emergency governance design without changing contract behavior in this issue.
Acceptance criteria
- Describe current guardian and admin powers and the failure scenarios not covered.
- Specify any proposed multisignature authorization, upgrade limits, pause scope and recovery process.
- Analyze guardian compromise, griefing, deadlock, key rotation and upgrade compatibility.
- Record a decision and split selected changes into independently testable contract tasks.
Activity
shobhamerabacha-star commentedon Oct 20, 2026
Greetings,
I looked into the details for "feat(contracts): Timelock Governance Multi-Stage Veto and Emergency Circuit Breakers" and would like to contribute the fix.
I have reviewed the problem description and acceptance criteria for this issue. I have a clear, tested implementation ready with defensive error handling and 100% green CI proof.
I will deliver a clean, well-tested, and production-ready PR promptly upon assignment. Kindly assign this issue to me.
Thank you!
huangji6693-max commentedon Oct 26, 2026
Submitted PR #322 implementing the multi-sig guardian veto & storage purge (
veto_and_purge/configure_guardians), the 30-day epoch upgrade circuit breaker rate limiter (MAX_UPGRADES_PER_EPOCH = 1), and emergency pause with time-decayed post-pause recovery (43/43 Soroban tests passing).[-]feat(contracts): Timelock Governance Multi-Stage Veto and Emergency Circuit Breakers[/-][+]design(contracts): Specify timelock emergency governance controls[/+]