Record an entry
Supported issuing workflows submit an entry to the log.
Loading...
Platform
Use a verifiable log to check that a recorded entry is included in a signed checkpoint.
Records & verification
A transparency log adds another layer of evidence. It organizes record fingerprints into a structure that supports inclusion checks and makes inconsistent history detectable.
Public transparency data and private business records are different. Review what an integration exposes before publishing information.
Platform
Supported issuing workflows submit an entry to the log.
Entries are grouped into a signed summary of the log’s state.
Use the explorer or proof tools to examine the available evidence.
Details and limitations
Start with a record and its available log reference. A transparency log groups entries into a structure that can be checked against a signed checkpoint. A leaf index identifies a position; it is not, on its own, proof that the record was included.
Where available, an inclusion proof connects the entry to a particular checkpoint. Check the checkpoint signature and the proof against the expected entry. The result describes inclusion in that checkpoint; it does not independently validate the contents of the recorded claim.
A public explorer helps recipients inspect published evidence. Do not confuse a public signing-key identifier with a private credential, and never publish private signing material. If inclusion evidence is missing, show that condition separately from the record's signature result.
Verify a complete proof and then change the test leaf or proof path. Check that the verifier rejects the changed evidence. Also test an unreachable log service so your application can explain the difference between an invalid proof and an unavailable fresh check.