Hyperliquid spot and perpetual trading on its own Layer 1
last updated
Hyperliquid runs spot and perpetual futures order books on its own Layer 1 blockchain, a network that processes and settles transactions. Spot trades exchange assets, while perpetual contracts create price exposure backed by collateral. Its HyperCore component handles matching and trading accounts; HyperEVM supports programmable applications on the same chain. A completed market action requires an execution record and the corresponding account change. Signing or submitting an order alone does not establish either result.
Key takeaway: An accepted order can remain unfilled, so execution records and the resulting balance or position determine whether a trade has completed.
Spot balances and perpetual positions
Spot and perpetual markets serve different purposes even when their order forms look similar. The distinction determines what the account holds after execution and which conditions govern its exposure.
Spot ownership
A spot purchase exchanges the quote asset for the selected base asset. The resulting balance represents that asset within the trading system. Its exact token identity matters, particularly when an interface uses a familiar display name for a wrapped asset. Holding a fully funded spot balance does not itself create a perpetual position or its funding obligations.
Perpetual exposure
A perpetual contract supports long or short exposure without delivering the underlying asset. Collateral backs the position, and profit or loss changes account equity. Funding payments help connect the contract price with its underlying reference. Ordinary perpetual contracts have no scheduled expiry, although market settlement can still occur under applicable rules.
Builder-deployed markets under HIP-3 use HyperCore trading infrastructure with additional operator responsibilities. The deployer defines the contract and oracle, sets permitted leverage, and can settle the market. Shared matching infrastructure therefore does not make every market’s collateral requirements or price feed identical.
HyperCore matching and HyperEVM applications
HyperCore matches orders using price-time priority. Better-priced orders take precedence, followed by earlier orders at the same price. The mechanism resembles centralized exchange matching, while the order books form part of blockchain state. HyperEVM supplies an Ethereum-compatible smart contract environment on the same network. Applications can interact with HyperCore through supported system interfaces. A balance in HyperEVM and a balance available for a HyperCore order remain distinct operational states, even though both environments share consensus.
Which balance can support a trade?
The account mode and selected market determine which balance can support a trade. A connected wallet establishes access; it does not establish available collateral. Onboarding supports wallet connections and email-based access, with deposit methods that depend on the interface. The destination environment and credited asset must match the intended trading use.
Standard accounts maintain separate spot, perpetual, and DEX balances. Unified accounts combine the spot balance of an asset with collateral for cross-margin positions using that asset. Portfolio margin combines eligible assets under portfolio-wide rules, subject to account eligibility requirements. An insufficient trading balance can trigger automatic borrowing against eligible collateral, creating debt that accrues interest. Once borrowing caps are reached, the user must supply additional margin in the settlement asset. These modes change the meaning of an available balance; holding an unrelated asset does not automatically satisfy every market’s collateral requirement.
Cross margin shares collateral within the scope that the account mode permits. Isolated margin allocates collateral to an individual position. Some markets impose stricter isolation rules, including restrictions on removing margin. Available buying power also differs from withdrawable funds because open positions must retain the required margin after a transfer.
Price limits and order instructions
The order instruction determines whether speed, a price boundary, or resting liquidity takes priority. Execution also requires sufficient balance or margin and compatible price and size increments.
Immediate execution and resting orders
Market orders seek immediate execution against available liquidity, so their fills can span different prices. A limit order sets the worst acceptable execution price. It can execute immediately when compatible orders exist, or remain open when its instructions permit resting. A limit price therefore controls price eligibility without guaranteeing a fill.
Good Til Cancel allows an unfilled order to remain on the book. Immediate or Cancel removes any portion that cannot execute immediately. Post Only prevents immediate matching and rejects an order that would take resting liquidity.
Position reduction and conditional orders
Reduce Only restricts an order to decreasing existing exposure. Take-profit and stop-loss orders add a trigger condition before their execution instructions become active. These controls address different questions: whether an order may increase exposure, when it activates, and what prices it may accept. Triggering alone does not establish that a position has closed.
Submission, fills, and the resulting account
An order response describes what happened to the instruction. A fill records an executed trade. Account balances and positions show the resulting exposure.
An open order has entered the system successfully but can still await execution. A partially filled order has already changed the account, even when some requested quantity remains outstanding. Cancellation stops the remaining instruction; it does not reverse earlier fills.
Execution records identify the traded instrument, direction, quantity, price, and charged fee. Multiple fills can belong to one order. Their combined quantity explains how much of the instruction actually executed, while weighting each fill price by its executed quantity gives the average execution price.
For spot trading, reconciliation concerns the assets exchanged and applicable fees. For perpetual trading, it concerns position size and direction, realized profit or loss, and remaining collateral. Other concurrent orders or account transfers can also affect the final state.
An order disappearing from the open-order list cannot distinguish a fill from a cancellation. A fully executed closing order also cannot establish a flat account when another action has changed the position.
Can trading continue after an uncertain closing order?
Trading can continue from a known position only after the closing order’s execution and the remaining exposure agree. Consider an attempted perpetual close whose confirmation disappears while the position display remains unclear. If the intended outcome was a full exit, the expected state is a zero position in that market.
Reading account records creates no additional exposure. Before placing another order, check the account and execution records:
- Confirm the selected account and market, including the account mode that governs its collateral.
- Check the closing order’s status and associated fills before submitting another instruction.
- Compare the executed quantity with the remaining position, accounting for other fills in the same market.
- Inspect outstanding orders that could change the position after the close.
- If exposure remains, confirm the remaining size and a valid Reduce Only instruction before another closing attempt.
A confirmed zero position satisfies the intended exit. A partial fill leaves exposure to manage. If the records disagree or remain unavailable, the closure remains unresolved; submitting another ordinary opposite-side order can create unintended exposure.
Trading costs and liquidation boundaries
Trading fees depend on the selected market and applicable maker or taker schedule. Account tiers, eligible discounts, and market-specific adjustments can change the charged rate. Slippage measures execution against the expected price and remains separate from the explicit fee. Perpetual funding rates affect payments between opposing positions while exposure remains open. A fee estimate alone therefore does not describe the economics of holding a position.
Hyperliquid uses the mark price to evaluate perpetual liquidation conditions. That reference can differ from the latest order-book trade. When equity falls below maintenance requirements, liquidation can reduce or close exposure. Cross-margin losses can affect other positions sharing that collateral. An estimated liquidation price can move as funding, collateral, or other positions change, so it is not a permanent boundary fixed at entry.
Public execution and control of the network
Onchain orders and account records make trading activity observable; wallet addresses do not provide transaction privacy. Network operation also depends on validators and their consensus rules. HYPE holders can delegate stake within HyperCore, while applications and vaults add separate contract or strategy dependencies. Public records help explain execution without removing those dependencies. A market order, vault deposit, and staking allocation produce different account states. The relevant completion condition changes when funds move from direct trading into a managed strategy or staking account.
Common questions about Hyperliquid
-
Do I need HYPE to pay gas for a HyperCore trade?
- Ordinary HyperCore trading does not require HYPE gas payments. Trading fees still apply, and deposits or withdrawals can involve costs associated with their route. HyperEVM transactions use HYPE for gas. The distinction follows the operation and execution environment, so a gas requirement for an application transaction does not describe an ordinary order-book trade.
-
Why does a valid-looking order price get rejected?
- An order price can fail validation when it does not match the market’s permitted price increment. Order size also has precision requirements, and minimum trade requirements can apply. A balance check cannot detect those formatting problems. The rejection reason distinguishes an invalid price or size from insufficient collateral, unavailable liquidity, or a market restriction.
-
Does a stop-loss limit order guarantee an exit?
- A stop-loss limit order does not guarantee an exit because execution still requires liquidity at an acceptable price. The mark price triggers the order, but the limit price governs matching. A rapid move can leave the triggered order resting without a fill. A stop-market order prioritizes execution within its applicable slippage protection rather than guaranteeing the trigger price.
-
What happens to attached protection when I cancel a partially filled parent order?
- Manually canceling a partially filled parent order also cancels its attached take-profit and stop-loss orders. The filled portion can therefore remain as a position without those attached instructions. A separate position-level protective order addresses that exposure. If insufficient margin causes cancellation after a partial fill, the system places the attached take-profit and stop-loss orders as though the parent had fully filled.
-
Can a TWAP finish without trading its entire requested size?
- A TWAP can reach the end of its duration without filling its entire requested size. It divides execution into scheduled suborders, each subject to execution constraints. Thin liquidity or a wide spread can prevent fills. Later suborders may attempt to catch up, but those attempts retain their limits and do not guarantee completion.
-
Which address should an API query use for account records?
- An account-data query should use the actual master account or subaccount address whose records it needs. Querying an authorized agent wallet can return empty results because the agent signs actions for a different account. Account mode also affects balance interpretation: unified and portfolio modes expose balances and holds through the spot clearinghouse state.
-
Are all Hyperliquid vaults able to trade the same markets?
- Vault capabilities differ between legacy HyperCore vaults and vaults implemented through HyperEVM contracts. Legacy HyperCore vaults do not support spot or HIP-3 trading. HyperEVM vaults can access those functions through supported system interfaces, subject to their own implementation. A vault’s strategy, permissions, and withdrawal rules therefore require separate consideration from direct order-book trading.
-
Is unstaked HYPE immediately available for spot trading?
- Undelegating HYPE and moving it back to a spot account are separate operations. After the delegation lockup permits undelegation, the balance returns to the staking account. A staking-to-spot transfer then passes through an unstaking queue. A visible staking balance therefore does not establish that the same amount is already available for a spot order.