Loading shell…
CryptoMulti-outcomeExpires Jan 1, 2027

Will July be the best month for Bitcoin in 2026?

Probability

11¢

1h

+0.0pp

24h

+0.0pp

24h Vol

$25.00

Liquidity

$7.7K

Probability (last 7 days)

-0.5pp 7d
Apr 18, 2026, 00:00Apr 24, 2026, 23:23
updated 0s ago·src:Polymarket CLOB

Why did it move?

 

Heuristic summary, generated from the public market metrics above: probability movement, volume, liquidity, spread, signals, and resolution status.

Timeline — news, trades, signals, price moves

AllTradesSignalsPrice
  • 0s agoResolve

    Market resolves in 6029.6h

    LOW
  • 23:23Signal

    Signal · Resolution risk

    Expires in 6030h with open resolution ambiguity.

    LOW
updated 0s ago·src:Polymarket CLOB·Polymarket Data

Active signals

Recent Trades

No recent trades visible from the Data API for this market.

updated 0s ago·src:Polymarket Data

Market Description

This market will resolve to the calendar month in 2026 during which Bitcoin has the highest percentage change. The “Change” value shown for each monthly candle will be used. A monthly candle is considered finalized once the following month’s candle is published. The resolution source is Binance, using the BTC/USDT trading pair: https://www.binance.com/en/trade/BTC_USDT If two or more months are tied for the highest percentage change, this market will resolve to the earliest month chronologically. Only Binance BTC/USDT data will be used. Prices from other exchanges, trading pairs, or data sources will not be considered. If it becomes impossible for a given month to have the highest percentage change in 2026, that outcome may resolve to “No” immediately.

Resolution & Risk

MEDIUM risk
End date
Jan 1, 2027
UMA status
n/a
Resolution source
Not specified in metadata
Market type
Multi-outcome (neg-risk)
  • Part of a multi-outcome event (neg-risk): only one market can resolve YES.
  • No primary resolution source listed — read the full market rules before acting.
Read full market rules on Polymarket

Alerts

¢
Deliver

In-app banners work now. Email / Telegram / Discord delivery lands when the backend alert dispatcher ships (needs RESEND_API_KEY + per-user webhook storage).