Q token mark QUADPublic Accountability

Wallet and balance labels

Wallets Display Labels. Chains Own Meaning.

Use this page to read chain metadata, denom labels, balance classes, fee classes, and finality states without turning display text into custody, redemption, yield, or launch claims.

For quote states, actual charges, refunds, delays, and receipt closure, use Fees And Finality.

Metadata State

Wallet metadata is a display and connection aid. It does not create value, admission, reward eligibility, or user access by itself.

SurfacePublic metadata pathBoundary
Core / QUADcore.uquad.org/chain.json publishes Core chain ID, RPC/REST bases, address prefix, fee currency, staking currency, and explorer templates.Metadata is not sale access, liquidity, redemption, or proof of monetary value.
Infra / BIGHTinfra.uquad.org/chain.json and assetlist.json are the Infra-owned wallet/asset metadata paths where published.BIGHT is a work-payment label for Infra services, not reserve collateral or a reward claim.
Bridge / OBOLBridge currently publishes product, route, proof, inventory, ledger, and vault labels on bridge.uquad.org.Do not treat Bridge product labels as destination-chain wallet metadata, native-host custody, or open movement.
Liquid / MALILiquid currently publishes motion, risk, readiness, endpoint-contract, and status labels on liquid.uquad.org.Do not treat motion labels as final balance truth, Core worth, or live market access.

Denom And Wallet Labels

A denom tells the wallet what to display. The owning chain still decides admission, spendability, settlement, and refusal.

LabelRead asDo not read as
QUAD / uquadCore native accounting, gas, staking, and public chain-balance metadata where Core publishes it.Sale access, allocation, reserve claim, reward eligibility, or price support.
stQUADA staged wallet metadata label where explicitly published.Live liquid staking, yield, redemption, or entitlement.
BIGHTInfra work payment, service settlement, receipt memory, proof, upload, query, and retrieval context.Core admitted value, raw compute reward, node earning, or hard collateral by itself.
OBOLBridge passage, lane security, proof carriage, relayer work, receipt work, and border friction context.Destination admission, host-asset ownership, or Core Treasury value.
MALILiquid motion, wrapper utility, position/risk, and settlement-request context.Final balance truth, Core worth, brokerage, live leverage, or reserve backing.
IBC voucherA route-specific representation whose meaning depends on source chain, path, receiving chain, and local policy.Clean native asset admission, host custody, or automatic redemption.
Silver wrapperA representation label that may point toward host-asset evidence or fallback exposure.The same thing as gold/native vault ownership, spendable native host asset, or easy redemption.
Gold / native vaultHost-asset custody or control only when the owning vault/host evidence surface proves it.A wallet display shortcut, Bridge passage result, or automatic destination-chain admission.

Balance Classes

Balance pages should say what kind of balance is being shown. Same number, different law.

ClassPublic meaningNot implied
User balanceVisible address or account balance on the owning chain or product surface.Admission by another chain, redemption, or spendability outside its local rule set.
Module balanceState held by a module, route, contract, product lane, or chain-owned account.User withdrawal rights or discretionary spend authority.
Escrow / bondedValue held for a quote, route, order, work item, validator, provider, or pending condition.Final settlement, refund approval, or completed work.
Reserve / bufferA published reserve, ballast, host-fee, finality, slippage, or risk buffer label.Solvency, liquid backing, price floor, yield, or redemption access.
QuarantineUnresolved, unsafe, replayed, unsupported, or not-yet-admitted state.Clean admission, payment completion, or eligible user funds.
Payable / receivableExpected, owed, invoiced, or pending value tracked as an obligation.Cash on hand, available budget, or spendable balance.
Restricted / stagedValue or metadata visible under a staged, disabled, test, or not-yet-public label.Live access, production launch, allocation, or permission to act.

Module Balance Flags

When a balance belongs to a module, route, product lane, or holding surface, the flag matters as much as the number.

