A Solana source signs over accounts or token accounts, identifies SPL assets by mint, and spends SOL for transaction fees. A Tron receipt belongs to a T-address as native TRX or the quoted TRC-20 contract; later activity consumes Tron resources or TRX fees. Solana and Tron use different network identities, gas assets, wallet support, confirmation behavior, and destination conventions. Validate each side independently in the current route.
TRX is the native gas asset for Tron. Tron Base58Check address, commonly beginning with T A TRC-20 token transfer is not an ERC-20 transfer even when an asset ticker exists on both sides.
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. Native XRP Ledger receipt can require a destination tag at a shared account; a tokenized XRP output instead follows the destination contract. Verify the exact TRC-20 contract and the Solana representation independently.
Route-specific mistakes include sending on a network other than Solana; using a destination that is not valid for Tron; running out of SOL before the source transaction is submitted; assuming solana and other 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 Tron receipt belongs to a T-address as native TRX or the quoted TRC-20 contract; later activity consumes Tron resources or TRX fees. Native XRP Ledger receipt can require a destination tag at a shared account; a tokenized XRP output instead follows the destination contract.
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. 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.
XRP is classified as a native asset for this route. XRP uses a network-specific contract asset on Tron. The recorded Tron representation uses 6 decimal places. Native XRP Ledger receipt can require a destination tag at a shared account; a tokenized XRP output instead follows the destination contract.
Solana account, token, program, signature, and fee activity remain public, and Tron address, token-transfer, contract, and resource activity remain public. For this SOL on Solana to XRP on Tron 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 Tron Base58Check address, commonly beginning with T; it does not hide either chain's public records.
The Tron side must match the TRC-20 contract or native TRX label shown in the route. The Solana side is a separate network representation.
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.
XRP is a contract representation on Tron with 6 decimals at TTjWeVeYWjsMpoBAuBX6pHGMFPyCgjQctz. TRX, not XRP, pays gas unless both symbols are the same. A Tron receipt belongs to a T-address as native TRX or the quoted TRC-20 contract; later activity consumes Tron resources or TRX fees. Native XRP Ledger receipt can require a destination tag at a shared account; a tokenized XRP output instead follows the destination contract.
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. On receipt, Native XRP Ledger receipt can require a destination tag at a shared account; a tokenized XRP output instead follows the destination contract.
SOL is the deposited native-asset input; XRP is the quoted native-asset output. Source allowance or native-spend rules and destination wallet/representation checks are evaluated separately.
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 Solana source signs over accounts or token accounts, identifies SPL assets by mint, and spends SOL for transaction fees. A Tron receipt belongs to a T-address as native TRX or the quoted TRC-20 contract; later activity consumes Tron resources or TRX fees. Native XRP Ledger receipt can require a destination tag at a shared account; a tokenized XRP output instead follows the destination contract.
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. SOL is recorded as native on this source.
Requirements are checked for the live SOL Solana to XRP Tron 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.
