Q token mark QUADPublic Accountability

Core economic surface

QUAD Core

Core is the constrained economic machine of QUAD: custody labels, refusal, routing law, validator state, payment posture, and the live Core chain observatory.

Core Snapshot

Broad public labels first. Detailed numbers stay on approved status or audit surfaces.

SurfaceQUAD Core
Current labelLive Core chain observation with route, receipt, and receiver hardening evidence
Public accessPublic observatory plus static indexer page
RegistryCore metadata published; third-party listing packets remain subject to endpoint and indexer review
Wallet metadataPublished at core.uquad.org/chain.json
Live check2026-06-14 status check reported chain id quad, moniker uquad, catching_up=false, endpoint contract updated 2026-06-14, and NTRN included in wallet metadata
Receiver evidenceBridgechain delivery index visible on Core; quarantine-only at last public check
MainnetCore chain is live; stronger economic-opening claims remain evidence-bound

How To Read This Page

Core owns admitted-value meaning. Other surfaces can send evidence, but they cannot make Core accept it.

Purpose

Custody discipline, admitted-value posture, refusal, quarantine, supply labels, and chain observation.

Posture

Live chain observation with receiver and route hardening evidence; stronger economic-opening labels wait for Core-owned proof.

Public stats

Use Core-owned pages for blocks, validators, metadata, receipts, and endpoint contracts. Main-domain stats are orientation only.

Not inherited

Infra receipts, Bridge transit, Liquid motion, website copy, listings, and crawler summaries do not become Core admission.

Core Public Promise

QUAD protects admitted value.

Core's public promise is admitted value, custody discipline, refusal, routing law, validator state, invoice/payment posture, and public economic observation.

Core is allowed to wait. If evidence, funding, routing, or classification is missing, the correct public posture is sleep, refuse, quarantine, or downgrade the claim.

Core Readiness Lens

Core is judged by whether it can explain custody, state, and refusal without leaning on sibling services.

Continuity

Core must keep blocks, validator state, metadata, and account posture readable even if another chain is unavailable.

Finance

Expected use, unpaid invoices, route volume, or sibling-chain activity do not become spendable Core money.

Technical

Readiness needs repeatable evidence: genesis/config posture, endpoint contracts, receiver rehearsal, and failure behavior.

Experience

The page should feel like a custody and state machine, with clear next checks and no reward inference.

Open the full Core lens map
ContinuityCore must keep local blocks, validators, staking, fees, module balances, and metadata observable even when sibling services are unavailable.Downgrade proof claims instead of borrowing another chain's availability. OperationsCore status should show current phase, blockers, stale dependencies, and next proof without becoming protocol law.Operations observes and escalates; it does not admit value. FinanceCore must not treat issuance, expected use, sibling services, route volume, unpaid invoices, or unrealized returns as spendable money.Spendable status needs chain-local account class and receipts. MarketCore should be explained as a custody and admitted-value surface, not a generic DeFi venue, sale, airdrop, wrapper, or yield product.Public language follows proof. TechnicalCore readiness needs repeatable proof: genesis/config posture, public metadata, endpoint contracts, receiver rehearsal, and failure behavior.Architecture is not readiness. InformationCore public truth needs owned source paths for metadata, status, law map, launch labels, and stale-state behavior.No critical truth should live only in private memory. DataCore exports, public indexer feeds, account freshness, failures, and status summaries need owner, evidence class, and redaction boundaries.Exports are evidence, not hidden policy authority. ExperienceCore should feel like a constrained economic machine: custody/truth state, quarantine, refusal, invoice/payment labels, and public next steps.Convenience cannot smooth Core law.

Core Experience Contract

Core should make state readable before anyone treats a label as money, governance, movement, or authority.

Core should answer one question first: what state is visible, and who is allowed to treat it as meaningful? The detailed label map is available for reviewers without dominating the page.

