Proposal execution delay < 24h
Convex Finance's assessment for RD-F-038 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
No formal execution delay enforced for routine admin operations. Snapshot vote conclusion to on-chain execution is multisig-dependent and can range from hours to days. No minimum execution delay enforced programmatically. BoosterOwner forceShutdown has 30-day delay, but this covers emergency path only. Routine admin actions (fee changes, pool management) can execute with 0 hours delay after 3-of-5 multisig signs.
Sources #
- DocsConvex Finance -- Voting and Gauge WeightsMultisig required to sign to establish Snapshot vote outcomes -- no enforced delay between vote and executionretrieved 2026-05-16
- Convex BoosterOwner.sol -- GitHub sourceBoosterOwner.sol: FORCE_DELAY = 30 days for forceShutdown path only; no delay on routine callsretrieved 2026-05-16
Methodology #
Determine whether the time between a governance proposal passing and its executability (including any internal delay) is less than 24 hours.
See the full factor methodology and distribution across all protocols →