FlagPublic meaningNot implied
ReceivingThe owning surface has observed or accepted incoming state for classification.Admitted value, clean user balance, or destination acceptance.
StagingThe balance is parked while a quote, route, proof, receipt, finality, or policy check completes.Spend authority, completed settlement, or launch readiness.
QuarantineThe balance is blocked, unresolved, replay-protected, unsafe, unsupported, or waiting for stronger evidence.Eligible user funds, sale access, or redeemable value.
EscrowedThe balance is tied to an order, route, service, provider, validator, or quote condition.Finished work, refund approval, or discretionary spend.
ReservedThe balance is held as buffer, host fee, finality risk, ballast, service capacity, or safety margin.Solvency, yield, backing guarantee, or liquid market depth.
RestrictedThe balance is visible but constrained by route, policy, test state, disabled lane, or not-yet-public status.Transferability, redemption, market access, or user entitlement.
TerminalThe balance or record has reached burn, sink, refusal, closure, expiry, or final disposition where published.Marketing scarcity, yield event, or broader economic activation.

If a module balance lacks a flag, read it as incomplete display context and check the owning surface before acting on it.

For account-class and spendability boundaries, use the Custody And Account Map.

Fee Labels

  • Gas estimate: expected chain execution cost before signing.
  • Gas limit: maximum execution gas the transaction may consume.
  • Gas price: fee rate for the chain where the transaction is signed.
  • Host-chain gas: external chain execution or submission cost, where Bridge or another surface publishes it.
  • Relayer fee: route transport cost, not admission or custody.
  • Service fee: product work cost such as upload, retrieval, proof, reissue, passage, or motion.

State Labels

  • Pending: accepted for review or waiting for chain/product action.
  • Confirming: seen but not final enough for the owning rule.
  • Finalized: final only inside the surface that says so.
  • Failed: attempted and not accepted as successful.
  • Refused: blocked by rule; retrying should not be implied as useful.
  • Expired: quote, route, proof window, or action window ended.
  • Refunded: returned under the owning surface's refund rule; not broader admission.

Expected And Actual Denoms

Any claim, credit, payout, refund, reward-like display, or service receipt should show what was expected and what was actually received.

FieldWhat it should showBoundary
Expected denomThe denom the quote, route, claim, service, payout, refund, or credit path expected before execution.Not proof that the route completed or that the asset is locally admitted.
Expected amountThe amount before fees, slippage, finality changes, refusal, expiry, or route adjustment.Not a guarantee unless the owning surface says it is locked.
Actual denomThe denom actually credited, refunded, quarantined, routed, or recorded by the owning surface.Not automatically the same thing as the requested host asset or native vault asset.
Actual amountThe amount recorded after fees, refusals, expiry, partial fill, route output, or settlement logic.Not evidence of fair price, reserve backing, or yield.
Receipt idThe public id tying expected state, actual state, refusal, expiry, or refund to an owning surface.Not universal truth or another chain's admission.
Difference reasonFee, route-output class, refund, refusal, expiry, partial execution, quarantine, or finality status.Not private operator procedure or an invitation to retry blindly.

No public reward path is opened by this page. If a future product screen uses claim, credit, payout, or reward-like language, it must show expected denom, actual denom, receipt, and refusal/expiry state.

Safe Reading Rule

Wallet convenience must not outrank chain law.

Display is not authority

A wallet label helps recognition. It does not create admission, custody, spend rights, rewards, yield, or redemption.

Local law applies

Core, Infra, Bridge, and Liquid each own their own balances, fees, finality, and refusal states.

Wrappers stay named

IBC vouchers, silver wrappers, and native/gold vault assets must stay distinct so readers do not confuse exposure, route, and custody.

Unsupported means unsupported

If metadata, assetlists, balance routes, or proof routes are not public, say so instead of inventing wallet readiness.

Viewing this page does not require connecting Keplr, signing a transaction, entering a seed phrase, or making a payment.