Timelock duration on upgrades
Uniswap (v2 + v3)'s assessment for RD-F-032 — scored green on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
V2: not applicable (immutable). V3: Timelock delay = 172,800 seconds (48 hours / 2 days). Maximum delay = 2,592,000 seconds (30 days). Above the 48h green threshold. Combined: green.
Detail #
Timelock contract 0x1a9C8182C09F50C8318d769245beA52c32BE35BC: delay() = 172800 seconds = 48 hours = 2 days. MAXIMUM_DELAY = 2,592,000 seconds = 30 days. All V3 governance actions (fee switch, treasury, enableFeeAmount) route through this Timelock. No bypass path exists.
Sources #
- EtherscanUniswap Timelock read contractTimelock 0x1a9C8182: delay = 172800 confirmed via Etherscan readretrieved 2026-05-12
Methodology #
Read the timelock delay (in hours) between a queued upgrade proposal and its executable state.
See the full factor methodology and distribution across all protocols →