Admin key custody type
Jupiter's assessment for RD-F-025 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Jupiter uses multisig custody: Squads-based for program upgrade authority; 4-of-7 multisig for JUP token vaults (Team Cold, Community Cold, Team Hot, Community Hot). No pure EOA admin documented. During governance pause since June 2025, founding team exercises de facto protocol authority without on-chain constraint. Admin key custody type is multisig but effective control during pause is centralized to founding team.
Sources #
- URLDeep Dive into Jupiter | CoinMarketCapJupiter tokenomics 4-of-7 multisig structureretrieved 2026-04-29
- JUP Minting and Accountability | Jupiter Research ForumJUP minting and accountability — multisig signer detailsretrieved 2026-04-29
- Managing Program Upgrades with Multisig: Case Study & Best Practices | SquadsSquads blog naming Jupiter as Squads userretrieved 2026-04-29
Methodology #
Read the effective admin/owner/upgrader role on deployed contracts and classify as: EOA / multisig / multisig+timelock / full DAO+timelock / immutable.
See the full factor methodology and distribution across all protocols →