Omni Terminal

Liquidations & Margin Stress

Liquidation-aware risk context built on documented stream and derivation contracts.

Liquidations are one of Omni Terminal’s most documented analytics surfaces. The terminal combines liquidation trades, liquidation stats, cluster and bucket views, FFF context, and margin stress summaries using documented upstream contracts and verification rules.

At a glance

Live liquidation context
Trades + stats Omni uses both recent liquidation events and richer liquidation-stats snapshots.
Risk views
Buckets + clusters + FFF The terminal surfaces more than raw prints by exposing derived cluster and curve context.
Margin stress
Positions live The margin stress tab is explicitly documented as using `positions_live`-backed backend summaries.

Why It Matters

What traders and researchers should take away

  • Liquidation pressure and margin stress can change the meaning of a price move fast.
  • Cluster and bucket views help traders read risk concentration instead of only reading individual liquidation prints.
  • Ask Omni and trader-profile workflows both reuse liquidation context, making this a core workflow area.

How it works

What the product uses behind the scenes

  • hyperliquid-data-api documents the liquidation position flow and Kafka/ClickHouse contracts.
  • Omni documents how liquidation-stats snapshots are consumed and how margin stress is derived.
  • The stream chain from node to data-api to terminal is explicitly documented and treated as a contract.

Notes

Things to know

  • Liquidation and stress analytics are stateful and time-sensitive; answers should distinguish live state from historical views.
  • Rate-limit-safe verification matters when probing public trader profiles or Hyperliquid info endpoints.
  • Descriptions should avoid certainty language because account and market state can drift quickly.

Liquidation surfaces

Omni turns liquidation data into a broader market and portfolio risk lens.

  • Streams recent liquidation trades.
  • Streams and renders liquidation stats including clusters, buckets, and FFF context.
  • Uses liquidation context in margin stress views, trader-profile probes, and Ask Omni prompts.

Margin stress

Margin stress docs need to explain how live position summaries are interpreted without overstating precision.

  • positions_live-backed summaries are the documented basis for margin stress views.
  • IM/MM, leverage, liquidation distance, and account mode context should be read together rather than as isolated numbers.
  • Ask Omni uses compact liquidation and account context to rank risk, not to guarantee outcomes.

How it is derived

The derivation path is documented across data-api and terminal docs.

  • Use LIQUIDATION_POSITION_FLOW.md for the position and derivation architecture.
  • Use KAFKA_AND_CH_STREAMS.md and Omni WS_STREAMS.md for stream and snapshot contracts.
  • Use Omni ai-notes.md for current downstream conventions such as positions_live and liquidation-stats behavior.

References

Implementation references

  • Liquidation position flow

    hyperliquid-data-api/docs/LIQUIDATION_POSITION_FLOW.md

    Documents the underlying derivation architecture for liquidation and position state.

  • Kafka and ClickHouse stream contracts

    hyperliquid-data-api/docs/KAFKA_AND_CH_STREAMS.md

    Documents the topic and snapshot contracts upstream of the terminal.

  • Omni AI notes

    omni-terminal/docs/ai-notes.md

    Documents current downstream conventions for liquidation-stats and margin stress behavior.

Next