industry · quantum risk
Jupiter admin keys & Quantum Risk
Verdict
Jupiter admin/program keys are not quantum-proof. Classical upgrade authorities can change aggregator behavior.
Overview
Routing programs are high-volume infrastructure—treat upgrade keys like production root material.
Cryptographic profile
- Signatures: Host-chain account signatures for role holders (typically classical ECDSA/Ed25519), Multisig/module keys as deployed
- Hash: Host-chain dependent
- Public-key exposure: Program authorities and team operational keys
- Hosts/context: Solana aggregator programs
What breaks
- Compromise of admin keys related keys for Jupiter
- Equating role separation or multisig with post-quantum algorithms
- Untracked multi-chain deployments of the same protocol
Mitigations
- Document privileged addresses from official docs per chain
- Hardware/MPC for guardians, admins, and large governors
- Return to /is-quantum-proof/jupiter for protocol context
- Use category hubs: lending, dex, perps, stablecoins
FAQ
Governance?
/is-quantum-proof/jupiter-governance
Related?
/is-quantum-proof/dex
Key concepts (technical dictionary)
Terms used on this page — open a definition: