Timelock duration on upgrades
Compound V3 (Comet)'s assessment for RD-F-032 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Timelock MINIMUM_DELAY = 172,800s = 48h. Active GovernorBravo (0x309a862): votingPeriod = 50,400 blocks (~7 days), votingDelay = 19,710 blocks (~2.7 days). Total governance cycle ~12 days. DeFiScan flags Stage 0 noting timelock alone is 2 days, below 7-day exit window standard. Scoring yellow because the minimum timelock delay alone is 48h (a hostile proposal could set eta at minimum); but the practical total cycle is ~12 days with the new governor.
Sources #
- Etherscanhttps://etherscan.io/address/0x6d903f6003cca6255D85CcA4D3B5E5146dC33925retrieved 2026-04-28
- https://www.defiscan.info/protocols/compound-v3/ethereumretrieved 2026-04-28
- https://etherscan.io/address/0x309a862bbC1A00e45506cB8A802D1ff10004c8C0retrieved 2026-04-28
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 →