Upgrade multisig signer configuration (M/N)

Orca'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 #

Pipeline-verified on-chain: 3-of-10 Squads v4 multisig. Vault PDA GwH3Hiv5mACLX3ufTw1pFsrhSPon5tdw252DBs4Rx4PV; parent multisig BQsDWkL417U4tVE2sDnPks469pKdm6YzFgKH77doiEjF. verified_threshold=3, verified_members=10. Display: 3/10.

Sources #

Tx
Squads v4 pipeline trace transaction confirming vault-multisig relationship4PyKvttqohcw8KVVwdNoFGSAjFNjvyNAtK7xasSzamW5nZei3RT3jrgtuYqVqXHD5rJ27hoJ61mboH6HVJ6sTjefretrieved 2026-05-16
Internal
Orca data cache — solana_multisigs threshold and memberscache sources.solana_multisigs[0]: verified_threshold=3, verified_members=10, retrieved_at=2026-05-16T02:13:34Zretrieved 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 orca factor RD-F-026 score green collected_at 2026-05-16 02:39:16