Files
proofs/lss/adapter-contract.tex
zeekay 1430256d11 proofs: Lux liquidity protocol adoption + Quasar refs + Pulsar naming
Squashed batch covering:

- lux-adopts-liquidity-protocol.tex: protocol adoption proof artifact
- chronology updates aligning Quasar consensus references to LP-020
- pq-finality-no-bls.tex: Pulsar (Corona-derived lattice threshold)
  naming clarification; per-block / per-epoch / per-era cert language
- quasar-cert-soundness.tex: Pulsar (systems-layer composition with
  key-era lifecycle, resharing, activation cert, rollback) vs Corona
  (signing primitive); math notation and theorems unchanged
- INFRASTRUCTURE-STATUS-2026-04-20.md → INFRASTRUCTURE-STATUS.md
  (drop date stamp from filename)
- LP back-refs and chronology integration

quasar-cert-soundness.tex production-publishable depth (March 3 final):

  - NEW Section 6 (Pulsar Key-Era Lifecycle Lemmas): formal
    definitions for Pulsar share state, GroupKey hash, and Refresh /
    Reshare / Reanchor transitions. Four lifecycle lemmas with full
    proofs:
      Lemma 10 (Generation monotonicity)
      Lemma 11 (KeyEraID stability across Reshare)
      Lemma 12 (GroupKey byte-identity across Refresh and Reshare)
      Lemma 13 (Rollback-lineage forward reconstruction)
    Plus Theorem 14 (Activation-certificate soundness): VerifyActivation
    accepts iff the new committee shares Lagrange-recombine to the
    master secret under the unchanged GroupKey, except with negligible
    probability under MLWE/MSIS.
  - Lagrange-recombination identity written as a labelled display
    equation, citing
    Crypto.Threshold.Reshare.reshare_preserves_public_key in
    lean/Crypto/Threshold/Reshare.lean for the mechanised companion.
  - Bibliography additions: hjky97 (Herzberg--Jarecki--Krawczyk--Yung
    proactive secret sharing), desmedtjajodia97 (redistribution),
    wongwangwing02 (verifiable redistribution), lp073 (Pulsar paper).
  - LP-073 section pointers updated to text-form references that
    survive without LP-073 .aux file.

Naming evolution: throughout this work, "Corona" refers to the
lattice signing primitive (Sign1/Sign2/Combine math); "Pulsar" refers
to the Lux production fork at github.com/luxfi/pulsar that wraps it
with key-era lifecycle for permissionless validator-set rotation.

- proofs/fhe/ (NEW): canonical proof bucket for the Lux FHE
  dual-runtime stack (LP-167 companion):
    correctness.tex             — encrypt → evaluate → decrypt correctness.
    dual-runtime-equivalence.tex — Lux FHE-Go and Lux FHE-C++ produce
                                   byte-equal output on identical inputs
                                   and parameters; KAT closure witness.
    nebula-binding.tex          — FHE result roots bind into Nebula /
                                   Quasar transcripts; reduces a forged
                                   binding to hash collision + Pulsar
                                   SUF-CMA forgery.
    parameter-security.tex      — concrete LWE parameter security under
                                   the Albrecht estimator; ≥128-bit
                                   classical and ≥128-bit quantum for
                                   PN10QP27 / PN11QP54 / PN9QP28_STD128.
  Theorem statements + remarks; no proof bodies duplicated in the
  companion paper (papers/lux-fhe-runtime/) — the paper cites these.
2026-03-03 12:00:00 -08:00

49 lines
2.2 KiB
TeX

%% ============================================================
%% lss/adapter-contract.tex
%% ============================================================
%%
%% Canonical LSS adapter contract — what every LSS-X.go file must
%% guarantee.
%% ============================================================
\subsection*{LSS adapter contract}
\begin{definition}[LSS adapter contract]
\label{def:lss-adapter-contract}
An LSS adapter (e.g.\ $\mathsf{lss\_pulsar.go}$, $\mathsf{lss\_lens.go}$)
MUST satisfy:
\begin{enumerate}[nosep]
\item \textbf{Lifecycle delegation.} The adapter does not implement
share-secret arithmetic; it calls into the kernel
($\mathsf{Pulsar.Reshare}$, $\mathsf{Lens.Reshare}$, etc.) and
wraps the output.
\item \textbf{Generation increment.} On every successful
$\mathsf{DynamicReshare}$, $g \mapsto g+1$ exactly. On
$\mathsf{Rollback}$, $g \mapsto g_{\text{current}}+1$ with
$\mathsf{rb} = g_{\text{current}}$.
\item \textbf{KeyEraID preservation.} $\eta$ is read-only across
$\mathsf{DynamicReshare}$. $\eta$ increments only on a separate
$\mathsf{Reanchor}$ entry point.
\item \textbf{GroupKey identity.} The kernel's $\mathsf{GroupKey}$
pointer flows through unmodified.
\item \textbf{Failure-mode containment.} On any verification failure
(commit mismatch, activation rejection), return an error and
retain the previous state. Do not silently fall back.
\item \textbf{No ECDSA-specific assumptions.} Adapters for non-ECDSA
kernels (Pulsar, Lens) MUST NOT inherit auxiliary secrets
$w$, $q$ from the LSS-CMP path; the underlying kernel handles
nonce blinding internally.
\end{enumerate}
\end{definition}
\begin{remark}[Adapter test contract]
The 10 acceptance tests in $\mathsf{lss\_pulsar\_test.go}$ and
$\mathsf{lss\_lens\_test.go}$ — GroupKey preservation, KeyEraID
preservation, Generation $+1$, RollbackFrom $= 0$ on forward, $t_{\text{old}}
\neq t_{\text{new}}$, disjoint set rotation, valid signature under
unchanged GroupKey, pairwise material regenerated, Rollback restores
prior state, malformed input rejected — collectively enforce
Definition~\ref{def:lss-adapter-contract} for the corresponding
adapter.
\end{remark}