Files
zeekay f4ee7a0525 Publish under the org, not a person
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.
2026-09-01 08:58:10 -07:00

91 lines
3.9 KiB
TeX

\documentclass[11pt,a4paper]{article}
\usepackage{../shared/luxcover}
\usepackage[utf8]{inputenc}
\usepackage[T1]{fontenc}
\usepackage{amsmath,amssymb,amsthm}
\usepackage{algorithm,algorithmic}
\usepackage{graphicx}
\usepackage{tikz}
\usepackage{pgfplots}
\usepackage{hyperref}
\usepackage{listings}
\input{../shared/lstlang}
\usepackage{color}
\usepackage{booktabs}
\usepackage{multirow}
\usepackage{subcaption}
\usetikzlibrary{positioning,shapes,arrows}
\pgfplotsset{compat=1.17}
% Theorem environments
\newtheorem{theorem}{Theorem}
\newtheorem{lemma}[theorem]{Lemma}
\newtheorem{proposition}[theorem]{Proposition}
\newtheorem{corollary}[theorem]{Corollary}
\newtheorem{definition}[theorem]{Definition}
% Code listing style
\definecolor{codegray}{rgb}{0.5,0.5,0.5}
\definecolor{codegreen}{rgb}{0,0.6,0}
\definecolor{codepurple}{rgb}{0.58,0,0.82}
\definecolor{backcolour}{rgb}{0.95,0.95,0.92}
\lstdefinestyle{mystyle}{
backgroundcolor=\color{backcolour},
commentstyle=\color{codegreen},
keywordstyle=\color{magenta},
numberstyle=\tiny\color{codegray},
stringstyle=\color{codepurple},
basicstyle=\ttfamily\footnotesize,
breakatwhitespace=false,
breaklines=true,
captionpos=b,
keepspaces=true,
numbers=left,
numbersep=5pt,
showspaces=false,
showstringspaces=false,
showtabs=false,
tabsize=2
}
\lstset{style=mystyle}
\title{Fast Probabilistic Consensus: Adaptive Threshold Consensus with Phase-Shift Dynamics}
\author{
Lux Research\thanks{Corresponding author: [email protected]}\\
\textit{Lux Industries, Inc.}\\
\texttt{[email protected]}
}
\date{2025}
\begin{document}
\luxcoverpage
\begin{abstract}
We present Fast Probabilistic Consensus (FPC), a novel Byzantine fault-tolerant consensus protocol that achieves agreement through adaptive threshold voting with phase-shift dynamics. FPC employs a sigmoid cooling function to transition from exploration ($\theta = 0.5$) to exploitation ($\theta = 0.8$) phases, enabling rapid convergence while preventing metastability. The protocol achieves $\varepsilon$-consensus with $\varepsilon = 2^{-\lambda}$ where $\lambda = \beta \cdot k \cdot (\theta - 0.5)^2$, tolerating up to $f < n/3$ Byzantine nodes. Through committee sampling of size $k = 20$-$30$ validators and requiring $\beta = 5$-$10$ consecutive confident rounds, FPC finalizes transactions in 1-3 seconds with message complexity $O(k \log n)$. We demonstrate FPC's integration within the Lux consensus stack, where it operates as the ``wave'' layer in a physics-inspired consensus architecture. The Zero-copy Application Protocol (ZAP) replaces gRPC+Protobuf for consensus messaging, achieving 9.69M messages/second with a $14\times$ deserialization improvement over Protobuf. FPC's safety, liveness, and BFT tolerance properties have been formally verified in Lean~4 with machine-checked proofs. Simulation results show 99.999\% safety with logarithmic scaling properties suitable for global networks of 100,000+ nodes.
\end{abstract}
\input{sections/01-introduction}
\input{sections/02-consensus-architecture-context}
\input{sections/03-fpc-algorithm}
\input{sections/04-adaptive-threshold-mechanism}
\input{sections/05-threshold-calculation}
\input{sections/06-pseudorandom-function-for-stability}
\input{sections/07-termination-conditions}
\input{sections/08-security-analysis}
\input{sections/09-performance-characteristics}
\input{sections/10-comparison-with-other-consensus-protocol}
\input{sections/11-integration-with-lux}
\input{sections/12-simulation-results}
\input{sections/13-zap-zero-copy-wire-format-for-consensus-}
\input{sections/14-mathematical-foundations}
\input{sections/15-implementation-details}
\input{sections/16-formal-verification}
\input{sections/17-future-work}
\input{sections/18-conclusion}
\input{sections/99-acknowledgments}
\end{document}