ACEUSDT rose 57% into Aug 8. The record covers the whole lead-up.
Move window: 2026-08-08 11:00 to 2026-08-08 17:00 UTC. The record for ACEUSDT currently ends 2026-08-14 00:00 UTC.
Counted on 2026-08-15, against a record covering to 2026-08-14 00:00 UTC. These numbers are frozen: this page will always say what it said the day it was written.
This move is in the event archive as a volatility spike on 2026-08-07. Open the archived event
Containment · 15m inside and Cascade clustering ≥ 0.55 and VWAP distance · day ≤ -0.032
feature.candle_containment_15m + feature.cascade_clustering_index + feature.vwap_dist
Read at 1 minute before the move.
Minutes like this appeared 69 times in the 43,201 minutes searched (0.2%). What followed leaned down: 47 of the 69 matches with a complete 30 minutes forward fell (68%).
Both are true: these readings sat before this rise, and the other times they appeared, what followed more often fell. That disagreement is the finding: a lead-up that looks special is not the same as one that usually comes before rises.
Of the 69 fires, 56 came before the move began; none were during it.
About 2.2 a day, on 16 of 31 days: spread through the record rather than one event.
q#c7f418b8 @ dataset de1f6756
Best supported: Containment · 15m inside and Cascade clustering ≥ 0.55 and VWAP distance · day ≤ -0.032, 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.
No account? Replay a real move tick by tick, free: TUT short squeeze · 9 Aug 2026.
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.
Book imbalance · top levels ≤ -0.94 and Book imbalance percentile ≤ 0.047 and Containment · 15m inside
feature.book_imbalance + feature.book_imbalance_pctrank + feature.candle_containment_15m
Read at 15 minutes before the move.
Minutes like this appeared only 4 times in the 43,201 minutes searched. What followed leaned down: 3 of the 4 matches with a complete 30 minutes forward fell (75%).
Both are true: these readings sat before this rise, and the other times they appeared, what followed more often fell. That disagreement is the finding: a lead-up that looks special is not the same as one that usually comes before rises.
Of the 4 fires, 2 came before the move began; none were during it.
About 0.1 a day, on 4 of 31 days: spread through the record rather than one event.
q#be938939 @ dataset de1f6756
Book imbalance · top levels ≤ -0.61 and Lower wick · 15m ≥ 0.6 and Cascade clustering ≥ 0.55
feature.book_imbalance + feature.candle_lower_wick_15m + feature.cascade_clustering_index
Read at 1 hour before the move.
Minutes like this appeared 131 times in the 43,201 minutes searched (0.3%). What followed leaned down: 85 of the 130 matches with a complete 30 minutes forward fell (65%).
Both are true: these readings sat before this rise, and the other times they appeared, what followed more often fell. That disagreement is the finding: a lead-up that looks special is not the same as one that usually comes before rises.
Of the 131 fires, 113 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 4.2 a day, on 26 of 31 days: spread through the record rather than one event.
q#4dcaed7c @ dataset de1f6756
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.
Every night the record counts what fired and what usually followed: the daily brief.