Event

Bitcoin Up or Down - June 10, 4:45PM-5:00PM ET

1 signal across 1 market · $1,294 tracked · resolves Jun 10, 2026

This Polymarket event tracks whether Bitcoin finishes the 4:45–5:00 PM ET window on June 10 higher or lower than where it started, based on the Chainlink BTC/USD data stream. PolySpotter has flagged $1,294 in smart money activity, including a recent signal from a serial timer with an 82% win rate.

Markets (1)

  1. Bitcoin Up or Down - June 10, 4:45PM-5:00PM ET1 signal · $1,294 tracked

Top trades across all markets

  1. Serial timer, 82% winner

    Sharp serial near-resolution bettor with an 82% record and +$120k lifetime P&L bought Up shortly before this BTC window resolved.

    $1,294Wallet win rate: 82%Score: 11.3

Top wallets in this event

  1. 0x073ba6b9cf$1,294 · 1 market · 1 alert · 82% wins

FAQs

What are the Bitcoin Up or Down June 10 odds on Polymarket?

The odds show how traders are pricing whether Bitcoin will be up or down over the 4:45–5:00 PM ET interval on June 10. PolySpotter tracks those market prices alongside smart money activity so you can see both the live prediction market odds and who is moving them.

What does this Bitcoin Up or Down market resolve on?

The market resolves to “Up” if the Chainlink BTC/USD price at 5:00 PM ET is greater than or equal to the price at 4:45 PM ET. If it is lower, the market resolves to “Down.”

What is the smart money doing in this Bitcoin market?

PolySpotter has tracked $1,294 in smart money across this event and one recent signal. The latest alert highlighted a serial timer with an 82% winner profile, suggesting experienced short-window traders are active here.

Is this based on Coinbase, Binance, or another Bitcoin price?

No. This event uses the Chainlink BTC/USD data stream as the resolution source, so prices on individual exchanges may differ from the value used to settle the market.

When does the Bitcoin Up or Down June 10 market resolve?

The event covers the 15-minute window from 4:45 PM to 5:00 PM ET on June 10 and is scheduled to resolve shortly after, by 21:00 UTC.