Hyperliquid Bridge Explained: Supported Routes, Fees and Risks

A bridge moves an asset between blockchain environments. Hyperliquid's native bridge is the route for depositing native USDC from Arbitrum into HyperCore and withdrawing that USDC back to an Arbitrum address. It is part of the path between an external wallet and the balances used by Hyperliquid's onchain exchange.

The word bridge can cause confusion because Hyperliquid also displays other asset deposit routes, while third-party bridges can move funds from other chains to Arbitrum. These paths may all help a user fund an account, but they do not share the same contracts, assets, fees or support process.

How does the native Hyperliquid bridge work?

For a deposit, the user sends native USDC on Arbitrum to the documented bridge contract through the official interface. Hyperliquid validators observe the deposit. The balance is credited on Hyperliquid after validators representing more than two-thirds of staking power have signed it.

The withdrawal path runs in reverse but is not simply an Arbitrum transaction submitted by the user. Hyperliquid deducts the withdrawal amount from the L1 balance, validators sign the withdrawal, and an EVM transaction requests it from the bridge after more than two-thirds of staking power has signed. A dispute period precedes finalization and distribution to the destination address.

Which routes does Hyperliquid support?

The native bridge has one core route: native USDC between Arbitrum and HyperCore. Hyperliquid's current onboarding documentation also lists direct deposit choices for selected assets on networks including Bitcoin, Ethereum, Solana, Monad and Plasma. Those additional choices are separate deposit rails; some are managed by an independent provider and normally credit the deposited asset to a spot balance before it is sold or used.

Is bridging the same as depositing on Hyperliquid?

A native USDC deposit uses the Hyperliquid bridge, so the two terms often describe the same user action. But deposit is the broader category. A supported BTC deposit on Bitcoin, for example, is an onboarding route shown by Hyperliquid; it is not a BTC transaction through the native Arbitrum bridge.

A third-party bridge adds another step. If USDC starts on Ethereum, Base or another chain, a user may first move it to Arbitrum through an external bridge and then deposit through Hyperliquid's native bridge. The first transaction depends on that third party. The second depends on Hyperliquid's Arbitrum bridge. Each step has its own contract, fee and failure modes.

What do you need to bridge USDC to Hyperliquid?

• Native USDC on the Arbitrum network, using the token accepted by the current deposit interface
• At least 5 USDC, which is the minimum documented for the native bridge
• A small amount of ETH on Arbitrum to pay the deposit transaction's gas
• The wallet address that should receive the corresponding Hyperliquid credit
• The official Hyperliquid application rather than a bridge address copied from a post or message

The minimum is not a recommendation for how much to deposit. It is a contract-processing threshold. The Bridge2 documentation warns that a deposit below 5 USDC is not credited. Hyperliquid support describes a limited email-wallet case where adding more may bring the total above the threshold, but a standard wallet deposit below the minimum may be unrecoverable. Treat 5 USDC as a hard floor and leave room for the Arbitrum gas transaction.

What fees does the Hyperliquid bridge charge?

The 1 USDC withdrawal charge is not a trading fee and is not reduced by a referral discount. It covers the Arbitrum gas costs handled by validators. Users do not need Arbitrum ETH to submit the Hyperliquid withdrawal, although they may need ETH later to move or use the USDC after it arrives on Arbitrum.

How long does the Hyperliquid bridge take?

Hyperliquid's Bridge2 documentation says a qualifying USDC deposit is normally credited in under one minute. It describes withdrawals as arriving in roughly three to four minutes, while the exchange API documentation uses an approximate five-minute figure. These are normal estimates, not deadlines.

Timing can extend if Arbitrum is congested, validators have not completed the required signatures, the bridge is in its dispute process or a third-party route is delayed. Follow the estimate shown in the live withdrawal modal and check the relevant transaction or explorer record before repeating an action.

How do Hyperliquid withdrawals to Arbitrum work?

A native USDC withdrawal starts in Hyperliquid's withdrawal flow. The user enters an amount and destination address, reviews the 1 USDC charge, and signs. The amount is deducted from the Hyperliquid balance immediately while validators process the bridge withdrawal to Arbitrum.

Is the Hyperliquid bridge the same as a HyperCore-HyperEVM transfer?

No. The native bridge discussed here connects Arbitrum USDC with HyperCore. Moving HYPE or another supported asset between HyperCore and HyperEVM is an internal movement between two execution environments within the Hyperliquid network. It uses separate controls and system-address mechanics.

This distinction matters when diagnosing a missing balance. USDC bridged from Arbitrum should be checked in the relevant HyperCore balance. HYPE transferred to HyperEVM should be checked in an EVM wallet configured for HyperEVM. Repeating either action before identifying the source, destination and network can compound the mistake.

What are the main Hyperliquid bridge risks?

• Wrong-network risk - sending an asset on an unsupported network can prevent it from being credited.
• Wrong-token risk - native USDC, USDC.e, USDT and other stablecoins are not interchangeable at the contract level.
• Minimum-deposit risk - a standard-wallet native bridge deposit below 5 USDC may be permanently lost.
• Address risk - a valid transaction to the wrong destination is still the wrong transfer.
• Contract risk - a bridge depends on contract code and its interaction with validators and external networks.
• Validator and liveness risk - the documented process requires stake-weighted signatures before funds are credited or released.
• Third-party risk - an external bridge, exchange or deposit provider adds separate custody, contract and support assumptions.
• Phishing risk - fake interfaces can request approvals or signatures that do not match the intended bridge action.
• Stablecoin risk - bridged USDC remains exposed to issuer, market and access risks.

Hyperliquid publishes its Bridge2 contract and says the bridge and its staking-related logic were audited by Zellic. Public code and an audit are useful controls, but they do not guarantee that the bridge, wallet, validator set, stablecoin or user action can never fail.

What should you check if a Hyperliquid bridge transfer is missing?