Bridge ETH from zkSync Era to Base

FromzkSync Era
ToBase
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.

Direction

ZKsync Era → Base

Asset

ETH

Source gas

ETH

Destination gas

ETH

How the Sasquatch deposit route works

1. Select the source

Choose the ETH asset and ZKsync Era network you currently hold.

2. Review the route

Check the estimated output, fees, timing, and Base destination network.

3. Create the order

Open the live route and follow the exact deposit instructions.

4. Track delivery

Use the receipt and status page until the destination funds arrive.

What you need to know

ETH source representation

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. Native ETH can fund both transfer value and gas on its selected network. If the source is WETH or another tokenized form, approval and unwrap or exchange logic differ.

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.

ETH destination representation

Ethereum is classified as a native asset for this route. ETH uses a native asset on Base. The recorded Base 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.

Base receipt-side 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.

zkSync Era deposit-side 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.

zkSync Era to Base bridge mistakes

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. A zkSync Era source executes in EraVM with native account-abstraction behavior and ETH fees before proof settlement to Ethereum. Native ETH can fund both transfer value and gas on its selected network. If the source is WETH or another tokenized form, approval and unwrap or exchange logic differ. A Base receipt belongs to the Base L2 balance and token contract, not Ethereum L1; later activity needs ETH specifically on Base. 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 ETH → ETH

ZKsync Era wallet, token-transfer, contract, log, and gas activity remain public, and Base wallet, token-transfer, contract, log, and gas activity remain public. For this ETH on ZKsync Era to ETH on Base 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 ETH deposit and ETH receipt
  • Compare standard and Private Route options for ZKsync Era → Base
  • Shows what remains public on ZKsync Era and Base before you deposit
Check Private Route availability →

Related routes

ZKsync Era to Base FAQs

What ETH representation leaves zkSync Era?

ETH is listed as the native representation on zkSync Era; ETH is used for network gas. A zkSync Era source executes in EraVM with native account-abstraction behavior and ETH fees before proof settlement to Ethereum. Native ETH can fund both transfer value and gas on its selected network. If the source is WETH or another tokenized form, approval and unwrap or exchange logic differ.

What ETH representation arrives on Base?

ETH is listed as the native representation on Base; ETH is used for network gas. A Base receipt belongs to the Base L2 balance and token contract, not Ethereum L1; later activity needs ETH specifically on Base. Determine whether ETH arrives as native destination gas or as a tokenized representation. Only the native balance can directly pay that network’s fees.

Does the same ETH ticker guarantee the same ledger form?

No. This bridge keeps the asset intent while moving between a native ETH and a native ETH. Match the source and output details in the live quote.

Which gas balances matter for this bridge?

A zkSync Era source executes in EraVM with native account-abstraction behavior and ETH fees before proof settlement to Ethereum. A Base receipt belongs to the Base L2 balance and token contract, not Ethereum L1; later activity needs ETH specifically on Base. The bridge output does not automatically fund every later gas need.

What destination address should be used?

EVM 0x account address Do not substitute a zkSync Era address merely because a wallet displays both networks.

What wrong-direction mistake can prevent delivery?

Sending on a network other than zkSync Era, selecting a representation not listed by the quote, or entering an address invalid for Base can prevent normal detection or receipt.

Can I bridge ETH from ZKsync Era to Base without KYC?

Requirements are checked for the live ETH ZKsync Era to Base 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 bridge FAQs →