Learn NOSHASHI, and the XRP Ledger underneath it

Watch first: 7 short narrated videos

7 VIDEOS · ABOUT 18 MINUTES IN ALL · CAPTIONS ON

Each video covers one idea from the course, with a voiceover and captions. Every figure in them is a real reading already quoted in the lessons, with its ledger index and date. Where a screen needs a live ledger connection, the video explains the screen rather than showing invented results.

1. 1 · What NOSHASHI does (2:32): noshashi.app/learn/videos/01-what-noshashi-does.mp4
2. 2 · XRP Ledger basics (2:35): noshashi.app/learn/videos/02-xrpl-basics.mp4
3. 3 · What an issuer can still do to your tokens (2:49): noshashi.app/learn/videos/03-issuer-powers.mp4
4. 4 · Listed depth versus funded depth (2:28): noshashi.app/learn/videos/04-funded-depth.mp4
5. 5 · Payments: what really arrived (1:49): noshashi.app/learn/videos/05-payments.mp4
6. 6 · How NOSHASHI helps institutions and enterprises (2:26): noshashi.app/learn/videos/06-for-institutions.mp4
7. 7 · The app, screen by screen (3:22): noshashi.app/learn/videos/07-app-tour.mp4

More videos from the XRPL community

Not made by NOSHASHI. These open on YouTube, the XRPL Learning Portal and XRPL Commons, and are the best free places to go deeper on the ledger itself.

• Intro to the XRP Ledger YouTube playlist · a video series on the ledger's key concepts (goes with lessons 1 to 4)
• Intro to the XRPL XRPL Learning Portal · free course: the ledger's history, how it works, key features
• Order books on the XRPL XRPL Learning Portal · part of the free "Deep dive into XRPL DeFi" course (goes with lessons 7 and 8)
• Introduction to the XRP Ledger XRPL Commons Academy · accounts, tokens, the DEX and consensus
• XRPL Commons YouTube channel · short tutorials, each on one transaction type
• XRP Ledger Apex 2024 YouTube playlist · talks from the XRPL developer conference

The official reference pages behind the most important lessons: clawback, the DEX, AMMs, partial payments and permissioned domains.

1 · How the ledger agrees on the truth

ABOUT 6 MINUTES

▶ Watch video 2: XRP Ledger basics (2:35)

The XRP Ledger (XRPL) is a public database, run since 2012, that keeps one shared record of who owns what. Thousands of servers around the world keep identical copies. Anyone can read it. Nobody, including its creators, can quietly change it.

Ledgers, one after another

The record moves forward in steps. Every 3 to 5 seconds the network produces a new ledger: a complete snapshot of every account and balance, plus the transactions that changed things since the last one. Each ledger has a number, its ledger index, which only ever goes up. At the time of writing it is past 107 million.

Consensus: how strangers agree

There is no mining. Instead, special servers called validators compare the transactions they have seen and vote. Each server trusts a list of validators it believes will not collude, called its UNL (Unique Node List). When at least 80% of trusted validators agree on the same set of transactions, that ledger becomes a validated ledger. From that moment it is final: it cannot be reversed or edited.

Ledgers exist in three states:

• Open / current: the ledger still collecting transactions. Its contents can change.
• Closed: no more transactions, but not yet agreed.
• Validated: agreed and final. This is the only kind NOSHASHI reads.

Why this matters for NOSHASHI

Because validated ledgers never change, a reading taken "at ledger 107,207,971" can be checked by anyone, at any time, by asking any server for that same ledger. Every NOSHASHI result carries its ledger index for exactly this reason.

KEY IDEAValidated means final. A ledger index is a timestamp nobody can argue with.

2 · Accounts, keys and reserves

ABOUT 6 MINUTES

Addresses

An account is a place on the ledger that can hold XRP and tokens. It is identified by an address that starts with r and is 25 to 35 characters long, for example Bitstamp's issuing account rvYAfWj5gh67oV6fW32ZzP3Aw4Eubs59B. There is also a newer X-address format that packs an address and a destination tag into one string.

Keys

Control of an account comes from a secret key. The secret (or seed, usually starting with s) generates a key pair: the private key signs transactions, the public key lets everyone check the signature. Anyone with the secret controls the account completely, so it must never be shared. NOSHASHI never asks for one: it only reads public data.

Reserves

