Public verifier
Check the receipt yourself.
This runs the real check — canonical JSON, a SHA-256 body hash, the Ed25519 signature, its pinned issuer key, and any signed chain commitment — in your browser. It is the same function the rest of the site calls, not a separate demonstration path. Receipt bytes and verification never leave this browser session.
What was checked
- Receipt format is supported
Passed: governed-receipt/v1
- Signature algorithm is supported
Passed: Ed25519
- Receipt is well-formed
Passed: supported envelope fields and required values are present
- Public key parses (Ed25519, 32 bytes)
Passed: fingerprint 510c17e9e517da7b…
- Signing key is pinned by this verifier
Passed: LockedIn Labs signed synthetic fixture · 510c17e9e517da7b…
- Ed25519 signature verifies against the public key
Passed: signed over the canonical body (sha256 48c9a8f63b0bdd7c…)
key fingerprint · 510c17e9e517da7b88ad36396ef6073866d6dce063de7e3721ddd3dbd6389b8a
The receipt — edit it
Change one character inside body and the signature check fails and names the field that broke. An unknown public key, unsupported envelope label, unsigned step, reordered chain, or broken signed terminal commitment fails as well.
A signature proves integrity relative to a key; it does not establish who owns that key. This verifier turns green only when the signature is valid and the key fingerprint is pinned in its offline issuer registry. The bundled sample uses a one-time LockedIn Labs synthetic fixture key whose private material is not shipped with this site. How the record is built.