mirror of
https://github.com/lux-apps/papers.git
synced 2026-10-30 18:15:21 +00:00
zeekay
75a04faa36
Resolves high-severity review findings: anachronistic dates aligned to citation floors; arithmetic corrected to match formulas; internal contradictions collapsed to the body-supported value; LP self-references aligned to filenames; liquidity-surface repo paths scrubbed; AI-slop trimmed. PDFs rebuilt separately.
112 lines
4.3 KiB
TeX
112 lines
4.3 KiB
TeX
\section{Per-Layer Security Guarantees}
|
|
|
|
\label{sec:layers}
|
|
|
|
\subsection{Layer 1: Consensus}
|
|
|
|
\begin{table}[ht]
|
|
\centering
|
|
\caption{Consensus layer security guarantees.}
|
|
\label{tab:consensus-security}
|
|
\begin{tabular}{llll}
|
|
\toprule
|
|
\textbf{Property} & \textbf{Guarantee} & \textbf{Assumption} & \textbf{Status} \\
|
|
\midrule
|
|
Safety & No conflicting finalized blocks & $f < n/3$, co-CDH & [Proven] \\
|
|
Liveness & Blocks finalized within $\Delta$ & Partial synchrony & [Proven] \\
|
|
PQ safety & Epoch-level finality & Module-LWE & [Assumed] \\
|
|
Privacy & Anonymous validator votes & Module-LWE (Pulsar) & [Assumed] \\
|
|
\bottomrule
|
|
\end{tabular}
|
|
\end{table}
|
|
|
|
\textbf{Triple-proof quantum finality} combines three independent proofs per epoch:
|
|
|
|
\begin{enumerate}[leftmargin=2em]
|
|
\item \textbf{BLS aggregate signature} (48 bytes): Classical speed, sub-millisecond
|
|
verification. \textbf{[Proven]} secure under co-CDH in the random oracle
|
|
model~\cite{boneh2001bls}.
|
|
\item \textbf{STARK-compressed ML-DSA} ($\sim$200 bytes): Post-quantum identity
|
|
binding. \textbf{[Assumed]} secure under Module-LWE (NIST FIPS 204). STARK
|
|
soundness \textbf{[Proven]} under collision-resistant hash functions.
|
|
\item \textbf{Corona threshold signature} (embedded in STARK): Anonymous
|
|
validator participation. \textbf{[Assumed]} secure under Module-LWE
|
|
(Ringtail-derived parameter set) with
|
|
parameters providing $> 128$-bit classical security.
|
|
\end{enumerate}
|
|
|
|
Total epoch proof size: 248 bytes. Epoch verification time: ${\sim}2$--$5$\,ms CPU
|
|
(dominated by STARK proof verification via hash-based FRI queries, requiring no
|
|
pairings)~\cite{lux-benchmarks}.
|
|
Block time: 1\,ms.
|
|
|
|
\subsection{Layer 2: Transport (P2P Network)}
|
|
|
|
\begin{table}[ht]
|
|
\centering
|
|
\caption{Transport layer security guarantees.}
|
|
\label{tab:transport-security}
|
|
\begin{tabular}{llll}
|
|
\toprule
|
|
\textbf{Property} & \textbf{Guarantee} & \textbf{Assumption} & \textbf{Status} \\
|
|
\midrule
|
|
Confidentiality & Encrypted P2P channels & CDH (X25519) + M-LWE & [Tested] \\
|
|
Integrity & Authenticated messages & HMAC-SHA256 & [Proven] \\
|
|
Forward secrecy & Past sessions protected & Ephemeral ML-KEM & [Assumed] \\
|
|
Peer auth & Mutual node authentication & Node certificate chain & [Tested] \\
|
|
\bottomrule
|
|
\end{tabular}
|
|
\end{table}
|
|
|
|
Hybrid key exchange (X25519 + ML-KEM-768) provides forward secrecy against quantum
|
|
adversaries as long as ephemeral ML-KEM private keys are erased after each session.
|
|
\textbf{[Tested]} via integration tests with simulated key compromise.
|
|
|
|
\subsection{Layer 3: Execution (EVM)}
|
|
|
|
\begin{table}[ht]
|
|
\centering
|
|
\caption{Execution layer security guarantees.}
|
|
\label{tab:execution-security}
|
|
\begin{tabular}{llll}
|
|
\toprule
|
|
\textbf{Property} & \textbf{Guarantee} & \textbf{Assumption} & \textbf{Status} \\
|
|
\midrule
|
|
Determinism & Same input $\to$ same output & EVM specification & [Tested] \\
|
|
Isolation & Contract cannot access other state & EVM sandboxing & [Tested] \\
|
|
Gas metering & Computation is bounded & Gas limit enforcement & [Proven] \\
|
|
PQ signatures & Quantum-safe tx verification & ML-DSA precompile & [Tested] \\
|
|
FHE & Encrypted computation & Ring-LWE (FHE) & [Assumed] \\
|
|
\bottomrule
|
|
\end{tabular}
|
|
\end{table}
|
|
|
|
Post-quantum precompiles (ML-DSA, ML-KEM, SLH-DSA) are activated at genesis.
|
|
\textbf{[Tested]} with 100\% coverage of NIST Known Answer Tests (KATs).
|
|
|
|
\subsection{Layer 4: Application (Smart Contracts)}
|
|
|
|
\begin{table}[ht]
|
|
\centering
|
|
\caption{Application layer security guarantees.}
|
|
\label{tab:application-security}
|
|
\begin{tabular}{llll}
|
|
\toprule
|
|
\textbf{Property} & \textbf{Guarantee} & \textbf{Assumption} & \textbf{Status} \\
|
|
\midrule
|
|
Access control & Owner-only functions enforced & Signature verification & [Tested] \\
|
|
Reentrancy & CEI pattern enforced & Audit/static analysis & [Tested] \\
|
|
Overflow & SafeMath / Solidity 0.8+ & Compiler guarantees & [Proven] \\
|
|
Oracle integrity & Multi-source price feeds & $> n/2$ honest oracles & [Assumed] \\
|
|
\bottomrule
|
|
\end{tabular}
|
|
\end{table}
|
|
|
|
Application-layer security is the responsibility of smart contract developers, not the
|
|
protocol. The protocol provides tools (precompiles, gas metering, access control
|
|
primitives) but cannot prevent application-level logic errors.
|
|
|
|
%% ========================================================================
|
|
%% 5. FAILURE MODES
|
|
%% ========================================================================
|