To stop people filling the shared ledger with junk, every account must keep some XRP locked as a reserve: a base reserve to exist (currently 1 XRP) plus an owner reserve for each object it owns, such as a trust line or an offer (currently 0.2 XRP each). Validators can vote to change these amounts. Reserved XRP cannot be spent, which is why NOSHASHI distinguishes a balance from what is actually spendable.

What an account records

KEY IDEAWhoever holds the key owns the account. Balance minus reserve is what can actually move.

3 · Transactions and what their results mean

ABOUT 5 MINUTES

Every change to the ledger is a transaction: a signed instruction such as Payment, OfferCreate (place a trade), TrustSet (open a trust line) or AccountSet (change a setting). Each one pays a tiny fee in XRP, called the transaction cost, which is destroyed rather than paid to anyone. When the network is busy the cost rises; NOSHASHI shows this as fee pressure.

Life of a transaction

1. The owner signs it with their key and submits it to a server.
2. The server gives a tentative result. This is not final.
3. Validators include it in a ledger that becomes validated.
4. Its final result is now fixed in the transaction's metadata.

Result codes

KEY IDEAOnly a result in a validated ledger is final. Read the metadata, not the request.

4 · Tokens, issuers and trust lines

ABOUT 6 MINUTES

Besides XRP, the ledger carries tokens (also called issued currencies or IOUs): digital dollars and euros, gold, tokenized treasury bills, shares. Every token is created by an issuer, an account that promises the token is backed by something. Stablecoins such as Ripple's RLUSD, Braza's BBRL, Schuman's EURØP and Novatti's AUDD are all issued this way on the XRPL.

Trust lines

To hold a token you open a trust line to its issuer with a TrustSet transaction. A trust line is a two-way link between you and the issuer that records a limit (the most you are willing to hold) and your balance. Each trust line you own counts toward your reserve.

Currency codes do not prove anything

A token is identified by two things together: its currency code (a 3-character code like USD, or a 40-character hex code for longer names) and its issuer address. Anyone can issue a token called USD. The code is a label; the issuer is the identity. Scammers exploit this by sending look-alike tokens to people's accounts.

How much is out there

An issuer's obligations are the total of its tokens held by others, readable with the gateway_balances call. That is the real circulating supply per currency, and it is what NOSHASHI reports as outstanding.

KEY IDEAAsk "who issued this?" before "what is it called?". The issuer address is the token's identity.

5 · What an issuer can still do to your tokens

ABOUT 8 MINUTES · THE MOST IMPORTANT LESSON

▶ Watch video 3: What an issuer can still do to your tokens (2:49)

Issuers can turn on powers, stored as flags on their account and settings on each trust line. They are public, but almost no wallet shows them. They decide whether a token is really yours.

Real readings

These are real certificates read from validated mainnet on 24 September 2026. You can re-run any of them for free on the certificate page.

How to read this: the NO-GO verdicts come from a blocking check, "no single key controls the issuer", failing. That is not an accusation. Keeping freeze rights is normal and often required for a regulated issuer. The certificate simply states what the issuer can still do, so a holder decides knowingly. Sologenic scores HOLD, not GO, only because it charges a transfer fee (a warning) and supply concentration was not measured.

KEY IDEAA token can be yours on paper and still be frozen or taken back. Read the issuer's powers before you hold it.

6 · Who really controls an account

ABOUT 6 MINUTES

An account can be signed for in three ways, and more than one can be active at once:

• Master key: the original key pair. It can be disabled with lsfDisableMaster, but only if another way to sign exists.
• Regular key: a second key the account nominates. Useful for keeping the master key offline; it can be changed or removed.
• Signer list (multi-signature): up to 32 signers, each with a weight. A transaction is valid when the weights of those who signed add up to the quorum.

Worked example: counting a quorum

Blackholing

An issuer that disables its master key, sets its regular key to an address whose private key cannot exist (such as rrrrrrrrrrrrrrrrrrrrBZbvji), and has no signer list is blackholed. Nobody can ever sign for it again: its settings and supply are frozen in time, for better and worse.

KEY IDEACount weights, not people, and check whether a master key can skip the whole process.

7 · The DEX and order books

ABOUT 8 MINUTES

▶ Watch video 4: Listed depth versus funded depth (2:28)

The XRPL has had a built-in exchange, the DEX, since 2012. Anyone can post an offer with OfferCreate, for example "sell 100 USD.Bitstamp for 190 XRP". All offers for one pair form an order book: bids on one side, asks on the other. The best prices meet in the middle; the average of the best bid and best ask is the mid price, and the gap is the spread.

