XRP is classified as a native asset for this route. XRP uses a quote-selected representation. Native XRP exists on one recorded origin network; other network forms require representation checks. Native XRP sending can require XRP Ledger address and destination-tag handling, while tokenized XRP uses the selected smart-contract network.
Solana is classified as a native asset for this route. SOL uses a quote-selected representation. Native SOL exists on one recorded origin network; other network forms require representation checks. Native SOL receipt uses a Solana address and can fund later fees; wrapped SOL uses an SPL token account and tokenized SOL elsewhere is not native.
Verify both asset identities, the selected network, current deposit instructions, and the receiving representation.
Native XRP sending can require XRP Ledger address and destination-tag handling, while tokenized XRP uses the selected smart-contract network. Native SOL receipt uses a Solana address and can fund later fees; wrapped SOL uses an SPL token account and tokenized SOL elsewhere is not native.
XRP leaves as a quote-selected representation. SOL arrives as a quote-selected representation.
XRP Ledger addresses, transfers, amounts, fees, and timing remain public, and Solana account, token, program, signature, and fee activity remain public. For this XRP on XRP Ledger to SOL on Solana path, Private Route is intended to reduce the direct visible relationship between activity around the source-side Classic XRP Ledger r-address; some custodial destinations also require a destination tag and destination-side Base58-encoded Solana account address; it does not hide either chain's public records.
Native XRP sending can require XRP Ledger address and destination-tag handling, while tokenized XRP uses the selected smart-contract network. On receipt, Native SOL receipt uses a Solana address and can fund later fees; wrapped SOL uses an SPL token account and tokenized SOL elsewhere is not native.
XRP is the deposited native-asset input; SOL is the quoted native-asset output. Source allowance or native-spend rules and destination wallet/representation checks are evaluated separately.
Native XRP sending can require XRP Ledger address and destination-tag handling, while tokenized XRP uses the selected smart-contract network. Match the source network shown by the quote. Confirm the destination network in the quote. Native SOL receipt uses a Solana address and can fund later fees; wrapped SOL uses an SPL token account and tokenized SOL elsewhere is not native.
Requirements are checked for the live XRP XRP to SOL 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.
