Upgrade multisig signer configuration (M/N)

Beefy Finance'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: 3-of-6 (0x34fEf5DA92c59d6aC21d0A75ce90B351D0Fb6CE6). Treasury multisig: 4-of-7 (0xc9C61194682a3A5f56BF9Cd5B59EE63028aB6041). Per-chain treasury Safes (Arbitrum, BSC, Optimism, Base, Polygon) all 4-of-7. Thresholds confirmed by data cache Safe API returns (api_status=found for all).

Sources #

Docs
Beefy Contracts and Timelocks Documentation3/6 signer multisig controls privileged functions; 4/7 treasury multisigretrieved 2026-05-16
Internal
Beefy data cache — all Safe multisig thresholds00-data-cache.json safe_multisigs[]: threshold and owner_count for all 7 Safesretrieved 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 →

rubric_version v1.7.0 protocol beefy factor RD-F-026 score green collected_at 2026-05-16 13:10:30