inspeximus published claims

114 entries · published 2026-08-31

This is an append-only log of signed statements. It is served as static files so you can check it without trusting whoever published it, and without asking anything of us.

Check it yourself

curl -sO https://dancenitra.github.io/inspeximus/transparency/head.json
curl -sO https://dancenitra.github.io/inspeximus/transparency/log.jsonl
curl -sO https://dancenitra.github.io/inspeximus/transparency/verify.py
python verify.py

verify.py uses the standard library only. It rebuilds the Merkle root from the published leaves and compares it with the published root, then re-derives sth_hash from the head's own fields. A root that does not follow from the leaves is what it catches.

Head

{
  "kind": "scitt-transparency-log",
  "n_tombstones": 0,
  "n_writes": 114,
  "sth_hash": "77c163b5085cf26e2ba096d64e50b2c5e3a609d557e255301fc3e5ddab7015df",
  "store_id": "scitt:4367a1480474b121",
  "tombstones_tip": "",
  "writes_tip": "ef8f3b1bc3b0bc6b9f3b3876bb9e3b1b6e97c10cf701443f5cf8d0e6c84b8d8d"
}

Files

filewhat it is
head.jsonentry count, Merkle root, and the hash over both
keys.jsonthe Ed25519 key that signs receipts, as JSON
keys.cborthe same key as a COSE Key Set (RFC 9052)
log.jsonlone line per entry: index, leaf hash, and the entry record
payloads.jsonthe text of each entry, so you can hash it and match what the log recorded
entries/<n>.cosethe RFC 9942 inclusion receipt for entry n
verify.pythe checker above

What this does not prove

It does not prove any entry is TRUE. A log records what was said, never that it was right.

It does not prove we have shown you the same log we showed somebody else. A static file is easy to serve in two versions, and only an independent WITNESS that remembers a previous head can catch that.

Witnesses

No witness has co-signed this log yet, so nothing here is evidence against equivocation. Running one is the most useful thing an outsider can do.

To become one, run this against this log from a machine we do not control. It remembers the head it last accepted and refuses to sign if the history it already saw has changed:

curl -sSfO https://raw.githubusercontent.com/DanceNitra/inspeximus/main/tools/witness_static_log.py
pip install inspeximus cryptography
python witness_static_log.py --url https://dancenitra.github.io/inspeximus/transparency --state my_state.json --out cosignatures/

To keep it running for nothing, copy this GitHub Actions workflow into a repository of your own. Actions minutes are free on a public repository and the job takes seconds.

Running it commits you to nothing. You are not vouching that any entry here is true. You are recording whether the history we showed you today extends the one we showed you before.

Keep the state file. It is the memory that makes a refusal possible, and a witness without one signs anything.

Registration happens where the signing key is, not over this address. There is no endpoint here that accepts an entry.