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

93 lines
3.6 KiB
TeX

\documentclass[11pt]{article}
\usepackage{../shared/luxcover}
\usepackage{amsmath,amssymb,amsthm}
\usepackage{graphicx}
\usepackage{booktabs}
\usepackage{hyperref}
\usepackage{listings}
\usepackage{xcolor}
\usepackage{tikz}
\usepackage{siunitx}
\usepackage{multirow}
\usepackage{algorithm}
\usepackage{algpseudocode}
\usetikzlibrary{arrows.meta,positioning,calc,shapes.geometric,fit}
\sisetup{group-separator={,}}
\definecolor{luxblue}{RGB}{30,64,175}
\definecolor{luxgold}{RGB}{234,179,8}
\definecolor{dagteal}{RGB}{13,148,136}
\definecolor{linearred}{RGB}{220,38,38}
\newtheorem{theorem}{Theorem}
\newtheorem{lemma}[theorem]{Lemma}
\newtheorem{corollary}[theorem]{Corollary}
\theoremstyle{definition}
\newtheorem{definition}[theorem]{Definition}
\title{DAG-EVM and Conflict-Graph Consensus\\for the Lux Multi-Chain}
\author{
Lux Research\thanks{Corresponding author: [email protected]}\\
\textit{Lux Industries, Inc.}\\
\texttt{[email protected]}
}
\date{March 2026}
\begin{document}
\luxcoverpage
\begin{abstract}
We present a unified DAG consensus model for the Lux multi-chain that lifts
Block-STM-style optimistic concurrency from a per-block scheduler into a
first-class finality primitive. Each block-producing chain (C-Chain EVM,
D-Chain DEX, Z-Chain ZK-UTXO, A-Chain AI, O-Chain Oracle, R-Chain Relay,
S-Chain ServiceNode) emits transaction batches as vertices in a native
directed acyclic graph, with conflict sets derived from the chain's natural
state model: EVM read/write sets, UTXO nullifiers, DEX order tuples,
job identifiers, feed rounds, destination-chain nonces, or service epochs.
Antichains are finalised in parallel under the Quasar post-quantum
certificate scheme; sequential worldview is preserved by a serialisability
theorem. We formalise the safety and no-double-spend properties in Lean~4
and TLA$^+$, prove commutativity of non-conflicting vertices, and show that
GPU-native conflict-graph reduction plus GPU ecrecover/keccak yields a
$32\times$ practical speedup on the dominant critical-path operations. The
result is a DAG-EVM that preserves bytecode-level compatibility with
Ethereum, a DAG-Z-Chain that preserves ZK-UTXO double-spend security, and a
framework that cleanly contrasts Lux against contemporary parallel and
DAG blockchains (Aptos, Sui, Solana, Monad, Fuel).
\end{abstract}
\tableofcontents
\newpage
%% ============================================================================
\input{sections/01-introduction}
\input{sections/02-chain-level-conflict-rules}
\input{sections/03-dag-evm}
\input{sections/04-dag-z-chain}
\input{sections/05-lean-4-development}
\input{sections/06-tla-specifications}
\input{sections/07-comparison-with-contemporaries}
\input{sections/08-gpu-native-conflict-detection}
\input{sections/09-cevm-consensus-integration}
\input{sections/09-four-way-parity}
\input{sections/10-cuda-port}
\input{sections/11-empirical-results}
\input{sections/12-pqz-cross-chain-parallelism}
\input{sections/13-v0.24-correctness-release}
\input{sections/14-v0.26-benchmarks}
\input{sections/99-conclusion}
\appendix
\section*{Reproducibility}
\textbf{Source code.} \texttt{github.com/luxfi/consensus} (commit \texttt{TBD}); EVM at \texttt{github.com/luxfi/evm}; node at \texttt{github.com/luxfi/node}.\\
\textbf{Build.} \texttt{go build ./...} and \texttt{go test ./...} at the corresponding release tag; CUDA port requires NVCC \(\geq\) 12.\\
\textbf{Hardware tested.} TBD (x86\_64 Linux; NVIDIA GPU for the CUDA execution path).\\
\textbf{Standards referenced.} EIPs cited inline (London/Cancun/Prague feature gates); FIPS 204 (ML-DSA) for the post-quantum cross-chain lane.\\
\textbf{Contact.} [email protected].
\end{document}