← all claims · /mcp

xrpl.mcp.signed_snapshot_verify

verify_snapshot_signature is stateless — re-derives leaf hash, checks Ed25519 signature against pinned pubkey, checks audit path against chain root, returns verify_result:bool + public_key_fingerprint + issues[].

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

What this claim says

label
verify_snapshot_signature is stateless — re-derives leaf hash, checks Ed25519 signature against pinned pubkey, checks audit path against chain root, returns verify_result:bool + public_key_fingerprint + issues[].
page
/mcp
claim id (yaml)
signed_snapshot_verify
behavior
STEP_CHANGE
Layer 3 source
cryptographic-signature

Risk note

No shared state with the writer, no I/O beyond loading the pinned public key — same verification path a third-party verifier would run. Accepts either the full MCP envelope ({data, proof, server}) or the bare signed payload dict. Malformed input (missing required fields, non-dict envelope, None) raises rather than returning verify_result=False — malformed input is a caller bug, not a verification result. Freshness_contract="≤ 5min" reflects in-process stateless check, not data staleness.

Evidence — code paths that back this claim

Verify

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.