Research is a work in progress. Estimated release: 1 December 2026. Our goal is to make it a search engine for trading setups in recorded crypto markets.

edgedepthEARLY ACCESS
Menu
Terminal
Recent moves
ResearchResearch hubResearch WorkbenchLiquidation mapsPublished reportsEvent archiveSaved studiesLive alertsData coverage
LearnGuidesReading libraryWorked examplesGuided lessonsFAQ
DevelopersConnect an AI agentOpen source
← All readings
Browse related readings

Research Readings Liquidations

Which side the trailing hour of liquidations fell on

Also shown as Liquidation side skew (1h)

Short notional minus long notional over their sum, so +1 means every liquidated dollar was a short being closed and -1 means every dollar was a long being flushed.

Full definition and limits

Which side the trailing hour of liquidations fell on: short notional minus long notional over their sum, so +1 means every liquidated dollar was a short being closed and -1 means every dollar was a long being flushed. Absent on an hour with no liquidations.

Live monitoring
Binance Futures only; depends on the full setup
Observed
measured over the trailing hour
Unit
Ratio
Valid range
-1 to 1
Use in Research

What this cannot see

Binance throttles liquidation publications, so these readings describe the observed feed and miss some liquidation records.

More on this limit

Count estimation is still under validation. It would require uncertainty, support and freshness checks, and would not recover hidden event times or validate a price-level heatmap or cascade forecast.

Technical details

Field ID

feature.liq_side_skew_1h

Valid query operators

at least, at most, between

Window operators: lowest, highest, average, latest or change in, over a trailing window.

Editable query preset

Example: A recorded value of 0.5 ratio can be used in the editable condition below.

Starting point only. Review and edit before running.

{
  "schema_version": "research_query.v2",
  "normalization_version": "archive_normalization.v1",
  "feature_version": "feature_defs.v1",
  "target": "record_occurrences",
  "where": {
    "all": [
      [
        "feature.liq_side_skew_1h",
        "gte",
        0.5
      ],
      [
        "times.anchor_time",
        "gte",
        "2025-07-15T00:00:00.000Z"
      ]
    ]
  },
  "sort": [
    "times.anchor_time",
    "desc"
  ],
  "page": {
    "limit": 5,
    "cursor": null
  }
}

The search reports how often the record held this condition and what followed. It does not decide whether an idea works.

Read alongside