Upgrade multisig signer configuration (M/N)
Cap (cUSD / stcUSD)'s assessment for RD-F-026 — scored green on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Dev multisig (0xb8FC...8793): threshold=3, owners=5. Cap Token Owner multisig (0x80A2...eA): threshold=3, owners=5 (same signers). 3-of-5 configuration on both.
Sources #
- Partner feedSafe Transaction Service API — dev multisigData cache safe_multisigs[0]: address=0xb8FC49402dF3ee4f8587268FB89fda4d621a8793, threshold=3, owner_count=5, api_status=foundretrieved 2026-05-17
- Safe Transaction Service API — cap token owner multisigData cache safe_multisigs[1]: address=0x80A216738E4e49B262Deae6bEb6578Bdf164c2eA, threshold=3, owner_count=5, api_status=foundretrieved 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 →
rubric_version v1.7.0 protocol cap factor RD-F-026 score green collected_at 2026-05-17 10:56:24