WETH input identity and handling
WETH is classified as a wrapped asset for this route. WETH uses a wrapped contract asset on zkSync Era. The recorded zkSync Era 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.
Leaving zkSync Era L2 for Ethereum L1
zkSync Era inclusion and its ethereum settlement are distinct from final receipt on Ethereum. The live route, rather than a generic rollup withdrawal assumption, determines the provider path and timing for this direction.
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 zkSync Era. Its token balance, approvals, and contract transfer behavior are separate from the native coin used for network gas.
Ethereum destination execution
Ethereum is a L1 EVM network in the Ethereum ecosystem. ETH pays destination-side network gas on Ethereum. EVM 0x account address An Ethereum receipt is an L1 native ETH balance or ERC-20 contract event; later token movement can require ETH gas and a new approval for another contract.
ETH output identity and receiving
Ethereum is classified as a native asset for this route. ETH uses a native asset on Ethereum. The recorded Ethereum 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.
zkSync Era source execution
zkSync Era is a L2 EVM network in the Ethereum ecosystem. ETH pays source-side network gas on zkSync Era. EVM 0x account address A zkSync Era source executes in EraVM with native account-abstraction behavior and ETH fees before proof settlement to Ethereum.
EVM-to-EVM execution boundary
zkSync Era and Ethereum 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 zkSync Era to ETH Ethereum
Route-specific mistakes include sending on a network other than zkSync Era; using a destination that is not valid for Ethereum; running out of ETH before the source transaction is submitted; treating a wrapped token as the native gas asset. A zkSync Era source executes in EraVM with native account-abstraction behavior and ETH fees before proof settlement to Ethereum. 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 Ethereum receipt is an L1 native ETH balance or ERC-20 contract event; later token movement can require ETH gas and a new approval for another contract. Determine whether ETH arrives as native destination gas or as a tokenized representation. Only the native balance can directly pay that network’s fees.