Network status

A two-stage path to production

This page reports exactly what the repository records — no more, no less. The repository is the source of truth for network status.

An operations room with wall displays.
Operations, watched closely before launch.

Launch posture

TestNet in January; MainNet in March

Last updated 17 Sep 2026. All dates and statuses come from this page — other pages link here.

Current status

Preparing

In development — the network is not live.

Public TestNet

January 2027

public pre-production

MainNet

March 2027

production, after approval

Genesis bundle

Checked in

config/mainnet/

TestNet is planned for January 2027. It is a public proving environment for validators, providers, integrations, upgrades, recovery, VEID, marketplace, and settlement flows. Its state may be reset, its tokens have no production value, and its data is not guaranteed to carry into MainNet.

MainNet is planned for March 2027. It is the persistent production network and requires successful TestNet exit evidence, final artifacts, and a fresh go/no-go approval. Exact UTC dates will be confirmed through the formal launch process; neither network is live until officially announced.

Why two stages

Validate, remediate, then promote

The separation is an explicit safety gate. January produces real multi-operator TestNet evidence. February is reserved for observation, fixing and re-testing defects, completing security and operational reviews, freezing the production release, and coordinating the final validator set.

March is the MainNet window only after those exit criteria are met. A successful TestNet launch does not automatically approve MainNet; release management must record a separate production decision.

Artifacts

Where the launch materials live

Everything an operator needs to verify is in the repository:

Parameters

Network parameters are chain state

Economic and operational parameters — inflation band, staking targets, take rate, unbonding period, approved clients — are defined by the protocol's default parameters and governed on-chain thereafter. The defaults are documented on the protocol page and in the documentation; live values on a running network always take precedence and are queryable from any node.

Operators

Preparing to validate at launch

Verify before you run

Confirm the release tag you intend to install has actually been published, that the target network has an approved launch or upgrade decision, and that the verification posture in VERIFICATION.md matches your deployment. Genesis materials should be validated against the published bundle in config/mainnet/.

Validator onboarding

The validator role, economics, dual consensus-plus-identity duties, and slashing model are covered on the staking page, with operational guides in the documentation. Start there, then coordinate with the validator community through the repository.
Validator & staking overview The road to mainnet, explained Decision record on GitHub