Emergency-veto multisig present
stHYPE (Valantis Labs)'s assessment for RD-F-040 — scored red on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
No emergency-veto or guardian multisig exists separate from the main admin Safe. PAUSER_ROLE held by the same Safe as upgrade role. Docs confirm 'no active on-chain veto mechanism.' No cancel role held by an independent party.
Sources #
- DocsstHYPE Roles and Controls Registrydocs.valantis.xyz/stakedhype/roles-and-controls-registry — no veto or cancel role distinct from main Safe listedretrieved 2026-05-17
- stHYPE Transparency and Risksdocs.valantis.xyz/stakedhype/transparency-and-risks — 'No active on-chain veto mechanism currently enforces upgrades'retrieved 2026-05-17
Methodology #
Determine whether an emergency-veto or guardian multisig exists with power to cancel malicious proposals before execution.
See the full factor methodology and distribution across all protocols →
rubric_version v1.7.0 protocol staked-hype factor RD-F-040 score red collected_at 2026-05-17 13:02:38