mirror of
https://github.com/lux-apps/papers.git
synced 2026-10-30 18:15:21 +00:00
zeekay
1ecc25e9cf
The seven engine specifications (lux-{photon,wave,nova,nebula,prism,ray,field}-protocol)
were fragmented short notes documenting layers of the same Quasar consensus stack.
This commit merges them into a single canonical reference, lux-consensus-engines.tex,
that uses one preamble, one set of theorems, one bibliography, and one composition
chapter showing how the engines layer into the LP-020 finality pipeline.
The seven originals are reduced to single-page breadcrumb stubs pointing at the
consolidated paper; their sections/ content is preserved on disk for git history.
- new: lux-consensus-engines/ (50 pages, 646KB PDF, ~2900 lines tex)
- breadcrumbs: each original keeps cover + title + stub paragraph naming its chapter
- composition: chapter 9 records the layered contract Photon < Wave < Nova < ...
- bibliography: consolidated from the seven original thebibliography blocks
31 lines
1.2 KiB
TeX
31 lines
1.2 KiB
TeX
\section{Security Analysis}
|
|
|
|
\label{sec:wave-security}
|
|
|
|
\subsection{Eclipse Attacks}
|
|
|
|
An eclipse attack attempts to isolate a validator's sample to consist only of Byzantine
|
|
nodes. With uniform random sampling from $n = 500$ validators and $k = 20$:
|
|
\[
|
|
\Pr[\text{all } k \text{ sampled are Byzantine}] = \binom{f}{k} / \binom{n}{k}
|
|
\leq \left(\frac{f}{n}\right)^k = (0.33)^{20} < 2^{-32}
|
|
\]
|
|
Network-level defenses (peer diversity, multiple transport protocols) further reduce this
|
|
probability in practice.
|
|
|
|
\subsection{Sybil Resistance}
|
|
|
|
The Wave protocol assumes a fixed, authenticated validator set. Sybil resistance is
|
|
provided by the staking mechanism on the platform chain: each validator must bond
|
|
stake, and the sampling probability is proportional to stake weight.
|
|
|
|
\subsection{Long-Range Attacks}
|
|
|
|
Wave's DAG structure and confidence counters are ephemeral---they concern only the
|
|
current UTXO set. Long-range attacks (rewriting history from a past state) are prevented
|
|
by the platform chain's periodic checkpointing.
|
|
|
|
%% -----------------------------------------------------------------------
|
|
%% 11. CONCLUSION
|
|
%% -----------------------------------------------------------------------
|