How often it went up16 measured cases
These odds in plain words
as of · counted from every past case of this pattern
Hacks of tokens outside the big categories with BTC below its 50-day average: 16 of the 33 past cases on record have a measured next-day move, and 4 of those 16 closed higher — a base rate of 25%, with a 90% range of 12% to 45%, counted as of Oct 3, 2026.
- By day 30, 8 of the 16 cases measured that far were still above the close before the event (50%).
- The typical day-30 move was +1.3%, the best +42.3% and the worst −63.0%.
- Against Bitcoin over the same 30-day windows, the typical case ran −6.1% vs BTC and beat it in 43.8% of 16 comparable cases.
- No recent-cases check yet: it needs 20 measured cases and this pattern has 16 as of Oct 3, 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 tokens outside the big categories →
Every past case33 cases
Every past hack behind these odds
as of · events and their measured price moves
All 33 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) | — | — | — | — | not measured yet | |
| Raydium (RAY) | — | +2.1% | +21.0% | +17.0% | up next day | |
| Humanity (H) | — | — | — | — | not measured yet | |
| Fluid (FLUID) | — | — | — | — | not measured yet | |
| Stake DAO (SDT) | — | — | — | — | not measured yet | |
| Resolv (RESOLV) | — | −10.2% | −46.9% | −54.4% | down next day | |
| Stake DAO (SDT) | — | — | — | — | not measured yet | |
| Aave (AAVE) | — | +1.8% | −14.3% | −18.4% | up next day | |
| 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) | — | — | — | — | not measured yet | |
| Saga (SAGA) | — | −6.8% | −41.4% | −18.3% | down next day | |
| 2025 | ||||||
| Flow (FLOW) | — | −42.8% | −63.0% | −64.1% | down next day | |
| Trust Wallet Token (TWT) | — | +0.7% | +3.8% | +2.0% | sideways next day | |
| yearn.finance (YFI) | — | −7.5% | +2.7% | −8.0% | down next day | |
| Zerobase (ZBT) | — | −4.2% | +17.9% | +19.6% | down next day | |
| Goldfinch (GFI) | — | — | — | — | not measured yet | |
| DIMO (DIMO) | — | — | — | — | not measured yet | |
| Moonwell (WELL) | — | — | — | — | not measured yet | |
| UXLINK (UXLINK) | — | — | — | — | not measured yet | |
| SwissBorg (BORG) | — | — | — | — | not measured yet | |
| OlaXBT (AIO) | — | — | — | — | not measured yet | |
| zkSync (ZK) | — | −3.5% | +42.3% | +19.7% | down next day | |
| Venus (XVS) | — | −7.9% | −3.4% | −16.0% | down next day | |
| Spell Token (SPELL) | — | −5.1% | −10.7% | −18.1% | down next day | |
| 1INCH (1INCH) | — | −0.8% | −29.6% | −16.8% | sideways next day | |
| 2024 | ||||||
| Echelon Prime (PRIME) | — | — | — | — | not measured yet | |
| PYTHIA (PYTHIA) | — | — | — | — | not measured yet | |
| Aave (AAVE) | — | +2.8% | +42.0% | +31.3% | up next day | |
| Ronin Token (RON) | — | — | — | — | not measured yet | |
| BitTensor (TAO) | — | −14.3% | +7.9% | +4.0% | down next day | |
| Rain Protocol (RAIN) | — | — | — | — | 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 16 measured past cases, not advice. A pattern is a set of conditions on an event and its token at the time (category group 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 25% figure on this page mean?
- It is a base rate: 4 of the 16 measured past cases of hacks of tokens outside the big categories with BTC below its 50-day average closed above the close before the event one day later, counted as of Oct 3, 2026.
- It is a count of the past, with a 90% range of 12% to 45% — 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 16.
- 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 16.
- A flipped flag means the older and newer halves of the record disagree about the direction.
- Where do the 33 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.