lean-transparency-log/README.md
mrwulf 2d77a2ba2f Genesis publication: 8 leaves, 4 attested libraries, dogfood-signed head
The public face of the Lean Transparency Log: every leaf (including the
first run's honest audit-failure attestations), the full STH history
(witness channel), per-component receipts, the provider public key, and
a standalone stdlib-only verify.py.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-06 16:02:23 +02:00

1.8 KiB

Lean Transparency Log — published mirror

This repository is the git-published face of a transparency log of formal-verification attestations: signed statements that the Lean 4 proofs of specific cryptographic Rust libraries, at specific git commits, re-check with exactly their documented assumptions.

Layout:

Path Content
entries/NNNNNN.json one log leaf per file, append-only (git history mirrors log history)
entries/<component>.attestation.json the newest attestation per library, for convenience
receipts/<component>.receipt.json inclusion proof binding that attestation to the latest signed head
sth-history.jsonl every Signed Tree Head ever issued — the witness channel: all cloners see the same heads
latest-sth.json the current head
provider.ed25519.pub the provider's public key (the sole trust anchor)
verify.py standalone verifier, Python standard library only

Verify everything locally, no installation:

python3 verify.py --all
python3 verify.py --receipt receipts/dalek-ed25519-verified.receipt.json

The online service (same data, live endpoints + customer documentation): https://zkdefi.org/lean-transparency-log

The provider tooling, agent tooling, and course materials: https://github.com/saymrwulf/proof-aware-crypto-tooling-agent

Honesty notes, always in force: attestations cover Rust source at a pinned commit (clone it — the git hash is the content hash — and build it yourself; compilers are declared trusted base). The log deliberately retains early leaves recording a failed audit run: an append-only trust ledger keeps its history. Tree heads are signed by the merkleized, proof-attested Ed25519 library itself, and each signature embeds the provider's own Merkle self-check of that library's leaf.