Hyperliquid exchange setup is built around a 5 USDC Arbitrum minimum

Arbitrum remains the direct USDC entry route

For a regular user, Hyperliquid's broader deposit menu still leaves native USDC on Arbitrum One as the shortest direct collateral route.

The interface also lists BTC on Bitcoin, ETH and ENA on Ethereum, selected assets on Solana, MON on Monad and XPL on Plasma. Those deposits create a spot balance that must be exchanged into the quote asset a chosen market accepts. Arbitrum funding skips that conversion because native Circle-issued USDC arrives as USDC collateral on HyperCore. The bridge enforces a 5 USDC minimum, and Arbitrum One identifies itself to EVM wallets with chain ID 42161. This page follows that route from wallet preparation through account verification, keeping asset conversion outside the setup sequence.

What must be in the wallet before connecting?

A prepared Hyperliquid wallet holds native Arbitrum USDC, enough ETH for gas and the address intended for trading.

Network identity

Select Arbitrum One, whose chain ID is 42161. Ethereum mainnet uses chain ID 1, so an identical EVM address does not place the same balance on both networks. MetaMask, Rabby and Coinbase Wallet expose the active network and account before connection. WalletConnect passes the chosen address from a compatible mobile or desktop wallet. Keep that address selected through the deposit because Bridge2 credits the sender.

Token identity

Use Circle-issued USDC under the ERC-20 contract 0xaf88d065e77c8cC2239327C5EDb3A432268e5831. It has 6 decimal places, and its EVM contract address contains 40 hexadecimal characters after the 0x prefix, or 42 characters in total. Bridged USDC is a separate token, even when a wallet displays the same symbol. Match the complete contract before opening the deposit panel. A ticker-only check misses network identity; the contract and chain ID together identify the asset Bridge2 accepts.

Gas balance

ETH pays for the Arbitrum deposit transaction, while Hyperliquid trading itself consumes no Arbitrum gas. The ETH amount follows the wallet's transaction estimate and the network base fee at submission. Keep enough for the displayed transaction rather than treating the 5 USDC threshold as an all-in setup cost. That threshold governs bridge credit; it does not supply gas or define useful trading collateral.

The sub-5 USDC failure depends on login type

A deposit below 5 USDC fails the bridge threshold, and recovery behavior differs between wallet and email accounts (compare Choosing exchange checklist ).

Hyperliquid's native Arbitrum bridge credits deposits of 5 USDC or more, while amounts below 5 USDC are not credited.

With a normal DeFi wallet, a sub-minimum transfer never reaches the HyperCore balance and the bridge provides no top-up recovery. An email login behaves differently because its generated wallet accepts another Arbitrum USDC transfer; once the combined amount reaches the minimum, the whole amount is credited. Email access uses a 6-digit verification code. That distinction belongs to account deposit handling, not the USDC token standard. Record the login route before funding and treat 5 USDC as a hard floor rather than a target. A larger deposit also leaves usable collateral after trading fees.

Connect, enable trading and deposit in that order

The clean setup sequence is connecting the wallet, enabling trading and then submitting the Arbitrum USDC deposit.

Deposit decision checklist

• If the balance is native USDC on Arbitrum One, open Deposit and use the connected wallet.
• If USDC sits on Ethereum or another chain, move it to Arbitrum One before this bridge step.
• If Arbitrum shows no ETH, add gas funds before opening the deposit transaction.
• If the amount is below 5 USDC, increase it before submitting.
• If access uses email, fund the generated address and retain access to the same inbox.

Connection signature

Connecting exposes the selected public address to the interface without moving funds. Enable Trading then requests a gasless wallet signature, which authorizes account actions on Hyperliquid. Read the address in the prompt and finish this signature before depositing. The signature does not spend ETH or transfer USDC, so it remains separate from the Arbitrum transaction.

Bridge transaction

Open Deposit, enter at least 5 USDC and confirm the transaction in the EVM wallet on Arbitrum One. That onchain action spends ETH gas and moves native USDC into Bridge2. HyperCore associates the eventual credit with the sending address. This ordering makes Hyperliquid exchange setup easy to inspect: one connected identity, one authorization state and one visible funding transaction. The wallet receipt supplies the transaction hash used during later verification.