When a new offer matches an existing one, they cross and trade. Token-to-token trades can be auto-bridged through XRP when that gives a better price.

Listed depth versus funded depth

Here is the catch that most tools miss. An offer stays on the book even after its owner no longer has the funds to fill it. It is still listed, but it cannot trade. These are unfunded offers. So:

• Listed depth = everything shown on the book.
• Funded depth = only what owners can actually deliver.

The ledger reports this itself. When you ask a server for a book with book_offers, an offer whose owner cannot cover it comes back with an extra field, taker_gets_funded, showing how much they really have. Adding up the listed amounts overstates the market.

A real measurement

Six XRPL pairs, measured with the same method on 8 September 2026 at ledger 106,850,266. "Ratio" is listed depth divided by funded depth within 10% of the mid price.

Median 4.4×. Deep stablecoin books are close to honest; the gap is concentrated in long-tail assets.

KEY IDEAListed depth is an advert. Funded depth is what you can actually get out at.

8 · AMM pools

ABOUT 5 MINUTES

Since the AMM amendment (XLS-30), the XRPL also has automated market makers: pools that hold two assets, for example XRP and a stablecoin, and trade against anyone at a price set by the ratio of the two balances. The DEX routes trades through both order books and pools, whichever is better.

• Liquidity providers deposit both assets and receive LP tokens, a share of the pool.
• Every swap pays a trading fee (up to 1%) that goes to the pool. LP token holders vote on the fee, weighted by how many LP tokens they hold.
• The auction slot is a seat anyone can bid LP tokens for. Its holder trades at a heavily discounted fee for a period, which rewards active traders who keep the pool's price in line.
• A pool whose asset is frozen by its issuer can be frozen too.

NOSHASHI's Pool Governance screen shows who votes the fee, what share of LP tokens those votes represent, and who holds the auction slot, because a pool whose fee is set by one large holder behaves differently from one with a spread of voters.

KEY IDEAA pool's fee and discounts are governed by whoever holds the most LP tokens. Check who that is.

9 · Payments in depth

ABOUT 7 MINUTES

▶ Watch video 5: Payments: what really arrived (1:49)

Partial payments

A Payment's Amount field says how much should arrive. But if the sender sets the partial payment flag (tfPartialPayment), the Amount becomes only a maximum. The payment can deliver far less and still finish with tesSUCCESS.

The authoritative figure is delivered_amount in the transaction's metadata. The XRPL's own documentation tells applications to credit that. Exchanges that credited Amount instead have been drained: attackers sent "large" payments that delivered almost nothing and withdrew the difference.

Other payment tools

KEY IDEACredit what was delivered, never what was asked for.

10 · NFTs and the rights issuers keep

ABOUT 4 MINUTES

The XRPL supports native NFTs (non-fungible tokens, XLS-20): unique tokens for art, tickets, deeds or memberships. Each one has a 64-character NFTokenID, and the ID itself encodes the rules the issuer set when minting:

• Burnable: the issuer can destroy it, even while you own it.
• Transferable: if not set, you can only sell it back to the issuer.
• Only XRP: it can only be sold for XRP.
• Mutable: the issuer can change what its URI points at, so the picture or document can change after you buy it.
• Transfer fee: the issuer takes up to 50% of every resale.

Because these rules are inside the ID, NOSHASHI's Token Rights screen can decode them without even contacting the ledger.

KEY IDEAOwning an NFT does not mean the issuer is done with it. Its ID tells you what they kept.

11 · Amendments: how the rules change

ABOUT 4 MINUTES

The XRPL's rules are changed by amendments. A new feature is written into the server software, then validators vote. It switches on only when it keeps at least 80% support for two weeks in a row. Servers that have not upgraded when an amendment activates become amendment blocked and stop following the ledger.

Many features in this course arrived this way: AMM (XLS-30), Clawback (XLS-39), NFTs (XLS-20), Credentials (XLS-70), Permissioned Domains (XLS-80) and Deep Freeze (XLS-77). "XLS" numbers are the public proposals behind them. NOSHASHI's Domain Grid lists which amendments are enabled.

KEY IDEANew rules need a supermajority for two weeks. What is enabled today is readable from the ledger.

12 · Compliance and regulation, made simple

ABOUT 8 MINUTES

