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.
Bitcoin is classified as a UTXO-native asset for this route. BTC uses a quote-selected representation. Native BTC exists on one recorded origin network; other network forms require representation checks. Native BTC must arrive at a provider-accepted Bitcoin address and becomes a UTXO after broadcast; an EVM address is not a native BTC destination.
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 BTC must arrive at a provider-accepted Bitcoin address and becomes a UTXO after broadcast; an EVM address is not a native BTC destination.
XRP leaves as a quote-selected representation. BTC arrives as a quote-selected representation.
XRP Ledger addresses, transfers, amounts, fees, and timing remain public, and Bitcoin UTXO inputs, outputs, change, and confirmation history remain public. For this XRP on XRP Ledger to BTC on Bitcoin 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 Native Bitcoin address supported by the route, including network-specific bech32 or legacy formats; 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 BTC must arrive at a provider-accepted Bitcoin address and becomes a UTXO after broadcast; an EVM address is not a native BTC destination.
XRP is the deposited native-asset input; BTC 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 BTC must arrive at a provider-accepted Bitcoin address and becomes a UTXO after broadcast; an EVM address is not a native BTC destination.
Requirements are checked for the live XRP XRP to BTC Bitcoin 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.
