Prediction evidence
unscoredPolicy v1.0Source post
Published 2 Sept 2026, 07:30 UTC · fetched 13 Oct 2026, 05:55 UTC
Michaël van de Poppe
@CryptoMichNL
This is very likely going to break upwards. The reasoning behind that is super simple, as it's currently been taking the liquidity beneath the lows. Next stop: $82,700 for #Bitcoin. https://t.co/1zhVnf6iMZView original on X ↗
How this was scored
Deterministic: the same prices and policy always give the same result
unscored Repeat call within an existing 24h episode
Only the end-of-horizon price counts. A brief move followed by a reversal is not a success. Read the methodology
Same 24h episode
Repeated same-asset, same-direction calls count once, anchored to the first eligible post
- “Thank you very much, sweep of the lows has happened on #Bitcoin and that was much needed. I don't think we'll drop much from here, much rather we continue to go sideways in this range before we'll take out higher. The best part: #Altcoins are holding up quite nicely vs. Bitcoin. Time to see the next rally.”Repeat1 Sept 2026, 19:15 UTC
- “As #Bitcoin is likely to break to the upside, I would expect to see a strong breakout of $SUI on the horizon. Breaking through $0.7330 triggers that move and the next stop then should be $0.87-0.90. I would also not be surprised if the BTC pair starts to break out and the trend goes to $1.50.”Repeat2 Sept 2026, 09:31 UTC
AI interpretation
Uses only text available at publication time
- Asset
- Bitcoin (BTC)
- Direction
- ▲ Bullish
- Intent
- explicit
- Horizon
- 24 hours (default, none stated)
- Evidence span
- “Next stop: $82,700 for #Bitcoin.”
- Confidence
- 90%
- Review state
- auto accepted
- Model / prompt
- gemini-3.1-flash-lite · prompt-v1
Outcome record
- Status
- unscored
- Baseline price
- —
- Evaluation price
- —
- Move
- —
- Neutral threshold
- ±1.00%
- Price provider
- —
- Evaluated at
- 13 Oct 2026, 06:11 UTC
- Policy version
- v1.0
Request a correction
Think the interpretation or outcome is wrong? Sign in with X to request a correction, so reviewers know who is asking.
Sign in to request a correction