Open the Core state-label map
PathWhat Core should showWhat it must not imply
Public value postureAdmitted, pending, quarantined, routed, settled, terminal, and stale labels where Core publishes them.Available spend, price, solvency, reserve backing, market depth, or launch readiness.
Treasury stateCustody/truth posture, accounting class, receipt link, and whether state is admitted, staged, quarantined, or terminal.Treasury funds are not a public wallet, router, sale pool, or discretionary spend account.
Invoice intakeReceived, admitted, routed, paid, duplicate, refused, delayed, and receipt-closed states.Unpaid invoices, expected use, or sibling-chain activity are not spendable Core money.
External Affairs railShared website/support payment posture where explicitly approved and receipt-backed.Alloc does not become the owner of money just because a public-support rail exists.
Claim or credit pathExpected denom, expected amount, actual denom, actual amount, receipt id, and difference reason.No reward path, yield path, allocation, or entitlement is open unless Core publishes that lane.
Quarantine pathWhat is held, why public action is blocked, what evidence can clear it, and what terminal state can close it.Quarantine is not hidden spend, eligible user funds, or soft admission.
Governance slotsGenesis law, machine-first posture, published parameters, proposal state, and any later on-chain or published process.Governance does not become a private override of live Core law.
Failed actionSleep, refuse, hold, quarantine, expired, duplicate, or stale-state labels with a public next check.Failure text should not encourage retries that cannot pass the same gate.
Health/postureCurrent chain health belongs on Core-owned status, block, validator, metadata, and endpoint pages.A stale main-domain page does not prove current height, current balance, admission, or activation.

This is the main-domain reading contract. Current numeric state belongs on Core-owned public surfaces such as core.uquad.org, not repeated as decorative numbers here.

What It Is

Core is the vault and law surface of QUAD. It holds, accounts, constrains, refuses, quarantines, sinks, and reports. It is not a trading desk and it is not a general action layer.

Public Core data should explain admitted value, supply condition, and whether the chain is healthy enough to keep presenting itself normally.

Standalone Mode

Core must keep its public promise even when the rest of the stack is late, unavailable, refusing, or unfunded.

The short rule: Core can keep observing, refusing, and accounting even when adjacent services are unavailable. It should downgrade dependent claims instead of borrowing certainty.

Open standalone failure cases
If Infra is unavailable

Core should keep local audit/export records and downgrade proof-memory claims until Infra can admit the relevant work.

If Bridge is unavailable

Core should not claim native-vault or destination-admission availability. It can keep local observation and refuse or quarantine uncertain imports.

If Liquid is unavailable

Core should not imply fast-lane settlement, market utility, or worth from motion. Core value meaning stays local.

If the public site is stale

Core state is read from Core-owned public surfaces and last-known public evidence, not from stale summaries.

If relayers or providers are unfunded

Core should downgrade movement and payment claims rather than pretend the route can complete.

Always

Treasury remains custody/accounting state, not convenience routing. Uncertain imports are admitted only after local verification; otherwise they are refused or quarantined.

Core Law Map

The short version: Core observes, classifies, accounts, refuses, quarantines, or acts.

Core is allowed to stop. Refusal, quarantine, sleep, and no-op behavior are normal outcomes when evidence or authority is missing.

Open Core law map
Truth order

Oracle observes signals, Market frames economic inputs, Treasury accounts for custody, Economics applies chain-local law, and Actions performs approved effects.

Audit observes

Audit records and exports public summaries. It does not command Treasury, mint supply, admit value, or override Core law.

Treasury accounts

Treasury is custody and value accounting. It is not a router, exchange, reserve-asset wrapper, or public price promise.

Alloc hands off

Alloc owns value branch and handoff posture, so movement has an accountable lane instead of becoming ambient authority.

Worth gates can stop

A gate can sleep, refuse, or do nothing when evidence is missing. Refusal is a normal safety outcome, not a site failure.

Quarantine and sink

Unresolved state belongs in quarantine. Terminal disposal belongs in sink or burn labels when safe to summarize.

Supply is bounded

Minting is bounded by public policy, safety posture, epoch allowance, and a hard-cap failsafe. Public observation balances do not imply redemption, allocation, or price support.

Public reading

Arrival is not admission, transit is not value, liquidity is not worth, and public attention is not protocol authority.

How It Fits

Core gives the project a stable accounting center. It lets public pages separate described, implemented, observed, live, closed, and stronger-proof-needed claims.

Registry and explorer packets remain review artifacts until the outside indexer accepts the current endpoint set and metadata.

The static indexer page exists so wallets, explorers, assistants, and cautious readers can classify the chain without needing JavaScript.

Bridgechain Receiver Evidence

Public receiver posture for Bridge-origin value. This is quarantine-first evidence, not unrestricted public movement.

Bridge-origin value lands as a quarantined fact first. Core still decides admission, classification, custody, or refusal under Core law.

At the 2026-06-01 public check, Core's delivery index exposed two Bridgechain delivery receipts: one quarantined, one blocked, and both marked quarantine-only. That is useful receiver evidence, not Treasury admission, sale access, liquidity, or production value movement.

View Core Receipts Delivery Index JSON
Open receiver detail
First landing

Bridgechain-origin value lands through QUAD x/bridge and then Quarantine. It does not land first in Treasury, Alloc, Mint, Foundation, CoreImport, or an ordinary account.