Compliance means following the laws that apply to moving money. For anyone handling XRPL assets professionally, it comes down to two questions: am I allowed to move this, and could I actually get out of it? The first is law and policy. The second is market reality.

The words you will meet

• KYC (Know Your Customer): verifying who a customer is.
• AML (Anti-Money-Laundering): rules and monitoring to stop criminal money.
• Sanctions screening: checking that no party is on a government blocklist. Wallet-analytics vendors do this by studying behaviour.
• Travel Rule (FATF Recommendation 16): when a transfer between regulated providers is above a threshold, the sender's and receiver's details must travel with it. FATF suggests USD/EUR 1,000; the US uses USD 3,000; the EU applies it with no minimum. NOSHASHI lets you set your jurisdiction's threshold and tells you when a transfer is in scope.
• VASP / CASP: a virtual (or crypto) asset service provider, the regulated business the rules apply to.
• MiCA: the EU's crypto-asset regulation, which governs stablecoin issuers such as those issuing euro e-money tokens.

What screening misses

Behaviour screening asks "is this counterparty risky?". It cannot see issuer configuration. A perfectly clean holder can be holding a token whose issuer can freeze it or claw it back. That is a property of the asset, not of the person, and it lives in the flags from lesson 5. NOSHASHI reads both sides.

Compliance built into the XRPL

• Credentials (XLS-70): an issuer of credentials (say, a KYC provider) can attach a verifiable credential to an account. It can be checked without revealing the underlying personal data, which is called selective disclosure.
• Permissioned domains (XLS-80): a defined area where only accounts holding the right credentials can take part.
• Counterparty concentration: how much of your activity goes to a few parties, measured with the Herfindahl-Hirschman Index (HHI): square each party's percentage share and add them up. 10,000 means one party has everything.

KEY IDEAKnow who you deal with, know what the asset allows, and keep evidence you can show later.

13 · What NOSHASHI is

ABOUT 4 MINUTES

▶ Watch video 1: What NOSHASHI does (2:32)

NOSHASHI is a desktop app for macOS, Windows and Linux that reads the live XRP Ledger and answers the two compliance questions about any account, token, pool or payment, from the same ledger reading:

1. Am I allowed to move this? Issuer powers, credentials, permissioned domains, Travel Rule scope, counterparty provenance and your own policy rules.
2. Could I actually get out of it? Funded order-book depth, AMM pools, and how concentrated the holders are.

Other tools answer one question or the other: compliance vendors rarely read the order book, and market terminals rarely read the flags. NOSHASHI reads both from the same WebSocket in the same second, and reports them as one result.

Who it is for

14 · How NOSHASHI reads the ledger

ABOUT 5 MINUTES

• Validated only. It reads validated ledgers from mainnet, the real XRP Ledger. Nothing is estimated, simulated or backfilled.
• Four servers, compared. It queries four public servers by name. If they disagree, the disagreement is shown as a finding, never averaged away.
• It says when it cannot tell. Where a figure cannot be established (for example, too little of a supply could be read to measure concentration), the app withholds it and says so, instead of showing zero.
• No keys, no custody. It never asks for a secret key, never signs, never moves money. It only reads public data.
• Stamped and fingerprinted. Every result carries the ledger index it was read at and a SHA-256 digest: a fingerprint of the exact result. Change one character and the digest changes completely.
• Local first. Your adjudication history (up to 10,000 verdicts) is stored on your device. The AI agent runs on your device by default.
• Self-verifying. The app can hash its own program file, so you can confirm you are running the published build.

The calls it makes are standard XRPL server methods, listed in Under the hood, so anyone can reproduce a reading with their own tools.

15 · Install and first launch

ABOUT 5 MINUTES

1. Open Downloads and choose your system: .dmg for Mac (Apple Silicon or Intel), .msi or -setup.exe for Windows, .deb, .rpm or .AppImage for Linux.
2. Install and open it. The landing screen shows the ledger live. Continue into the console.
3. Glance at Mission Control first: it confirms the app is connected and shows the latest validated ledger.
4. Use the sidebar on the left. Screens are grouped into Overview, Adjudication, Markets & Exposure, Treasury & Issuance, Record, Intelligence and Public, with System at the bottom.
5. Try Check an Address: paste any address starting with r and press CHECK THIS ADDRESS. The free plan includes 10 checks a month.
6. Visit Settings: appearance (light or dark), notifications, the global keyboard shortcut for the menu-bar HUD, and Updates, where new versions install in place.
7. To unlock paid screens, open Pricing in the app, choose a plan and sign in. Account holds your subscription, two-factor authentication and API keys.

