ART-604 · Verify-Rails · Agent Trust Registry Family

ERC-8004 Registry Entry Verifier

Checks whether a claimed ERC-8004 agent registry entry (Identity, Reputation, or Validation registry) and an on-chain record you independently read from the registry contract agree field-by-field, and separately whether any address-shaped field in that on-chain record is EIP-55 checksum-valid. Two independently reported findings, never fused into one boolean. Generic schema only, no per-registry-type adapter code.

Generic field-by-field comparison EIP-55 checksum check, independent agent_id always opaque, never resolved

🔒 All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data — use synthetic or anonymised inputs only.

Scope: two supplied records agree, never live chain state

This tool never queries a registry contract itself and makes no network call of any kind. The on-chain_record is whatever you paste in, read by you from a block explorer or your own RPC call, and may already be stale by the time you paste it. A CONSISTENT verdict means the two supplied records agree with each other, not that they reflect the registry's current state. agent_id is compared as an opaque literal string throughout: never parsed as a number, never resolved against an Agent Card or A2A endpoint, and never cached.

Registry context (echoed only, not verified)

FieldRegistry type

FieldChain ID (optional)

FieldRegistry contract address (optional)

Claimed entry (what you believe the registry says; paste any JSON object)

JSONclaimed_entry

On-chain record (what YOU independently read from the registry contract; this tool never fetches it)

JSONonchain_record

–

Overall Determination

–

Entry Consistency

Per-check findings

Check	Verdict	Detail

Field-by-field comparison

Field	Claimed	On-chain	Match

Address checksum findings (independent of the match column above)

Field	Value (on-chain)	Checksum

Compliance Flags

Not proven by this check

⚠ DECISION-SUPPORT DRAFT. Never a claim about current on-chain state, agent trustworthiness, or reputation validity. Checks only whether two supplied records agree, and whether supplied addresses are checksum-well-formed.

OpenChainGraph v0.4 artifact · execution_hash:

–

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 `verify_erc8004_registry_entry`. Task: Check whether a caller-supplied claimed ERC-8004 agent registry entry (Identity, Reputation, or Validation registry) and a caller-supplied on-chain record, independently read by the caller from the registry contract, agree field-by-field, and separately whether any address-shaped field in the on-chain record is EIP-55 checksum-valid.
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.
Open the tool with the sample prefilled: https://ainumbers.co/chaingraph/art-604-erc8004-registry-entry-verifier.html#p=v1.H4sIAAAAAAAA_wECAP3_e31Dv6ajAgAAAA