Direction
BNB Chain → Solana
Asset
AVAX
Source gas
BNB
Destination gas
SOL
Choose the AVAX asset and BNB Chain 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.
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; AVAX uses AVAX 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 Avalanche receipt belongs on C-Chain and can fund later gas; an AVAX token on another chain remains a contract balance. A compatible wallet may create or use an associated token account, and SOL—not AVAX 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.
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. The BNB Chain side is contract-tracked rather than a native gas balance. Native AVAX exists on one recorded origin network; other network forms require representation checks. 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. The Solana side is contract-tracked rather than a native gas balance. Native AVAX exists on one recorded origin network; other network forms require representation checks. AVAX leaves as a network-specific contract asset. AVAX arrives as a network-specific contract asset.
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. Native Avalanche receipt belongs on C-Chain and can fund later gas; an AVAX token on another chain remains a contract balance.
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 AVAX 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 BNB pays the EVM source transaction, while 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.
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 receipt uses a native SOL balance or SPL token account identified by mint; later token movement and account creation use SOL fees. Native Avalanche receipt belongs on C-Chain and can fund later gas; an AVAX token on another chain remains a contract balance.
No. This bridge keeps the asset intent while moving between a AVAX contract token and a AVAX contract token. Match the source and output details in the live quote.
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. The bridge output does not automatically fund every later gas need.
Base58-encoded Solana account address Do not substitute a BNB Chain address merely because a wallet displays both networks.
Sending on a network other than BNB Chain, 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 AVAX BNB Chain 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.
