AVAX input identity and handling
Avalanche is classified as a native asset for this route. AVAX uses a native asset on Avalanche. The recorded Avalanche representation uses 18 decimal places. On Avalanche C-Chain, native AVAX funds both the transfer value and gas; on another chain, an AVAX-labelled contract behaves as a token input instead.
From Avalanche L1 into Arbitrum L2
Avalanche source execution occurs on L1, while Arbitrum delivery occurs on a separate L2 ledger that settles to ethereum. AVAX pays source gas and ETH is the destination gas asset; identical-looking wallet addresses do not merge the balances or transaction histories.
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 Arbitrum. 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.
WETH output identity and receiving
WETH is classified as a wrapped asset for this route. WETH uses a wrapped contract asset on Arbitrum. The recorded Arbitrum 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.
Avalanche source execution
Avalanche is a L1 EVM network in the Avalanche ecosystem. AVAX pays source-side network gas on Avalanche. EVM 0x account address An Avalanche source route uses C-Chain Snowman execution and AVAX gas; X-Chain or P-Chain balances are not valid C-Chain deposits.
EVM-to-EVM execution boundary
Avalanche 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 AVAX Avalanche to WETH Arbitrum
Route-specific mistakes include sending on a network other than Avalanche; using a destination that is not valid for Arbitrum; running out of AVAX before the source transaction is submitted; treating a wrapped token as the native gas asset. An Avalanche source route uses C-Chain Snowman execution and AVAX gas; X-Chain or P-Chain balances are not valid C-Chain deposits. On Avalanche C-Chain, native AVAX funds both the transfer value and gas; on another chain, an AVAX-labelled contract behaves as a token input instead. 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. WETH arrives as a token contract balance. It may need an explicit unwrap before becoming native ETH and cannot itself pay transaction gas.