Q token mark QUADPublic Accountability

One sitting overview

Stack Overview

QUAD is a multi-chain economic system for admitted value, verifiable work, controlled passage, and fast settlement. Four surfaces, four jobs: Core accounts, Infra proves, Bridge carries, Liquid moves.

Why use QUAD Evidence Updates External references

The Four Jobs

Each surface owns a different kind of public meaning.

Core protects admitted value

Core is the conservative accounting surface: chain state, fees, staking metadata, admission posture, quarantine, sink/terminal state, and public economic labels.

Infra proves useful work

Infra is the work and memory surface: BIGHT funding, upload, verify, retrieve, contract work, receipt memory, proof, balances, and retained evidence.

Bridge carries across boundaries

Bridge is the passage surface: acquisition, inventory, source pools, owner vaults, gates, host evidence, receipts, refusals, refunds, and movement-closed labels.

Liquid moves and settles

Liquid is the motion surface: positions, wrappers, risk, liquidation posture, settlement requests, explicit-law labels, and market-closed state.

Architecture In Plain Terms

The stack is coordinated, not merged. Evidence can cross surfaces; meaning stays local.

Core Bridge Liquid
Work Evidence Infra

Proof-First Path

Start with what can be checked, then move toward the more sensitive claims.

1. Observe CoreCheck chain state, validators, metadata, and Core-owned status. 2. Use InfraCheck BIGHT wallet paths, funding, upload, verify, retrieve, balances, ledger, and proof. 3. Read BridgeReview passage, source pools, owner vaults, inventory, gates, host evidence, proof, and closed movement labels. 4. Watch LiquidReview motion, positions, risk, settlement posture, and market-closed labels. 5. Check phasesRead current jobs, next gates, and what remains closed. 6. Check referencesRead outside-reference rules before treating a repo, listing, post, or crawler result as validation.

Current Public Posture

One compact status read. The owner surface still carries the current proof.

CoreObservable; mainnet hardening
InfraProduct proof and BIGHT work paths
BridgePassage evidence; movement closed
LiquidMotion posture; markets closed
EconomicsActivation path published; lanes gated
ReferencesOfficial surfaces first; outside acceptance scoped

What Counts Right Now

Use this split before turning a visible page, route, repo, or crawler answer into a stronger claim.

StateWhat it meansHow to read it
ObservableThe owner surface publishes live or static state that can be opened directly, such as Core chain status, metadata, validator views, docs, summaries, and evidence pages.You can cite the visible surface, but not infer sale access, entitlement, market activity, or future rights.
Product-activeThe owner surface presents a usable product path, such as Infra BIGHT funding, upload, verification, retrieval, balances, ledger, proof, and retained evidence.Use the product route as the receipt owner. Do not treat it as a promise that another chain accepts the same state.
Published boundaryThe owner surface explains the product, routes, gates, refusal states, reserve posture, or market posture while some movement remains deliberately closed.Closed means closed. The public page is a map and evidence surface, not permission to move value.
Staged or local evidenceSource folders, local release artifacts, manifests, and package checks can support readiness work before a public owner route carries the claim.Useful for build review. Not enough by itself for outside indexing, live-lane claims, or third-party validation.
External referenceA registry, explorer, wallet label, repo, article, or community post may point at QUAD after its own owner accepts and publishes it.Treat it as an outside reference only within the scope it actually published. Official owner surfaces remain the source of truth.

Use Cases By Surface

Useful paths stay attached to the surface that owns the receipt.

SurfaceUse casesPublic boundary
CoreEconomic state review, validator observation, fee/staking metadata, admission posture, quarantine and terminal state reading.Not a wallet, sale, airdrop, claim, price, or redemption page.
InfraReceipt memory, proof retrieval, contract storage, retained records, evidence bundles, challenge history, paid reissue, and public data lanes.Not raw compute rewards, node earning, or unrestricted public payload access.
BridgeAcquisition, reserve ledger, inventory truth, source pools, owner vaults, route gates, host evidence, proof, refunds, and passage records.Not destination admission, live IBC, wrapper minting, sell/redeem/swap access, or open movement by default.
LiquidMotion posture, position views, wrappers, risk labels, liquidation states, state-promotion rehearsal, and settlement-request records.Not live public markets, leverage access, final balance truth, or Core worth by speed alone.

Why Separation Matters

Most failure modes start when one surface borrows meaning from another.

Receipt is not universal truth

A receipt proves a bounded event under the owner surface. It does not force every other chain to accept the same meaning.

Transit is not admission

Bridge can carry evidence. Core or another receiver still decides local meaning under its own rules.

Motion is not worth

Liquid can move quickly. Final balance truth still belongs to the settlement owner and its published state.

Visibility is not launch

Public pages, status files, route labels, and crawler summaries help review. They do not open economics.

Roadmap By Evidence Gates

Progress moves when public proof can carry the claim.

Observe

Publish state, metadata, public pages, and safe first-read paths.

Harden

Run repeatable endpoint, product, failure, and release checks.

Explain

Publish purpose, category, model, risks, obligations, references, and boundaries.

Freeze

Freeze intended indexed genesis, metadata, endpoint posture, and route contracts.

Open narrowly

Open one bounded lane with owner-published status, fee, receipt, refusal, and recovery labels.

Expand on proof

Broader movement, liquidity, and market language wait for stronger receipts and dated owner updates.

Safety Boundaries

  • No seed phrase, private key, recovery phrase, or payment is needed to read the site.
  • No page creates sale access, allocation, reward eligibility, ownership, governance rights, or future entitlement.
  • No external listing, repo, wallet label, explorer, or assistant summary becomes authority by itself.
  • No public route should expose private payloads, credentials, operator procedure, or sensitive mechanics.

Community Path

  • Ask status questions: bring a public route, visible state, and expected next step.
  • Report bugs: include public ids and exact visible text, not private keys or private logs.
  • Review docs: use source, category, phase, reference, and risk pages before summarizing.
  • Coordinate carefully: community participation is coordination, not allocation or future privilege.