Omni Terminal

L4 Orderbook

Order-level depth context for traders who need more than top-of-book.

Omni Terminal exposes L4 as a first-class view so traders can inspect liquidity structure, active order behavior, and order-level market pressure alongside price and liquidation signals.

At a glance

Hyperliquid L4
Supported The terminal has dedicated L4 URL building, state reducers, and ladder rendering logic.
Snapshot + updates
Both L4 handling includes snapshot ingestion and incremental update processing for ongoing ladder state.
Interpretation role
Liquidity context L4 is used as a structure and liquidity lens, not as a standalone trading promise.

Why It Matters

What traders and researchers should take away

  • L4 helps distinguish visible liquidity structure from ordinary top-of-book noise.
  • It supports reading where liquidity is resting, moving, or getting consumed.
  • Inside Omni, traders can line up L4 behavior with price, liquidations, and news in one workflow.

How it works

What the product uses behind the scenes

  • The Omni terminal has dedicated L4 socket builders, reducers, and supported-market checks.
  • The node/orderbook stack documents L4 snapshot limits and downstream backpressure behavior.
  • The terminal UI places L4 beside the rest of the market context rather than as a separate tool.

Notes

Things to know

  • L4 is a market-structure tool, not a certainty engine.
  • Not every market type is treated the same; support checks exist in the Omni L4 implementation.
  • Order-level data still needs to be interpreted with broader context and not read as guaranteed intent.

L4 surface

Omni has a dedicated L4 surface and supporting reducer logic for Hyperliquid.

  • Builds L4 websocket URLs from the browser-facing terminal API shape.
  • Maintains L4 state with snapshot handling and incremental order-status updates.
  • Renders ladder-like depth views so traders can inspect liquidity structure directly.

State model

Order-level data has to be reconstructed and bounded carefully before it becomes a useful UI surface.

  • Snapshots establish the initial ladder state before incremental updates are applied.
  • Reducers keep the browser state bounded so stale or unsupported markets do not pollute the view.
  • The upstream orderbook server documents snapshot bounds, backpressure behavior, and readiness expectations.

How traders use it

The point of L4 is to turn raw depth into usable market structure context.

  • Read liquidity concentration and price-level interest.
  • Compare L4 pressure against recent price and liquidation behavior.
  • Use it as one part of a combined view with funding, news, and risk.

Limits

Public docs should keep L4 claims grounded in what order-level data can and cannot prove.

  • Visible orders can move or cancel, so L4 should not be described as guaranteed intent.
  • Not every venue or market shape has identical L4 support; implementation checks are part of the contract.
  • The terminal does not ask the browser to connect directly to node-orderbook infrastructure.

References

Implementation references

  • Hyperliquid L4 implementation

    omni-terminal/src/lib/hyperliquidL4.ts

    Documents Omni-side L4 state handling, ladder construction, and supported market checks.

  • Realtime L4 URL handling

    omni-terminal/src/lib/hyperliquidRealtime.ts

    Shows the terminal websocket path for raw L4 orderbook routing.

  • Orderbook server runtime notes

    hyperliquid-node-orderbook-docker/orderbook/src/README.md

    Documents L4 snapshot bounds and the stream-gap/backpressure contract from the orderbook server.

Next