Telegram (ask questions / claim the issue here first): https://t.me/+DOylgFv1jyJlNzM0
Why this matters
multisig_governance/src/lib.rs stores the entire PendingTransfer (with a 7-day PROPOSAL_TTL_SECONDS timelock window plus a min 24h delay) under instance storage (KEY_PENDING) and never bumps instance TTL anywhere in the contract. Unlike the other contracts, there is no bump_instance_ttl helper, so a long-lived proposal awaiting its timelock can have its instance storage archived, making finalize_admin_transfer and approvals fail and the contract effectively unusable.
Acceptance criteria
Files to touch
- multisig_governance/src/lib.rs
Out of scope
- Migrating governance state to persistent storage layout changes
- Adding multiple concurrent proposals
Why this matters
multisig_governance/src/lib.rs stores the entire PendingTransfer (with a 7-day PROPOSAL_TTL_SECONDS timelock window plus a min 24h delay) under instance storage (KEY_PENDING) and never bumps instance TTL anywhere in the contract. Unlike the other contracts, there is no bump_instance_ttl helper, so a long-lived proposal awaiting its timelock can have its instance storage archived, making finalize_admin_transfer and approvals fail and the contract effectively unusable.
Acceptance criteria
Files to touch
Out of scope