mirror of
https://github.com/lux-apps/papers.git
synced 2026-10-30 18:15:21 +00:00
zeekay
f4ee7a0525
Bylines, paper authorship, correspondence addresses and the founder blurb under each post named an individual. They name the organisation that published the work instead: the brand on posts and pages, the research byline on papers, and research@ in place of a personal address. Both are what these repositories already used elsewhere — nothing new was coined. Co-authors are untouched. Where a paper named someone else alongside, they stay named; only the one byline changed. Bibliography entries, running heads, PDF metadata and affiliations move with it, so a citation still resolves to whoever the cited paper names. Sample and fixture data uses the placeholder name these tests already use elsewhere, so no assertion changed meaning.
% Lux NIST MPTC Submission Package — README
% NIST IR 8214C-style submission for the Lux multi-party threshold cryptography stack.
% Per repository policy: papers/, proofs/, audits/ are LaTeX-only — no Markdown.
\documentclass[11pt]{article}
\usepackage[margin=1in]{geometry}
\usepackage{hyperref}
\usepackage{enumitem}
\usepackage{longtable}
\usepackage{booktabs}
\usepackage{../shared/luxcover}
\title{Lux NIST MPTC Submission Package\\\large NIST IR 8214C style}
\author{Lux Network}
\date{}
\begin{document}
\luxcoverpage
\maketitle
\section*{Thesis}
\begin{quote}
Lux is not merely adding post-quantum signatures to a chain; it defines a hybrid
finality architecture for DAG-native consensus, with protocol-agnostic threshold
lifecycle, post-quantum threshold sealing, and cross-chain propagation of Horizon
finality.
\end{quote}
\section*{Long-form abstract}
We present Lux, a hybrid post-quantum consensus architecture for DAG-native
chains. Lux separates fast operational finality from durable post-quantum
finality. Validators emit Photons over a Nebula DAG substrate; classical BLS
aggregates form Beams for low-latency confirmation, while ML-DSA attestations
and Pulsar lattice-threshold Pulses provide post-quantum finality over Nebula
roots. Prism binds all certificate lanes to the same transcript, and Quasar
reaches Horizon finality when the bound lanes verify.
This package is the NIST IR 8214C-style submission for the Lux multi-party
threshold cryptography stack. It covers the Pulsar lattice threshold scheme
(post-quantum), the Lens curve threshold scheme (FROST/RFC 9591 family,
classical), the LSS lifecycle framework (protocol-agnostic dynamic resharing),
and their composition into Quasar Horizon (consensus-side) and Warp 2.0
(cross-chain). Mathematical specifications, parameter sets, domain-separation
registry, serialization spec, reference-implementation pointers, experimental
evaluation, security analysis, and side-channel considerations are organized
per NIST IR 8214C.
\section*{Map to LP-105}
The Lux Finality Stack vocabulary (LP-105) names the components covered by
this submission:
\begin{longtable}{p{0.32\textwidth}p{0.22\textwidth}p{0.36\textwidth}}
\toprule
\textbf{Component} & \textbf{LP-105 name} & \textbf{NIST submission section} \\
\midrule
Lattice (Module-LWE) two-round threshold signature & Pulsar kernel & spec/technical-specification \S Pulsar \\
Curve (FROST family) threshold signature & Lens kernel & spec/technical-specification \S Lens \\
Protocol-agnostic dynamic-resharing lifecycle & LSS & spec/technical-specification \S LSS \\
Hybrid finality boundary, transcript-bound & Quasar Horizon & spec/technical-specification \S Quasar Horizon \\
Cross-chain envelope carrying Horizon finality & Warp 2.0 & spec/technical-specification \S Warp 2.0 \\
\bottomrule
\end{longtable}
Pulsar wraps the Pulsar two-round MAC-authenticated lattice threshold
primitive; Lens wraps the FROST 2-round Schnorr threshold primitive. LSS
provides one lifecycle for both. Quasar Horizon composes Beam (BLS aggregate)
+ ML-DSA cert set (FIPS 204) + Pulse (Pulsar threshold) into a Prism-bound
finality artifact. Warp 2.0 carries that finality across chain boundaries.
\section*{Reference list}
The reference implementations cited in the submission are at the canonical
Go repos under \verb|github.com/luxfi/|:
\begin{itemize}[leftmargin=*]
\item \verb|github.com/luxfi/pulsar| --- Pulsar kernel + key-era lifecycle
(math kernel forked byte-equal from Pulsar; lifecycle is novel)
\item \verb|github.com/luxfi/lens| --- Lens kernel
(FROST 2-round Schnorr over Ed25519 / secp256k1 / Ristretto255)
\item \verb|github.com/luxfi/threshold| --- LSS lifecycle framework
+ per-kernel adapters (\verb|lss_pulsar.go|, \verb|lss_lens.go|, \verb|lss_cmp.go|)
\item \verb|github.com/luxfi/consensus| --- Quasar engine + Horizon composition
\item \verb|github.com/luxfi/warp| --- Warp 1.x + Warp 2.0 cross-chain envelopes
\end{itemize}
All five repos share the freeze tag \verb|v0.1.0-rc1-pq-consensus-freeze|
(Mar-3, 2026).
\section*{Submission contents}
\begin{verbatim}
lux-nist-mptc-submission/
\xe2\x94\x9c\xe2\x94\x80\xe2\x94\x80 README.tex (this file)
\xe2\x94\x9c\xe2\x94\x80\xe2\x94\x80 known-limitations.tex
\xe2\x94\x9c\xe2\x94\x80\xe2\x94\x80 spec/
\xe2\x94\x82 \xe2\x94\x9c\xe2\x94\x80\xe2\x94\x80 technical-specification.tex
\xe2\x94\x82 \xe2\x94\x9c\xe2\x94\x80\xe2\x94\x80 parameter-sets.tex
\xe2\x94\x82 \xe2\x94\x9c\xe2\x94\x80\xe2\x94\x80 domain-separation-registry.tex
\xe2\x94\x82 \xe2\x94\x94\xe2\x94\x80\xe2\x94\x80 serialization-spec.tex
\xe2\x94\x9c\xe2\x94\x80\xe2\x94\x80 reference-impl/
\xe2\x94\x82 \xe2\x94\x94\xe2\x94\x80\xe2\x94\x80 impl-pointers.tex
\xe2\x94\x94\xe2\x94\x80\xe2\x94\x80 evaluation-report/
\xe2\x94\x9c\xe2\x94\x80\xe2\x94\x80 experimental-evaluation.tex
\xe2\x94\x9c\xe2\x94\x80\xe2\x94\x80 security-analysis.tex
\xe2\x94\x94\xe2\x94\x80\xe2\x94\x80 side-channel-considerations.tex
\end{verbatim}
\section*{NIST IR 8214C alignment}
NIST IR 8214C specifies the reference framework for multi-party threshold
cryptography submissions. This package follows that framework with the
following Lux-specific extensions:
\begin{itemize}[leftmargin=*]
\item \textbf{Hybrid composition.} NIST IR 8214C focuses on threshold
primitives in isolation. The Quasar Horizon composition
(Beam + ML-DSA + Pulse) is treated as a downstream-spec artifact that
uses the threshold primitive (Pulse) as one lane of a multi-lane
finality cert. The composition theorem is documented in
\verb|spec/technical-specification.tex| \S Quasar Horizon with reference
to the proof bucket.
\item \textbf{Cross-chain transport.} Warp 2.0 (cross-chain envelope
carrying Pulse) is documented as a secondary deployment target
alongside the consensus-side primary use.
\item \textbf{Honest classification of proof wrappers.} The Z-Chain
Groth16 wrapper around the ML-DSA cert set is explicitly classified
as classical (pairing-based, broken under Shor); the PQ root of trust
is ML-DSA + Pulse. This is consistent with the LP-105 proof-lane
classification policy.
\end{itemize}
\section*{How to read this package}
\begin{enumerate}
\item Start with \verb|spec/technical-specification.tex| for the high-level
mathematical spec.
\item \verb|spec/parameter-sets.tex| lists concrete parameters and security
bits.
\item \verb|spec/domain-separation-registry.tex| specifies every
personalization tag.
\item \verb|spec/serialization-spec.tex| specifies the canonical wire
formats.
\item \verb|reference-impl/impl-pointers.tex| points at the Go canonical
commits.
\item \verb|evaluation-report/experimental-evaluation.tex| cites the
benchmark report.
\item \verb|evaluation-report/security-analysis.tex| cites the proof
bucket.
\item \verb|evaluation-report/side-channel-considerations.tex| cites the
constant-time review.
\item \verb|known-limitations.tex| is honest about what we have and
have not done.
\end{enumerate}
\section*{License}
The reference implementations are open source under the licenses listed
in each repo. The specification documents are licensed under the same
terms as the Lux Improvement Proposals (LP-001 onward).
\section*{Contact}
\verb|[email protected]| for cryptographic questions;
\verb|[email protected]| for implementation questions.
\section*{References (key)}
\begin{itemize}[leftmargin=*]
\item NIST IR 8214C: Multi-Party Threshold Cryptography Schemes. NIST, 2024.
\item LP-105: The Lux Finality Stack --- Public Vocabulary and Internal Names.
\item LP-073: Pulsar --- Dynamic Lattice Threshold Signatures.
\item LP-077: Linear Shamir's Secret Sharing.
\item LP-103: Lens --- Curve-Based Threshold Signatures.
\item LP-020: Quasar Consensus 3.0.
\item LP-070: FIPS 204 ML-DSA Signatures.
\item LP-075: BLS Aggregate Signatures.
\item Pulsar: A Lattice-Based Threshold Signature for Post-Quantum
Consensus. IEEE S\&P 2025.
\item RFC 9591: The FROST Protocol. RFC Editor, 2024.
\item FIPS 204: Module-Lattice-Based Digital Signature Standard. NIST, 2024.
\end{itemize}
\appendix
\section*{Reproducibility}
\textbf{Source code.} \texttt{github.com/luxfi/pulsar}, \texttt{github.com/luxfi/lens}, \texttt{github.com/luxfi/threshold}, \texttt{github.com/luxfi/consensus}, \texttt{github.com/luxfi/warp} (all at freeze tag \texttt{v0.1.0-rc1-pq-consensus-freeze}, Mar-3 2026).\\
\textbf{Build.} \texttt{go build ./...} and \texttt{go test ./...} in each repo at the freeze tag.\\
\textbf{Hardware tested.} TBD (commodity x86\_64 Linux; benchmark report cites concrete machine specs).\\
\textbf{Standards referenced.} NIST IR 8214C (MPTC), FIPS 203 (ML-KEM), FIPS 204 (ML-DSA), FIPS 205 (SLH-DSA), RFC 9591 (FROST).\\
\textbf{Contact.} [email protected].
\end{document}