← RABBIT HOLE AI

Verify a sealed session

RECOMPUTED ENTIRELY IN YOUR BROWSER · NOTHING IS UPLOADED

Every answer the gate returns ships with a downloadable record: SHA-256 leaf hashes over the query, the response, the receipt, and the rest; a Merkle root over those leaves; and an Ed25519 signature over the root. This page recomputes all of it from the file you give it and shows you each check pass or fail. It runs on your machine — the file is read locally and never leaves the page.

What a green result proves: the record is the one this gate sealed, at the time it claims, and the readable text beside it is the text that was sealed. What it does not prove: that any model was correct. That distinction is the point — verify the artifact, don't trust the vendor.

Every exchange also carries its attribution — the division of labor behind the answer: what you wrote, what the model produced, what the gate substituted, what was retrieved or recalled, each tied to the part of the record that seals it. A signature proves a record wasn't altered; attribution shows who authored which part. Different questions — both answered here.

Drop a verum-session-*.json here, or