Files
papers/lux-restaking/lux-restaking.tex
zeekay dd93cb41f7 papers: cover-consistency + build pass on Lux Tier-2/3 catalogue
Sweep across the non-Tier-1 paper catalogue (Tier-1 owned by parallel
agent and excluded). All 113 processed papers already had luxcover
wired up; this commit fixes 14 build breakers and produces fresh
PDFs across the catalogue.

Fixes:
- lux-blockchain-scaling-laws: em-dash inside lstlisting -> --
- lux-corona-pq: stale \input pointing at 03-the-corona-scheme renamed
  to 03-the-corona-scheme (file already renamed on disk)
- lux-lattice-cryptography-primer: same Corona->Corona rename
- lux-formal-verification-lean4: Lean source uses unicode (×, ∀, ∃, ∈,
  ∧, ∨, ∩, ≠, ⟨, ⟩, ·, ¬) inside lstlistings. Added a literate map
  so listings render the math glyphs without UTF-8 fault.
- lux-id-did-specification: ✓/✗ in tabular replaced with \ding{51}
  / \ding{55} (pifont). Added pifont package.
- lux-ntt-simd-implementation: middle-dot in Go assembly listings;
  added literate {·}{\textperiodcentered}.
- lux-ntt-transform: μ, ×, –, — in regular text (no T1 fontenc).
  Replaced with $\mu$/$\times$/--/--- via unicode->latex sweep.
- lux-perpetuals-derivatives, lux-quantum-consensus,
  lux-quasar-consensus, lux-tee-computing-mesh: same unicode->latex
  sweep across body text. Also fixed broken math segment
  `$L_{avg} = 10$\times$$` -> `$L_{avg} = 10\times$`.
- lux-zchain: emoji glyphs in roadmap table replaced with
  parenthetical text.
- lux-triple-proof-consensus: dropped duplicate \usepackage{geometry}
  that clashed with luxcover (geometry option clash).
- pq: defined missing \Rq macro.

PDFs rebuilt for the full Tier-2/3 set.

Excluded (Tier-1, parallel agent): lp-073-pulsar, lp-stricte2epq,
dag-evm-formal, lp-010-quasar-stm-{3,4}, lp-020-quasar-consensus,
lux-institutional-custody, lux-nist-mptc-submission, pqsafe-il5,
pq-rns, plus shared/ and lps/.
2026-05-13 01:27:59 -07:00

81 lines
3.0 KiB
TeX

\documentclass[11pt]{article}
\usepackage{../shared/luxcover}
\usepackage{amsmath,amssymb,amsthm}
\usepackage{mathtools}
\usepackage{bm}
\usepackage{graphicx}
\usepackage{booktabs}
\usepackage{hyperref}
\usepackage{enumitem}
\usepackage{algorithm}
\usepackage{algpseudocode}
\usepackage{xcolor}
\usepackage{tikz}
\usepackage{pgfplots}
\pgfplotsset{compat=1.18}
\usepackage{array}
\usepackage{multirow}
\usepackage{float}
\hypersetup{colorlinks=true,linkcolor=black,citecolor=blue,urlcolor=blue}
\newtheorem{theorem}{Theorem}
\newtheorem{lemma}[theorem]{Lemma}
\newtheorem{proposition}[theorem]{Proposition}
\newtheorem{corollary}[theorem]{Corollary}
\newtheorem{definition}{Definition}
\newtheorem{remark}{Remark}
\title{\textbf{Restaking Protocol for Lux Network Security Extension}\\
\large Enabling Capital-Efficient Economic Security Sharing Across Appchains and Actively Validated Services}
\author{
Zach Kelling\thanks{Corresponding author: [email protected]}\\
\textit{Lux Industries, Inc.}\\
\texttt{[email protected]}
}
\date{2024}
\begin{document}
\luxcoverpage
\begin{abstract}
We present the \textbf{Lux Restaking Protocol} (LRP), a mechanism enabling LUX token holders
to extend the economic security of their staked capital to multiple Actively Validated Services
(AVSs) and application-specific appchains simultaneously. Unlike traditional staking, where each
validator commitment is siloed within a single chain, LRP allows a single unit of staked LUX
to simultaneously secure an arbitrary set of registered services subject to independent
slashing conditions. We formalize the security model as a hypergraph of staking commitments,
prove that aggregate economic security is superadditive under realistic parameter regimes, and
derive tight bounds on the systemic risk introduced by correlated slashing events. Our
capital-efficiency analysis demonstrates that LRP achieves a 4.7$\times$ improvement in
security-per-token-staked compared to isolated appchain validation, with measurable improvements
in bootstrapping economics for new appchains. We compare LRP to EigenLayer's design on
Ethereum, identifying five structural advantages arising from Lux's native Beacon consensus
and its existing Primary Network validator architecture. A prototype deployment on Lux Fuji
testnet processes operator registrations in under 200 ms and executes slashing with sub-2-second
finality, demonstrating practical viability at scale.
\end{abstract}
\tableofcontents
\newpage
%%==========================================================================
\input{sections/01-introduction}
\input{sections/02-background}
\input{sections/03-formal-model}
\input{sections/04-slashing-architecture}
\input{sections/05-operator-registration-protocol}
\input{sections/06-avs-marketplace}
\input{sections/07-capital-efficiency-analysis}
\input{sections/08-systemic-risk-analysis}
\input{sections/09-comparison-with-eigenlayer}
\input{sections/10-implementation}
\input{sections/11-formal-security-analysis}
\input{sections/12-discussion}
\input{sections/99-conclusion}
\end{document}