About xrpldashboard

xrpldashboard is a read-only observatory for the XRP Ledger. We track validators, AMM pools, RWA tokens, whale activity, credentials, amendments, MPTs, lending, and the full spectrum of XRPL on-chain activity. Free for retail users, forever. No wallet connection, no token sales, no trading interface — just public ledger analysis with verifiable methodology.

Launched: May 9, 2026. We're live and actively smoothing out rough edges. If you spot something that looks wrong or doesn't render right, tell us — we'd rather hear it from you than ship around it.

Recent shipping highlights

Mission

Help XRP holders understand on-chain activity. Not get rich. Not sell liquidity. Not push tokens. Just data, explained well, for people who want to understand what they own.

Principles

  1. Retail-free, forever. No paywall will ever bump a retail user.
  2. Plain language over jargon. Every metric is explained simply.
  3. Link out generously. We're a dashboard, not a directory — we send you to XRPSCAN, Bithomp, and others for the granular details they do better.
  4. Editorial voice is part of the product. We make choices about what to show and how — that's the work.
  5. Trust over features. We never sensationalize. We never imply intent we can't verify. We'd rather omit than overstate.
  6. Mission-first. The funding model serves the mission, not the other way around.
  7. Open source. MIT-licensed. The full source is on GitHub — anyone can fork, audit, or self-host.
  8. Transparent metrics. Our visitor analytics (/analytics — including bots and scanner probes) and our infrastructure status (/health) are both publicly viewable. Nothing to hide.

How it works

Every live number on this site — price, TVL, transaction volume, balances — is computed directly from the XRP Ledger. We do not source any metric from third-party analytics APIs (Bithomp, xrpl.to, XPMarket, DefiLlama, etc.). Their products are good — but if we wrapped them for our data, we'd just be a thinner version of their work. Account display labels are a separate concern (see "Reference labels" below) — there, XRPSCAN's public well-known list is one of several sources we layer onto on-ledger identifiers.

Live ledger data

Comes from public XRPL nodes. A node is just a peer in the consensus network — it can't lie about ledger contents without the rest of the network rejecting it. The data is canonical.

Browser-side from wss://xrplcluster.com (XRP Ledger Foundation-operated community cluster); server-side worker from wss://s2.ripple.com. See /methodology for full source breakdown and rotation plan.

Reference labels

Token display names are hand-curated in our open-source repo, each with a verifiable source URL, accepted via public PR review (see TOKEN_NAMES.md). Account labels are layered: a hand-curated first-party list (KNOWN_ACCOUNTS.md, sourced from exchange disclosures and project .toml files) takes priority, with public reference data (XRPSCAN well-known list, AMM and MPT issuer labels we derive ourselves) filling the long tail. Each label's source is recorded so you can tell which is which.

Domain attestation

Beyond hand-curated labels, we cryptographically verify institutional issuers via the on-ledger Domain field + xrp-ledger.toml two-way chain. Verified issuers display a green ✓ badge with their domain name. Currently rendered on /mpt/issuer/<wallet> pages; will extend to /tokens and /whales as more domains attest. See /methodology#attestation for the full mechanism.

Cross-checking

We link out to XRPSCAN, Bithomp, and other sources so you can verify our numbers against alternative readings whenever you want. Linking out for verification strengthens the trust principle, not weakens it.

Methodology notes

Every external dependency we have — XRPL nodes, the Postgres provider, the CDN — is named on /methodology, with the cache TTL of every surface that touches it. If a number on this site is wrong, that's where you find out why.

Signed integrity snapshots

Every UTC day we publish a cryptographically signed snapshot of headline metrics — ledger index, AMM pool count and TVL, MPT count, named-accounts count — chained into an append-only Merkle tree and signed with our Ed25519 key. Anyone can fetch any past snapshot, verify the signature against our published public key, and prove the number was attested by us on the recorded date. No other XRPL dashboard publishes verifiable historical data.

Our signing key fingerprint: 7F:D4:F2:F4:D2:57:7C:BE

The same fingerprint is pinned on /methodology and in DNS TXT _xrpld-snapshot-key.xrpldashboard.com. All three sources must agree — if any one of them is altered without the others, the discrepancy is the alarm. Full public key at /.well-known/snapshots/pubkey.pem; verification form at /snapshots/verify; daily snapshot index at /snapshots/.

How it's funded

Hosting and infrastructure currently run ~$25/month (Render Standard), covered out of pocket. As the project grows we'll be applying for XRPL ecosystem grants, and donations are welcome (see contact email). Eventually a paid institutional tier (API access, alerts, custom dashboards) will help fund the public retail dashboard, which stays free forever.

Who's behind it

Charlie Bruce is the developer behind xrpldashboard. He built it to bring utility and understanding to everyone who interacts with the XRP Ledger — retail holders and institutional investors alike. The goal isn't to serve any particular issuer or exchange; it's to make the ledger legible to the people who use it. Feedback, corrections, and contributions are welcome — see Get involved below.

Get involved