mirror of
https://github.com/lux-apps/papers.git
synced 2026-11-02 11:39:52 +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.
42 lines
2.5 KiB
TeX
42 lines
2.5 KiB
TeX
\documentclass[11pt]{article}
|
|
\usepackage{../shared/luxcover}
|
|
\usepackage{amsmath, amssymb, algpseudocode, graphicx, hyperref, booktabs}
|
|
|
|
\title{Quasar: Quantum-Secure Multi-Engine Consensus with Triple-Proof Quantum Finality}
|
|
\author{
|
|
Lux Research\thanks{Corresponding author: [email protected]}\\
|
|
\textit{Lux Industries, Inc.}\\
|
|
\texttt{[email protected]}
|
|
}
|
|
\date{2022 (Revised 2025)}
|
|
|
|
\usepackage{amsthm}
|
|
\newtheorem{theorem}{Theorem}
|
|
\newtheorem{definition}{Definition}
|
|
\newtheorem{lemma}{Lemma}
|
|
\newtheorem{proposition}{Proposition}
|
|
\begin{document}
|
|
|
|
\luxcoverpage
|
|
|
|
\begin{abstract}
|
|
We present \textbf{Quasar}, a quantum-secure consensus protocol family for Lux Network's Q-Chain, achieving \textbf{10\,ms finality} with GPU-accelerated BLS (100\,ms CPU BLS fallback) through triple-proof validation combining classical BLS signatures with post-quantum Corona threshold signatures. Quasar consists of six layered consensus engines (Photon, Wave, Nova, Nebula, Prism, Quasar) supporting both linear chains and DAGs, integrated with Verkle trees for efficient state proofs and witness validation. The triple-proof mechanism creates a $<$10\,ms attack window physically impossible to exploit even with large-scale quantum computers, while maintaining performance competitive with classical consensus systems. Q-Chain replaces Lux 1.0's P-Chain as the platform management layer, handling validator coordination, staking operations, appchain creation, and network governance with quantum-resistant guarantees. With a 1\,B gas block limit ($\sim$47{,}619 txs/block), a full block clears in $\sim$10\,ms of GPU-BLS opcode-execution time---a \textbf{$\sim$4.8\,M TPS execution-only upper bound (opcode dispatch), not an end-to-end finality figure}; end-to-end finality is bound by signature recovery, settlement conflict-detection, and BLS/PQ finality. This provides defense-in-depth against both classical and quantum adversaries.
|
|
\end{abstract}
|
|
|
|
\input{sections/01-introduction}
|
|
\input{sections/02-system-architecture}
|
|
\input{sections/03-core-innovation-triple-proof-quantum-fin}
|
|
\input{sections/04-consensus-engines}
|
|
\input{sections/05-platform-management}
|
|
\input{sections/06-performance-characteristics}
|
|
\input{sections/07-post-quantum-security}
|
|
\input{sections/08-security-considerations}
|
|
\input{sections/09-network-deployment}
|
|
\input{sections/10-implementation}
|
|
\input{sections/11-future-work}
|
|
\input{sections/13-appendix-a-consensus-parameter-tuning}
|
|
\input{sections/14-appendix-b-cryptographic-specifications}
|
|
\input{sections/99-conclusion}
|
|
|
|
\end{document}
|