Q markQUADCore Observatory

Readiness

This page separates live Core observation, operational readiness, and stronger economic claims. Public status moves by dated evidence, not hype dates or implied promises.

Current statusTransaction lookupSupply policyAdmissionEconomic activationIntake lane

Current public update

Published 2026-06-12. The no-cache live check reached Core status, RPC status, chain metadata, endpoint-contract, and homepage routes.

What is live

The public Core observatory exposes status, blocks, ledger transactions, balances, validators, wallet metadata, intake-lane path, delegation metadata, and RPC boundary pages. The 2026-06-12 status check reported chain id quad, moniker uquad, and catching_up=false.

What remains bounded

Governance remains bounded. External audit reports are not published from this surface. Stronger economic claims require their own public evidence.

What to inspect

Use public addresses, transaction lookup, intake-lane state, wallet metadata, and optional delegation. Do not treat site activity as reward eligibility, allocation, or future privilege.

Core hardening page

This is the public hardening surface for Core. It records what can be observed now, what still needs evidence, and which claims remain refused until stronger proof exists.

Evidence before stronger claims

Public liveness, endpoint stability, wallet metadata, intake-lane refusal behavior, staking path, receipt visibility, and module balances must stay coherent over time.

Route provenance, governance posture, relayer floats, and export readiness are watched as separate evidence.

Still watched

Validator independence, audited high-risk boundaries, production relayer funding, external provider readiness, and freeze economics remain bounded until their own evidence is published.

Refused claims

Hardening is not a sale, reward program, allocation, independent audit, exchange listing, price guarantee, liquidity guarantee, or guarantee that all future gates will pass.

Update rule

Material changes should be dated and attached to a public reason, not silently rewritten into a stronger claim.

Doctrine hardening now visible

The public page does not expose private thresholds, but the readiness posture now names the Core invariants that must keep holding over time.

Truth order

Oracle, Market, Treasury, Economics, and Actions must stay in order. Audit remains observer/export surface only.

Custody boundaries

Treasury stays passive custody and NAV; Alloc owns routing; Quarantine contains unresolved value; Sink handles terminal disposal.

Worthiness gates

Mint, seller, restaker, burn, fee, and route surfaces should be able to sleep or refuse when truth, NAV, safety, timing, or supply gates are not met.

Supply safety

Minting remains bounded by NAV, safety state, epoch allowance, the 10% per-epoch ceiling, and the 21B hard-cap protective failsafe.

Burn and supply data are proof surfaces, not redemption, buyback, or guaranteed price-support claims.

Core operation watch

This run is public enough to inspect directly, while long-range freeze judgment stays evidence-bound until time has exercised the edges.

Already visible

Blocks, transaction lookup, intake-lane state, module balances, fee burn routing, validator state, and public wallet metadata are visible from the observatory.

Economic surfaces

Mint, quarantine staging, seller pressure, restaker flow, invoice handling, and export receipts are watched as behavior over time, not marketed as guarantees.

Decision rule

A freeze candidate can become a freeze only after the run stays coherent across cadences, not because one block, tx, or page looks healthy.

Detailed runtime feedsLive posture panels for governance, relayer funding, provider journey, flagged routes, and degrade state.

Public claim posture

Claims from adjacent chains and providers downgrade automatically when the indexed evidence is missing, stale, harness-only, or not locally admitted by Core.

Loading claim posture...

Governance posture

Governance visibility is bounded by machine law. Voting state does not become discretionary control, Treasury authority, or a bypass around module gates.

Governance statusAwaiting endpoint refresh
MaturityAwaiting endpoint refresh
ReasonAwaiting endpoint refresh
ClassesAwaiting endpoint refresh
Feed updatedAwaiting endpoint refresh
Loading governance posture...

Relayer gas float

Relayer floats are launch blockers until real wallets, balances, packet or transaction receipts, and reimbursement receipts exist. They do not grant custody or market authority.

StatusAwaiting endpoint refresh
DomainsAwaiting endpoint refresh
FundedAwaiting endpoint refresh
BlockedAwaiting endpoint refresh
Feed updatedAwaiting endpoint refresh
Loading relayer gas-float posture...

Relayer gas ledger

The ledger records public wallet, balance, packet or transaction, and reimbursement evidence when it exists. Empty rows mean funding has not been proven yet.

StatusAwaiting endpoint refresh
EntriesAwaiting endpoint refresh
Funded domainsAwaiting endpoint refresh
Missing domainsAwaiting endpoint refresh
ReimbursementsAwaiting endpoint refresh
Feed updatedAwaiting endpoint refresh
Loading relayer gas ledger...

Relayer packet backlog

This is packet-lifecycle observation from QUAD's Bridge surface. Active ICA/provider lane health is separated from stale transfer residue, and harness lanes remain labeled as harness evidence.

StatusAwaiting endpoint refresh
PendingAwaiting endpoint refresh
Expired pendingAwaiting endpoint refresh
TimeoutAwaiting endpoint refresh
FailedAwaiting endpoint refresh
ICA controllerAwaiting endpoint refresh
Feed updatedAwaiting endpoint refresh
Loading relayer packet backlog...

