Q token mark QUADPublic Accountability

Public status

Status Surface

A plain view of readiness, documentation state, owning-surface chain and product routes, audit summary condition, and current boundaries.

Current Public Posture

Status stays plain: what is published, what is live, what is staged or closed, and where owning-surface data belongs.

Observe CoreLive chain observation, validators, blocks, transactions, metadata, and Core public-law boundaries. Use BIGHTInfra product paths for quote-first purchase, paid upload, receipt verification, retrieval, balances, ledger, and proof labels. Read BridgeBridge product journey, source pools, per-asset ledger rows, owner vaults, gates, host evidence, proof, and lane-gated labels. Observe LiquidLiquid motion, explicit-law labels, route proof, settlement posture, risk labels, endpoint verification, state promotion, migration rehearsal, and public market closure. Surface directoryFull route map for pages, public files, endpoint contracts, and owning-surface evidence. Wallet labelsMetadata, denoms, balances, fees, finality states, wrappers, and vouchers. Readiness officeProduct, technical, operating, accounting, market, and current proof blockers.

Audit export: Public summary pending.

Opening Policy

Public status and production authority are separate. A stronger claim should only appear when the owning surface has public evidence for it.

If a route is staged, closed, or unavailable, the page should say that plainly instead of implying activity from adjacent work. Use the Status And Error Labels guide for refusal, stale, unpaid, expired, duplicate, invalid, unauthorized, and degraded states.

Status Policy

Public status reports condition and availability. It does not publish private controls, operator procedure, access details, or sensitive security mechanics.

If a public source is not ready, the site should say that plainly instead of filling the gap with a decorative number.

Operating Control Plane

This is the public triage view for the stack. It helps a reader see phase, evidence class, current blocker, next action, and claim boundary without opening every repo or subdomain.

SurfacePublic operating stateNext public action
CoreCore chain observation is public through the Core surface. The 2026-06-14 check reached status, RPC status, chain metadata, endpoint contract, intake lane, compatibility intake route, and homepage; receiver evidence remains quarantine-first, not Treasury admission or economic opening.Keep Core metadata, receipts, validator view, supply posture, and admission labels owner-published before stronger Core claims.
InfraInfra has canonical app, CometBFT, public intake, external export receiver, Bridge export adapter, relayers, BIGHT wallet support, quote-first purchase, paid upload, verify, retrieve, balances, ledger, receipts, provider payout posture, and proof labels where the owner route is open.Attach usage summaries, payable closure, and receipt counts only when Infra publishes them.
BridgeBridge publishes product journey, resident-node evidence, IBC transport proof, source-pool ledger rows, owner-vault allocation proof, host-evidence, proof, gate, Infra export wires, and route-gated labels.Keep self-serve or broader public movement lane-gated until Bridge-owned signer, quote, fee, finality, receiver, relayer, RPC reconciliation, and destination evidence justify a stronger label.
LiquidLiquid publishes motion posture, endpoint-checked contracts, explicit-law labels, route-proof state, risk/readiness labels, and market-closed state where available.Publish stronger position, settlement, venue, wrapper, and market labels only from Liquid-owned evidence.
Main websiteThe main domain owns orientation, status, docs, summary files, crawler guidance, release packaging, and public boundaries.Keep `launch-current/`, `launch.zip`, manifest, release receipt, sitemap, summary, and assistant guide aligned before upload.
External railsRegistries, explorers, wallets, hosts, forums, providers, and payment rails are useful only inside their published scope.Do not treat outside discovery, self-hosted visibility, or pending packets as endorsement, launch, custody, liquidity, or market access.
What this shows

Public phase posture, owner surface, evidence class, current blocker, next public check, and downgrade behavior.

What this withholds

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

What this cannot do

It cannot grant protocol authority, governance authority, production launch, financial reconciliation, custody authority, or economic activation.

Product State Labels

Use these labels consistently before treating a page, route, receipt, or product path as usable.

LabelMeaningDo not infer
LiveThe owning surface says the route is currently usable or observable in its stated environment.Mainnet launch, liquidity, custody, or admission beyond that surface.
Testnet / rehearsalTest tokens, staging, smoke proof, or rehearsal evidence exists for that lane.Monetary value, production value movement, rewards, or entitlement.
PlannedThe route, feature, or lane is described as intended work.Implementation, availability, launch date, or user action.
Disabled / closedThe route is intentionally unavailable, blocked, or not accepting public action.Failure, abandonment, or hidden availability.
StaleThe page or feed may lag the owning surface or current chain state.Current height, current balance, current transaction state, or current product availability.
Not-yet-publicEvidence may exist privately or locally, but the public surface is not ready to carry the claim.Public proof, user access, production readiness, or permission to quote as live.

