BTCBTC$64,184-0.57%|
ETHETH$1,793.58-0.72%|
USDTUSDT$0.99922-0.01%|
BNB$587.9000-0.49%|
USDCUSDC$0.99959-0.01%|
XRPXRP$0.95718+0.56%|
SOLSOL$72.4400+1.36%|
TRXTRX$0.30551+0.88%|
FIGR_HELOCFIGR_HELOC$1.0390+0.00%|
HYPEHYPE$68.8700+2.26%|
ZECZEC$925.8300+3.76%|
XMRXMR$507.4000-0.64%|
DOGEDOGE$0.05858-0.03%|
LEOLEO$9.2900+1.47%|
USDSUSDS$0.99997+0.02%|
WBTWBT$61.9500-0.80%|
LINKLINK$9.1400-0.14%|
ADAADA$0.15274+0.40%|
XLMXLM$0.13745-0.24%|
USDEUSDE$0.99931-0.02%|
DAIDAI$1.0000+0.02%|
NEARNEAR$3.2100+0.76%|
BCHBCH$208.5900+1.19%|
RAINRAIN$0.00586807-22.16%|
LTCLTC$44.4900-0.29%|
CCCC$0.08040-3.87%|
AVAXAVAX$7.1600+0.75%|
UNIUNI$5.2400+1.60%|
XAUTXAUT$3,840.3-0.24%|
SUISUI$0.72321+0.27%|
BTCBTC$64,184-0.57%|
ETHETH$1,793.58-0.72%|
USDTUSDT$0.99922-0.01%|
BNBBNB$587.9000-0.49%|
USDCUSDC$0.99959-0.01%|
XRPXRP$0.95718+0.56%|
SOLSOL$72.4400+1.36%|
TRXTRX$0.30551+0.88%|
FIGR_HELOCFIGR_HELOC$1.0390+0.00%|
HYPEHYPE$68.8700+2.26%|
ZECZEC$925.8300+3.76%|
XMRXMR$507.4000-0.64%|
DOGEDOGE$0.05858-0.03%|
LEOLEO$9.2900+1.47%|
USDSUSDS$0.99997+0.02%|
WBTWBT$61.9500-0.80%|
LINKLINK$9.1400-0.14%|
ADAADA$0.15274+0.40%|
XLMXLM$0.13745-0.24%|
USDEUSDE$0.99931-0.02%|
DAIDAI$1.0000+0.02%|
NEARNEAR$3.2100+0.76%|
BCHBCH$208.5900+1.19%|
RAINRAIN$0.00586807-22.16%|
LTCLTC$44.4900-0.29%|
CCCC$0.08040-3.87%|
AVAXAVAX$7.1600+0.75%|
UNIUNI$5.2400+1.60%|
XAUTXAUT$3,840.3-0.24%|
SUISUI$0.72321+0.27%|
Hyperliquid (HIP-4 outcome contracts)
Prediction MarketTier-2On-chain CLOB with outcome contractsVerified

Hyperliquid (HIP-4 outcome contracts)

Hyperliquid's HIP-4 outcome markets: fully collateralised Yes/No contracts settled in USDC on HyperCore, sharing one margin account with perps and spot.

Visit website

Key Facts

TypeOn-chain CLOB with outcome contracts
Chain / RailHyperliquid L1 (HyperCore) — outcome tokens are native HyperCore assets alongside perps and spot
CollateralUSDC (AQAv2 quote asset); earliest canonical markets quoted in USDH before the switch
JurisdictionGlobal, but closed to the United States and Ontario, Canada, sanctioned territories, and any country the interface later designates for outcome markets
Data ConfidenceVerified

Scale Signal

About $283M cleared and ~19,000 unique traders since the May 2026 launch, including $16.2M of volume and 351,000 trades in the first week of September 2026.

Overview

HIP-4 is Hyperliquid's route into prediction markets, and it looks nothing like Polymarket or Kalshi. Rather than bolt a betting app onto the side, HIP-4 adds a new native instrument type to HyperCore — the same on-chain central limit order book that runs the exchange's perpetuals and spot markets. Outcome contracts sit in the same account, the same margin system and the same matching engine as everything else on the venue, which is the whole point: a trader who already has a Hyperliquid account can take a view on a Fed decision, a CPI print or the price of oil without opening anywhere new, transferring collateral or learning a second interface. The proposal was announced on 2 February 2026, reached testnet that week, activated on mainnet on 2 May 2026, and was co-authored by John Wang, Kalshi's head of crypto.

What an outcome contract actually is

