Independent verification

Re-run the proof yourself.

A WASM verifier from the independent origin monitor.iscc.codes recomputes this proof in your browser. The result below is produced here — the monitor instance monitor.iscc.id is not in the trust path. The audited checker is controlled by no monitor.

Verification record not yet run

Fetch proof bundle from the monitor

Recompute the leaf hash from the record bytes

Walk the Merkle inclusion path

Rebuild the root and match the hub-signed checkpoint

Check the signature against the hub's did:web key

The in-browser WASM checker (/_ds/verify.wasm, loaded via /_ds/wasm_exec.js) recomputes the steps above locally; until it runs, no verdict is claimed.

Skeptical client · split-view check

Compare your own (size, root)

If the checkpoint your client saw disagrees with the monitor's, the hub presented two histories.

Mismatch — possible split view

Illustrative — what a real mismatch shows. No verdict has run unless the verification record above reports one. On a mismatch you would see:

The recomputed proof does not rebuild the hub-signed root: the hub may have shown you a different history. Keep your signed checkpoint and the bundle — both signed histories are evidence. Report it; do not discard either.

This verifier app is a static site on monitor.iscc.codes — a different origin from any monitor instance. It takes the instance to audit as a parameter and recomputes every proof locally, so the instance you point it at is never in the trust path. One audited checker serves the whole federation.