What XRP represents
XRP is native to XRP Ledger; XRP representations on other networks are tokenized assets. Native XRP belongs to XRP Ledger and can involve destination-tag requirements at shared accounts. XRP-labeled contracts on other networks are tokenized representations, not native ledger payments.
Native XRP origin
XRP is recorded as native on XRP Ledger. Native status describes the ledger balance and gas behavior on that network, not every token carrying the ticker.
XRP forms away from the origin
Contract forms are recorded on BNB Chain, Tron. Each form needs its own address, wallet, and network check.
XRP network-by-network inventory
XRP Ledger (native), BNB Chain (contract), Tron (contract)
XRP decimal formats differ
Recorded representations use 2 decimal formats. A receiving application must read the destination contract metadata instead of assuming the source precision applies.
Receiving XRP without a network mismatch
A tokenized XRP representation is not a native XRP Ledger payment. Do not infer native XRP Ledger support from an XRP ticker on another network. Native XRP and token representations on other networks are not interchangeable.
Routes arriving as XRP
ARB → XRP, AVAX → XRP, BNB → XRP, BTC → XRP, DAI → XRP, DOGE → XRP, ETH → XRP, HYPE → XRP, LINK → XRP, OP → XRP
Routes spending XRP
XRP → ARB, XRP → AVAX, XRP → BNB, XRP → BTC, XRP → DAI, XRP → DOGE, XRP → ETH, XRP → HYPE, XRP → LINK, XRP → OP
XRP privacy and wallet linking
Approvals, token transfers, wallet reuse, amounts, timing, and later consolidation can remain visible. Private Route availability and identity requirements must be checked separately.