Leaderboardvince.call #1518
JUPITER PREDICTIONSSEASON 1
VERIFIED CALL
Bitcoin above ___ on August 20?
72,000 yes
ENTRY
22.1¢
SOLD AT
80.8¢
CALLER
@vince.
PLACED
2026-08-20 · 14:33 UTC
Nº 0001518R
WIN
+266%
962730184815
JUPCALLERS.FUN
Post to XSave
VerifiedwinBitcoin above ___ on August 20?: 72,000 yes, +266%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

Yes 26c 72.000 #nfa Risky 6/10 https://jup.ag/prediction/POLY-844167

Record

Posted
Thu, 20 Aug 2026 14:33:53 UTC
Entry
22.1¢ → sold 80.8¢ (closed early; scored on the sale price)Entry 22.1¢: the price the Buy button actually charged the moment the call was posted. The caller wrote 26¢, but that price was not there to buy.

Outcome

Closed early by the caller at 80.8¢, +58.7¢ on the 22.1¢ entry.

closed early via #close (msg 1540013721441669220, posted 2026-08-20T15:04:43.263Z): entry 22.1c -> exit 73.3c (+51.2c realized); CLOB history 0.733 at 2026-08-20T15:04:12.000Z (31s from post); "#close" | RE-PRICED from the trade tape once it indexed: exit 73.3c -> 80.8c (taker bought the other outcome at 19c, which is this one sold at 81c, 15s from the post)

graded Thu, 20 Aug 2026 15:05:07 UTC
Verification details
Message id
1540005962730184815 open in Discord ↗ (requires server membership)
Market
POLY-844167 jup.ag ↗
Capture
auto-captured: #nfa + jup.ag link; side matched to outcome of "Bitcoin above ___ on August 20?"; boarded from review queue (was: side "Yes" does not match event "Bitcoin above ___ on August 20?" (POLY-844167)); the written side "Yes" matched no market here, so it was read from the event: only "72,000 yes" is referenced outside the matchup phrase; entry 22.1¢ from the order-book ask at post time (caller stated 26¢)
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 (#1518). Corrections are published, never silent: see methodology.