xrpl.mcp.signed_snapshot_daily

get_signed_snapshot returns the Ed25519-signed daily snapshot for a given ISO date + the Merkle audit path against the chain root (writer: signed_snapshot_walker / signed_snapshot.sign_snapshot).

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.mcp.signed_snapshot_daily.json or send Accept: application/json on this URL. URI is permanent — safe to cite.

What this claim says

label: get_signed_snapshot returns the Ed25519-signed daily snapshot for a given ISO date + the Merkle audit path against the chain root (writer: signed_snapshot_walker / signed_snapshot.sign_snapshot).
page: /mcp
claim id (yaml): signed_snapshot_daily
behavior: STEP_CHANGE
Layer 3 source: cryptographic-signature

Risk note

Absence IS the signal: if the walker has not produced today's snapshot yet, or the date predates the chain start, the tool raises rather than returning a stub. Payload is a pass-through of the on-disk signed envelope (leaf_hash, chain_root, previous_root, audit_path, signature_ed25519, signing_pubkey_fingerprint) — an agent can hand this straight back into verify_snapshot_signature and complete the round-trip receipt. Pinned pubkey served at /.well-known/snapshots/pubkey.pem; chain served at /.well-known/snapshots/chain.json.

Evidence — code paths that back this claim

mcp_tools_signed_snapshot.py:tool_get_signed_snapshot
signed_snapshot.py:sign_snapshot
signed_snapshots/<date>.json (on-disk source of truth)

Verify

CLAIMS.yaml on GitHub walker_health signed snapshot chain methodology · for AI agents

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