Swap WETH on zkSync Era to WBTC on 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.

What you need to know

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.

WBTC output identity and receiving

Wrapped Bitcoin is classified as a wrapped asset for this route. WBTC uses a wrapped contract asset on Base. The Base side is contract-tracked rather than a native gas balance. WBTC arrives as a wrapper-contract token and must not be sent onward to a native Bitcoin address without an explicit unwrap or bridge path.

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 WBTC 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. WBTC arrives as a wrapper-contract token and must not be sent onward to a native Bitcoin address without an explicit unwrap or bridge path.

Private Route for WETH → WBTC

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 WETH on zkSync Era to WBTC 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 WETH deposit and WBTC 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

Swap WETH on zkSync Era to WBTC on Base FAQs

What exactly leaves zkSync Era as WETH?

WETH is a contract representation on zkSync Era with 18 decimals at 0x5AEa5775959fBC2557Cc8789bC1bf90A239D9a91. ETH, not WETH, pays gas unless both symbols are the same. 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.

What exactly arrives on Base as WBTC?

WBTC is a contract representation on Base at 0x0555e30da8f98308edb960aa94c0db47230d2b9c. ETH, not WBTC, pays gas unless both symbols are the same. A Base receipt belongs to the Base L2 balance and token contract, not Ethereum L1; later activity needs ETH specifically on Base. WBTC arrives as a wrapper-contract token and must not be sent onward to a native Bitcoin address without an explicit unwrap or bridge path.

Why does the WETH to WBTC direction matter?

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. On receipt, WBTC arrives as a wrapper-contract token and must not be sent onward to a native Bitcoin address without an explicit unwrap or bridge path.

What changes between the source and destination asset roles?

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

What should be matched before sending WETH?

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 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. WBTC arrives as a wrapper-contract token and must not be sent onward to a native Bitcoin address without an explicit unwrap or bridge path.

Can the wrapped asset pay native network gas?

No. 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 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.

What funds the zkSync Era source transaction?

ETH is the native gas asset for zkSync Era. A zkSync Era source executes in EraVM with native account-abstraction behavior and ETH fees before proof settlement to Ethereum. WETH is token-tracked and can need approval before transfer.

Can I swap WETH on zkSync to WBTC on Base without KYC?

Requirements are checked for the live WETH zkSync to WBTC 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 Help Center FAQs →