Hyperliquid

Hyperliquid is an onchain perp order book for active traders

Hyperliquid is a trading blockchain where an order book lists bids and offers, while perpetual contracts track prices without expiring. Its HyperCore engine matches spot and perp orders entirely onchain under price-time priority, then settles margin through the same layer-one state. Traders get familiar market, limit, stop, take-profit and TWAP controls without paying gas per order. The trade-off is direct exposure to leverage, hourly funding, bridge dependencies and a validator-run price system.

Updated 6 Aug 2026

Fast order-book control for active perpetual traders

Importantly, Hyperliquid gives active traders centralized-exchange-style order control while keeping orders, cancels, fills and liquidations in shared chain state. This matters when a strategy depends on queue position, exact limit prices and rapid position changes rather than a swap against a liquidity pool.

Perpetual markets support long and short exposure without an expiry date. A trader expecting BTC weakness can open a short against USDC collateral, attach a stop loss and later close with a reduce-only order; buying HYPE on the spot book, by contrast, changes the actual token balance. Automated firms can use the API, while discretionary users receive the same market, limit, scale and time-weighted average price controls through a trading interface.

Margin risk arrives before funding cost

Perpetual margin determines how much collateral backs a position and when the clearinghouse closes it. Cross margin shares collateral across all cross positions; isolated margin fences the assigned collateral inside one position.

Leverage is selected as an integer from 1x up to each asset's maximum, and documented market limits span 3x to 40x. The maintenance requirement equals half the initial margin fraction at maximum leverage, producing endpoints of 16.7% for a 3x market and 1.25% for a 40x market. Liquidation responds to the mark price, not a single last trade. That mark combines the local book with validator-published reference data, reducing dependence on one venue or one print.

For positions above 100,000 USDC, an initial partial liquidation sends 20% of the position to the book, followed by a 30-second cooldown. If equity falls below two-thirds of maintenance margin and book execution does not restore compliance, the HLP liquidator vault takes the backstop path. A backstop cross liquidation transfers cross positions and cross margin; isolated backstop liquidation stays within its assigned margin. Funding and other cross positions can move the displayed liquidation price after entry, so it is a state estimate rather than an immutable boundary.

HyperCore's matching path

HyperCore is the specialized execution layer that holds order books, margin state and the clearinghouse. HyperBFT consensus gives validators one transaction order, allowing price-time priority to operate onchain rather than through a separate matching server.

When a resting perp order meets an incoming order, the clearinghouse checks margin again for the resting side. Within each block, order-related actions are arranged in 3 groups: non-GTC/IOC actions, cancels, then actions that submit GTC or IOC orders. Prices accept up to 5 significant figures, with a ceiling of 6 decimal places for perps and 8 for spot; each asset's size precision sets the tighter tick constraint.

Validator oracle updates arrive about every 3 seconds. The standard mark calculation uses 3 main inputs, including a 150-second exponential moving average of the local basis. Binance, OKX, Bybit, Kraken, KuCoin, Gate and MEXC contribute to the external reference set where relevant, while assets whose primary liquidity lives locally follow the corresponding local-source rule.

Funding keeps perpetual prices tied to spot

Perpetual funding keeps a contract near its underlying spot reference by transferring value between longs and shorts. Settlement occurs every 1 hour, using one-eighth of an 8-hour funding calculation, and the protocol keeps the payment peer to peer.

The fixed interest component is 0.01% per 8 hours, equivalent to 0.00125% in each hourly slice. A premium component reflects the difference between impact prices and the oracle: positive funding means longs pay shorts, while negative funding reverses the direction. Premium samples are taken every 5 seconds and averaged across the hour; the resulting funding rate is capped at 4% per hour.

Contract size, oracle price and the applicable funding rate set the cash transfer. A position can be directionally correct over a short interval yet lose part of its return through repeated funding payments. Because standard perpetuals never expire, closing the position - not waiting for delivery - ends that exposure.

Use order instructions to control execution

HyperCore order instructions determine whether an order rests, crosses the spread or only reduces existing exposure. Market orders seek immediate execution, while limit orders trade at the chosen price or better and preserve price control at the cost of uncertain completion.

