Hyperliquid is an On-Chain Perpetuals Venue with Order Book Execution

Hyperliquid is a trading-focused layer-one blockchain where perpetuals - leveraged contracts without expiry - meet through a fully on-chain order book, a public list of bids and asks. Traders self-custody their account keys, post collateral, and place spot or derivatives orders while HyperCore handles matching, margin, funding, and liquidation in chain state. Its defining choice is to combine centralized-exchange-style execution with verifiable settlement, while HyperEVM adds Ethereum-compatible smart contracts beside the trading engine.

Posted 2026-08-04

A complete trade, from Arbitrum collateral to a closed position

The HyperCore trading workflow begins with an EVM wallet or an email-backed wallet account. Rabby, MetaMask, Coinbase Wallet, and WalletConnect provide familiar connection paths. For the native bridge route, the wallet needs native USDC on Arbitrum plus enough ETH to pay for the deposit transaction. The minimum credited deposit is 5 USDC; an amount below that threshold is not credited.

After the balance arrives, the trader selects a spot or perpetual market. A perpetual order requires a direction, size, cross or isolated margin, an integer leverage setting from 1× to the market maximum, and an order type. Once the order fills, the position view displays entry price, mark price, unrealized profit or loss, funding, and an estimated liquidation price. A reduce-only order closes exposure without opening the opposite position. With no positions or resting orders left, USDC can be withdrawn to Arbitrum for a fixed 1 USDC fee, and the withdrawal itself requires no Arbitrum ETH from the user.

Execution model decides which alternative fits

Alternative perpetual venues differ most in matching, custody, collateral, and account access. An on-chain order book serves traders who want visible bids and asks, while a pool-based venue replaces the maker queue with liquidity supplied by deposited assets.

Hyperliquid puts orders, cancellations, fills, and liquidations into HyperCore state. dYdX Chain is the closest architectural alternative: it is a dedicated derivatives blockchain built with Cosmos SDK and CometBFT around an order book and matching engine. GMX takes another route, executing against GM and GLV liquidity pools with Chainlink Data Streams on networks including Arbitrum and Avalanche. Drift runs on Solana and combines its decentralized limit order book with keeper matching and an automated market maker fallback.

A custodial service such as Coinbase Advanced changes the decision again. It supplies account recovery, identity onboarding, fiat-linked account services, and jurisdiction-specific access, while controlling the trading account infrastructure. The meaningful choice is therefore not a maximum-leverage number; it is whether the trader wants self-custody, a particular execution model, and direct responsibility for collateral movement.

Two execution environments share one validator set

HyperCore and HyperEVM are the two execution environments of the Hyperliquid blockchain. Both inherit consensus and finality from HyperBFT, a proof-of-stake design inspired by HotStuff, but they handle different kinds of activity.

HyperCore contains the native order books, matching engine, margin state, spot balances, funding, and liquidation logic. These functions do not wait for a general-purpose smart contract to interpret each order. HyperEVM supplies Ethereum Virtual Machine compatibility for Solidity applications and ERC-20 contracts, with transfers and system interfaces connecting its applications to Core assets and market state.

The dual-block EVM configuration schedules fast blocks every 1 second with a 2 million gas limit and large blocks every 1 minute with a 30 million gas limit. Its on-chain mempool accepts the next 8 nonces for each address and prunes transactions older than 1 day. This separation preserves a fast path for ordinary interactions while leaving room for larger contract deployments.

Order instructions determine price control and queue position

The HyperCore central limit order book matches buyers and sellers by price and time priority. Every order type changes either execution certainty, price certainty, or whether the instruction rests as visible liquidity.

• Market: seeks an immediate fill against available orders, accepting the prices present in the book.
• Limit with GTC: fills at the chosen price or better and otherwise remains until filled or canceled.
• Post-only ALO: adds liquidity or is rejected rather than immediately taking liquidity.
• IOC: fills the available quantity immediately and cancels any remainder.
• Trigger orders: include Stop Market, Stop Limit, Take Market, and Take Limit instructions.
• Scale and TWAP: distribute one intended position across multiple prices or timed suborders.

A time-weighted average price order sends a suborder every 30 seconds and applies a 3% maximum-slippage constraint to each submission. If execution falls behind, a later catch-up suborder is capped at 3 times the normal suborder size. That constraint limits each attempt, but it does not guarantee that the complete requested quantity fills before the schedule ends.

Cross and isolated margin change which collateral is exposed

Cross margin and isolated margin determine how collateral supports a perpetual position. Cross margin is the default and shares available account equity among cross positions; isolated margin assigns a separate collateral amount to one position, so its liquidation does not reach unrelated isolated positions or the cross account.

Initial margin equals position notional divided by the selected leverage, and leverage must be an integer from 1× through the asset's maximum. Removing collateral is subject to an additional transfer rule: the remaining margin must meet the larger of the initial-margin requirement or 10% of total open notional. Funding payments and unrealized profit or loss continue to change account equity after entry.

