Proposal execution delay < 24h
Uniswap (v2 + v3)'s assessment for RD-F-038 — scored green on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
V2: not applicable (no governance). V3: voting period = 40,320 blocks (~7d) + voting delay = 13,140 blocks (~2.3d) + Timelock delay = 2 days. Total minimum from proposal creation to execution = ~11 days. No sub-24h path exists. Combined: green.
Detail #
GovernorBravoDelegator: votingPeriod=40320 blocks; votingDelay=13140 blocks. Timelock: delay=172800 seconds (2 days). A proposal must: (1) be submitted (requires 2.5M UNI proposer), (2) wait 13140 blocks (~2.3d voting delay), (3) receive votes for 40320 blocks (~7d), (4) queue in Timelock, (5) wait 2 days before execution. Minimum total: ~11 days. No emergency fast-path exists.
Sources #
- Etherscan
- GovernorBravoDelegator read proxyGovernorBravo: votingPeriod=40320 blocks; votingDelay=13140 blocksretrieved 2026-05-12
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 →