Fast answer
Bid-ask spread signals need liquidity context, size, risk, and closure proof.
Before using a crypto bid-ask spread signal, record the venue, pair, timestamp, bid, ask, spread percentage, order size, depth, slippage estimate, fee assumptions, volatility context, entry trigger, invalidation, stop plan, and final close record. A narrow or wide spread is not a complete signal.
If the provider posts spread language without venue, pair, order size, depth, fees, risk fields, and follow-up after execution conditions change, lower the evidence confidence.
Liquidity checks
What to inspect in crypto bid-ask spread signals.
Venue and pair
Spreads are venue-specific. The alert should name the exchange, pair, product type, quote currency, and whether the data reflects spot or derivatives.
Order size and depth
A top-of-book spread can look tight while realistic size still slips. Check depth, expected fill size, fees, and market-order assumptions.
Volatility and timing
Spreads can widen during news, funding events, liquidations, maintenance windows, and thin-session periods. A signal needs a timing rule.
Complete record
The provider should preserve the original alert, spread snapshot, depth or slippage context, updates, fill status, risk handling, and final close note.
Source context
Spread context does not replace signal proof.
Binance Academy defines bid-ask spread as the difference between the lowest asking price and the highest bid price on an order book. That liquidity context does not prove a third-party spread signal has edge, realistic execution, or reliable reporting.
Review standard
A reviewable spread call connects liquidity, size, risk, and result.
For CSR evidence review, crypto bid-ask spread signals should preserve the original alert, source link or screenshot, timestamp, symbol, venue, product type, bid, ask, spread, order-size assumption, depth, fee assumptions, entry condition, invalidation, stop, target, updates, and final status. A spread snapshot is not a substitute for a verifiable track record.