The road to mainnet: gates, not dates
You will be able to list what has to be true before mainnet opens, say which of it is already evidenced, and recognise a launch promise that skips a step.
The rule
There is no launch date, and that is the policy.
Mainnet is locked in the software itself, and it opens when validation is complete rather than when a calendar says so: audit findings closed, the network holding under stress, releases reproducible. No presale and no promise of return is attached to it. Anyone quoting a launch date or selling an early allocation is describing something this project does not offer, and there is no allocation to sell, because nothing is premined.
The gates
Freeze, sign, spread out, burn in, audit.
The order is written down. The consensus rules are frozen at a tagged commit. A release is built from that commit with signatures, a bill of materials and provenance, and rebuilt by a second builder to show the bytes match. Several producers run it in separate failure domains, meaning different hardware, networks and people, through a thirty-day burn-in with divergence monitoring. The frozen commit is then audited independently, the findings are closed, the release is rebuilt and burned in again, and only then is launch considered.
Where it stands
Some gates carry evidence; others have not started.
The readiness record marks a gate done only when it has been checked, not when something was built. Evidence exists for much of it: the full test suite, adversarial tests for eclipse, partition and crash recovery, mainnet's own genesis rules running in a test chain, and a public testnet release whose signatures and independent rebuild anyone can verify. The consensus freeze, the multi-operator burn-in and the audit of a frozen commit have not started. The independent reviews carried out so far produced findings to close, not a clearance.
What launches, and what waits
Mainnet opens with the core and nothing else.
The first mainnet release carries the base chain: mining, validation, post-quantum signatures, the RPC and the explorer. Wrapped assets stay switched off at launch, and each one activates later as a separate event with its own audit and its own proof of reserve. Mainnet starts from its own genesis with nothing premined, which is the only honest way to begin a chain whose testnet has, until then, been a place to learn and to break things.
In short
- Mainnet opens on evidence, not on a date, and there is no presale or allocation to buy.
- The gates run in order: freeze, signed reproducible release, independent producers, burn-in, audit.
- Tests and a verifiable release are evidenced; the freeze, the burn-in and the frozen-commit audit have not started.
- Mainnet launches with the core only, from its own genesis; wrapped assets activate one by one afterwards.
Keep reading