Upgrade multisig signer configuration (M/N)
Superstate's assessment for RD-F-026 — scored red on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
No multisig identified for upgrade authority. Both upgrader addresses (0xad309BB6... for USTB, 0x8abC89D9... for USCC) are plain EOAs confirmed via Etherscan. Safe API returns 404 for both. Effective M/N = 1/1 for each upgrade pathway. Parent funding contract 0x8C7Db8A9... has 176 transactions but is unverified on Etherscan and is not a Gnosis Safe.
Sources #
- EtherscanUSTB Upgrade Authority EOA on Etherscan0xad309BB6f13074128b4F23EF9EA2fe8552AfCA83 is an EOA (no contract code); 0x8abC89D9b56dFD90dA18e8E18CFaC9111100bDd1 is an EOA (no contract code)retrieved 2026-05-16
- Safe API 404 for USTB Upgrade EOASafe API returns 404 for 0xad309BB6... confirming it is not a Gnosis Saferetrieved 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 →