Upgrade multisig signer configuration (M/N)
Usual (USD0 / bUSD0 / USUAL)'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 #
Treasury Safes: 8/15 (collateral), 6/11 (yield), 3/7 (longterm) — confirmed via Safe API. ProxyAdmin Safe 0xaaDa24... threshold and owner count NOT retrieved (Etherscan confirms Safe contract but data cache did not enumerate this 4th Safe). Upgrade authority threshold is unknown — assessed yellow on gap.
Sources #
- EtherscanProxyAdmin Safe — Etherscan0xaaDa24358620d4638a2eE8788244c6F4b197Ca16 — Safe contract confirmed but threshold not surfaced from pageretrieved 2026-05-17
- Usual data cache — Safe multisig enumeration00-data-cache.json: safe_multisigs[0].threshold=8, owner_count=15; [1].threshold=6, owner_count=11; [2].threshold=3, owner_count=7retrieved 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 →