The official specification defines outcomes as fully collateralised contracts that settle within a fixed range. In practice each market has two sides, usually Yes and No, and each side is a token that trades between $0.001 and $0.999 — so the price is the market's implied probability. Buying Yes at 62¢ costs 62¢, that is the entire amount you can lose, and there is no leverage, no funding rate and no liquidation engine anywhere in the process. At expiry the protocol applies a settleFraction: Yes tokens convert into that fraction of the quote asset and No tokens receive the remainder, which is normally 1 and 0. Hyperliquid frames outcomes as a general-purpose primitive rather than a prediction-market product — bounded, options-like instruments that settle on a date are the other intended use, and they compose with portfolio margin and the HyperEVM.

What is listed

The first market was a recurring daily Bitcoin binary that settles at 06:00 UTC against the BTC mark price on HyperCore and redeploys itself every day. On 25 May 2026 validators expanded into canonical markets on off-chain events: the June Fed rate decision, May CPI year-on-year in three buckets, NBA Finals games and the 2026 NBA champion, and a multi-outcome 2026 World Cup winner field. Recurring series now include multi-outcome price buckets — a contract that settles into below, between or above two price thresholds — and sports markets are what drove HIP-4's early growth. Since permissionless deployment opened, most new listings have moved in the opposite direction: the seven approved templates are financial, covering binary price markets, price-touch markets, scalar price markets and Fed policy-rate outcomes, so the permissionless layer is currently narrower than the canonical one.

How the book and the payout work

The Yes and No order books for the same outcome are merged so they share liquidity: an order to buy Yes at price p is the same order as selling No at 1 − p, and price-time priority generalises to price-side-time priority, with resting sells sorted ahead of resting buys at the same merged level. Yes and No prices therefore stay pinned near $1 together, and the spread between them is where arbitrage lives. Advanced users can manually split and merge outcomes to move between primary and dual balances. Where a single question has several possible answers, each answer trades on its own book but the outcomes are linked by negate and merge operations, which lets holders of No shares across the question redeem quote tokens before the underlying markets even settle.

Fees

The specification states that outcome-market fees are currently zero for initial testing, and that builder codes work exactly as they do in spot trading: a builder earns a builder fee on sell orders that specify their code. Permissionless deployers can receive up to 50% of the trading fees their markets generate. Zero is a testing-period setting rather than a promise, so treat it as the current state rather than the permanent schedule.

Who creates markets

Market creation moved in two stages. In the permissioned phase validators chose and published every market themselves, using automated newsfeed software run as part of chain operations, with on-chain validator voting governing both deployment and settlement; the stake for that route was reported at 1,000,000 HYPE. Permissionless deployment went live on mainnet on 29 August 2026 and split the job in two: validators now approve reusable templates and vote on slashing, while third-party deployers instantiate individual markets inside those templates after bonding 500,000 HYPE for at least six months — a stake that is slashable for poorly defined or incorrectly settled markets. Deployers are capped at 100 concurrent outcomes and 500 new deployments a day, with the intent to scale to 1,000 and 5,000. Canonical markets continue alongside them, and permissionless deployers may launch markets that overlap with canonical ones.

Traction

Adoption has been real but modest next to the incumbents. Privy reported $50M of volume within the first 14 days of mainnet; by day 25 Galaxy measured HIP-4 at 20.1% of combined BTC prediction-market 24-hour volume, $2.38M against Polymarket's $9.46M. Third-party trackers put cumulative volume at roughly $283M with close to 19,000 unique traders by mid-September, and the first week of September alone saw $16.2M of volume across 351,000 trades — a visible step up after the World Cup markets and again after permissionless launch. By early September, close to 1,000 individual outcome markets were live across canonical and permissionless deployments combined.

What to check before you trade

  • Where you are. The US and Ontario are blocked at the interface, and outcome markets are additionally closed to designated "Excluded Persons"; disguising your location is prohibited by the terms and enforced technically.
  • Fees are in testing mode. Zero protocol fees today, with builder fees possible on top — not a permanent fee schedule.
  • Permissionless markets are unreviewed. Hyperliquid states that markets created through permissionless deployment are surfaced from on-chain activity and are not reviewed, verified or approved by the company.
  • Resolution is the risk. Price markets settle mechanically, but event markets depend on a resolution source, and the terms explicitly disclaim liability for disputed settlement or payout.
  • Zero is a real outcome. A Yes bought at 62¢ can be worth nothing, and the terms describe outcome trading as a risk of immediate and total loss with illiquidity.

Regulatory Status

