BNB Chain uses EVM account addresses and BNB 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. AVAX uses AVAX contract token on the source; ETH uses ETH 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. Determine whether ETH arrives as native destination gas or as a tokenized representation. Only the native balance can directly pay that network’s fees. A compatible wallet may create or use an associated token account, and SOL—not ETH unless it is SOL—pays later Solana fees.
BNB is the native gas asset for BNB Chain. AVAX is contract-tracked and can require an allowance before transfer. A BNB Smart Chain source uses BNB gas and BEP-20 contracts; a familiar 0x account does not turn a BEP-20 deposit into ERC-20.
Route-specific mistakes include sending on a network other than BNB Chain; using a destination that is not valid for Solana; running out of BNB before the source transaction is submitted; assuming evm and solana addresses are interchangeable. A BNB Smart Chain source uses BNB gas and BEP-20 contracts; a familiar 0x account does not turn a BEP-20 deposit into ERC-20. 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 receipt uses a native SOL balance or SPL token account identified by mint; later token movement and account creation use SOL fees. Determine whether ETH arrives as native destination gas or as a tokenized representation. Only the native balance can directly pay that network’s fees.
Avalanche is classified as a native asset for this route. AVAX uses a network-specific contract asset on BNB Chain. The recorded BNB Chain representation uses 18 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.
Ethereum is classified as a native asset for this route. ETH uses a network-specific contract asset on Solana. The recorded Solana representation uses 8 decimal places. Determine whether ETH arrives as native destination gas or as a tokenized representation. Only the native balance can directly pay that network’s fees.
BNB Chain wallet, token-transfer, contract, log, and gas activity remain public, and Solana account, token, program, signature, and fee activity remain public. For this AVAX on BNB Chain to ETH 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. The destination must be a Solana-compatible address. Base58-encoded Solana account address
An SPL-token receipt uses the relevant mint and token account; the wallet or route may create an associated token account when needed. SOL is used for later Solana activity.
AVAX is a contract representation on BNB Chain with 18 decimals at 0x1CE0c2827e2eF14D5C4f29a091d735A204794041. BNB, not AVAX, pays gas unless both symbols are the same. A BNB Smart Chain source uses BNB gas and BEP-20 contracts; a familiar 0x account does not turn a BEP-20 deposit into ERC-20. 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.
ETH is a contract representation on Solana with 8 decimals at 7vfCXTUXx5WJV5JADk17DUJ4ksgau7utNKj4b963voxs. SOL, not ETH, 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. Determine whether ETH arrives as native destination gas or as a tokenized representation. Only the native balance can directly pay that network’s 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. On receipt, Determine whether ETH arrives as native destination gas or as a tokenized representation. Only the native balance can directly pay that network’s fees.
AVAX is the deposited native-asset input; ETH 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 BNB Smart Chain source uses BNB gas and BEP-20 contracts; a familiar 0x account does not turn a BEP-20 deposit into ERC-20. A Solana receipt uses a native SOL balance or SPL token account identified by mint; later token movement and account creation use SOL fees. Determine whether ETH arrives as native destination gas or as a tokenized representation. Only the native balance can directly pay that network’s fees.
Requirements are checked for the live AVAX BSC to ETH 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.
