Direction
ZKsync Era → Solana
Asset
BNB
Source gas
ETH
Destination gas
SOL
Choose the BNB asset and ZKsync Era network you currently hold.
Check the estimated output, fees, timing, and Solana destination network.
Open the live route and follow the exact deposit instructions.
Use the receipt and status page until the destination funds arrive.
zkSync Era uses EVM account addresses and ETH for source gas. Solana uses Solana accounts, transaction signatures, and SOL for destination activity. A 0x address is not a valid substitute for the Solana receiving address shown by the route. BNB uses BNB contract token on the source; BNB uses BNB contract token on Solana.
Base58-encoded Solana account address A Solana receipt uses a native SOL balance or SPL token account identified by mint; later token movement and account creation use SOL fees. Native BSC receipt can fund BNB gas, while externally bridged BNB arrives as a representation that needs the destination chain’s gas token. A compatible wallet may create or use an associated token account, and SOL—not BNB unless it is SOL—pays later Solana fees.
ETH is the native gas asset for zkSync Era. BNB is contract-tracked and can require an allowance before transfer. A zkSync Era source executes in EraVM with native account-abstraction behavior and ETH fees before proof settlement to Ethereum.
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. The zkSync Era side is contract-tracked rather than a native gas balance. Native BNB exists on multiple recorded origin networks; other network forms require representation checks. BNB is classified as a native asset for this route. BNB uses a network-specific contract asset on Solana. The recorded Solana representation uses 8 decimal places. The Solana side is contract-tracked rather than a native gas balance. Native BNB exists on multiple recorded origin networks; other network forms require representation checks. BNB leaves as a network-specific contract asset. BNB arrives as a network-specific contract asset.
Route-specific mistakes include sending on a network other than zkSync Era; using a destination that is not valid for Solana; running out of ETH before the source transaction is submitted; assuming evm and solana addresses are interchangeable. 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. A Solana receipt uses a native SOL balance or SPL token account identified by mint; later token movement and account creation use SOL fees. Native BSC receipt can fund BNB gas, while externally bridged BNB arrives as a representation that needs the destination chain’s gas token.
ZKsync Era wallet, token-transfer, contract, log, and gas activity remain public, and Solana account, token, program, signature, and fee activity remain public. For this BNB on ZKsync Era to BNB on Solana path, Private Route is intended to reduce the direct visible relationship between activity around the source-side EVM 0x account address and destination-side Base58-encoded Solana account address; it does not hide either chain's public records.
No. Base58-encoded Solana account address ETH pays the EVM source transaction, while SOL is used for later Solana activity.
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.
BNB is a contract representation on Solana with 8 decimals at 9gP2kCy3wA1ctvYWQk75guqXuHfrEomqydHLtcTCqiLa. SOL, not BNB, pays gas unless both symbols are the same. A Solana receipt uses a native SOL balance or SPL token account identified by mint; later token movement and account creation use SOL fees. Native BSC receipt can fund BNB gas, while externally bridged BNB arrives as a representation that needs the destination chain’s gas token.
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.
A zkSync Era source executes in EraVM with native account-abstraction behavior and ETH fees before proof settlement to Ethereum. A Solana receipt uses a native SOL balance or SPL token account identified by mint; later token movement and account creation use SOL fees. The bridge output does not automatically fund every later gas need.
Base58-encoded Solana account address Do not substitute a zkSync Era address merely because a wallet displays both networks.
Sending on a network other than zkSync Era, selecting a representation not listed by the quote, or entering an address invalid for Solana can prevent normal detection or receipt.
Requirements are checked for the live BNB ZKsync Era to Solana 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.
