Mainnet Status

Last updated: 2026-04-30

Executive status

Constrained low-value canary: conditional go after the final devnet evidence bundle passes on the exact deployed program/runtime/explorer build.

Broad public mainnet launch: no-go.

This page is a launch-status marker, not a generic mainnet runbook.

Current canary scope

The only mainnet-v1 path currently being prepared is a constrained marketplace canary:

Out of scope for base mainnet-v1

These surfaces are not launch blockers because they are intentionally excluded from the first base canary:

Deployment order gate

Protocol account-layout changes must be deployed before runtime/CLI/explorer builds that depend on those layouts.

Required order:

1. deploy upgraded protocol containing launch controls
2. verify IDL/account layout on target cluster
3. deploy or pin runtime/CLI/explorer build aligned with that protocol
4. run set-job-spec and cancel-dispute smoke transactions
5. run the full devnet evidence suite

A mixed old-protocol/new-runtime deployment is a no-go.

Required evidence before canary launch

The canary can only launch after evidence is attached for:

Use /docs/deployment/devnet-validation for the active command set.

Canary launch configuration

Recommended canary defaults:

What changed since the old status page

The docs used to say no stable mainnet path existed. The current state is more specific:

Telegram buyer rails

The remaining gate is not a new code surface. It is the final live devnet evidence package for the exact deployed build.

Final rule

Go:

No-go:

enforced