Direction
Solana → BNB Chain
Asset
SOL
Source gas
SOL
Destination gas
BNB
Choose the SOL 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. SOL is read from its Solana mint or native account, while SOL 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 SOL leaves a Solana account through a signed transaction and pays the fee; wrapped or tokenized SOL uses a token account or external contract 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 SOL receipt uses a Solana address and can fund later fees; wrapped SOL uses an SPL token account and tokenized SOL elsewhere is not native. A Solana address cannot receive this EVM-side output.
Solana is classified as a native asset for this route. SOL uses a native asset on Solana. Native SOL exists on one recorded origin network; other network forms require representation checks. Solana is classified as a native asset for this route. SOL 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 SOL exists on one recorded origin network; other network forms require representation checks. SOL leaves as a native asset. SOL arrives as a network-specific contract 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 SOL leaves a Solana account through a signed transaction and pays the fee; wrapped or tokenized SOL uses a token account or external contract 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 SOL receipt uses a Solana address and can fund later fees; wrapped SOL uses an SPL token account and tokenized SOL elsewhere is not native.
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 SOL on Solana to SOL 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.
SOL is listed as the native representation on Solana; SOL is used for network gas. A Solana source signs over accounts or token accounts, identifies SPL assets by mint, and spends SOL for transaction fees. Native SOL leaves a Solana account through a signed transaction and pays the fee; wrapped or tokenized SOL uses a token account or external contract instead.
SOL is a contract representation on BNB Chain with 18 decimals at 0x570A5D26f7765Ecb712C0924E4De545B89fD43dF. BNB, not SOL, pays gas unless both symbols are the same. 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 SOL receipt uses a Solana address and can fund later fees; wrapped SOL uses an SPL token account and tokenized SOL elsewhere is not native.
No. This bridge keeps the asset intent while moving between a native SOL and a SOL contract token. 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 SOL 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.
