What to Check Before Trading Hyperliquid HIP-3? 5 Risks to Verify

On-Chain

03 October 2026

Before trading HIP-3, what you need to check is not the risk of Hyperliquid itself, but the risk of the deployer. HIP-3 allows third parties to stake 500,000 HYPE and then deploy perpetual contract markets on their own. The deployer is responsible for defining oracle prices, leverage limits, and settlement rules. HyperCore provides matching and margin infrastructure, but price inputs, market operations, and exception handling are controlled by the deployer. This means that under the same trading interface, the actual source of risk for different HIP-3 markets is completely different.

OKX Exchange
A leading global cryptocurrency platform,suitable for both beginners and experienced traders.
New user benefit: 20% off trading fees upon registration!！

The following five items are arranged in the order of "can you bear it, can you understand it, and what to do if something goes wrong."

Item 1: Who is the deployer, and how many markets does it operate

HIP-3 markets are created by third-party deployers, not officially launched by Hyperliquid. Currently, TradeXYZ controls more than 90% of the HIP-3 market share. Other small deployers face extremely high competitive pressure, and some deployers have announced business closures because they could not compete with TradeXYZ's USDC-denominated similar markets.

The direct problem caused by deployer concentration is: if the dominant deployer has operational problems or pricing anomalies, the affected trader base is very wide. A Blockworks Research sample analysis of 136 paid HIP-3 listed projects shows that only 44 recovered their auction costs, and the median auction cost recovery period for non-TradeXYZ markets is about 4 years.

What you need to check: Open the Hyperliquid interface and confirm which DEX your target market belongs to (such as xyz, flx, and other deployer identifiers). Check the deployer's historical operation records, current number of active markets, and total open interest. If the deployer has only one market and trading volume is very small, slippage and liquidity risk will be significantly higher.

Item 2: Where does the oracle price come from

The HIP-3 deployer is responsible for setting the oracle price. The setOracle action allows the deployer to submit markPxs, oraclePxs, and externalPerpPxs. The final mark price is a combination of these inputs and the local order book mid-price.

This creates a risk structure different from the Hyperliquid main site. The pricing problem of the main site BTC perpetual is the responsibility of the protocol itself; for HIP-3 stock-type perpetuals, the pricing responsibility is layered between the protocol and the deployer. The Trade.xyz SK Hynix pricing anomaly event is a concrete case: the quality of data provided by the deployer directly determines whether the mark price seen by traders is trustworthy.

What you need to check: Confirm the underlying asset type of the market. For assets with continuous prices and publicly verifiable spot sources (such as mainstream crypto assets), oracle risk is relatively controllable. For stocks, Pre-IPO, and private equity assets, the underlying itself does not have 24/7 continuous trading. The deployer needs to handle after-hours prices, exchange rate conversion, and reference market gaps, so data quality uncertainty is significantly higher.

Item 3: Is the 1% price movement limit suitable for your underlying

The HIP-3 protocol layer imposes a limit of at most 1% deviation from the previous value per update on the mark price. The oracle updates at least every 2.5 seconds, and calling once every 3 seconds is recommended. If there is no update within 10 seconds, the mark price falls back to the local order book best bid/best ask mid-price.

This mechanism is a protection for assets with smooth price changes, but an obstacle for assets with jumpy price changes. Jsquare Research's analysis points out that binary prediction markets, interest rate markets, and low-liquidity assets have structural difficulties under the HIP-3 framework: when the real price needs to jump from 0.50 to 1.00, the on-chain price can only gradually approach in 1% increments each time, and the price deviation generated during this period provides arbitrage space for informed traders.

What you need to check: Determine whether the asset you are trading has a "step pricing" characteristic. If the asset price may jump instantly under event-driven conditions (such as election results, earnings releases, sports events), HIP-3's 1% rate limit means your position may hit the liquidation line before the price adjustment is completed.

Item 4: Margin mode and your account abstraction type

HIP-3 markets use cross margin by default, but the account abstraction type determines the scope of cross margin. According to Hyperliquid documentation: when using a unified account or portfolio margin, cross margin positions across multiple DEXs under the same collateral type share margin; when using standard abstraction, cross margin only applies to assets within the same DEX.

This means the same USDC collateral has a completely different risk exposure range under different account settings. Under standard abstraction, losses on TradeXYZ will not eat into your margin on other DEXs; under a unified account, they may.

In addition, HIP-3 DEXs also support a mode called "no cross," which allows cross margin but prohibits margin withdrawal. Some assets are strictly isolated margin, and margin is released proportionally as positions are closed and cannot be manually withdrawn.

What you need to check: Before opening a position, confirm your account abstraction type and the margin mode applicable to that HIP-3 market. If you have positions on multiple DEXs, the shared scope of cross margin directly determines whether a single market loss will trigger chain liquidations.

Item 5: The deployer can actively settle your market

The HIP-3 deployer has the haltTrading permission and can cancel all orders and settle positions at the current mark price. The same action can also be used to resume trading, effectively "recycling" the asset for reuse.

The design intent of this mechanism is to allow the deployer to handle things in an orderly manner during oracle failures, market anomalies, or contract expiration, but it means your position can be force-closed when the deployer deems it necessary. The settlement price is the mark price at the time halt is triggered, not a price you choose.

Deployers are also subject to slashing constraints: the 500,000 HYPE stake must be maintained for at least 183 days. Even if unstaking is initiated and enters the 7-day queue, the stake can still be slashed. Slashing is determined by validator stake voting against behavior that threatens protocol correctness, normal operation, or performance.

What you need to check: Understand under what conditions the market deployer may trigger a halt. For contracts with a clear expiration date (such as after a Pre-IPO listing), deployer settlement is an expected process; for perpetual contracts without an expiration date, active settlement is an unconventional operation, and you need to pay attention to whether the deployer has a record of similar behavior.

Standard for completing the five checks

You do not need to give a "safe" conclusion for every item. The sign of completing the check is: you can clearly explain where the risk of this trade comes from — whether it is the deployer's data quality, the pricing characteristics of the underlying itself, or your own margin settings.

If you cannot confirm more than two of the five items, the safer approach is to observe first and not trade. HIP-3's permissionless listing mechanism lowers the threshold for market creation, but it does not lower the threshold for judgment. The deployer staked 500,000 HYPE, but that does not mean you do not need to see clearly for yourself.

OKX Exchange
A leading global cryptocurrency platform,suitable for both beginners and experienced traders.
New user benefit: 20% off trading fees upon registration!！