evidren
English

Check it yourself.

Drop an Evidence Pack below. Every digest is recomputed and the sha256 chain relinked, entirely in your browser. Nothing is uploaded.

Select the files. They stay on your machine.

The page needs manifest.json to know what to check; audit.jsonl and chain-head.json are what it checks.

Drag the pack folder here

Try it on an example.

A synthetic pack: a scripted session run through the real engine when this page was built, and exported the way evidren evidence exports. It is not anyone's real record.

The sender's fingerprint for it, as a sender would give it to you separately: 57bebee63d5094084ee2039f45a98300204a71b6b398ed46edbf6e1320e1996a

The edited copy changes one recorded deny to allow on line 3. The rewritten copy makes the same change and then recomputes every hash after it. It passes every check on this page. Only its fingerprint differs from the sender's.

Download the example to check it with a shell instead: VERIFY.md, audit.jsonl, chain-head.json, manifest.json, policy.json, shadow-report.json, summary.json.

What you can rely on, and what you cannot.

  1. The files. audit.jsonl is the record, one line per decision. chain-head.json names the last line. manifest.json lists a fingerprint for every file. VERIFY.md explains how to check all of it with a shell alone.
  2. The result. Consistent, or the file and the line where it breaks.
  3. What a pass does not show. That the pack was not rewritten as a whole: for that, compare the fingerprint with one the sender gave you separately. That the recorded events really happened. That nothing is missing: only actions routed through Evidren are recorded, and an absent line cannot be seen. Compliance with any law or standard.
What this page checks 
1. every file's sha256 against the digest recorded in manifest.json
2. every line's prevHash against the sha256 of the previous line
3. chain-head.headHash against the sha256 of the last line

NOT CHECKED: the HMAC tail seal. It is keyed by the install's
redaction key, which never leaves the origin machine. No third
party can check it, this page included. The pack's own manifest
says so: "d18HmacTailSeal": false.

Check 3 catches a tail that was cut off while chain-head.json was left as it was. A pass means the files agree with each other. And because of the NOT CHECKED block, a pass cannot show that nothing was destroyed before export.