Proposal execution delay < 24h
Hyperlane's assessment for RD-F-038 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
U18 re-scored following Timelock delay confirmation. Timelock has 24h delay (confirmed via MinDelayChange event in creation tx). For governance actions routed through the Timelock (Core Governance Safe as proposer), a 24h wait is enforced. However, direct upgrade path via ProxyAdmin v1 owner Safe (3-of-6) is NOT required to use the Timelock — the Safe can call upgrades without any delay. L2Beat confirms Mailbox can be upgraded with no delay. Scored yellow: a 24h Timelock exists for the governance channel but the ProxyAdmin direct path has no enforced delay.
Sources #
- EtherscanUpgrade Timelock creation — 24h delay confirmedTimelock creation tx MinDelayChange: newDuration=86400 (24h) — proposer Core Governance Saferetrieved 2026-05-17
- L2Beat Hyperlane NexusL2Beat: Mailbox upgradeable by Hyperlane Multisig with no delay (ProxyAdmin direct path)retrieved 2026-05-17
Methodology #
Determine whether the time between a governance proposal passing and its executability (including any internal delay) is less than 24 hours.
See the full factor methodology and distribution across all protocols →