Not licensed, approved or registered by any regulator. The interface is run by Hyperliquid Corp, which states it does not own, control or operate the Hyperliquid chain and does not review, verify or approve markets created through permissionless deployment. Use of the interface is barred for people resident in, located in, incorporated in or with a registered office in the US or Ontario, Canada, plus sanctioned or export-controlled jurisdictions and citizens of those territories. Outcome markets are further closed to 'Excluded Persons' — jurisdictions designated from time to time — with technical blocks on the outcomes tab and an explicit ban on circumventing them. Users must not disguise their location and are solely responsible for whether derivative or outcome trading is lawful for them.

Features & Market Details

The primitive, not the product

HIP-4 is deliberately written as infrastructure. The specification describes outcomes as fully collateralised contracts that settle within a fixed range, useful for prediction markets and for bounded, options-like instruments, and notes what they add to HyperCore: non-linearity, dated contracts, and a form of derivative exposure that involves neither leverage nor liquidations. That framing matters because it means everything else on the chain can reach them — they share the margin account with perps and spot and compose with portfolio margin and the HyperEVM, so an outcome position can hedge a directional one in the same collateral without a transfer to a second venue. Hedging discontinuous risk — a Fed decision, a CPI print — is the textbook use case the design points at.

How the contract behaves

Each market has two sides, each with its own token, labelled by the sideSpecs field of the outcome metadata and usually just Yes and No. Prices run from $0.001 to $0.999 and read directly as implied probability: a Yes mid of 0.47 is a 47% chance, and a No mid of 0.53 is the same event priced from the other side, with the small gaps between them reflecting spreads and short-lived arbitrage. Everything is paid upfront — a Yes token bought at 0.62 costs 0.62 and can never trigger a margin call, because the maximum loss is the position itself. Because the sides are native HyperCore assets rather than wrapped ERC-20 tokens, the existing order, cancel and WebSocket tooling works with only minor encoding changes, and each side carries a #N coin identifier in API responses and market-data streams.

The merged book

Yes and No order books for the same outcome are merged so the two sides share one pool of liquidity: buying Yes at price p is equivalent to selling No at 1 − p, and time priority generalises to price-side-time priority, with resting sell orders sorted ahead of resting buy dual orders at the same merged price level. The result is that the pair stays anchored around $1 rather than drifting apart as two thin independent books. Advanced users can manually split and merge outcomes to convert between primary and dual balances; most operations hide that machinery, but a few edge cases — such as an order that both matches and rests, where historical order queries can return primary and dual orders separately — are still on the list to smooth out in a future network upgrade.

Settlement, and the recurring BTC series

At settlement the protocol converts Yes tokens into settleFraction of the quote asset and No tokens into the remainder, so a binary market settles to 1 and 0. Price-based markets use the mark price on HyperCore and, importantly, do not read a single print at the settlement timestamp: the target is a linear interpolation between the mark-price updates immediately before and after settlement, so a market settles Yes only if the interpolated price at the exact settlement time clears the target. That interpolation is a real defence against a stale or spiked tick deciding a market, and it is the kind of detail worth understanding before assuming a wick settled an outcome.

The recurring series is deployed and settled by the protocol on a fixed cadence rather than by a person. The first was a daily BTC binary settling at 06:00 UTC, described on-chain as class:priceBinary|underlying:BTC|expiry:20260503-0600|targetPrice:78213|period:1d, with multi-price bucket series following — class:priceBucket with two thresholds, settling into below, between and above, where exactly one of the three outcomes settles to 1. The protocol guarantees at most one recurring series per combination of series type, underlying and period.

Questions and multi-outcome markets

A question is a collection of outcomes where exactly one settles to Yes and all the others settle to No. Each outcome keeps its own order book, but the outcomes are linked by negate and merge operations, and the practical benefit is early liquidity: a user holding No shares across several outcomes of the same question can redeem quote tokens before the underlying markets resolve. Multi-outcome structures arrived within days of mainnet as price buckets, validators expanded them to fields such as the 2026 World Cup winner and Fed policy outcomes, and the permissionless policy-rate templates are designed to be combined into multi-outcome questions rather than launched alone.

Fees, builder codes and deployer economics

Outcome markets currently charge no protocol fee while the system is in initial testing. Builder codes work as they do elsewhere on Hyperliquid: builders earn a builder fee on sell orders that specify their code, so a front-end can monetise flow without touching the matching logic. On the deployment side, permissionless deployers can receive up to 50% of the trading fees their markets generate, which is the economic reason to lock a 500,000 HYPE bond. Because the zero-fee setting is explicitly attached to the testing window, the fee line on any HIP-4 market is worth re-checking before you size a trade.

Becoming a deployer

