Timelock duration on upgrades

Across Protocol's assessment for RD-F-032 — scored gray on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.

Evidence summary #

Timelock duration on upgrades (hours) | **No on-chain timelock contract exists for HubPool or SpokePool upgrades.** The oSnap 3-day (originally; governance manual specifies 5-day liveness for Snapshot proposals) liveness applies only to Snapshot-originated proposals. The Across Council can execute upgrades directly via the multisig with zero delay. Effective upgrade timelock: 0 hours for Council direct-execution path. | Profile §6 ("No explicit timelock contract identified"); governance manua...

Sources #

Curator note
Extracted from 02-governance-admin.md — RD-F-032; no URL citedretrieved 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 →

rubric_version v1.7.0 protocol across-protocol factor RD-F-032 score gray collected_at 2026-04-30 21:19:18