Prediction evidence
neutralPolicy v1.0Source post
Published 24 Jul 2026, 17:27 UTC · fetched 13 Oct 2026, 05:56 UTC
K A L E O
@CryptoKaleo
Quoting · 23 Jul 2026, 14:40 UTC · context given to the AI
BREAKING: 45% chance Bitcoin hits $50,000 before $100,000 https://t.co/BfPAeWHwTQ#Bitcoin / bitcoin:native Still confident we see one last leg lower before the bottom is in this bear market. Optimistic path is hold off and continue to bounce a bit until mid to late August before moving lower, but also wouldn't be surprised if it happens sooner. One way or another - I think we're close to the bottom from a time perspective and it's important to have some capital ready to deploy when it happens and continue to stack and position yourself in high conviction plays. Don't expect to see $100K+ and new ATHs until 2027.View original on X ↗
How this was scored
Deterministic: the same prices and policy always give the same result
- Baseline: first BTC price at or after publication, $64,117 at 24 Jul 2026, 18:00 UTC.
- Evaluation: price at the end of the 24 hours horizon, $64,206 at 25 Jul 2026, 18:00 UTC.
r = 64206.14 / 64117.07 − 1 = +0.14%- Direction d = −1 (bearish), so
d × r = -0.14%against a neutral band of ±1.00% → neutral
Only the end-of-horizon price counts. A brief move followed by a reversal is not a success. Read the methodology
AI interpretation
Uses only text available at publication time
- Asset
- Bitcoin (BTC)
- Direction
- ▼ Bearish
- Intent
- explicit
- Horizon
- 24 hours (default, none stated)
- Evidence span
- “Still confident we see one last leg lower before the bottom is in this bear market.”
- Confidence
- 85%
- Review state
- auto accepted
- Model / prompt
- gemini-3.8-flash · prompt-v1
Outcome record
- Status
- neutral
- Baseline price
- $64,117
- Evaluation price
- $64,206
- Move
- +0.14%
- Neutral threshold
- ±1.00%
- Price provider
- coinbase
- 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