Skip to content

Outcome - Prediction Markets On Hyperliquid's Exchange Layer

Jun 9, 20263 min

Outcome is a non-custodial front end for Hyperliquid's HIP-4 event-contract system, where YES and NO tokens trade inside the same account a trader already uses for perps and spot on Hyperliquid’s native exchange.

Outcome V2 is live with zero fees while HIP-4 remains in testing.

In this edition, we look at how the product works, what changes when event risk shares the exchange layer, and what the USDH transition means.

How Outcome’s Event Contracts Work

Outcome is a live prediction-market interface built on HIP-4, Hyperliquid’s onchain event-contract primitive where builders stake HYPE to deploy binary markets that settle to 0 or 1 USDH. Outcome targets traders who already hold collateral on Hyperliquid and want event exposure alongside perp positions.

A trader buys YES or NO tokens representing a possible outcome; exactly one side pays 1 USDH at resolution, which keeps the combined value of both sides close to 1 USDH throughout the market’s life. A YES token priced at 0.40 USDH reads as the market pricing that event at roughly 40% probability.

Trading on Outcome requires adding Outcome’s builder code, a Hyperliquid account-level setting that authorizes the interface to route trades and collect a fee on top of standard Hyperliquid fees. The builder fee is currently zero. Builder codes allow any front end on HyperCore to register a builder address, charge a fee for routing trades, and draw from the same underlying liquidity pool as every other builder on the network.

HIP-4 combines YES and NO orders into a single shared order book, where liquidity from both sides interacts simultaneously under price-side-time priority. A merged structure gives any new outcome market immediate access to the full depth of both YES and NO order flow combined.

Hyperliquid’s 1.4M active traders solve a cold start problem that standalone prediction platforms cannot replicate.

HIP-4's Two-Tier Settlement Model

Settlement runs differently depending on where the resolution data comes from. For exchange-native price events, HyperCore reads the relevant mark price directly at the resolution timestamp, automatically redeems the winning side, and cancels open orders without any step to claim. The data is deterministic, which removes the dispute surface that external oracle systems carry.

Hyperliquid expanded HIP-4 to support offchain macro events including US inflation data and Fed decisions, with validators taking responsibility for both market deployment and settlement.

Validators run automated newsfeed software as part of regular chain operations, ingest the relevant data, and vote on resolution rather than delegating to a third-party oracle like UMA. That model removes the external adjudication dependency, but validator-based settlement on contested or ambiguous outcomes has no live track record yet.

Phase 2 and What Permissionless Deployment Opens

HIP-4 launched in a curated Phase 1 where the Hyperliquid team selects which markets go live. Phase 2 opens permissionless deployment: any builder meeting the 1M HYPE staking requirement can deploy outcome markets. That stake is slashable and burned if the builder violates market rules, which prices manipulation economically rather than relying on curation.

The trajectory mirrors HIP-3, which opened perpetual futures to permissionless deployment and where external builders now account for a significant share of Hyperliquid’s total volume. Once Phase 2 opens, any builder can stake 1M HYPE, register a builder code, deploy a market on any event, and capture a routing fee through their own interface without Hyperliquid’s approval. Outcome’s infrastructure is ready to deploy once this goes live.

The live settlement currency is USDH. Coinbase announced on May 14, 2026 that it is becoming the official USDC treasury deployer on Hyperliquid, has acquired the right to purchase USDH brand assets from Native Markets, and expects USDH markets to sunset over time. Markets eventually shift to USDC settlement in the near future.

Important Links