An XRP Ledger wallet whose key is on another device
XRP and the tokens issued on the ledger, in a Chrome and Brave extension - while the key that signs stays on a device with no network. The XRP Ledger is the network; XRP is the asset that lives on it, and this wallet says which of the two is leaving your account.
The reserve is read, not guessed
An XRPL account cannot spend below its reserve, and the reserve is a figure the validators vote on - so it is read from the ledger rather than written into the software. What the send screen offers as your maximum is what the chain will actually let go.
The destination tag is part of the recipient
An exchange address without its tag is a payment nobody can attribute. The account itself says whether it requires one, so the warning comes from the chain rather than from a list of exchanges that is wrong the day it goes stale.
Issued tokens, by currency AND issuer
On this ledger an asset is a couple: a currency code and the account that issues it. Two issuers may legitimately use the same code, so a token that borrows a known symbol from another issuer is called out - on the extension and again on the offline device, which re-derives that verdict from the signed bytes rather than believing what the browser said.
Refused before you walk to the Vault
Sending an issued token needs a trust line on both sides, room left under the recipient’s limit, an issuer that has not frozen the line, and a fee that is still XRP. All of it is checked before the ceremony starts, so a refusal costs two reads instead of a walk to another device and two QR scans.
XRP Ledger wallet: questions people ask
Can I hold RLUSD with the Locker Protocol Wallet?
Yes. RLUSD and any issued token on the XRP Ledger appear once a trust line exists, and a trust line can be opened from the wallet - with the reserve it locks and the ceiling you are signing for named before you approve it.
Where is my XRP private key?
On a second device with no network connection - the Locker Vault. The extension holds the address only, and every signature is approved on that device by QR code.
Does it handle destination tags?
Yes, as part of the recipient rather than as an optional field. The wallet also reads whether the destination account requires a tag, and refuses to stage a payment without one when it does.
Do XRPL apps connect to it?
Not yet, and that is deliberate: no injection standard has settled on the XRP Ledger, so the wallet ships the chain without pretending to a dApp surface. Sending, receiving and tokens work; connecting a site does not.