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; TRX uses TRX 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 TRX receipt belongs to a Tron address and can support network resources; tokenized TRX on another ledger cannot supply Tron bandwidth or energy. A compatible wallet may create or use an associated token account, and SOL—not TRX 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.
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 TRX receipt belongs to a Tron address and can support network resources; tokenized TRX on another ledger cannot supply Tron bandwidth or energy.
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. Native BNB can fund value and BSC gas, while tokenized BNB requires the source chain’s gas asset and contract handling.
TRON is classified as a native asset for this route. TRX uses a network-specific contract asset on Solana. The recorded Solana representation uses 6 decimal places. Native TRX receipt belongs to a Tron address and can support network resources; tokenized TRX on another ledger cannot supply Tron bandwidth or energy.
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 TRX 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.
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.
TRX is a contract representation on Solana with 6 decimals at GbbesPbaYh5uiAZSYNXTc7w9jty1rpg3P9L4JeN4LkKc. SOL, not TRX, 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 TRX receipt belongs to a Tron address and can support network resources; tokenized TRX on another ledger cannot supply Tron bandwidth or energy.
Native BNB can fund value and BSC gas, while tokenized BNB requires the source chain’s gas asset and contract handling. On receipt, Native TRX receipt belongs to a Tron address and can support network resources; tokenized TRX on another ledger cannot supply Tron bandwidth or energy.
BNB is the deposited native-asset input; TRX is the quoted native-asset output. Source allowance or native-spend rules and destination wallet/representation checks are evaluated separately.
Native BNB can fund value and BSC gas, while tokenized BNB requires the source chain’s gas asset and contract handling. 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 TRX receipt belongs to a Tron address and can support network resources; tokenized TRX on another ledger cannot supply Tron bandwidth or energy.
Requirements are checked for the live BNB Polygon to TRX 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.