Worked example - all changing inputs are hypothetical: assume a hypothetical account with no other positions deposits 1,000 USDC, selects hypothetical 3× leverage, and opens a hypothetical long at 2,000 per unit. The position has 3,000 USDC of notional and a size of 1.5 units. At a hypothetical exit price of 2,100, with hypothetical fees and funding set to zero, the 100-unit price rise produces 150 USDC of gross profit and 1,150 USDC of closing equity. A hypothetical 5% adverse move produces a 150 USDC gross loss instead.

Trading cost combines execution fees, spread, and hourly funding

The HyperCore cost model separates trading fees from funding and market impact. The published base perpetual tier charges 0.045% for taker execution and 0.015% for maker execution, while the base spot tier charges 0.070% and 0.040%, respectively. Fee tiers use rolling 14-day weighted volume and are assessed daily in UTC; spot volume receives a 2× weight in that calculation.

One fee tier applies across core perpetuals, HIP-3 perpetuals, and spot markets. Six staking-discount bands begin above 10 HYPE and culminate in a 40% discount above 500,000 HYPE. Spread and price impact remain separate from the fee schedule because they arise from the orders available at the moment of execution.

Funding settles every hour, using one eighth of an eight-hour rate whose fixed interest component is 0.01% per eight hours. The premium component is sampled every 5 seconds and averaged over the hour, while the funding rate is capped at 4% per hour. Positive funding transfers value from longs to shorts; negative funding reverses that direction. The payment is peer-to-peer rather than protocol revenue.

Mark price and maintenance margin govern liquidation

The liquidation engine compares account equity with maintenance margin using a mark price that combines external centralized-exchange prices with local order-book state. A temporary last trade therefore does not independently decide liquidation, and the displayed estimate can move as funding, cross-position profit or loss, and margin tiers change.

For core markets whose maximum leverage ranges from 3× to 40×, maintenance margin ranges from 16.7% to 1.25% because it equals half the initial margin at maximum leverage. Once equity falls below maintenance, the engine first sends market orders to close the position through the book, with a 0% liquidation-clearance fee. If equity falls below two-thirds of maintenance margin before book liquidation succeeds, the liquidator vault supplies the backstop.

Liquidatable positions above 100,000 USDC receive a 20% partial market-liquidation attempt first. A 30-second cooldown follows a partial-liquidation block, during which further market-liquidation orders cover the full position. Cross margin places multiple positions behind the same equity buffer, whereas isolated margin confines this process to its assigned position. Front-end access and chain state are also separate operating layers: regional or compliance controls can restrict a particular interface while account state remains on-chain.

Shared market state supports traders, liquidity providers, and builders

The shared HyperCore state supports discretionary trading, automated market making, native spot assets, and community-deployed derivatives. API wallets act as signing agents for a master account, while subaccounts separate positions and margin without requiring a new primary wallet for every strategy.

HIP-1 defines capped-supply fungible tokens with native spot order books, and HIP-2 supplies automated liquidity on a 0.3% price grid that updates at 3-second intervals. HIP-3 lets a builder operate perpetual markets while choosing oracle inputs, leverage limits, and settlement. A HIP-3 deployer must maintain 500,000 staked HYPE, and that requirement remains for 30 days after all of its markets are halted.

HLP, the Hyperliquidity Provider vault, supplies market-making liquidity, participates in liquidations, supplies USDC to supported earning functions, and receives part of trading fees. Its deposit lock lasts 4 days from the most recent deposit. Depositors share the vault's profit and loss, including the consequences of inventory, execution, and liquidation activity.

HYPE connects consensus, fee discounts, and market deployment

HYPE is the proof-of-stake asset securing HyperBFT and the staking asset behind several protocol permissions. An active validator must self-delegate 10,000 HYPE, and that self-delegation remains locked for 1 year. Consensus treats more than two-thirds of total stake as a quorum.

A delegation to one validator has a 1-day lock. Moving an unstaked balance from the staking account back to the spot account enters a 7-day queue, with at most 5 pending withdrawals per address. Rewards accrue every minute, distribute daily, and are automatically redelegated. These timing rules make staked HYPE less liquid than HYPE already held in a spot balance.

From specialized derivatives engine to broader financial chain

The project's development sequence explains its unusual structure. It began with a purpose-built perpetuals engine, then extended HyperCore through HIP-1 spot assets and HYPE-based proof of stake. HyperEVM added general-purpose contracts beside the order books, while HIP-3 opened a path for independent teams to define and operate additional perpetual markets.

That progression keeps trading as the coordination layer rather than treating it as one application among unrelated contracts. Hyperliquid fits users who value visible order-book execution, self-custodied account keys, programmable APIs, and settlement under a dedicated validator network. It demands comfort with collateral transfers, margin mechanics, funding, bridge assumptions, and interface eligibility. Someone seeking fiat deposits, reversible account administration, or a simple unleveraged purchase may find a regulated custodial exchange or a conventional spot venue more appropriate.