First-order boundary

Stop the setup sequence after the collateral balance appears. Market selection, leverage, order type and margin mode belong to the first order rather than to bridge funding. A deposit does not open a position or choose cross versus isolated margin. Keeping those decisions separate makes the credited USDC balance the clear completion point.

How do you confirm the deposit reached HyperCore?

A successful Hyperliquid deposit appears as USDC in HyperCore after the Arbitrum transaction confirms and validators credit it.

Start with the wallet's Arbitrum activity and note the confirmed transaction hash, sending address and USDC amount. Then reconnect the same address and inspect Portfolio or the balance shown beside the trading interface. Bridge deposits are credited in less than 1 minute under the documented flow, so a missing balance after confirmation calls for an identity check before another transfer. Compare chain ID 42161, the native USDC contract and the connected address. Also check the amount met the 5 USDC floor. These four observations separate a pending transaction from a wrong-network, wrong-token or sub-minimum deposit.

One successful bridge credit verifies funding; repeated test deposits add gas cost without improving the check.

Fees and balances after the bridge

On those terms, Hyperliquid separates Arbitrum deposit gas, exchange trading fees and the fixed USDC withdrawal charge into three cost lines.

Deposit cost

The native bridge sets a 5 USDC minimum rather than a fixed deposit fee. Arbitrum charges ETH gas for the deposit transaction, and the wallet calculates that amount from gas units and the network fee. The full qualifying USDC amount becomes the HyperCore deposit balance. Gas remains the only variable setup cost on this direct route.

Trading cost

Base-tier perpetual fees start at 0.045% for takers and 0.015% for makers. Base-tier spot fees are 0.070% for takers and 0.040% for makers. Hyperliquid determines the user tier from rolling 14-day weighted volume, assessed daily in UTC, with spot volume counting at 2 times its value. These percentages apply after funding and should remain separate from the Arbitrum gas calculation.

Return trip

Withdrawing USDC back to Arbitrum deducts a fixed 1 USDC fee on Hyperliquid, so keep that amount outside committed margin. The user signs the withdrawal on Hyperliquid and spends no ETH for the Arbitrum transaction. Validators submit and finalize the bridge actions; the documented flow delivers funds in about 3–4 minutes. The requested amount leaves the Hyperliquid balance immediately, while the destination wallet receives native Arbitrum USDC after the dispute period and finalization. More than two-thirds of stake-weighted validator power must sign the withdrawal before it advances. The bridge fee covers their Arbitrum gas.

When is the account ready for its first order?

A Hyperliquid account is ready when trading is enabled, HyperCore shows collateral and the order ticket recognizes balance. HyperEVM is a separate environment with chain ID 999 and HYPE as its gas token; it is not the network selected for this Arbitrum deposit. HyperEVM HYPE uses 18 decimals, while native Arbitrum USDC uses 6. Leave the wallet on the network requested by each action. Perpetual contracts apply funding every 1 hour, so opening a position introduces a balance change beyond setup. Readiness ends at a funded, enabled account; position configuration begins in the order ticket.

The bridge mechanism behind the balance credit

Absent anything unusual, Hyperliquid's Bridge2 contract escrows Arbitrum USDC while HyperCore validators attest deposits and maintain the corresponding account balance.

A deposit emits an Arbitrum event tied to the sender, and validators sign the credit on HyperCore. More than two-thirds of staking power must sign before the balance is credited. HyperBFT provides consensus for HyperCore and HyperEVM, while Bridge2 anchors the USDC side on Arbitrum. The two environments share the account address but perform different jobs: Arbitrum moves the ERC-20 token and HyperCore records trading collateral.

Withdrawals reverse the accounting path through validator signatures, a dispute period and finalization transactions. The user's immediate Hyperliquid balance reduction and later Arbitrum receipt are therefore separate states. For setup, the decisive checkpoint remains the credited HyperCore balance under the same address that sent at least 5 USDC.