Prediction evidence

unscoredPolicy v1.0

Source post

Published 23 Sept 2026, 23:09 UTC · fetched 12 Oct 2026, 06:22 UTC

Ash Crypto

@AshCrypto

Bitcoin is going to $200,000 ETH is going to $10,000 You are not bullish enough.
View 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

  • “BREAKING : 🇺🇸 BlackRock and other ETFs have bought $346.98 million worth of Bitcoin and $104.63 million worth of Ethereum. Institutions continue to load up. https://t.co/VjvKvBbSm4”Repeat24 Sept 2026, 03:59 UTC
  • “Don't panic over this correction. Bitcoin already had a massive run, so a pullback like this is completely normal. The first support to watch is $81K–$82K. The bigger trend is still positive as long as BTC holds the Weekly MA 50 near $78K. But if $83K is lost, this bounce starts looking more like a bull trap, with $75K as the next major support. For ETH, the support zone sits around $2,550–$2,350. Leverage traders need to be careful here. But if you’re a spot trader with a 2-year view, corrections like this can be good opportunities to buy at better prices.”Repeat24 Sept 2026, 10:39 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
“Bitcoin is going to $200,000”
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