Most input fields take an XRPL address (r…). Transaction and NFT screens take a 64-character hex hash instead. Every action button changes to "READING…" while it works and back when the result is in.

16 · Verdicts, checks and receipts

ABOUT 6 MINUTES

When NOSHASHI adjudicates something, it runs a set of checks, each with a severity. The overall verdict follows from them:

Each individual check reports one of five states:

The receipt

Every verdict produces a cryptographic receipt: what was checked, the ledger index, the rules version, each check's outcome and a SHA-256 digest over all of it. Copy it into your records. Anyone who later recomputes the digest over the same contents gets the same value; if anything was altered, they will not.

Your policy

Checks can be tuned by your organisation's policy: your thresholds and required credentials. When a verdict is shown under a policy it says so, and a verdict shown as "raw ledger facts, no policy applied" means only the built-in checks ran.

KEY IDEARead the verdict, then open the checks: every result names the exact rule that decided it.

17 · Every screen, step by step

ABOUT 25 MINUTES · KEEP IT AS A REFERENCE

▶ Watch video 7: The app, screen by screen (3:22)

In sidebar order. Button names are shown LIKE THIS, exactly as they appear in the app. FREE marks screens that work without a paid plan.

Overview

Adjudication · "am I allowed to move this?"

Markets & Exposure · "could I get out of it?"

Treasury & Issuance

Record

Intelligence

Public tools

Account and extras

18 · For organisations and developers

ABOUT 5 MINUTES

▶ Watch video 6: How NOSHASHI helps institutions and enterprises (2:26)

Organisation policy with four-eyes approval

An organisation can share one policy. A change is saved as a draft, can be simulated against past verdicts to see what it would have changed, and goes pending when submitted. A second person must approve it before it is active (four-eyes). Every step is logged.

Exceptions and evidence requests

When a NO-GO must be overridden for a good reason, a user requests an exception. A reviewer can approve, reject, or request more evidence first. The decision and its reasons are kept with the verdict.

Investigations

An investigation (a case) collects verdicts, readings and notes about one issuer or counterparty. Its log is hash-chained: each entry includes the fingerprint of the one before, so entries cannot be quietly edited or removed. Cases can be shared across an organisation.

Webhooks and the Compliance API

Webhooks send signed notifications of events (for example, a policy activated) to your own systems. The Compliance API offers read access to verdicts and readings for integration; see the API docs.

19 · The Agent and the Observer

ABOUT 4 MINUTES

The Agent is an AI assistant built into the app. By default it runs on your own device through a local model (Ollama or LM Studio), so nothing leaves your machine. You can connect a remote provider with your own API key instead.

• Compliance mode: ask about a reading, a verdict or a rule, and it answers from what the app actually measured.
• Support mode: help with using the app, with human escalation when needed.
• Observer mode: watches the issuers and wallets you care about and raises alerts when something changes, such as an issuer flag flipping. One click opens an investigation with the evidence attached.
• Governance: rules for what the agent may and may not do.

20 · Account security: making an account hard to take over

ABOUT 7 MINUTES

An XRP Ledger account belongs to whoever can sign for it. Nobody at a help desk can reset it, and no transaction can be undone. So security on the XRPL is about one question: who holds a key that can sign, and how easily could someone else get it?

Most accounts are emptied the same way: the secret seed is exposed. It gets typed into a fake wallet or "airdrop claim" site, stored in a cloud note or screenshot, or read off the clipboard by malware. The ledger itself is not broken into.

The four defences, from simplest to strongest

• Keep the master seed offline. Write it on paper or steel, never in a photo, email or cloud note. Nobody legitimate, including NOSHASHI, ever needs it.
• Sign with a regular key held in a hardware wallet (SetRegularKey). Day-to-day signing never touches the master seed. If the regular key leaks, the master key replaces it in one transaction.
• Require several signers for a treasury (SignerListSet, for example two of three). One stolen seed can then move nothing. Then disable the master key, or the signer list can be bypassed.
• Close the doors strangers use. AccountSet flags can refuse unsolicited NFT offers, checks and payment channels, which is how many phishing links arrive. Deposit Authorisation goes further: only senders you approve can pay you at all.

Address poisoning

