JUPITER PREDICTIONSSEASON 1
VERIFIED CALL
Bitcoin above ___ on August 17?
64,000 no
ENTRY
83.4¢
SOLD AT
91.6¢
CALLER
@lovingrishi
PLACED
2026-08-17 · 12:16 UTC
Nº 0001335R
WIN
+10%
146938646558
JUPCALLERS.FUN
VerifiedwinBitcoin above ___ on August 17?: 64,000 no, +10%Market ↗

Verified: message id, word-for-word text, market link and entry price all captured when the call was posted.

Original Discord message, word for word

https://jup.ag/prediction/POLY-828453 Taking 64000 No @80 #nfa

Record

Posted
Mon, 17 Aug 2026 12:16:11 UTC
Entry
83.4¢ → sold 91.6¢ (closed early; scored on the sale price)

Outcome

Closed early by the caller at 91.6¢, +8.2¢ on the 83.4¢ entry.

closed early via #close (msg 1538929334817521684, posted 2026-08-17T13:22:27.000Z): entry 83.4c -> exit 91.6c (+8.2c realized); trade tape at the close: taker sold this outcome at 92c, 46s from the post; "#close 64000". APPLIED BY HAND: his three attempts (13:22, 13:28, 13:31) were all queued by the close guard, which read the bracket "64000" as a side contradicting his own "64,000 no" — the stored bracket carries a thousands separator and the guard compared them literally. Priced at the FIRST attempt, the moment he asked to close. Guard fixed the same day.

graded Mon, 17 Aug 2026 13:58:05 UTC
Verification details
Message id
1538884146938646558 open in Discord ↗ (requires server membership)
Market
POLY-828453 jup.ag ↗
Capture
auto-captured: #nfa + jup.ag link; side matched to outcome of "Bitcoin above ___ on August 17?"; side inferred from the linked event: only "64,000 no" is referenced outside the matchup phrase; entry 83.4¢ from the order-book ask at post time
Think this is wrong (misattributed, wrong entry, wrong grade, duplicate, not a call)? Say so in #prediction-alpha-nfa and tag AG with this call id (#1335). Corrections are published, never silent: see methodology.