Files
zooqueen a10bf7bbc6 papers: reconcile Corona to Module-LWE (Ringtail-derived, rank-7), not Ring-LWE rank-1
- canonical lux-corona-pq paper: rank-7 Module-LWE (A in R_q^{8x7}, q=48-bit), Module-SIS
- scrub residual Corona Ring-LWE/R-LWE labels across ethos-of-lux, pqsafe-il5,
  lux-whitepaper, lux-quasar-composition, lp-020; Corona<->Pulsar = parameter regime,
  both Module-LWE (not rank-1-vs-rank-k)
- LLM.md: drop stale 'Corona as rank-1' wobble note; align to code/Ringtail params
- rebuild affected PDFs
2026-06-20 01:59:25 -07:00

110 lines
5.1 KiB
TeX

\section{Activation roadmap}
\label{sec:activation}
%% ============================================================================
\subsection{Activation height}
QuasarSTM~4.0 activated on Lux mainnet at \textbf{2026-02-14, 17:00
UTC}. The activation predicate is
\[
\mathit{quasar.execution\_version} \geq 4
\]
in the Quasar consensus engine (LP-020). Wave-tick rounds emitted with
$\mathit{execution\_version} < 4$ after the activation height are
rejected.
Validators upgraded across the preceding week:
\begin{itemize}[leftmargin=2em]
\item \textbf{2026-02-07}: spec freeze; \texttt{cevm} v0.41--v0.49
milestone train feature-complete on \texttt{main}.
\item \textbf{2026-02-08 to 2026-02-13}: staged validator rollout;
$\geq 80\%$ stake on 4.0 by 2026-02-13~18:00~UTC.
\item \textbf{2026-02-14 17:00~UTC}: hard activation. 4.0 becomes the
only valid execution version.
\end{itemize}
\subsection{The v0.41--v0.49 deliverable train}
\begin{table}[ht]
\centering
\small
\caption{The 4.0 deliverable train. All milestones landed on
\texttt{cevm} \texttt{main} between 2026-01-15 and 2026-02-07. The
activation height (2026-02-14) is the partition.}
\label{tab:roadmap}
\begin{tabular}{p{0.07\linewidth}p{0.32\linewidth}p{0.51\linewidth}}
\toprule
\textbf{Ver.} & \textbf{Theme} & \textbf{Headline content} \\
\midrule
v0.41 & CUDA backend mirror & Persistent CTAs, \texttt{\_\_threadfence}, layout-byte-identical with Metal \\
v0.42 & Cert-subject hardening + \texttt{KnownTotalOrder} & \texttt{certificate\_subject} includes P/Q/Z roots; \texttt{KnownTotalOrder} introduced; Nova/Nebula mode roots separated \\
v0.43 & ConflictSpec ABI + LaneClass + dynamic VersioningMode + AdaptiveSchedule drain & \S\S\,\ref{sec:conflictspec}, \ref{sec:laneclass}, \ref{sec:multiverse}, \ref{sec:abmf} \\
v0.44 & Real BLS12-381 pairing kernel & Replaces HMAC-keccak BLS placeholder. \S\,\ref{sec:verifiers} \\
v0.45 & Real Corona Module-LWE + real Groth16 & Replaces HMAC-keccak placeholders. \S\,\ref{sec:verifiers} \\
v0.46 & Full EVM coverage + journaled SSTORE + EIP-2929/3529 + Tier 3 reducers & 175 opcodes; reducer commit \S\,\ref{sec:tier3} \\
v0.47 & Predictive scheduling + Chiron hint roots & Per-tick \texttt{hint\_roots} \S\,\ref{sec:horizon}, \cite{chiron2025} \\
v0.48 & Motor VersionBlock + A/B/M/F drains + fiber checkpoints & \S\S\,\ref{sec:versionblock}, \ref{sec:abmf}, \ref{sec:checkpoints} \\
v0.49 & CSMV commit-server scaffold + formal CPU reference + cross-backend determinism harness & \S\,\ref{sec:determinism}; harness gated in CI at $\geq 96\%$ line coverage on the CPU reference oracle (LP-137-COVERAGE.md) \\
\bottomrule
\end{tabular}
\end{table}
\subsection{Migration steps for validators}
\begin{enumerate}[leftmargin=2em]
\item Upgrade \texttt{cevm} to a release built from \texttt{cevm}
$\geq$ v0.49.
\item Re-roll the Quasar consensus engine binary (LP-020) with
\texttt{execution\_version=4} support.
\item Verify the cert verifier table at engine creation; on production
networks the verifier table must be \texttt{kProdVerifiers}
(\S\ref{sec:verifiers}). The \texttt{EVM\_DEV\_HMAC\_VERIFIER}
flag is rejected at startup.
\item Run \texttt{cevm-genesis-replay} against the latest 3.0 round to
confirm byte-identical roots before publishing.
\item Publish on the validator gossip channel and join 4.0 round
production.
\end{enumerate}
There is no on-disk state migration. 4.0 reads 3.0 round artifacts as
historical 3.0 rounds; new rounds emitted post-activation are 4.0
rounds.
\subsection{Migration steps for app developers}
\begin{enumerate}[leftmargin=2em]
\item Recompile contracts against the 4.0 EVM (175 opcodes); contracts
that compiled against 3.0 (118 opcodes) are forward-compatible.
\item Adopt the Solidity \texttt{lane\_class} attribute on hot state
variables to opt into the AdaptiveSchedule fast path
(\S\ref{sec:conflictspec}). Without the attribute, the predictor
and historical sources still apply; the attribute adds a
higher-priority \texttt{Static} source.
\item For DEX-style hot lanes (fee accumulators, order-book levels),
adopt the \texttt{Commutative} class to route writes through
Tier~3 reducers (\S\S\,\ref{sec:tier3}, \ref{sec:laneclass}).
\item Re-run integration tests against the cross-backend determinism
harness (\S\ref{sec:determinism}); contracts that produce
identical roots in both backends are 4.0-clean.
\end{enumerate}
\subsection{Out of scope for 4.0 (5.0 research)}
\begin{itemize}[leftmargin=2em]
\item Multi-GPU MVCC over RDMA.
\item Operation-window validation for pathological long transactions.
\item Formal proof of kernel refinement against the abstract
semantics. (4.0 ships the abstract semantics and the
differential fuzzer; the proof is 5.0.)
\item Distributed CSMV commit server. (4.0 ships the single-GPU
scaffold.)
\item 800G InfiniBand / GPUDirect cell topologies.
\end{itemize}
These are tracked under a separate \emph{QuasarSTM 5.0 research} document
that does not touch the 4.0 production specification.
%% ============================================================================