This summary follows §20 of the whitepaper. The progress of every item is tracked in the roadmap status document. Anything that touches consensus is scheduled and activated only through the public proposal process (AIP).
Done in the current release
Rust full node and chainstate, proof of work with ASERT, wallet with post-quantum signing, NIST level 5 signature suites from the testnet genesis, post-quantum encrypted P2P transport (hybrid Noise with ML-KEM-1024 and ML-DSA-87 node identities), hardened network sync, RPC, trustless UTXO snapshot bootstrap, native vault, recovery, multisig and HTLC flows, an embedded node library for mobile wallets, and signed source releases (ML-DSA-87 and SLH-DSA-SHAKE-256s).
Phase 2 remainder — wider public testnet
- Keep minimum chain work and assumevalid current on testnet each release; set mainnet values once it has history
- Further P2P hardening (private relay, anti-eclipse)
- Consolidated public documentation
- Wallet UX and operational fixes as they appear
Phase 3 — Mainnet preparation
- Final mainnet genesis and parameter freeze
- Quantum-mining review before the freeze: published estimates against the measured hashrate and stale rate
- External security audit, expanded fuzzing and benchmarks — no mainnet launch without an external audit
- Operational auth-data pruning and archive-node service flags
- Formal operation of mainnet DNS seeds
- Address-to-key-id resolution improvements in the wallet
Phase 4 — Advanced scaling and tooling
- Channels and payment pools, as layer-1 support only (no consensus change)
- Hardware wallets
- Relay and policy improvements that do not change consensus
- Improved operational privacy
Phase 5 — Modular compute and strong privacy
- Richer execution domains and external validity
- Strong privacy off layer 1 (including any future ring or confidential design) — not specified, not scheduled for base templates
Phases 4 and 5 are future work from the point of view of the base layer: higher layers are built off it, add no consensus rule and get no privilege from it. What the base layer owes them is honest, documented limits (whitepaper §4.3 and §5.1).