BNB is classified as a native asset for this route. BNB uses a network-specific contract asset on Ethereum. The Ethereum side is contract-tracked rather than a native gas balance. Native BNB can fund value and BSC gas, while tokenized BNB requires the source chain’s gas asset and contract handling.
Ethereum source execution occurs on L1, while zkSync Era delivery occurs on a separate L2 ledger that settles to ethereum. ETH 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.
Chainlink is classified as a governance or utility token for this route. LINK uses a network-specific contract asset on zkSync Era. The zkSync Era side is contract-tracked rather than a native gas balance. LINK arrives as a network-specific contract balance. The wallet still needs the destination native asset before it can transfer or approve LINK later.
Ethereum is a L1 EVM network in the Ethereum ecosystem. ETH pays source-side network gas on Ethereum. EVM 0x account address An Ethereum source pays L1 base and priority fees in ETH, and an ERC-20 input can require a separate approval before the route deposit.
Ethereum 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 Ethereum; using a destination that is not valid for zkSync Era; running out of ETH before the source transaction is submitted. An Ethereum source pays L1 base and priority fees in ETH, and an ERC-20 input can require a separate approval before the route deposit. Native BNB can fund value and BSC gas, while tokenized BNB requires the source chain’s gas asset and contract handling. A zkSync Era receipt belongs to EraVM account state and uses ETH for later fees; proof settlement to Ethereum remains distinct from L2 delivery. LINK arrives as a network-specific contract balance. The wallet still needs the destination native asset before it can transfer or approve LINK later.
Ethereum 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 BNB on Ethereum to LINK on zkSync Era 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; it does not hide either chain's public records.
BNB is a contract representation on Ethereum at 0xb8c77482e45f1f44de1745f52c74426c631bdd52. ETH, not BNB, pays gas unless both symbols are the same. An Ethereum source pays L1 base and priority fees in ETH, and an ERC-20 input can require a separate approval before the route deposit. Native BNB can fund value and BSC gas, while tokenized BNB requires the source chain’s gas asset and contract handling.
LINK is a contract representation on zkSync Era at 0x52869bae3e091e36b0915941577f2d47d8d8b534. ETH, not LINK, 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. LINK arrives as a network-specific contract balance. The wallet still needs the destination native asset before it can transfer or approve LINK later.
Native BNB can fund value and BSC gas, while tokenized BNB requires the source chain’s gas asset and contract handling. On receipt, LINK arrives as a network-specific contract balance. The wallet still needs the destination native asset before it can transfer or approve LINK later.
BNB is the deposited native-asset input; LINK is the quoted token output. Source allowance or native-spend rules and destination wallet/representation checks are evaluated separately.
Native BNB can fund value and BSC gas, while tokenized BNB requires the source chain’s gas asset and contract handling. An Ethereum source pays L1 base and priority fees in ETH, and an ERC-20 input can require a separate approval before the route deposit. A zkSync Era receipt belongs to EraVM account state and uses ETH for later fees; proof settlement to Ethereum remains distinct from L2 delivery. LINK arrives as a network-specific contract balance. The wallet still needs the destination native asset before it can transfer or approve LINK later.
ETH is the native gas asset for Ethereum. An Ethereum source pays L1 base and priority fees in ETH, and an ERC-20 input can require a separate approval before the route deposit. BNB is token-tracked and can need approval before transfer.
Sending BNB on a network other than Ethereum, 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 BNB Ethereum to LINK 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.
