Direction
Polygon → Solana
Asset
BNB
Source gas
POL
Destination gas
SOL
Choose the BNB asset and Polygon 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.
Polygon uses EVM account addresses and POL 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. BNB uses BNB contract token on the source; BNB uses BNB 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 BSC receipt can fund BNB gas, while externally bridged BNB arrives as a representation that needs the destination chain’s gas token. A compatible wallet may create or use an associated token account, and SOL—not BNB unless it is SOL—pays later Solana fees.
POL is the native gas asset for Polygon. BNB is contract-tracked and can require an allowance before transfer. A Polygon PoS source uses its validator/checkpoint system and POL gas; its token contracts and checkpoints are separate from Ethereum L1.
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 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 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 Polygon; using a destination that is not valid for Solana; running out of POL before the source transaction is submitted; assuming evm and solana addresses are interchangeable. A Polygon PoS source uses its validator/checkpoint system and POL gas; its token contracts and checkpoints are separate from Ethereum L1. Native BNB can fund value and BSC gas, while tokenized BNB requires the source chain’s gas asset and contract handling. 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 BSC receipt can fund BNB gas, while externally bridged BNB arrives as a representation that needs the destination chain’s gas token.
Polygon wallet, token-transfer, contract, log, and gas activity remain public, and Solana account, token, program, signature, and fee activity remain public. For this BNB on Polygon to BNB 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 POL pays the EVM source transaction, while SOL is used for later Solana activity.
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 source uses its validator/checkpoint system and POL gas; its token contracts and checkpoints are separate from Ethereum L1. 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 Solana with 8 decimals at 9gP2kCy3wA1ctvYWQk75guqXuHfrEomqydHLtcTCqiLa. SOL, not BNB, 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 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 Polygon PoS source uses its validator/checkpoint system and POL gas; its token contracts and checkpoints are separate from Ethereum L1. 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 Polygon address merely because a wallet displays both networks.
Sending on a network other than Polygon, 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 BNB Polygon 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.
