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.
55 lines
2.2 KiB
TeX
55 lines
2.2 KiB
TeX
\section{Introduction}
|
|
|
|
This paper expands on LP-217
|
|
(\texttt{lps/LP-217-cert-profile-modes.md}) with the Corona/Pulsar
|
|
parity audit verdict (2026-06-03), the per-mode use cases, and the
|
|
LP-202 monotonic tier-degradation contract that lets a single cert
|
|
struct serve all relying-party policies.
|
|
|
|
\subsection{What was wrong before}
|
|
|
|
LP-017 v1 named cert profiles after astronomical phenomena: Pulsar,
|
|
Aurora, Polaris. Three concrete failures of the codename surface:
|
|
|
|
\begin{enumerate}[leftmargin=2em,nosep]
|
|
\item \textbf{Posture is opaque.} ``Aurora'' does not announce that
|
|
BLS is the fast-path leg or that lattice diversity is present.
|
|
Operators ask ``is Aurora PQ?'' -- the answer requires reading
|
|
LP-017's specification text.
|
|
\item \textbf{Ordering is non-monotone.} Pulsar $\to$ Aurora $\to$
|
|
Polaris is the v1 security ordering, but the names give no hint
|
|
that Polaris is a superset of Aurora. A new operator reading the
|
|
codenames in alphabetical order builds the wrong mental model.
|
|
\item \textbf{No room for pure-PQ variant.} A chain that does not
|
|
need a classical fast-path (post-PQ-transition L1, sovereign
|
|
network not anchored to a BLS bridge) has no v1 name; the v1
|
|
spec assumes BLS is always present.
|
|
\end{enumerate}
|
|
|
|
\subsection{What this LP solves}
|
|
|
|
The 4-mode ladder fixes all three: names declare posture, ordering
|
|
is monotone (each step is a superset), and pure-PQ variants are
|
|
first-class (prefix \texttt{strict-}).
|
|
|
|
\begin{equation}
|
|
\textrm{PQ-off} \subset \textrm{PQ-fast} \subset \textrm{PQ-strict}
|
|
\subset \textrm{PQ-heavy}
|
|
\end{equation}
|
|
|
|
Each step adds exactly one independent security property. The
|
|
pure-PQ variants drop BLS:
|
|
|
|
\begin{itemize}[leftmargin=2em,nosep]
|
|
\item \texttt{strict-PQ-fast} $=$ Pulsar
|
|
\item \texttt{strict-PQ-strict} $=$ Pulsar + Corona
|
|
\item \texttt{strict-PQ-heavy} $=$ Pulsar + Corona + Magnetar
|
|
\end{itemize}
|
|
|
|
Seven valid configurations total. The QuasarCert wire format
|
|
(LP-182) is unchanged; the cert struct shape is unchanged; the
|
|
LP-017 v1 composition predicates (\texttt{IsPolaris},
|
|
\texttt{IsDoubleLattice}, \texttt{HasHashBased}) are unchanged.
|
|
The new mode name is a single header byte on the operator config
|
|
knob -- \texttt{quasar.cert\_mode}.
|