mirror of
https://github.com/lux-apps/papers.git
synced 2026-11-03 05:07:46 +00:00
zeekay
4a753bb639
Restructured from flat .tex/.pdf files into per-paper subdirectories. Added Antje Worring as co-author on all papers. Synced PDFs to pdfs/ for download site.
50 lines
2.5 KiB
TeX
50 lines
2.5 KiB
TeX
\section{Comparison with Contemporaries}
|
|
|
|
\label{sec:contemporaries}
|
|
%% ============================================================================
|
|
|
|
\begin{table}[h]
|
|
\centering
|
|
\small
|
|
\begin{tabular}{lllll}
|
|
\toprule
|
|
\textbf{System} & \textbf{Exec parallelism} & \textbf{Consensus DAG?} & \textbf{Conflict source} & \textbf{State model} \\
|
|
\midrule
|
|
Ethereum & none & linear & -- & EVM (account) \\
|
|
Aptos & Block-STM & linear & r/w sets & Move (resource) \\
|
|
Sui (Mysticeti) & object-type & DAG (Narwhal) & object IDs & Move (object) \\
|
|
Solana & account-lock & linear & static lockset & account \\
|
|
Monad & OCC + pipeline & linear & r/w sets (post-hoc) & EVM \\
|
|
Fuel & UTXO-parallel & linear & UTXO inputs & UTXO \\
|
|
Aleph Zero & none & DAG (AlephBFT) & -- & substrate \\
|
|
\midrule
|
|
\textbf{Lux C-Chain (DAG-EVM)} & Block-STM & \textbf{DAG} & \textbf{r/w sets} & EVM \\
|
|
\textbf{Lux X-Chain} & DAG-native & \textbf{DAG} & UTXO inputs & UTXO \\
|
|
\textbf{Lux Z-Chain (DAG-Z)} & parallel verify & \textbf{DAG} & nullifiers & ZK-UTXO \\
|
|
\textbf{Lux Q-Chain} & attest-parallel & \textbf{DAG+Quasar} & PQ stamps & attestation \\
|
|
\bottomrule
|
|
\end{tabular}
|
|
\caption{Lux versus contemporary parallel / DAG blockchains. Lux is the
|
|
only production system in which (a) the execution engine's conflict graph
|
|
is the consensus DAG and (b) this shape holds uniformly across EVM,
|
|
UTXO, ZK-UTXO, and PQ attestation workloads.}
|
|
\label{tab:contemporaries}
|
|
\end{table}
|
|
|
|
The critical distinction: Sui's Narwhal DAG carries \emph{transaction
|
|
availability}, not the execution conflict graph. The DAG is collapsed to a
|
|
total order by Bullshark/Mysticeti and then executed sequentially (or
|
|
parallel by object-type, separately). Aptos' Block-STM operates inside a
|
|
linear block: if block $B_n$ is not yet finalised, no transaction of
|
|
$B_{n+1}$ can execute even if entirely independent. Monad stacks
|
|
pipelining on linear consensus; DAG-level parallelism is not available.
|
|
Solana's account-lock model is static (declared in the tx), not derived
|
|
from execution footprints, and does not compose with DAG consensus.
|
|
|
|
Lux is the only production design in which the same conflict predicate
|
|
drives intra-block execution (Block-STM) \emph{and} inter-block finality
|
|
(nebula DAG) — yielding a uniform model across all chains with a natural
|
|
parallelism axis (EVM, DEX, UTXO, ZK, Oracle, Relay).
|
|
|
|
%% ============================================================================
|