Swap WBTC on zkSync Era to SOL 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.
SOL / USD
Price
24h
High
Low
Vol

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 zkSync Era. The recorded zkSync Era 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.

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.

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

SOL output identity and receiving

Solana is classified as a native asset for this route. SOL uses a network-specific contract asset on Base. The recorded Base representation uses 9 decimal places. Native SOL receipt uses a Solana address and can fund later fees; wrapped SOL uses an SPL token account and tokenized SOL elsewhere is not native.

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 WBTC zkSync Era to SOL 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. WBTC leaves through a custodial wrapper contract with token approval and source-chain gas; no native Bitcoin UTXO is spent by that transfer. A Base receipt belongs to the Base L2 balance and token contract, not Ethereum L1; later activity needs ETH specifically on Base. Native SOL receipt uses a Solana address and can fund later fees; wrapped SOL uses an SPL token account and tokenized SOL elsewhere is not native.

Private Route for WBTC → SOL

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 WBTC on zkSync Era to SOL 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 WBTC deposit and SOL 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 WBTC on zkSync Era to SOL on Base FAQs

What exactly leaves zkSync Era as WBTC?

WBTC is a contract representation on zkSync Era with 8 decimals at 0xBBeB516fb02a01611cBBE0453Fe3c580D7281011. ETH, not WBTC, 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. 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 Base as SOL?

SOL is a contract representation on Base with 9 decimals at 0x311935Cd80B76769bF2ecC9D8Ab7635b2139cf82. ETH, not SOL, 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. Native SOL receipt uses a Solana address and can fund later fees; wrapped SOL uses an SPL token account and tokenized SOL elsewhere is not native.

Why does the WBTC to SOL 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, Native SOL receipt uses a Solana address and can fund later fees; wrapped SOL uses an SPL token account and tokenized SOL elsewhere is not native.

What changes between the source and destination asset roles?

WBTC is the deposited wrapped-asset input; SOL 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 WBTC?

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 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. Native SOL receipt uses a Solana address and can fund later fees; wrapped SOL uses an SPL token account and tokenized SOL elsewhere is not native.

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. 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. WBTC is token-tracked and can need approval before transfer.

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

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