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.
Ethereum is classified as a native asset for this route. ETH uses a quote-selected representation. Native ETH exists on multiple recorded origin networks; other network forms require representation checks. Determine whether ETH arrives as native destination gas or as a tokenized representation. Only the native balance can directly pay that network’s fees.
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. Determine whether ETH arrives as native destination gas or as a tokenized representation. Only the native balance can directly pay that network’s fees.
XRP leaves as a quote-selected representation. ETH arrives as a quote-selected representation.
XRP Ledger addresses, transfers, amounts, fees, and timing remain public, and Ethereum wallet, token-transfer, contract, log, and gas activity remain public. For this XRP on XRP Ledger to ETH on Ethereum 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 EVM 0x 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, Determine whether ETH arrives as native destination gas or as a tokenized representation. Only the native balance can directly pay that network’s fees.
XRP is the deposited native-asset input; ETH 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. Determine whether ETH arrives as native destination gas or as a tokenized representation. Only the native balance can directly pay that network’s fees.
Requirements are checked for the live XRP XRP to ETH Ethereum 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.
