BNB is classified as a native asset for this route. BNB uses a quote-selected representation. Native BNB exists on multiple recorded origin networks; other network forms require representation checks. Native BNB can fund value and BSC gas, while tokenized BNB requires the source chain’s gas asset and contract handling.
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.
Native BNB can fund value and BSC gas, while tokenized BNB requires the source chain’s gas asset and contract handling. Native XRP Ledger receipt can require a destination tag at a shared account; a tokenized XRP output instead follows the destination contract.
BNB leaves as a quote-selected representation. XRP arrives as a quote-selected representation.
BNB Chain wallet, token-transfer, contract, log, and gas activity remain public, and XRP Ledger addresses, transfers, amounts, fees, and timing remain public. For this BNB on BNB Chain 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.
Native BNB can fund value and BSC gas, while tokenized BNB requires the source chain’s gas asset and contract handling. On receipt, Native XRP Ledger receipt can require a destination tag at a shared account; a tokenized XRP output instead follows the destination contract.
BNB is the deposited native-asset input; XRP is the quoted native-asset output. Source allowance or native-spend rules and destination wallet/representation checks are evaluated separately.
Native BNB can fund value and BSC gas, while tokenized BNB requires the source chain’s gas asset and contract handling. 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 BNB BNB 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.
