TAKEUSDT rose 85% into Aug 3. The record covers the whole lead-up.
Move window: 2026-07-29 09:00 to 2026-08-03 04:00 UTC. The record for TAKEUSDT currently ends 2026-08-03 00:00 UTC.
This move ran past the end of the record, so the counts below cover the lead-up and the covered part of the move. The rest joins the record after tonight’s rebuild.
Upper wick · 15m ≥ 0.67 and Cascade clustering ≥ 0.58
feature.candle_upper_wick_15m + feature.cascade_clustering_index
Read at 1 minute before the move.
Minutes like this appeared 135 times in the 43,201 minutes searched (0.3%). What followed leaned up: 85 of the 135 matches with a complete 30 minutes forward rose (63%).
Of the 135 fires, 109 came before the move began and 26 happened while it was already under way. A fire during the move sees it; it does not telegraph it.
About 4.4 a day, on 29 of 31 days: spread through the record rather than one event.
q#f5eed095 @ dataset b91f2197
Best supported: Upper wick · 15m ≥ 0.67 and Cascade clustering ≥ 0.58, the combination with the most fires before the move began.
Opens this exact search in the research tool. Nothing runs until you confirm it there, and arming it as an alert sends a message when it next becomes true.
Picked in hindsight: the counts include every other time these readings appeared, not just this move.
Also counted
This is not a similarity search. Each count matches the exact readings above and nothing else.
Upper wick · 15m ≥ 0.67 and Cascade clustering ≥ 0.58 and VWAP distance · day ≤ -0.021
feature.candle_upper_wick_15m + feature.cascade_clustering_index + feature.vwap_dist
Read at 15 minutes before the move.
Minutes like this appeared only 22 times in the 43,201 minutes searched. What followed leaned up: 15 of the 22 matches with a complete 30 minutes forward rose (68%).
Of the 22 fires, 17 came before the move began and 5 happened while it was already under way. A fire during the move sees it; it does not telegraph it.
About 0.7 a day, on 14 of 31 days: spread through the record rather than one event.
q#131b91e6 @ dataset b91f2197
Cascade clustering ≥ 0.58 and Minutes to funding ≤ 1 and Return · 1h ≤ -0.024
feature.cascade_clustering_index + feature.mins_to_funding + feature.ret_1h
Read at 1 hour before the move.
Minutes like this appeared only 3 times in the 43,201 minutes searched. What followed leaned down: 2 of the 3 matches with a complete 30 minutes forward fell (67%).
Of the 3 fires, 2 came before the move began and 1 happened while it was already under way. A fire during the move sees it; it does not telegraph it.
About 0.1 a day, on 3 of 31 days: spread through the record rather than one event.
q#ef0d5002 @ dataset b91f2197
Fires often arrive as clusters of consecutive minutes, and forward windows overlap. A cluster is one episode, not many independent trials.
If these counts read weaker than the move suggested, that is the tool working: the lead-up of a picked move always looks special until it is counted everywhere else.