Wallets show only the first and last few characters of an address. An attacker generates an address whose start and end match one you pay, then sends you a tiny amount so the fake sits in your history right next to the real one. The next time you copy "the usual" address from history, you pay the attacker.

In NOSHASHI

SECURITY CENTER › ACCOUNT CHECK (free) grades any address from A to F. It shows who can sign, recent key and settings changes, poisoning attempts against the account and open doors. It also writes a hardening plan: unsigned transactions you review and sign in your own wallet. SAFE SEND (free) checks an address you are about to pay against your own address book and names any lookalike.

KEY IDEAYour account is exactly as safe as the least protected key that can sign for it. Take addresses from your own records, never from transaction history.

21 · When an account is emptied: what can and cannot be done

ABOUT 7 MINUTES

What to do in the first hour

• Move anything left to a brand-new account created on a device that never held the old seed. Whoever has the old key can empty the rest at any moment.
• Check whether keys were changed. A thief often adds their own regular key or signer list, so they keep signing even after you notice.
• Follow the value. Every movement is public. Trace where it went and where it is now.
• Report it to the police with the evidence: transaction hashes, amounts, times and destination tags. In the US that is the FBI's IC3 (ic3.gov); in the UK, Action Fraud.

The recovery paths that do exist

• A custodial service freezes a deposit. If stolen value was paid to an exchange (an account that requires destination tags), the exchange can identify and freeze the customer behind that tag if reached quickly, usually with a police reference.
• A token's issuer freezes or claws back. Issued tokens are the issuer's obligations. Unless it has given up the right, the issuer can freeze the trust lines holding stolen tokens, and with clawback enabled it can take them back and reissue them.
• Sanctions and law enforcement. If the trail reaches a listed address (OFAC SDN), authorities have powers individuals do not.

How thieves hide the trail, and how it is followed anyway

Thieves spray hundreds of dust payments to bury the real transfers, and move value through throwaway accounts that delete themselves with AccountDelete. A trace that ignores the dust and follows the deletions sees through both. Generated accounts that share an ending (like the "xaman" series above) mark an organised operation.

In NOSHASHI

SECURITY CENTER › INCIDENT RESPONSE (Pro and above) does this for you:

• It reads the key changes that preceded the theft.
• It follows the value hop by hop through payments and account deletions, past the dust.
• It says what became of every account the value reached: still holding it, deleted, an exchange, or sanctioned.
• It rates every recovery path honestly and writes a dossier with a SHA-256 fingerprint for police, exchanges and issuers.

Enterprise traces five hops deep and opens the dossier as an investigation case. Strategic adds Guardian: a signed security_alert webhook within a minute of any watched account's keys changing, and one-click watching of every account in a theft trail.

KEY IDEANothing reverses a validated payment. Speed, evidence and the right request to the right party are what recover funds, when anything can.

22 · Getting XRP back, and signing safely

ABOUT 8 MINUTES

Stolen XRP cannot be pulled back, but a lot of XRP is simply stuck, waiting for its owner to sign one transaction. And most thefts start with one signature the owner did not understand. This lesson covers both.

XRP you can get back

• Matured escrows. An escrow does not pay out on its own. Once its FinishAfter time passes, someone must submit EscrowFinish, or the XRP waits forever.
• Expired escrows and payment channels. After CancelAfter or an expiry, EscrowCancel or a closing PaymentChannelClaim returns what was never paid out, plus the reserve.
• Uncashed checks. A check written to you pays nothing until you submit CheckCash.
• The owner reserve. Every object an account owns locks 0.2 XRP: each trust line, DEX order, NFT offer, ticket and preauthorisation. Removing ones you no longer need frees it. Closing an account entirely with AccountDelete returns everything except a 0.2 XRP fee.

The XRPL's "revoke approvals"

There are no token allowances on the XRP Ledger, but some things you leave open let others take value later:

• a check you wrote (the payee can pull up to its amount);
• an NFT sell offer (anyone, or its named buyer, can take the NFT at that price; at zero it is a giveaway);
• a funded payment channel;
• an old DEX order;
• a regular key or signer you no longer control.

Each can be cancelled with one transaction.

Read before you sign

A phishing site does not need your seed if you will sign for it. The signatures that empty accounts are:

• SetRegularKey or SignerListSet, which hand signing power to someone else;
• AccountDelete, which sends everything to its Destination;
• an NFTokenCreateOffer selling an NFT for nothing.

