Q token mark QUADPublic Accountability

Fast movement

Liquid

Liquid is the fast movement surface. It gives motion, wrappers, risk, and settlement labels a place to be inspected without turning speed into final truth.

Liquid moves quickly, then settles exactly.

Liquid Snapshot

Broad public labels first. Liquid-specific status belongs on the Liquid subdomain.

SurfaceLiquid
Current labelPublic Liquid endpoint checks passed; explicit-law, motion, route-proof, and export-view contracts are published; market activity closed
Public accessPublic summary, endpoint contract, motion data, route proof, explicit-law audit contract, and export-view contract
EngineOne-second motion engine smoke passed in default-safe mode on 2026-06-01
Endpoint checkPublic endpoint verification passed on 2026-06-11 with no checker blockers
Token roleMALI is motion and market utility: wrapper posture, execution pressure, fast-lane liquidity, and settlement-adjacent work
MainnetNot live

How To Read This Page

Liquid owns fast-movement evidence. Speed, wrappers, and engine output still have to hand off to settlement authority.

Purpose

Motion, position, wrapper, risk, clearing, liquidation, state-promotion, migration rehearsal, and settlement-request labels.

Posture

Pre-SDK state durability, promotion, migration rehearsal, explicit-law smoke evidence, route-proof sealing, endpoint verification, and one-second engine smoke evidence; public market activity remains closed.

Public stats

Use liquid.uquad.org for status JSON, motion JSON, endpoint contracts, proof, roles, readiness, explicit-law labels, route proof, and Liquid-specific state labels.

Not inherited

Liquid motion does not prove Core worth, reserve backing, Bridge admission, Infra truth, final balance truth, or live market access.

Liquid Experience Contract

Liquid should read like fast movement with brakes: quote, order, position, wrapper, liquidation, export, and settlement owner are separate labels.

Liquid’s public promise is fast, bounded motion: show the lane, the risk label, and the settlement owner before anyone treats movement as final.

Open the Liquid motion-label map
PathWhat Liquid should showWhat it must not imply
Quote screenPrice, fee, route, slippage limit, expiry, payment denom, settlement owner, and whether the quote is indicative, accepted, expired, or refused.A quote is not a trade, custody, market access, Core admission, redemption, or guaranteed settlement.
Order pathPending, accepted, filled, partially filled, expired, cancelled, refused, settled, and receipt-bound states.An accepted order is not final balance truth until the owning settlement surface records it.
Position viewCollateral label, debt label, exposure, wrapper status, risk band, liquidation threshold, margin posture, and settlement truth owner.Exposure is not reserve backing, wallet spend authority, admitted Core value, or claim eligibility.
Wrapper viewBacking class, representation class, redemption path, degraded backing, disabled redemption, and fallback status where applicable.A wrapper label is not native asset ownership unless the owning surface publishes that stronger state.
Liquidation pathTrigger, threshold breach, notice if any, execution, refusal, settlement, surplus, deficit, and receipt.Liquidation state is not yield, reward, punishment narrative, or discretionary confiscation.
Reward-like displayIf any reward-like, rebate, surplus, fee return, or settlement credit appears, it must show actual denom, actual amount, receipt id, and source.It must not force conversion assumptions, imply entitlement, or imply future rewards.
Export to InfraWhat was exported, who owns the later proof, what can be reconstructed, and which payload or receipt boundary remains private.An Infra export does not prove payload truth, Core worth, Bridge admission, or Liquid final balance by itself.
Settlement ownerWhich surface owns final balance truth, state root, receipt, refusal, and rollback or recovery path.Engine motion, quote speed, wrapper posture, or public attention cannot become settlement authority.

This is the main-domain reading contract. Liquid-specific status belongs on liquid.uquad.org; the main site keeps the meaning clean when fast-lane data is stale, closed, or still pre-SDK.

Q mark

What It Is

Liquid shows wrapper posture, lane status, local risk labels, state preparation, endpoint-contract exports, and motion meaning.

It stays separate from Core custody and private execution logic: movement can be fast, but settlement still has to be earned.

Why Use It

Use Liquid when fast movement needs clear lane labels, wrapper posture, settlement boundaries, risk state, and public proof that speed cannot outrun settlement truth.

How It Fits

Liquid is the stack's fast-lane surface. It can prepare motion, risk, wrapper, and settlement labels, but it does not get to turn speed into final truth.

Settlement remains the final balance owner. Bridge delivery and Infra imports stay contextual until Liquid accepts them under its own rules. Public market activity is not live.

Current Public Evidence

