Hyper liquid

Hyper liquid moves trading funds through deposits, execution and withdrawals

Hyper liquid credits deposits, executes orders and processes withdrawals subject to account obligations. Following the money means distinguishing an external transfer from a usable balance, an accepted order from a fill and a withdrawal request from receipt at the destination. Fees, funding payments and open positions can change what remains available. The account mode also matters because it determines whether spot and perpetual balances share collateral or occupy separate balances.

Last updated

A trading balance becomes withdrawable only when account obligations permit the transfer, and the withdrawal completes when the destination receives funds.

The receiving balance determines the funding path

The deposit must reach the balance the intended trade can use. A compatible token at the same wallet address in another execution environment does not establish that trading funds have arrived.

Transfers into HyperCore

HyperCore maintains trading balances, while HyperEVM runs smart contracts. CCTP, the Cross-Chain Transfer Protocol, supports transferring USDC through HyperEVM into HyperCore. A transfer configured only for receipt on HyperEVM leaves a different balance from a completed HyperCore deposit. Funding records therefore need the receiving environment as well as the recipient address. The legacy Arbitrum bridge is deprecated, so its instructions and historical timing should not describe every deposit.

Deposited spot assets

Supported deposits can also arrive as spot assets. If the account lacks the required quote or collateral asset, a conversion may be necessary. Eligible portfolio margin accounts can instead borrow against supported collateral, subject to borrowing limits. A conversion trade creates its own fill and fee records. Account mode then determines how the resulting balance interacts with perpetual positions: unified accounts share a balance for each asset, while standard accounts separate spot and perpetual balances.

A confirmed debit precedes a credited deposit

A successful transaction on the sending chain establishes that the source action occurred. Crosschain receipt requires the remaining transfer operations to complete. For a CCTP deposit directed to HyperCore, these include attestation, minting on HyperEVM and forwarding into the trading balance. The source transaction and destination credit belong to the same transfer, but they record different events. Retain the transaction identifier, intended recipient and received amount together; forwarding charges can explain a difference between the sent and credited amounts.

A confirmed debit precedes a credited deposit: A successful transaction on the sending chain establishes that the source action occurred. Crosschain receipt requires the remaining transfer operations to complete. For a CCTP deposit directed to HyperCore, these include attestation, minting on HyperEVM and forwarding into the trading balance. The source transaction and destination credit belong to the same transfer, but they record different events. Retain the transaction identifier, intended recipient and received amount together; forwarding charges can explain a difference between the sent and credited amounts.

View image file

An accepted order can still leave funds committed

Order acceptance establishes that an instruction entered the trading system. Execution depends on its price conditions, available liquidity and execution options. These parameters determine whether an unfilled quantity can remain active.

Order parameter Supported setting or behavior Execution and position limits
Limit price Execution at the selected limit or better A submitted order does not establish a fill
Good till cancel GTC Unfilled quantity can remain on the book
Post only ALO Execution occurs only as a resting order
Immediate or cancel IOC Unfilled quantity is cancelled
Reduce only Position reduction The order cannot open an opposite position

Cancellation stops the remaining instruction; it does not reverse completed fills. A partially executed order can therefore leave both a changed position and a cancelled remainder. Record the executed quantity separately from the order’s final status.

An accepted order can still leave funds committed: Cancellation stops the remaining instruction; it does not reverse completed fills.; A partially executed order can therefore leave both a changed position and a cancelled remainder. Record the executed quantity separately from the order’s final status.

View image file

Fills, fees and funding explain balance changes

Executed trades establish the quantity and price used to reconcile trading activity. The submitted quantity alone cannot explain an account change when an order fills partially or executes across several prices. Spot fills change token holdings. Perpetual fills change position exposure and the associated margin accounting.

Fees belong beside the fills that incurred them. Applicable schedules differ between spot and perpetual trading, and maker rebates can also affect the trading balance. For reconciliation, use the recorded charge or rebate instead of applying one assumed fee rate to every transaction.

Perpetual funding payments can change a position holder’s balance without a new trade. Funding transfers value between the two sides of a contract. Its direction depends on the funding rate, so the account may pay or receive it. A balance comparison covering an open position must include these payments alongside fills.

Open positions constrain the amount available to withdraw

The amount available for withdrawal reflects continuing collateral requirements. Displayed account value and withdrawable funds answer different questions.

Shared collateral after a position closes

