Direction
Solana → BNB Chain
Asset
BNB
Source gas
SOL
Destination gas
BNB
Choose the BNB asset and Solana network you currently hold.
Check the estimated output, fees, timing, and BNB Chain destination network.
Open the live route and follow the exact deposit instructions.
Use the receipt and status page until the destination funds arrive.
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. BNB 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. Native BNB can fund value and BSC gas, while tokenized BNB requires the source chain’s gas asset and contract handling. 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.
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 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 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 native asset. The ticker remains the same while the ledger representation changes across the route.
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. Native BNB can fund value and BSC gas, while tokenized BNB requires the source chain’s gas asset and contract handling. 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.
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 BNB 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.
The source uses a Solana signature, mint or native account, and SOL fees. The destination uses a 0x account, BNB gas, and the quoted EVM token contract or native balance.
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 source signs over accounts or token accounts, identifies SPL assets by mint, and spends SOL for transaction fees. Native BNB can fund value and BSC gas, while tokenized BNB requires the source chain’s gas asset and contract handling.
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.
No. This bridge keeps the asset intent while moving between a BNB contract token and a native BNB. Match the source and output details in the live quote.
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. The bridge output does not automatically fund every later gas need.
EVM 0x account address Do not substitute a Solana address merely because a wallet displays both networks.
Sending on a network other than Solana, selecting a representation not listed by the quote, or entering an address invalid for BNB Chain can prevent normal detection or receipt.
Requirements are checked for the live BNB Solana to BNB Chain 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.
