Q token mark QUADPublic Accountability

Known before claimed

Risks And Assumptions

This page names the main public assumptions behind Core, Infra, Bridge, Liquid, the website, and outside rails. A risk is not a failure by itself. It is a claim that still needs owner-published evidence, a downgraded label, or a closed state.

If an assumption is not proven by the owning surface, the public claim should shrink until it is.

Risk Labels

Use these labels before treating a page, route, receipt, or feed as stronger than the evidence supports.

LabelPublic meaningWhat should happen
OpenThe assumption is known and has not been publicly closed by the owner surface.Keep the claim narrow and point to the next proof needed.
ReducedEvidence lowers the risk, but the public route still depends on a condition, provider, phase, or receipt.Show the evidence and keep the remaining assumption visible.
MonitoredThe route is usable or observable, but freshness, uptime, cost, or dependency state can change.Keep timestamps, owner, and downgrade behavior visible.
BlockedThe route, claim, or phase cannot advance until a missing proof, funding path, provider, validator, or decision exists.Refuse, pause, or downgrade instead of implying availability.
ClosedThe owner surface has published enough evidence for the specific claim being made.Quote the owner and do not expand the closure beyond that claim.

Assumption Classes

Most bad public claims start when one assumption quietly borrows another surface's authority.

Owner

Which chain or public surface is allowed to say the state is true?

Freshness

When was the state last updated, and what happens when it goes stale?

Funding

Who pays for the route, provider, gas, proof work, refund, or continuity lane?

Endpoint

Is the public route live, staged, stale, disabled, or only an orientation link?

Counterparty

Does a host chain, relayer, registry, provider, wallet, or indexer need to accept something?

Meaning

Does the evidence prove only observation, or does it also prove admission, custody, settlement, or closure?

Stack Register

Each row names the public risk, the current safe reading, and what would reduce it.

SurfaceRisk to watchClosing evidence
CoreChain observation can be mistaken for economic opening, admission, liquidity, or production value movement.Core-owned pages, receipts, policy labels, validator state, and explicit opening evidence.
InfraBIGHT work lanes, receipt memory, upload, retrieval, proof, and contracts can be mistaken for raw compute rewards or generic data rewards.Infra-owned quotes, receipts, balances, service states, failure labels, and contract closure records.
BridgePassage records, host evidence, inventory, and vault labels can be mistaken for destination admission, redemption, or open movement.Bridge-owned route state, gate state, host evidence, refusal/refund state, and terminal receipt records.
LiquidMotion, position, wrapper, and market-adjacent labels can be mistaken for final settlement truth.Liquid-owned settlement request state, risk labels, wrapper boundaries, and settlement-owner acknowledgement.
Main websiteOrientation pages can be mistaken for the owner of chain state.Links to owner surfaces, stale labels, release receipts, source ranking, and static summary files.
External railsWallets, registries, indexers, RPC providers, and hosts can lag, cache, refuse, or display incomplete state.Owner route, timestamp, metadata version, current endpoint response, and downgrade rule.
FundingExpected use, route volume, issuance, receivables, or sibling services can be mistaken for spendable money.Owner-published payable, receivable, float, receipt, refund, and budget labels.
SupportSupport text can accidentally strengthen a claim, expose private material, or promise an outcome.Public ids, owner surface, current visible state, exact refusal/delay label, and receipt closure.

Evidence That Reduces Risk

  • Owner-published state: the owning chain or subdomain names the state directly.
  • Fresh timestamp: the route says when the evidence was generated or checked.
  • Receipt id: a stable public id links event, owner, proof class, and closure.
  • State label: live, staged, disabled, stale, blocked, reduced, closed, or monitored.
  • Failure label: refusal, timeout, expired quote, unpaid state, quarantine, refund, or terminal state.
  • Artifact receipt: release hash, manifest, public file list, and rendered smoke check where appropriate.

Evidence That Does Not Close Risk

  • Search result: crawler visibility is not owner-published state.
  • Wallet display: a label or balance display is not spend authority by itself.
  • Route volume: activity is not profit, reserve, solvency, or self-funding.
  • Static fallback: cached state helps orientation but cannot prove current liveness.
  • Adjacent chain progress: one chain cannot upgrade another chain's claim.
  • Local evidence: source-folder proof is useful, but public claims must say whether it is deployed.

If An Assumption Fails

The safe response is a smaller claim, not a louder promise.

Refuse

Reject the action when owner, funding, signer, endpoint, denom, quote, or proof state is invalid.

Pause

Stop accepting new work when the route, provider, relayer, host lane, or funding path is unavailable.

Downgrade

Keep orientation available while lowering live, production, continuity, or current-state claims.

Quarantine

Hold uncertain value, route output, proof result, or counterparty state until the owner can classify it.

Refund

Return accepted value only under the owner surface's published refund and receipt rule.

Terminalize

Close an item as expired, refused, written off, stale, unrecoverable, or completed with a public label.

What This Page Does Not Do

A public risk register makes review easier. It does not open closed systems.

No stronger launch claim

This page does not open production value movement, liquidity, redemption, sale access, or allocation.

No private operating detail

This page does not publish credentials, signer handling, provider accounts, private logs, or non-public implementation detail.

No inherited authority

Core, Infra, Bridge, Liquid, the website, wallets, registries, and crawlers do not inherit each other's proof.