Utility guide

Your agent can pay over XRPL. ProofRelay proves what it bought.

Use PREP-4 x402-XRPL evidence to bind payment requirements, transaction references, facilitator receipts, service responses, and replay outcomes without exposing wallet keys, prompts, paid data, or customer files.

Minimal evidence shape

original_request_hash
sha256...
payment_requirement_hash
sha256...
payment_payload_hash
sha256...
xrpl_tx_hash
64-hex transaction reference
prep4_evidence_bundle_hash
0x...

When to use this

  • An agent or buyer pays for an API, MCP, data, or tool result using x402-XRPL.
  • The resource operator needs proof of what was requested, paid for, delivered, and replay-checked.
  • A reviewer needs public-safe hashes instead of wallet keys, raw prompts, private paid data, or logs.

Template

{
  "proofrelay_profile": "PREP-4-xrpl-payment-v0.1",
  "x402_xrpl_flow": {
    "original_request_hash": "0x...",
    "payment_requirement_hash": "0x...",
    "payment_payload_hash": "0x...",
    "facilitator_receipt_hash": "0x...",
    "service_response_hash": "0x...",
    "replay_result_hash": "0x..."
  },
  "settlement": {
    "network": "mainnet",
    "tx_hash": "64-hex...",
    "validated_ledger": true
  }
}

Local demo commands

python -m src.prep.validator validate configs/revenue/proofrelay_samples/prep4_x402_xrpl/valid_x402_xrpl_prep4.json
python scripts/revenue/canary_proofrelay_x402_xrpl.py --strict

Boundary

ProofRelay verifies internal evidence consistency, receipt ordering, payment or entitlement context, hash-chain continuity, and replay behavior for submitted non-confidential bundles.

ProofRelay does not process payments, custody funds, settle x402 charges, certify legal/title status, verify real-world truth, review source code, or certify model safety.

x402-XRPL moves value; ProofRelay verifies the evidence around the paid action. ProofRelay is not a wallet, custodian, facilitator, payment processor, escrow agent, or legal-truth oracle.

ProofRelay offer ladder