Files
papers/lp-020-quasar-consensus/lp-020-quasar-consensus.tex
zooqueen 12912be1b5 papers: reconcile Corona to Module-LWE (Ringtail-derived, rank-7), not Ring-LWE rank-1
- canonical lux-corona-pq paper: rank-7 Module-LWE (A in R_q^{8x7}, q=48-bit), Module-SIS
- scrub residual Corona Ring-LWE/R-LWE labels across ethos-of-lux, pqsafe-il5,
  lux-whitepaper, lux-quasar-composition, lp-020; Corona<->Pulsar = parameter regime,
  both Module-LWE (not rank-1-vs-rank-k)
- LLM.md: drop stale 'Corona as rank-1' wobble note; align to code/Ringtail params
- rebuild affected PDFs
2026-06-20 01:59:25 -07:00

103 lines
4.5 KiB
TeX

\documentclass[11pt,a4paper]{article}
\usepackage{../shared/luxcover}
\usepackage[utf8]{inputenc}
\usepackage[T1]{fontenc}
\usepackage{amsmath,amssymb,amsfonts,amsthm}
\usepackage{graphicx}
\usepackage{hyperref}
\usepackage{booktabs}
\usepackage{algorithm}
\usepackage{algpseudocode}
\usepackage{enumitem}
\usepackage{xcolor}
\hypersetup{colorlinks=true,linkcolor=black,citecolor=blue,urlcolor=blue}
\newtheorem{theorem}{Theorem}[section]
\newtheorem{lemma}[theorem]{Lemma}
\newtheorem{corollary}[theorem]{Corollary}
\newtheorem{proposition}[theorem]{Proposition}
\newtheorem{definition}{Definition}[section]
\newtheorem{remark}{Remark}[section]
\title{LP-020: Quasar 3.0 Consensus\\[4pt]
\large Three-Lane Post-Quantum Certificates\\
over the P/Q/Z/A/B/M/F Chain Pipeline}
\author{
Zach Kelling\thanks{Corresponding author: [email protected]}\\
\textit{Lux Industries, Inc.}\\
\texttt{[email protected]}
}
\date{Spec freeze: 15 December 2025\quad|\quad
Final review: 20 December 2025\quad|\quad
Activation: 25 December 2025}
\begin{document}
\luxcoverpage
\begin{abstract}
\noindent 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.
We present Quasar 3.0, the post-quantum Byzantine fault tolerant consensus
protocol activated on the Lux primary network on 25 December 2025. Quasar 3.0
finalizes a block by producing a single \emph{QuasarCert} that aggregates
three independent verification \emph{lanes}: a BLS12-381 aggregate signature
(classical fast path, discrete logarithm), a Corona two-round Module-LWE
threshold signature (Q-Chain ceremony root), and a Z-Chain Groth16 proof that
rolls up $N$ ML-DSA-65 validator signatures into a single 192-byte SNARK plus
a 32-byte public-inputs hash. The third lane is \emph{not} a raw per-validator
ML-DSA list; it is a Z-Chain proof artifact, allowing the per-block on-chain
cost of post-quantum identity binding to drop from $N \times 3{,}309$ bytes
to $192 + 32$ bytes regardless of validator count. Every QuasarCert is bound
to a \emph{certificate subject} that hashes the chain id, epoch, round, mode,
and the seven chain-specific roots
($P_\text{val} \mathbin\| Q_\text{cer} \mathbin\| Z_\text{vk} \mathbin\|
A_\text{att} \mathbin\| B_\text{br} \mathbin\| M_\text{mpc} \mathbin\|
F_\text{fhe}$) together with the parent block hash, parent state root,
parent execution root, gas limit, and base fee, making cross-epoch and
cross-chain replay structurally impossible. The three lanes are verified
independently by the QuasarGPU substrate (LP-132): BLS aggregate verify
(${\sim}875\,\mu$s for $n{=}100$ on CPU), Corona batch verify ($O(1)$
amortized after DKG), and a single Groth16 pairing check (200--500\,$\mu$s
GPU batched). On a 21-validator mainnet board, full three-lane GPU
verification runs in 0.5--1.5\,ms; the network targets a 500\,ms block time
and sustained $\geq$100K TPS per chain. An adversary must simultaneously
break the discrete logarithm on BLS12-381, Module-LWE for Corona, and
Module-LWE/MSIS for ML-DSA to forge a QuasarCert; breaking any one or any
two leaves the remaining lane intact.
\end{abstract}
\tableofcontents
\newpage
%% ============================================================================
\input{sections/01-introduction}
\input{sections/02-system-model}
\input{sections/03-protocol}
\input{sections/04-cryptographic-layers}
\input{sections/05-chain-separation-for-threshold-cryptogra}
\input{sections/06-quasarcert-formal-definition}
\input{sections/07-security-analysis}
\input{sections/08-performance}
\input{sections/09-implementation}
\input{sections/10-formal-verification}
\input{sections/11-related-work}
\input{sections/13-why-not-threshold-ml-dsa-or-threshold-fa}
\input{sections/14-activation-roadmap}
\input{sections/15-future-work}
\input{sections/99-conclusion}
\appendix
\section*{Reproducibility}
\textbf{Source code.} \texttt{github.com/luxfi/consensus} (commit \texttt{TBD}); wire protocol at \texttt{github.com/luxfi/zap}; Corona at \texttt{github.com/luxfi/corona}.\\
\textbf{Build.} \texttt{go build ./...} and \texttt{go test ./...} at the freeze tag \texttt{v0.1.0-rc1-pq-consensus-freeze}.\\
\textbf{Hardware tested.} TBD (commodity x86\_64 Linux validators).\\
\textbf{Standards referenced.} FIPS 204 (ML-DSA-65), FIPS 206 (draft, threshold context), BLS12-381 (IETF draft), NIST IR 8214C (MPTC).\\
\textbf{Contact.} [email protected].
\end{document}