Files
zooqueen ac61e71667 Reconcile Corona/Pulsar taxonomy: both are Module-LWE
Scrub residual Ring-LWE mislabels of the Corona/Pulsar threshold
signature family per canonical decision-b (source: ringtail/sign/config.go
M=8,N=7, q=0x1000000004A01).

- Corona = Module-LWE (Ringtail-derived parameter set, A in R_q^{8x7}),
  not Ring-LWE / not "Module-LWE at rank 1".
- Pulsar = Module-LWE (ML-DSA-65, FIPS-204 byte-equal).
- Corona+Pulsar differ by parameter regime/codebase, NOT hardness family:
  intra-lattice parameter/implementation diversity, NOT family-disjoint.
- True family-disjoint defense = Magnetar (hash, SLH-DSA) / HQC (codes).

Reframed the false Corona(R-LWE)-vs-Pulsar(M-LWE) family-independence
across lp-219/lp-220/lp-222/lp-223 (P3Q kinds), lux-quasar-composition
(profile hardness table + composition corollary/proof), lux-magnetar-pq,
and the superseded triple-proof/quasar drafts (anonymous lattice
threshold lane = Corona). Legitimate FHE/TFHE Ring-LWE, NTT citations,
and neutral "rank-1" lattice facts left intact. PDFs rebuilt.
2026-06-20 02:26:47 -07:00

73 lines
2.5 KiB
TeX

\documentclass[11pt,a4paper]{article}
\usepackage{../shared/luxcover}
\usepackage[utf8]{inputenc}
\usepackage[T1]{fontenc}
\usepackage{amsmath,amssymb,amsfonts}
\usepackage{graphicx}
\usepackage{hyperref}
\usepackage{booktabs}
\usepackage{enumitem}
\usepackage{xcolor}
\usepackage{siunitx}
\usepackage{listings}
\hypersetup{colorlinks=true,linkcolor=black,citecolor=blue,urlcolor=blue}
\lstset{
basicstyle=\ttfamily\scriptsize,
breaklines=true,
frame=single,
showstringspaces=false,
}
\title{P3Q: Unified-Slot Post-Quantum Verifier\\
Dispatch Framework}
\author{Lux Industries, Inc. \\
\texttt{[email protected]}}
\date{2026-06-03}
\begin{document}
\luxcoverpage
\begin{abstract}
P3Q is the unified-slot post-quantum verifier framework at EVM
precompile slot \texttt{0x012205}: one slot, one ABI, and a
leading \texttt{kind} byte that dispatches into per-kind
threshold-signature verifier cores via the \texttt{P3QVerifier}
Go interface. This paper specifies the framework itself --- the
2026-06-03 architectural decomplection from sibling-slots to a
single slot with kind-byte dispatch, the \texttt{P3QVerifier}
registration interface, and the cross-family composition into
LP-217 cert profile modes --- independently of any one
cryptographic family or any one caller. PQ-secured rollups
(LP-218) are P3Q's primary consumer, but P3Q is its own surface:
any contract --- a bridge light-client, a cross-chain message
verifier, an on-chain custody policy --- calls the same slot for
post-quantum threshold-signature verification. The per-kind
verifiers are specified in
companion LPs: \textbf{LP-223 Pulsar} (rank-$k$ Module-LWE,
FIPS-204 ML-DSA-65 threshold, kind~$0x01$), \textbf{LP-220
Corona} (Module-LWE, two-round Corona threshold, kind~$0x02$),
and \textbf{LP-222 Magnetar} (hash-based, FIPS-205 SLH-DSA
threshold, kind~$0x03$). The framework's reason to exist is
cross-family-maximum security: a single structural break in any
one PQ family must not compromise a PQ-heavy rollup, because the
kinds span two mutually independent families --- lattice
(Module-LWE, shared by Pulsar and Corona at distinct parameter
sets) and hash collision resistance (Magnetar). Future kinds
add a byte to the dispatch table, not a slot to the EVM.
\end{abstract}
\tableofcontents
\newpage
\input{sections/01-introduction}
\input{sections/02-architectural-decision}
\input{sections/06-verifier-interface}
\input{sections/07-composition}
\bibliographystyle{plain}
\bibliography{biblio}
\end{document}