Bridge BNB from zkSync Era to Ethereum

FromzkSync Era
ToEthereum
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 → Ethereum

Asset

BNB

Source gas

ETH

Destination gas

ETH

How the Sasquatch deposit route works

1. Select the source

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

2. Review the route

Check the estimated output, fees, timing, and Ethereum 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

BNB source representation

BNB is classified as a native asset for this route. BNB uses a network-specific contract asset on zkSync Era. The recorded zkSync Era representation uses 18 decimal places. Native BNB can fund value and BSC gas, while tokenized BNB requires the source chain’s gas asset and contract handling.

Leaving zkSync Era L2 for Ethereum L1

zkSync Era inclusion and its ethereum settlement are distinct from final receipt on Ethereum. The live route, rather than a generic rollup withdrawal assumption, determines the provider path and timing for this direction.

BNB destination representation

BNB is classified as a native asset for this route. BNB uses a network-specific contract asset on Ethereum. The Ethereum side is contract-tracked rather than a native gas balance. Native BSC receipt can fund BNB gas, while externally bridged BNB arrives as a representation that needs the destination chain’s gas token.

Ethereum receipt-side execution

Ethereum is a L1 EVM network in the Ethereum ecosystem. ETH pays destination-side network gas on Ethereum. EVM 0x account address An Ethereum receipt is an L1 native ETH balance or ERC-20 contract event; later token movement can require ETH gas and a new approval for another contract.

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 Ethereum bridge mistakes

Route-specific mistakes include sending on a network other than zkSync Era; using a destination that is not valid for Ethereum; 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 BNB can fund value and BSC gas, while tokenized BNB requires the source chain’s gas asset and contract handling. An Ethereum receipt is an L1 native ETH balance or ERC-20 contract event; later token movement can require ETH gas and a new approval for another contract. Native BSC receipt can fund BNB gas, while externally bridged BNB arrives as a representation that needs the destination chain’s gas token.

Private Route for BNB → BNB

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

Related routes

ZKsync Era to Ethereum FAQs

What BNB representation leaves zkSync Era?

BNB is a contract representation on zkSync Era with 18 decimals at 0x7400793aAd94C8CA801aa036357d10F5Fd0ce08f. ETH, not BNB, 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. Native BNB can fund value and BSC gas, while tokenized BNB requires the source chain’s gas asset and contract handling.

What BNB representation arrives on Ethereum?

BNB is a contract representation on Ethereum at 0xb8c77482e45f1f44de1745f52c74426c631bdd52. ETH, not BNB, pays gas unless both symbols are the same. An Ethereum receipt is an L1 native ETH balance or ERC-20 contract event; later token movement can require ETH gas and a new approval for another contract. Native BSC receipt can fund BNB gas, while externally bridged BNB arrives as a representation that needs the destination chain’s gas token.

Does the same BNB ticker guarantee the same ledger form?

No. This bridge keeps the asset intent while moving between a BNB contract token and a BNB contract token. 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. An Ethereum receipt is an L1 native ETH balance or ERC-20 contract event; later token movement can require ETH gas and a new approval for another contract. 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 Ethereum can prevent normal detection or receipt.

Can I bridge BNB from ZKsync Era to Ethereum without KYC?

Requirements are checked for the live BNB ZKsync Era to Ethereum 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 →