TFR Travel-Rule Batch Conformance

Note (dated 2026-08-04): a chain composes independent computations performed in an analytical order. No step's output is carried into the next step by the execution model; each step computes from its own declared inputs. This is true of every chain on this site, including chains whose per-step copy below reads as a data handoff.

Originator/beneficiary field completeness on hashed/synthetic transfer batches incl. unhosted-wallet branch (ART-104) -> Merkle integrity (cry-04). Reuses the shipped synthetic-batch screening pattern; no real PII.

OpenChainGraph · 2 Steps cryptographic mandate Hash-Anchored §4 chain_depth:2 Client-Side · Zero PII

Chain Stages · 2 Steps

1 ROOT · D0 node

TFR Travel-Rule Batch Validator art-104-tfr-travel-rule-batch-validator

batch conformance + flagged transfers (H1) feed the verifier

MCP Call · validate_tfr_travel_rule_batch

{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "validate_tfr_travel_rule_batch",
    "arguments": {}
  },
  "id": 1
}

↓

2 TERMINAL · D2 node

Merkle Batch Verifier cry-04-merkle-batch-verifier

Exports composite travel-rule artifact with Merkle-root execution_hash (H2), final stage

MCP Call · verify_merkle_batch

{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "verify_merkle_batch",
    "arguments": {}
  },
  "id": 1
}

Export Artifacts

Download the §4 chain definition artifact (hash-anchored composite JSON) or the §13.11 W3C Verifiable Credentials view. Both derive from the chain definition — no new hash is minted. Available after hash computation.