ART-104 · Wave 20 · MiCA CASP · Travel Rule

TFR Travel-Rule Batch Validator

Validates originator/beneficiary field completeness on synthetic transfer batches. TFR recast Reg. (EU) 2023/1113. Unhosted wallet enhanced DD. Batch conformance + Merkle root.

Zero PII Client-side only TFR Recast Applied 30 Dec 2024 CASP Transitional Cliff 30 Jun 2026
🔒 All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data — use synthetic or anonymised inputs only.
⚠ SYNTHETIC DATA ONLY — Enter only synthetic, hashed, or anonymised transfer data. Do not enter real names, account numbers, wallet addresses, or transaction IDs. This tool validates field structure on synthetic batches only.
Key Dates
KEY DATES — MiCA Title V (CASP) applied 30 Dec 2024 · CASP transitional cliff 30 Jun 2026 (16 EU states) · ESMA MAR-crypto RTS 17 Dec 2024 · TFR recast applied 30 Dec 2024
Presets
Transfer Batch (Synthetic JSON)
Batch Conformance Summary
Flagged Transfers
Compliance Flags
Key Dates
KEY DATES — MiCA Title V (CASP) applied 30 Dec 2024 · CASP transitional cliff 30 Jun 2026 (16 EU states) · ESMA MAR-crypto RTS 17 Dec 2024 · TFR recast applied 30 Dec 2024
⚠ DECISION-SUPPORT DRAFT. Not a filing or legal advice. Verify all thresholds and dates against MiCA Reg. (EU) 2023/1114 and current official sources.
Execution Hash & Artifact
SHA-256 execution hash (JCS canonical):

      

        
    
    
        
        
      

    


    
    

      

    

  







  

    
Ask your agent

    
  

  
Copy this paragraph into Claude, OpenClaw, or any MCP-aware agent to run this exact tool, with this sample, and verify the artifact.

  
Run the AINumbers MCP tool `validate_tfr_travel_rule_batch`. Task: Validate originator/beneficiary field completeness on synthetic/hashed transfer batches (self-/cross-CASP + unhosted-wallet branches) per TFR recast Reg.
Call it with arguments: {"policy_parameters":{}}
Verify before trusting: call `verify_execution_hash` on mcp.ainumbers.co (https://mcp.ainumbers.co/mcp) with the parameter `claimed_hash` set to the returned `execution_hash`, passing the full artifact the run returned (the object containing `policy_parameters` + `output_payload` + `execution_hash`; equivalently `policy_parameters` + `output_payload` with `claimed_hash`), not the bare hash string.
Return the ledger link https://ledger.ainumbers.co/ so a human can re-verify without contacting us.
PII rule: All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data — use synthetic or anonymised inputs only.
Over MCP, the run happens on the AINumbers worker. No AINumbers server stores your inputs.
Open the tool with the sample prefilled: https://ainumbers.co/chaingraph/art-104-tfr-travel-rule-batch-validator.html#p=v1.H4sIAAAAAAAA_wECAP3_e31Dv6ajAgAAAA