diff --git a/paper/ltl.pdf b/paper/ltl.pdf index a5e6810..7a1eddd 100644 Binary files a/paper/ltl.pdf and b/paper/ltl.pdf differ diff --git a/paper/ltl.tex b/paper/ltl.tex index 0f776ab..113a72c 100755 --- a/paper/ltl.tex +++ b/paper/ltl.tex @@ -47,7 +47,7 @@ showstringspaces=false,breaklines=true,xleftmargin=.5em,xrightmargin=.5em} \large A Transparency Model and the Lean Transparency Log} \author{Olaf Horvath\\ \small Olaf.Horvath@zkdefi.org \quad ORCID 0009-0004-8008-5805} -\date{July 2026 \quad (v0.4)} +\date{July 2026 \quad (v0.5)} \begin{document} \maketitle @@ -71,9 +71,10 @@ are compared. We instantiate the model as the Lean Transparency Log (LTL), using Lean~4 replay attestations and an RFC~9162 Merkle tree. We give explicit -collision-extracting arguments for inclusion and consistency, formalize the -consumer pinning and policy boundaries, and evaluate a live deployment over four -production Ed25519 codebases. The public log contains thirteen leaves; its thirteenth +collision-extracting arguments for inclusion and consistency, lift them to +scheme-level accountability games with an explicit composition theorem, +formalize the consumer pinning and policy boundaries, and evaluate a live +deployment over four production Ed25519 codebases. The public log contains thirteen leaves; its thirteenth leaf attests a Lean mechanization of the accumulator's own security arguments (222 inventoried environment constants, 61 human-reviewed assumption cones, and a single uninterpreted SHA-256 axiom). The mechanization effort also exposed, via differential testing, a nontrivial @@ -153,7 +154,9 @@ what a lightweight consumer learns without executing Lean. Using the RFC~9162 tree unchanged, we define signed views, inclusion receipts, local history pinning, and transferable same-size fork evidence. We give explicit collision-extracting soundness arguments specialized to the consumer -algorithms. +algorithms, and lift them to scheme level: concrete games for position +binding, history binding, and fork evidence, discharged by explicit +reductions (\S\ref{sec:games}). \item \textbf{Boundary-conformance policy.} Each leaf records the exact axiom names reported by Lean. Consumers compare those observations with their own policy; operator labels can veto but cannot @@ -307,6 +310,8 @@ property. It says when conflicting claims become attributable; it does not cryptographically prove that the replay observation was honestly produced. Throughout, ``accountability'' means signed-view and history accountability; observation validity remains external to the mechanism. +Section~\ref{sec:games} states clauses (i)--(iv) as games and explicit +reductions and proves the construction satisfies them. \begin{figure}[t] \centering @@ -374,6 +379,8 @@ enough for a third party to replay. \subsection{Consumer goals} +Each goal below is formalized as a game in Section~\ref{sec:games}. + \begin{description}[leftmargin=1.5em,itemsep=5pt] \item[G1: Position-bound membership.] If a consumer accepts leaf $d$ at index $m$ against signed head $(n,r)$, then $d$ occupies position $m$ in a leaf list @@ -592,6 +599,177 @@ predicate. Consequently the public attestation says exactly this: the model is proved; deployment correspondence is finite-tested and relies on an unmechanized authentic-size/root invariant. +\subsection{Scheme-level games and a composition theorem}\label{sec:games} + +The theorems above bind single artifacts to a reference leaf list. This +subsection lifts them to the scheme: precise experiments for the accountability +clauses of Definition~2, and a theorem that the construction satisfies them. +Two modeling choices deserve emphasis. First, the replay operator \emph{is} the +adversary and legitimately holds the signing key, so the position-binding and +history games contain no secrets and no oracles; any adaptive interaction can +be replayed into a single output, and the games are therefore non-interactive +--- mirroring the deployment, in which receipt verification itself is +non-interactive. Signatures constrain a different party: the frame-resistance +game, in which a third party attempts to fabricate equivocation evidence +against a key holder who never equivocated. Second, SHA-256 is a fixed, +unkeyed function, so ``collision resistance'' cannot be a probability +statement over a key space; following the human-ignorance +treatment~\cite{rogaway}, every hash statement below is an \emph{explicit +reduction} --- a named algorithm transforming a winning transcript into a +concrete collision --- which is the scheme-level continuation of the corpus's +named-extractor discipline. + +\paragraph{Accepted-artifact syntax.} +Fix the algorithms of Section~\ref{sec:construction}. A head $h=(n,r;\sigma)$ +carries the canonical signed payload of \S4.2; $\mathsf{Vf}_{pk}(h)=1$ iff its +signature verifies. An \emph{opening} of leaf $d$ at index $m$ under $(n,r)$ +is a path $P$ with $m (The full walk-through is lecture 11 in the

The paper

Accountable Distribution of Machine-Checked Correctness Evidence: A Transparency Model and the Lean Transparency Log -(PDF, 17 pages, v0.4 — revised after two independent round-12 reviews) — the trust -decomposition (expensive verification produces an observation; transparency makes the -observation accountable; consumer-local policy decides acceptance), collision-extracting -soundness for inclusion and consistency, the policy boundary where operator labels can veto -but never grant acceptance, the live thirteen-leaf deployment whose entry 13 attests the -accumulator's own mechanized model, and the measured model/deployment divergence (3,867 -lied-size cases, every one accepted only by the deployed verifier) reported as a result -rather than hidden. +(PDF, 19 pages, v0.5) — the trust decomposition (expensive verification produces an +observation; transparency makes the observation accountable; consumer-local policy decides +acceptance), collision-extracting soundness for inclusion and consistency, scheme-level +accountability GAMES with an explicit composition theorem (position binding, history +binding, fork evidence — all discharged by named reductions), the policy boundary where +operator labels can veto but never grant acceptance, the live thirteen-leaf deployment +whose entry 13 attests the accumulator's own mechanized model, and the measured +model/deployment divergence (3,867 lied-size cases, every one accepted only by the +deployed verifier) reported as a result rather than hidden. Previous versions: v0.2 (19 pages, the system report) · v0.1 (4 pages).