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.
Sui is classified as a native asset for this route. SUI uses a quote-selected representation. Native SUI exists on one recorded origin network; other network forms require representation checks. Native SUI receipt creates Sui coin objects that can fund later gas. A smart-contract token outside Sui does not become a native object.
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 SUI receipt creates Sui coin objects that can fund later gas. A smart-contract token outside Sui does not become a native object.
XRP leaves as a quote-selected representation. SUI arrives as a quote-selected representation.
XRP Ledger addresses, transfers, amounts, fees, and timing remain public, and Sui account, object, transaction-effect, and fee activity remain public. For this XRP on XRP Ledger to SUI on Sui 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 Sui hexadecimal account address with an object-based asset model; 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 SUI receipt creates Sui coin objects that can fund later gas. A smart-contract token outside Sui does not become a native object.
XRP is the deposited native-asset input; SUI 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 SUI receipt creates Sui coin objects that can fund later gas. A smart-contract token outside Sui does not become a native object.
Requirements are checked for the live XRP XRP to SUI Sui 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.
