Timelock duration on upgrades
Cap (cUSD / stcUSD)'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 delay = 86,400 seconds = 24 hours. Per rubric: green = ≥48h, yellow = 24–47h. Cap's 24h delay is at the yellow boundary.
Sources #
- EtherscanCap TimelockController — getMinDelay = 86400sConstructor arg: minDelay (uint256): 86400. Confirmed via decoded constructor args on Etherscan.retrieved 2026-05-17
- Cap protocol docs — timelock delay documentationProtocol docs: 'mandatory 1-day minimum delay'retrieved 2026-05-17
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 →
rubric_version v1.7.0 protocol cap factor RD-F-032 score yellow collected_at 2026-05-17 10:56:24