Upgrade multisig signer configuration (M/N)
stHYPE (Valantis Labs)'s assessment for RD-F-026 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Documented 4-of-6 threshold. Safe API unavailable on HyperEVM (api_status: error). Docs-sourced with medium confidence. All 6 signer addresses enumerated in roles-and-controls-registry. Yellow because threshold is below the multisig+timelock green threshold.
Sources #
- DocsstHYPE Roles and Controls Registrydocs.valantis.xyz/stakedhype/roles-and-controls-registry — Multisig Configuration: 4 of 6 signers; 6 signers listedretrieved 2026-05-17
- Pipeline data cache — Safe API gap flag00-data-cache.json safe_multisigs[0].threshold: null; api_status: error — confirms Safe API blocked on HyperEVMretrieved 2026-05-17
Methodology #
Read `threshold` and `getOwners()` on the multisig controlling upgrade / sensitive ops. Store as `required` (M) and `total` (N); render as "M/N". For EOA admins record `required=1, total=1` (display "1/1"). Null when admin is immutable or full DAO with no fixed signer set.
See the full factor methodology and distribution across all protocols →