Paste any OpenChainGraph artifact JSON below. The verifier recomputes the SHA-256 execution hash client-side and tells you whether it matches the stored value. No data leaves your browser.
✓ Zero network requests on this page, enforced by a CI gate (connect-src 'none' plus a static scan for fetch/XHR/WebSocket) that fails the build if this claim ever stops being true. Scope note: this covers the verifier only, not the separate anchor/timestamping tool, which makes outbound calls to anchor a proof.
Artifact JSON
Load a review bundle (optional, SPEC §27.4 gate-consumer)
Paste {"artifact":{...}, "gate":{"gate_policy":"dual_control","gate_threshold":{"role":"approver","threshold":2}}, "records":[...]}: a chain step's declared gate alongside the artifact it guards and any §27.2 records already collected. Only artifact is required. Loading a bundle runs the same hash verification as above, then evaluates the declared gate automatically. This is an evidence recorder, never a blocker; nothing below disables verification or export.
Artifact metadata
Hash comparison
Stored execution_hash
Computed (this browser)
§20 Anchor Bindings
This artifact carries one or more anchor_bindings entries. This page does not verify the binding itself; see the OCG Receipt Verifier or the Verification Desk for that. It links out to the anchor's own verifier, pre-filled with this artifact's execution_hash.
This artifact's chain.ancestry_digest transitively commits its entire cited ancestor sub-DAG. Paste the artifacts it cites, directly or transitively, as a JSON array below, then walk the digest bottom-up. This page never fetches ancestors; you provide the bundle.
Stored ancestry_digest
Status
Computed (bottom-up)
Reason
Human accountability (SPEC §27)
Sign an approval/rejection/override record for this artifact, evaluate whether its haGatePolicy precondition is currently satisfied, and assemble a §27.6 evidence bundle. Everything below runs client-side, and no data leaves your browser.
0. Declared gate (from loaded bundle)
gate_policy
Status
Evidence
Reason
Non-blocking: this reflects the declared gate's evidentiary state at load time. It never disables signing, verification, or export below. Add approval records in step 1 (or paste more into the records box in step 2) and click "Load & review bundle" again to re-evaluate.
1. Approval record
2. Gate-precondition evaluator (§27.4–§27.5)
Status
Evidence
Reason
3. Evidence-bundle export (§27.6, Tier 1 JSON)
Assembles a haEvidenceBundle from the artifact above and the records pasted into step 2. This page ships the mandatory Tier 1 JSON export; the SD-JWT Disclosure Workbench's Evidence Bundle tab reuses the same shipped §13.12 exporter to issue this bundle as a selective-disclosure JWT.