Direction
Bitcoin → ZKsync Era
Asset
BTC → BNB
Source gas
BTC
Destination gas
ETH
Choose the BTC asset and Bitcoin network you currently hold.
Check the estimated output, fees, timing, and ZKsync Era destination network.
Open the live route and follow the exact deposit instructions.
Use the receipt and status page until the destination funds arrive.
Bitcoin uses a UTXO source model while zkSync Era uses a non-UTXO destination model. Native Bitcoin deposits require a supported Bitcoin address, confirmation-aware input handling, and attention to change outputs; an EVM token labeled BTC or WBTC is not native BTC.
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.
Bitcoin is a L1 Bitcoin Script network in the Bitcoin ecosystem. BTC pays source-side network gas on Bitcoin. Native Bitcoin address supported by the route, including network-specific bech32 or legacy formats A Bitcoin source spends UTXOs, creates a fee-bearing transaction and possible change, and waits for the route provider’s confirmation depth.
Bitcoin source execution occurs on L1, while zkSync Era delivery occurs on a separate L2 ledger that settles to ethereum. BTC pays source gas and ETH is the destination gas asset; identical-looking wallet addresses do not merge the balances or transaction histories.
The live quote lists the exact Bitcoin input asset and zkSync Era output representation. A shared ticker is not proof of a shared contract, native ledger, decimals, or wallet support.
Route-specific mistakes include sending on a network other than Bitcoin; using a destination that is not valid for zkSync Era; running out of BTC before the source transaction is submitted; assuming bitcoin and evm addresses are interchangeable. A Bitcoin source spends UTXOs, creates a fee-bearing transaction and possible change, and waits for the route provider’s confirmation depth. A zkSync Era receipt belongs to EraVM account state and uses ETH for later fees; proof settlement to Ethereum remains distinct from L2 delivery.
Bitcoin UTXO inputs, outputs, change, and confirmation history remain public, and ZKsync Era wallet, token-transfer, contract, log, and gas activity remain public. For this BTC on Bitcoin to BNB on ZKsync Era path, Private Route is intended to reduce the direct visible relationship between activity around the source-side Native Bitcoin address supported by the route, including network-specific bech32 or legacy formats and destination-side EVM 0x account address; it does not hide either chain's public records.
Bitcoin is the UTXO source and BTC fees apply before the provider credits zkSync Era. Tokenized BTC on an account chain is not the same ledger asset.
The live route lists assets supported in this direction. Confirm that the selected source representation has an explicit zkSync Era output before depositing.
A Bitcoin source spends UTXOs, creates a fee-bearing transaction and possible change, and waits for the route provider’s confirmation depth. A zkSync Era receipt belongs to EraVM account state and uses ETH for later fees; proof settlement to Ethereum remains distinct from L2 delivery. The bridge output does not automatically fund every later gas need.
EVM 0x account address Do not substitute a Bitcoin address merely because a wallet displays both networks.
Sending on a network other than Bitcoin, selecting a representation not listed by the quote, or entering an address invalid for zkSync Era can prevent normal detection or receipt.
Requirements are checked for the live BTC Bitcoin to ZKsync Era 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.
