Upgrade multisig signer configuration (M/N)
StakeWise v3'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 #
4-of-7 multisig. Threshold=4, owner_count=7. Seven owner addresses enumerated in cache and profile. Same 7 owners on Gnosis Chain Safe (0x8737f638E9af54e89ed9E1234dbC68B115CD169e, also 4-of-7). Yellow: threshold is at lower edge of peer norm for $795M TVL LST; signer identities not fully publicly verified (only tsudmi.eth confirmed).
Sources #
- EtherscanStakeWise: MultiSig | EtherscanDAO Treasury Safe read confirms 4-of-7 configuration, 88 total transactionsretrieved 2026-05-16
- StakeWise data cache — Safe API pipeline verified00-data-cache.json sources.safe_multisigs[0]: threshold 4, owner_count 7, owners listed; api_status foundretrieved 2026-05-16
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 →