Liquid Snapshot
Broad public labels first. Liquid-specific status belongs on the Liquid subdomain.
QUADPublic Accountability
Broad public labels first. Liquid-specific status belongs on the Liquid subdomain.
Liquid owns fast-movement evidence. Speed, wrappers, and engine output still have to hand off to settlement authority.
Motion, position, wrapper, risk, clearing, liquidation, state-promotion, migration rehearsal, and settlement-request labels.
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.
Use liquid.uquad.org for status JSON, motion JSON, endpoint contracts, proof, roles, readiness, explicit-law labels, route proof, and Liquid-specific state labels.
Liquid motion does not prove Core worth, reserve backing, Bridge admission, Infra truth, final balance truth, or live market access.
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.
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.
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.
Use Liquid when fast movement needs clear lane labels, wrapper posture, settlement boundaries, risk state, and public proof that speed cannot outrun settlement truth.
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.
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.
Durability, promotion, and migration rehearsals are visible, but consensus stores and keeper authority remain gated.
Market, ordering, risk, position, settlement, inventory, and clearing logic have local runtime surfaces without opening a market.
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.
Liquid-local admission, delay, quarantine, refusal, and audit labels are represented without claiming Core authority, Infra authority, settlement truth, or balance mutation.
Position open, funding, close, settlement acknowledgement, liquidation candidate, liquidate, and liquidation settlement have runtime smoke evidence.
Liquid can expose machine-facing and public-facing export roots from the same record while refusing settlement-truth, balance-mutation, and private-surface claims.
Pre-SDK service health, RPC stress, artifact checks, and stable refusal behavior are tracked with node_start_ready=false.
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 owns final balance truth. Position, wrapper, clearing, reserve, Bridge, Infra, and Engine outputs must hand off.
MALI belongs to motion and market utility. It is not Core value gravity, the vault, or final settlement truth by speed alone.
Consensus stores, state roots, keeper-backed authority, relayer gas, runtime compatibility, market opening, and owner-published settlement evidence remain blockers.
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.
Whether fast movement surfaces are described, staged, testing, or live.
Whether wrapper labels are public and source-backed.
Whether public risk state is plain without exposing private execution logic.
Whether public routes are reachable, checked, stale, static, or unavailable without claiming settlement truth.
Whether admission, delay, quarantine, refusal, and audit labels are visible without claiming Core authority, Infra authority, settlement truth, or balance mutation.
Whether one-second tooling stays advisory until the authority rail validates, refuses, settles, audits, and exports.
Whether settlement, wrapper, position, Bridge intake, Infra import/export, reserve, and public views remain in their own authority lanes.
Whether pre-SDK state stays labeled as pre-SDK until consensus-backed stores and state roots exist.
Whether rehearsed migration plans stay separate from applied consensus state.
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.
Liquid purpose, public scope, authority separation, risk boundary, endpoint-contract posture, explicit-law boundary, and staged/pre-SDK posture.
Current motion, position, settlement, wrapper, liquidation, endpoint, and export status.
Liquid outage does not imply Core admitted value, Bridge route failure, market closure, final balances, or live settlement truth.