HIP-4 Is Live on Mainnet: Prediction Markets Just Joined Hyperliquid's Trading Stack
Hyperliquid activated HIP-4 Outcome Markets on mainnet on May 2, 2026, with the first market being a daily BTC price prediction by Outcomexyz. Here is what HIP-4 actually is, why it lives on the same account interface as perps, and what it changes for traders running orderflow strategies.
$ Stop reading delayed data. Compare live order book depth across 5 exchanges right now.
Launch Free Terminal →Hyperliquid activated HIP-4 Outcome Markets on mainnet on May 2, 2026. The launch was understated. There was no token launch, no airdrop, no fanfare beyond a Discord post and a quiet update to the docs. The first live market is a daily BTC closing price prediction operated by Outcomexyz. Within 72 hours of going live, daily resolution markets had attracted roughly $4 million in collateral across the early outcome contracts.
Most traders glanced at HIP-4 and assumed it was Hyperliquid trying to compete with Polymarket. That framing is technically correct and analytically wrong. HIP-4 is not a separate venue grafted onto Hyperliquid. It is a contract type that lives on the same account, settles in the same USDC margin, and shares the same orderflow infrastructure as the perpetual futures and spot markets that already trade on the platform. That structural detail is what changes the calculus for traders, and it is the reason this matters more than the launch size suggests.
Here is what HIP-4 actually is, in concrete terms.
A HIP-4 market is a fully collateralized contract that pays out based on a binary or scalar outcome at a defined expiry. The first BTC daily market is binary, asking whether BTC closes above or below a strike at 00:00 UTC each day. Buyers of yes pay a price between 0 and 1 USDC, with the resolution returning either 1 USDC (if the outcome is yes) or 0 USDC (if no). The price between launch and resolution moves with the perceived probability of the outcome. This is the same mechanic that powers Polymarket and Kalshi, with one critical difference. The collateral, the margin, the trading interface, and the order book all live inside the same Hyperliquid account that holds your perpetual positions.
Why this matters operationally for a trader. Polymarket runs on Polygon, requires a separate wallet bridge, and has its own liquidity profile that does not interact with crypto perps. Kalshi requires a US bank account and fiat KYC. HIP-4 lets a trader who already has USDC margin on Hyperliquid open a prediction market position alongside their existing BTC perp position without bridging, without onboarding to a separate platform, and without losing the netting benefit of holding correlated exposures in the same account.
The strategic implications run a few layers deeper.
First, prediction markets are a clean way to express conviction on macro or event-driven catalysts that are difficult to size in pure perp positioning. A trader who believes BTC will close above $80,000 today can buy a yes contract at, say, 0.62 USDC and either resolve at 1 USDC for a 60 percent return on capital, or sell out partway through the session at a higher mid-price as confidence rises. The leverage characteristics are bounded and known in advance, which is the opposite of the unbounded liquidation risk that defines perp positions.
Second, prediction market prices feed back into the orderflow data. The implied probability of a HIP-4 market is observable, and over time it becomes another input that orderflow systems can read. If the BTC daily HIP-4 is pricing 0.78 yes for a close above the current spot level, that is a piece of crowd-sourced macro positioning data that conventional CVD, OBI, and funding rate inputs do not capture. We are watching how this layer behaves and will likely surface HIP-4 implied probabilities inside the Buildix deep view as the data depth allows.
Third, HIP-4 sits structurally close to HIP-3, which is the proposal that introduced builder-deployed perpetuals and brought tokenized stocks, oil, gold, and the S&P 500 to Hyperliquid. HIP-3 has crossed roughly $2.3 billion in real-world asset open interest, with trade.xyz alone representing more than 90 percent of HIP-3 volume. HIP-4 is the second major builder-deployed product type on the same trading platform, and the early sign is that it follows the same trajectory. Outcomexyz is to HIP-4 what trade.xyz is to HIP-3. A specialized builder using a generalized infrastructure to ship a product that previously required its own venue.
The bigger picture is that Hyperliquid is positioning itself as a general-purpose financial primitive layer rather than a single-product DEX. Perpetual futures are the original product. HIP-3 added commodities, equities, and FX. HIP-4 added expiring outcome contracts. The shared infrastructure is the orderbook, the matching engine, the margin system, and the network of integrated wallets and bots. Each new product type lowers the marginal cost of being on the platform for both builders and traders.
What HIP-4 does not do, at least not yet. The early markets are limited in scope. The Outcomexyz BTC daily market is the headline live market, with a small number of secondary markets in the pipeline. Compared to Polymarket, which has hundreds of active markets across sports, politics, and macro events, HIP-4 has a coverage gap that will take months to close. The price discovery and liquidity profile is also still developing, with bid-ask spreads on resolution markets meaningfully wider than on the more mature BTC perp.
Resolution risk is also worth flagging. HIP-4 markets are settled by oracles defined per market. The Outcomexyz BTC daily market uses a price feed from a defined source at the resolution time. If the oracle disagrees with what a trader sees on their own chart, there is no manual override, the on-chain oracle wins. This is consistent with how Polymarket and Kalshi resolve markets, but it is worth understanding before you take a position.
For traders running orderflow strategies on Buildix, the immediate impact is small but worth tracking. We are not yet computing HIP-4 implied probability as a Signal Engine V5 component, because the data depth is too shallow to test against. Once HIP-4 has roughly six to eight weeks of resolution history, we will likely add an implied probability layer that traders can use as an additional filter on directional setups. In the meantime, the Hyperliquid screener and deep view continue to cover the perps and the HIP-3 builder pairs in real time, and Hyperliquid remains supported from day one, which still distinguishes Buildix from most analytics platforms in this space.
A practical observation. The traders most likely to benefit from HIP-4 in the short term are those running event-driven strategies who already use prediction markets to express macro views and want to consolidate their stack. If you are running a daily BTC directional bias and currently expressing it through both a Hyperliquid perp and a Polymarket position, HIP-4 lets you collapse those into a single account with a single margin pool. The capital efficiency gain is real, even if the markets are still limited.
The longer-term observation is harder to validate yet. If HIP-4 follows the HIP-3 trajectory, where a builder ecosystem grows around the product type and pulls liquidity from the existing dedicated venues, Hyperliquid becomes a venue where a trader can hold perps, builder-deployed RWA perps, and prediction market contracts all in one place. That is structurally different from the current crypto trading landscape, where traders typically run several disconnected accounts to do the same thing. Whether HIP-4 reaches that scale is an open question. It is now possible to track the answer.
Buildix is freemium, and the free screener covers Hyperliquid alongside Binance, Bybit, OKX, and dYdX. The integrated AI Strategy Advisor with BYOK across OpenAI, Anthropic, Google, Groq, Mistral, and Ollama can interpret HIP-3 RWA pair data and Hyperliquid funding rates in plain language. Sign up at buildix.trade to watch the HIP-4 early markets resolve and the data depth build over the coming weeks. The orderflow implications will surface in the V5 engine when the data justifies it.