SimpleFunctions

Francesca Hong receive at least 35% of the popular vote in the 2026 Wisconsin Democratic gubernatorial primary

At least 35% is priced at 98¢ on Kalshi. Current book: 96¢ bid, 99¢ ask, 3¢ spread. This outcome ranks #3 of 8 inside Will Francesca Hong receive at least.

Price history

98¢ current

+29¢
75¢100¢
Jul 20, 2026Aug 6, 2026

Contract brief

If the certified percentage of the popular vote received by Francesca Hong in the 2026 Wisconsin Democratic gubernatorial primary is 35% to 100%, inclusive of both endpoints, then the market resolves to Yes.

Outcome

At least 35%

Rank

#3 of 8

Leader

At least 20% 99¢

Range

20¢-99¢

Family volume

$947

Identifier

KXVOTEPRIMARY-GOVWINOMD26FHONFHON-67

Aug 7, 2026, 3:08 AM UTC · 10m ago

Implied probability

98¢
Latest venue quote
Aug 7, 2026, 3:08 AM UTC · 10m ago

Bid

96¢

Ask

99¢

Spread

Reported volume

$8K

Family rank

#3 of 8

8 outcomes · Will Francesca Hong receive at least

Closes

Aug 11, 2027

Family volume

$947

Orderbook snapshot

96 / 99¢

Kalshi
3¢ spread
BidSize
96¢500
95¢787
92¢525
91¢550
90¢30
AskSize
99¢2.4K

Contract terms

What resolves this market.

YES condition

If the certified percentage of the popular vote received by Francesca Hong in the 2026 Wisconsin Democratic gubernatorial primary is 35% to 100%, inclusive of both endpoints, then the market resolves to Yes.

Venue

Kalshi

Closes

Aug 11, 2027

Identifier

KXVOTEPRIMARY-GOVWINOMD26FHONFHON-67

SF Signal
SF Index
1148.43
Regime
taker

Indicators

Yield, cliff risk, volatility, and regime.

IY (Yes)

4.1%

IY (No)

2371.1%

Adj IY

1148%

CRI

24

Overround

3.1%

LAS

0.03

Regime

taker

Score

0.636

Observability

direct

Event type

political

Full indicator table

4.1%
2371.1%
Adj IY
1148%
24
Overround
3.1%
LAS
0.03

Related readings

Matched from SimpleFunctions blog, opinions, technical guides, concepts, and learn pages.

Browse library
Technicalguide

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.

Blogmarkets

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.

Opinioncomparison

Kalshi vs Polymarket: Mechanics, Fees, Regulation, Liquidity (2026)

Side-by-side comparison of Kalshi and Polymarket in 2026. Fee math, calibration data, withdrawal speed, and a decision tree for picking the right venue.

Blogmarkets

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.

Opinionanalysis

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.

Opinionanalysis

Implied Yield vs Raw Probability: Why Bond-Adjacent Prediction Markets Need a Different Lens

Why fixed-income-adjacent prediction-market contracts need to be priced in implied yield, not raw probability, with two real Kalshi Fed-decision contracts as a case study.

SimpleFunctions context

Index, screen, query, and monitor.

Open index

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.