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. POL uses native POL 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. POL is a native source balance. A Polygon PoS source uses its validator/checkpoint system and POL gas; its token contracts and checkpoints are separate from Ethereum L1.
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 POL can pay Polygon PoS gas, while a POL-labelled contract on another network uses that chain’s gas and token-transfer rules. 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.
POL (ex-MATIC) is classified as a governance or utility token for this route. POL uses a native asset on Polygon. The recorded Polygon representation uses 18 decimal places. Native POL can pay Polygon PoS gas, while a POL-labelled contract on another network uses that chain’s gas and token-transfer rules.
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. 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 POL 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. The destination must be a Solana-compatible address. Base58-encoded Solana account address
An SPL-token receipt uses the relevant mint and token account; the wallet or route may create an associated token account when needed. SOL is used for later Solana activity.
POL is listed as the native representation on Polygon; POL is used for network gas. A Polygon PoS source uses its validator/checkpoint system and POL gas; its token contracts and checkpoints are separate from Ethereum L1. Native POL can pay Polygon PoS gas, while a POL-labelled contract on another network uses that chain’s gas and token-transfer rules.
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.
Native POL can pay Polygon PoS gas, while a POL-labelled contract on another network uses that chain’s gas and token-transfer rules. On receipt, Native BSC receipt can fund BNB gas, while externally bridged BNB arrives as a representation that needs the destination chain’s gas token.
POL is the deposited token input; BNB is the quoted native-asset output. Source allowance or native-spend rules and destination wallet/representation checks are evaluated separately.
Native POL can pay Polygon PoS gas, while a POL-labelled contract on another network uses that chain’s gas and token-transfer rules. 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. Native BSC receipt can fund BNB gas, while externally bridged BNB arrives as a representation that needs the destination chain’s gas token.
Requirements are checked for the live POL Polygon to BNB 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.
