Roadmap

Milestones, in order, without dates. Each item moves to "Live" when it is proven on the test environment and released to production, not before. The order is the plan; the pace follows the proofs.

#Live

• Final Wallet on five mainnets. Ethereum, Optimism, Base, Arbitrum and Polygon, armed with the post-quantum anchor, the identity root and the four signer sets. Post-quantum-native wallet creation is open.
• The Pre-Final Chain, the state plane in service today. Account ledger, intent log, bundle log, settlement log, registries, the PHI supply ledger (no external submission yet), post-quantum precompiles; one-second blocks, final when produced. Final Chain itself is still in development; this build is temporary and not open to external execution, and all data moves to Final Chain when it is released.
• The post-quantum execution lane, end to end. Encrypted intents admitted by a post-quantum quorum, anchored, and executed on the target chain with no operator step: immediate and approval-gated intents; sub-account creation; Launch Sale purchases; a cross-chain settlement lock.
• Transport without hot keys. No long-lived spend key anywhere in transport; single-use accounts where a private builder lane exists.
• PHI Launch Sale. Armed on all five mainnets; purchases are admitted on the Pre-Final Chain. It opens in month 4, after the Malta license (around month 3), then runs its one-month window — 5 % of PHI at a fixed USD 1.00. The six-month ICO opens in month 5, right after that sale, price growing every hour. Unsold PHI goes to the reserve, never the team. See PHI Tokenomics.
• Explorer and dashboard, both environments.
• Morphing. Live on the Pre-Final Chain now: long or short exposure from locked PHI, maximum loss the PHI morphed, no debt. Settlement moves to Final Chain at its launch. See Morphing.
• Developer tools. The testnet PHI faucet and the test endpoints.
• Key rotation and guardian freeze that do not wait for inactivity. Both act on the account ledger; the account plane is carried to every chain as soon as it changes.

#Building now

• Documentation. This wiki and the site's docs, maintained as one.
• Scheduled execution that lands at the chosen time. The lead gate and the contract side are in place on the test environment. A scheduled intent can be cancelled until 90 seconds before execution (per target chain) and executes in the first block at or after its time.
• Private intents, the wire first. The envelope header that hides who an intent's recipients are is in service on test; the sealed content nobody can read early follows (see After).

#With the release

After the live wallet: the one-month Launch Sale in month 4, the ICO in month 5, then MultiDEX.

• The browser extension. The new wallet lands as an extension with its own provider announced to pages (never intercepting another wallet's), an isolated WebAssembly post-quantum core, and a plain typed-data signing lane for ordinary accounts. The interface is rebuilt from the user guide, not from the contracts.
• Post-quantum tunnels to the Pre-Final Chain. Certificate-authenticated, key-encapsulated sessions from the wallet to our nodes, terminating at the node rather than at a TLS edge.
• Receipts and direct reads everywhere. Every posting answers with a receipt that carries the real transaction hash; state-plane readers answer by lookup, never by scanning blocks.
• Settlement-class calls execute on idle chains without waiting for a bundle, so registries and roots stay in sync everywhere.
• vAssets on mainnet. The settlement roots are advanced on all five mainnets; the per-chain registry copies land with the release.
• Public ICO. Opens in month 5, right after the one-month Launch Sale, at USD 2.00, and runs for six months.
• 50 chains by the ICO. Five mainnets are live with the wallet; the deployment is automated end to end, and the target is fifty chains by the time the ICO opens — the same address for every wallet on each, the chain count visible on the site as it grows.
• MultiDEX. Cross-chain asset trading, the next product after the ICO, before Final Chain and the Liquidity Cloud.
• Locks at scheduling. Assets and fee set aside when an intent is scheduled, released inside the execution, for wallets and — through the settlement custody — for plain accounts.
• Private intents in full. Nobody, the operator included, can read an intent before it is due: per-slot member keys released only when the slot opens, and the private option priced on the ladder.
• Paying every fee in PHI. Locked PHI on any chain, native gas sponsored by the protocol, tier discounts from the particle ladder.
• A wider cryptographic suite in the nodes. FN-DSA-1024 (FIPS 206) beside ML-DSA-87; Classic McEliece-8192128 and FrodoKEM-1344 beside ML-KEM-1024 and HQC-5, four key-encapsulation families in total; a four-cipher content cascade (four nested authenticated layers); key generation split across nodes for every algorithm.

#Next: Final Chain

• Final Chain, the Quantum Tesselated Protocol. Today's Pre-Final Chain is temporary. Final Chain's architecture has diverged from it: asynchronous by design, participation per module and per zone in a UTXO-like model alongside the EVM — fully EVM-compatible, as the Pre-Final Chain is today; only strictly sequential parts of a protocol behave differently, and a dedicated lane lets them persist their ordering — and a global attestation chain over the whole. It keeps every interface this documentation describes: the same ledgers and logs, the same proofs, the same precompiles, the same certificate roots. PHI becomes its execution asset; every fee there goes to holders and node operators.
• vAssets morph on Final Chain — scheduled with the Final Chain release. Positions in vAssets morphed on the state plane from the day Final Chain is released. The Liquidity Cloud follows Final Chain. See Liquidity Cloud.
• Services become node modules. The fleet's functions move into the node: indexing, co-signing and slot keys, the shard log, the fee ledger, settlement, the node-facing encrypted tunnel, routing and protection, and the HTML interface.
• How it is built. Post-quantum Byzantine fault-tolerant consensus. Blocks are not on a fixed cadence: block intervals are ranges set by priority, down to one millisecond, with finality in 50 milliseconds — and no empty blocks anywhere, a block exists because something happened. All time is denominated in nanoseconds, for the parallel, globally asynchronous admission of DAG vertices and for the quantum internet. The global attestation chain carries only the reconciliations and the zero-knowledge proofs of the active zones and groups within a global block ticker; its blocks are not hash-joined but chained by the public keys of two post-quantum algorithms, with the verifications chained in turn.
• Keys made by the network. Key generation decentralised across nodes for every key, under our own secret-sharing construction (a Shamir variant), so no complete secret exists in one place. For Final Chain, not the Pre-Final Chain.
• Your own zone. Participation is per zone, and a zone can be yours: a company, a government or any institution can host a zone with access, privacy and permission rules tuned to its needs — its own rules for its own users — secure and private, and always integrated with Final Chain rather than apart from it. A module's scope is the whole chain, one zone or one group, and identities join and leave modules as they please.
• Nodes upgrade independently; modules earn by use. User-based module incentives: demand for a module, a new one or an upgrade grows with the users who want it, and operators who adapt faster earn more.

#After

• Staking on Final Chain nodes. Delegated proof of stake (dPoS), open to every PHI holder by delegation from their own wallet — not only to node operators. Fees split between holders, node operators and the treasury that funds module incentives, moving toward the operators as the incentive pools are spent; nothing burned; a staking reserve releasing 12 % of what remains each year; rewards scaled by the particle ladder and by the node types and modules run; delegation that never moves PHI out of a wallet. See PHI Tokenomics and PHI.
• Chains as modules. Other chains join Final Chain as modules, wrapped in post-quantum security together with their assets. See the whitepaper's end state.
• Platforms as modules; one identity to publish and to prove. Current apps and platforms become modules through special connectors; on compatible platform modules a Final Certificate is mandatory for publishing and carries the platform's trust scores; KYC is streamlined — the user discloses what they choose, revocation is leaving, and the saving is shared between the person, the protocol, and all holders and operators. See Final Identity.

#How to read this page

Nothing here is a promise of a date. Items move up as the test environment proves them; the order is what we commit to.

#See also

Whitepaper · Architecture overview · Operations and environments