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.
- 01
Protocol foundations
Implemented locallyThe 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.
- 02
Persistence and storage constitution
Implemented locallyDurable state under the same discipline: additive witnesses, byte-identical sealed history, write-once genesis artifacts.
Gate: Sealed on the development line.
- 03
Public proof surfaces
In developmentThis 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.
- 04
Developer preview
PlannedPublic documentation, specifications and first developer artifacts (docs.fxchain.network and related surfaces).
Gate: Unlocks when developer-facing artifacts are proven, versioned and publishable.
- 05
Deployments: devnet, then testnet, then mainnet
ReservedRunning 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.
- 06
Product activations
ReservedFxWallet, FxTrade, FxBank, FxPay and the tools follow the chain - never precede it.
Gate: Each product activates behind its own staged plan and regulatory boundaries.