Files
papers/lux-warp-v2/lux-warp-v2.tex
zeekay ced35b03ed papers: Mar-3 freeze deliverables for hybrid PQ consensus stack
Quasar Horizon (consensus composition over Pulsar / ML-DSA / BLS lanes
under Prism + LSS lifecycle), Warp 2.0 (Pulse-backed cross-chain envelope
with forward-only v1->v2 migration and lattigo ReadUint64Slice DoS fix),
benchmark report (microbench, reshare, activation, Warp 2.0 verify, Prism
composition, GPU headroom, cross-WAN latency), and NIST IR 8214C-style
submission package (spec, parameter sets, domain separation, serialization,
reference-impl pointers, evaluation report, security analysis, side-channel
considerations).

All four deliverables compile cleanly via pdflatex+bibtex and reference
the canonical proof bucket files at proofs/{definitions,pulsar,lss,quasar}.
No duplication of proof bodies; cite by file path.
2026-03-03 12:00:00 -08:00

78 lines
3.6 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{listings}
\usepackage{xcolor}
\usepackage{tikz}
\usepackage{float}
\usepackage{enumitem}
\usepackage{array}
\usepackage{multirow}
\usepackage{tabularx}
\input{../shared/lstlang}
\usetikzlibrary{arrows.meta,positioning,shapes.geometric,fit,calc}
\hypersetup{colorlinks=true,linkcolor=black,citecolor=blue,urlcolor=blue}
\lstset{
basicstyle=\ttfamily\scriptsize,
breaklines=true,
frame=single,
numbers=left,
numberstyle=\tiny\color{gray},
keywordstyle=\color{blue!70!black}\bfseries,
commentstyle=\color{green!50!black}\itshape,
stringstyle=\color{red!60!black},
showstringspaces=false,
}
\newtheorem{theorem}{Theorem}
\newtheorem{lemma}[theorem]{Lemma}
\newtheorem{definition}{Definition}
\newtheorem{proposition}[theorem]{Proposition}
\newtheorem{remark}{Remark}
\title{Warp 2.0: Pulse-Backed Cross-Chain Source Finality}
\author{
Zach Kelling\thanks{Corresponding author: [email protected]}\\
\textit{Lux Industries, Inc.}\\
\texttt{[email protected]}
}
\date{2026-03-03 \quad\textit{Subtitle: An envelope evolution carrying source-chain Horizon finality across chain boundaries via Pulsar Pulses.}}
\begin{document}
\luxcoverpage
\begin{abstract}
\noindent 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.
\textbf{This paper.} Warp 2.0 is the cross-chain envelope that carries source-chain Horizon finality across chain boundaries. Warp 1.x \cite{lp075} signs cross-chain messages with a BLS aggregate over the source chain's validator-key registry; that classical-only design gives a destination chain no PQ guarantee about the source's state. Warp 2.0 adds a Pulsar Pulse over a canonical transcript binding the source chain's $\mathsf{NebulaRoot}$, $\mathsf{KeyEraID}$, and $\mathsf{Generation}$. The destination verifier runs Prism over the source's transcript using the source-chain key registry. Beam, ML-DSA, and Pulse all lift their soundness arguments from the consensus side (Quasar Horizon \cite{luxquasarhorizon,lp020}) to the cross-chain side via transcript binding, with one explicit theorem (Warp 2.0 envelope unforgeability, \texttt{proofs/quasar/warp-pq-soundness.tex}) covering the cross-chain case. We document the wire format, the v1 $\to$ v2 migration discipline (forward-only; v1 verifiers reject the leading \texttt{0x02} byte), the L2 transitive inheritance, and the constant-time fuzz harness that surfaced one vulnerability (a lattigo $\mathsf{ReadUint64Slice}$ DoS) which is fixed in production. Warp Private (FHE-encrypted payload, optionally Pulse-signed) is orthogonal and discussed only briefly here.
\end{abstract}
\tableofcontents
\newpage
\input{sections/01-introduction}
\input{sections/02-warp-evolution}
\input{sections/03-envelope-format}
\input{sections/04-cross-chain-binding}
\input{sections/05-soundness}
\input{sections/06-fuzz-discovered-vulnerability}
\input{sections/07-implementation}
\input{sections/08-related-work}
\bibliographystyle{plain}
\bibliography{references}
\end{document}