Arbitrum is classified as a governance or utility token for this route. ARB uses a quote-selected representation. Sending ARB can require a token allowance, while ETH—not ARB—must fund Arbitrum gas. Verify the outbound ARB contract if the source is not Arbitrum.
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.
Sending ARB can require a token allowance, while ETH—not ARB—must fund Arbitrum gas. Verify the outbound ARB contract if the source is not Arbitrum. Native XRP Ledger receipt can require a destination tag at a shared account; a tokenized XRP output instead follows the destination contract.
ARB leaves as a quote-selected representation. XRP arrives as a quote-selected representation.
Arbitrum wallet, token-transfer, contract, log, and gas activity remain public, and XRP Ledger addresses, transfers, amounts, fees, and timing remain public. For this ARB on Arbitrum to XRP on XRP Ledger path, Private Route is intended to reduce the direct visible relationship between activity around the source-side EVM 0x account address 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.
Sending ARB can require a token allowance, while ETH—not ARB—must fund Arbitrum gas. Verify the outbound ARB contract if the source is not Arbitrum. On receipt, Native XRP Ledger receipt can require a destination tag at a shared account; a tokenized XRP output instead follows the destination contract.
ARB is the deposited token input; XRP is the quoted native-asset output. Source allowance or native-spend rules and destination wallet/representation checks are evaluated separately.
Sending ARB can require a token allowance, while ETH—not ARB—must fund Arbitrum gas. Verify the outbound ARB contract if the source is not Arbitrum. 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 ARB Arbitrum 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.
