Hyper liquid is a Trading-First Layer 1 Where Margin Rules Define Risk

Trading fees before the first order

Day to day, Hyper liquid charges separate maker-and-taker schedules for perpetuals and spot, using a rolling 14-day volume tier assessed at the end of each UTC day. Before volume or staking discounts, the perpetual base rate is 0.045% for takers and 0.015% for makers. The corresponding spot rates are 0.070% and 0.040%. A maker rests liquidity on the book, while a taker immediately trades against an existing order.

Spot volume receives a 2x weighting when the shared fee tier is calculated, and sub-account activity contributes to the master account's tier. HyperCore trading actions do not require a separate gas payment, which keeps order placement and cancellation distinct from blockchain transfer costs. Depositing USDC through Arbitrum requires ETH for Arbitrum gas, while a USDC withdrawal to Arbitrum carries a fixed $1 protocol fee.

Order books, validator memory, or oracle-priced pools?

The central choice among Hyper liquid, dYdX Chain, and GMX concerns where matching and liquidity live. HyperCore records its order books in Layer 1 state and matches orders by price-time priority. dYdX Chain, built with the Cosmos SDK and CometBFT, keeps short-term orders in validator memory for up to 20 blocks before expiry, while completed fills enter consensus state. Both expose recognizable bid-and-ask markets, but their storage paths differ.

GMX follows another model: GM and GLV pools supply liquidity, while Chainlink Data Streams provide oracle prices and pool imbalance influences price impact. It has no central limit order book or queue position. Binance offers familiar order-book execution through a centralized account and custody model. HyperCore is the relevant alternative when self-custody, transparent book state, and native matching belong in the same settlement system.

What actually settles on HyperCore?

HyperCore is the native trading engine inside the Layer 1, holding order books, positions, margin balances, and liquidation state. The chain has 2 connected execution components: HyperCore for financial primitives and HyperEVM for general smart contracts. HyperBFT, a proof-of-stake consensus design inspired by HotStuff, gives both components the same ordered state and security model.

Every asset book accepts prices in valid tick increments and sizes in valid lot increments, then matches compatible orders by price and arrival time. Margin is checked when an order opens and checked again when the resting side matches, so an earlier oracle move cannot bypass collateral rules. Within a block, cancels are handled before actions that submit Good Til Cancel or Immediate or Cancel orders. HyperEVM remains part of the same chain rather than operating as an external rollup.

From order instruction to verified fill

An order on HyperCore moves from a signed instruction into the consensus-ordered book, where its type determines whether it rests, fills, or cancels. A Good Til Cancel limit order remains available until execution or cancellation. Immediate or Cancel removes any unfilled remainder, and Add Liquidity Only rejects an instruction that would immediately take liquidity. Reduce Only prevents a closing instruction from increasing or reversing the position.

Perpetual orders must meet a $10 minimum notional, while spot orders require at least 10 units of the quote token. Prices accept up to 5 significant figures, subject to no more than 6 decimal places for perpetuals or 8 for spot and the asset's size-decimal setting. These precision rules explain why a visually sensible price sometimes fails validation.

Time-weighted average price orders divide a larger instruction into suborders sent every 30 seconds. Each suborder has a 3% maximum-slippage constraint. When earlier slices fall behind, later slices may grow, although each remains capped at 3 times the normal suborder size. Verification therefore means checking filled size, average execution price, remaining order quantity, fees, and the resulting position rather than treating submission as execution.

Funding the account without mixing networks

The simplest Hyper liquid funding path starts with an EVM account, USDC on Arbitrum, and enough ETH to pay the deposit transaction's network gas. Connecting the wallet and enabling trading uses a signature; the deposit itself moves USDC through the native Arbitrum bridge. An Arbitrum USDC deposit must reach the 5 USDC minimum, and another token sent through that route does not become trading collateral.

Email access creates a blockchain address after a 6-digit code check, while wallet access preserves control through the connected signer. After the balance appears, distinguish USDC held for spot from USDC available to perpetuals, because the two balances serve different accounting systems. The initial order should use a deliberately small notional, a chosen margin mode, and an order type whose fill behavior is already understood.

Cross margin, isolated margin, and the liquidation boundary

