QuantProp. Analyze a trade file ↗
coinback / Data audit

Binance COIN-M liquidation snapshot validation sample

Binance COIN-M liquidation snapshot checked directly: every row duplicated twice, 50 real events after deduplication, and research caveats.

Original record: 2024-10-14 · Migrated: 2026-10-27 · Translated from Korean: 2026-10-27
A historical record, not rerun in this migration.

The figures, hypotheses and verdicts of the time are preserved. A past positive result or candidate mention does not mean validated profitability today or a live-trading recommendation. Validation periods that were already used are not treated as new independent validation.

This is an English translation of a preserved Korean original. It describes conditions at the time of writing, not current provider specifications, costs or regulations. Phrases in the original about blocking or avoiding losses interpret simulated experiments and are not realized account results. Statistical trial counts differ from the number of independent strategies or CSV rows.

Binance COIN-M liquidation snapshot validation sample

Subject

  • Product: BTCUSD_PERP (COIN-M perpetual futures)
  • Date: 2024-10-14 UTC
  • Official source: https://data.binance.vision/data/futures/cm/daily/liquidationSnapshot/BTCUSD_PERP/BTCUSD_PERP-liquidationSnapshot-2024-10-14.zip
  • Checked on: 2026-07-16

Direct check results

  • The official ZIP file was actually downloaded and extracted.
  • The original CSV consists of 1 header row and 100 data rows.
  • Every row appears exactly twice as a fully identical duplicate.
  • Removing fully identical rows leaves 50 liquidation event rows.
  • The liquidationSnapshot duplicate-row problem is also reported in Binance's official repository.

File layout

  • *.original.zip: the original ZIP received from Binance
  • Plain *.csv: the CSV extracted from the original ZIP
  • *.deduplicated.csv: a minimally modified version with fully identical rows removed
  • *.cleaned.csv: a cleaned version that adds UTC/KST times and the liquidated position side after deduplication
  • normalize_liquidations.py: script that regenerates the cleaned version

Side interpretation

  • side=SELL: a forced sell order, so labelled as a long-position liquidation
  • side=BUY: a forced buy order, so labelled as a short-position liquidation

Caveats

  • This sample is BTCUSD_PERP COIN-M data, not BTCUSDT USD-M.
  • The liquidation stream is a snapshot that delivers only the latest liquidation order per symbol in each 1,000ms window. It is not a complete reconstruction of all liquidations.
  • Deduplication was based on rows where every original field is fully identical.
  • Before research use, missing days, duplicate patterns and contract specifications over the full period must be checked separately.

SHA-256

  • Original ZIP: ac313ff6899b255b157cb77d7e20e23713efa1ffda9c3e936079e947076c2cc9
  • Extracted original CSV: e5f5b94a8418b794090a2ea43b690877ad290e9c5310019bf4156fe0095a14c4
  • Deduplicated CSV: 9d7aece1c8b70155e5e62888e11512b6b460e90d704bac6c257da50ed38fdda1

Source and migration evidence

Source: Binance_BTCUSD_PERP_liquidation_sample_2024-10-14/README_KO.md

Original SHA-256: a8aefc1c3d77427d99bd9b4d2aa1b648825e2c01f1af17489ac93d2d4cf8c3d2

Raw data and account information are not part of the public package. The original results do not replace statistical or scientific revalidation. The English text is a translation; numbers, tables and charts are carried over unchanged.