Hyperliquid

Hyperliquid is a Fully On-Chain Order-Book Exchange

Hyperliquid is a blockchain exchange where perpetual futures are contracts without expiry and an on-chain order book publicly records bids and asks. Its custom Layer 1 combines self-custodial trading with the familiar controls of a centralized venue: market and limit orders, cross or isolated margin, funding payments, and liquidations. HyperCore runs the native perpetual and spot markets, while HyperEVM adds Ethereum-compatible smart contracts to the same consensus-backed state.

Updated on 6 Aug 2026

Bottom line: Hourly funding, rather than contract expiry, keeps perpetual prices aligned with their underlying markets.

Trading fees before the first order

The trading fee schedule separates perpetual and spot activity, then assigns one account-wide tier from rolling 14-day weighted volume. Hyperliquid's base tier charges 0.045% for a perpetual taker and 0.015% for a perpetual maker; base spot rates are 0.070% taker and 0.040% maker. Spot volume receives a 2× weight when the shared tier is calculated, so the two markets contribute differently to the same threshold.

Trading actions on HyperCore have no separate network-gas charge, although maker or taker fees still apply to fills. Depositing USDC through the native Arbitrum route requires ETH for the Arbitrum transaction. Withdrawing USDC to Arbitrum deducts a fixed 1 USDC fee instead of requiring ETH in the trading account. Funding sits outside these trading fees because it passes directly between long and short positions.

One chain, two execution environments

The Hyperliquid blockchain divides execution between HyperCore and HyperEVM. HyperCore contains the order books, matching engine, margin accounts, and liquidation logic; HyperEVM provides an Ethereum Virtual Machine environment for Solidity contracts and standard Ethereum tooling.

HyperBFT consensus orders both components inside one Layer 1 state. An order, cancellation, trade, or liquidation reaches finality with the committed block, so the public chain carries the exchange's authoritative sequence rather than a private matching server. HyperEVM mainnet uses chain ID 999, HYPE has 18 decimals there, and EIP-1559 governs gas pricing. Base fees and priority fees are burned. This split gives traders a purpose-built venue while letting developers compose applications around its native liquidity.

How the on-chain order book reaches a fill

The HyperCore order book matches bids and asks by price-time priority. Prices must land on the market's tick size, sizes must respect its lot size, and margin is checked when an opening order arrives and again when a resting order matches.

Price inputs accept up to 5 significant figures. Perpetual prices are limited to 6 decimal places minus the asset's size decimals, while spot uses an 8-decimal ceiling under the same rule. Inside each block, the execution order separates non-book actions, cancellations, and actions that submit Good Til Cancel or Immediate or Cancel orders. That deterministic ordering makes a cancellation's position in the block observable.

Available controls include market, limit, post-only, stop, take-profit, scale, and time-weighted average price orders. A TWAP sends a suborder every 30 seconds with a 3% maximum-slippage constraint. When it falls behind schedule, a later suborder is capped at 3× the normal slice, so the parent order can finish with some quantity unfilled.

Perpetuals, spot markets, and vault strategies

Perpetual futures are the primary trading product, while spot order books and vaults extend the same HyperCore machinery to ownership and managed strategies. A perpetual position uses collateral to take long or short exposure without acquiring the underlying asset, and its funding payment helps track the reference market.

Spot trading transfers HIP-1 assets between accounts rather than creating derivative exposure. HIP-2 adds protocol-run liquidity logic for new USDC-quoted spot books, while HIP-3 lets qualified builders operate separate perpetual DEXs with their own market definitions and oracles. Vaults package trading strategies into share-based deposits; a user-managed vault assigns 10% of profits to its owner, whereas protocol vaults do not apply that profit share. HLP uses this vault framework for market making and backstop liquidation activity.

From wallet connection to usable collateral