Decode every request before signing it.

"My deposit never arrived"

A payment that failed moved nothing but its fee. For example, tecDST_TAG_NEEDED means the exchange required a destination tag you did not give, and the XRP is still in your account.

A payment that succeeded without the right tag is in the exchange's pooled account. Only the exchange can credit it, and it usually will if you send the transaction hash, the ledger, the amount and your account details.

Is this account really who it says?

Anyone can write "bitstamp.net" in an account's Domain field. The claim is proven only when that website lists the account in its /.well-known/xrp-ledger.toml. XRP Toolkit's donations account names xrptoolkit.com, and xrptoolkit.com lists it back: that is verified.

In NOSHASHI

In SECURITY CENTER, these tools are free on every plan:

• PRE-SIGN CHECK gives a verdict on any transaction or blob: SAFE-LOOKING, CAREFUL or DO NOT SIGN.
• RECOVER FUNDS lists stuck XRP and reserve, each with its unsigned transaction.
• EXPOSURE AUDIT lists every open permission, each with its revoke.
• DEPOSIT HELP explains a lost deposit and writes the letter to the exchange.
• DOMAIN CHECK verifies an account's claimed domain.
• PERSONAL GUARDIAN sends desktop alerts for three of your own addresses.

Paid plans add more:

• Pro values every holding in XRP, scans 25 addresses at once, watches 50 addresses, and maps SCAM CLUSTERS: the accounts one operation funds and sweeps.
• Institutional scans 500 addresses at once.
• Enterprise maps clusters four hops deep, into a case.
• Strategic watches a whole cluster server-side.

KEY IDEANobody can reverse a theft, but you can finish, cancel, cash and clean up what is yours, and refuse to sign what you have not read.

23 · Protecting customers' XRP

ABOUT 9 MINUTES

Banks' customers have deposit insurance. Customers of a business that holds XRP for them have nothing like it, and when such a business fails they usually learn too late that the XRP was not there. The XRP Ledger cannot insure anyone, but it can prove a great deal. This lesson covers what an institution can prove to its customers, and the tools that stop XRP leaving to the wrong place.

Proof of reserves, and of liabilities

Reserves alone prove little: a business can show a large balance and owe more. The other half is liabilities, what it owes its customers. A Merkle sum tree proves that total without revealing anyone's balance:

• each customer's balance becomes a leaf, keyed by a hash nobody else can link to them;
• pairs of leaves are hashed together with their sums, up to a single root and a total;
• the institution publishes only the root, the total and the number of customers;
• each customer receives the path from their leaf to the root and can check that their balance is counted, and that no branch carries a negative sum (the trick that hides debts).

Reserves divided by that total is the coverage ratio. NOSHASHI reads the named reserve accounts from a validated ledger every day and records an attestation, each one hash-chained to the one before, so a changed record shows.

A protection fund no single key can move

An institution can also set XRP aside to make customers whole up to a limit each, the way a deposit scheme promises a fixed amount per depositor. The ledger shows whether that fund is real:

• locked in escrow until a date: nobody can move it early;
• under a signer list with the master key disabled: several people must sign;
• behind one key: whoever holds it can take it, so it counts for nothing.

Ripple's escrow wallet #03 shows the strongest form: 3.3 billion XRP locked in escrows, the account itself under a 4-of-8 signer list.

This is verification, not insurance. NOSHASHI pays no claims, and no government scheme stands behind a program. It shows what is really set aside.

Stopping XRP leaving to the wrong place

• Withdrawal screening checks a customer's withdrawal before it is signed: whether it will bounce, whether the destination is brand new or hours old (most stolen withdrawals go to fresh accounts), whether it imitates an address the customer used before, and whether it or its funders are OFAC-listed or reported scams.
• The shared scam registry holds addresses institutions reported with transaction evidence, each confirmed by a reviewer who did not file it.
• The phishing link feed reads a validated ledger every minute and keeps every domain advertised in XRP dust. A real relay sprayed 1-drop payments at 99 accounts, then deleted itself into the next account.
• The emergency kit is the ordered set of transactions that saves a compromised account: take back what others can pull, move the value to a cold account, change the keys. Built on tickets, it can be signed today and kept offline.
• Market surveillance reads a token's order-book history: one account placed and replaced 171 EUROP orders in minutes and none filled. That makes a book look deeper than it is, whether it is spoofing or an ordinary market maker re-quoting.