Delivery is not admission

A Bridge delivery may create a quarantined fact only. Core still decides admission, classification, custody, yield status, or refusal under Core law.

Receipt posture

The receiver records local delivery receipts and refuses replay before value moves. Public evidence may show ids, hashes, denom, amount, status, and timing.

Current public feed

Core publishes /index/bridgechain-deliveries.json and the receipts page for receiver evidence. The feed is quarantine-first and must not be read as Treasury, Alloc, Mint, Foundation, or CoreImport admission.

Current route boundary

Receiver evidence remains route-scoped until transport, packet submission, quarantine proof, post-classification behavior, and operating funding are captured for the route being claimed.

Market Route And Receiver Evidence

Core can show route law and receiver proof without turning route evidence into open market access.

Route support, asset admission, and Bridge transport are separate claims. Core can prove a rehearsal without opening liquidity or destination admission.

Open route and receiver detail
Route policy

Market routes now require an owner, purpose, reason tag, cap, slippage bound, Alloc requirement, and receipt requirement before execution can be treated as policy-covered.

Admission is not venue support

Asset admission and route support are separate. A whitelisted asset can still report hold, no-route, quarantine, or sleep if the venue route is not supported.

Bridge envelopes

Bridge execution envelopes require reason and provenance, keeping source module, source kind, and native-target law visible before movement is described.

Transport evidence

The Core and Bridge transport path has produced packet-clearing evidence, but transport still does not decide Core value meaning.

Receiver quarantine

A Core-facing Bridge delivery moved voucher value into quarantine and required a Core receipt before Bridge acknowledgement. Quarantine remained the first safe landing.

Still closed

Open liquidity, automatic public IBC movement, host execution, and destination admission stay closed until the owning surface publishes evidence for that lane.

Public Metadata And Listing Posture

Useful for validators and reviewers; stronger outside-indexing labels stay tied to endpoint evidence.

Core publishes wallet metadata, static classification, endpoint contracts, and genesis access as public review material. Funding, topology, route evidence, and outside-indexer acceptance remain separate gates.

Chain metadata Static index Endpoint contract Genesis Readiness
Open metadata and launch-candidate detail
Wallet metadata

core.uquad.org/chain.json publishes the current Core chain ID, RPC/REST bases, address prefixes, fee currency, staking currency, and explorer templates.

Registry packet

Chain Registry-style metadata and asset metadata are review material. Outside acceptance depends on the current endpoint set, current genesis, and the reviewer/indexer's rules.

Live hardening

The current Core surface is live and evidence-bound. It is not a sale, reward program, redemption path, or unbounded public value opening.

Static indexer

/static-index is a plain HTML classification page for wallets, explorers, assistants, and cautious readers.

Public indexer direction

CoreExport, account freshness, health, metrics, summary, and public failure classes are the safe data shapes for later deployed checks.

Release manifest

Core release material tracks rebuild, focused tests, clean-home block production, indexer validation, claim sweep, and endpoint checks before stronger outside references are requested.

Production topology

Topology material keeps validator and peer counts, separate homes and service users, keyless observation, monitoring, and temporary-role wind-down as explicit hardening gates.

Relayer gas floats

Core has approved relayer-gas domains, but each remains launch-blocking until funding and evidence exist. Relayers are operational gas support only, not custody, counterparty, or payment authority.

Native acquisition acks

Native-acquisition acknowledgements carry status and destination-surface rules. Submitted, sourced, refunded, quarantined, failed, and finalized states cannot bypass Core admission law.

Financial Boundary

Core accounting should be visible without turning every balance or future expectation into spendable money.

Balances and invoices are accounting facts first. They only become spendable, admitted, or activated when Core-owned evidence says so.

Open financial boundary table
ClassPublic meaningNot implied
Custody stateCore can show custody/truth posture where publishable.Not available spend, yield, sale access, or market liquidity.
Admitted asset registerAssets need local admission, classification, and evidence before they become Core-recognized state.Arrival, receipt, route, or wrapper label is not admission.
External affairs railCore may carry the shared website support rail as an explicit public-surface exception.Not a general subsidy for other chains' nodes, providers, relayers, or operating budgets.
Receivables and invoicesUnpaid invoices and expected service income can be tracked as obligations or expectations.Not cash, reserve value, launch readiness, or spendable budget.
Issuance and supply labelsSupply posture can be published as accounting state.Not reserve backing, price support, or economic activation.

Core Token Model

Public token model only. This is not a sale, allocation schedule, price model, or promise of future value.

