Q token mark QUADPublic Accountability

Proof handles, not hype handles

Public References

QUAD is new, so the official surfaces are the first references. External links become stronger only when they are accepted, current, and explicit. This page explains where to look and what not to infer from a listing, repo, post, crawler result, or explorer.

External Reference Path Source Map Credibility Summary

Reference Ladder

Use the strongest current source that actually exists.

Reference classHow to read itBoundary
Official owner surfaceCore, Infra, Bridge, Liquid, or the main website page that owns the claim.Best public source for its own state, but not for sibling authority.
Owner JSON or receiptMachine-readable status, metadata, receipt, endpoint contract, or public data from the owner.Read freshness, evidence class, and state label before quoting.
Public repoApproved repository material can explain code, metadata, packets, or contracts.A repo is not launch, audit, listing, liquidity, or production activation.
Registry or explorer listingAccepted third-party index or wallet/explorer metadata can help discovery.A listing is not endorsement, solvency, custody, admission, or market access.
Audit reportA published report can support the scope it actually reviewed.No report link means no public external audit claim.
Forum, article, or postUseful for context only when it points back to owner evidence.Commentary does not outrank the owner surface.
Search or assistant summaryUseful for discovery, never for authority.If it cannot read current owner data, it should say it cannot verify.

Official Starting Points

These are the canonical handles to quote before relying on outside commentary.

uquad.orgMain public information, orientation, status, boundaries, docs, and static release files. core.uquad.orgCore chain observation, metadata, validators, blocks, and Core-owned state. infra.uquad.orgInfra BIGHT paths, work receipts, upload, retrieval, proof, balances, and product state. bridge.uquad.orgBridge passage, acquisition, inventory, vault lanes, gates, host evidence, and proof state. liquid.uquad.orgLiquid motion, positions, risk, settlement posture, endpoint contracts, and readiness state. Source mapTruth ladder, owner surfaces, conflict handling, and downgrade rules. External reference pathHow to share, list, post, or submit QUAD without token-promo framing or false validation.

Reference Status Slots

Slots stay plain until the reference exists. Empty slots should not be dressed up as momentum.

AssetCurrent public postureWhat it would prove
Public repositoriesUse only approved public material where published.Code or metadata visibility within the published scope.
Chain registry packetStaged until the intended indexed genesis and metadata are ready.Submission or acceptance status only when the registry owns that status.
Explorer / indexer referenceHelpful when stable, but self-hosted references stay self-hosted references.Discoverability and block/state reading, not independent endorsement.
Wallet metadataRead as display and routing metadata.Denom, prefix, chain id, and endpoint handles where current.
Audit reportsNo public external report should be claimed until a report exists.The reviewed scope, date, findings, and exclusions.
Technical postsUseful when they link back to owner evidence and avoid reward framing.Context and discoverability, not authority.
Community referencesCoordination only unless a page explicitly publishes a stronger status.Support path, feedback path, and current public instructions.

Good Outside Reference Shape

  • Names the surface: Core, Infra, Bridge, Liquid, or main website.
  • Links to the owner: official page, JSON, receipt, or metadata route.
  • States the phase: live, staged, blocked, closed, monitored, or not yet public.
  • States the boundary: what the reference proves and what it does not prove.
  • Avoids bait: no airdrop, reward, moon, allocation, or passive-income framing.

Bad Reference Shape

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

Before Sharing QUAD Elsewhere

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

Lead with role

Say admitted value, verifiable work, controlled passage, and fast settlement before using narrower labels.

Point to proof

Use owner pages, current metadata, public receipts, and the source map rather than screenshots.

Keep status bounded

If a route is staged, blocked, self-hosted, or not yet public, say that plainly.

Skip incentives

Do not pitch access, rewards, allocations, passive income, or future privilege.

Respect scope

Do not turn local evidence, a repo, a self-hosted explorer, or a crawler result into production proof.

Use the site summary

When in doubt, quote summary.txt and llms.txt.