Bridge Hyperliquid (HyperEVM) to zkSync Era

FromHyperliquid
TozkSync Era
ENTER AMOUNT
Squatch Guard
Before a deposit order moves forward, Squatch Guard checks the amount, asset, network, and active quote window against the order details.

Direction

Hyperliquid → ZKsync Era

Asset

USDC

Source gas

HYPE

Destination gas

ETH

How the Sasquatch deposit route works

1. Select the source

Choose the USDC asset and Hyperliquid network you currently hold.

2. Review the route

Check the estimated output, fees, timing, and ZKsync Era destination network.

3. Create the order

Open the live route and follow the exact deposit instructions.

4. Track delivery

Use the receipt and status page until the destination funds arrive.

What you need to know

From Hyperliquid (HyperEVM) L1 into zkSync Era L2

Hyperliquid (HyperEVM) source execution occurs on L1, while zkSync Era delivery occurs on a separate L2 ledger that settles to ethereum. HYPE pays source gas and ETH is the destination gas asset; identical-looking wallet addresses do not merge the balances or transaction histories.

Hyperliquid (HyperEVM) deposit-side execution

Hyperliquid (HyperEVM) is a L1 EVM network in the Hyperliquid ecosystem. HYPE pays source-side network gas on Hyperliquid (HyperEVM). EVM 0x account address; confirm the destination is HyperEVM A HyperEVM source spends HYPE for EVM gas; HyperCore balances, vault positions, and other Hyperliquid account states are not interchangeable inputs.

Select a zkSync Era-compatible output

EVM 0x account address ETH is the native gas asset for zkSync Era. The quote identifies whether the delivered asset is native, contract-based, or bridged.

zkSync Era receipt-side execution

zkSync Era is a L2 EVM network in the Ethereum ecosystem. ETH pays destination-side network gas on zkSync Era. EVM 0x account address A zkSync Era receipt belongs to EraVM account state and uses ETH for later fees; proof settlement to Ethereum remains distinct from L2 delivery.

Hyperliquid (HyperEVM) to zkSync Era bridge mistakes

Route-specific mistakes include sending on a network other than Hyperliquid (HyperEVM); using a destination that is not valid for zkSync Era; running out of HYPE before the source transaction is submitted. A HyperEVM source spends HYPE for EVM gas; HyperCore balances, vault positions, and other Hyperliquid account states are not interchangeable inputs. A zkSync Era receipt belongs to EraVM account state and uses ETH for later fees; proof settlement to Ethereum remains distinct from L2 delivery.

Private Route for USDC → USDC

Hyperliquid wallet, token-transfer, contract, log, and gas activity remain public, and ZKsync Era wallet, token-transfer, contract, log, and gas activity remain public. For this USDC on Hyperliquid to USDC on ZKsync Era path, Private Route is intended to reduce the direct visible relationship between activity around the source-side EVM 0x account address; confirm the destination is HyperEVM and destination-side EVM 0x account address; it does not hide either chain's public records.

  • Reduces the obvious link between the USDC deposit and USDC receipt
  • Compare standard and Private Route options for Hyperliquid → ZKsync Era
  • Shows what remains public on Hyperliquid and ZKsync Era before you deposit
Check Private Route availability →

Related routes

Hyperliquid to ZKsync Era FAQs

Which asset can travel from Hyperliquid (HyperEVM) to zkSync Era?

The live route lists assets supported in this direction. Confirm that the selected source representation has an explicit zkSync Era output before depositing.

Which gas balances matter for this bridge?

A HyperEVM source spends HYPE for EVM gas; HyperCore balances, vault positions, and other Hyperliquid account states are not interchangeable inputs. A zkSync Era receipt belongs to EraVM account state and uses ETH for later fees; proof settlement to Ethereum remains distinct from L2 delivery. The bridge output does not automatically fund every later gas need.

What destination address should be used?

EVM 0x account address Do not substitute a Hyperliquid (HyperEVM) address merely because a wallet displays both networks.

What wrong-direction mistake can prevent delivery?

Sending on a network other than Hyperliquid (HyperEVM), selecting a representation not listed by the quote, or entering an address invalid for zkSync Era can prevent normal detection or receipt.

Can I bridge USDC from Hyperliquid to ZKsync Era without KYC?

Requirements are checked for the live USDC Hyperliquid to ZKsync Era quote. Verification requirements can depend on the provider, amount, jurisdiction, and current route. Sasquatch does not verify this route as universally no-KYC; check the live flow before continuing.

View all bridge FAQs →