Upgrade multisig signer configuration (M/N)

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

JUP token vaults: 4/7 multisig (documented). Signers include Jupiter team, independent ecosystem signers (Mert/Helius, Stepan/Squads, Nico/Neodyme), and professional custodians. Program upgrade authority multisig: Squads usage confirmed but specific multisig address, threshold, and signer count not publicly disclosed. Cannot confirm M/N for the program upgrade authority.

Sources #

Governance
JUP Minting and Accountability | Jupiter Research ForumJUP Minting and Accountability forum post with signer detailsretrieved 2026-04-29
URL
Deep Dive into Jupiter | CoinMarketCapJupiter tokenomics multisig structureretrieved 2026-04-29

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 jupiter factor RD-F-026 score yellow collected_at 2026-04-29 11:51:25