Ethereum is classified as a native asset for this route. ETH uses a network-specific contract asset on Hyperliquid (HyperEVM). The recorded Hyperliquid (HyperEVM) representation uses 18 decimal places. Native ETH can fund both transfer value and gas on its selected network. If the source is WETH or another tokenized form, approval and unwrap or exchange logic differ.
BNB Chain is a L1 EVM network in the BNB Chain ecosystem. BNB pays destination-side network gas on BNB Chain. EVM 0x account address A BNB Smart Chain receipt uses the BEP-20 contract or native BNB balance selected by the route; later token movement needs BNB gas.
Avalanche is classified as a native asset for this route. AVAX uses a network-specific contract asset on BNB Chain. The recorded BNB Chain representation uses 18 decimal places. Native Avalanche receipt belongs on C-Chain and can fund later gas; an AVAX token on another chain remains a contract balance.
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.
Hyperliquid (HyperEVM) and BNB Chain can use the same 0x address syntax, but they are separate networks with different chain identifiers, gas balances, token contracts, and transaction histories.
Route-specific mistakes include sending on a network other than Hyperliquid (HyperEVM); using a destination that is not valid for BNB Chain; 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. Native ETH can fund both transfer value and gas on its selected network. If the source is WETH or another tokenized form, approval and unwrap or exchange logic differ. A BNB Smart Chain receipt uses the BEP-20 contract or native BNB balance selected by the route; later token movement needs BNB gas. Native Avalanche receipt belongs on C-Chain and can fund later gas; an AVAX token on another chain remains a contract balance.
Hyperliquid (HyperEVM) wallet, token-transfer, contract, log, and gas activity remain public, and BNB Chain wallet, token-transfer, contract, log, and gas activity remain public. For this ETH on Hyperliquid (HyperEVM) to AVAX on BNB Chain 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.
ETH is a contract representation on Hyperliquid (HyperEVM) with 18 decimals at 0x1fbcCdc677c10671eE50b46C61F0f7d135112450. HYPE, not ETH, 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. Native ETH can fund both transfer value and gas on its selected network. If the source is WETH or another tokenized form, approval and unwrap or exchange logic differ.
AVAX is a contract representation on BNB Chain with 18 decimals at 0x1CE0c2827e2eF14D5C4f29a091d735A204794041. BNB, not AVAX, pays gas unless both symbols are the same. A BNB Smart Chain receipt uses the BEP-20 contract or native BNB balance selected by the route; later token movement needs BNB gas. Native Avalanche receipt belongs on C-Chain and can fund later gas; an AVAX token on another chain remains a contract balance.
Native ETH can fund both transfer value and gas on its selected network. If the source is WETH or another tokenized form, approval and unwrap or exchange logic differ. On receipt, Native Avalanche receipt belongs on C-Chain and can fund later gas; an AVAX token on another chain remains a contract balance.
ETH is the deposited native-asset input; AVAX is the quoted native-asset output. Source allowance or native-spend rules and destination wallet/representation checks are evaluated separately.
Native ETH can fund both transfer value and gas on its selected network. If the source is WETH or another tokenized form, approval and unwrap or exchange logic differ. A HyperEVM source spends HYPE for EVM gas; HyperCore balances, vault positions, and other Hyperliquid account states are not interchangeable inputs. A BNB Smart Chain receipt uses the BEP-20 contract or native BNB balance selected by the route; later token movement needs BNB gas. Native Avalanche receipt belongs on C-Chain and can fund later gas; an AVAX token on another chain remains a contract balance.
HYPE is the native gas asset for Hyperliquid (HyperEVM). A HyperEVM source spends HYPE for EVM gas; HyperCore balances, vault positions, and other Hyperliquid account states are not interchangeable inputs. ETH is token-tracked and can need approval before transfer.
Sending ETH on a network other than Hyperliquid (HyperEVM), or using an address that is not valid for BNB Chain, can prevent detection or delivery. Match both network labels and representations to the active route.
Requirements are checked for the live ETH Hyperliquid to AVAX BSC 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.
