Fast answer
Market depth signals need venue, size, spread, and closure proof.
Before using a crypto market depth signal, record the venue, pair, timestamp, top-of-book spread, depth range, assumed order size, visible wall age, cancellation risk, expected slippage, entry trigger, invalidation, stop plan, and final close record. Displayed depth is not complete signal proof.
If the provider posts depth screenshots without venue, pair, depth range, assumed size, spread, slippage context, risk fields, and follow-up after the book changes, lower the evidence confidence.
Depth checks
What to inspect in crypto market depth signals.
Venue and product
Order books are venue-specific. The alert should name exchange, pair, spot or derivatives product, and quote currency.
Depth range and size
Top-of-book data can differ from the depth needed for a real order. Check the price range and assumed order size.
Refresh and cancellation risk
Displayed orders can move, cancel, or refill. A depth signal should explain wall age, refresh behavior, and spoofing risk.
Complete record
The provider should preserve the original book snapshot, timestamp, entry assumptions, updates, fill status, stop handling, and final close note.
Source context
Market-depth context does not replace signal proof.
CME Group describes its Liquidity Tool as analyzing bid-ask spreads, book depth, and cost-to-trade statistics, including market depth at each price level. That execution-quality context helps frame market-depth claims, but it does not prove a third-party crypto depth signal has edge or reliable reporting.
Review standard
A reviewable depth call connects book data, execution assumptions, risk, and result.
For CSR evidence review, crypto market depth signals should preserve the original alert, order-book source, timestamp, symbol, venue, depth range, assumed size, spread, slippage estimate, trigger rule, invalidation, stop, target, updates, and final status. A depth snapshot is not a substitute for a verifiable track record.