mirror of
https://github.com/lux-apps/papers.git
synced 2026-11-02 11:39:52 +00:00
zeekay
98343d238e
Quasar Horizon (consensus composition over Pulsar / ML-DSA / BLS lanes
under Prism + LSS lifecycle), Warp 2.0 (Pulse-backed cross-chain envelope
with forward-only v1->v2 migration and lattigo ReadUint64Slice DoS fix),
benchmark report (microbench, reshare, activation, Warp 2.0 verify, Prism
composition, GPU headroom, cross-WAN latency), and NIST IR 8214C-style
submission package (spec, parameter sets, domain separation, serialization,
reference-impl pointers, evaluation report, security analysis, side-channel
considerations).
All four deliverables compile cleanly via pdflatex+bibtex and reference
the canonical proof bucket files at proofs/{definitions,pulsar,lss,quasar}.
No duplication of proof bodies; cite by file path.
97 lines
4.4 KiB
TeX
97 lines
4.4 KiB
TeX
\section{Related Work}
|
|
|
|
\label{sec:related}
|
|
%% ============================================================================
|
|
|
|
\paragraph{Block-STM (Aptos / Diem).}
|
|
Block-STM~\cite{gelashvili2022blockstm} introduced ordered speculative
|
|
execution against a known canonical order. Its central contribution
|
|
is treating the canonical order as a validation primitive rather than
|
|
a serialisation bottleneck. QuasarSTM~3.0 inherits the speculative-
|
|
execute / validate / repair structure and extends it with lane
|
|
abstraction, three-tier validation, semantic reducers, checkpoint-
|
|
based incremental repair, deterministic contention management, commit
|
|
horizons, and multi-GPU sharding.
|
|
|
|
\paragraph{TL2 (DISC 2006).}
|
|
Transactional Locking II~\cite{dice2006tl2} introduced commit-time
|
|
locking with a global version clock. QuasarSTM shards TL2 into
|
|
per-lane clocks (\S\ref{sec:lanes}) and uses lane-clock invariance as
|
|
the Tier-1 fast validation predicate (\S\ref{sec:validation}). There
|
|
is no global clock anywhere in QuasarSTM.
|
|
|
|
\paragraph{TicToc (SIGMOD 2016).}
|
|
TicToc~\cite{yu2016tictoc} eliminated the global timestamp counter
|
|
with per-data-item $(\mathit{read\_ts}, \mathit{write\_ts})$ pairs.
|
|
QuasarSTM adopts the per-key timestamp pair (\S\ref{sec:tictoc}) to
|
|
\emph{reduce false aborts}, with the hard rule
|
|
(Invariant~\ref{inv:tictoc-determinism}) that timestamps cannot
|
|
reorder consensus. Canonical TicToc derives the order from the
|
|
timestamps; QuasarSTM accepts the order from Quasar and uses
|
|
timestamps only to justify the absence of an abort.
|
|
|
|
\paragraph{GPU-STM literature.}
|
|
Cederman et al.~\cite{cederman2010} and Holey et
|
|
al.~\cite{holey2014} catalogue SIMT livelock and scalability collapse
|
|
under skewed access as the dominant pathologies of naive GPU-STM
|
|
ports. QuasarSTM rejects both root causes: deterministic contention
|
|
management (\S\ref{sec:contention}), bounded repair
|
|
(Lemma~\ref{lem:bounded-retry}), and Prism refraction
|
|
(\S\ref{sec:prism}) that isolates hot lanes \emph{before} STM sees
|
|
them.
|
|
|
|
\paragraph{Aria.}
|
|
Aria~\cite{lu2020aria} executes a batch against a single snapshot
|
|
and deterministically commits the maximal serializable subset.
|
|
QuasarSTM~3.0 does \emph{not} adopt this model; the 3.1 evolution
|
|
(\S\ref{sec:adaptive}) introduces an Aria-style commit-selection
|
|
service.
|
|
|
|
\paragraph{ESSN / multiversion serialization graphs.}
|
|
Adya et al.~\cite{adya2000essn} formalise validation against a
|
|
multiversion serialization graph. QuasarSTM~3.0 uses the simpler
|
|
``visible-version under canonical order'' validation; the 3.1
|
|
evolution introduces an MVSG-derived rule
|
|
(\texttt{KnownTotalOrder}~\cite{lp010-quasarstm}).
|
|
|
|
\paragraph{Quasar consensus stack.}
|
|
Quasar~\cite{quasar2025} is the post-quantum BFT consensus layer that
|
|
supplies $\preceq_{\mathrm{can}}$ to QuasarSTM.
|
|
LP-132~\cite{lp132-quasarexec} is the GPU execution adapter that
|
|
hosts QuasarSTM (wave-tick scheduler, device-resident rings, EVM
|
|
fiber VM, async cold-state, per-lane cert verification).
|
|
|
|
\subsection{Adaptive Evolution: 3.1, 3.2, 4.0}
|
|
\label{sec:adaptive}
|
|
|
|
QuasarSTM~3.0 (this paper) is the GPU-native ordered MVCC baseline.
|
|
Ongoing research---out of scope for the 3.0 specification---converges
|
|
on a hybrid adaptive thesis: predict independence, isolate owned
|
|
state, defer commutative hot operations, use MVCC only where needed,
|
|
validate against a known deterministic order, and keep the GPU
|
|
commit path batched. Three named generations are tracked in the
|
|
LP-010 living document~\cite{lp010-quasarstm}:
|
|
|
|
\begin{itemize}[leftmargin=2em]
|
|
\item \textbf{3.1}: ConflictSpec ABI (AFT 2025
|
|
conflict-specifications work~\cite{aft2025conflictspec}),
|
|
NEMO~\cite{nemo2025} LaneClass (owned / shared / hot-shared /
|
|
commutative), Aria-style deterministic commit selection.
|
|
\item \textbf{3.2}: RapidLane~\cite{rapidlane2025} deferred-object
|
|
reducers, ForeSight~\cite{foresight2025} predictive scheduler,
|
|
Chiron~\cite{chiron2025} execution-hint roots,
|
|
Multiverse~\cite{multiverse2026} dynamic per-lane versioning
|
|
mode.
|
|
\item \textbf{4.0}: CSMV~\cite{csmv} GPU client/server commit
|
|
separation, Motor~\cite{motor2024} VersionBlock RDMA layout,
|
|
vMVCC~\cite{vmvcc} formally specified CPU reference, surgical
|
|
operation-level concurrency for pathological long
|
|
transactions.
|
|
\end{itemize}
|
|
|
|
These are research, not specification. The 3.0 spec frozen on
|
|
December~15, 2025 stands on its own.
|
|
|
|
|
|
%% ============================================================================
|