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.
Arbitrum is classified as a governance or utility token for this route. ARB uses a quote-selected representation. A receiving wallet should show the exact ARB contract on the destination. Receipt does not fund ETH gas for later token movement.
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. A receiving wallet should show the exact ARB contract on the destination. Receipt does not fund ETH gas for later token movement.
XRP leaves as a quote-selected representation. ARB arrives as a quote-selected representation.
XRP Ledger addresses, transfers, amounts, fees, and timing remain public, and Arbitrum wallet, token-transfer, contract, log, and gas activity remain public. For this XRP on XRP Ledger to ARB on Arbitrum 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, A receiving wallet should show the exact ARB contract on the destination. Receipt does not fund ETH gas for later token movement.
XRP is the deposited native-asset input; ARB is the quoted token 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. A receiving wallet should show the exact ARB contract on the destination. Receipt does not fund ETH gas for later token movement.
Requirements are checked for the live XRP XRP to ARB Arbitrum 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.
