Q token mark QUADPublic Accountability

Network evidence

Network Use

A plain view of usable public paths, what counts as product evidence, what still needs receipts or owner-published summaries, and what should not be treated as traction yet.

Use Infra Observe Core Data Provenance Proof Archive

Current Evidence

Some product paths are visible. Stronger usage or adoption claims still need owning-surface receipts, named disclosures, or public summaries from the surface that owns the data.

Core observationCore state, metadata, validators, blocks, and chain labels belong on core.uquad.org.
Infra product surfaceBIGHT purchase, upload, verify, retrieval, balances, and ledger paths belong on infra.uquad.org.
Infra work usageUsage totals need Infra-owned receipts or public summaries before they should be quoted.
Receipt evidenceOwned by the route that issued the receipt and bounded by its proof class.
Bridge passageBridge product pages can show passage posture, inventory, proof, gates, host evidence, and closed movement labels.
Liquid movementLiquid motion labels belong to Liquid and do not prove Core worth, final settlement, or live market access.
Provider countNot publicly reported
Public partnersNot yet announced
Public tractionNot yet published as partner or volume claims

What You Can Use Now

These are public paths a reader can inspect or start from without treating review activity as adoption, reward eligibility, or investment demand.

Observe CoreConfirm liveness, public state, validators, and metadata. Read CategoryUnderstand what the stack is before treating use, proof, or traffic as a familiar crypto category. Read ReferencesCheck which outside references are official, pending, accepted, self-hosted, or not yet published. Use InfraUse BIGHT wallet, funding, upload, verify, retrieve, balances, and ledger paths where the owner route is open. Read BridgeReview pools, vaults, reserve posture, gates, proof, and refusal labels. Check LiquidReview motion, settlement, risk, readiness, and public state labels. Read docsChoose the reader, validator, reviewer, builder, operator, or product-user path. CoordinateUse Discord onboarding for chain coordination, support prompts, reports, and docs feedback.

What Counts As Usage Evidence

Usage should be counted by owner-published records, not by enthusiasm, screenshots, or copied summaries.

Evidence classWhat it can supportWhat it cannot support
Owner receiptA bounded action happened on the issuing surface: upload, retrieval, quote, proof, refusal, passage, or settlement request.Payload truth, sibling-chain admission, market access, reward eligibility, or final value.
Owner summaryPublished counts, public totals, or status summaries from the surface that owns the data.Partner adoption, revenue, solvency, liquidity, or external validation unless explicitly published.
Current public routeA product path is reachable and carries the owner's current label.That every path is open, paid, production-ready, or economically activated.
Accepted outside referenceDiscovery or indexing inside the outside owner's stated scope.Endorsement, audit completion, launch status, custody, or market access.
Community reportA lead for support or docs improvement when it includes a public route or id.Adoption, partner disclosure, validator privilege, allocation, or authority over chain state.

Product Paths

The main domain points to product paths. The subdomain owns the action and the receipt.

Upload workSubmit bounded storage work where the route is open and receive a receipt. Verify receiptCheck a public receipt without exposing private payloads. BalancesRead visible wallet, reserve, work-credit, and balance posture. Bridge inventoryReview held-asset and request-linked value labels without treating movement as open.
More product feeds
BIGHT walletOpen public wallet and address labels for Infra. Liquid motionRead motion labels as local evidence, not final worth.

What Counts Later

  • Infra: usage summaries, receipt counts, funding state, and service-volume labels from Infra-owned public routes.
  • Bridge: route counts, host evidence, gate labels, inventory summaries, and refund/refusal totals from Bridge-owned routes.
  • Liquid: motion, position, risk, settlement-request, and venue-quality summaries from Liquid-owned routes.
  • Providers: count labels only when the owning surface intentionally publishes them.
  • Partners: named only after an approved public disclosure.

What Does Not Count

  • Public attention by itself.
  • Referral or prize activity as a substitute for product use.
  • Rumored partnerships.
  • Unverified screenshots or copied claims.
  • Private messages, rumors, or third-party summaries without public surface links.
  • Discord membership, bug reports, validator interest, or docs feedback by itself.
No public disclosure

No partner, pilot, or stack-wide adoption claim has been announced on this page.

Pilot announced

Reserved slot for a public, approved pilot disclosure.

Published usage evidence

Reserved slot for public usage evidence after the owning surface publishes enough receipts or feed data to support it.

Read Data Provenance Proof Archive Source Map Discord Onboarding References