Solana uses Solana accounts and SOL for source fees, while zkSync Era uses an EVM 0x account and ETH for destination gas. Confirm the destination token contract and do not paste a Solana address into the EVM destination field. AVAX is read from its Solana mint or native account, while BNB arrives at the quoted zkSync Era native or contract representation.
Base58-encoded Solana account address SOL is the native gas asset for Solana. A Solana source signs over accounts or token accounts, identifies SPL assets by mint, and spends SOL for transaction fees. On Avalanche C-Chain, native AVAX funds both the transfer value and gas; on another chain, an AVAX-labelled contract behaves as a token input instead. The mint/account selected by the quote must match the source wallet balance.
EVM 0x account address ETH is the native gas asset for zkSync Era. A zkSync Era receipt belongs to EraVM account state and uses ETH for later fees; proof settlement to Ethereum remains distinct from L2 delivery. Native BSC receipt can fund BNB gas, while externally bridged BNB arrives as a representation that needs the destination chain’s gas token. A Solana address cannot receive this EVM-side output.
Route-specific mistakes include sending on a network other than Solana; using a destination that is not valid for zkSync Era; running out of SOL before the source transaction is submitted; assuming solana and evm addresses are interchangeable. A Solana source signs over accounts or token accounts, identifies SPL assets by mint, and spends SOL for transaction fees. On Avalanche C-Chain, native AVAX funds both the transfer value and gas; on another chain, an AVAX-labelled contract behaves as a token input instead. A zkSync Era receipt belongs to EraVM account state and uses ETH for later fees; proof settlement to Ethereum remains distinct from L2 delivery. Native BSC receipt can fund BNB gas, while externally bridged BNB arrives as a representation that needs the destination chain’s gas token.
Avalanche is classified as a native asset for this route. AVAX uses a network-specific contract asset on Solana. The recorded Solana representation uses 8 decimal places. On Avalanche C-Chain, native AVAX funds both the transfer value and gas; on another chain, an AVAX-labelled contract behaves as a token input instead.
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 BSC receipt can fund BNB gas, while externally bridged BNB arrives as a representation that needs the destination chain’s gas token.
Solana account, token, program, signature, and fee activity remain public, and zkSync Era wallet, token-transfer, contract, log, and gas activity remain public. For this AVAX on Solana to BNB on zkSync Era path, Private Route is intended to reduce the direct visible relationship between activity around the source-side Base58-encoded Solana account address and destination-side EVM 0x account address; it does not hide either chain's public records.
No. EVM 0x account address The BNB output belongs to the quoted EVM representation.
SOL pays source fees on Solana. ETH pays later transactions on zkSync Era; the delivered BNB does not replace that gas balance unless it is the native asset.
AVAX is a contract representation on Solana with 8 decimals at KgV1GvrHQmRBY8sHQQeUKwTm2r2h8t4C8qt12Cw1HVE. SOL, not AVAX, pays gas unless both symbols are the same. A Solana source signs over accounts or token accounts, identifies SPL assets by mint, and spends SOL for transaction fees. On Avalanche C-Chain, native AVAX funds both the transfer value and gas; on another chain, an AVAX-labelled contract behaves as a token input instead.
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 receipt belongs to EraVM account state and uses ETH for later fees; proof settlement to Ethereum remains distinct from L2 delivery. Native BSC receipt can fund BNB gas, while externally bridged BNB arrives as a representation that needs the destination chain’s gas token.
On Avalanche C-Chain, native AVAX funds both the transfer value and gas; on another chain, an AVAX-labelled contract behaves as a token input instead. On receipt, Native BSC receipt can fund BNB gas, while externally bridged BNB arrives as a representation that needs the destination chain’s gas token.
AVAX is the deposited native-asset input; BNB is the quoted native-asset output. Source allowance or native-spend rules and destination wallet/representation checks are evaluated separately.
On Avalanche C-Chain, native AVAX funds both the transfer value and gas; on another chain, an AVAX-labelled contract behaves as a token input instead. A Solana source signs over accounts or token accounts, identifies SPL assets by mint, and spends SOL for transaction fees. A zkSync Era receipt belongs to EraVM account state and uses ETH for later fees; proof settlement to Ethereum remains distinct from L2 delivery. Native BSC receipt can fund BNB gas, while externally bridged BNB arrives as a representation that needs the destination chain’s gas token.
Requirements are checked for the live AVAX Solana to BNB zkSync 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.
