Signed integrity snapshots
Every day at 00:05 UTC we capture a small set of canonical metrics (XRPL ledger index, total AMM pools, total TVL, MPT count, named-accounts count), hash them into a Merkle leaf, extend the global chain, and sign the result with our Ed25519 key. Any visitor can fetch a past snapshot, verify the signature against our public key, and prove the number was attested on the recorded date. No other XRPL dashboard publishes cryptographically verifiable historical data.
● chain active
21 snapshots
committed since
2026-05-14.
current chain root
1725e2341ba4c13f01d4fcf88ad8b5bc03d2ff302555ba489936c6d94745cdeb
Snapshots
2026-06-03
2026-06-02
2026-06-01
2026-05-31
2026-05-30
2026-05-29
2026-05-28
2026-05-27
2026-05-26
2026-05-25
2026-05-24
2026-05-23
2026-05-22
2026-05-21
2026-05-20
2026-05-19
2026-05-18
2026-05-17
2026-05-16
2026-05-15
2026-05-14
How to verify a number yourself
- Fetch our public key: /.well-known/snapshots/pubkey.pem (also pinned in /about and in DNS TXT
_xrpld-snapshot-key). - Fetch the signed snapshot for the date you care about, e.g.
/.well-known/snapshots/2026-06-03.json. - Re-derive the leaf hash: SHA-256 of (
0x00|| canonical-JSON of the{signing_domain, schema_version, snapshot_date_utc, metrics}subset). - Reconstruct the chain root by walking the
audit_pathfrom the leaf, hashing pairs with a0x01domain-separator prefix. - Verify the Ed25519 signature:
signature_ed25519against the canonical-JSON of the envelope summary{signing_domain, schema_version, snapshot_date_utc, leaf_hash, leaf_index, leaves_total, chain_root, previous_root}, using the public key from step 1.
One-click verification
Try our verification form — paste a date and a metric name+value, and we'll run all checks server-side and show the result.
Source: signed_snapshot.py in the public repo. Methodology: /methodology.