Learn · Network
Road to MainNet: TestNet 2027 to Launch
VirtEngine's launch posture is unusual for the industry: it is a checked-in, versioned decision record, not a marketing countdown. This guide reports exactly what the repository records and shows you how to verify it yourself.
The launch sequence
TestNet is planned for the January 2027 launch window. It is the public pre-production environment for multi-operator validation and may be reset; its tokens have no production value and its state is not guaranteed to migrate to MainNet.
MainNet is planned for the March 2027 launch window. It is the persistent production network and requires TestNet exit evidence, final artifacts, and a fresh go/no-go approval. Exact dates will be published through the formal launch process, and neither network should be described as live before confirmation.
Why the windows are separated
January provides real public TestNet evidence across consensus, validator and provider operations, VEID, marketplace and settlement flows, upgrades, monitoring, recovery, and incident response.
February is reserved for observing results, remediating and re-testing defects, completing security and operational reviews, freezing production artifacts, and coordinating validators. March is the MainNet window only after those exit criteria are accepted; TestNet success is not automatic MainNet approval.
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
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.
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/.
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.
Asked about mainnet roadmap
Do TestNet tokens or state carry into MainNet?
No guarantee. TestNet is pre-production and may reset; MainNet needs TestNet exit evidence, final artifacts, and a fresh approval.
What happens in February?
Observing results, remediating and re-testing defects, completing security and operational reviews, freezing production artifacts, and coordinating validators — the unglamorous work between evidence and approval.
What should operators verify before running?
That their release tag is actually published, that the target network has an approved launch or upgrade decision, and that VERIFICATION.md matches their deployment — with genesis materials validated against the published bundle in config/mainnet/.