Files
zeekay 53a476db38 papers: add sovereign-exchange, lux-growth-round, lp-310 sections; index them
Four papers had been written but never committed, and INDEX.md already listed
some of them — so the index pointed at files that did not exist in the repo.

Adds:
- sovereign-exchange/ (tex + pdf)
- lux-growth-round/ (tex + pdf)
- lp-310-universal-liquidity/sections/ — five section .tex files that the
  paper \input{}s, so the top-level tex could not build without them
- built PDFs for fee-settlement, lp-208-dag-mempool, lp-310, lux-aivm

PDFs are tracked here by convention: 172 were already committed alongside 1,648
.tex sources, and the ignore rules only exclude the separate pdfs/ directory.
Each of the four has its matching .tex in the same directory — verified, not
assumed.

LaTeX build artifacts (.aux .log .out .toc .fdb_latexmk) stay ignored; nothing
outside .tex/.pdf/INDEX.md is staged. No .md anywhere in the new papers —
papers are LaTeX.
2026-07-26 08:52:12 -07:00

45 lines
2.6 KiB
TeX

\section{Current Status}
\label{sec:status}
This section states, without embellishment, what is shipped versus
specified. An operator evaluating the venue should be able to separate the
running substrate from the protocol layered on it.
\begin{center}
\small
\begin{tabular}{@{}lll@{}}
\toprule
\textbf{Component} & \textbf{Status} & \textbf{Evidence / location}\\
\midrule
\texttt{0x9999} settlement precompile & \textbf{Shipped, live} & Mainnet C-Chain; a maker/taker fill settled on-chain with an atomic two-leg receipt (see below)\\
D-Chain CLOB matching engine & \textbf{Shipped} & \texttt{luxfi/dex}: 169\,ns avg match (p50 125 / p99 292\,ns), 5.91M orders/s single-thread, 11.88M/s $\times$10, 49\,ns cancel, CPU/GPU parity\\
AMM V2 / V3 contracts & \textbf{Shipped} & \texttt{luxfi/standard} constant-function pools\\
Signed order / inventory reservation & \textbf{In build} & Signed-order path and GPU-verified orders exist; the full RFQ settlement predicate is being hardened to \S\ref{sec:rfq}\\
Universal router (waterfall + split) & \textbf{In build} & Off-chain quote aggregation and the atomic multi-leg settlement of \S\ref{sec:router-atomic}\\
Cross-L1 aggregation & \textbf{Spec} & Depends on the shipped bridge; the router's sibling-quote path is specified in \S\ref{sec:router-global}\\
Encrypted-intent submission & \textbf{Spec} & The FHE precompile is shipped; the mempool glue is a separate specification\\
\bottomrule
\end{tabular}
\end{center}
\subsection{The settled fill, in full}
The load-bearing claim --- that atomic, real-time, non-custodial on-chain
settlement is a running primitive rather than a design --- is evidenced by a
live mainnet fill. A maker posted a bid; a taker sold $10$ units of the base
asset into it at price $1.1$; the settlement receipt carried the on-chain
fill event with output amount $11$, together with both ERC-20 transfer legs,
in a single accepted transaction, conserving value exactly ($10 \times 1.1 =
11$). The fill crossed the fresh bid rather than a stale resting order,
confirming price priority. Everything in \S\ref{sec:rfq}--\S\ref{sec:security}
composes \emph{above} this settled primitive.
\subsection{Honest gaps}
The router and the full RFQ predicate are the active build surface; until
they land, the venue runs on the shipped native legs (AMM~+~book~+~\texttt{0x9999})
with the signed-quote PMM leg maturing. Cross-L1 aggregation and encrypted
intent are specified and depend on shipped substrate (bridge, FHE
precompile) but are not yet wired into the router. None of these gaps affect
the guarantees of the shipped native path; they extend its reach and depth.