WETH input identity and handling
WETH is classified as a wrapped asset for this route. WETH uses a wrapped contract asset on Ethereum. The recorded Ethereum 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 Ethereum L1 into zkSync Era L2
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.
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 Ethereum. Its token balance, approvals, and contract transfer behavior are separate from the native coin used for network gas.
zkSync Era destination execution
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.
ETH output identity and receiving
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.
Ethereum source execution
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.
EVM-to-EVM execution boundary
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.
Mistakes specific to WETH Ethereum to ETH zkSync Era
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; treating a wrapped token as the native gas asset. 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. 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. 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.