XRP Ledger · XRP
Keep your XRP signing keys off your phone.
Your iPhone prepares an XRP payment. Apple Watch checks the payment and current ledger state before you can approve it.
Current support
XRP Ledger in Cryptograph.
Native assets, token standards, and connection methods differ by network.
- Native asset
- XRP
- Payments
- Native XRP sends and receive-address display.
- Destination tags
- Optional destination tags are shown and bound to the signed payment.
- WalletConnect
- Not currently available for XRP Ledger.
On Apple Watch
What you approve.
An XRP payment is valid only for a particular account sequence and ledger window. Those liveness fields are part of what you approve.
- 01The sender, destination, XRP amount, fee, and destination tag are bound to the signed payment.
- 02The account sequence and LastLedgerSequence appear on Apple Watch.
- 03Apple Watch checks a validated ledger snapshot before display and again before signing.
- 04The request is refused if its sequence is stale or its expiry lies outside the permitted ledger window.
Network-specific security
The watch checks XRP Ledger state twice.
A payment request can become stale while it waits for approval. Cryptograph checks the sending account and validated ledger before showing the request.
Immediately before signing, Apple Watch repeats that check. The sequence must still match and the expiry must remain within twenty validated ledgers.
Current limit
Cryptograph supports native XRP payments.
Issued currencies, path payments, and requests whose consequential fields cannot be shown are not signed.