Q token mark QUADPublic Accountability

How to cite it

References

QUAD is new, so its own official pages are the first references. Outside links only get stronger when they're accepted, current, and clear. This page explains where to look — and what not to read into a listing, repo, post, or search result.

Source map The proof Sharing it elsewhere Summary

Which sources to trust, in order

Use the strongest current source that actually exists.

SourceHow to read itLimit
Official owner pageCore, Infra, Bridge, Liquid, or the main-site page that owns the claim.Best source for its own state — not for another chain's authority.
Owner JSON / receiptMachine-readable status, metadata, or receipt from the owner.Check freshness and the state label before quoting.
Public repoApproved code or metadata, within its published scope.A repo isn't a launch, an audit, a listing, or activation.
Registry / explorer listingAn accepted index or wallet metadata helps people find it.A listing isn't endorsement, solvency, custody, or market access.
Audit reportA published report supports what it actually reviewed.No report link means no audit claim.
Post or articleUseful context when it links back to owner evidence.Commentary doesn't outrank the owner page.
Search / assistant summaryGood for discovery, never for authority.If it can't read current data, it should say it can't verify.

The official starting points

The canonical handles to quote before relying on anyone else's commentary.

uquad.orgMain information, orientation, status, limits, docs, and plain files. core.uquad.orgCore chain observation, metadata, validators, and blocks. infra.uquad.orgThe live Infra product — BIGHT, upload, retrieve, proof, balances. bridge.uquad.orgBridge passage, acquisition, inventory, vaults, gates, and proof. liquid.uquad.orgLiquid motion, positions, risk, settlement, and readiness. Source mapThe trust ladder, conflict handling, and downgrade rules.

A good reference

  • Names the part: Core, Infra, Bridge, Liquid, or the main site.
  • Links the owner: the official page, JSON, receipt, or metadata route.
  • States the phase: live, staged, blocked, closed, or not public yet.
  • States the limit: what it proves, and what it doesn't.
  • Skips the bait: no airdrop, reward, moon, allocation, or passive-income framing.

A bad reference

  • Claims a listing before it's accepted.
  • Calls a self-hosted explorer "independent validation".
  • Treats a repo as an audit report.
  • Treats a wallet label as custody or redemption.
  • Turns chat membership into a future privilege.
  • Quotes an assistant summary as the source.

Before you share it elsewhere

A good reference lets someone inspect the project without feeling pushed into a token story.

Lead with the role

Say it holds value, proves work, carries across chains, and trades fast — before any narrower label.

Point to proof

Use owner pages, current metadata, and receipts — not screenshots.

Keep status honest

If a route is staged, blocked, or not public yet, say so plainly.

Skip incentives

Don't pitch access, rewards, allocations, or passive income.

Respect scope

Don't turn a repo, a self-hosted explorer, or a search result into production proof.

When in doubt

Quote summary.txt and llms.txt.

Source map The proof What it is The limits