LINK input identity and handling
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 is a contract-token input, so the source wallet needs the network’s native gas asset and may need to approve the exact LINK contract.
Base to zkSync Era L2 handoff
This route crosses two L2 execution environments. Base settles to ethereum, while zkSync Era settles to ethereum; each side keeps its own gas balance, token contracts, transaction hash, and settlement progress.
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 zkSync Era. 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.
WETH output identity and receiving
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 arrives as a token contract balance. It may need an explicit unwrap before becoming native ETH and cannot itself pay transaction gas.
Base source execution
Base is a L2 EVM network in the Ethereum ecosystem. ETH pays source-side network gas on Base. EVM 0x account address A Base source transaction is sequenced on the OP Stack rollup and later settles to Ethereum; Base ETH and Base token approvals remain on the L2 ledger.
EVM-to-EVM execution boundary
Base 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 LINK Base to WETH zkSync Era
Route-specific mistakes include sending on a network other than Base; 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. A Base source transaction is sequenced on the OP Stack rollup and later settles to Ethereum; Base ETH and Base token approvals remain on the L2 ledger. LINK is a contract-token input, so the source wallet needs the network’s native gas asset and may need to approve the exact LINK contract. A zkSync Era receipt belongs to EraVM account state and uses ETH for later fees; proof settlement to Ethereum remains distinct from L2 delivery. WETH arrives as a token contract balance. It may need an explicit unwrap before becoming native ETH and cannot itself pay transaction gas.