Fast answer
Liquidity sweep signals need level, close, liquidity, and closure proof.
Before using a crypto liquidity sweep signal, record the venue, pair, timestamp, swept level, wick or break distance, close location, volume, market-depth context, spread, slippage estimate, entry trigger, invalidation, stop plan, and final close record. A swept level is not complete signal proof.
If the provider posts liquidity-sweep language without the swept level, close condition, venue, spread/depth context, risk fields, and follow-up after the setup fails or resolves, lower the evidence confidence.
Sweep checks
What to inspect in crypto liquidity sweep signals.
Swept level
The alert should name the prior high, prior low, range boundary, equal high/low, or obvious level being swept.
Close condition
Check whether the candle closed back inside the range, held outside the level, or left no clear confirmation.
Depth and spread
A sweep can happen in thin books. Spread, slippage, order size, and venue depth decide whether followers could execute realistically.
Complete record
The provider should preserve the original alert, before/after chart, updates, skipped entries, stop outcomes, and final close note.
Source context
Sweep language does not replace signal proof.
Investopedia explains that stop hunting can involve driving prices above or below anticipated stop placements and that clustered stop orders can add volatility once triggered. That context overlaps with liquidity-sweep language, but it does not prove a third-party sweep signal has edge, fill quality, or reliable reporting.
Review standard
A reviewable liquidity sweep call connects level, confirmation, risk, and result.
For CSR evidence review, crypto liquidity sweep signals should preserve the original alert, source chart, timestamp, symbol, venue, time frame, swept level, close condition, spread or depth context, trigger rule, invalidation, stop, target, updates, and final status. A liquidity label is not a substitute for a verifiable track record.