saymrwulf/proof-aware-crypto-tooling-agent
1
0
Fork 0
mirror of https://github.com/saymrwulf/proof-aware-crypto-tooling-agent.git synced 2026-09-03 19:53:43 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

site: the one argument opens the page — three sentences, the dilemma and our point between

Browse source 
Operator order: the top value add as three sentences at the very top.
S1 names the two failure modes every alternative has (cost stays with
you, or belief is demanded); S2 places this site at the unique point
between (proof results as cheap as one signature + a handful of hashes,
without turning them into trust); S3 states the guarantee (permanently
recorded, key-bound, assumption-scoped — never believed, only held
accountable). The what-is-here paragraph follows concretely; the old
cost paragraph is absorbed (say it once).
This commit is contained in:
mrwulf 2026-08-17 13:27:05 +02:00
parent 7a6499c452
commit ca2a59f8a7
1 changed files with 17 additions and 12 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

29
provider/src/pacta_provider/webdocs.py
View file

@ -217,19 +217,24 @@ def render_docs(log: TransparencyLog, base_path: str) -> str:
· <a href="https://zkdefi.org/saymrwulf">code</a> · <a href="https://zkdefi.org/saymrwulf">code</a>
· <a href="https://zkdefi.com/">cv</a></p> · <a href="https://zkdefi.com/">cv</a></p>
<h1>LTL — the Lean Transparency Log</h1> <h1>LTL — the Lean Transparency Log</h1>
<p>This site is a <strong>public notary for machine-checked proofs about cryptographic <p><strong>Every known way of consuming formal verification fails on one of two
software</strong>. A proof assistant — <a href="https://lean-lang.org">Lean&nbsp;4</a>, a program sides: either the cost stays with you (re-running a theorem prover), or the cost
that checks mathematical proofs mechanically — has verified precise statements about the code disappears because you are asked to believe a label. This site holds the point in
that <em>checks signatures</em>: in four widely deployed <strong>Ed25519</strong> libraries, in an between — it makes machine-checked proof results as cheap to check as one
implementation of <strong>SLH-DSA</strong> (FIPS&nbsp;205, the hash-based post-quantum signature signature and a handful of hashes, without turning them into trust. Every claim
standard), and in <strong>the Merkle-tree machinery of this log itself</strong>. Every completed the operator ever makes is recorded here permanently, bound to his key, and
proof check is recorded here as a signed, numbered entry that can never be altered or removed — scoped to its exact assumptions: he can never be believed, only held
{len(entries)} entries so far, drawn live further down this page.</p> accountable.</strong></p>
<p>Re-checking such proofs yourself takes a toolchain and real compute time. This log gives you <p>Concretely: a proof assistant — <a href="https://lean-lang.org">Lean&nbsp;4</a>, a
cheaper positions to stand on: in milliseconds you can verify that the operator is permanently program that checks mathematical proofs mechanically — has verified precise
bound to every claim he ever made — and you can escalate, step by step, up to redoing statements about the code that <em>checks signatures</em>: in four widely deployed
everything yourself. The ladder below lists every position, cheapest first.</p> <strong>Ed25519</strong> libraries, in an implementation of <strong>SLH-DSA</strong>
(FIPS&nbsp;205, the hash-based post-quantum signature standard), and in <strong>the
Merkle-tree machinery of this log itself</strong>. Each completed proof check is one
signed, numbered entry that can never be altered or removed — {len(entries)} entries
so far, drawn live further down this page. How much of our work you re-verify is
your choice, from milliseconds to everything:</p>
<h2>Choose where you stand — the trust ladder</h2> <h2>Choose where you stand — the trust ladder</h2>