Timelock duration on upgrades
stHYPE (Valantis Labs)'s assessment for RD-F-032 — scored red on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
No on-chain timelock. AccessControlDefaultAdminRules delay = 0 explicitly documented. April 9 2026 upgrade tx (0x11482a6a) executed directly via Safe.execTransaction with no TimelockController interaction. Docs state 'no protocol-wide on-chain upgrade timelock guarantee.' The '48-hour' in changelog is off-chain policy only.
Sources #
- DocsstHYPE Upgrade and Risk Governancedocs.valantis.xyz/stakedhype/upgrade-and-risk-governance — 'There is currently no protocol-wide on-chain upgrade timelock guarantee for proxy upgrades'retrieved 2026-05-17
- stHYPE Roles and Controls Registrydocs.valantis.xyz/stakedhype/roles-and-controls-registry — 'AccessControlDefaultAdminRules is initialized with delay 0 in current deployments'retrieved 2026-05-17
- HyperEVMScan — April 2026 stHYPE upgrade transactionhyperevmscan.io tx 0x11482a6a4d24946fb79d3c631310633e700b38cb4bef56a357d301339e7a6bbe — Safe execTransaction directly triggered Upgraded event; no timelock contract in call chainretrieved 2026-05-17
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 staked-hype factor RD-F-032 score red collected_at 2026-05-17 13:02:38