Ed25519 is not quantum-safe. Shor's algorithm breaks Curve25519 just as efficiently as secp256k1. Jupiter's aggregator position makes it the single densest ed25519 HNDL archive on Solana — and the JUP airdrop built the most complete user key registry in a single event.
This is one of the most widely repeated — and most dangerous — myths in the Solana ecosystem. Here is the exact reason it is wrong:
ed25519 ≠ quantum-safe. Solana uses ed25519 (Curve25519 / Edwards25519). This is an elliptic curve signature scheme. Shor's algorithm solves the elliptic curve discrete logarithm problem in polynomial time — on Curve25519 just as effectively as on secp256k1. The curve is different. The vulnerability is identical.
Quantum-safe = lattice or hash-function-based. NIST FIPS 203 (ML-KEM / Kyber), FIPS 204 (ML-DSA / Dilithium), and FIPS 205 (SLH-DSA / SPHINCS+) are quantum-resistant. They do not use elliptic curves. Neither secp256k1 nor ed25519 qualifies. Both are Shor-vulnerable.
User signs a swap via Jupiter: a single signed ed25519 transaction routes through Raydium, Orca, Phoenix, Meteora, Lifinity simultaneously — one signing event archives keys across all liquidity sources at once.
Jupiter Perps / JLP interaction: JLP providers and perps traders sign continuous deposit, withdrawal, fee-claim, and position-update transactions — high-frequency ed25519 key interaction archive per address.
JUP governance vote: every vote is a signed ed25519 transaction from the voter's wallet — governance corpus sorted by JUP balance = ranked HNDL attack queue for largest governance participants.
CRQC decryption: Shor's algorithm recovers ed25519 private keys from the permanent Solana ledger archive → wallet drain, governance capture, JLP liquidity theft, perps position manipulation — all from archived signed transactions.
The January 2024 JUP airdrop distributed 700M+ JUP to hundreds of thousands of wallets. Every claim transaction was a signed ed25519 key commitment archived on Solana's permanent ledger — the most comprehensive single-event user HNDL registry in Solana's history. Sorted by wallet size, it is a ready-made CRQC priority attack queue.
Jupiter routes the majority of Solana's DEX volume. Every aggregated swap is a signed ed25519 transaction permanently archived on Solana's ledger since 2021. Because Jupiter covers all major AMMs simultaneously, its transaction archive represents the widest cross-section of Solana user ed25519 keys on any single protocol — richer HNDL coverage than Raydium, Orca, or any individual AMM alone.
JUP holders stake tokens for governance voting and Active Staking Rewards (ASR). Every governance vote is a signed ed25519 transaction permanently archived. Largest vote-locked JUP addresses represent highest-value governance targets. Recovering a threshold of top governance addresses enables adversarial protocol control without acquiring any JUP — bypassing normal token-weighted governance entirely.
Jupiter Perps uses a keeper network to execute pending orders (open, close, liquidate positions). Keeper wallets sign every execution transaction with ed25519. A CRQC recovering keeper keys grants adversarial control over all pending order executions platform-wide — enabling selective liquidation suppression, front-running, and fabricated settlement at scale.
JLP (Jupiter Liquidity Pool) providers deposit SOL, BTC, ETH, USDC, and USDT to serve as counterparty to all Jupiter Perps traders. Providers interact continuously through deposit, withdrawal, and fee-claim signed ed25519 transactions. Recovering JLP provider keys enables adversarial withdrawal of pool liquidity — removing backstop capital for all active perps positions simultaneously.
Jupiter Limit Orders and DCA (Dollar-Cost Averaging) functionality archives signed ed25519 open-order and cancellation transactions. Long-running DCA plans generate extended high-frequency key interaction archives per address. Recovering these keys enables adversarial modification or cancellation of pending orders across all Jupiter structured-product users.
Jupiter's upgrade authority and administrative multisig use ed25519 keys. Threshold recovery of upgrade authority signers grants adversarial control over all Jupiter program accounts — enabling malicious contract upgrades that redirect fees, drain liquidity, or disable the platform entirely. Single highest-impact administrative target in the Jupiter ecosystem.
Jupiter aggregates Raydium, Orca, Phoenix, Meteora, Lifinity, and other AMMs. A CRQC targeting any upstream AMM's admin or LP provider keys cascades into Jupiter's routing — reducing available liquidity and potentially causing Jupiter's best-route to redirect through compromised pools. Jupiter inherits quantum exposure from every protocol in its aggregation stack.
Archive phase (2021 → present): State-level adversary harvests Solana's permanent ledger — JUP airdrop claims (Jan 2024), all Jupiter swap transactions (2021→present), governance votes, JLP interactions, DCA/limit order archives. Sorted into priority queues: airdrop claim wallets by JUP received; swap users by lifetime USD volume; JLP providers by pool share; governance voters by vote weight.
CRQC decryption — priority targets: First pass — Jupiter Perps keeper execution keys (controls all pending order execution platform-wide). Second pass — JUP governance top holders (protocol control without token acquisition). Third pass — JLP provider keys ranked by pool share (liquidity backstop drain). Fourth pass — airdrop claimants ranked by JUP received (largest individual wallet drains).
Execution layer compromise: Recovered keeper ed25519 keys enable adversary to selectively suppress liquidations (letting underwater positions grow), front-run all pending orders, and fabricate settlement prices. All active Jupiter Perps traders are simultaneously exposed — JLP acts as the counterparty bearing losses from adversarially manipulated settlements.
JLP drain + governance capture: JLP provider keys enable adversarial pool withdrawal — removing liquidity backstop before liquidations are triggered, causing undercollateralised positions to cascade through JLP. Simultaneously, recovered governance top-holder keys redirect JUP DAO votes — protocol freezes, fee parameter changes, or upgrade approvals all executable without legitimate token-holder participation.
Solana-wide cascade + admin capture: Recovered upgrade authority keys enable malicious Jupiter program upgrades — redirecting all swap fees, inserting backdoors, or draining protocol-owned liquidity accounts. Because Jupiter routes through all major Solana AMMs, market disruption spreads immediately to Raydium, Orca, and Phoenix — affecting the entire Solana DeFi ecosystem through Jupiter's aggregator centrality.
Jupiter's quantum migration is uniquely complex because it depends on Solana L1 first — a prerequisite entirely outside Jupiter's control. No JIP (Jupiter Improvement Proposal) addressing post-quantum cryptography has been published as of September 2026.
Solana L1 ed25519 replacement (external prerequisite — Jupiter cannot proceed without this): Solana's base-layer address format, validator consensus, and transaction signing all use ed25519. Jupiter's wallets, programs, and governance cannot migrate to PQC addressing until Solana itself introduces a new post-quantum address scheme. No Solana Foundation PQC roadmap has been published as of September 2026. This single dependency blocks all downstream migration.
JUP token re-issuance across hundreds of thousands of wallets: JUP was distributed to hundreds of thousands of wallets in the January 2024 airdrop and subsequent distributions. A new PQC-addressed JUP token contract requires every holder to migrate their balance to a new quantum-safe address — coordinating migration across the largest Solana airdrop recipient set without a single centralised migration authority.
Jupiter Perps keeper network re-architecture: All keeper execution wallets must be replaced with PQC-signed equivalents. Because keepers are continuously executing live order settlements, migration must be zero-downtime — any gap between old and new keeper key sets creates a window where orders are unexecutable. Live open positions cannot be simply paused during keeper migration without forcing losses on all active traders.
JLP provider key rotation and pool contract upgrade: All JLP provider addresses must migrate to PQC equivalents. The JLP pool contract itself requires an upgrade to accept new PQC-format deposit and withdrawal instructions. Provider migration must be coordinated to avoid pool liquidity gaps during the transition window — any gap leaves active perps positions undercollateralised.
JUP governance vote-lock migration (circular dependency): DAO governance vote-locks must be migrated to new PQC-addressed wallets. But the governance migration proposal itself requires JUP holder votes — which must be cast using the same ed25519 keys being migrated. This circular dependency (migrate the keys that must approve the migration) means governance migration cannot be approved by normal vote during active CRQC threat.
Upstream AMM aggregation compatibility update: Jupiter's routing must be updated to route through PQC-compatible liquidity sources only. This requires Raydium, Orca, Phoenix, Meteora, Lifinity, and every other AMM in Jupiter's routing table to independently complete their own PQC migrations first. Jupiter cannot aggregate quantum-safe swaps until every upstream AMM it routes through has individually migrated — a multi-protocol, multi-team coordination dependency with no central authority.
DCA, Limit Order, and structured product re-architecture: Jupiter's DCA and Limit Order products maintain long-running signed instruction sets. All open DCA plans and limit orders must be cancelled and re-created under new PQC-addressed wallets. Extended-duration DCA plans have the highest HNDL accumulation risk — migration must either force-close or provide a transparent migration path for ongoing plans without retroactive HNDL exposure.
This analysis focuses on post-quantum risk. Jupiter has significant classical-security and product achievements — none of which address quantum key vulnerability.
Jupiter consistently routes 70–80% of Solana's DEX volume. Best-route execution across Raydium, Orca, Phoenix, and Meteora delivers minimal slippage for traders of all sizes.
The JUP airdrop was one of the largest token distributions in crypto history — establishing a broad, decentralised governance base and strong community alignment from day one.
Jupiter Perps provides a fully on-chain perpetual futures platform with JLP as the liquidity backstop. Deep integration with Solana's speed and low-cost architecture enables a competitive perps product.
Jupiter's DCA and Limit Order products extend beyond simple swap aggregation — enabling structured on-chain accumulation strategies and conditional execution without centralised custody.
The ASR governance framework aligns long-term JUP holders with protocol direction. Vote-locking incentivises governance participation and reduces short-term speculative governance attacks.
Jupiter's deep integration across Solana's AMM landscape gives it a near-comprehensive view of on-chain liquidity — an infrastructure advantage that has compounded over multiple years of operation.
| Criterion | Jupiter (JUP) | BMIC |
|---|---|---|
| Signing Algorithm | ed25519 (Curve25519) — Shor-vulnerable | ML-DSA (CRYSTALS-Dilithium) NIST FIPS 204 — quantum-resistant |
| Key Encapsulation | None (no PQC key exchange layer) | ML-KEM (CRYSTALS-Kyber) NIST FIPS 203 |
| Hash-Based Signatures | Not implemented | SLH-DSA (SPHINCS+) NIST FIPS 205 |
| HNDL Risk Level | Critical — densest ed25519 HNDL corpus on Solana (aggregator position) | Designed to be HNDL-safe from day one |
| JUP Airdrop HNDL | 700M+ JUP airdrop = largest single-event Solana HNDL registry | Not applicable — BMIC uses PQC from launch |
| PQC Migration Plan | No JIP published (Sep 2026) | PQC-native from day one |
| Governance Key Risk | JUP vote-lock governance — ed25519 keys HNDL-archived since 2024 | ML-DSA governance signing |
| Keeper Execution Risk | Centralised keeper ed25519 keys control all perps order execution | ERC-4337 account abstraction — no classical keeper key dependency |
| Upstream Dependency | Cannot migrate until Solana L1 upgrades (external blocker) | Ethereum + ERC-4337 path; PQC wallet layer already deployed |
| NIST FIPS Compliance | Not applicable — no PQC | FIPS 203 + FIPS 204 + FIPS 205 |
| Account Abstraction | Solana native account model — no ERC-4337 equivalent | ERC-4337 — quantum-safe transaction bundling |
| Governance Circular Dependency | PQC migration vote requires ed25519 signatures from keys being migrated | No legacy key dependency in governance architecture |
Unlike Jupiter, which inherits Solana's ed25519 cryptographic foundation with no published PQC migration path, BMIC's architecture is designed around NIST-standardised post-quantum primitives from launch.
ML-KEM (CRYSTALS-Kyber) — NIST FIPS 203: Lattice-based key encapsulation. Used to wrap vault and backup encryption keys, so a harvested archive remains unreadable without the lattice private key — not vulnerable to Shor's algorithm.
ML-DSA (CRYSTALS-Dilithium) — NIST FIPS 204: Lattice-based digital signatures. Used to attest device handoff and backup integrity — replaces the ed25519 / secp256k1 signing layer that Shor's algorithm targets on Solana and Ethereum.
SLH-DSA (SPHINCS+) — NIST FIPS 205: Hash-function-based signatures. Security derived from SHA-3 — zero elliptic curve dependency. No Shor's algorithm attack path exists.
ERC-4337 Account Abstraction: Enables quantum-safe transaction signing and bundling without reliance on secp256k1 or ed25519 Externally Owned Accounts. The smart contract wallet layer decouples identity from classical key types.
Jupiter's ed25519 key architecture is efficient and fast for classical threat models. Against a CRQC, ed25519 provides identical vulnerability to secp256k1 — Shor's algorithm attacks both with polynomial-time complexity. The curve is different. The security outcome is the same.
No. Jupiter operates entirely on Solana's ed25519 cryptographic infrastructure. Ed25519 (Curve25519) is an elliptic curve signature scheme vulnerable to Shor's algorithm. Every JUP governance vote, swap transaction, perps position, and airdrop claim is archived on Solana's permanent ledger. No JIP addressing post-quantum migration has been published as of September 2026.
No. Ed25519 uses the elliptic curve discrete logarithm problem on Curve25519 for security. Shor's algorithm solves this problem in polynomial time on a cryptographically-relevant quantum computer — the same attack path used against secp256k1 on Ethereum. The different curve does not change the algorithmic vulnerability. Quantum safety requires lattice-based or hash-function-based cryptography (ML-KEM, ML-DSA, SLH-DSA), not ed25519.
Jupiter's January 2024 JUP airdrop distributed 700M+ JUP to hundreds of thousands of wallets. Every claim transaction permanently archived an ed25519 signed key commitment on Solana's ledger. This created the largest single-event Solana user HNDL corpus in the blockchain's history — a ranked adversarial priority queue sorted by JUP received, ready for CRQC decryption when the technology becomes available.
Jupiter's address space, transaction signing, governance, and token contracts all use Solana's ed25519 account model. Solana L1 must introduce a post-quantum address scheme at the protocol level before any Solana application can migrate. Solana has published no PQC roadmap as of September 2026. This external dependency blocks Jupiter's migration regardless of Jupiter's own technical capacity or team intent.
BMIC implements NIST FIPS 203 (ML-KEM / CRYSTALS-Kyber), FIPS 204 (ML-DSA / CRYSTALS-Dilithium), and FIPS 205 (SLH-DSA / SPHINCS+) — post-quantum primitives explicitly designed to resist Shor's algorithm. Jupiter operates on ed25519 with no PQC layer. BMIC also uses ERC-4337 account abstraction to avoid classical elliptic curve key dependencies entirely. Jupiter has no equivalent.
BMIC is the only presale-stage crypto project built on NIST FIPS 203/204/205 post-quantum cryptography. Jupiter routes on ed25519 — Shor-vulnerable, no migration path. BMIC is quantum-safe from day one.
Buy BMIC — bmic.ai →⚠️ DYOR. This is not financial advice. Crypto presales carry substantial risk including total loss of capital. Always verify independently before investing.