It be reported by any of the Source Agencies that the operational deployment in Earth orbit of a data center delivering at least 1 megawatt of electrical power to compute hardware on a single spacecraft or a unified co-orbital cluster operating as one compute system, actively processing workloads before Jan 1, 2035
Before Jan 1, 2035 is priced at 32¢ on Kalshi. Current book: 31¢ bid, 32¢ ask, 1¢ spread. This outcome ranks #1 of 6 inside Will it be reported by any of the Source Agencies that the operational deployment in Earth orbit of a data center delivering at least 1 megawatt of electrical power to compute hardware on a single spacecraft or a unified co-orbital cluster operating as one compute system, actively processing workloads before Jan 1, 20.
Price history
32¢ current
+7¢Contract brief
If the operational deployment in Earth orbit of a data center delivering at least 1 megawatt of electrical power to compute hardware on a single spacecraft or a unified co-orbital cluster operating as one compute system, actively processing workloads after Issuance and before Jan 1, 2035, then the market resolves to Yes.
Outcome
Before Jan 1, 2035
Rank
#1 of 6
Leader
Before Jan 1, 2035 31¢
Range
6¢-31¢
Family volume
$19K
Identifier
KXSPACEDATACENTER-26-35JAN01
May 28, 2026, 5:38 PM UTC · 30m ago
Implied probability
Bid
31¢
Ask
32¢
Spread
1¢
24h volume
$4K
Family rank
#1 of 6
6 outcomes · Will it be reported by any of the Source Agencies that the operational deployment in Earth orbit of a data center delivering at least 1 megawatt of electrical power to compute hardware on a single spacecraft or a unified co-orbital cluster operating as one compute system, actively processing workloads before Jan 1, 20
Closes
Jan 1, 2035
Family volume
$19K
Orderbook snapshot
31 / 32¢
Contract terms
What resolves this market.
YES condition
If the operational deployment in Earth orbit of a data center delivering at least 1 megawatt of electrical power to compute hardware on a single spacecraft or a unified co-orbital cluster operating as one compute system, actively processing workloads after Issuance and before Jan 1, 2035, then the market resolves to Yes.
Venue
Kalshi
Closes
Jan 1, 2035
Identifier
KXSPACEDATACENTER-26-35JAN01
Event family
Will it be reported by any of the Source Agencies that the operational deployment in Earth orbit of a data center delivering at least 1 megawatt of electrical power to compute hardware on a single spacecraft or a unified co-orbital cluster operating as one compute system, actively processing workloads before Jan 1, 20.
The same race as a probability stack: rank, volume, and where this contract sits against the other outcomes.
Total volume
$19K
Outcomes
6
Highest price
Before Jan 1, 2035 31¢
Current share
22%
Before Jan 1, 2035
kalshi · KXSPACEDATACENTER-26-35JAN01
Before Jan 1, 2033
kalshi · KXSPACEDATACENTER-26-33JAN01
Before Jan 1, 2031
kalshi · KXSPACEDATACENTER-26-31JAN01
Before Jan 1, 2030
kalshi · KXSPACEDATACENTER-26-30JAN01
Before Jan 1, 2029
kalshi · KXSPACEDATACENTER-26-29JAN01
Before Jan 1, 2028
kalshi · KXSPACEDATACENTER-26-28JAN01
Indicators
Yield, cliff risk, volatility, and regime.
Regime
neutral
Score
0.5
Full indicator table
Odds pages
Related prediction questions
Related readings
Matched from SimpleFunctions blog, opinions, technical guides, concepts, and learn pages.
MCP Servers for Prediction Markets: Connect Claude Code to Kalshi and Polymarket
Connect Claude Code, Cursor, or Cline to Kalshi and Polymarket prediction markets via MCP. One-line setup, 18 tools, real-time market data for AI agents.
Maker / Taker Regime in Prediction Markets: How to Read the Orderbook State
Three regime states (maker-dominated, taker-dominated, neutral) and how to read which one a Kalshi or Polymarket contract is in. Strategy follows regime, not thesis.
Kalshi vs Polymarket: Which Prediction Market Should You Trade?
In-depth comparison of Kalshi and Polymarket for prediction market traders. Regulatory structure, liquidity, fees, API tooling, and cross-venue trading with SimpleFunctions.
Prediction Market Orderbook Analysis: Reading Depth, Spread, and Liquidity
How to read prediction market orderbooks. Binary settlement, spread-as-percentage, depth asymmetry, executable edge calculation, and cross-venue arbitrage analysis.
Kalshi vs Polymarket: A Developer's Comparison of APIs, Orderbooks, and Liquidity
Data-driven comparison of Kalshi and Polymarket APIs, orderbooks, rate limits, and liquidity. Code examples for building on both prediction markets.
Liquidity Availability Is the Real Edge in Prediction Markets
Implied yield, cliff risk, and overround all describe what to trade. Liquidity Availability Score describes whether the orderbook can absorb the trade. Why LAS is the indicator that decides who actually books P&L.
SimpleFunctions context
Index, screen, query, and monitor.
Prediction Market Index
Market-wide volatility, geo risk, breadth, and activity around this contract.
Market Screener
Filter adjacent contracts by volume, expiry, IY, CRI, venue, and theme.
Event Probability API
Read 32% as a structured event probability object for agents and apps.
Realtime Data API
Prices, orderbooks, movement, heat, and liquidity indicators across venues.
World State API
Compact market-aware context packets for agent sessions and scheduled refresh.
Hedging Workflows
Map a thesis or exposure to candidate event markets and monitoring paths.
How we compute these odds
SimpleFunctions aggregates live prediction-market contracts from Kalshi and Polymarket. Each slug groups contracts that resolve on the same underlying event, identified by venue event_id.
For binary slugs, the headline probability is the liquidity-weighted mid-price across all bound contracts. For multi-outcome slugs (e.g. elections with 3+ candidates), the headline is the leader’s price; we never arithmetically average disjoint outcomes — that would produce a number with no real-world meaning.
Snapshots refresh every 5 minutes during market hours; daily aggregates are computed at 04:00 UTC. The 30-day sparkline is drawn from per-ticker daily means stored in market_indicator_daily; 24h delta and movement events are derived from the same source.