Q token mark QUADPublic Accountability

Public readiness

Readiness Office

A public map of what still needs proof. Use it to find the right surface, the current blocker, and the next evidence class without exposing private procedure or implying production launch.

How To Read This Page

Readiness is not one thing. A chain can have local proof while still missing accounting closure, operating controls, market clarity, or live packet evidence.

DescribedDoctrine or public copy exists.
Local proofCode, tests, manifests, or static exports prove shape.
Chain observedLive chain or staged-surface evidence exists.
Live receiptLive transaction, packet, payment, payout, or host receipt exists.
Public reconciledThe owning surface reconciles the fact.
BlockedMissing proof, funding, signer, route, public surface, or decision.

Use This Page To Decide Where To Look Next

The readiness office is the triage desk. The owning surface still carries the current proof.

CoreCheck chain state, metadata, validators, supply policy, and Core economic status.Best for liveness and custody posture. InfraCheck BIGHT wallet, funding, upload, verify, retrieve, balances, ledger, receipts, proof, and failure states.Best for usable product paths. BridgeCheck acquisition, inventory, source-pool, owner-vault, host-evidence, gates, proof, and movement-closed status.Best for passage evidence. LiquidCheck motion, positions, settlement posture, migration rehearsal, explicit-law labels, and market-closed status.Best for movement posture. ModelRead economics, validators, governance, security assumptions, rollout, token utility, and chain interaction.Best for the public system story. CategoryUse the plain category guide before treating QUAD as a familiar crypto bucket.Best for first explanations. PhasesRead current jobs, next gates, and what remains closed before quoting launch progress.Best for phase questions. State labelsCheck whether a route is live, testnet/rehearsal, planned, disabled, stale, or not-yet-public.Best before acting. VerifyUse the evidence ladder before treating a claim as live, staged, blocked, or closed.Best before quoting. RisksCheck which assumptions are open, reduced, monitored, blocked, or closed before relying on a claim.Best before depending on a route. Dependency mapCheck what a surface depends on and how stale dependencies downgrade public claims.Best before relying on siblings. Acceptance pathsCheck whether a journey has owner, action, cost, receipt, failure, and boundary evidence.Best before readiness claims. Proof archiveFollow evidence by owner, proof class, public route, boundary, and freshness.Best for progress checks.

What This Page Helps Answer

The readiness office is a public triage view. It should make the next proof obvious, not bury the reader in internal work.

Lens frameSee the checkpoint frame used to judge the stack without flattening chain boundaries. Risk registerSee the public assumption labels that keep readiness claims from outrunning evidence. Product gapWhat each chain still has to make offerable, testable, payable, provable, or operable. WorkstreamsTechnical, operating, accounting, and market work that still needs closure. PrioritiesThe cross-stack items that improve public readiness first.

Product Readiness

The product question is simple: can each surface be offered, tested, paid for, proved, and operated without shortcuts becoming law?

Core needs economic closure, Infra needs paid service closure, Bridge needs passage closure, and Liquid needs motion/settlement closure. Each chain has to prove its own part.

Open chain product gaps
Core

Needs final genesis economics, admission proof, value-adjustment evidence, supply surface, and live payment/relayer proof.

Infra

Needs live money-bearing surfaces, provider settlement, BIGHT payment access, service accounting, challenge economy, and capacity envelope.

Bridge

Needs production vault activation, live IBC, host-backed inventory truth, refund/surplus law, signer separation, and route-provider risk closure.

Liquid

Needs desk spine, position truth, risk and liquidation product, venue quality, wrapper backing behavior, and multi-epoch soak.

Workstreams To Close

These are the public buckets behind the readiness score. They stay readable here; the proof belongs on the owning surface.

Technical readiness
  • Product dependency DAG and versioned chain-to-chain interface contracts.
  • Cross-chain integration harness, failure-first test matrix, and refusal behavior.
  • Evidence-class enforcement in code, release checks, provenance, and observability.
Operating readiness
  • Stack control plane, launch dependency graph, and daily stale/blocked/unfunded status.
  • End-to-end acceptance journeys for Core, Infra, Bridge, Liquid, and support paths.
  • Support playbooks, incident handling, handoff, and continuity packet.
Financial accounting readiness
  • Per-chain books, authority maps, custody, payables, receivables, and reconciliation.
  • Infra revenue/provider accounting, Bridge inventory/refund accounting, and Liquid exposure accounting.
  • Stack-wide interchain obligations, seed provenance, runway, and non-authority reconciliation boundary.
Market readiness
  • One-line stack positioning, audience paths, and proof-first landing flow.
  • Product comparison, public proof archive, evidence timeline, and external references.
  • Discord onboarding without reward framing, category drift, or unsupported production claims.

Current Priority Stack

These are the cross-cutting work items that would improve the whole public surface first.

The next public-readiness wins are the dependency map, the proof archive, acceptance paths, the custody map, support playbooks, and the continuity and handoff guide.

Open priority stack
1. Product dependency map

Use the public dependency map to show what Core, Infra, Bridge, Liquid, relayers, RPC providers, indexers, wallets, and public sites depend on.

2. Proof archive

Use the public evidence timeline to separate source-folder progress, subdomain exports, proof classes, and stale/superseded states.

3. Acceptance journeys

Use the public acceptance paths for Core transaction, Infra upload/verify/retrieve, Bridge request/refund/refusal, Liquid position lifecycle, provider settlement, and support reissue standards.

4. Balance and custody maps

Use the public custody map to name what each chain owns, owes, records, refuses, pays, and cannot touch.

5. Support playbooks

Make common failures readable: stuck transactions, wrong denoms, funding refusal, stale packets, pending invoices, failed uploads, and delayed receipts.

6. Continuity and handoff

Use the continuity guide to show what survives, downgrades, rolls back, or hands off when a dependency is stale.

This page can show

Readiness gaps, proof classes, current blockers, next proof needed, and links to the owning surfaces.

This page withholds

Private controls, operator procedure, sensitive timing, credentials, provider internals, signer details, and sensitive mechanics.

This page does not open

Mainnet, value movement, live liquidity, sale access, reward eligibility, allocation, market access, or production activation.