Check it yourself.

Paste a sealed record or its link. Your browser canonicalises it, hashes it and compares the result with the hash sealed on the record. Only the record id is sent, to fetch that sealed hash.

WHAT VERIFICATION ACTUALLY IS

1
Canonicalise
Sort every key, strip the whitespace, end with one newline.
—
2
Hash
SHA-256 over those exact bytes.
—
3
Compare
Against the hash sealed on the record.
—

RESULT

Nothing checked yet.

Paste a record above and press Verify.

DO IT WITHOUT US

$ jq -S -c . record.json > canonical.json
$ sha256sum canonical.json
<sha256>  canonical.json
# no sha256sum on your Mac? shasum -a 256 canonical.json

Terminal on Mac, any shell on Linux or WSL.

jq -S sorts the keys, -c strips the whitespace. That is the whole canonicalisation. Compare the output against the sealed hash on the record.

IF IT DOES NOT MATCH

Then one of two things is true.

The JSON was edited

by anyone, including us, at any point after sealing

You canonicalised differently

different key order, whitespace or line ending gives a different hash - on Windows, check you used the Windows commands

We cannot tell you which from here. That is the point: the check does not trust us either.

Every record page carries a check hash link. It comes here, pre-filled.

public · no account · works offline

VERIFY A RECORD