Q token markQUADTestnet Observatory

Readiness

This page separates testnet observation from mainnet claims. QUAD testnet can be live while mainnet remains pending; the transition depends on public criteria, not a hype date.

Current statusLedger indexTester path

Current public update

Published 2026-05-04. Next public update is due no later than 2026-06-04, or sooner after a material testnet change.

What is live

The public testnet observatory exposes status, blocks, ledger transactions, balances, validators, wallet metadata, faucet path, and RPC boundary pages.

What is pending

Mainnet is not live. Governance and staking views are not exposed on this observatory yet. External audit reports are not published from this surface.

What to test

Use public addresses, test tokens, transaction lookup, and issue reports. Do not treat testnet activity as value, reward eligibility, allocation, or future privilege.

Testnet end criteria

Testnet ends only after the public checks below are satisfied or deliberately superseded by a published update.

  • Observable liveness. Blocks, status, index freshness, and transaction visibility remain stable through the public observatory.
  • Tester path complete. Wallet setup, faucet/test-token path, transaction lookup, known-issues guidance, and support routing are usable without asking for wallet secrets or payment.
  • Security posture stated. High-sensitivity surfaces are labeled, public incident wording exists, and no audit or safety claim is implied before evidence exists.
  • Public terminology aligned. Main site docs, glossary, and testnet labels agree on QUAD identity, testnet status, and what is not live.
  • Stale wording cleared. Public pages do not claim mainnet, rewards, external endorsements, independent validators, or live governance unless visible and approved.

Mainnet start criteria

A target date should be published only when these gates are credible. Until then, mainnet status is pending.

Chain readiness

Genesis, validator posture, public endpoints, transaction path, and observability are ready for public value custody decisions.

Security readiness

Bridge, Vault, and other high-sensitivity surfaces have public posture labels and reviewed evidence appropriate to their risk.

Operations readiness

Known issues, incident updates, deployment checks, and rollback/recovery communication are prepared in public-safe language.

Incident summary format

Public incident updates should explain impact without exposing exploit paths, private mitigations, keys, validator internals, or defensive timing.

Affected surface

Status, faucet, ledger, RPC boundary, wallet metadata, validators, or another public surface.

User impact

What a tester may see: delayed indexing, failed broadcast, stale status, paused faucet, or unavailable endpoint.

Current state

Investigating, mitigated, monitoring, resolved, or waiting for next testnet window.

Next update

Give an exact date or time window when another public update will be posted.

Yellow flags this site rejects

These are public-affairs guardrails for testnet communication.

  • No pay-to-play testnet access. Testnet funds are test tokens only and never require real-money payment.
  • No reward promises. Faucet use, Discord membership, node operation, code review, or transaction testing does not create reward eligibility, allocation, ownership, governance rights, leverage, or future entitlement.
  • No mainnet claims during testnet. A running testnet is evidence of public observation, not evidence that mainnet or public value custody is live.
  • No silent date slips. If a public target date is later published and changes, the reason should be dated and visible.
  • No hype-only updates. Progress updates should be technical, specific, and public-safe.
  • No raw safety claims. Bridge, Vault, and other high-sensitivity surfaces should not be called safe without public evidence appropriate to the claim.