BTC price on Jan 1, 2027
BTC price on Jan 1, 2027 is priced at 1¢ on Kalshi. Current book: 0¢ bid, 1¢ ask, 1¢ spread. This page tracks a standalone prediction-market contract.
Price history
1¢ current
Contract brief
If the simple average of the sixty seconds of CF Benchmarks' BRTI before 12 AM EST is between 20000.00-24999.99 at 12 AM EST on Jan 1, 2027, then the market resolves to Yes.
Outcome
BTC price on Jan 1, 2027
Rank
Standalone
Leader
—
Range
—
Family volume
$246K
Identifier
KXBTCY-27JAN0100-B22500
May 28, 2026, 8:09 PM UTC · 0m ago
Implied probability
Bid
0¢
Ask
1¢
Spread
1¢
24h volume
$7K
Family rank
Standalone
Standalone contract
Closes
Jan 1, 2027
Family volume
$246K
Orderbook snapshot
0 / 1¢
Contract terms
What resolves this market.
YES condition
If the simple average of the sixty seconds of CF Benchmarks' BRTI before 12 AM EST is between 20000.00-24999.99 at 12 AM EST on Jan 1, 2027, then the market resolves to Yes.
Venue
Kalshi
Closes
Jan 1, 2027
Identifier
KXBTCY-27JAN0100-B22500
Event family
This market.
The same race as a probability stack: rank, volume, and where this contract sits against the other outcomes.
Total volume
$246K
Outcomes
1
Highest price
BTC price on Jan 1, 2027 1¢
Current share
100%
BTC price on Jan 1, 2027
kalshi · KXBTCY-27JAN0100-B22500
Indicators
Yield, cliff risk, volatility, and regime.
Regime
neutral
Score
0.341
Observability
low
Event type
financial
Related readings
Matched from SimpleFunctions blog, opinions, technical guides, concepts, and learn pages.
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.
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.
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.
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.
Cross-Venue Edge Detection: Kalshi vs Polymarket
How to detect and exploit price divergences between Kalshi and Polymarket. Covers why pure arbitrage fails, cross-venue edge detection algorithms, and thesis-informed trading strategies.
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 1% 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.