Q token mark QUADPublic Accountability
QUAD Q token mark

Four surfaces. One public rule: proof before claims.

QUAD is the Quantitative Universal Amortisation Dollar: a Cosmos SDK economic-chain stack for admitted value, verifiable work, controlled passage, and fast settlement.

Start with the running Core chain. From there, follow the surface that owns the job: Infra prices BIGHT work, Bridge records boundary movement, Liquid labels fast motion, and private RPC sells CU access across its customer endpoint surface as a separate rail.

Observe Core Why Use QUAD Use Infra Read Bridge Observe Liquid Private RPC Public Surfaces Readiness Office Join Discord

Four Jobs

The stack is coordinated, not merged. Each surface has its own role, evidence, and public boundary.

QUAD is gravity. Infra is memory. Bridge is anywhere. Liquid is motion.

CoreProtects admitted value.

Chain observation, custody labels, supply posture, refusal, quarantine, quote intake, and economic law.

 InfraSells provable work.

BIGHT-priced storage, receipts, retrieval, contracts, retained memory, verification, Core-export receiver receipts, and provider evidence.

 BridgeCarries across boundaries.

Native acquisition, source pools, owner vaults, host-lane evidence, reserve ledgers, proof packets, host-gas receipts, route acknowledgements, and refusal labels.

 LiquidMoves and settles.

Fast motion, positions, wrappers, explicit law, risk, clearing, route proof, state promotion, and settlement-request evidence.

Pick The Door That Matches The Question

The website now routes by intent. A validator, tester, reviewer, and builder should not have to read the same wall of doctrine to find the right public surface.

New ReaderFirst-reading order, evidence labels, and surface ownership. UtilityWhy use each surface, what proof it owns, and what it refuses to claim. ObserverObserve the running Core chain and public chain metadata. Builder / IntegratorFind public routes for Infra, Bridge, Liquid, receipts, and status. ReviewerSee product gaps, technical closure, operating readiness, and accounting gaps. CommunityJoin coordination without seed phrases, payment, or reward framing.

Readiness Lenses

The product gaps are now being read through five practical lenses. They are public orientation, not private operating authority.

ProductCan the thing be honestly offered, tested, paid for, proved, and operated? TechnicalCan it run, interoperate, fail cleanly, rebuild, and expose state? OperatingWho owns it, what is stale, what costs money, and what blocks it? FinancialCan each chain close its books without merging authority? MarketCan outsiders understand it without hype or wrong incentives?

Open Executive Lens Map

Proof-First Landing Path

Use this route when quoting or reviewing the project. Each click has an owner, a proof class, and a boundary.

Observe Core Use Infra Read Bridge Observe Liquid Private RPC
Open the full proof-first route
  1. Observe CoreShows the running Core observatory, ledger, balances, readiness, and quote-first intake labels. It does not prove redemption, investment value, or automatic economic opening.
  2. Use InfraShows the BIGHT product path for wallet, buy, upload, verify, retrieve, contracts, receipts, proof, Core-export receiver state, and external-chain receiver state. Service receipts do not become Core admission or reward eligibility.
  3. Read BridgeShows Bridge-owned acquisition, source-pool inventory, per-asset ledger rows, owner-vault proof, host evidence, gates, proof packets, and route acknowledgement labels. Delivery remains separate from destination admission.
  4. Observe LiquidShows Liquid-owned motion, position, explicit-law, risk, readiness, route-proof, and settlement-request labels. Market movement remains closed until owner-published evidence changes the label.
  5. Use Private RPCShows an API-key-gated endpoint product with quote-first CU access, payment rails, wallet-linked credit, key-status, and fleet-status surfaces. One CU balance covers the customer RPC surface; it does not custody funds, settle chain state, admit value, or replace chain-owned truth.
  6. Open Surface DirectoryShows owner routes and fallback links. If a subdomain is stale, downgrade the claim and use the proof archive.
  7. Check ReadinessShows current gaps and next proof needed before stronger public claims. Does not certify launch or market access.
  8. Join DiscordRoutes public questions, issue reports, validator interest, docs feedback, and updates back to owner surfaces. Does not create allocation, rewards, private support, or authority over chain state.
What this proves

That the public site gives a visible review path with owner surfaces, proof classes, and current boundaries.

What this does not prove

It does not prove current height, balance, liquidity, market access, production value movement, or economic activation unless the owner route publishes that state.

If a route is stale

Use Proof Archive, Source Map, and Updates, then say the current state cannot be verified.

Use the Public Surface Safely

Viewing QUAD public surfaces does not require Keplr, a wallet connection, a signature, a seed phrase, or payment. Public coordination is for review, support, and orientation.

Public observation

Reading pages, joining coordination, or checking receipts does not create allocation, reward eligibility, ownership, investment status, or future entitlement.

Authority boundaries

Receipt, transit, liquidity, attention, and launch talk each need their own owner route before they become Core truth, admission, worth, or activation.

Category clarity

QUAD is an economic-chain stack, not a drone company, survey platform, AI training-data chain, DePIN rewards system, PoW mining chain, wallet app, or claim page.