A Good Til Cancel order stays until it fills or is canceled. Immediate or Cancel attempts the available quantity at once and removes the remainder; Post Only, also called Add Liquidity Only, refuses immediate execution so the order enters the book as maker liquidity. Reduce Only blocks an oversized closing order from reversing a long into a short, a useful guard when multiple exits target the same position.

TWAP divides a parent order into suborders sent every 30 seconds, each with a 3% maximum slippage constraint. When earlier slices fall behind, a later slice cannot exceed 3 times the normal suborder size. Stop-market and take-market instructions activate at their trigger and submit market orders, while stop-limit and take-limit variants preserve a limit price. These controls manage execution behavior; none removes gap risk or guarantees a fill.

Move collateral through the Arbitrum bridge

The native Arbitrum bridge is the direct collateral route for USDC, and an EVM wallet supplies the deposit signature. Rabby, MetaMask, Coinbase Wallet and WalletConnect-compatible setups fit that path; an email login is another supported account route.

An Arbitrum deposit requires USDC plus enough ETH for the originating network transaction, and the minimum credited deposit is 5 USDC. Enabling trading uses a gasless signature, after which HyperCore orders themselves do not consume wallet gas. The deposit lands in the perps balance, which can be moved atomically to the spot balance when the intended market uses spot assets.

The native bridge credits a deposit after more than two-thirds of staking power has signed it, and every withdrawal costs a fixed 1 USDC. Withdrawals return USDC to Arbitrum and do not require the user to hold Arbitrum ETH on the trading side. The relevant costs are the originating Arbitrum transaction, maker or taker fees on completed trades and the fixed bridge withdrawal charge.

Spot, HyperEVM and HYPE

HyperCore spot trading and the HyperEVM share one Layer 1 but serve different workloads. HyperCore provides native books and margin logic; HyperEVM runs general-purpose Ethereum Virtual Machine contracts with HYPE as gas.

HIP-1 defines capped-supply fungible tokens for native spot markets. A HIP-1 token name has a maximum of 6 characters, and its size precision must sit at least 5 decimal places below its smallest-unit precision. Native spot books quote against spot USDC at initialization, while spot USDC itself uses 8 decimals for both size and smallest-unit accounting.

HyperEVM mainnet uses chain ID 999, gives HYPE 18 decimals, and implements EIP-1559 under the Cancun execution rules without blobs. Its base and priority fees are burned. The split lets trading remain specialized in HyperCore while smart contracts access a familiar EVM environment; moving assets between those components follows a defined transfer path rather than an ordinary spot-book trade.

dYdX Chain, GMX and Jupiter Perps use different market structures

dYdX Chain, GMX and Jupiter Perps offer distinct answers to the same perpetual-trading requirement. The central difference is market structure: a validator-operated order book, pooled counterparty liquidity or an application-specific chain with its own order flow.

dYdX Chain uses the Cosmos SDK and CometBFT for a sovereign proof-of-stake derivatives chain with an order-book interface. GMX routes perpetual positions against protocol liquidity pools and oracle pricing across networks including Arbitrum and Avalanche. Jupiter Perps operates on Solana with the JLP pool holding custody assets and absorbing trader profit and loss. These models replace queue-based maker liquidity with different inventory and oracle arrangements.

Hyperliquid's distinguishing choice is to put the order books and clearinghouse inside HyperCore while settling them under the same Layer 1 consensus. That appeals to traders who value visible depth and maker-style execution. Pool-based venues support a different workflow because the quote derives from pool capacity and oracle rules rather than a public price-time queue. Venue choice changes collateral, bridge, liquidation and execution exposure at once.

Match Hyperliquid to an order-book trading process

In the same way, Hyperliquid suits traders who already reason in spreads, queue priority, leverage, funding and mark price. Its strongest fit is an active process that values native order books, API access, transparent liquidation rules and a single chain state for spot and perps.

An occasional spot buyer gains less from the specialized order controls, while a liquidity provider must understand inventory, maker fees and HLP strategy exposure. The protocol also asks users to accept HyperBFT validator consensus, an Arbitrum bridge for the native USDC route and the operational risk of a younger Layer 1. None of those trade-offs is captured by the displayed leverage slider.

Product choice comes first because spot changes a token balance and a perp creates margined price exposure. Margin mode defines the loss boundary, the exit instruction shapes execution, and the planned holding period determines how many hourly funding events enter the trade. Together, those mechanics decide whether the chain's speed and visible queue fit the intended strategy.