Verifies an extract's Merkle inclusion against a root only when that root is anchored by a recognized source: a recognized OCG artifact/chain envelope (dogfood, our own receipt format), or an external anchor (RFC 3161 timestamp, OpenTimestamps, Sigstore transparency log, or an on-chain commitment composed via VR-1). A self-produced root with no recognized anchor is explicitly refused, not silently passed. The universal self-produced hash-chain explorer stays dead, and this refusal is why.
🔒 All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data — use synthetic or anonymised inputs only.
What this does NOT prove
Inclusion of one leaf under an anchored root does not validate the extract's contents beyond that leaf hash, does not prove the committed set is complete, and does not extend freshness beyond the anchor's own time semantics. An unanchored, self-produced root is refused outright: it is never treated as verified evidence. Driven by amended AS 1105 (FY2026) and the AICPA practice aid on not relying on unanchored chain explorers.
Extract
Anchor Source
–
Determination
–
Anchored
–
Root Match
Anchored inclusion check
What was NOT proven
Compliance Flags
Provenance
Clean-room RFC 6962 (Certificate Transparency) domain-separated Merkle-tree pattern: an independent implementation, no code copied from any CT-log or Merkle library. On-chain anchoring composes with VR-1 (verify_eth_state_proof, art-279); this kernel never re-verifies an EIP-1186 state proof itself.
⚠ DECISION-SUPPORT DRAFT. Not an audit and not a PCAOB opinion. This tool verifies inclusion under an anchored root only; see "What was NOT proven" above.
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_anchored_extract`. Task: Verify an extract's Merkle inclusion against a root only when that root is anchored by a recognized source: a recognized OCG artifact/chain envelope, or an external anchor (RFC 3161 timestamp, OpenTimestamps, Sigstore transparency log, or an on-chain commitment composed via verify_eth_state_proof, VR-1).
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-286-anchored-extract-verifier.html#p=v1.H4sIAAAAAAAA_wECAP3_e31Dv6ajAgAAAA