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 / 2073775743197426126:memecoin:$LIT

Prediction evidence

correctPolicy v1.0

Source post

Published 5 Jul 2026, 14:27 UTC · fetched 20 Oct 2026, 05:25 UTC

Al

Altcoin Sherpa

@AltcoinSherpa

$LIT still 1 of the strongest coins on the market overall, slow grind up without any meaningful pullback. I've just been watching it and haven't traded. Still looks incredibly strong though and 1 to buy a dip on. Could even grind to $3 honestly https://t.co/BwI12dQNyj

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.35 at 5 Jul 2026, 15:00 UTC.
Evaluation: price at the end of the 24 hours horizon, $2.53 at 6 Jul 2026, 15:00 UTC.
r = 2.52677856980921 / 2.35226229472737 − 1 = +7.42%
Direction d = +1 (bullish), so d × r = +7.42% (neutral only if the price is unchanged) → correct

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: explicit
Horizon: 24 hours (default, none stated)
Evidence span: “$LIT still 1 of the strongest coins on the market overall, slow grind up without any meaningful pullback.”
Confidence: 100%
Review state: auto accepted
Model / prompt: gpt-6-luna+decisions · decisions-v3

Outcome record

Status

correct

Baseline price

$2.35

Evaluation price

$2.53

Move

+7.42%

Neutral threshold

Unchanged price only

Price provider

geckoterminal

Evaluated at

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