document repository — transparency log identity

This page publishes the identity of the append-only log that records every operation in this repository. A client pins the set of keys below; it accepts a new one only through a transition statement signed by a key it already trusts.

Current key

logId
74648e9a4e46829a051482d2a1c1f77befd3172e96dc0ef8cde7d15bf966566d
logSigPub_b64
MMc03asXHRNjhq7rkUZuzGmBNb2yFAn0muZlmC5WjvE=
alg
ed25519
custody
kms-hsm
signing from tree size
1

Latest signed tree head

No head has been published yet.

Key history

logIdpublic keytree sizesintroduced by
74648e9a4e46829a051482d2a1c1f77befd3172e96dc0ef8cde7d15bf966566dMMc03asXHRNjhq7rkUZuzGmBNb2yFAn0muZlmC5WjvE=1 – currentfirst key

Verifier releases

No verifier release has been published yet. When one is, its version, file name and SHA-256 appear here, and every evidence package carries the same binaries, their hashes, the verifier source for that exact version and the rebuild recipe.

Endpoints

keys
https://api.docs.itix.eu/v1/log/keys
latest head
https://api.docs.itix.eu/v1/log/sth
inclusion proof
https://api.docs.itix.eu/v1/log/proof/inclusion?seq=
consistency proof
https://api.docs.itix.eu/v1/log/proof/consistency?first=
gossip
https://api.docs.itix.eu/v1/log/sth/observed
this page as JSON
https://docs.itix.eu/.well-known/docrepo-log.json

Two validly-signed heads at one tree size with different roots are proof of misbehaviour, not suspicion. Report what you were served to the gossip endpoint; it is unauthenticated by design.