mirror of
https://github.com/lux-apps/papers.git
synced 2026-11-03 05:07:46 +00:00
zeekayandHanzo Dev
178febad68
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]>
98 lines
4.0 KiB
TeX
98 lines
4.0 KiB
TeX
\section{Composition With Sibling LPs}
|
|
|
|
\begin{table}[h]
|
|
\centering
|
|
\small
|
|
\begin{tabular}{@{}lp{9cm}@{}}
|
|
\toprule
|
|
\textbf{LP} & \textbf{Composition} \\
|
|
\midrule
|
|
LP-063 & Z-Chain; the parent L1 hosting rollup commits \\
|
|
LP-073 & Pulsar threshold signature (the scheme P3Q verifies) \\
|
|
LP-078 & EVM precompiles; precompile registry P3Q joins \\
|
|
LP-182 & QuasarCert wire format (the cert the rollup state inherits) \\
|
|
LP-200 & ZAP Stack umbrella; the no-codec wire guarantee \\
|
|
LP-202 & Pipelining and cert tier degradation; the finality timeline the rollup inherits \\
|
|
LP-203 & GPU-native verify; projected batched P3Q verify (production P3Q verify is pure-Go/CPU) \\
|
|
LP-204 & Network of blockchains (Tier-3 rollup definition, ``no own validator set'') \\
|
|
LP-217 & Cert profile modes (per-rollup \texttt{CertModeFloor} selection) \\
|
|
\bottomrule
|
|
\end{tabular}
|
|
\caption{Composition of LP-218 with sibling LPs.}
|
|
\label{tab:composition}
|
|
\end{table}
|
|
|
|
\section{Performance Characteristics}
|
|
|
|
\begin{table}[h]
|
|
\centering
|
|
\small
|
|
\begin{tabular}{@{}p{6cm}rl@{}}
|
|
\toprule
|
|
\textbf{Metric} & \textbf{Value} & \textbf{Source} \\
|
|
\midrule
|
|
P3Q precompile verify, single sig & $\sim$\SI{50}{\micro\second} (CPU) & pure-Go FIPS-204 verify \\
|
|
P3Q precompile verify, batched ($N{=}64$) & $\sim$\SI{5}{\milli\second} aggregate (projected) & LP-203 Pulsar aggregate row \\
|
|
Rollup batch finalization end-to-end (PQ-fast parent) & $\sim$\SI{5}{\milli\second} & PQ-fast preliminary + P3Q verify \\
|
|
Rollup batch finalization end-to-end (PQ-strict parent) & $\sim$\SI{15}{\milli\second} & PQ-strict final + P3Q verify \\
|
|
Sequencer throughput (single node) & \SI{100}{\kilo tx/s}--\SI{1}{\mega tx/s} & NIC-bound; not Z-Chain-bound \\
|
|
Aggregate throughput, $M$ rollups on one Z-Chain & $10{+}$\SI{}{\mega tx/s} & $M$ sequencers compose \\
|
|
Gas cost per rollup batch on Z-Chain & $\sim$\SI{50000}{gas} (P3Q) $+$ $\sim$\SI{21000}{gas} base & One P3Q verify per batch \\
|
|
\bottomrule
|
|
\end{tabular}
|
|
\caption{Performance characteristics. \textbf{Projected} where
|
|
labeled. The production P3Q verify path is the pure-Go/CPU FIPS-204
|
|
verify; a batched GPU verify path (LP-203) is projected, not
|
|
measured.}
|
|
\label{tab:performance}
|
|
\end{table}
|
|
|
|
Throughput scales horizontally in $M$ (rollups per Z-Chain).
|
|
Z-Chain's verify capacity is the bottleneck only at $M \gg 100$ --
|
|
at $M{=}100$, Z-Chain verifies 100 P3Q sigs per block
|
|
($\sim$\SI{5}{\milli\second} total verify, well within block
|
|
budget).
|
|
|
|
\section{Cross-Rollup Atomicity}
|
|
|
|
Two rollups deployed on the same Z-Chain instance can commit
|
|
atomically: both \texttt{RollupBatchTx}es land in the same Z-Chain
|
|
block and share the same QuasarCert. Either both finalize or
|
|
neither does. This is automatic -- no additional protocol is
|
|
needed.
|
|
|
|
Cross-L1 atomicity (rollup-on-Lux $\leftrightarrow$
|
|
rollup-on-Hanzo-L1) requires the bridgevm path defined in LP-204
|
|
``Tier-1 $\leftrightarrow$ Tier-1 bridge'' and is out of scope for
|
|
this LP. A future LP will specify rollup-to-rollup cross-L1
|
|
atomic composition.
|
|
|
|
\section{Activation Marker}
|
|
|
|
\begin{verbatim}
|
|
activates: 2025-12-25T16:20:00-08:00
|
|
activates-unix: 1766708400
|
|
\end{verbatim}
|
|
|
|
The P3Q precompile is callable at slot \texttt{0x012205} from the
|
|
genesis block of the new final Lux network. Rollup deployments via
|
|
\texttt{RollupGenesisTx} are accepted by Z-Chain from height 0.
|
|
|
|
\section{Backwards Compatibility}
|
|
|
|
None. The pre-Quasar Edition Lux network had no P3Q precompile and
|
|
is a separate network out of scope.
|
|
|
|
\section{Future Work}
|
|
|
|
\begin{itemize}[leftmargin=2em,nosep]
|
|
\item \textbf{Rollup-to-rollup atomic composition} across
|
|
L1 boundaries (cross-Tier-3 atomicity via bridgevm) -- a future LP.
|
|
\item \textbf{LP-220} -- P3Q-Corona: wire the Module-LWE threshold
|
|
verifier into P3Q kind \texttt{0x02} on the existing
|
|
\texttt{0x012205} slot (for Corona-threshold-signed rollups).
|
|
\item \textbf{LP-221} -- Dedicated STARK/Groth16 verifier precompile
|
|
(alternative to the generic EVM verifier for ZK rollups; closes
|
|
the $\sim$\SI{500000}{gas} STARK-verify cost gap).
|
|
\end{itemize}
|