Direction
Solana → Polygon
Asset
BNB
Source gas
SOL
Destination gas
POL
Choose the BNB asset and Solana network you currently hold.
Check the estimated output, fees, timing, and Polygon 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 Polygon uses an EVM 0x account and POL 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 Polygon 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 POL is the native gas asset for Polygon. A Polygon PoS receipt follows Polygon token contracts and checkpointed execution; later movement uses POL gas rather than Ethereum L1 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 network-specific contract asset on Polygon. The recorded Polygon representation uses 18 decimal places. The Polygon 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 leaves as a network-specific contract asset. BNB arrives as a network-specific contract asset.
Route-specific mistakes include sending on a network other than Solana; using a destination that is not valid for Polygon; 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 Polygon PoS receipt follows Polygon token contracts and checkpointed execution; later movement uses POL gas rather than Ethereum L1 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 Polygon wallet, token-transfer, contract, log, and gas activity remain public. For this BNB on Solana to BNB on Polygon 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, POL 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 a contract representation on Polygon with 18 decimals at 0x5c4b7CCBF908E64F32e12c6650ec0C96d717f03F. POL, not BNB, pays gas unless both symbols are the same. A Polygon PoS receipt follows Polygon token contracts and checkpointed execution; later movement uses POL gas rather than Ethereum L1 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 BNB 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 Polygon PoS receipt follows Polygon token contracts and checkpointed execution; later movement uses POL gas rather than Ethereum L1 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 Polygon can prevent normal detection or receipt.
Requirements are checked for the live BNB Solana to Polygon 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.
