Account identity
Aperture derives and validates the public account under XRP Ledger rules. It does not assign a generic address from another network family.
Supported production mainnet
XRP Ledger in Aperture.
A network-aware home for XRP—with XRP Ledger addresses, fees, asset identity, transaction state, and safety boundaries kept visible.
Understand the network
XRP Ledger is not just a ticker.
XRP Ledger is an account-based payments network with validated ledgers, sequence numbers, reserves, trust lines, and native support for issued currencies.
Address format. A classic address beginning with r, or an X-address that can encode both an account and destination tag.
Many custodial destinations require a destination tag. A correct classic address with a missing or incorrect tag may not be credited to the intended user.
Native asset and tokens
XRP is the native asset and pays the transaction cost. An issued currency is identified by both its currency code and issuer account; the code alone is not authoritative.
Fees and transaction state
The XRP transaction cost is destroyed rather than paid to Aperture. A transaction is final when it is included in a validated ledger with a successful result.
Mainnet boundary
This catalog entry is XRP Ledger mainnet. Aperture’s production catalog does not expose testnet balances, endpoints, or transaction routes.
Receive safely
The network is part of the address.
In Aperture, choose XRP Ledger and the exact asset before copying an address or QR code. The sender, exchange, or bridge must use the same mainnet. A matching symbol, logo, or familiar-looking string does not prove compatibility.
- Confirm the receive screen says XRP Ledger.
- Copy or scan the complete address; do not retype it.
- Check whether the sending service requires an additional memo, tag, or network-specific field.
- For a new route or meaningful amount, consider a small test transfer first.
- Keep the receive screen available until the sender has verified the same network.
Send deliberately
Review what the signature will authorize.
Aperture keeps asset selection, recipient validation, amount, fee review, authorization, broadcast, and finality as distinct stages. Before authorizing a transaction on XRP Ledger, review the full recipient, the XRP amount, and the network fee together.
Blockchain transfers may be irreversible. Aperture cannot cancel a confirmed transaction, recover an incorrect destination, or move an asset that was sent through the wrong network.
Transaction signing happens on the device. Public account data, fee requests, transaction history, and the signed transaction may reach network infrastructure; the private signing key is not part of the broadcast payload.
Verify independently
Use the right source for the right question.
Network documentationUnderstand XRP Ledger protocol rules
Public block explorerInspect XRP Ledger public chain state
Aperture JournalHow accounts and networks stay separate
Aperture JournalReceive crypto safely in Aperture
External documentation and explorers are independent public resources. Their availability, labels, and data are not controlled by Aperture.
Aperture for iPhone and iPad
One interface. 25 mainnets. No blurred boundaries.
Use XRP Ledger alongside Aperture’s other supported mainnets while keeping network identity, asset identity, fees, and transaction status explicit.