Tamper evidence
Inspect the cryptographic trail behind Sealright records. Values below are read from the Sealright database each time this page loads.
Verification checks
These checks recompute stored hashes and compare linked records. An “OK” result describes the current database state; external proof requires checking an anchor with its independent provider.
How the record is protected
1. Content commitment. Each stored idea version or reveal is hashed into a ledger entry. The content check recomputes that commitment against stored text.
2. Linked entries. Each entry stores its payload hash, previous entry hash and its own hash. The chain check recomputes the entry hash and follows the links.
3. Closed batches. Entries in a closed batch produce a Merkle root. A checkpoint binds that root, entry range, chain head and previous checkpoint.
4. External anchors. An anchor records where a checkpoint was published. The database check confirms an anchor row exists; it does not confirm that the external reference is reachable or matches the published value.
Append-only triggers guard ordinary updates and deletes. Privileged database access could bypass those guards; externally published checkpoints provide the independent comparison when verified separately. Entries awaiting a batch have no batch checkpoint yet.