Cross margin is the default mode and shares collateral across every cross position in the account, so profit or loss in one market changes the buffer supporting the others. Isolated margin confines allocated collateral and position risk to one market. Leverage is selectable in whole-number steps from 1x to that asset's maximum, and opening margin equals position notional divided by the chosen leverage.

Maintenance margin defines the liquidation boundary and equals half the initial-margin rate at the market's maximum leverage. For a market capped at 20x leverage, the initial fraction at maximum leverage is 5% and the maintenance rate is 2.5%. Removing collateral also leaves at least the greater of the initial-margin requirement or 10% of total open notional. Consequently, available balance and account equity are not interchangeable figures.

Liquidation begins when account equity falls below the applicable maintenance requirement, using mark price rather than the latest individual trade. For a liquidatable position above 100,000 USDC in notional, the first market liquidation order targets 20% of the position. A 30-second cooldown follows a partial liquidation, and a failed book liquidation below two-thirds of maintenance margin moves to the HLP liquidator vault. HyperCore charges no separate liquidation clearance fee.

Hourly funding keeps perpetuals near spot

Funding on perpetual positions transfers value directly between longs and shorts every 1 hour, encouraging the contract price to track its underlying spot market. A positive rate means longs pay shorts; a negative rate reverses that direction. The formula computes an 8-hour rate and applies one-eighth each hour, with a fixed interest component of 0.01% per 8 hours, equivalent to 0.00125% hourly.

The premium component measures order-book impact prices against the oracle price. Samples arrive every 5 seconds and are averaged across the hour, while the interest-minus-premium adjustment is clamped between -0.05% and 0.05%. The final funding rate is capped at 4% per hour, and the payment uses oracle-priced position notional. Funding changes account balance continuously, so it also changes the distance to liquidation during a long-held leveraged position.

Spot trading, perpetual exposure, and programmable liquidity

Across most deployments, HyperCore supports spot ownership, leveraged perpetual exposure, and protocol-managed liquidity through separate accounting paths. Spot execution exchanges native assets through order books, whereas perpetuals create long or short exposure without an expiry date. HLP, the Hyperliquidity Provider vault, runs market-making and liquidation strategies, supplies USDC to protocol functions, and receives part of trading fees. Its deposit lock lasts 4 days from the most recent deposit.

Crucially, HyperEVM extends those trading primitives into Ethereum Virtual Machine applications under the same HyperBFT consensus. Mainnet uses chain ID 999, and HYPE is the native gas asset with 18 decimals on HyperEVM. Its fee market implements EIP-1559; both base fees and priority fees are burned. Builders gain an EVM environment near HyperCore liquidity, while users must keep HyperCore spot balances, perpetual collateral, and HyperEVM gas balances operationally distinct.

A decision checklist for this trading design

The Hyper liquid design fits traders who require self-custody with central-limit-order-book behavior, as well as builders placing EVM applications beside native trading liquidity. Match the mechanism to the intended workflow before transferring capital:

• Order-book execution: require visible bids, asks, spreads, and price-time priority before selecting HyperCore.
• Margin containment: select isolated margin when one position must remain separate from the cross-collateral pool.
• Funding tolerance: compare the hourly funding direction with the planned holding period before opening a perpetual.
• Vault access: treat HLP capital as unavailable for 4 days after the most recent deposit.
• Application use: keep HYPE on HyperEVM when an EVM action requires gas on chain ID 999.

Position maintenance after the fill

Position maintenance on HyperCore centers on mark price, liquidation price, funding, free collateral, resting orders, and realized fees. Cross-margin estimates move when another cross position changes, while isolated positions accept explicit margin additions or removals. A stop-market trigger becomes a market order, so the available book still determines its execution price. Reduce Only is the appropriate instruction when a close must never create exposure in the opposite direction.

Automated traders also need signer discipline. An API wallet signs for a master account or sub-account, but account queries must use the actual trading address rather than the agent address. The protocol stores the 100 highest nonces for each signer, and a new nonce must fall between 2 days before and 1 day after the block timestamp. Routine reconciliation should compare fills, funding transfers, fee deductions, collateral, and every remaining Good Til Cancel order after each trading session.