TRON is classified as a native asset for this route. TRX uses a quote-selected representation. Native TRX exists on one recorded origin network; other network forms require representation checks. Native TRX can supply Tron bandwidth or energy resources and fees. Tokenized TRX outside Tron follows the source contract ledger.
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 Ledger receipt can require a destination tag at a shared account; a tokenized XRP output instead follows the destination contract.
Verify both asset identities, the selected network, current deposit instructions, and the receiving representation.
Native TRX can supply Tron bandwidth or energy resources and fees. Tokenized TRX outside Tron follows the source contract ledger. Native XRP Ledger receipt can require a destination tag at a shared account; a tokenized XRP output instead follows the destination contract.
TRX leaves as a quote-selected representation. XRP arrives as a quote-selected representation.
Tron address, token-transfer, contract, and resource activity remain public, and XRP Ledger addresses, transfers, amounts, fees, and timing remain public. For this TRX on Tron to XRP on XRP Ledger path, Private Route is intended to reduce the direct visible relationship between activity around the source-side Tron Base58Check address, commonly beginning with T and destination-side Classic XRP Ledger r-address; some custodial destinations also require a destination tag; it does not hide either chain's public records.
Native TRX can supply Tron bandwidth or energy resources and fees. Tokenized TRX outside Tron follows the source contract ledger. On receipt, Native XRP Ledger receipt can require a destination tag at a shared account; a tokenized XRP output instead follows the destination contract.
TRX 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 TRX can supply Tron bandwidth or energy resources and fees. Tokenized TRX outside Tron follows the source contract ledger. Match the source network shown by the quote. Confirm the destination network in the quote. Native XRP Ledger receipt can require a destination tag at a shared account; a tokenized XRP output instead follows the destination contract.
Requirements are checked for the live TRX TRON to XRP XRP 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.
