Timelock duration on upgrades

Rocket Pool'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 #

RPIP-60 (Protocol Upgrade Guardrails) mandates a 1-week upgrade_delay between proposal approval and execution. Combined with the 1-week vote delay, total time from proposal to execution is ~2 weeks (336 hours). This substantially exceeds the 48-hour green threshold. Implemented at Saturn One (February 2026).

Sources #

GitHub
RocketDAOProtocolSettingsProposals.solRocketDAOProtocolSettingsProposals constructor: voteDelayTime = 1 weekretrieved 2026-05-04
Governance
RPIP-60: Protocol Upgrade GuardrailsRPIP-60: upgrade_delay initially set to 1 weekretrieved 2026-05-04

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 rocket-pool factor RD-F-032 score green collected_at 2026-05-04 15:40:28