Skip to content

Home Arena Leaderboard Token sale

Loading…

Public calls. Verifiable outcomes.

Methodology Docs Privacy Terms & risk X ↗

Leaderboard This week Head to head Get ranked Methodology Claim profile

Published scoresSign in with X

Leaderboard / @AltcoinSherpa / 2080629091745620046:memecoin:$LIT

Prediction evidence

incorrectPolicy v1.0

Source post

Published 24 Jul 2026, 12:20 UTC · fetched 19 Oct 2026, 13:39 UTC

Al

Altcoin Sherpa

@AltcoinSherpa

$LIT is getting close to a buy for me, I think anywhere from the $1.80-$2.00 area is decent. To be determined if we're going to run back to the highs on this current move but I think a bounce play is definitely happening somewhere soon. More watching and waiting for now but entire market is a bit choppy

View original on X ↗

How this was scored

Deterministic: the same prices and policy always give the same result

Baseline: first $LIT price at or after publication, $2.11 at 24 Jul 2026, 13:00 UTC.
Evaluation: price at the end of the 24 hours horizon, $2.06 at 25 Jul 2026, 13:00 UTC.
r = 2.06177669140834 / 2.10549218959628 − 1 = -2.08%
Direction d = +1 (bullish), so d × r = -2.08% (neutral only if the price is unchanged) → incorrect

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: Memecoins: $LIT ($LIT)
Direction: ▲ Bullish
Intent: inferred
Horizon: 24 hours (default, none stated)
Evidence span: “$LIT is getting close to a buy for me, I think anywhere from the $1.80-$2.00 area is decent.”
Confidence: 90%
Review state: auto accepted
Model / prompt: gpt-6-luna+decisions · decisions-v3

Outcome record

Status

incorrect

Baseline price

$2.11

Evaluation price

$2.06

Move

-2.08%

Neutral threshold

Unchanged price only

Price provider

geckoterminal

Evaluated at

21 Oct 2026, 18:15 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