Direction
Hyperliquid → Base
Asset
WBTC
Source gas
HYPE
Destination gas
ETH
Choose the WBTC asset and Hyperliquid network you currently hold.
Check the estimated output, fees, timing, and Base 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 Hyperliquid (HyperEVM). The recorded Hyperliquid (HyperEVM) 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.
Hyperliquid (HyperEVM) source execution occurs on L1, while Base 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.
Wrapped Bitcoin is classified as a wrapped asset for this route. WBTC uses a wrapped contract asset on Base. The Base side is contract-tracked rather than a native gas 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.
Base is a L2 EVM network in the Ethereum ecosystem. ETH pays destination-side network gas on Base. EVM 0x account address A Base receipt belongs to the Base L2 balance and token contract, not Ethereum L1; later activity needs ETH specifically on Base.
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.
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 Hyperliquid (HyperEVM). 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 Hyperliquid (HyperEVM); using a destination that is not valid for Base; running out of HYPE before the source transaction is submitted; treating a wrapped token as the native gas asset. A HyperEVM source spends HYPE for EVM gas; HyperCore balances, vault positions, and other Hyperliquid account states are not interchangeable inputs. WBTC leaves through a custodial wrapper contract with token approval and source-chain gas; no native Bitcoin UTXO is spent by that transfer. A Base receipt belongs to the Base L2 balance and token contract, not Ethereum L1; later activity needs ETH specifically on Base. 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 wallet, token-transfer, contract, log, and gas activity remain public, and Base wallet, token-transfer, contract, log, and gas activity remain public. For this WBTC on Hyperliquid to WBTC on Base 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.
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 source spends HYPE for EVM gas; HyperCore balances, vault positions, and other Hyperliquid account states are not interchangeable inputs. 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 Base at 0x0555e30da8f98308edb960aa94c0db47230d2b9c. ETH, not WBTC, pays gas unless both symbols are the same. A Base receipt belongs to the Base L2 balance and token contract, not Ethereum L1; later activity needs ETH specifically on Base. 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 HyperEVM source spends HYPE for EVM gas; HyperCore balances, vault positions, and other Hyperliquid account states are not interchangeable inputs. A Base receipt belongs to the Base L2 balance and token contract, not Ethereum L1; later activity needs ETH specifically on Base. The bridge output does not automatically fund every later gas need.
EVM 0x account address Do not substitute a Hyperliquid (HyperEVM) address merely because a wallet displays both networks.
Sending on a network other than Hyperliquid (HyperEVM), selecting a representation not listed by the quote, or entering an address invalid for Base can prevent normal detection or receipt.
Requirements are checked for the live WBTC Hyperliquid to Base 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.
