Markets, accounts and order controls
Sections ↑Hyperliquid combines spot and perpetual order books within HyperCore, the trading component of its own blockchain. HyperEVM is the separate general-purpose smart-contract environment connected to that system. Orders, cancellations and liquidations are recorded by the chain; using an application built on HyperEVM can add another developer, contract and set of permissions to the route.[2]
Trading scope and account configuration
| Service or mode | How it operates |
|---|---|
| Native perpetuals | Contracts have no scheduled expiry. Most use USDC collateral against a USDT-derived underlying price, without adjusting profit and loss for the USDC/USDT exchange rate; the specification describes this as a quanto arrangement.Source 8 |
| Spot trading | A deposited spot asset must be sold for the relevant quote token before it supplies that trading balance. The token and network shown in the deposit flow matter; a spot ticker is not proof of unrestricted native-chain delivery.Source 5 |
| Unified account | One balance per collateral asset supports spot trading and cross-margin positions using that asset across supported DEXs. A USDT balance does not automatically become USDC.Source 16 |
| Manual / Standard | Spot, perpetual and individual DEX balances remain separate. Cross margin applies within each DEX.Source 16 |
| Portfolio margin | Eligible spot assets and cross-margin positions share portfolio risk. Current collateral includes HYPE, BTC, USDC and USDT; borrowing can occur automatically.Source 16 |
| Builder-deployed markets | HIP-3 deployers define contracts, oracles and leverage and can halt a market, cancel its orders and settle positions at the current mark price. These powers belong to the relevant deployer.Source 34 |
Orders and execution conditions
| Instruction | Documented behaviour |
|---|---|
| Market / limit | Market orders seek immediate execution; limit orders specify a price or better. Good-till-cancelled, immediate-or-cancel and post-only instructions control the treatment of unfilled amounts. Reduce-only prevents an instruction from adding reverse exposure.Source 6 |
| Time-weighted execution | TWAP supports five minutes to seven days and a US$100 minimum. Suborders have 3% maximum slippage and intervals of at least 30 seconds; missed slices can leave the total incompletely executed.Source 6 |
| Attached TP / SL | The mark price triggers the exit. Market exits have 10% slippage tolerance; a chosen limit controls execution price but can remain unfilled after a gap. Fixed-size exits do not automatically resize with a changing position.Source 7 |
| Partially filled parent order | If the trader cancels the remainder, its child TP/SL instructions are also cancelled. The partial position needs a separately submitted exit. The documented insufficient-margin cancellation branch treats children differently.Source 7 |
| Chase order | The browser repeatedly reprices a post-only order. Closing or refreshing that tab, disconnecting, switching address or connecting the address in another browser terminates the chase. This is a material exception to chain-held order persistence.Source 29 |
Order capacity and precision are separate restrictions. The default ceiling is 1,000 open orders, rising by one per additional USDC5 million traded to a 5,000 maximum. At 1,000 existing orders, new reduce-only or trigger orders are rejected. Filling the ordinary-order allowance can therefore remove capacity needed for a protective instruction.[12]
The specification caps market orders at US$30 million, US$5 million, US$2 million or US$500,000 according to the instrument’s maximum-leverage band; limit-order ceilings are ten times those amounts. Price precision permits five significant figures subject to decimal limits, with an integer-price exception. Quantity precision comes from each asset’s szDecimals metadata.[8][36]
Trading fees, funding and other charges
Sections ↑Tiers use rolling 14-day weighted volume, assessed daily in UTC: perpetual volume plus twice spot volume. The table shows base rates before modifiers.[4]
Base trading rates, percentage of executed notional
| 14-day weighted USD volume | Perps maker | Perps taker | Spot maker | Spot taker |
|---|---|---|---|---|
| Base | 0.015% | 0.045% | 0.040% | 0.070%Source 4 |
| Above 5 million | 0.012% | 0.040% | 0.030% | 0.060%Source 4 |
| Above 25 million | 0.008% | 0.035% | 0.020% | 0.050%Source 4 |
| Above 100 million | 0.004% | 0.030% | 0.010% | 0.040%Source 4 |
| Above 500 million | 0% | 0.028% | 0% | 0.035%Source 4 |
| Above 2 billion | 0% | 0.026% | 0% | 0.030%Source 4 |
| Above 7 billion | 0% | 0.024% | 0% | 0.025%Source 4 |
HYPE staking tiers discount fees by 5%–40%, beginning above 10 HYPE and reaching the maximum above 500,000 HYPE. HIP-3 deployer shares, growth mode, aligned quote assets and quote-token pairs change the effective rate; the base tariff is not universal.[4]
An application can also collect a separately approved builder fee, capped at 0.1% on perpetuals and 1% on spot. It applies to both perpetual sides but not the buying side of spot. The main wallet approves each builder’s maximum; revocation stops that approval. These charges are distinct from the deployer component of a HIP-3 market.[22]
Perpetual funding transfers value between long and short holders each hour; Hyperliquid takes no fee from that payment. The calculation combines a fixed interest component with the contract premium, and uses underlying oracle value rather than mark-price value for the payment base. The published absolute cap is 4% per hour, not a typical expected rate.[11]
For a hypothetical US$20,000 oracle-valued position and a positive 0.01% hourly funding rate, the long pays USDC2 for that interval. Holding it for six identical intervals would cost USDC12. Actual rates and notional change; this illustration excludes trading fees, price movements, builder charges and borrowing interest.[11]
Portfolio margin adds borrowing economics. Insufficient settlement-token balance can create a loan against eligible collateral; HYPE and BTC have published loan-to-value ratios of 0.65 and 0.50. Interest accrues continuously and is indexed hourly. The stablecoin rate depends on utilisation, while the protocol retains 10% of borrowed interest as a liquidation buffer. The displayed lending yield must not be treated as a fixed cash-account rate.[21]
Deposits, withdrawals and transferable balances
Sections ↑Funding routes and the relevant service provider
| Route | Conditions and practical consequence |
|---|---|
| Wallet connection | Connect an EVM wallet and sign Enable Trading. The direct USDC wallet flow uses Arbitrum; source-chain gas is needed for depositing even though ordinary HyperCore trading is gas-free.Source 5 |
| Email USDC deposits | The documented Across-managed flow accepts USDC on Arbitrum, Base, Ethereum and Polygon. Below USDC5, funds are redirected to the email wallet; below USDC1, they are lost.Source 27 |
| Wrong token or network | The email-flow guide describes automatic redirection of unsupported deposits within ten minutes, with wallet export needed to recover them. This is specific to that deposit address and does not promise recovery for every incorrect blockchain transfer.Source 27 |
| Direct wallet minimum | The wallet-connected USDC guide says deposits below USDC5 are lost. Its threshold must not be substituted with the different email-flow rule.Source 27 |
| Fiat purchase | Swapped.com supplies the independent fiat on-ramp. Its payment eligibility, quote and support apply; the inspected Hyperliquid page does not establish a direct bank account or a corresponding fiat cash-out facility.Source 26 |
| Cross-chain withdrawal | Use Withdraw and review the chosen chain, cost and expected duration. Send moves tokens between Hyperliquid addresses; it is not a withdrawal to another blockchain.Source 25 |
USDC is now natively minted on Hyperliquid, with Circle’s HyperEVM contracts and CCTP transfer routes. The current documentation says the legacy Arbitrum bridge holds less than 10% of HyperCore’s USDC supply. Earlier accounts centred entirely on that bridge no longer describe the full USDC route.[15]
For an outstanding transfer, Portfolio → Deposits & Withdrawals distinguishes pending, completed and failed actions. A completed action has an explorer link for checking its recipient. A failed BTC, ETH or SOL route may require the independent Unit team. The current withdrawal guide uses the estimate in the withdrawal window, so no single fixed settlement deadline is established across networks.[25]
Account equity is not the same as removable margin. For a transfer out of a cross account or isolated position, remaining margin must meet both initial-margin requirements and 10% of total open-position notional. This restriction also covers moves to spot and isolated-margin transfers. A realised gain can therefore remain unavailable for withdrawal while exposure remains open.[9]
Asset control, collateral and loss allocation
Sections ↑Self-custody means the signing key controls the address; it does not eliminate the contracts, consensus or collateral rules used by a trade. The audit page identifies Zellic work on the legacy bridge and separately points to Circle contract audits. These are defined technical reviews, not an audited balance sheet, a per-customer insurance policy or a guarantee against trading loss.[20]
Exposure and loss-handling mechanisms
| Mechanism | What can happen |
|---|---|
| Cross margin | Collateral supports the account’s other cross positions. Isolated margin confines collateral to the chosen position; strict-isolated assets also prohibit removing margin before proportional position closure.Source 9 |
| Order-book liquidation | When equity breaches maintenance requirements, liquidation seeks execution on the book. A successful partial close can leave residual collateral. Mark price, funding and other cross positions can change the displayed liquidation estimate.Source 10 |
| Backstop liquidation | Below two-thirds of maintenance margin, the liquidator vault can take over the affected positions and margin. In cross mode this can consume the cross account’s equity. There is no separate clearance fee, but retained maintenance margin can be lost.Source 10 |
| Auto-deleveraging | If an account becomes negative, opposite-side traders are ranked by unrealised profit and leverage and may have positions closed against it at the previous mark price. A profitable open position is therefore still exposed to forced close-out.Source 35 |
| HIP-3 deployer stake | Validators can slash a deployer for specified misconduct or operational failures. Slashed stake is burned rather than distributed to affected users; it is not a compensation fund available to each trader.Source 34 |
The compromised-wallet guide treats an exposed address as permanently unsafe. It directs users to secure a new wallet, move remaining assets and revoke permissions; a support ticket cannot make an exposed signing key safe again. HyperEVM assets may need separate attention even when HyperCore access has been changed by an unauthorised multisig.[23]
Access restrictions and account continuity
Sections ↑The 15 June 2026 interface terms exclude US and Ontario persons/entities, relevant sanctioned territories and their citizens. Outcome markets have additional exclusions. Access must comply with local law; location-masking does not create eligibility.[1]
Subaccounts become available after US$100,000 volume: initially up to ten, with further US$100 million increments unlocking more to a fifty-account maximum. They share the master’s fee tier, but not referral discounts. This is an operational threshold rather than a separate retail or institutional regulatory classification.[17]
Portfolio margin requires a master account above US$5 million weighted volume or US$10,000 account value, with value below US$25 million. Asset-level supply and borrowing caps also apply; hitting a cap can cause fallback to non-portfolio behaviour. Eligibility for the mode does not ensure that every intended loan can be created.[21]
The reviewed schedules do not establish a periodic inactivity debit. Separately, an API agent can expire or be pruned after deregistration or when its registering account has no funds. That is an authorisation lifecycle, not a published account-wide dormancy charge.[13]
Support, outages and disputes
Sections ↑Published assistance routes
Scope Ticket form; files and images cannot be received or viewed.
Scope Use open-ticket → Create ticket; support is inside the ticket channel.
Support warns that a reply may take up to 48 hours, longer over weekends. This channel is not documented as an emergency dealing desk with authority to close a position. Queries about independently developed HyperEVM applications go to that application’s team.[14]
The status page separates frontend, blockchain and API. On 20 October it reported all operational; its 10 October network upgrade ran from 08:15 to a completion notice at 08:35 UTC. A working website alone does not establish that a blockchain order has been accepted.[38]
For API interruptions, the WebSocket documentation requires reconnection and reconciliation of missed data using the returned snapshot or an information request. An unconfirmed display should be checked against actual order status before another instruction is submitted.[37]
The terms require dispute notice within 30 days, including identity, issue and requested remedy. After 30 days without informal resolution, they specify individual LCIA arbitration in London, in English, subject to stated exceptions. Contractual liability is capped at US$100, subject to applicable law.[1]
Regulatory scope of the interface and protocol
Sections ↑Hyperliquid Corp.’s terms expressly disclaim governmental licensing or registration of the interface and Hyperliquid. This is the provider’s statement, not a firm-register verification.[1]
Permissionless market deployment is a technical permission within HyperCore. A deployer selects its contract, oracle and settlement operations; that ability does not establish regulatory permission to offer the product to every visitor. The same app can therefore surface markets with different operating responsibilities.[34]
Operator, development and scale
Sections ↑Hyperliquid Corp. provides the reference interface; its incorporation jurisdiction was not established in the inspected terms.[1]
The contributor account identifies Hyperliquid Labs, led by Jeff and iliensinc, and traces the team from proprietary market making in 2020 to DeFi development in 2022. Labs says it is self-funded without external capital. This development-team account is distinct from identifying the interface contracting company or every application built on the chain.[3]
DefiLlama’s 20 October snapshot showed approximately US$208.6 billion in trailing 30-day perpetual notional and US$4.08 billion in spot turnover. These are different measures; the former includes leverage. Neither is a verified count of individual traders, and combined protocol statistics should not be attributed solely to one interface.[39]
Current documentation supports unified, portfolio and Standard modes and discontinues DEX abstraction. Older screenshots can therefore misrepresent the balance aggregation of a newly unified account.[16]
- Operator
- Hyperliquid Corp. — reference interface
- Exchange model
- Decentralised
- Service scope
- HyperCore order books, account modes and associated interfaces; independent builders have additional responsibilities.
- Client types
- Not established
- Pricing publication
- Public pricing
- Pricing scope
- 14-day tiers with product, collateral and builder modifiers.
- Funding scope
- Crypto network-specific routes; Swapped.com supplies the separate fiat on-ramp.
- Custody and asset handling
- Wallet signing plus chain, collateral and independent application controls; no insured per-client balance established.
- Client eligibility
- US, Ontario and sanctions exclusions apply to the reference interface.
- Support
- Official ticket routes; independent application and payment support are separate.
- Authorisation and registration scope
- Interface terms disclaim governmental licensing or registration.
Exchange metadata checked 20 Oct 2026Source 2Source 1Source 20Source 26Source 14Source 4Source 5
Vaults, staking, records and automation
Sections ↑Additional services and exit conditions
| Service | Scope and withdrawal consequence |
|---|---|
| HLP | The protocol vault runs market-making and liquidation strategies, supplies USDC in Earn and shares profits or losses. Each new deposit resets a four-day withdrawal lock. A vault balance is investment exposure, not unconditionally available cash.Source 31 |
| Legacy trader vaults | Depositors share the leader’s strategy rather than receiving separately copied positions in their own account. The legacy guide describes a one-day lock and 10% profit share to the leader; withdrawal can close exposure and incur slippage.Source 30 |
| Newer HyperEVM vaults | Builders can create custom accounting, tokenised shares and authorised trading agents through CoreWriter. The legacy one-day/10% terms must not be assumed for every independently built vault.Source 18 |
| HYPE staking | Delegation has a one-day lock. Moving undelegated HYPE from staking to spot uses a separate seven-day queue, with at most five pending withdrawals. Validator commission and daily automatically redelegated rewards affect the outcome.Source 32 |
| Historical points | The initial points phase ended in May 2024 and the L1 phase in November 2024. Those historical programmes do not establish a current withdrawable signup bonus.Source 33 |
The official history guide links an independently maintained Enigma exporter. Its market-data archive is approximately monthly, requester-paid and may have gaps; it is not a promise of complete tax-ready statements. Keep transaction and funding records together with the wallet addresses and networks needed to interpret them.[28]
API agents sign for a master account or its subaccounts; public account queries use the actual account address rather than the agent address. Replacing or expiring an agent changes signing authority. It does not itself reverse a filled position, so outstanding instructions and exposure require separate reconciliation. The guide cautions against reusing pruned agent addresses because signed actions can become replayable.[13]
The API provides an explicit scheduled cancel-all mechanism: its time must be at least five seconds ahead, with up to ten triggers per UTC day. It cancels open orders, not existing positions. This control has to be configured; merely closing the bot or browser does not request it.[19]
IP limits include 1,200 weighted REST units per minute and ten WebSocket connections. Address action allowances are separately volume-based. Unified and portfolio modes also impose 50,000 daily user actions. An algorithm must account for both classes of limit, including spare capacity for cancellation.[12][16]
The documentation uses “agent wallet” for delegated signing authority. That term does not establish an AI adviser or a managed strategy; the authority granted to an external tool must be assessed separately from whatever analysis it displays.[13]
Sources & further reading
- Interface terms, 15 June 2026 Hyperliquid · Accessed 20 Oct 2026
- HyperCore and HyperEVM Hyperliquid · Accessed 20 Oct 2026
- Core contributors Hyperliquid · Accessed 20 Oct 2026
- Trading fee schedule Hyperliquid · Accessed 20 Oct 2026
- Trading and funding entry routes Hyperliquid · Accessed 20 Oct 2026
- Order types and validity Hyperliquid · Accessed 20 Oct 2026
- Attached exit orders Hyperliquid · Accessed 20 Oct 2026
- Contract specifications Hyperliquid · Accessed 20 Oct 2026
- Margin modes and withdrawals Hyperliquid · Accessed 20 Oct 2026
- Liquidation mechanics Hyperliquid · Accessed 20 Oct 2026
- Perpetual funding methodology Hyperliquid · Accessed 20 Oct 2026
- API and user limits Hyperliquid · Accessed 20 Oct 2026
- API wallet authority Hyperliquid · Accessed 20 Oct 2026
- Official support guide Hyperliquid · Accessed 20 Oct 2026
- Native USDC and legacy bridge Hyperliquid · Accessed 20 Oct 2026
- Account abstraction modes Hyperliquid · Accessed 20 Oct 2026
- Subaccount eligibility Hyperliquid · Accessed 20 Oct 2026
- HyperEVM and legacy vaults Hyperliquid · Accessed 20 Oct 2026
- Order and cancellation API Hyperliquid · Accessed 20 Oct 2026
- Published audit scope Hyperliquid · Accessed 20 Oct 2026
- Portfolio margin and borrowing Hyperliquid · Accessed 20 Oct 2026
- Builder fee permissions Hyperliquid · Accessed 20 Oct 2026
- Compromised wallet procedure Hyperliquid · Accessed 20 Oct 2026
- Missing email verification codes Hyperliquid · Accessed 20 Oct 2026
- Tracing a withdrawal Hyperliquid · Accessed 20 Oct 2026
- Fiat on-ramp support Hyperliquid · Accessed 20 Oct 2026
- USDC deposit exceptions Hyperliquid · Accessed 20 Oct 2026
- Historical data and exports Hyperliquid · Accessed 20 Oct 2026
- Browser-dependent chase orders Hyperliquid · Accessed 20 Oct 2026
- Legacy vault withdrawals Hyperliquid · Accessed 20 Oct 2026
- HLP protocol vault Hyperliquid · Accessed 20 Oct 2026
- HYPE delegation and unstaking Hyperliquid · Accessed 20 Oct 2026
- Historical points programmes Hyperliquid · Accessed 20 Oct 2026
- Builder-deployed perpetuals Hyperliquid · Accessed 20 Oct 2026
- Auto-deleveraging Hyperliquid · Accessed 20 Oct 2026
- Tick and lot precision Hyperliquid · Accessed 20 Oct 2026
- WebSocket reconnection Hyperliquid · Accessed 20 Oct 2026
- Service status and maintenance Hyperliquid · Accessed 20 Oct 2026
- Protocol turnover snapshot DefiLlama · Accessed 20 Oct 2026
This profile reports dated public information, including exchange-published services and terms. It does not independently test or guarantee trading, custody, pricing or withdrawals. Inclusion is not an endorsement. Permissions and protections apply only to the named legal entity, service and client category; check the current official records and your contract.
Report an error or submit an update