HIP-3: Builder-Deployed Perpetual Markets and RWA Outlook

Hyperliquid quietly changed who is allowed to create a market. For a serious trader the question is no longer what does the exchange list? but who deployed this market, what oracle did they pick, and what happens to me if they get it wrong?

For its first few years, trading a perpetual on Hyperliquid meant trading a market the protocol itself had curated, much like Binance or Bybit, where a listing committee vets spot liquidity before a contract goes live. HIP-3 ends that model. It lets any qualifying builder deploy a perpetual market directly onto Hyperliquid's core engine, choosing the asset, the oracle, and the contract specifications. Hyperliquid still handles execution, margining, and settlement; the builder defines and operates the market.

That single change is why, by mid-2026, Hyperliquid is the venue where you can trade perpetuals on tokenized equities, commodities, and FX alongside crypto, and why open interest in those real-world-asset (RWA) markets has become one of the most-watched numbers in the ecosystem. It is also why your risk is no longer just directional. This note explains the mechanism precisely, then maps the microstructure traps that come with it.

From a listing committee to a deployment framework

A centralized exchange treats a new derivative as a curation problem. Before a contract launches, a committee checks that the underlying has deep, multi-venue spot liquidity so the index price is hard to manipulate. That gatekeeping is slow, but it concentrates risk-management expertise in one place.

HIP-3 inverts the arrangement. Per the official documentation, the deployer of a perp market is responsible for market definition (the oracle definition and contract specifications) and market operation (setting oracle prices, leverage limits, and settling the market if needed). The market runs on the same HyperCore stack as every other Hyperliquid perp, with the same high-performance margining, order books, and a unified API, so execution quality is inherited. What is not inherited is the curation. The builder makes the judgment calls a listing committee used to make, and the consequences land on the people who trade the market.

In practice the early winners are specialists. As of mid-2026 a single deployer, trade.xyz, accounts for the large majority of HIP-3 open interest in tokenized stocks and commodities, and consortiums such as Dreamcash, Tether, and Selini Capital have launched RWA perps collateralized by on-chain stablecoins. Market-structure figures move quickly, so treat them as context, not constants.

The mechanism that actually matters

If you only remember the marketing line, permissionless perps, you will misprice the risk. The specifics determine whether a market is safe to size into. These are from Hyperliquid's official HIP-3 documentation.

Two implications fall straight out. First, the economics favor the builder: a fixed 50% fee share on a market you control is a real revenue line, which is exactly why sophisticated teams are deploying RWA venues. Second, the 500k HYPE stake is the protocol's alignment lever, and it is backed by a slashing regime that makes deployer competence your problem too.

Where builder markets break: the oracle

Hyperliquid's headline safety design is that the mark price is derived from external spot feeds rather than its own order book, which neutralizes the classic push-the-perp-book attack. The official spec keeps the oracle general at the protocol level but warns that perps make the most sense when there is a well-defined underlying that is difficult to manipulate, and notes that deployers are subject to slashing for every market they list.

That caveat exists because HIP-3 deliberately opens the door to assets with thin or non-existent CEX spot markets. When there is no deep external reference, the deployer must construct one, and the cost to move a shallow reference can be lower than the open interest riding on the perp. Two failure shapes follow:

• Manipulation premium. If a market's index leans on a few shallow venues, price can be pushed to force liquidations. A time-weighted feed blunts instant flash-loan moves but not sustained pressure. Before you trust a market, look at what the oracle is made of, not just where the price is.

• Stale-feed disconnects. If the source feed stops updating, the mark can freeze while the contract keeps trading on sentiment. When it catches up, the correction can be abrupt, and on an hourly funding cadence the wrong side of a frozen premium is expensive well before the snap-back.

RWA perpetuals: the calendar is a microstructure risk

The most distinctive HIP-3 use case is the RWA perpetual: equities, commodities, FX, and similar. These collide with a mismatch that does not exist for crypto, namely that traditional markets close, and the perp does not.

Hyperliquid settles funding on an hourly cadence from a one-hour premium average. When an RWA's underlying spot market closes on Friday, its reference can stop updating for the weekend while the perpetual keeps trading around the clock. If demand bids the perp above the static reference, the premium, and the funding paid by longs to shorts, can accumulate hour after hour. Collecting that funding looks attractive until Monday, when the traditional market reopens and the reference can re-price in a single gap. A short that harvested weekend funding now faces that gap with little room to react.

Liquidity, HLP, and auto-deleveraging

A perp with no liquidity is untradeable at size. A centralized exchange solves this by paying designated market makers; HIP-3 has no such guarantee. New markets often lean on the Hyperliquid Liquidity Provider (HLP) vault for baseline depth, but HLP allocates capital dynamically on risk-adjusted terms. If a market shows toxic or one-sided flow, HLP can widen quotes or step back, exactly when you would want it present.

When a bankrupt position cannot be closed in a thin book, Hyperliquid uses auto-deleveraging (ADL): profitable traders on the opposite side are closed at the bankruptcy price. The uncomfortable corollary for a successful strategy in a long-tail market is that being right makes you a candidate for ADL. There is no published threshold to rely on; the defensive posture is to watch order-book depth and open interest, keep leverage modest, and rotate profits out rather than assume you can exit on demand.

Slashing and cross-margin: read these before you size

Slashing falls on the deployer, but shapes your market

To keep markets honest, a deployer's 500k HYPE is slashable by stake-weighted validator vote, and remains slashable through the 7-day unstaking queue. The documentation is explicit that slashing does not distinguish between malice, incompetence, and compromised keys, what matters is the effect on the protocol, and that slashed stake is burned, not distributed to affected users. Indicative ceilings: up to 100% for inputs causing invalid state transitions or prolonged downtime, up to 50% for brief downtime, up to 20% for performance degradation. The practical signal: a deployer's stake at risk is a rough proxy for how carefully a market is likely to be run, and burned stake means you should never assume a slashing event will compensate you.

Cross-margin is irreversible and gated

Enabling cross-margin on a HIP-3 asset is, per the docs, irreversible. Validators only permit it for assets meeting eligibility standards (sufficient observable liquidity, a reliable external oracle, and manipulation resistance), and they review for slashing whenever an asset's external price moves more than 50% relative to the start-of-day price. Assets where 50% daily moves are expected more than once a month are ineligible for cross-margin. For you, the takeaway is concrete: know whether the HIP-3 market you are trading is cross or isolated. If it shares your cross-margin pool, a dislocation in one long-tail asset can reach the rest of your account.

Strategic implications

HIP-3 is best read as a deliberate transfer of responsibility. The protocol keeps what it is uniquely good at, fast and solvent execution and settlement, and pushes market design and curation out to a competitive layer of builders. That is what makes the RWA expansion possible at speed, and it is why the durable edge for a trader here is operational diligence, not just a price view: audit the oracle, the deployer, the margin mode, and the liquidity before you size, and treat unfamiliar builder markets as guilty until proven liquid. For builders, the calculus is the mirror image: a fixed 50% fee share on a market you control is a genuine business, paid for with a 500k HYPE stake exposed to a slashing regime that does not care whether a failure was malicious or merely careless.

How to monitor

• Open interest by HIP-3 DEX and asset — concentration and growth; verify the current figure before citing it.

• Oracle composition — the number and depth of venues behind a market's index.

• Funding versus the underlying — especially the weekend premium on RWA pairs.

• Book depth and ADL exposure — programmatically, via the API, rather than a UI warning light.

• Deployer stake and margin mode — stake maintained, and whether the market is cross or isolated.