PINNED INVESTIGATIONSee this market’s latest move

TAKEUSDT rose 84% into Aug 3. The record covers the whole lead-up.

Move window: 2026-07-29 16:00 to 2026-08-03 04:00 UTC. The record for TAKEUSDT currently ends 2026-08-05 00:00 UTC.

Counted on 2026-08-07, against a record covering to 2026-08-05 00:00 UTC. These numbers are frozen: this page will always say what it said the day it was written.

Book imbalance · top levels ≥ 0.84 and Book imbalance percentile ≥ 0.9 and Cascade clustering ≥ 0.58

feature.book_imbalance + feature.book_imbalance_pctrank + feature.cascade_clustering_index

Read at 1 hour before the move.

Minutes like this are common here: 440 of the 43,201 minutes searched (1%), about 14 a day. What followed was close to a coin flip: 240 rose and 199 fell over the next 30 minutes (439 of the 440 matches have a complete 30 minutes forward).

Of the 440 fires, 327 came before the move began and 57 happened while it was already under way. A fire during the move sees it; it does not telegraph it. Timing was checked for the first 400 of the 440 fires.

About 14 a day, on 30 of 31 days: spread through the record rather than one event.

q#1a24af9f @ dataset 9dad0852

WATCH FOR THIS Watch the ignition replay

Best supported: Book imbalance · top levels ≥ 0.84 and Book imbalance percentile ≥ 0.9 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.

No account? Replay a real move tick by tick, free: EVAA short squeeze · 8 Jul 2026.

Picked in hindsight: the counts include every other time these readings appeared, not just this move.

What the minutes before it looked like

Where these readings were taken

Hourly candles. The marked lines are the minutes the readings came from: 1 minute, 15 minutes, 1 hour, 4 hours and 24 hours before the move began. Every one of them sits before the move, never inside it.

A reading stands out when it sits outside the range it usually holds. The rules are fixed: the same ones the moment reader on the research page uses.

At 1 minute before the move, 4 of the 39 readings stood out. 2026-07-29 15:59 UTC

READING	BEFORE THE MOVE	SEARCHES FOR
Compression · 15m feature.candle_compression_15m	2.646	≥ 2.6
Cascade clustering feature.cascade_clustering_index	0.5848	≥ 0.58
Minutes to funding feature.mins_to_funding	1	≤ 1
Realized vol percentile feature.realized_vol_pctrank	0.9268	≥ 0.92

At 15 minutes before the move, 4 of the 39 readings stood out. 2026-07-29 15:45 UTC

READING	BEFORE THE MOVE	SEARCHES FOR
Compression · 15m feature.candle_compression_15m	2.646	≥ 2.6
Cascade clustering feature.cascade_clustering_index	0.5848	≥ 0.58
Minutes to funding feature.mins_to_funding	15	≤ 15
OI velocity percentile feature.oi_velocity_pctrank	0.9944	≥ 0.99

At 1 hour before the move, 3 of the 39 readings stood out. 2026-07-29 15:00 UTC

READING	BEFORE THE MOVE	SEARCHES FOR
Book imbalance · top levels feature.book_imbalance	0.8462	≥ 0.84
Book imbalance percentile feature.book_imbalance_pctrank	0.9019	≥ 0.9
Cascade clustering feature.cascade_clustering_index	0.5848	≥ 0.58

At 4 hours before the move, 2 of the 39 readings stood out. 2026-07-29 12:00 UTC

READING	BEFORE THE MOVE	SEARCHES FOR
Cascade clustering feature.cascade_clustering_index	0.5848	≥ 0.58
VWAP distance · day feature.vwap_dist	-0.02291	≤ -0.022

At 24 hours before the move, 3 of the 39 readings stood out. 2026-07-28 16:00 UTC

READING	BEFORE THE MOVE	SEARCHES FOR
Compression · 15m feature.candle_compression_15m	0.4211	≤ 0.43
Cascade clustering feature.cascade_clustering_index	0.5849	≥ 0.58
Minutes to funding feature.mins_to_funding	0	≤ 1

Also counted

This is not a similarity search. Each count matches the exact readings above and nothing else.

Compression · 15m ≥ 2.6 and Cascade clustering ≥ 0.58 and Realized vol percentile ≥ 0.92

feature.candle_compression_15m + feature.cascade_clustering_index + feature.realized_vol_pctrank

Read at 1 minute before the move.

Minutes like this appeared 32 times in the 43,201 minutes searched (<0.1%). What followed leaned up: 18 of the 32 matches with a complete 30 minutes forward rose (56%).

Of the 32 fires, 20 came before the move began and 9 happened while it was already under way. A fire during the move sees it; it does not telegraph it.

About 1 a day, on 21 of 31 days: spread through the record rather than one event.

q#2ea10983 @ dataset 9dad0852

Compression · 15m ≥ 2.6 and Cascade clustering ≥ 0.58 and OI velocity percentile ≥ 0.99

feature.candle_compression_15m + feature.cascade_clustering_index + feature.oi_velocity_pctrank

Read at 15 minutes before the move.

Minutes like this appeared 36 times in the 43,180 minutes searched (<0.1%). What followed leaned up: 20 of the 36 matches with a complete 30 minutes forward rose (56%).

Of the 36 fires, 26 came before the move began and 7 happened while it was already under way. A fire during the move sees it; it does not telegraph it.

About 1.2 a day, on 23 of 31 days: spread through the record rather than one event.

q#b7514a70 @ dataset 9dad0852

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.