Skip to content
Network

Capabilities earned, not features launched

The roadmap is a sequence of gates, not a calendar. A stage activates when its proof exists - and not one moment before.

  1. 01

    Protocol foundations

    Implemented locally

    The constitutional core of FxChain: native laws, organs, deterministic execution and sealed eras D0-D6 on the development line, with conformance checks green on every change.

    Gate: Sealed. Later stages build on top without re-cutting what is sealed.

  2. 02

    Persistence and storage constitution

    Implemented locally

    Durable state under the same discipline: additive witnesses, byte-identical sealed history, write-once genesis artifacts.

    Gate: Sealed on the development line.

  3. 03

    Public proof surfaces

    In development

    This portal, its truth board and the changelog: the places where progress is stated factually and claims carry statuses.

    Gate: Ships in phases; the content engine follows the core pages.

  4. 04

    Developer preview

    Planned

    Public documentation, specifications and first developer artifacts (docs.fxchain.network and related surfaces).

    Gate: Unlocks when developer-facing artifacts are proven, versioned and publishable.

  5. 05

    Deployments: devnet, then testnet, then mainnet

    Reserved

    Running FxChain networks. Each deployment activates separately, and only when its capability is earned.

    Gate: No deployment is announced with a date. Activation follows proof, not calendar.

  6. 06

    Product activations

    Reserved

    FxWallet, FxTrade, FxBank, FxPay and the tools follow the chain - never precede it.

    Gate: Each product activates behind its own staged plan and regulatory boundaries.

No dates are published on purpose: a date would be a claim without proof. Progress is recorded factually in the changelog as it happens.

Watch the gates open.

The changelog records progress as it ships; the contact line is open for serious builders and institutions.