Timelock duration on upgrades

Wormhole'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 traditional timelock contract exists. Guardian VAA signing itself introduces inherent latency (guardians must observe, sign, and aggregate — typically minutes, not hours). Once a valid 13/19 VAA is assembled, execution on `submitContractUpgrade()` is immediate (zero on-chain timelock delay). | Governance.sol (no timelock modifier visible); search results confirming "once a properly signed VAA is submitted, changes execute immediately" | **yellow**

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 wormhole factor RD-F-032 score gray collected_at 2026-04-28 01:38:43