Skip to main content

Roadmap

This roadmap is organized as milestones, not a status board. Workstreams run in parallel; sequencing may adjust based on benchmarks, audits, and ecosystem readiness.

Scope: This roadmap covers Quantum L1 and the layered stack built on it. It does not cover making other chains quantum-safe, retroactively securing ECDSA addresses (cryptographically impossible), or specific delivery dates (the order of milestones is more meaningful than dates that would only be wrong).

Completed​

  • Devnet 1 — Falcon signatures on Simplex consensus.
  • Devnet 2 — ML-DSA-44 userland authorization + Falcon consensus on Commonware + EVM-compatible execution. Full PQ stack: composite transaction type 0x7A, KeyVault precompile (key rotation + scoped access), CryptoSwitchboard precompile (runtime algorithm governance), pre-EVM composite signature verification, verifier precompiles.
  • PQ Smart Wallet prototype — End-to-end system complete, Arbitrum as initial chain, PQ verifier deployed. See PQ Smart Account.
  • Mithril implementation — Constant-time implementation of threshold ML-DSA (ePrint 2026/013). See Mithril.
  • pq-encoder and pq-oid (TypeScript & Rust) — DER / JWK / PEM encoding for PQ keys and signatures; OID constants for ML-KEM, ML-DSA, SLH-DSA. See post-quantum-packages.
  • Litepaper v0.9 published; crypto-agile hedging framework designed.
  • RalphStarter.ai launched — 2,000+ developer downloads in week 1.

PQ Wallet Layer (cross-chain)​

  • Verifier contracts deployed per supported chain (ML-DSA lane). Stylus-based on Arbitrum; pure-EVM verifier in development for non-Stylus chains.
  • PQ smart wallet library — wallet delegates verification to verifier contract. See PQ Smart Account → ERC-7579 validator module.
  • Local PQ signing tool (CLI) and integration into standard dev pipelines.
  • Foundry / Hardhat enablement, with upstream PRs where feasible.
  • Frontend onboarding and migration flows. See Asset migration and quantum-safe UX.
  • Native Quantum wallet with MPC, TEE, and Mithril threshold ML-DSA.
  • Expanded wallet integrations.

Quantum L1 (PQ-by-default chain)​

Devnet 3 — NonceManager, gas economics, epoch manager, Quantum CLI​

  • NonceManager precompile for 2D nonce tracking (RIP-7712 style).
  • Native gas sponsorship via envelope-level fee payer.
  • Block gas economics — fee market tuning, gas pricing for PQ precompiles.
  • Epoch manager — validator set transitions, epoch-based state management.
  • Quantum CLI — key management, transaction submission, node operations.

Devnet 4 — Threshold certificates for consensus (optional, benchmark-gated)​

PQ threshold signatures with DKG to compress quorum proofs into a single signature. Must not erase Simplex's fast-path advantages. Benchmark-gated; Ringtail is a candidate but not committed.

Entanglement bridge​

  • LayerZero v2 integration (adapters + bridge cores).
  • PQ boundary enforcement: pending credit → PQ claim().
  • Required PQ-DVN in EVM → Quantum security stacks.
  • End-to-end benchmarks and operational runbooks.

See Entanglement bridge.

Testnet → Mainnet​

Testnet​

  • Full surface enabled (consensus + PQ userland + Native AA + supported wallet-layer components).
  • Multiple independent audits:
    • Consensus and networking.
    • PQ transactions and precompiles.
    • Bridge and DVN.
    • Verifier contracts and smart wallet.
    • Mithril.

Mainnet​

  • Launch and bug bounty.
  • QCN begins as a post-launch track (phased, benchmark-gated). See QCN.

Post-mainnet — P2P transport PQ-KEM evaluation​

We will evaluate adopting ML-KEM (Kyber) for P2P key establishment based on:

  • Measured operational need — confidentiality expectations, metadata sensitivity, threat model evolution.
  • Measured performance impacts — CPU, bytes, tail latency.
  • Implementation maturity, auditability, incident response readiness.

No hybrid KEM design is planned at this stage. The goal is a clean single-lane decision if and when measured need and risk justify it.

  • Litepaper summary — the one-page brief that maps to this roadmap
  • Benchmarks — what we measure to gate the benchmark-gated items
  • Threat model — what each milestone improves and what it doesn't