CoinDesk’s report at 6:42 a.m. EST on 20 November placed a pocket of potential long liquidations on the Binance heatmap between $60,500 and $60,900. Bitcoin in that note was around $61,500, so the pocket sat just below the spot price of that morning. It was a map of positions that would be forced closed if the price traded there. It was not a level a reader had written into a plan.
One drop, three liquidation clocks already followed that pocket through Saturday, when Binance touched $55,130. The pocket was traded. The question that note left open is which price deserves an alert when the heatmap and the trade plan mark different prices.
Two marks, one job
Alerts versus signals separates the tools. An alert says the price is here. A signal says here is a setup, with an asset, a direction, a time, and an invalidation. The alert goes on the invalidation, the level that would end the idea you already wrote down. Set the trade alert at the level that would invalidate the setup you wrote down.
Friday morning offered a second mark, drawn by other people’s leverage. Moving the alert to the edge of that pocket changes the plan to match a map that expires as positions close. By Saturday the map’s pocket was behind the price. An alert parked there would have fired because $60,500 traded. The firing would still have been a clock, not a new call.
A later cluster is the same kind of mark
crypto.news on 21 November marked liquidation clusters above Saturday’s price near $62,700 and $66,000. Those clusters are another heatmap, drawn after the morning pocket had already been traded through. They are candidates for a watcher’s curiosity. They become an alert only if they are the invalidation already in the setup. A cluster overhead is not that invalidation merely because it is the next pocket on the picture.
Beside a CryptoCrispy plan
Write the level that ends the idea before you look at the heatmap. If the heatmap and that level differ, the alert stays on the level you wrote. The heatmap can tell you where forced closes were crowded at the time the picture was taken.
Keep the assistant call that is already published. Keep the position size printed for that trade. Hold adds nothing. Count the call once, even when the Pivot agrees.
Takeaways
- At 6:42 a.m. EST on 20 November, CoinDesk’s Binance pocket was $60,500 to $60,900, with Bitcoin near $61,500.
- Saturday traded through that pocket. A later map marked clusters near $62,700 and $66,000.
- The alert stays on the invalidation in the setup. A heatmap pocket is a different mark.
CryptoCrispy provides market analytics and trading tools. This article is general information, not personal financial advice. Heatmap levels are from CoinDesk and crypto.news, dated in the text, and move when the window moves. They are not CryptoCrispy performance.