Wallet
- An Orchard spending key, kept in this browser (the demo service holds it only if WebAssembly is unavailable — testnet only).
- An XRPL testnet account, funded from the faucet as it is created.
- Your notes and proofs, kept in this browser when it runs WebAssembly. Nothing to install.
XRPL accountpublic
Pool walletoff ledger
Move XRP from your account into the pool. It arrives as a private note. How it worksYour XRPL account pays the pool account. The payment memo commits to the bundle built first; the quorum anchors it once the deposit is on the ledger.
Pay another address inside the pool. Nothing reaches the ledger but the pool's anchor; the recipient sees the note after syncing. How it worksThe bundle is proved, the quorum re-verifies it, and the pool writes one anchor memo to the ledger. Amount, sender and recipient stay inside the pool.
Take XRP back out to any XRPL address. A fresh address keeps your account off the payout; a new address needs at least 1 XRP. How it worksThe quorum marks the note spent first, then pays the destination from the pool account. Amounts and timing stay public, so they can still match a deposit to a payout.
Show a lender you hold at least your private balance in the pool. Nothing moves and nothing is unshielded: each of the pool's signers re-checks the proof on its own node, and the quorum writes the result on your XRPL account as a credential that expires in 24 hours — a lender reads it from the ledger by your address. If your account lacks the pool's entry credential, the app has the demo issuer write it first and confirms it with your signature. Demo-grade: the proof names the notes it proves, so the node operators can see when those notes are next spent; the app spends them to yourself right after, so your later payments are not linked to this proof. How it worksYour wallet proves, in your browser, that unspent notes worth at least your balance are yours — bound to your account, a fresh request id, the current ledger and a 24-hour expiry. Each signer's node re-verifies that proof read-only against its own state; k of N signers then sign a CredentialCreate from the pool account to your account, and your account's own signature accepts it. The credential says "controlled at least X as of ledger L", not "controls it now": a snapshot, not a lock. The signers' nodes see your account, the amount and the ledger window; a lender sees only the credential.
Hand an auditor your viewing key: they can check your history without taking your word for it. Share it only with an auditor you trust. read-only
Activity
Nothing yet. Your first shield will land here.