Hyperliquid HIP-3 Perps Explained: Markets, Fees, and Risks

The standard perp DEX and a HIP-3 market have different operators and responsibilities. HIP-3 lets builders deploy perp DEXs permissionlessly, but “permissionless” does not mean that every listing is reviewed, unlimited, or standardized. The deployer defines the underlying reference and contract specification, provides oracle prices, and operates market settings such as leverage limits and settlement. Protocol conditions can also apply, including staking, listing auctions, collateral requirements, and validator actions.

Hyperliquid's HIP-3 specification currently lists a 500,000 HYPE stake requirement for mainnet deployers and a requirement to maintain it for at least 183 days after deploying a DEX. These are protocol conditions for deployers; they are not the margin a trader must deposit to open a position. Protocol requirements can change, so a builder considering a launch should check the current specification. A user cannot infer a market's safety or a deployer's competence from the stake amount alone.

HIP-3 orders use HyperCore's order-book and matching infrastructure, so a HIP-3 DEX is not a separate blockchain or trading app. Each DEX nevertheless has an independent order book and margin configuration. Liquidity and collateral capacity on another DEX do not automatically combine with it. First identify the DEX name shown with the symbol, the exact asset identifier, and the market's trading status. Similar asset names do not describe the same contract when the deployer or contract definition differs.

Hyperliquid's API separates the list of perp DEXs, deployer information, and each DEX's metadata, asset contexts, account state, and market limits. A screen or script that queries only the default perp DEX may miss a HIP-3 market's margin schedule, open-interest cap, funding, or current trading status. Check the selected DEX in the trading interface; if you use a data tool, make sure the request targets that DEX. Field definitions and query scope are in the perpetuals API reference.

Unrealized P&L, margin, and liquidation decisions depend on a market's price reference. In HIP-3, the deployer defines the oracle and its updates. A familiar ticker or the fact that a market is listed on HyperCore does not prove that the reference price represents a deep, independently traded spot market. Check whether the underlying can actually be traded, whether the oracle source is independent and liquid, how an index or feed is calculated, and how resistant it is to manipulation.

The deployer API describes actions for updating prices, funding multipliers and interest rates, margin tables, open-interest caps, and trading halts. Defined responsibilities can help identify who operates a market, but they do not mean every market uses the same settings. Check the initial specification, later change permissions, update interval, and behavior during a feed failure in the deployer actions reference.

For example, if an index relies heavily on one thinly traded token venue, a small trade or delayed feed could widen the gap between the oracle and the order book. That is not just a display issue around liquidation prices. Funding, unrealized P&L, account equity, and settlement can react to values from different points in time. Conversely, even a robust oracle with several observable spot markets does not make fills identical to standard perps when contract size, tick size, collateral, or maximum order size differ.

Separate order books and margin settings across HIP-3 DEXs do not mean every position is isolated margin. Check the margin mode configured for the asset. Hyperliquid's current specification sets criteria for HIP-3 assets that may use cross margin, including sufficient observable liquidity, a reliable external oracle, and resilience to price manipulation. Deployers can set the margin mode, and validator requirements may also apply. A leverage number on screen does not show how much of your account balance can be exposed to a loss.

Cross margin across DEXs operated by different deployers can transmit a market shock through a shared account. If an abnormal price in one market reduces account equity, the available margin for positions in another can fall too. A high maximum leverage is not a recommendation to use it. Review each asset's maintenance-margin tiers, open-interest limit, liquidation reference price, backstop or ADL path, and the account's cross-margin setting together. The perpetual margin guide explains general margin ranges; the perpetual liquidation guide covers liquidation mechanics and the limits of displayed prices.

The standard Hyperliquid perp fee tier may not be enough to estimate the total cost of a HIP-3 trade. The official fee documentation says a user's base tier applies across spot, standard perps, and HIP-3, while a HIP-3 deployer can configure an additional market fee share. Referral or staking discounts may also apply under their conditions. The final execution cost therefore depends on the current account tier, maker or taker status, collateral, and market settings. Configurable ranges and discounts can change.

Consider the official example for normal mode with non-aligned collateral. Treat the user's base fee as one unit: a feeScale of 0 means one unit to the protocol and none to the deployer; 0.5 means one protocol unit plus half a unit for the deployer; and 1 means one unit for each. A setting of 0.5 does not make the total fee half the base fee. At 1, a deployer share equal to the base fee is added. Check the Hyperliquid fee documentation and the deployer fee-setting specification for the current formula and exceptions involving growth mode or aligned collateral.

Here is a hypothetical amount to make the scale concrete. With a base rate of 0.045%, a single $10,000 taker fill has a base fee of $10,000 × 0.00045 = $4.50. Assume non-aligned collateral, normal mode, and a deployer fee scale of 0.5. The documented proportions produce a $4.50 protocol share and a $2.25 deployer share, or $6.75 in total. This is not the actual fee for every HIP-3 market. Tier, maker or taker status, referral and staking discounts, growth mode, collateral, and deployer settings can change it. When estimating a round trip, verify that the same assumptions apply to the closing fill.

Fee tiers are based on rolling 14-day volume. Spot and perp volume both contribute, and the current documentation weights spot volume at twice its amount. When comparing HIP-3 markets, record more than the displayed fee on one fill: account tier, spot-volume weighting, discount order, deployer share, and maker rebates all matter. Picking the smallest number from a tier table and calling it the total cost may not match the execution ledger. See the perpetual trading costs guide for the general distinction between maker, taker, and account costs.

A HIP-3 deployer can halt an asset with haltTrading. The current specification says this cancels all resting orders and settles open positions at the current mark price. The same action can be used to resume trading. In other words, a perp can have no expiration date and still not guarantee that a trader can close at any chosen order-book price. Who defines and operates the market, the price reference at the halt, and the account treatment are practical parts of the contract.

This matters if tradable liquidity disappears or an index reference changes. The settlement price is not guaranteed to match the last executable bid or ask, and other account items such as fees, funding, or collateral conversion can remain relevant. Before trading, check the market status and notices, who can halt it, and the current mark price. The Hyperliquid funding guide compares standard perp funding with the separate settings available for HIP-3.

Do not compare two HIP-3 markets by asset name or leverage alone. Align what one contract represents, the assets used for P&L and collateral, the oracle and mark-price fields, whether a fee is quoted per fill or for both sides, and whether the deployer share is included. Two contracts that reference different indexes or instruments may not hedge each other, even if both include “BTC” in their names.

For each market, record the DEX and asset identifier, trading status, oracle source, collateral, contract specification, maximum leverage and maintenance schedule, cross or isolated mode, open-interest limit, total taker cost, funding rules, and halt and settlement process. If official documentation does not disclose an item, mark it as unknown instead of filling it in with the standard perp's value. The perpetuals API reference explains how to query market status, price, and margin contexts.

These checks describe differences to consider when comparing HIP-3 markets; they do not recommend a deployer or exchange. Published protocol rules alone cannot guarantee oracle quality, executable liquidity, operational competence, or future losses. Compare the latest market specification with the fee and margin conditions shown for your account before placing an order.