Q token mark QUADPublic Accountability

First read

Start Here

Start with the running Core chain, then follow the surface that owns your question: Core for admitted value, Infra for work proof, Bridge for passage evidence, and Liquid for fast movement.

The One-Minute Map

Read the system by ownership. Do not merge the surfaces just because they link to each other.

Core / QUAD

Economic custody, refusal, quarantine, supply posture, validator state, and public chain observation.

Infra

Verifiable storage, receipts, retained memory, proof labels, contract work, BIGHT-priced service lanes, and provider settlement evidence.

Bridge

Native acquisition intent, passage, route evidence, vault labels, host evidence, refusal, and delivery receipts.

Liquid

Fast movement, positions, wrappers, risk labels, clearing, liquidation posture, and settlement-request visibility.

First Five Clicks

This path gives a cold reader enough context before the denser pages.

1. Observe CoreSee the running chain, chain id, validators, blocks, transactions, and metadata. 2. Why Use QUADSee the useful reason for Core, Infra, Bridge, and Liquid before reading deeper docs. 3. Read Stack OverviewGet the four-chain role map, proof-first path, current posture, and safety boundaries in one sitting. 4. Read ArchitectureSee how the four surfaces coordinate without becoming one module. 5. Verify ClaimsSeparate described, observed, staged, live, closed, and refused states. 6. Choose JourneyFind the allowed action, fee, finality, receipt, refusal, and next public check. 7. Read BoundarySee why receipts, transit, liquidity, listings, and attention do not inherit authority.

Surface First Reads

Pick the surface that owns the question. Each path starts broad, then moves to the live or product-specific page.

QUAD / CoreStart with admitted value, custody discipline, chain observation, token model, and receiver quarantine. InfraStart with BIGHT-funded work, upload, receipt verification, retrieval, balances, ledger, and proof labels. BridgeStart with controlled passage, acquisition, inventory truth, owner vaults, host evidence, provider risk, receipts, and destination-admission boundaries. LiquidStart with fast movement, positions, wrappers, risk, liquidation, venue quality, settlement truth, and market-closed posture. Stack overviewStart with the one-sitting map of how the four surfaces work together and what each one refuses to inherit. Whole stackStart with how Core, Infra, Bridge, and Liquid coordinate without merging authority.

For current state, continue from the main overview to the owning subdomain. The main page explains the role; the subdomain owns live or staged evidence.

What The Main Site Owns

The main domain is the orientation surface. It explains the map, then points readers to the chain surface that owns the evidence.

Open main-site ownership
Identity

Names the project, wrong categories, wallet safety boundary, and public interpretation rules.

Routing

Points readers to Core, Infra, Bridge, Liquid, status, docs, summaries, and the owning subdomain for live or staged evidence.

Readiness language

Labels whether claims are described, observed, staged, live, blocked, closed, stale, or publishable.

Static fallback

Keeps summary.txt, llms.txt, site map, and sitemap.xml readable when dynamic surfaces lag.

What To Look For

Ask what public evidence backs the claim, which surface owns it, and what the evidence does not prove.

Open evidence reading order
Status label

What phase does the page claim: observation, staged, local, live, blocked, or closed?

Owner surface

Which chain or website owns the state being shown?

Receipt or feed

Is there a transaction, receipt, JSON feed, endpoint contract, or public status record?

Boundary

What does this evidence not prove?

Next gate

What still has to be proven before the claim can move up a phase?

Pick Your Reader Path

Different readers need different entry points. The safest path is the one that matches what you are trying to verify.

New visitorPlain identity, current posture, and what QUAD is trying to be.Start here when the name is all you know. TesterFunding, status, metadata, receipt, and product paths.Use public addresses only. ValidatorRead chain-local validator, liveness, endpoint, degraded-state, slash-risk, and readiness labels.Validator review is not allocation or future privilege. ProviderStart from Infra work, receipt, proof, contract, balance, and service-closure paths.Provider work needs owner-published receipts. BuilderUse public contracts, schemas, source ranking, stale-state handling, and must-not-build warnings.Preserve owner, proof, phase, and boundary labels. ReviewerEconomic model, governance posture, security assumptions, rollout, and chain interaction.Public model only. Security reviewerAudit slots, disclosure boundaries, withheld mechanics, and report-state labels.No private procedure or exploit detail. Route readerProduct journey, acquisition, source pool, owner vault, route, gate, host evidence, proof, and refusal labels.Bridge is passage, not admission. Liquidity readerRead Liquid motion, risk, wrapper, settlement-request, and market-closed labels.Motion is not Core worth or final settlement. Community memberUse Discord for status questions, docs feedback, and public coordination.No seed phrases, payments, or entitlement claims. Crawler / indexerUse summary, assistant guide, sitemap, source map, proof archive, and owner routes.Say cannot verify instead of inventing current state.

Boundary Checks

These are the mistakes this site is built to prevent.

A receipt is not universal truth

Infra and Bridge receipts prove bounded handling. They do not force Core meaning.

Transit is not admission

Bridge can carry evidence to a receiver; the receiver still decides local meaning under its own rules.

Motion is not worth

Liquid speed, wrappers, markets, and positions do not create Core value by themselves.

Public status is not a sale

Viewing pages, using public chain surfaces, joining community channels, or running tests does not create allocation, rewards, ownership, or future entitlement.

Surface Subdomains

Open the surface that owns the live or staged evidence you need.

core.uquad.orgCore chain observatory, blocks, ledger, validators, receipts, balances, and metadata. core-path.htmlAdmitted-value, monetary-accounting, validator, supply, activation, and mainnet-hardening path. category.htmlPlain category guide for admitted value, verifiable work, controlled passage, and fast settlement. references.htmlOfficial surfaces, outside-reference boundaries, repo slots, listing posture, and audit-report slots. credibility.htmlProof handles, owner surfaces, evidence classes, pending assets, and claim limits. phases.htmlPhase order, opening gates, current jobs, and closed-state boundaries. infra.uquad.orgInfra storage product, BIGHT purchase, upload, verify, retrieve, contracts, proof, and receipts. infra-path.htmlStore, prove, retrieve, remember: the main-domain Infra product path and public/private payload boundary. wallets.htmlWallet metadata, denom labels, balance classes, fees, wrappers, vouchers, and finality states. fees.htmlQuotes, expected and actual charges, gas, service fees, host costs, refunds, delays, and receipt closure. lifecycle.htmlRequest, quote, payment/signature, execution, waiting, receipt, refusal, refund, quarantine, and closure. obligations.htmlOperating costs, payer labels, payables, receivables, floats, and self-funding boundaries. risks.htmlOpen assumptions, risk labels, closing evidence, downgrade behavior, and owner boundaries. bridge.uquad.orgBridge product journey, acquisition, pools, vaults, ledger, gates, host evidence, proof, and public data. bridge-path.htmlControlled passage, native acquisition, inventory truth, owner vaults, provider risk, and proof receipts. liquid.uquad.orgLiquid motion, position, settlement, risk, state promotion, migration rehearsal, proof, readiness, and roles. liquid-path.htmlFast movement with settlement discipline: desk, position, wrapper, risk, liquidation, venue, and settlement boundaries.