Arbitrum is classified as a governance or utility token for this route. ARB uses a network-specific contract asset on BNB Chain. The recorded BNB Chain representation uses 18 decimal places. Sending ARB can require a token allowance, while ETH—not ARB—must fund Arbitrum gas. Verify the outbound ARB contract if the source is not Arbitrum.
BNB Chain source execution occurs on L1, while zkSync Era delivery occurs on a separate L2 ledger that settles to ethereum. BNB 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.
Ethereum is classified as a native asset for this route. ETH uses a native asset on zkSync Era. The recorded zkSync Era representation uses 18 decimal places. Determine whether ETH arrives as native destination gas or as a tokenized representation. Only the native balance can directly pay that network’s fees.
BNB Chain is a L1 EVM network in the BNB Chain ecosystem. BNB pays source-side network gas on BNB Chain. EVM 0x account address A BNB Smart Chain source uses BNB gas and BEP-20 contracts; a familiar 0x account does not turn a BEP-20 deposit into ERC-20.
BNB Chain 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 BNB Chain; using a destination that is not valid for zkSync Era; running out of BNB before the source transaction is submitted. A BNB Smart Chain source uses BNB gas and BEP-20 contracts; a familiar 0x account does not turn a BEP-20 deposit into ERC-20. Sending ARB can require a token allowance, while ETH—not ARB—must fund Arbitrum gas. Verify the outbound ARB contract if the source is not Arbitrum. A zkSync Era receipt belongs to EraVM account state and uses ETH for later fees; proof settlement to Ethereum remains distinct from L2 delivery. Determine whether ETH arrives as native destination gas or as a tokenized representation. Only the native balance can directly pay that network’s fees.
BNB Chain 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 ARB on BNB Chain to ETH 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.
ARB is a contract representation on BNB Chain with 18 decimals at 0x0acdb582C1d5512Ea31fD64b9C07882CB31E494D. BNB, not ARB, pays gas unless both symbols are the same. A BNB Smart Chain source uses BNB gas and BEP-20 contracts; a familiar 0x account does not turn a BEP-20 deposit into ERC-20. Sending ARB can require a token allowance, while ETH—not ARB—must fund Arbitrum gas. Verify the outbound ARB contract if the source is not Arbitrum.
ETH is listed as the native representation on zkSync Era; ETH is used for network gas. A zkSync Era receipt belongs to EraVM account state and uses ETH for later fees; proof settlement to Ethereum remains distinct from L2 delivery. Determine whether ETH arrives as native destination gas or as a tokenized representation. Only the native balance can directly pay that network’s fees.
Sending ARB can require a token allowance, while ETH—not ARB—must fund Arbitrum gas. Verify the outbound ARB contract if the source is not Arbitrum. On receipt, Determine whether ETH arrives as native destination gas or as a tokenized representation. Only the native balance can directly pay that network’s fees.
ARB is the deposited token input; ETH is the quoted native-asset output. Source allowance or native-spend rules and destination wallet/representation checks are evaluated separately.
Sending ARB can require a token allowance, while ETH—not ARB—must fund Arbitrum gas. Verify the outbound ARB contract if the source is not Arbitrum. A BNB Smart Chain source uses BNB gas and BEP-20 contracts; a familiar 0x account does not turn a BEP-20 deposit into ERC-20. A zkSync Era receipt belongs to EraVM account state and uses ETH for later fees; proof settlement to Ethereum remains distinct from L2 delivery. Determine whether ETH arrives as native destination gas or as a tokenized representation. Only the native balance can directly pay that network’s fees.
BNB is the native gas asset for BNB Chain. A BNB Smart Chain source uses BNB gas and BEP-20 contracts; a familiar 0x account does not turn a BEP-20 deposit into ERC-20. ARB is token-tracked and can need approval before transfer.
Sending ARB on a network other than BNB Chain, 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 ARB BSC to ETH 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.
