Timelock duration on upgrades
M^0'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 #
No OZ TimelockController. TTG epoch provides ~30-day minimum delay for standard proposals (Transfer + Voting epoch). EmergencyGovernor uses threshold voting — potentially < 24h if threshold POWER percentage is met. Periphery proxy upgrades have zero delay (deployer EOA direct).
Sources #
- EtherscanSwapFacility Proxy — EtherscanSwapFacility proxy admin = EOA: no timelock on admin roleretrieved 2026-05-16
- EmergencyGovernor.sol — m0-foundation/ttg GitHubEmergencyGovernor source: execute() without TimelockController delayretrieved 2026-05-16
- M^0 TTG Governance OverviewStandard proposals: ~30 day minimum (Transfer + Voting epoch cycle)retrieved 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 m0 factor RD-F-032 score yellow collected_at 2026-05-16 09:46:19