Fast answer
Crypto liquidation heatmap-signal checks prove whether a cluster was usable context or hindsight decoration.
Before accepting a liquidation-heatmap signal, record the heatmap source, exchange coverage, pair, side, time window, cluster level, open interest, funding context, invalidation, and final status.
If a provider posts only a heatmap screenshot after price moves, with no timestamped pre-trade level, invalidation, or final record, the proof is weak.
Data checks
What to inspect in liquidation heatmap signal records.
Source coverage
The record should name the heatmap source, venues covered, pair, time window, and whether spot or futures data is included.
Cluster direction
Review whether the call explains long-liquidation or short-liquidation clusters and the price levels involved.
Context overlap
Open interest, funding, order book, spread, and volatility context help separate real risk from colorful noise.
Final record
The signal should show pre-trade timestamp, updates, invalidation, execution assumptions, and final close or cancellation.
Source context
Liquidation streams and forced liquidation context need careful interpretation.
Binance futures documentation describes liquidation order streams as snapshots of force-liquidation order information, and Binance Academy explains forced liquidation as automatic position closure under certain conditions. A heatmap signal should therefore be treated as a map of possible forced-position pressure, not a standalone entry instruction.
Review standard
A reviewable heatmap signal ties the cluster to a timestamped thesis.
For CSR evidence review, liquidation-heatmap records should include source, venue coverage, pair, side, cluster level, timestamp, setup logic, invalidation, updates, costs, and final status.