Liquid Proof

Current proof ladder

Live consensus statusProves chain ID, block production, height, time, and sync posture at the moment read.Live node informationProves the served application identity and read-adapter status at the moment read.Current public stateDated owner summary of controlled venue, export, access policy, and remaining work.Market boundaryExplains what Liquid operates and why that does not open a public exchange.

Dated operational evidence

These statements were last proved through 2026-08-11 and should be reread before being used as fresh measurements.

SDK chain

The state-preserving SDK cutover retained the live liquid-1 chain and its public status route.

Controlled venue

Go multi-leg liquidity rounds landed with host acknowledgements on pools 3492 and 3493.

Recovery posture

An idempotent clearing watchdog replaced relayer restarts as the venue packet-strand response.

Infra history

Liquid venue snapshots were produced, pulled by Infra, and admitted through the external-chain interop receiver.

Wallet reads

The REST adapter provides bounded reads and simulation; transaction broadcast stays on the RPC path.

Fail-closed pricing

Layered fallbacks cover the current venue legs; missing required prices stop action rather than inventing value.

What this does not prove

It does not prove that public market access, deposits, listings, leverage, or rewards are available.
It does not turn pool depth into backing, redemption, guaranteed liquidity, or Core worth.
It does not make Infra an authority over Liquid settlement.
It does not make a sent interchain message successful until host acknowledgement and resulting state are checked.
It does not make a historical readiness packet current merely because the old route remains accessible.

Historical archive

Earlier rehearsal, route-binding, source-wait, protocol-USDC, endpoint-check, and wallet-read receipts remain under Data. They are now labelled historical rather than used as the homepage’s present tense.