The onboarding path consists of connecting an EVM account, enabling trading with a signature, and funding the appropriate balance. MetaMask, Rabby, WalletConnect-compatible accounts, and an email-created embedded wallet all lead to an address-controlled HyperCore account; enabling trading is a gasless signed action.

For the native USDC bridge route, the source asset is USDC on Arbitrum and the minimum credited deposit is 5 USDC. ETH pays the source-chain gas, not the trading engine. After crediting, unified account mode uses one balance per asset across eligible spot and cross-margin activity, while standard mode keeps spot, perpetual, and separate DEX balances apart. Before placing an order, the market, collateral asset, margin mode, size, leverage, and order option should all describe the intended exposure.

A withdrawal reverses the route to Arbitrum and charges the fixed 1 USDC bridge fee. Sending a different token to a USDC deposit route does not convert it into collateral, so the selected network and asset must match the deposit method.

Margin, funding, and liquidation boundaries

Margin controls determine how much collateral supports a perpetual position and when the protocol reduces it. Cross margin shares account equity across cross positions; isolated margin confines collateral and liquidation accounting to one position. Leverage is selected as an integer from 1 up to the asset's published maximum.

Removing margin from a cross account must leave at least the larger of its initial-margin requirement or 10% of total open notional. Funding transfers occur every 1 hour, although the formula is expressed as an 8-hour rate and apportioned into hourly payments. Its fixed interest component is 0.01% per 8 hours, the variable premium reflects the gap between contract and oracle prices, and the protocol caps funding at 4% per hour.

Maintenance margin equals half the initial margin at an asset's maximum leverage. When account equity falls below maintenance margin, market orders attempt to close the position through the book. For a liquidatable mainnet position larger than 100,000 USDC, the first partial-liquidation order submits 20% of its size to the book, followed by a 30-second cooldown. Backstop transfer to the liquidator vault applies below two-thirds of maintenance margin when book execution has not restored the requirement. Cross margin therefore links the fate of several positions, while isolated margin narrows that connection.

Where HYPE fits into the system

HYPE is the native asset for validator staking, HyperEVM gas, spot trading, and tier-based trading discounts. Its HIP-1 definition sets a maximum supply of 1 billion units, while fee-driven burns remove units from supply through the assistance-fund mechanism.

Validator operation requires 10,000 HYPE of self-delegation, and that self-delegation remains locked for 1 year. A delegation to a validator has a 1-day lock before it can be removed. Transfers from staking back to the spot balance enter a 7-day unstaking queue, and each address can have at most 5 pending withdrawals. Rewards accrue each minute, distribute daily, and automatically redelegate. Those timings make liquid HYPE, staked HYPE, and HYPE used for gas economically related but operationally distinct balances.

Wallet custody and recovery choices

Wallet custody determines who can authorize trades and how account access is restored. MetaMask and Rabby expose standard EVM accounts, while Ledger and Trezor keep signing keys in hardware; the email-created wallet offers a private-key export for portability.

BIP-39 defines 5 valid mnemonic lengths: 12, 15, 18, 21, or 24 words. A compatible seed restores the underlying wallet, not a special exchange username. An EVM address itself is 20 bytes, but knowing the address provides observation only; trading authority comes from the key or an explicitly authorized agent key.

Wallet custody and recovery choices
Access route Backup or recovery standard
Browser EVM wallet BIP-39 mnemonic or imported private key, as configured by the wallet
Hardware wallet Device-generated BIP-39 seed restored through compatible hardware
Email-created embedded wallet Exported EVM private key for portable account recovery

Agent wallets can sign trading actions without exposing the master key to an automated strategy, but their authorization remains active until revoked. Losing every valid recovery secret leaves no protocol-level password reset, so the selected access route needs an independent, readable backup.

From trading venue to programmable financial stack

The protocol's development sequence moved from native exchange functions toward token issuance and general smart-contract composition. Hyperliquid concentrated matching, margin, and settlement in HyperCore, then extended that state with HYPE staking, HIP standards, and HyperEVM applications.

