Fast answer
Bitcoin liquidation-signal checks prove whether a BTC leverage event was visible before the result.
Before accepting a Bitcoin liquidation signal, record the BTC pair or contract, venue, liquidation side, amount or level, time window, open interest, funding, trigger, and final outcome.
If a provider marks a BTC liquidation call as successful without showing the original alert, data source, side, and final close, the result is not reviewable.
Data checks
What to inspect in Bitcoin liquidation signal records.
BTC contract
The record should separate BTC spot context from BTC perpetual or delivery-futures liquidation data.
Liquidation side
Long liquidations and short liquidations imply different pressure and should not be merged into one vague signal.
Venue and coverage
Exchange coverage, stream limits, snapshots, and data delay affect whether followers could act on the alert.
Outcome trail
Updates, invalidation, stop logic, execution costs, and final close records make the call auditable.
Source context
BTC liquidation alerts come from futures-market force-close data.
Binance documents all-market liquidation snapshots for futures streams, while its forced-liquidation glossary explains automatic closure of leveraged positions. Bitcoin liquidation signals should therefore show which BTC futures data feed or venue was used and whether the alert was timely enough to review.
Review standard
A reviewable BTC liquidation signal names side, venue, and timing.
For CSR evidence review, Bitcoin liquidation records should include contract, venue, side, amount or level, timestamp, open-interest and funding context, alert path, updates, invalidation, and final status.