Live chain
The browser reads these fields directly from /status and public node information.
Networkliquid-1
HeightLoading
SyncLoading
Latest blockLoading
RuntimeLoading
Public marketClosed
Current capability posture
Observed and verified through 2026-08-11.
SDK chain live
liquid-1 is the live chain identity. “main_net” is the application version label, not a promise of public market access.
Venue live
Protocol-operated liquidity and execution are active on Osmosis pools 3492 and 3493 through a keyless interchain account.
Infra export live
Liquid produces typed records; Infra pulls and admits them through interop. Full venue pool snapshots are paced hourly.
Wallet reading live
The bespoke REST adapter exposes bounded reads and simulation. It does not broadcast transactions or mutate balances.
Degraded and closed states
Healthy chain transport does not erase product or engineering limits.
- Public market access is closed. There is no public deposit, swap, listing, leverage, or liquidity guarantee.
- Venue execution may correctly decline. Price, depth, inventory, cost, acknowledgement, or freshness gates can refuse a round.
- Pool snapshots have no volume fields. Infra can archive holdings and weights; trading-volume claims need a different source.
- Historical receipts are not current authority. June rehearsal and route-binding packets remain evidence of those dated steps only.
Current-state sources
Chain statusMutable height, block time, chain ID, and sync posture.Node informationApplication and Cosmos SDK version plus read-adapter evidence.Public state recordDated operational posture, venue description, exports, boundaries, and current work.ReadinessRemaining work that live transport does not solve.