In NOSHASHI

• Free: EMERGENCY KIT with the drainer check, WHO IS THIS?, and SCAM REGISTRY lookups and link checks, in the Security Center and at noshashi.app/protection/ for customers.
• Institutional: proof of reserves with customer inclusion proofs, attested daily, and filing reports to the registry.
• Enterprise: a protection fund and public page, withdrawal screening, and market surveillance.
• Strategic: protection alerts by signed webhook, and the phishing link feed as an API.

KEY IDEAA promise about customers' XRP is worth what the ledger can show: reserves you can read, liabilities each customer can check, and a fund no single key can take.

Eight things you can do today

EACH TAKES 2 TO 10 MINUTES

A · Before paying someone new

1. Open Check an Address, paste their address, press CHECK THIS ADDRESS.
2. Open Provenance, press TRACE PROVENANCE: how old is the account and who funded it?
3. If they are an exchange, confirm the destination tag you were given.
4. Decide knowingly; keep the readings if the amount matters.

B · Before accepting or buying a token

1. Find the token's issuer address, not just its name.
2. Authority → CERTIFY AUTHORITY: can the issuer freeze, claw back or act with one key? What fee does it charge?
3. Order Book → enter the code and issuer → READ THIS BOOK: how much funded depth is there to exit?
4. Issuance: how concentrated are the holders?
5. Passport → GENERATE PASSPORT to keep or share the record.

C · Checking that a payment really arrived

1. Copy the transaction hash from the sender or your history.
2. Settlement → paste it → READ SETTLEMENT.
3. Compare requested with delivered. If the partial-payment flag is set, credit only the delivered amount.

D · Proving who controls a treasury (for an auditor)

1. Control Surface → treasury address → READ CONTROL SURFACE.
2. Record the minimum signers, whether the master key is disabled, and what is locked in reserve.
3. Ledger & Policy → EXPORT for a signed file. Send it with the ledger index; the auditor can re-check both.

E · Running a settlement through your policy

1. Verification → enter the account, destination and amount.
2. Run it. Read GO / HOLD / NO-GO, then open each check.
3. On NO-GO with a legitimate reason, request an exception; a reviewer decides, possibly after asking for evidence.
4. Copy the receipt into your records.

F · Watching issuers you depend on

1. Add the wallets and issuers to Portfolio & Radar with ADD TO BOOK.
2. Turn on the Observer in the Agent.
3. When a flag changes, open the alert and start an investigation in one click.

G · Sorting out unexpected tokens in your wallet

1. Inbox → your address → READ CLAIMS.
2. Anything flagged uncashable is an impersonation. Do not interact with it or visit links in its memo.

H · Changing your organisation's rules safely

1. Ledger & Policy → Policy → create a draft with the new threshold.
2. Simulate it against past verdicts to see what would have changed.
3. Submit it; a second person approves it (four-eyes). It is logged either way.

Free tools on this website

• Authority certificate: paste any issuer address and get the same six checks as the app's Authority screen, with the ledger index and digest. Free and no account needed.
• Misread cases: real examples where a quick reading of the ledger gives the wrong answer.
• Research: measurements and methods, each with its date and ledger.
• Docs: getting started, architecture, receipts, policies, webhooks, the API and troubleshooting.
• Plain-language guide: a shorter introduction.
• Status and Progress: service health and release notes.

Plans, trust and what's next

Current details are on Pricing. The code is public on GitHub, every reading is ledger-stamped and fingerprinted, and security details are on Trust & security.

Coming next

Opt-in crash reporting, a phone-sized layout, translations into seven languages, and an iPhone and iPad version (it already compiles; see the iOS notes).

Questions people ask

Knowledge check

75 QUESTIONS IN 6 ROUNDS · YOUR ANSWERS STAY IN YOUR BROWSER

Answer as many as you like, then press Check my answers. Every answer is explained, right or wrong. Stuck on a word? Open Words used here under a question for plain definitions from the word list.

Rounds 1 to 3 cover the ledger, markets and payments, and the app. Round 4 tests the vocabulary. Round 5 asks how NOSHASHI helps institutions and enterprises: treasuries, compliance teams, desks, payments firms, issuers and auditors. Round 6 covers account security, what to do after a theft, and getting stuck XRP back.

Word list

EVERY TERM IN THIS COURSE, A TO Z

Under the hood

FOR THE CURIOUS