| Outcome | Probability | Yes Bid | Yes Ask | 24h Change | Volume | |
|---|---|---|---|---|---|---|
| Target Price: $91.7410 | 0% | 0¢ | 0¢ | — | $0 | Trade → |
This prediction market asks whether SOL (Solana) will hit the $91.7410 price target during a specific 15‑minute interval; it matters because short intraday moves can create trading opportunities and test market microstructure.
Solana is a high‑throughput smart‑contract blockchain whose token (SOL) often exhibits rapid intraday volatility driven by liquidity, large orders, network events, and news. Fifteen‑minute targets are sensitive to orderbook depth and short‑term catalysts rather than long‑term fundamentals, and past SOL behavior includes sudden spikes tied to on‑chain incidents and macro crypto headlines.
Odds on this contract represent the aggregated market view about whether SOL will meet that $91.7410 threshold in the specified 15‑minute window and will update as new information arrives; treat them as a real‑time signal, not a guarantee of outcome.
The platform defines the start and end timestamps for the 15‑minute window in the event's settlement rules; because this contract currently shows 'Closes: TBD', the precise window will be posted on the event page or official notices—check the contract details prior to trading.
Resolution will follow the data source specified in the event's rulebook (a designated exchange or consolidated oracle); consult the event's resolution/source section to see which venue or oracle is controlling settlement.
The settlement mechanics (e.g., highest trade, last trade, or quote midpoint) are defined in the event's official rules; review the contract's resolution criteria to know which metric will be used to determine whether the target was met.
Zero reported volume indicates the contract has had no executed trades so far, which often means limited liquidity and wider spreads; trading such a market can be difficult and prices may move sharply when a few orders execute, so factor execution risk into decisions.
Contingency procedures are specified in the event's resolution policy—common approaches include using a backup feed, extending the observation window, or administratively reviewing the data; check the platform's dispute and fallback rules for this contract for exact remedies.