A transparency log gives a recorded entry a place in a history that can be checked using cryptographic evidence. It complements a record’s own signature. It does not make an untrue statement true, and it does not automatically capture actions from systems that were never connected.
Start with the entry
An issuing workflow can submit a supported record reference or fingerprint to the log. Entries are organized into a tree whose root summarizes a particular state. A signed checkpoint connects that summary to the log’s signing identity. A verifier needs the relevant key to check the checkpoint signature.
An inclusion proof supplies the information needed to check that a particular entry belongs to the tree represented by a checkpoint. It establishes inclusion in that recorded state, rather than the truth of the entry’s business claims.
Three questions for a reviewer
- What record am I checking? Match the entry to the document or statement you received.
- Which checkpoint supports it? Inspect the checkpoint, its signature, and the verification key used.
- What does the result establish? Distinguish a successful inclusion check from current revocation status and from the trustworthiness of the issuer.
Consistency between recorded states is another question. A single inclusion proof should not be described as a complete audit of all log operations or all actions performed by an organization.
Understand incomplete historical evidence
Some historical Truthlocks checkpoints from the earlier hosting environment lack the recovered public-key material needed to verify their signatures. Those records are preserved, but preservation is not the same as successful verification. Check the evidence available for the specific checkpoint instead of assuming that a successful check of a newer record also validates older history.
The transparency explorer is the place to inspect available records and checkpoints. Keep confidential business documents separate from information intentionally exposed through public transparency tooling.
Plan for future verification
When exporting supported evidence, retain the record, signatures, verification keys, and applicable proof material together. Use the proof-bundle guide to understand what a package contains and which checks still require a current online status lookup. Teams issuing official documents should define who manages keys and how recipients obtain updated verification information.