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.
zkSync Era to Base L2 handoff
This route crosses two L2 execution environments. zkSync Era settles to ethereum, while Base settles to ethereum; each side keeps its own gas balance, token contracts, transaction hash, and settlement progress.
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.
Base destination execution
Base is a L2 EVM network in the Ethereum ecosystem. ETH pays destination-side network gas on Base. EVM 0x account address A Base receipt belongs to the Base L2 balance and token contract, not Ethereum L1; later activity needs ETH specifically on Base.
LINK output identity and receiving
Chainlink is classified as a governance or utility token for this route. LINK uses a network-specific contract asset on Base. The Base side is contract-tracked rather than a native gas balance. LINK arrives as a network-specific contract balance. The wallet still needs the destination native asset before it can transfer or approve LINK later.
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 Base 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 LINK Base
Route-specific mistakes include sending on a network other than zkSync Era; using a destination that is not valid for Base; 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. A Base receipt belongs to the Base L2 balance and token contract, not Ethereum L1; later activity needs ETH specifically on Base. LINK arrives as a network-specific contract balance. The wallet still needs the destination native asset before it can transfer or approve LINK later.