What Is Hyperliquid HIP-3? Builder-Deployed Perp Markets Explained

HIP-3 is the upgrade that turned Hyperliquid from an exchange into a market factory. Activated on mainnet on October 13, 2025, it lets independent teams — not Hyperliquid itself — deploy and run their own perpetual futures markets on Hyperliquid's order book and clearing infrastructure. The result has been an explosion of non-crypto markets: by mid-2026, builder-deployed markets accounted for more than a third of all Hyperliquid trading volume, and 23 of the top 30 assets by open interest were commodities and equities rather than cryptocurrencies.

This guide explains what HIP-3 actually is, how a builder deploys a market (and the 500K-HYPE bond that keeps them honest), how fees are split, what has been deployed so far, and the risks the model introduces. It also clears up the single most common confusion in this corner of Hyperliquid — HIP-3 is not the same thing as builder codes — which has its own guide. No hype, the sharp edges stated plainly.

Published June 14, 2026. Last updated June 14, 2026.

What HIP-3 is: permissionless market deployment

On a centralized exchange, a small team decides which contracts exist; listing a new market is a private, gatekept decision. HIP-3 inverts that. It is a permissionless framework: any qualifying builder can define a new perpetual market — choosing the underlying, the oracle that prices it, the collateral it accepts, and its risk limits — and deploy it onto Hyperliquid's shared infrastructure, where it trades on the same on-chain order book as the core markets. Hyperliquid provides the rails; the builder defines the market.

That is why markets nobody expected on a crypto venue — gold, silver, Tesla, the S&P 500, pre-IPO names like SpaceX — now live on Hyperliquid. They were deployed by builders filling demand the exchange would never have prioritized on its own.

How a builder deploys a market: the 500K HYPE bond

Deployment is permissionless but not free or anonymous. A builder must stake at least 500,000 HYPE — on the order of $25 million at recent prices — which acts as a security bond. If the deployer behaves maliciously or negligently (a faulty oracle, mismanaged risk limits), Hyperliquid's validators can slash a portion of that stake. The bond aligns the deployer's incentives with the market's integrity: run it badly and it costs you directly.

Once staked, a deployer can launch its first three markets for free; additional market slots are allocated through an auction where deployers bid for them. The deployer is then responsible for the market's ongoing design — most importantly the oracle, since in many of these markets (pre-IPO names especially) the oracle is the only thing anchoring price to reality.

How fees and incentives work

HIP-3 markets split trading fees 50/50 between the deployer and the Hyperliquid protocol. The deployer earns half the fees its market generates as the return on its staked bond and its work running the market; the protocol earns the other half, which flows back into the Hyperliquid ecosystem. The design grows the total pie rather than cannibalizing core markets — a new gold or Tesla market brings volume and fees that simply did not exist on the venue before.

This is a different mechanism from builder codes, and the two are constantly conflated. The HIP-3 fee split is about who deployed and runs the market. Builder codes are about which app routed a given order. A trade can involve both — and the next section, plus the dedicated builder-codes guide, keeps them straight.

HIP-3 vs builder codes — not the same thing

HIP-3 is about market creation: staking HYPE to deploy and operate a perp market. Builder codes are about order attribution: an app attaching its identifier to an order it routes, to earn a small fee on that fill (capped at 0.10% for perps). You can use builder codes without ever touching HIP-3 — most trading apps do exactly that, routing orders into Hyperliquid's existing markets and earning a builder fee. And a HIP-3 market exists regardless of which app's builder code is on any given order.

The short version: HIP-3 deployers earn from markets they created; builder-code apps earn from order flow they routed. For the full mechanics of the second one — approvals, the fee cap, and how it makes free trading tools sustainable — see Hyperliquid Builder Codes Explained.

What's been deployed — and where it's going

The early winners were commodities: gold and silver markets drew hundreds of millions in open interest within months. Then came equities and indices through trade.xyz — Tesla, Nvidia, Apple, Amazon and licensed index products — which now represent the large majority of HIP-3 open interest. And builders like Ventuals and TradeXYZ deployed the pre-IPO category, synthetic perps on private companies such as SpaceX, OpenAI and Anthropic (covered in our pre-IPO perps guide). For trading real-world equities and indices specifically, see Trading Stocks & Indices on Hyperliquid.

The trajectory is toward Hyperliquid becoming a venue where the market set is defined by demand rather than by a listing committee — a structural advantage no centralized exchange can easily match, and the reason HIP-3 volume has grown so fast.

Risks the model introduces

Permissionless market creation moves risk onto the deployer's design choices. The oracle is the biggest one: a HIP-3 market is only as sound as the price feed its deployer chose, and faulty-oracle incidents have already caused sharp, unfair liquidations in some builder markets. The 500K-HYPE slashing bond deters negligence but does not make a thin, young market behave like a deep one. New markets also have little price history, wider spreads, and — for equity and pre-IPO names — gap and session risks that crypto perps don't have.

Practical guidance: treat a builder-deployed market as distinct from a core Hyperliquid market. Read who deployed it and how its oracle works before sizing a position, and assume thinner liquidity and larger gaps than the majors.

Where Signalview fits

Signalview builds non-custodial AI agents that trade Hyperliquid perps, with strategies backtested over 18 months and scored from −100 to +100. Most of our coverage is the core book — BTC, ETH, SOL, HYPE and the liquid majors — where deep history makes a verifiable backtest meaningful. We also support selected HIP-3 markets where the data supports it (the trade.xyz equity perps behind a feature flag), while being careful about markets too young to backtest honestly — pre-IPO names among them.

The honest principle is the same one that runs through this whole site: a strategy is only worth automating if you can inspect how it performed across real history. HIP-3 vastly expands what trades on Hyperliquid; it does not change the requirement that the evidence has to exist before an agent acts on it.

Risk note: perpetual futures — core or builder-deployed — are leveraged, high-risk instruments. Builder-deployed markets add oracle and liquidity risk on top, and you can lose your entire margin. Nothing here is investment advice.