JUPITER PREDICTIONSSEASON 2
VERIFIED CALL
Bitcoin above ___ on October 30?
82,000
ENTRY
10¢
SOLD AT
2.5¢
CALLER
@Buddy
PLACED
2026-10-29 · 10:26 UTC
Nº 0006735R
LOSS
-75%
908738185125
COMMUNITY.JUP.AG
LOSSVerifiedPredictionsCall #6735 · Season 2
Verified: message id, word-for-word text, market link and entry price all captured when the call was posted.
Bitcoin above ___ on October 30?
Said · before resolution · timestamped in Discord
“Pick: 82,000 Reasoning: Bitcoin will really up , at this support should get pushed higher , 82k seems like a strech but doable , we never know #nfa (submitted on community.jup.ag)”
Buddy on community.jup.ag
Enteredthe ask at that moment, not a price typed later
82,000 @ 10¢
flat 1-unit stake: every call on the board is scored the same way · closed early at 2.5¢
Resolved · caller’s sale
Closed early by the caller at 2.5¢, -7.5¢ on the 10¢ entry.
-0.75uat a 1-unit stake (sold at 2.5¢)
Verification details
- Submission id
1565310908738185125(submitted on this site, not posted in Discord)- Market
POLY-1241186jup.ag ↗ (opens in a new tab)- Capture note
- submitted on community.jup.ag; event "Bitcoin above ___ on October 30?"; entry 10¢ from the order-book ask at submit; final at submit: the price the caller confirmed on the form
- Graded via
- closed early via #close (msg 1565529829572711605, posted 2026-10-30T00:56:37.507Z): entry 10c -> exit 2.5c (-7.5c realized); order-book bid at the close: 2.5c (ask 2.6c); final at close: the order-book bid when the caller pressed close; "#close"
Think this is wrong (misattributed, wrong entry, wrong grade, duplicate, not a call)? Say so in #prediction-alpha-nfa (opens in a new tab) and tag AG with this call id (#6735), within 48 hours of grading. Corrections are published, never silent: see methodology.
The market
Bitcoin above ___ on October 30?
- Venue
- Jupiter Prediction Markets
- Jupiter trade
- No Jupiter trade found in linked wallets
- Ask at post
- 82,000 @ 10¢
- Resolution
- caller’s sale (closed early)