Solana uses Solana accounts and SOL for source fees, while BNB Chain uses an EVM 0x account and BNB 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 BNB Chain 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 BNB is the native gas asset for BNB Chain. 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 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 BNB Chain; 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 BNB Smart Chain receipt uses the BEP-20 contract or native BNB balance selected by the route; later token movement needs BNB gas. 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 native asset on BNB Chain. The recorded BNB Chain 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 BNB Chain wallet, token-transfer, contract, log, and gas activity remain public. For this AVAX on Solana to BNB on BNB Chain 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. BNB pays later transactions on BNB Chain; 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 listed as the native representation on BNB Chain; BNB is used for network gas. 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 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 BNB Smart Chain receipt uses the BEP-20 contract or native BNB balance selected by the route; later token movement needs BNB gas. 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 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.
