NOSHASHI / LEDGER DESKSTABLECOIN INTELLIGENCE · PUBLIC BETA

01 / FOLLOW THE EVIDENCE

One asset.
Different measures.

RLUSD across the XRP Ledger and Ethereum.
Know what moved. Know what it means.

Supply movement ≠ liquidity movement ≠ trading volume.

Not read. Fetch a snapshot on demand; this page does not poll.

XRP LEDGER

Issuer obligations

Unavailable

No operational-wallet exclusions. Not issuer-reported circulating supply.

No source reading yet.

Two distinct ledger observations are needed for a trend.
Observed samples & exact values

    ETHEREUM

    Contract totalSupply

    Unavailable

    Finalized block, not circulating supply or reserves.

    No source reading yet.

    Two distinct ledger observations are needed for a trend.
    Observed samples & exact values

      The two measurements use different definitions and are never added together. Public node reports do not independently verify consensus, backing, redeemability or legal rights. Cached readings retain their original observation and ledger times.

      02 / CHANGE REVIEW · LOCAL PREVIEW

      Notice a change. Investigate the cause.

      Requires two distinct observations from the same chain.

      Checks the last two samples in this tab only. No background monitoring, saved alert policy or notification delivery. Closing the tab clears samples. A change is not a mint/burn attribution or a liquidity alert.

      03 / ASK THE RIGHT QUESTION

      Evidence before interpretation.

      Supply

      Issuer obligations and contract supply describe outstanding token accounting. Mint/burn attribution needs verified transaction evidence and a defined interval.

      Inspect issuer permissions ↗

      Liquidity

      Funded offers and pool reserves describe particular venues at a moment in time. They do not guarantee an executable price.

      Inspect funded depth ↗

      Activity

      Transfers and trades are different events. No market-wide volume, holder concentration or historical mint/burn total has been measured here.

      Inspect delivered evidence ↗

      04 / SETTLEMENT WORKFLOW · CONCEPT PROTOTYPE

      Follow the handoffs.

      1. 01Issuer
      2. 02Custodian
      3. 03Payment provider
      4. 04Blockchain
      5. 05Settlement
      6. 06Verification
      7. 07Audit record

      Generic workflow, not a claimed integration. Each relationship, asset, chain, settlement condition and permission must be established separately. NOSHASHI can inspect public XRPL delivered-payment evidence; it does not verify off-chain custody or legal settlement.

      Explore the Settlement Exception Desk ↗

      05 / REGULATORY EVIDENCE · STATUS MODEL

      A status is not a verdict.

      PROPOSEDPENDINGFINALEFFECTIVEWITHDRAWNSUPERSEDED

      Tracker prototype: no live regulatory feed loaded. Future entries require jurisdiction, original document, publication date, effective date and human review. A nomination is not an appointment. An article never changes production compliance rules.

      SOURCE REGISTER

      Identity. Method. Limitations.

      Ripple: official token addresses ↗ · Identity checked 13 November 2026.

      XRPL issuer: rMxCKbEDwqr76QuheSUMdEGf4B9xJ8m5De
      Currency: 524C555344000000000000000000000000000000
      Ethereum proxy: 0x8292bb45bf1ee4d140127049757c2e0ff06317ed

      XRPL gateway_balances methodology ↗ · Issuer reserve reporting ↗

      Reserve attestations and reported circulation have separate reporting dates; they are not merged into an on-chain snapshot. Ethereum and XRPL are not an exhaustive inventory of all supported RLUSD networks.

      Bring a workflow.
      Inspect the evidence together.

      Evaluate public issuer settings, delivered payments and funded-depth snapshots with NOSHASHI.

      Explore Risk Desk ↗Request a demo · Become a tester · Discuss a pilot ↗