HIP-1 defines capped-supply fungible assets and native spot books; its human-readable token name is limited to 6 characters, and size decimals must sit at least 5 places below unit decimals. HIP-2 supplies automated on-chain quoting for USDC pairs. HIP-3 opens perpetual-market deployment to builders who define the contract, oracle, leverage limits, and settlement process. HyperEVM then gives Solidity applications access to the same consensus domain, with HYPE serving as gas. The sequence explains why the project resembles both an exchange and application infrastructure.

Order books or liquidity pools: choosing an alternative

The main alternatives differ in where orders meet liquidity and which chain holds collateral. Hyperliquid's defining combination is a native Layer 1 with fully on-chain, price-time-priority books for both perpetuals and spot.

dYdX Chain also presents an order-book workflow, but its short-term orders live in validator memory unless filled, while stateful orders are committed on-chain. GMX routes perpetual trades against GM and GLV liquidity pools using oracle-based pricing on networks including Arbitrum, Avalanche, and MegaETH. Jupiter Perps uses the JLP pool on Solana, giving pool liquidity rather than a resting central-limit-order book. Uniswap remains a spot automated-market-maker alternative when leverage and perpetual funding are unnecessary.

A trader who values visible bids, asks, post-only placement, and direct price priority has a clear reason to prefer the HyperCore design. Pool-based venues shift the decision toward collateral composition, oracle execution, utilization, and liquidity-provider exposure. Chain support, available markets, order controls, custody workflow, and margin model are more durable selection criteria than a temporary fee promotion or headline volume figure.

Are subaccounts counted toward the master account's fee tier?

Yes, subaccount volume counts toward the master account's fee tier. Activity rolls into the master account's 14-day weighted volume, and the master account and its subaccounts share one tier. Vault volume is treated separately, so vault activity does not merge with the wallet's ordinary trading calculation. Spot volume retains its protocol-defined 2× weighting when the shared tier is determined.

Do HIP-1 tokens automatically appear as ERC-20 assets?

No, a HIP-1 token is a native HyperCore asset rather than an ERC-20 contract. Builders may deploy a corresponding ERC-20 representation on HyperEVM and link it through the protocol's native-transfer process. The linked forms then move between the two execution environments, but deploying one standard does not independently create the other. Wallet interfaces must also recognize the HyperEVM contract before displaying that representation.

Are HLP vault profits guaranteed?

No, HLP vault profits are not guaranteed. The vault runs market-making and liquidation strategies whose positions produce gains and losses as markets move. A depositor owns a proportional share of the resulting vault equity, subject to the vault's withdrawal mechanics. HLP is a protocol vault, so it does not charge the 10% owner profit share that applies to user-managed vaults.

What happens if a TWAP order finishes with unfilled size?

Any unfilled TWAP quantity remains unexecuted when the scheduled duration ends. The algorithm sends suborders every 30 seconds and limits each slice to 3% slippage. If earlier slices fall behind, later ones attempt to catch up but cannot exceed 3× the normal suborder size. Thin liquidity or a fast-moving book can therefore leave the completed parent order smaller than its original target.

Is identity verification stored in a HyperCore account?

No, a HyperCore account is represented on-chain by an EVM address rather than an identity record. The controlling wallet or an authorized agent key signs account actions. Eligibility to use a particular interface remains a separate matter governed by that interface's access rules and jurisdiction settings. Possession of a compatible address therefore establishes technical control, not automatic eligibility for every product or region.

Does the trading API provide WebSocket market data?

Yes, HyperCore API servers provide WebSocket streams alongside REST-style information requests. WebSocket subscriptions support continuously changing data such as order books, trades, and account updates, while request-response calls handle snapshots and history. Signed trading actions go to an API server and are forwarded into HyperBFT consensus. HyperEVM contract interactions use Ethereum-compatible JSON-RPC methods as a separate interface.