Timelock duration on upgrades

Yearn Finance'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 #

U3 RESOLVED: OZ TimelockController (0x88Ba032be87d5EF1fbE87336B7090767F367BF73) getMinDelay() = 604800 seconds (7 days). Etherscan readContract confirms 604800. Cache value 604800 is correct. Profiler's conflicting '0 seconds' reading was a pipeline fetch error. 7d >> 48h green threshold.

Sources #

Docs
Yearn Core Contracts — Yearn Docsdocs.yearn.fi/developers/addresses/core-contracts lists TimelockController at this address across all chainsretrieved 2026-05-16
Etherscan
TimelockController readContract — Etherscan0x88Ba032be87d5EF1fbE87336B7090767F367BF73 readContract getMinDelay() = 604800retrieved 2026-05-16

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 yearn-finance factor RD-F-032 score green collected_at 2026-05-16 08:34:32