Run it yourself
Nothing on this page is a promise. It is a check you run.
Every panel below executes in your browser, against the same engine files this
site ships. No server, no API key, no network call. Open your developer console if you would rather
drive it by hand — assets/lockchain.mjs and assets/crypto.mjs are plain ES
modules with no dependencies.
1 · Ed25519 against the RFC 8032 test vectors
The signing code is not taken on trust. These are the official test vectors from RFC 8032 §7.1: a known secret key must produce a known public key and a known signature, byte for byte. The panel also feeds the verifier a tampered message and a wrong key, because a verifier that only ever says yes has not been tested.
2 · Build a ledger, then break it four different ways
This builds a small custody chain, commits a signed checkpoint over it, and verifies all four integrity layers. Then it damages the record four times — once per layer — and shows each layer catching its own damage and only its own. A layer nobody has watched fail is not a layer.
3 · The duplicate-leaf collision
A Merkle root over an odd number of leaves, where the last leaf is duplicated to pad the level,
is ambiguous: a tree over three events can share a root with a tree over four. Signing the root
alone therefore accepts a weaker claim than it appears to. This engine signs the root
together with event_count and the sequence range. The panel demonstrates the collision
on raw hashes, then shows the signed checkpoint refusing it.
4 · The doctrine, enforced in code
The evidence ladder is in the schema, not in a style guide. A machine-authored record may not claim ALLEGATION, EVIDENCE, FINDING or CONCLUSION, and a machine-authored narrative containing a conclusion word is refused outright — while the blueprint's own permitted phrasings pass. The panel tries both directions.
5 · Verify an exported record
An evidence export is a plain JSON snapshot: events, checkpoints and the public keys needed to check them. Drop one here and it is verified entirely on this page — the file never leaves your machine. Use the button to download the snapshot this page just generated, then re-upload it, edit it in a text editor, and upload it again to watch the layers report the difference.
What a green result does and does not mean
A green result means no alteration, removal, reordering or unregistered signer was detected in the material supplied. It is not a statement that anything recorded is true. Cryptography can demonstrate that recorded bytes have not been altered in defined ways; it cannot prove that an allegation contained inside those bytes is true. Nor is it tamper-proof: a privileged attacker holding every database, signing key, checkpoint and backup could fabricate a replacement history. Separating signing keys from application databases, rotating and auditing keys, protecting checkpoints and keeping independent verification material is what makes that expensive.