Q markQUADLaunch Signals

Mainnet Launch Signals

Core is in public testnet observation. This page defines what can end testnet, what can start mainnet, and which labels stay refused until the public facts change.

ReadinessSecurityUsage EvidenceCommunications

Public Testnet End Criteria

Testnet ends only when the observable system has enough receipts to stop calling the run exploratory.

  • Runtime stability. Core builds, boots, produces blocks, keeps public RPC and static observation pages reachable, and survives operator ingress without unexplained halts.
  • Economic path receipts. Mint, Treasury, Alloc, Seller, Restaker, Distributor, Sink, Quarantine, Exchange, and Bridgechain receipt paths have public or operator-verifiable proof for their intended roles.
  • Truth freshness. Oracle, market, Treasury, economics, and action surfaces fail closed when stale or unsupported.
  • Wallet and explorer readiness. Public chain metadata, wallet add instructions, explorer links, validator list, and transaction lookup are documented enough for outside operators to inspect.
  • Security disclosure path. Audit status, high-sensitivity surfaces, and a vulnerability disclosure route are public before mainnet labels are used.

Mainnet Start Criteria

Mainnet is not a marketing word. It requires a frozen posture that can be inspected, operated, and rolled forward without private assumptions.

Genesis freeze candidate

Genesis must match the documented asset law, supply law, escrow posture, validator posture, and initial custody split.

Operator runbooks

Emergency posture, public endpoint policy, validator setup, relayer behavior, and disclosure handling must be written before broad launch.

Independent inspection

Audit status, security posture, public receipts, governance posture, and validator independence must be labeled honestly.

No hidden claim upgrade

Testnet blocks, faucet activity, private endpoint inventory, or route dry-runs do not become production usage or mainnet readiness by implication.

Date And Label Discipline

Dates and labels are public facts, not pressure tools.

Mainnet dateNo mainnet date is published until the criteria above are credible. Date slipsIf a public date is later published and moves, the public reason must move with it. Mainnet labelsMainnet, production, live value, final freeze, and launch labels appear only after mainnet is actually live. Usage labelsTestnet traffic, faucet traffic, relayer funding, and internal endpoint boxes are not public usage claims. Readiness labelsReadiness pages remain hardening surfaces until a real launch state changes the facts.

Page Separation

Testnet and production pages should not blur into each other.

  • Testnet pages stay testnet. Core testnet observation remains separate from mainnet, production, token-sale, custody, and exchange pages.
  • Production pages need production evidence. A future mainnet page must point to mainnet chain id, mainnet genesis, mainnet validators, mainnet endpoint policy, and mainnet security posture.
  • Old testnet evidence remains historical. Testnet receipts can explain how the system was hardened, but they cannot replace mainnet evidence.
  • No label inheritance. Bridge, Infra, Liquid, and Core are separate economies; one surface becoming ready does not make every other surface production-ready.