Public nameQUAD
Minimal denomuquad
Decimals6
Address prefixquad
Current networkquad
PhaseLive Core metadata and chain observation; no sale, reward, or redemption claim
Accounting unit

QUAD is the native Core unit used to express public economic state on the QUAD chain. It is how Core labels supply, fees, staking metadata, and public chain balances.

Fee and staking denom

On the observable Core chain, uquad is published as the fee currency and staking currency in wallet metadata. That makes it usable for funded transaction paths, not a claim of monetary value, reward eligibility, redemption, or allocation.

Admission discipline

Outside assets do not become clean Core value just because they arrive. Core's public model is about whether value is admitted, pending, quarantined, routed, or settled.

Quarantine boundary

Unsupported, unresolved, or unsafe movement belongs behind quarantine labels until it can be classified. Quarantine is a safety boundary, not a yield or reward surface.

Sink and terminal state

Terminal disposition belongs in public summaries when safe to show. A burn, sink, or terminal label is state accounting, not marketing scarcity.

stQUAD label

stQUAD may appear in Core wallet metadata as a public label. It should not be read as a liquid-staking product, yield promise, redemption path, or entitlement.

Reserve assets may matter inside the broader system, but QUAD should not be summarized as a Bitcoin wrapper, vault token, lending product, or a product that sells exposure to any asset. The public model is the rule system around admission, custody, routing, quarantine, and settlement. Open the roadmap or open the economic activation path.

What To Check

Core pages should answer public accountability questions without publishing private mechanics.

For a fast pass, check status, metadata, balances, receipts, and whether every stronger claim has a Core-owned evidence route.

Open Core accountability checklist
Status label

Whether Core is described, implemented, observed, staged, or live.

Audit summary

Whether public accounting summaries are available.

Boundary

Whether the page avoids wallet, sale, reward, or mainnet claims.

Core law

Whether truth order, audit observation, custody, refusal, quarantine, sink, and bounded supply posture are described without private controls.

Transport evidence

Whether transport lanes are labeled by route and boundary, not treated as Core admission or module money movement.

Registry posture

Whether public metadata stays review-scoped until outside indexers accept the current genesis and endpoint posture.

Core Reader Journey

A visitor should be able to verify Core without guessing, connecting a wallet just to browse, or inferring rewards from coordination activity.

1. ObserveOpen the Core chain observatory for public chain state. 2. Check metadataReview chain ID, denom, prefix, RPC/REST bases, and explorer templates. 3. Read Core pathUnderstand admitted-value accounting, validators, supply policy, hardening gates, and closed claims. 4. Read token modelUnderstand QUAD/uquad as current public metadata, not sale or entitlement. 5. Check opening lanesRead what remains closed before minting, distribution, movement, liquidity, or markets open. 6. Check continuitySee what Core must still prove when sibling services are stale, offline, or refusing. 7. Verify claimsUse evidence labels before quoting Core as live, closed, staged, or blocked.

If Core Is Unavailable

The main site keeps the public map readable when the Core subdomain, live feed, or chain observatory cannot be reached.

Still shown

Static Core purpose, boundary, law map, public metadata links, status policy, and verification routes.

Downgraded

Live observation, audit freshness, chain telemetry, receiver rehearsal state, and any claim that depends on a current Core endpoint.

Not inferred

Core outage does not imply mainnet launch, custody failure, Treasury movement, value admission, or economic activation.

Next check

Use Status, Verify, and the Core subdomain once it is reachable again.

Core modules

Public names only. This page explains responsibilities without publishing internal operating details.

The module names are public orientation labels. Private operating detail stays out of the main domain.

Open public module labels
Oracle

Observes inputs that other layers may consider under Core law.

Market

Frames public economic inputs without becoming settlement truth.

Treasury

Accounts for custody and publishes approved public summaries.

Economics

Applies chain-local rule posture before action is allowed.

Actions

Performs approved effects after the required Core law checks.

Alloc

Handles value branch and handoff posture through one accountable layer.

Mint

Reports bounded supply state.

Quarantine

Contains unresolved or unsafe state until it is classified.

Sink

Shows terminal disposition summaries.

Audit

Publishes plain-language status and summaries.

Public boundary

  • Private controls.
  • Operator-sensitive mechanics.
  • Internal implementation detail.
  • Transport details that would imply asset admission before classification, timeout, audit, and quarantine checks are complete.
  • Operational detail beyond public status.

Launch shape

Core stays simple in public: publish only the labels and summaries needed for public accountability.

Live numbers belong on the approved status or audit surface, not repeated across every page.

Current listing posture: metadata is published by Core, while official third-party listing depends on the receiving indexer and its endpoint checks.