Swap WETH on zkSync Era to DOGE on BNB Chain

FromzkSync Era
ToBNB Chain
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.
DOGE / USD
Price
24h
High
Low
Vol

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.

Leaving zkSync Era L2 for BNB Chain L1

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

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.

BNB Chain destination execution

BNB Chain is a L1 EVM network in the BNB Chain ecosystem. BNB pays destination-side network gas on BNB Chain. EVM 0x account address A BNB Smart Chain receipt uses the BEP-20 contract or native BNB balance selected by the route; later token movement needs BNB gas.

DOGE output identity and receiving

Dogecoin is classified as a UTXO-native asset for this route. DOGE uses a network-specific contract asset on BNB Chain. The recorded BNB Chain representation uses 8 decimal places. Native DOGE receipt creates a Dogecoin UTXO at a compatible address; tokenized DOGE instead appears under a destination contract.

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 BNB Chain 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 DOGE BNB Chain

Route-specific mistakes include sending on a network other than zkSync Era; using a destination that is not valid for BNB Chain; 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 BNB Smart Chain receipt uses the BEP-20 contract or native BNB balance selected by the route; later token movement needs BNB gas. Native DOGE receipt creates a Dogecoin UTXO at a compatible address; tokenized DOGE instead appears under a destination contract.

Private Route for WETH → DOGE

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

Related routes

Swap WETH on zkSync Era to DOGE on BNB Chain 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 BNB Chain as DOGE?

DOGE is a contract representation on BNB Chain with 8 decimals at 0xbA2aE424d960c26247Dd6c32edC70B295c744C43. BNB, not DOGE, pays gas unless both symbols are the same. A BNB Smart Chain receipt uses the BEP-20 contract or native BNB balance selected by the route; later token movement needs BNB gas. Native DOGE receipt creates a Dogecoin UTXO at a compatible address; tokenized DOGE instead appears under a destination contract.

Why does the WETH to DOGE 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, Native DOGE receipt creates a Dogecoin UTXO at a compatible address; tokenized DOGE instead appears under a destination contract.

What changes between the source and destination asset roles?

WETH is the deposited token input; DOGE 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 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 BNB Smart Chain receipt uses the BEP-20 contract or native BNB balance selected by the route; later token movement needs BNB gas. Native DOGE receipt creates a Dogecoin UTXO at a compatible address; tokenized DOGE instead appears under a destination contract.

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 BNB Smart Chain receipt uses the BEP-20 contract or native BNB balance selected by the route; later token movement needs BNB gas.

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 DOGE on BSC without KYC?

Requirements are checked for the live WETH zkSync to DOGE BSC 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 →