Network
The decision record
Mainnet is planned for the January 2027 launch window. The final date and release materials will be published through the formal launch process.
The network should not be described as live before formal launch confirmation. Verify current status from published release materials rather than assuming a service is available.
Network
What is already checked in
- config/mainnet/ — final canonical allocations and the genesis publication bundle
- _docs/operations/mainnet-go-no-go-decision.md — the formal launch decision record
- RELEASE.md and VERIFICATION.md — release engineering and artifact verification posture
- docs/COMPATIBILITY.md — version and deployment compatibility guidance
Network
What launch means operationally
At launch, validators bring the chain up against the published bundle, with the governance-approved economic parameters active from block one: identity-led allocation, conservative staking incentives, and the marketplace settlement machinery.
Network
How to verify before you operate
Operators preparing for launch should verify three things directly from the repository: that the release tag they intend to run has actually been published, that the target network has an approved launch or upgrade decision, and that the verification posture in VERIFICATION.md matches their deployment. Genesis materials should be validated against the published bundle in config/mainnet/.
Network
After genesis
Post-launch, network truth is chain state: parameters are queryable from any node, governance proposals are public, and upgrades follow the coordination machinery stakeholders vote on. The repository remains the source of truth for releases and operational posture — the habit of verifying against it should outlive launch day.