Swap WBTC on Avalanche to WETH on zkSync Era

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

What you need to know

WBTC input identity and handling

Wrapped Bitcoin is classified as a wrapped asset for this route. WBTC uses a wrapped contract asset on Avalanche. The recorded Avalanche representation uses 8 decimal places. WBTC leaves through a custodial wrapper contract with token approval and source-chain gas; no native Bitcoin UTXO is spent by that transfer.

From Avalanche L1 into zkSync Era L2

Avalanche source execution occurs on L1, while zkSync Era delivery occurs on a separate L2 ledger that settles to ethereum. AVAX pays source gas and ETH is the destination gas asset; identical-looking wallet addresses do not merge the balances or transaction histories.

WBTC unwrap or exchange input check

WBTC is a custodial tokenized Bitcoin representation on smart-contract networks. Its transfers use token contracts and approvals rather than native Bitcoin inputs and outputs. On this route WBTC is the source token on Avalanche. 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.

Avalanche source execution

Avalanche is a L1 EVM network in the Avalanche ecosystem. AVAX pays source-side network gas on Avalanche. EVM 0x account address An Avalanche source route uses C-Chain Snowman execution and AVAX gas; X-Chain or P-Chain balances are not valid C-Chain deposits.

EVM-to-EVM execution boundary

Avalanche 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 WBTC Avalanche to WETH zkSync Era

Route-specific mistakes include sending on a network other than Avalanche; using a destination that is not valid for zkSync Era; running out of AVAX before the source transaction is submitted; treating a wrapped token as the native gas asset. An Avalanche source route uses C-Chain Snowman execution and AVAX gas; X-Chain or P-Chain balances are not valid C-Chain deposits. WBTC leaves through a custodial wrapper contract with token approval and source-chain gas; no native Bitcoin UTXO is spent by that transfer. 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.

Private Route for WBTC → WETH

Avalanche 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 WBTC on Avalanche to WETH 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 WBTC deposit and WETH receipt
  • Compare standard and Private Route options for Avalanche → zkSync Era
  • Shows what remains public on Avalanche and zkSync Era before you deposit
Check Private Route availability →

Related routes

Swap WBTC on Avalanche to WETH on zkSync Era FAQs

What exactly leaves Avalanche as WBTC?

WBTC is a contract representation on Avalanche with 8 decimals at 0x50b7545627a5162F82A992c33b87aDc75187B218. AVAX, not WBTC, pays gas unless both symbols are the same. An Avalanche source route uses C-Chain Snowman execution and AVAX gas; X-Chain or P-Chain balances are not valid C-Chain deposits. WBTC leaves through a custodial wrapper contract with token approval and source-chain gas; no native Bitcoin UTXO is spent by that transfer.

What exactly arrives on 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 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.

Why does the WBTC to WETH direction matter?

WBTC leaves through a custodial wrapper contract with token approval and source-chain gas; no native Bitcoin UTXO is spent by that transfer. On receipt, WETH arrives as a token contract balance. It may need an explicit unwrap before becoming native ETH and cannot itself pay transaction gas.

What changes between the source and destination asset roles?

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

What should be matched before sending WBTC?

WBTC leaves through a custodial wrapper contract with token approval and source-chain gas; no native Bitcoin UTXO is spent by that transfer. An Avalanche source route uses C-Chain Snowman execution and AVAX gas; X-Chain or P-Chain balances are not valid C-Chain deposits. 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.

Can the wrapped asset pay native network gas?

No. WBTC leaves through a custodial wrapper contract with token approval and source-chain gas; no native Bitcoin UTXO is spent by that transfer. An Avalanche source route uses C-Chain Snowman execution and AVAX gas; X-Chain or P-Chain balances are not valid C-Chain deposits. A zkSync Era receipt belongs to EraVM account state and uses ETH for later fees; proof settlement to Ethereum remains distinct from L2 delivery.

What funds the Avalanche source transaction?

AVAX is the native gas asset for Avalanche. An Avalanche source route uses C-Chain Snowman execution and AVAX gas; X-Chain or P-Chain balances are not valid C-Chain deposits. WBTC is token-tracked and can need approval before transfer.

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

Requirements are checked for the live WBTC Avalanche to WETH 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 →