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
153 snapshots
committed since
2026-05-14.
current chain root
0db1c17ebcc70c5ebffc588fb40b11761d0ab07d6fb071e2f844f9efc6af2ba1
● on-ledger anchor
Since
2026-08-07, each daily chain_root is additionally
anchored on the XRP Ledger from anchor account
rL2yMECEyUT94pLDrAcetMNMG1H4xqpNWQ to ops account
rwrcJL3Exd1ZUYz11Wug6wvWC448CiTXfd, with the root committed inside
the transaction memo. Cadence is weekly, manual today; the
language upgrades when automation lands.
first anchor
tx 01D0BB9D230955F43DB35703E2EB7F5DFA43CEB69CCBBF57FBC8F17407E50DF8
ledger 106140698 · 2026-08-07 21:49:32 UTC ·
tesSUCCESS
Memo format (v1):
xrpldashboard/anchor/v1|<ISO date>|<chain_root_hex>
in MemoData. Verifiers MUST strip trailing whitespace on the MemoData string
before splitting or comparing (wallet UIs may append newlines). Full spec
including Type A / Type B shapes: see
/methodology#signed-snapshots-xrpl-anchor.
Snapshots
2026-10-17
2026-10-16
2026-10-15
2026-10-14
2026-10-13
2026-10-12
2026-10-11
2026-10-10
2026-10-09
2026-10-08
2026-10-07
2026-10-06
2026-10-05
2026-10-04
2026-10-03
2026-10-02
2026-10-01
2026-09-30
2026-09-29
2026-09-28
2026-09-27
2026-09-26
2026-09-25
2026-09-24
2026-09-23
2026-09-22
2026-09-21
2026-09-20
2026-09-19
2026-09-15
2026-09-14
2026-09-13
2026-09-12
2026-09-11
2026-09-10
2026-09-09
2026-09-08
2026-09-07
2026-09-06
2026-09-05
2026-09-04
2026-09-03
2026-09-02
2026-09-01
2026-08-31
2026-08-30
2026-08-29
2026-08-28
2026-08-27
2026-08-26
2026-08-25
2026-08-24
2026-08-23
2026-08-22
2026-08-21
2026-08-20
2026-08-19
2026-08-18
2026-08-17
2026-08-16
2026-08-15
2026-08-14
2026-08-13
2026-08-12
2026-08-11
2026-08-10
2026-08-09
2026-08-08
2026-08-07
2026-08-06
2026-08-05
2026-08-04
2026-08-03
2026-08-02
2026-08-01
2026-07-31
2026-07-30
2026-07-29
2026-07-28
2026-07-27
2026-07-26
2026-07-25
2026-07-24
2026-07-23
2026-07-22
2026-07-21
2026-07-20
2026-07-19
2026-07-18
2026-07-17
2026-07-16
2026-07-14
2026-07-13
2026-07-12
2026-07-11
2026-07-10
2026-07-09
2026-07-08
2026-07-07
2026-07-06
2026-07-05
2026-07-04
2026-07-03
2026-07-02
2026-07-01
2026-06-30
2026-06-29
2026-06-28
2026-06-27
2026-06-26
2026-06-25
2026-06-24
2026-06-23
2026-06-22
2026-06-21
2026-06-20
2026-06-19
2026-06-18
2026-06-17
2026-06-16
2026-06-15
2026-06-14
2026-06-13
2026-06-12
2026-06-11
2026-06-10
2026-06-09
2026-06-08
2026-06-07
2026-06-06
2026-06-05
2026-06-04
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-10-17.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.