mirror of
https://github.com/lux-apps/papers.git
synced 2026-10-30 18:15:21 +00:00
zeekay
663cc83ca3
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.
63 lines
2.9 KiB
TeX
63 lines
2.9 KiB
TeX
\section{Namespace 2 -- ShapeKind byte}
|
|
\label{sec:shapekind}
|
|
|
|
The ShapeKind byte is the discriminator at byte 1 of every ZAP
|
|
envelope, namespaced under each TypeKind. The ShapeKind value space
|
|
is fresh per TypeKind -- the same byte value can mean different
|
|
things under different TypeKinds without collision.
|
|
|
|
LP-300 records only the \emph{cross-LP-visible} ShapeKinds -- those
|
|
that pass between LPs at the consensus/wire boundary. Per-VM TxKind
|
|
tables (e.g., \texttt{dexvm} \texttt{OrderTx} / \texttt{CancelTx} /
|
|
\texttt{SwapTx}) are internal to the owning chains-VM and are
|
|
documented in LP-186 plus the per-VM wire files; they are NOT
|
|
re-listed in LP-300.
|
|
|
|
\subsection{Cross-LP-visible ShapeKinds}
|
|
|
|
\begin{table}[h]
|
|
\centering
|
|
\small
|
|
\begin{tabular}{@{}p{1.8cm}p{1.8cm}p{1.8cm}p{6.0cm}p{1.2cm}@{}}
|
|
\toprule
|
|
\textbf{TypeKind} & \textbf{ShapeKind} & \textbf{Owner LP} & \textbf{Purpose} & \textbf{Status} \\
|
|
\midrule
|
|
\texttt{0xE8} & \texttt{0x40} & LP-218 & \texttt{RollupBatchTx} body kind & Draft \\
|
|
\texttt{0xE9} & \texttt{0x41} & LP-218 & \texttt{RollupChallengeTx} body kind & Draft \\
|
|
\texttt{0xEA} & \texttt{0x42} & LP-218 & \texttt{RollupExitTx} body kind & Draft \\
|
|
\texttt{0xEB} & \texttt{0x43} & LP-218 & \texttt{RollupGenesisTx} body kind & Draft \\
|
|
\texttt{0xEC} & \texttt{0x44} & LP-219 & \texttt{RollupAggregateBatch} body kind (cross-rollup atomic) & Draft \\
|
|
\texttt{0xF0} & \texttt{0x50} & LP-214 & \texttt{LightClientBlockHeaderRequest} body kind & Draft \\
|
|
\texttt{0xF1} & \texttt{0x51} & LP-214 & \texttt{LightClientStateProofRequest} body kind & Draft \\
|
|
\texttt{0xF2} & \texttt{0x52} & LP-214 & \texttt{LightClientCertProof} body kind & Draft \\
|
|
\bottomrule
|
|
\end{tabular}
|
|
\caption{The eight cross-LP-visible ShapeKinds. LP-218 owns the
|
|
\texttt{0x40--0x43} band under TypeKinds \texttt{0xE8--0xEB}. LP-219
|
|
adds \texttt{0x44} under TypeKind \texttt{0xEC} as the cross-rollup
|
|
atomic extension that reuses LP-211 semantics at the rollup tier.
|
|
LP-214 owns the \texttt{0x50--0x52} band under TypeKinds
|
|
\texttt{0xF0--0xF2}.}
|
|
\label{tab:shapekind}
|
|
\end{table}
|
|
|
|
\subsection{Delegated ShapeKind tables}
|
|
|
|
Two TypeKind blocks delegate their ShapeKind tables out of LP-300
|
|
entirely:
|
|
|
|
\begin{itemize}[leftmargin=2em,nosep]
|
|
\item \textbf{\texttt{0xC0--0xCB} (chains-VM, LP-186).} Each
|
|
chains-VM TypeKind has its own ShapeKind table for the VM's
|
|
internal tx types. These are documented in LP-186 and the per-VM
|
|
wire files. Cross-VM TxKind collisions are impossible because each
|
|
VM's ShapeKind space is local to its TypeKind.
|
|
\item \textbf{\texttt{0xD0--0xDF} (P2P, LP-201).} Each P2P TypeKind
|
|
is degenerate at the ShapeKind level -- one TypeKind, one shape.
|
|
No per-TypeKind ShapeKind table exists or is needed. The ShapeKind
|
|
byte position is always \texttt{0x00} for these envelopes.
|
|
\end{itemize}
|
|
|
|
LP-300's job for these blocks is to record \emph{that} the delegation
|
|
exists, not the contents of the delegated tables.
|