Cross margin positions share collateral within the applicable account scope. Closing one position can leave other positions consuming that collateral, especially when they carry unrealized losses. The margin previously associated with the closed position therefore need not become fully available. Unified accounts and standard accounts differ in how cross margin extends across trading venues.

Restrictions on removing margin

Margin cannot be removed independently from strict isolated positions; it is released proportionally as the position closes. Other margin removal also remains subject to transfer requirements. A withdrawal rejected for insufficient available margin requires a smaller request or enough available margin before resubmission. Waiting alone does not guarantee that enough margin will become available. Reducing exposure may change available funds, but the execution price and remaining positions determine the new amount.

Withdrawal processing continues after the account debit

For CCTP withdrawals to an external EVM chain, the HyperCore debit starts a process that routes through HyperEVM before destination receipt. USDC is burned, the transfer receives an attestation and minting occurs on the destination chain. Automatic forwarding can complete delivery where the chosen configuration supports it. Custom hook data can require the recipient to handle message receipt instead.

The selected chain and method determine the applicable processing costs. The withdrawal amount must exceed the combined required fees, including forwarding where used. An accepted request with an outstanding destination operation differs from a rejected request with no accepted transfer. Before another submission, establish whether the original debit and transfer already exist. Creating a second request does not complete the first one.

Withdrawal processing continues after the account debit: For CCTP withdrawals to an external EVM chain, the HyperCore debit starts a process that routes through HyperEVM before destination receipt.; USDC is burned, the transfer receives an attestation and minting occurs on the destination chain.; Automatic forwarding can complete delivery where the chosen configuration supports it. Custom hook data can require the recipient to handle message receipt instead.

View image file

Reconciliation uses the account mode and transaction history

Reconciliation means explaining the ending balance using the opening balance and recorded changes. Unified and portfolio margin accounts report balances and holds in spot clearinghouse state; individual perpetual venue states do not provide a meaningful standalone balance view for those modes. Standard accounts require attention to their separate balances. Portfolio margin reconciliation must also include outstanding borrowing and interest paid or earned. Internal transfers must appear on both sides of the relevant records, without being counted again as new external funding.

Fill history, funding history and non-funding ledger updates cover different activity. The last category includes deposits, withdrawals, transfers and liquidations. Combining them explains changes a trade list alone would miss. For automated records, distinguish an initial subscription snapshot from later updates so existing entries are not counted twice.

A completed exit leaves no unintended exposure

Receipt at the destination completes a withdrawal. It does not establish that every trading position or outstanding order has ended.

A full trading exit also requires the intended positions to be closed and unwanted resting orders to be cancelled. A closing instruction can leave residual exposure when it fills only partially. Reduce-only execution prevents the closing instruction from opening an opposite position, but the resulting position size still determines whether exposure remains.

Match the destination receipt to the withdrawal record, including the asset, recipient and net amount. Keep any remaining trading balance distinct from funds already received elsewhere. That distinction leaves a concrete account of what exited, what remains available and what still supports an open position.

Useful questions about Hyper liquid

Can I withdraw USDC directly from a spot balance?

The CCTP withdrawal flow to external EVM chains supports USDC from either a HyperCore spot or perpetual balance. The request identifies the source balance, while account obligations still constrain the available amount. This support does not establish that every interface exposes both choices.

Does the first outbound transfer include an account activation charge?

A new HyperCore account funded through CCTP can incur its one-time activation charge on the first outbound action. The incoming deposit can be tradable before that charge is collected. Activation and transfer processing are separate costs, so a first withdrawal needs enough available funds for both applicable charges.

Is a HyperCore USDC balance the same as holding the token on HyperEVM?

A HyperCore balance represents protocol-level credits, while native USDC for the CCTP deposit arrangement remains in the deposit contract on HyperEVM. Withdrawal redeems the corresponding native USDC through the supported flow. This distinction matters when reconciling a trading balance with token transfers recorded in the smart contract environment.

Do I pay a separate blockchain gas charge for each trade?

Trading on Hyper liquid does not require a separate gas payment for each trade. Trading fees still apply, and depositing or withdrawing can involve gas or processing charges under the selected transfer method. These costs belong to different operations in the account history.

Will a single fill-history request retrieve every trade the account has made?

A single fill-history request does not guarantee the account’s complete trading history. API responses have result limits, and the time-based fill endpoint also limits how much recent history remains available. Regularly retained records can therefore cover activity a later request no longer returns.