A $100 million betting market prices oil like the CME options floor?

Part 1 of an ongoing series.

·series

This is the first post of a longer series on a project comparing prediction markets and traditional markets, and looking at exploitation opportunities. This post will map out the terrain: venues, contracts, why naive comparisons fail, and an important finding that recalibrated the project. This project required some collaboration with relevant industry experts (which will be referenced in later posts).

This past Spring, while the Strait of Hormuz was the most dangerous shipping lane on earth, two very different groups of people were pricing the same question. On one side: the CME crude options complex - the professional venue backed by half a century of market infrastructure, and hundreds of listed strikes per expiry. On the other: pseudonymous accounts on a crypto betting site, wagering on questions such as "will WTI hit $110 in May?" at prices that read directly as probabilities.

The premise of the project is simple: when two venues price the same event under different mechanics, clienteles, and constraints, the difference between them is information - about risk premia, behavioural bias, market structure, and occasionally money left on the table. First we need to establish an accurate comparison - which is what this first post details.

Three objects, one name

Of course, the 'price of oil' is not just one number - WTI crude trades as three legally and mechanically distinct objects.

The three objects called 'the price of oil'
The three objects called 'the price of oil'

Three details are immediately important:

Where naive comparisons fail

The library

The engineering discipline behind those principles is the product thus far - a tested library where every pricing path is cross-checked against closed forms and Monte Carlo by an independent adversarial pass (473 automated tests, running on 15 million rows of minute-level quotes, settlement prints, and oracle candles archived from free but perishable sources). Two of the used datasets are actually deleted on a schedule (this will be the object of a future post looking into perishable data and reverse-engineering).

Three months of live data

Looking at the three months of live data, the headline is relatively clear - the crowd does not seem to be wrong.

Three months of live data: venue agreement at the aggregate level
Three months of live data: venue agreement at the aggregate level

Agreement here, however, does not suggest that the two worlds are the same market. The June 2025 war made the distinction vivid, with Polymarket running liquid markets on "US military action against Iran before July"; oil ran its own referendum on the same events. Inverting the option-implied distribution through an event-mixture model lets you ask what escalation probability the oil market was pricing. The answer diverged from the event contracts in both directions at different times, with oil moving a day earlier on the initial escalation. Then, after the US strike, the event contract resolved YES at 1.0 while oil unwound its entire war premium in two sessions, because the realized strike did not disrupt supply. Both were 'right' but they priced different objects - a named and straightforward indicator versus a supply-disruption bundle. Scoring one against the other would be a category error.

June 2025: option-implied escalation probability against the event contract
June 2025: option-implied escalation probability against the event contract

What the agreement does not show

A clean null at the aggregate level is certainly not the end of the story, but instead is the beginning of a more interesting one. Underneath the zero mean, the disagreement between the venues has a real structure, varying systematically with moneyness, time to resolution, and contract type. Where structure looks persistent, I have pre-registered hypotheses and am tracking them against live resolutions (rather than positions). The anatomy of that structure is another interesting thread to explore in a future post.

What's next

My next post on this will likely be looking at the free per-strike volatility data hiding in CME's public settlement files, and how its undocumented convention can be reverse engineered for valuable and typically expensive data. This will be accompanied by a deeper dive into data that perishes on a schedule. Further forwards, I would also like to analyse what changes to structure under agreement occur during a non-war period.