Chainlink is classified as a governance or utility token for this route. LINK uses a network-specific contract asset on Hyperliquid (HyperEVM). The Hyperliquid (HyperEVM) side is contract-tracked rather than a native gas balance. LINK is a contract-token input, so the source wallet needs the network’s native gas asset and may need to approve the exact LINK contract.
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.
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.
BNB is classified as a native asset for this route. BNB uses a network-specific contract asset on zkSync Era. The recorded zkSync Era representation uses 18 decimal places. Native BSC receipt can fund BNB gas, while externally bridged BNB arrives as a representation that needs the destination chain’s gas token.
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 zkSync Era can use the same 0x address syntax, but they are separate networks with different chain identifiers, gas balances, token contracts, and transaction histories. The recorded settlement context includes ethereum, so L1 and L2 confirmation behavior should not be assumed identical.
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. LINK is a contract-token input, so the source wallet needs the network’s native gas asset and may need to approve the exact LINK contract. A zkSync Era receipt belongs to EraVM account state and uses ETH for later fees; proof settlement to Ethereum remains distinct from L2 delivery. Native BSC receipt can fund BNB gas, while externally bridged BNB arrives as a representation that needs the destination chain’s gas token.
Hyperliquid (HyperEVM) 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 LINK on Hyperliquid (HyperEVM) to BNB 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.
LINK is a contract representation on Hyperliquid (HyperEVM) at 0x1ac2ee68b8d038c982c1e1f73f596927dd70de59. HYPE, not LINK, 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. LINK is a contract-token input, so the source wallet needs the network’s native gas asset and may need to approve the exact LINK contract.
BNB is a contract representation on zkSync Era with 18 decimals at 0x7400793aAd94C8CA801aa036357d10F5Fd0ce08f. ETH, not BNB, pays gas unless both symbols are the same. A zkSync Era receipt belongs to EraVM account state and uses ETH for later fees; proof settlement to Ethereum remains distinct from L2 delivery. Native BSC receipt can fund BNB gas, while externally bridged BNB arrives as a representation that needs the destination chain’s gas token.
LINK is a contract-token input, so the source wallet needs the network’s native gas asset and may need to approve the exact LINK contract. On receipt, Native BSC receipt can fund BNB gas, while externally bridged BNB arrives as a representation that needs the destination chain’s gas token.
LINK is the deposited token input; BNB is the quoted native-asset output. Source allowance or native-spend rules and destination wallet/representation checks are evaluated separately.
LINK is a contract-token input, so the source wallet needs the network’s native gas asset and may need to approve the exact LINK contract. 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. Native BSC receipt can fund BNB gas, while externally bridged BNB arrives as a representation that needs the destination chain’s gas token.
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. LINK is token-tracked and can need approval before transfer.
Sending LINK on a network other than Hyperliquid (HyperEVM), or using an address that is not valid for zkSync Era, can prevent detection or delivery. Match both network labels and representations to the active route.
Requirements are checked for the live LINK Hyperliquid to BNB zkSync 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.
