ETH input identity and handling
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. 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.
Leaving Arbitrum L2 for BNB Chain L1
Arbitrum inclusion and its ethereum settlement are distinct from final receipt on BNB Chain. The live route, rather than a generic rollup withdrawal assumption, determines the provider path and timing for this direction.
WETH wrapped-token output 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 destination token on BNB Chain. Its token balance, approvals, and contract transfer behavior are separate from the native coin used for network gas.
BNB Chain destination execution
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.
WETH output identity and receiving
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 arrives as a token contract balance. It may need an explicit unwrap before becoming native ETH and cannot itself pay transaction gas.
Arbitrum source execution
Arbitrum is a L2 EVM network in the Ethereum ecosystem. ETH pays source-side network gas on Arbitrum. EVM 0x account address On an Arbitrum source, the Nitro sequencer records L2 execution before Ethereum settlement completes; ETH funds gas and ERC-20 inputs can need approval.
EVM-to-EVM execution boundary
Arbitrum 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. The recorded settlement context includes ethereum, so L1 and L2 confirmation behavior should not be assumed identical.
Mistakes specific to ETH Arbitrum to WETH BNB Chain
Route-specific mistakes include sending on a network other than Arbitrum; using a destination that is not valid for BNB Chain; running out of ETH before the source transaction is submitted; treating a wrapped token as the native gas asset. On an Arbitrum source, the Nitro sequencer records L2 execution before Ethereum settlement completes; ETH funds gas and ERC-20 inputs can need approval. 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. WETH arrives as a token contract balance. It may need an explicit unwrap before becoming native ETH and cannot itself pay transaction gas.