Liquidations & Margin Stress

See Hyperliquid liquidation concentration, then inspect the positions behind it.

Omni Terminal brings liquidation events, price buckets, clusters and margin stress into the trading workspace. Select a bucket to inspect the positions contributing to that price range, then open a wallet address to investigate its live trader profile. Use this context alongside price, funding and AI-analyzed news; liquidation levels can change as prices, collateral and positions change.

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 Review current position exposure and account margin context alongside liquidation levels.

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.
Position side and liquidation flow are explicit: long-position liquidations create sell flow, while short-position liquidations create buy flow.
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.
A concentration of estimated liquidation levels is not a prediction that price will reach them or that every position will liquidate.
Account mode, collateral, funding and position changes can move liquidation levels; check freshness and available coverage.

Screenshots

Real UI references

These are captured from Omni Terminal routes with public-safe state. Private balances, wallet secrets, access headers, and live private positions are not used.

Omni liquidation bucket detail showing BTC heatmap context and underlying public position estimates — **Liquidation bucket detail with heatmap context and underlying position estimates. Values are a dated snapshot; liquidation prices can change.** Source: `/terminal/liquidation-bucket?symbol=BTC&price=74300&kind=bucket` 2026-10-15 - bde1451b

Liquidation surfaces

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

Open Liq Stats for the selected market to review long/short exposure and recent liquidation bursts.
Switch between Buckets, Clusters and FFF to inspect how liquidation exposure is distributed.
Click a bucket to open its detail view and inspect contributing positions, including side, size and estimated liquidation price.
Select a wallet address to investigate the public trader profile. Ask Omni can add portfolio and news context to your risk review.

Margin stress

Review margin pressure in the context of the current account and positions.

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.

Trader-profile link

Liquidation context is also an investigation surface for public wallets and trader profiles.

Click an address in the liquidation panel to open its public profile without leaving the research workflow.
Expand the profile to inspect Equity and PnL Performance charts, open orders, recent fills and account metrics. Choose View positions in terminal to inspect market charts.
Rankings based on current position unrealized PnL describe a snapshot, not a record of a trader’s lifetime performance.

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.