WETH input identity and handling
WETH is classified as a wrapped asset for this route. WETH uses a wrapped contract asset on BNB Chain. The recorded BNB Chain representation uses 18 decimal places. WETH leaves through a wrapper contract and needs native chain gas. A WETH token balance cannot pay the gas required to submit its own transfer.
From BNB Chain L1 into Arbitrum L2
BNB Chain source execution occurs on L1, while Arbitrum 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.
WETH unwrap or exchange input check
WETH is a contract wrapper for ETH. It can be transferred as a token but cannot replace the native gas balance required by the network. On this route WETH is the source token on BNB Chain. Its token balance, approvals, and contract transfer behavior are separate from the native coin used for network gas.
Arbitrum destination execution
Arbitrum is a L2 EVM network in the Ethereum ecosystem. ETH pays destination-side network gas on Arbitrum. EVM 0x account address An Arbitrum receipt appears on the Nitro L2 ledger under an Arbitrum token contract or native ETH balance; later spending needs Arbitrum ETH while L1 settlement continues separately.
ETH output identity and receiving
Ethereum is classified as a native asset for this route. ETH uses a native asset on Arbitrum. The recorded Arbitrum 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 source execution
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.
EVM-to-EVM execution boundary
BNB Chain and Arbitrum 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.
Mistakes specific to WETH BNB Chain to ETH Arbitrum
Route-specific mistakes include sending on a network other than BNB Chain; using a destination that is not valid for Arbitrum; running out of BNB before the source transaction is submitted; treating a wrapped token as the native gas asset. 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. WETH leaves through a wrapper contract and needs native chain gas. A WETH token balance cannot pay the gas required to submit its own transfer. An Arbitrum receipt appears on the Nitro L2 ledger under an Arbitrum token contract or native ETH balance; later spending needs Arbitrum ETH while L1 settlement continues separately. Determine whether ETH arrives as native destination gas or as a tokenized representation. Only the native balance can directly pay that network’s fees.