Swap AVAX on Linea to ETH on zkSync Era

FromLinea
TozkSync Era
ENTER AMOUNT
Squatch Guard
Before a deposit order moves forward, Squatch Guard checks the amount, asset, network, and active quote window against the order details.
ETH / USD
Price
24h
High
Low
Vol

What you need to know

AVAX input identity and handling

Avalanche is classified as a native asset for this route. AVAX uses a network-specific contract asset on Linea. The recorded Linea 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.

Linea to zkSync Era L2 handoff

This route crosses two L2 execution environments. Linea settles to ethereum, while zkSync Era settles to ethereum; each side keeps its own gas balance, token contracts, transaction hash, and settlement progress.

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.

Linea source execution

Linea is a L2 EVM network in the Ethereum ecosystem. ETH pays source-side network gas on Linea. EVM 0x account address A Linea source is executed on the zkEVM rollup and later proven to Ethereum; L2 inclusion and proof settlement are distinct source milestones.

EVM-to-EVM execution boundary

Linea 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 AVAX Linea to ETH zkSync Era

Route-specific mistakes include sending on a network other than Linea; using a destination that is not valid for zkSync Era; running out of ETH before the source transaction is submitted. A Linea source is executed on the zkEVM rollup and later proven to Ethereum; L2 inclusion and proof settlement are distinct source milestones. 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. 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.

Private Route for AVAX → ETH

Linea wallet, token-transfer, contract, log, and gas activity remain public, and zkSync Era wallet, token-transfer, contract, log, and gas activity remain public. For this AVAX on Linea to ETH on zkSync Era path, Private Route is intended to reduce the direct visible relationship between activity around the source-side EVM 0x account address and destination-side EVM 0x account address; it does not hide either chain's public records.

  • Reduces the obvious link between the AVAX deposit and ETH receipt
  • Compare standard and Private Route options for Linea → zkSync Era
  • Shows what remains public on Linea and zkSync Era before you deposit
Check Private Route availability →

Related routes

Swap AVAX on Linea to ETH on zkSync Era FAQs

What exactly leaves Linea as AVAX?

AVAX is a contract representation on Linea with 18 decimals at 0x5471ea8f739dd37E9B81Be9c5c77754D8AA953E4. ETH, not AVAX, pays gas unless both symbols are the same. A Linea source is executed on the zkEVM rollup and later proven to Ethereum; L2 inclusion and proof settlement are distinct source milestones. 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.

What exactly arrives on zkSync Era as ETH?

ETH is listed as the native representation on zkSync Era; ETH is used for network gas. 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.

Why does the AVAX to ETH direction matter?

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. On receipt, Determine whether ETH arrives as native destination gas or as a tokenized representation. Only the native balance can directly pay that network’s fees.

What changes between the source and destination asset roles?

AVAX is the deposited native-asset input; ETH is the quoted native-asset output. Source allowance or native-spend rules and destination wallet/representation checks are evaluated separately.

What should be matched before sending AVAX?

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. A Linea source is executed on the zkEVM rollup and later proven to Ethereum; L2 inclusion and proof settlement are distinct source milestones. 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.

What funds the Linea source transaction?

ETH is the native gas asset for Linea. A Linea source is executed on the zkEVM rollup and later proven to Ethereum; L2 inclusion and proof settlement are distinct source milestones. AVAX is token-tracked and can need approval before transfer.

What is the most dangerous wrong-network mistake here?

Sending AVAX on a network other than Linea, or using an address that is not valid for zkSync Era, can prevent detection or delivery. Match both network labels and representations to the active route.

Can I swap AVAX on Linea to ETH on zkSync without KYC?

Requirements are checked for the live AVAX Linea to ETH zkSync quote. Verification requirements can depend on the provider, amount, jurisdiction, and current route. Sasquatch does not verify this route as universally no-KYC; check the live flow before continuing.

View all Help Center FAQs →