← all claims · /snapshots

xrpl.snapshots.signed_snapshot_xrpl_anchor

Each daily chain_root is additionally anchored on the XRP Ledger via Payment memo from anchor rL2yMECEyUT94pLDrAcetMNMG1H4xqpNWQ → ops rwrcJL3Exd1ZUYz11Wug6wvWC448CiTXfd. Weekly, manual cadence.

green Sovereign source — our own infrastructure (local rippled node or Ed25519 signing key). Currently sellable through the future paid tier and signable in the daily snapshot chain.
Machine-readable status: /claims/xrpl.snapshots.signed_snapshot_xrpl_anchor.json or send Accept: application/json on this URL. URI is permanent — safe to cite.

What this claim says

label
Each daily chain_root is additionally anchored on the XRP Ledger via Payment memo from anchor rL2yMECEyUT94pLDrAcetMNMG1H4xqpNWQ → ops rwrcJL3Exd1ZUYz11Wug6wvWC448CiTXfd. Weekly, manual cadence.
page
/snapshots
claim id (yaml)
signed_snapshot_xrpl_anchor
behavior
STEP_CHANGE
Layer 3 source
xrpl_onledger_anchor

Risk note

First anchor tx 01D0BB9D230955F43DB35703E2EB7F5DFA43CEB69CCBBF57FBC8F17407E50DF8 at ledger 106140698, 2026-08-07 21:49:32 UTC, tesSUCCESS. Bootstrap-hop tx E94ADB8CF438EB94DCC00725572CBCC03ACC3084F12DE706AEB4D418B6A7438B (25 XRP anchor→ops funding) is the ONLY sanctioned non-memo outbound from the anchor account, ever — verifiers must allowlist that single hash and reject any other non-memo Payment. MemoData shape v1 (namespace-in-field): `xrpldashboard/anchor/v1|<ISO date>|<chain_root_hex>` (Type A) or `xrpldashboard/anchor-correction/v1|<ISO date>|<prior tx>|<chain_root_hex>` (Type B). Verifiers MUST .strip() MemoData before splitting — Xaman appends 6 trailing newlines. Cadence is weekly, manual today; missed weeks are reconciled explicitly, never backdated. Trust model: the anchor proves timestamped commitment to a published digest — that this exact chain_root existed and was published by this date. It does not prove the underlying analytics are correct; that is the job of the four-layer audit, cross-checks, and published methodology. The anchor makes silent rewriting detectable, not errors impossible. Full amendment history and rejected alternatives: docs/ONLEDGER_ANCHOR_SPEC.md.

Evidence — code paths that back this claim

Verify

Sovereignty classification derives from the claim's Layer 3 source per /methodology. Last verified 2026-09-19. This surface is documented in docs/PAID_MACHINE_TIER_DESIGN.md § 3.1.