Permissionless deployment is permissionless in structure only. A deployer stakes 500,000 HYPE — tens of millions of dollars at recent prices — for at least six months on mainnet, or 100 HYPE on testnet, and activates through activateOutcomeDeployer. That single bond secures every market the deployer runs, so the fixed cost can be spread across a catalogue rather than paid per listing, and the same stake cannot double as an existing HIP-3 perpetual deployment. Markets must fit a template approved by validator vote; a structure that does not fit an existing template has to get one approved first. Live mainnet templates at launch were seven: binaryPrice, priceTouch, scalarPrice, policyRateDecision, policyRateIncrease, policyRateDecrease and policyRateNoChange. Deployment limits at launch were 100 concurrent outcomes per deployer and up to 500 new outcomes a day, with slots freeing as outcomes settle and an stated intention to scale to 1,000 concurrent and 5,000 daily. Deployers set the question, the settlement date and the outcome criteria allowed by the template, and they are responsible for settling what they deploy — which is precisely where the bond can be slashed.

Who is deploying today

Outcome was the first permissionless deployer, opening 28 markets across crypto, stocks, indices, commodities and economic events — BTC, HYPE, the S&P 500, Nasdaq, gold, silver, WTI and the September Fed decision — alongside a $1M liquidity programme paying $50K in USDC a week across eligible markets, which is not available to US users. Skew followed with support from the Nasdaq-listed Hyperion DeFi, which supplied its 500,000 HYPE stake in exchange for a share of fees, beginning with an hourly BTC up/down market before widening out. Overlap with canonical markets is explicitly allowed, so the same question can trade in several places at once — useful for comparing liquidity, and a reason to check which book you are actually looking at before you trade.

Resolution, and where it can go wrong

Canonical markets are deployed and settled by the validator set, which ingests outside information through automated newsfeed software run as part of chain operations and votes on outcomes on-chain; Hyperliquid has said validators should ideally publish fewer than ten canonical markets each, given that their real job is now governing templates and slashing. Permissionless markets resolve in one of two ways: price-threshold markets settle mechanically from the interpolated mark price, while event markets depend on the deployer's authorised oracle or another resolution source that submits the result on-chain. That is a fast, self-contained model with no external resolution layer and no third-party vote — and it concentrates judgment into a bonded deployer whose money is at risk if a market is poorly worded or wrongly settled. The interface terms state plainly that markets created through permissionless deployment are not reviewed, verified or approved by Hyperliquid Corp, and disclaim liability for disputed settlement or payout.

Scale: the venue versus the primitive

HIP-4's numbers and Hyperliquid's numbers are different orders of magnitude, and it is worth keeping them apart. The exchange itself runs about $8.5B of 24-hour volume and $16.3B of open interest across roughly 2.7M users, with throughput measured around 200,000 orders per second. The outcome primitive on top of it cleared roughly $283M cumulatively between May and mid-September 2026, with about 19,000 unique traders, a $16.2M week in early September, and close to 1,000 live markets by that point. Against the wider sector — combined prediction-market lifetime volume passed $150B in April 2026, and CoinGecko put Q2 2026 notional across the category at $113.8B — HIP-4 is a fast-growing challenger with a small base, not yet a volume leader. Its structural advantage is the venue it sits on: sub-second finality, deep matching infrastructure and one margin account, which neither a consumer prediction app nor a regulated exchange can replicate without a rebuild.

Limitations

  • The interface blocks the US and Ontario, and outcome markets are closed to additional designated jurisdictions; disguising your location to get around that is prohibited by the terms and enforced with technical blocks.
  • Neither the interface nor the chain is licensed, approved or registered with any regulator, and users carry sole responsibility for whether outcome trading is lawful where they are.
  • Zero fees apply during an initial testing window and can change; builder and deployer fees can be layered on top of whatever the protocol charges.
  • Permissionless markets are unreviewed by Hyperliquid Corp, which disclaims liability for anything that goes wrong with them.
  • Event markets depend on the deployer's resolution source, so a badly worded question is a settlement risk rather than a trading risk you can hedge.
  • Positions are binary and can go to zero, and the terms describe outcome trading as carrying a risk of immediate and total loss and illiquidity.
  • Permissionless deployment is expensive: 500,000 HYPE locked for six months and slashable, and the currently approved templates cover financial markets rather than the sports and culture markets that drove early volume.
  • Overlapping markets are allowed, so the same question can trade across several books with different liquidity and spreads.
  • Outcome markets are not available through every front end or venue region, and liquidity in newly deployed markets is thin and dependent on the deployer's incentives.

Bitnxt uses cookies to run the site, understand how it is used, and measure ads. You can accept or decline below, and change your choice any time in our Privacy Policy.