How often it went up14 measured cases
These odds in plain words
as of · counted from every past case of this pattern
Hacks of micro-cap tokens with BTC below its 50-day average: 14 of the 22 past cases on record have a measured next-day move, and 1 of those 14 closed higher — a base rate of 7%, with a 90% range of 2% to 27%, counted as of Oct 4, 2026.
- By day 30, 5 of the 14 cases measured that far were still above the close before the event (36%).
- The typical day-30 move was −9.4%, the best +42.3% and the worst −46.9%.
- Against Bitcoin over the same 30-day windows, the typical case ran −13.0% vs BTC and beat it in 21.4% of 14 comparable cases.
- No recent-cases check yet: it needs 20 measured cases and this pattern has 14 as of Oct 4, 2026.
Source: every past event of this kind and the price move measured after it · fetched
Coming upON RECORD
Coming up: scheduled events that match this pattern
as of · upcoming events
NO DATA YET Bitcoin's trend on a future day is only known on that day, so no scheduled hack can be matched to this pattern before it happens.
Scheduled ones without the BTC condition: Hacks of micro-cap tokens →
Every past case22 cases
Every past hack behind these odds
as of · events and their measured price moves
All 22 past cases behind the numbers above, newest first. Each row links to the event on its token's page, and a row not measured yet shows when its window closes.
| Date | Token | Venue / size | Next day | 30 days | vs BTC | Result |
|---|---|---|---|---|---|---|
| 2026 | ||||||
| Ocean Protocol (OCEAN) | — | — | — | — | not measured yet | |
| Taiko (TAIKO) | — | −14.7% | −8.0% | −11.5% | down next day | |
| AZTEC (AZTEC) | — | −8.9% | −20.8% | −18.1% | down next day | |
| Stake DAO (SDT) | — | — | — | — | not measured yet | |
| Drift Protocol (DRIFT) | — | −40.0% | −41.5% | −56.1% | down next day | |
| Resolv (RESOLV) | — | −10.2% | −46.9% | −54.4% | down next day | |
| Stake DAO (SDT) | — | — | — | — | not measured yet | |
| Solv Protocol (SOLV) | — | −7.0% | +9.5% | +12.1% | down next day | |
| IoTeX (IOTX) | — | −17.6% | 0.0% | −4.2% | down next day | |
| Moonwell (WELL) | — | −6.5% | +2.7% | −3.2% | down next day | |
| Saga (SAGA) | — | −6.8% | −41.4% | −18.3% | down next day | |
| 2025 | ||||||
| Zerobase (ZBT) | — | −4.2% | +17.9% | +19.6% | down next day | |
| Goldfinch (GFI) | — | +2.8% | −25.7% | −28.7% | up next day | |
| DIMO (DIMO) | — | — | — | — | not measured yet | |
| Moonwell (WELL) | — | −14.5% | −28.2% | −14.5% | down next day | |
| Balancer (BAL) | — | — | — | — | not measured yet | |
| OlaXBT (AIO) | — | — | — | — | not measured yet | |
| zkSync (ZK) | — | −3.5% | +42.3% | +19.7% | down next day | |
| Spell Token (SPELL) | — | −5.1% | −10.7% | −18.1% | down next day | |
| Volt Inu (VOLT) | — | — | — | — | not measured yet | |
| 2024 | ||||||
| Echelon Prime (PRIME) | — | −1.7% | +5.0% | −9.4% | down next day | |
| PYTHIA (PYTHIA) | — | — | — | — | not measured yet | |
Source: every event whose token matched the pattern at the time; price moves measured by PatternPlus · fetched
How this is counted
How these odds are counted
as of · methodology
This page is a count of 14 measured past cases, not advice. A pattern is a set of conditions on an event and its token at the time (market-cap bucket and BTC regime), kept once 8 of its cases have a measured next-day move.
- Every share comes with a 90% range (a Wilson interval).
- Patterns with 20 or more measured cases are counted again on their older 60% and newest 40% of cases, and a pattern whose majority side flips is flagged as flipped.
- Past patterns can stop working.
The full method — how patterns are built, the 90% ranges, the recent-cases check and the minimum number of cases — is on the methodology page.
Questions
Questions about this pattern
as of · answers generated from this count
- What does the 7% figure on this page mean?
- It is a base rate: 1 of the 14 measured past cases of hacks of micro-cap tokens with BTC below its 50-day average closed above the close before the event one day later, counted as of Oct 4, 2026.
- It is a count of the past, with a 90% range of 2% to 27% — not advice, and past patterns can stop working.
- How is a case measured?
- Each case compares the last daily UTC close before the event with the closes 1 and 30 days after it, exactly as on every event list on this site.
- The vs-BTC column subtracts Bitcoin's move over the same 30 days.
- Why does this pattern exist and others not?
- A pattern is kept only once at least 8 past cases have a measured next-day move.
- This one has 14.
- Narrower combinations of the same conditions with fewer than 8 cases are left out, and their cases stay counted in the broader pattern.
- What does the recent-cases check say here?
- Nothing yet — the split needs 20 measured cases and this pattern has 14.
- A flipped flag means the older and newer halves of the record disagree about the direction.
- Where do the 22 cases come from?
- From this site's own event history: every hack with a known date whose token met the pattern's conditions at the time, with its moves measured from CoinPaprika daily closes.
- The full list, with dates, is on this page.