| Outcome | Probability | Yes Bid | Yes Ask | 24h Change | Volume | |
|---|---|---|---|---|---|---|
| Target Price: $634.12 | 0% | 0¢ | 0¢ | — | $0 | Trade → |
This market asks whether BNB will meet a $634.12 price target within a specified 15-minute window; it matters because short intraday moves can reflect liquidity, order-flow shocks, or news-driven volatility in the crypto market.
BNB is the native token of the Binance ecosystem and has historically shown rapid intraday swings around major exchange events, macro crypto moves, and large trades. Short-window targets like a 15-minute threshold capture transient liquidity and microstructure effects rather than long-term fundamentals.
Prediction market odds for this contract summarize traders' collective expectations about whether that 15-minute pricing condition will occur; they update in real time as new information, orders, or news arrive and should be read as a market-implied consensus, not a guaranteed outcome.
The market refers to a contiguous 15-minute period specified in the event's resolution rules; the exact start and end timestamps for that window will be listed on the KALSHI event page and determine which prices are considered for settlement.
The authoritative price source and any index or exchange used for resolution are defined in the event's resolution section on KALSHI; consult the market rules there to see whether a specific exchange, consolidated index, or mid-price is the reference.
That depends on the event's exact condition—some contracts resolve on any intrawindow touch while others require the price at a specific timestamp or the 15-minute close to meet the threshold; check the contract language on KALSHI to know which interpretation applies.
The event currently lists the close as TBD; KALSHI will publish the trading cutoff and the scheduled resolution window on the market page—monitor the event details for updates and email/notification options if you want an alert.
KALSHI's market rules include fallback procedures or arbitration for data unavailability; those contingencies—such as using an alternate feed or delaying resolution—are described in the event's resolution policy on the platform.