Q token mark QUADPublic Accountability

Progress by evidence, not vibes

Phases and Opening Gates

How QUAD moves forward: observe first, harden next, write down the rules, freeze them, then open narrow lanes only when the owning chain can back the claim.

No phase on this page opens a sale, reward, live movement, or market.

Where each part sits

A quick read, without turning one chain's progress into another's authority.

CoreHardening toward mainnet; observable now.
InfraLive product and BIGHT work paths.
BridgePassage evidence; movement still gated.
LiquidMotion and settlement staging; market closed.
WebsiteIdentity, routing, and release receipts.
Outside referencesStaged unless the outside source owns acceptance.

The order it moves through

Each step earns the next — nothing skips ahead.

1. Observe

Publish state, metadata, status labels, and safe first-read paths.

2. Harden

Prove endpoints, failure behaviour, and release artifacts under repeatable checks.

3. Explain

Publish purpose, model, risks, limits, and product boundaries in plain language.

4. Freeze

Lock the intended genesis, metadata, endpoints, and route contracts.

5. Open one lane

Open a single bounded lane with published status, fee, receipt, and recovery labels.

6. Expand on proof

Broader movement, liquidity, and markets need stronger receipts and dated updates.

Each chain's current job and next step

Where each one is, and what it has to do next.

ChainDoing nowNext step
CoreShowing chain state, validators, the token model, and economic hardening.Freeze genesis and endpoints, finish validator review, and close the public policy.
InfraMaking the BIGHT loop usable and provable — fund, upload, verify, retrieve, receipt.More receipts, cleaner failure states, provider accounting, and product polish.
BridgeShowing crossings, acquisition, inventory, vaults, gates, host evidence, and closed movement.Route-execution proof, refund/surplus posture, relayer closure — then narrower movement gates.
LiquidShowing motion, positions, risk, settlement requests, and market-closed labels.Settlement acknowledgement, risk controls, and fresh feeds before any opening language.
WebsiteKeeping the stack readable and linking the owner surfaces.Keep artifacts current, post dated updates, and visibly downgrade stale routes.

What you can do now

  • Watch Core: check current chain state on the Core surface.
  • Use Infra: follow the live BIGHT product paths.
  • Read Bridge: inspect passage, inventory, gates, and host evidence.
  • Watch Liquid: read motion and settlement posture — motion isn't a final balance.
  • Quote carefully: use the verify and boundary pages before summarising.

What stays closed

  • No distribution, sale, airdrop, or reward campaign.
  • No production Bridge movement lane from this page.
  • No live liquidity or market opened by phase wording.
  • No registry, explorer, wallet, repo, or summary becomes authority by itself.
  • No observation, coordination, or testing creates a future entitlement.