When a label is unclear, downgrade the claim and check the owning subdomain before acting or quoting. For custody, reserve, liquidity, redemption, yield, solvency, destination admission, or launch language, use the financial and admission inference check.

Main Website Operating Posture

The public site is a shared stack surface. It must stay useful even when live feeds, subdomains, or source-folder evidence are moving at different speeds.

Static continuity

Homepage, start, status, docs, verify, boundary, site map, summary, assistant guide, and sitemap remain the static reader path.

Surface ownership

Live chain state belongs on the owning subdomain. The main site points to it and labels what it can safely claim.

Stale-state behavior

If a feed or subdomain lags, public copy should downgrade the claim instead of inventing a number, date, launch state, or proof.

Release discipline

Source pages and launch export must be kept in sync before any public upload. A passed static check is release hygiene, not production chain proof.

For degraded surfaces, release labels, rollback states, and public handoff rules, use the Continuity And Handoff guide.

Live Feed Behavior

When dynamic data cannot be read, the main site keeps orientation available and downgrades current-state claims.

The static telemetry contract is available at data/observability-contract.json. It defines metric owners, stale behavior, alert labels, and what must not be inferred from one metric.

Current sourceStatic fallback
FreshnessLive feed not yet checked
BoundaryStatic data cannot prove current chain state

If this page is using static fallback data, check the owning surface directly before quoting current height, transactions, admission state, liquidity, or launch status.

Core chain state Infra product state Bridge product state Liquid motion state RPC fleet state Observability JSON

Recent Public Developments

The short version of the current stack state. Use the readiness office for the deeper gap map.

Main website

The main domain now works as the orientation layer: identity, routing, status, readiness, and plain summaries.

Readiness lenses
Core

Core is live as chain id quad. The 2026-06-14 status check reached status, RPC status, chain metadata, endpoint contract, intake lane, compatibility intake route, and homepage routes with catching_up=false. Core wallet metadata now includes NTRN alongside QUAD, stQUAD, AKT, ATOM, STRD, TIA, OSMO, USDC, and INJ. Stronger admission, liquidity, and economic-opening claims stay closed until separately evidenced.

Core status
Infra

Infra is the clearest product route today: canonical app, CometBFT, public intake, Core-export receiver receipts, external-chain receiver receipts, quote-first BIGHT purchase, paid upload, verify, retrieve, balances, ledger, proof, onboarding, provider guidance, settled provider payout posture, and public snapshot routes. The 2026-06-14 public snapshot reports upload/query/download settled through the product surface.

Infra onboarding
Bridge

Bridge-1 is live with real-money posture and zero ungated public routes. Bridge publishes product journey, source-pool ledger rows for BTC, ETH, USDC, PAXG, and INJ, and quote-first PAXG, USDC, and ATOM into OBOL lane shapes. Payment remains gated by live quote, expected sender or memo binding, finality, receiver matching, and lane-specific relay readiness.

Bridge intake
Liquid

Liquid publishes endpoint-checked public contracts, motion posture, explicit-law labels, route-proof state, one-second engine smoke evidence, and launch blockers while market activity remains closed. The 2026-06-12 route check confirmed the Liquid public routes and restored live RPC/status paths at /status, /rpc/status, and /net_info.

Liquid status JSON
RPC

The private RPC rail is running chain nodes plus CU auth, key status, claim, fleet status, and payment feeder services with fresh payment-rail and CU payment data. The 2026-06-14 live check showed 14 monitored rows, 13 synced rows, dYdX back in sync, Axelar unsynced, BTC full-index status, and a CU payment feed with 4 observed payments, 2 matched payments, 2 unmatched payments, 1 credited customer, and 5,870 total CU credited. It remains quote-first endpoint access, not custody or chain authority.

RPC status JSON
Stack rule

The stack is coordinated, not merged. Meaning, payment, punishment, admission, and settlement stay local to the surface that owns them.

Readiness office
Shown

Public labels, surface links, audit-summary state, chain pointers, and release posture.

Omitted

Private controls, implementation paths, evaluation logic, access details, and operator procedure.

Later

Live exporters can appear on the surface that owns the data once the feed is safe to publish.