Liquid can show posture without opening a market.

Public evidence is state-preparation, refusal, bounded runtime evidence, and live public-surface verification today: durability, promotion, migration rehearsal, explicit-law smoke, endpoint checks, route proof, one-second motion engine smoke, runtime health, and boundary labels.

Stronger market claims still wait for consensus-backed stores, state roots, relayer funding, and owner-published market-opening evidence.

Open Liquid evidence detail
State preparation

Durability, promotion, and migration rehearsals are visible, but consensus stores and keeper authority remain gated.

Runtime shell

Market, ordering, risk, position, settlement, inventory, and clearing logic have local runtime surfaces without opening a market.

Endpoint verification

The Liquid public endpoint contract checker passed against liquid.uquad.org on 2026-06-11, including public-copy safety, endpoint, stats, motion-summary, route-index, route-proof, source-wait, and explicit-law checks.

Explicit law

Liquid-local admission, delay, quarantine, refusal, and audit labels are represented without claiming Core authority, Infra authority, settlement truth, or balance mutation.

Signed lifecycle smoke

Position open, funding, close, settlement acknowledgement, liquidation candidate, liquidate, and liquidation settlement have runtime smoke evidence.

Export view

Liquid can expose machine-facing and public-facing export roots from the same record while refusing settlement-truth, balance-mutation, and private-surface claims.

Comet/ABCI health

Pre-SDK service health, RPC stress, artifact checks, and stable refusal behavior are tracked with node_start_ready=false.

Engine boundary

The 2026-06-01 engine smoke passed default-safe build and lightweight runtime checks. Engine output is advisory proposal evidence only. Settlement, balances, admission, governance, payment approval, and final routing stay with the chain.

Settlement authority

Settlement owns final balance truth. Position, wrapper, clearing, reserve, Bridge, Infra, and Engine outputs must hand off.

MALI role

MALI belongs to motion and market utility. It is not Core value gravity, the vault, or final settlement truth by speed alone.

Launch blockers

Consensus stores, state roots, keeper-backed authority, relayer gas, runtime compatibility, market opening, and owner-published settlement evidence remain blockers.

What To Check

Liquid should become readable through simple lane labels before it ever asks for trust.

Check lane state, wrapper posture, risk labels, endpoint contracts, authority separation, and whether rehearsed migration is still clearly separate from applied consensus state.

Open Liquid checklist
Lane state

Whether fast movement surfaces are described, staged, testing, or live.

Wrapper posture

Whether wrapper labels are public and source-backed.

Risk label

Whether public risk state is plain without exposing private execution logic.

Endpoint contract

Whether public routes are reachable, checked, stale, static, or unavailable without claiming settlement truth.

Explicit law

Whether admission, delay, quarantine, refusal, and audit labels are visible without claiming Core authority, Infra authority, settlement truth, or balance mutation.

Engine boundary

Whether one-second tooling stays advisory until the authority rail validates, refuses, settles, audits, and exports.

Authority separation

Whether settlement, wrapper, position, Bridge intake, Infra import/export, reserve, and public views remain in their own authority lanes.

Launch honesty

Whether pre-SDK state stays labeled as pre-SDK until consensus-backed stores and state roots exist.

Migration honesty

Whether rehearsed migration plans stay separate from applied consensus state.

If Liquid Is Unavailable

The main site keeps Liquid's fast-lane boundary readable when the Liquid subdomain, endpoint contract, motion surface, or risk page is stale or offline.

Still shown

Liquid purpose, public scope, authority separation, risk boundary, endpoint-contract posture, explicit-law boundary, and staged/pre-SDK posture.

Downgraded

Current motion, position, settlement, wrapper, liquidation, endpoint, and export status.

Not inferred

Liquid outage does not imply Core admitted value, Bridge route failure, market closure, final balances, or live settlement truth.

Next check

Use Status, Verify, and the Liquid subdomain once it is reachable again.

Public scope

  • Shows public fast-lane status summaries.
  • Shows wrapper, pool, motion, cadence, priority, position, authority, and settlement labels when available.
  • Shows plain local risk labels.
  • Publishes endpoint, motion, route-proof, export-view, and explicit-law audit contract files as public verification surfaces.
  • Can describe one-second Engine smoke evidence without turning it into settlement truth, payment approval, market opening, or production throughput.
  • Can describe relayer gas floats and keeper-backed stores as launch blockers without opening market access.

Public boundary

  • Core custody.
  • Private market logic.
  • Private execution timing.
  • Operator-sensitive movement selection.
  • Final balances from Engine output alone.