
Introducing Hyperodds, a trading terminal for outcome markets on @HyperliquidX.
We're bringing matching order books across deployers into one console, with fair price estimates and trading costs shown before you sign with your own wallet.
Hyperodds.
Two trading venues, with your own wallets signing
The planned trading routes are Hyperliquid and Polymarket.
7
Edge means the price you can actually obtain
A displayed reference probability and an available execution price are different observations.
3
A fair line with sources, age and confidence
The fair line is our proposed reference estimate for a market's probability.
3
Contract grades that explain the fine print
Our matching design compares resolution sources, cut off times, thresholds and void rules across HIP-4, Polymarket and Kalshi.
Inside HyperOdds’s proposed design:
We are designing the merged book around a simple experience: when multiple deployers offer the same contract, the trader should be able to review their combined available liquidity.
4
HyperOdds is being built around this decision:
The trader still needs settlement equivalence and a view of partial execution, especially when a plan spans separate venues.
7
The problem: similar questions, scattered liquidity
An outcome market turns a specified event into tradable positions.
3
HyperOdds is a trading terminal we are building for outcome markets, with Hyperliquid at its core.
The goal is to bring scattered markets, comparable contract rules, reference probabilities and execution decisions into one place.
5
What a Better Outcome Quote Still Needs Before It Becomes a Trade
HyperOdds is building an outcome-market terminal with contract comparison, reference context and execution depth.
7
Compare the settlement text before calling the prices different opinions.
HyperOdds' proposed contract view needs the source and timing in focus. Similar headlines can describe different outcomes.
8
The Outcome Trading Terminal We’re Building
Our design starts with HIP-4 markets across Hyperliquid deployers.
4
Inside HyperOdds’s proposed design:
A screen full of probabilities is only useful when the person reading it can connect each number to an actual contract and a realistic trading decision.
1
1
The Outcome Trading Terminal We’re Building
A trader should be able to understand what a market means, what price is available for their order size, and what happens after they sign.
1
The Outcome Trading Terminal We’re Building
The goal is to bring scattered markets, comparable contract rules, reference probabilities and execution decisions into one place.
1
Inside HyperOdds’s proposed design:
The distinction between a reference estimate and an executable order matters throughout the process, especially when a plan depends on fills at more than one venue.
1
The decision before the feature list
HyperOdds proposes a terminal that brings those observations together across outcome markets.
1
3
The decision before the feature list
Before acting, the relevant question changes from the number to the contract, available size and route.
1
A concrete decision before the mechanism
HyperOdds’ proposed terminal is most useful when the reference line adds context without replacing those decisions or promising that separate venue orders will fill together.
1
A concrete decision before the mechanism
The trader still needs to compare settlement rules, available depth and the actual execution route.
1
3










