mirror of
https://github.com/lux-apps/papers.git
synced 2026-10-30 18:15:21 +00:00
zooqueen
ed0d9cabdf
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.
6 lines
844 B
TeX
6 lines
844 B
TeX
\section*{Abstract}
|
|
|
|
|
|
We present \textbf{triple-proof quantum finality}, a consensus mechanism for the Lux Network that achieves simultaneous classical speed, post-quantum security, and validator privacy in 248 bytes per epoch. The mechanism combines three independent cryptographic proofs: (1) BLS12-381 aggregate signatures for sub-millisecond classical consensus, (2) STARK-aggregated ML-DSA-65 (FIPS 204) signatures for post-quantum identity binding, and (3) Corona lattice-based threshold signatures for anonymous validator participation. No single cryptographic break compromises the system. At 1ms block times, the mechanism requires approximately 1 TB/year of storage for block headers and epoch proofs combined. We provide benchmarks showing ${\sim}2$--$5$\,ms CPU QuasarCert verification on commodity hardware~\cite{lux-benchmarks}.
|
|
|