Direction
ZKsync Era → Hyperliquid
Asset
WBTC
Source gas
ETH
Destination gas
HYPE
Choose the WBTC asset and ZKsync Era network you currently hold.
Check the estimated output, fees, timing, and Hyperliquid destination network.
Open the live route and follow the exact deposit instructions.
Use the receipt and status page until the destination funds arrive.
Wrapped Bitcoin is classified as a wrapped asset for this route. WBTC uses a wrapped contract asset on zkSync Era. The recorded zkSync Era representation uses 8 decimal places. WBTC leaves through a custodial wrapper contract with token approval and source-chain gas; no native Bitcoin UTXO is spent by that transfer.
zkSync Era inclusion and its ethereum settlement are distinct from final receipt on Hyperliquid (HyperEVM). The live route, rather than a generic rollup withdrawal assumption, determines the provider path and timing for this direction.
Wrapped Bitcoin is classified as a wrapped asset for this route. WBTC uses a wrapped contract asset on Hyperliquid (HyperEVM). The recorded Hyperliquid (HyperEVM) representation uses 8 decimal places. WBTC arrives as a wrapper-contract token and must not be sent onward to a native Bitcoin address without an explicit unwrap or bridge path.
Hyperliquid (HyperEVM) is a L1 EVM network in the Hyperliquid ecosystem. HYPE pays destination-side network gas on Hyperliquid (HyperEVM). EVM 0x account address; confirm the destination is HyperEVM A HyperEVM receipt belongs to its EVM execution state and uses HYPE for later gas; it should not be interpreted as a HyperCore position or vault balance.
zkSync Era is a L2 EVM network in the Ethereum ecosystem. ETH pays source-side network gas on zkSync Era. EVM 0x account address A zkSync Era source executes in EraVM with native account-abstraction behavior and ETH fees before proof settlement to Ethereum.
WBTC is a custodial tokenized Bitcoin representation on smart-contract networks. Its transfers use token contracts and approvals rather than native Bitcoin inputs and outputs. On this route WBTC is the source token on zkSync Era. Its token balance, approvals, and contract transfer behavior are separate from the native coin used for network gas.
Route-specific mistakes include sending on a network other than zkSync Era; using a destination that is not valid for Hyperliquid (HyperEVM); running out of ETH before the source transaction is submitted; treating a wrapped token as the native gas asset. A zkSync Era source executes in EraVM with native account-abstraction behavior and ETH fees before proof settlement to Ethereum. WBTC leaves through a custodial wrapper contract with token approval and source-chain gas; no native Bitcoin UTXO is spent by that transfer. A HyperEVM receipt belongs to its EVM execution state and uses HYPE for later gas; it should not be interpreted as a HyperCore position or vault balance. WBTC arrives as a wrapper-contract token and must not be sent onward to a native Bitcoin address without an explicit unwrap or bridge path.
ZKsync Era wallet, token-transfer, contract, log, and gas activity remain public, and Hyperliquid wallet, token-transfer, contract, log, and gas activity remain public. For this WBTC on ZKsync Era to WBTC on Hyperliquid path, Private Route is intended to reduce the direct visible relationship between activity around the source-side EVM 0x account address and destination-side EVM 0x account address; confirm the destination is HyperEVM; it does not hide either chain's public records.
WBTC is a contract representation on zkSync Era with 8 decimals at 0xBBeB516fb02a01611cBBE0453Fe3c580D7281011. ETH, not WBTC, pays gas unless both symbols are the same. A zkSync Era source executes in EraVM with native account-abstraction behavior and ETH fees before proof settlement to Ethereum. WBTC leaves through a custodial wrapper contract with token approval and source-chain gas; no native Bitcoin UTXO is spent by that transfer.
WBTC is a contract representation on Hyperliquid (HyperEVM) with 8 decimals at 0x0555E30da8f98308EdB960aa94C0Db47230d2B9c. HYPE, not WBTC, pays gas unless both symbols are the same. A HyperEVM receipt belongs to its EVM execution state and uses HYPE for later gas; it should not be interpreted as a HyperCore position or vault balance. WBTC arrives as a wrapper-contract token and must not be sent onward to a native Bitcoin address without an explicit unwrap or bridge path.
No. This bridge keeps the asset intent while moving between a WBTC wrapped token and a WBTC wrapped token. Match the source and output details in the live quote.
A zkSync Era source executes in EraVM with native account-abstraction behavior and ETH fees before proof settlement to Ethereum. A HyperEVM receipt belongs to its EVM execution state and uses HYPE for later gas; it should not be interpreted as a HyperCore position or vault balance. The bridge output does not automatically fund every later gas need.
EVM 0x account address; confirm the destination is HyperEVM Do not substitute a zkSync Era address merely because a wallet displays both networks.
Sending on a network other than zkSync Era, selecting a representation not listed by the quote, or entering an address invalid for Hyperliquid (HyperEVM) can prevent normal detection or receipt.
Requirements are checked for the live WBTC ZKsync Era to Hyperliquid 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.
