QUADPublic Accountability
Claims move upward only when the public evidence exists. If live data cannot be read, the site should say so plainly.
Before acting on a claim, confirm the source, status label, owner, and safety boundary.
A receipt is useful because it is narrow. Read the owner, event, proof class, and boundary before treating it as evidence.
High-risk words only mean what the owning public evidence says they mean. A label is not a stronger claim by itself.
When in doubt, downgrade the claim to orientation and check the owning subdomain before quoting, buying, routing, validating, or building around it.
The main site should orient the reader and send live-state questions to the surface that owns them.
The main site points to public sources. Live chain data belongs on the Core observatory or the page that owns the feed.
Use these public paths to avoid guessing what a click, receipt, wallet label, or stale page means.
Open Core, check current status, then read metadata. If it is stale, treat this site as orientation only.
Open Infra, read the quote or product lane, then keep the receipt id. Refusal is a valid outcome.
Use Infra receipt or proof lookup. Reissue and reconstruction belong to the owning proof surface.
Check quote, source pool, vault, output class, host evidence, and refusal before treating passage as meaningful.
Read motion, wrapper, risk, and settlement labels separately. Speed does not create final balance truth.
Wallet display context is not admission, custody, reward, or entitlement.
Action-like links should be read with fee, finality, and refusal in mind before a visitor touches a subdomain.
Before using an action route, ask three questions: who owns the fee, who owns finality, and what happens if the route refuses?
Readable labels help people move carefully, but labels must not become false authority.
A receipt proves one bounded event from one owning surface. A wallet label helps display context. Neither one becomes universal authority.
For the full wallet, denom, balance, fee, and finality guide, use Wallet And Balance Labels.
If something looks wrong, the useful report is small, factual, and tied to the owning surface.
A good support report names the page, surface, action, public id, visible error, and expected next step. The dedicated Receipts And Support page gives the triage shape. Never include seed phrases, private keys, or private logs.
Copy the page or subdomain where the action happened: main site, Core, Infra, Bridge, or Liquid.
Name the action plainly: observe, upload, verify, route, settle, receipt lookup, wallet display, or status read.
Include the public receipt id, transaction id, quote id, route id, or error label when available. Do not share seed phrases or private keys.
Name wallet type, network label, denom label, and whether the issue is display, fee, signing, route, or receipt lookup.
Quote the visible public error or refusal label. Do not send private logs, keys, or operator routes.
Say whether you expected a status refresh, proof lookup, route acknowledgement, refund/refusal, or settlement label.
These labels are plain public status, not a private operations dashboard.
Use the short list first. Open the expanded list only when you need the exact feed.
Status labels, public feed source, static fallback data, chain links, and evidence states.
Private access details, validator keys, control logic, evaluation rules, and operator timing.
Post-reset checks should prove the intended indexed genesis, public metadata, endpoint posture, and indexer feeds before outside submissions are treated as ready.