Provider journey

Registration, packet action, claim floor, yield admission, and distributor visibility are shown as separate stages. This does not promise rewards or promote harness providers to production lanes.

StatusAwaiting endpoint refresh
ProvidersAwaiting endpoint refresh
Routed yieldAwaiting endpoint refresh
Waiting pathAwaiting endpoint refresh
Pending packetsAwaiting endpoint refresh
Reward denomsAwaiting endpoint refresh
Feed updatedAwaiting endpoint refresh
Loading provider journey...

Reward-output manifest

Provider source denoms and user reward output denoms stay visible as separate facts. Distributor preview is not a reward promise.

StatusAwaiting endpoint refresh
Provider rowsAwaiting endpoint refresh
Routed admissionsAwaiting endpoint refresh
Reward denomsAwaiting endpoint refresh
Claimable denomsAwaiting endpoint refresh
Feed updatedAwaiting endpoint refresh
Loading reward-output manifest...

Alloc flagged routes

Alloc route staging is visible separately from Treasury NAV and user balances. A pending flagged route can be a correct sleep state when worthiness, dust, receiver state, or cadence says no.

StatusAwaiting endpoint refresh
RoutesAwaiting endpoint refresh
Below floorAwaiting endpoint refresh
RefusedAwaiting endpoint refresh
RetryingAwaiting endpoint refresh
Feed updatedAwaiting endpoint refresh
Loading Alloc flagged routes...

Foundation can-pay gates

Foundation payment readiness is measured from Foundation-held settlement budget and External Affairs instructions only. Treasury NAV is reserve backing, not an invoice wallet.

StatusAwaiting endpoint refresh
Settlement balanceAwaiting endpoint refresh
Pending instructionsAwaiting endpoint refresh
Pending amountAwaiting endpoint refresh
GatesAwaiting endpoint refresh
Feed updatedAwaiting endpoint refresh
Loading Foundation can-pay gates...

Financial posture label

Public financial figures are observations from Core state. They are not mainnet value, realized income, payment guarantees, redemption rights, or spendable cash.

LabelAwaiting endpoint refresh
StatusAwaiting endpoint refresh
RefusalsAwaiting endpoint refresh
ExceptionsAwaiting endpoint refresh
Admitted NAVAwaiting endpoint refresh
Infra liabilityAwaiting endpoint refresh
Feed updatedAwaiting endpoint refresh
Loading financial posture...

Emergency and degrade path

Public state, recovery owner, and update owner are visible without exposing private mitigations, keys, operator internals, or bypass authority.

StatusAwaiting endpoint refresh
SurfacesAwaiting endpoint refresh
Degraded/refusingAwaiting endpoint refresh
Blocked/waitingAwaiting endpoint refresh
Update ownerAwaiting endpoint refresh
Feed updatedAwaiting endpoint refresh
Loading emergency and degrade path...

Evidence review criteria

Core public claims should strengthen only after the public checks below are satisfied or deliberately superseded by a dated update.

  • Observable liveness. Blocks, status, index freshness, and transaction visibility remain stable through the public observatory.
  • Participation path complete. Wallet setup, intake-lane path, transaction lookup, optional delegation, 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, static index, LLM guide, and Core labels agree on QUAD identity, public status, and refused claims.
  • Doctrine boundaries hold in public. Treasury custody, Alloc routing, Quarantine containment, Sink terminal disposal, Audit observation, and mint supply limits remain distinguishable in the public explanation.
  • Stale wording cleared. Public pages do not claim mainnet, rewards, external endorsements, independent validators, or live governance unless visible and approved.

Stronger public claim criteria

Stronger public claims should be published only when these gates are credible and source-backed.

Chain readiness

Genesis, validator posture, public endpoints, transaction path, and observability are ready for public inspection and evidence review.

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 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, intake lane, ledger, RPC boundary, wallet metadata, validators, or another public surface.

User impact

What a visitor may see: delayed indexing, failed broadcast, stale status, paused intake lane, or unavailable endpoint.

Current state

Investigating, mitigated, monitoring, resolved, or waiting for the next public update.

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 Core communication.

  • No pay-to-play access. Intake-lane access never requires real-money payment.
  • Participation boundary. Intake-lane use, Discord membership, node operation, code review, and transaction activity can support testing and review without creating reward eligibility, allocation, ownership, governance rights, leverage, or future entitlement.
  • No status inflation. Public observation is evidence, not proof of independent audit, exchange listing, production safety, or public value guarantee.
  • 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.
  • No raw safety claims. Bridge, Vault, and other high-sensitivity surfaces should not be called safe without public evidence appropriate to the claim.
  • No adjacent-surface upgrade. Bridge, Infra, Liquid, wallet metadata, explorer listings, or third-party summaries do not make Core mainnet live, production-safe, admitted, or value-bearing.