Files
zeekay 663cc83ca3 docs(papers): ZAP stack + cert profile modes + pitch decks (LP-186..300)
Companion LaTeX papers to luxfi/LPs:
- lp-200-zap-stack: full ZAP-as-substrate paper (10-layer model, deco-
  mplected concerns, performance).
- lp-200-lux-vs-avalanche-diff: code-translation appendix.
- lp-203-gpu-native-verify, lp-205-pipelined-quasar, lp-208-dag-mempool,
  lp-209-mysticeti-ordering, lp-210-block-stm, lp-211-cross-shard-atomic,
  lp-217-cert-profile-modes, lp-218-zap-p3q-pq-rollup,
  lp-220-p3q-corona-magnetar, lp-221-stark-fri-verifier,
  lp-300-schema-registry.

Pitch / outreach decks (luxcover.sty templated):
- blackrock-nahmii-pitch, corporate-dao-stack-analysis,
  nahmii-patent-acquisition, pq-patent-family-future-infringers,
  lux-substrate-platform-pitch, w3a-foundation-membership,
  multi-validator-scale, vfs-archive-cost-study.

Edits aligning to LP-217 / LP-200:
- lp-020-quasar-consensus 02-system-model + 08-performance.
- lp-073-pulsar 11-quasar.
- lp-103-omnichain-explorer 03-chain-support.
- lp-104-graph-engine.
- lp-201-zap-universal-wire/wire-inventory.csv.
- lp-306-lx-social-dex sections/02.
- lux-adoption-roadmap, lux-chain-architecture,
  lux-consensus-engines/08-composition, lux-crypto-agility,
  lux-evm-precompile-engineering/02, lux-fhe-smart-contracts/05,
  lux-quasar-composition/04+06+10, lux-reproducible-builds.
- INDEX.md cross-links the new papers.
2026-06-10 22:35:37 -07:00

71 lines
2.7 KiB
TeX

\section{Pipeline Stages}
Three stages, one per in-flight block. Each stage is defined by its
trigger, its work, the subsystem it touches, and its independence
properties relative to its siblings.
\begin{table}[h]
\centering
\small
\begin{tabular}{@{}lp{3.2cm}p{3.2cm}p{4cm}@{}}
\toprule
\textbf{Stage} & \textbf{Trigger} & \textbf{Subsystem} & \textbf{Independence claim} \\
\midrule
Select & Round $N{+}2$ leader-rotation slot opens & Mempool (ranked heap) + Block-STM speculator & Heap pointer-shuffles non-overlapping with Build($N{+}1$)'s tx-set drain \\
Build & Select stage of same block emits ordered tx-set & ZAP encoder + round-digest binder & Per-block ZAP encoder operates on a different block's transcript than Sign($N$) \\
Sign & Build stage of same block emits block frame & Consensus engine (BLS + Pulsar + Corona + Magnetar legs) & Per-block cert aggregation is content-independent of any other block's aggregation \\
\bottomrule
\end{tabular}
\caption{The three pipeline stages and their orthogonality claims.}
\label{tab:stages}
\end{table}
\subsection{Select stage}
\paragraph{Work.} Mempool sample $\to$ tx-ordering $\to$ Block-STM
speculative execute.
\paragraph{Output.} Ordered candidate tx-set pinned to ZAP buffer
offsets.
\paragraph{Failure.} Mempool empty $\to$ propose empty block;
speculator timeout $\to$ drop speculative branch, propose with
non-speculated set.
\subsection{Build stage}
\paragraph{Work.} Construct block header ZAP frame referencing
selected tx buffers.
\paragraph{Output.} Block frame: parent-hash + tx-set offset list +
leader sig over round-digest.
\paragraph{Failure.} ZAP encode error $\to$ invalid block; fail back
to Select with a smaller candidate set.
\subsection{Sign stage}
\paragraph{Work.} Leader broadcasts block-hash; cert-leg threshold
ceremony begins per LP-217 mode.
\paragraph{Output.} QuasarCert at the operator's configured mode.
\paragraph{Failure.} Insufficient leg sigs $\to$ cert published at
LP-202 lower tier; surviving legs commit the block at the
next-lower mode (LP-217).
\subsection{Stage independence is the load-bearing claim}
The three stages touch orthogonal subsystems. The Select stage's
mempool heap traversal does not interact with the Build stage's ZAP
encoder; the Build stage's encoder does not interact with the Sign
stage's cert-leg aggregator. The independence is not an
implementation property -- it is a structural one. The mempool, the
encoder, and the aggregator each consume bytes and produce bytes; no
two share mutable state.
The stage list maps 1:1 onto the per-block pipeline LP-202 specifies.
LP-202 specifies the per-block atomic-unwind contract; this LP
specifies the multi-block pipeline composed of multiple per-block
pipelines running concurrently.