Files
papers/lux-quasar-consensus/sections/06-performance-characteristics.tex
zeekayandHanzo Dev 178febad68 papers: reconcile T-Chain -> M-Chain / F-Chain / B-Chain per LP-134
Every rendered "T-Chain" / "ThresholdVM" / "teleportvm" reference across
the paper corpus is rewritten to the correct canonical chain by concern:
threshold signing / MPC / bridge custody / key recovery -> M-Chain (MVM);
FHE / encrypted compute / threshold decryption -> F-Chain (FVM); teleport
/ cross-chain messaging -> B-Chain (bridgevm); consensus Pulsar stays
Q-Chain. Section lux-trust-kernel/03-t-chain-threshold-governance.tex
renamed -> 03-f-chain-encrypted-policy.tex (with \input + xref fixes).
Braided "T-Chain" sections split by concern (M vs F). Only lp-020's
chain-separation rationale and the shared lux/chains/thresholdvm library
path retain the name, to record the removal. All changed papers rebuilt
(pdflatex, rc=0, no undefined refs).

ยง09 of lux-dao-governance-framework reframed: fabricated "production
deployment" metrics ($50M/$240k/$12M, survey %s, "as of Oct 2024")
relabeled as illustrative design configurations with no invented
replacements; reality noted (DAO treasury is a 1/1 Safe); conclusion
echo + one "first production" overclaim softened.

This commit also captures concurrent corpus workstreams on the same tree.

Co-authored-by: Hanzo Dev <[email protected]>
2026-07-02 00:57:09 -07:00

65 lines
1.9 KiB
TeX

\section{Performance Characteristics}
\subsection{Mainnet Configuration (21 validators)}
\begin{table}[h]
\centering
\begin{tabular}{@{}ll@{}}
\toprule
\textbf{Parameter} & \textbf{Value} \\
\midrule
K (Sample size) & 21 \\
$\alpha$ (Preference quorum) & 13 \\
$\alpha_{conf}$ (Confidence quorum) & 18 \\
$\beta$ (Confidence threshold) & 8 \\
Q-Threshold (Corona) & 15 of 21 \\
Quasar Timeout & 10ms (GPU BLS) / 100ms (CPU fallback) \\
Block Gas Limit & 1{,}000{,}000{,}000 (1\,B) \\
Txs/Block & $\sim$47{,}619 (at 21{,}000 gas/tx) \\
Finality Target & 10ms (GPU BLS) / 100ms (CPU BLS fallback) \\
\bottomrule
\end{tabular}
\label{tab:mainnet-params}
\end{table}
\subsection{Performance Metrics}
\begin{table}[h]
\centering
\begin{tabular}{@{}lll@{}}
\toprule
\textbf{Metric} & \textbf{Value} & \textbf{Description} \\
\midrule
Block Gas Limit & 1\,B & 47{,}619 txs/block at 21k gas/tx \\
Finality (GPU BLS) & 10ms & Primary target (co-located validators) \\
Finality (CPU BLS) & 100ms & Fallback (commodity hardware) \\
GPU BLS Aggregation & 3ms & Metal/CUDA shader \\
Corona Aggregation & 7ms & PQ signature combination \\
Certificate Size & 2.9KB & Combined BLS + Corona \\
\bottomrule
\end{tabular}
\label{tab:performance}
\end{table}
\subsection{Throughput Analysis}
Under Byzantine conditions ($f < n/3$), with 1\,B gas block limit:
\begin{align}
\text{Txs/block} &= \frac{1{,}000{,}000{,}000}{21{,}000} \approx 47{,}619 \\
\text{TPS (GPU BLS)} &= \frac{47{,}619}{0.010\text{s}} = 4{,}761{,}904 \text{ TPS} \\
\text{TPS (CPU BLS)} &= \frac{47{,}619}{0.100\text{s}} = 476{,}190 \text{ TPS}
\end{align}
These are execution-only opcode-dispatch upper bounds, \emph{not} end-to-end finality:
end-to-end throughput is additionally bound by signature recovery, settlement
conflict-detection, and BLS/PQ finality.
Finality probability after $\beta$ rounds:
\begin{equation}
P(\text{finality}) \geq 1 - \epsilon, \quad \epsilon \approx 10^{-10}
\end{equation}