mirror of
https://github.com/lux-apps/papers.git
synced 2026-10-30 18:15:21 +00:00
zeekayandHanzo Dev
e2cb62c540
I resolved these files toward a June commit that called the billion-order figures fabricated, and that commit was itself the mistaken one. The July campaign it predates does not assert its numbers, it checks them: a GPU-versus-CPU parity run matching exactly, 38,000,000 fills on both sides at 1,000,000 books, depth 32, 32 takers each, on hardware this estate owns. It also names the error in the earlier framing. Consensus determinism was taken to force a single-thread launch and forfeit the GPU. It does not: determinism constrains ordering WITHIN a book and says nothing across books, so one thread per book — each matching its taker stream in strict price-time priority, bit-for-bit re-executable, millions of threads — saturates the accelerator with every book deterministic. Restored at the later versions across all 27 files: the accounting section, the CLOB matcher, lightspeed-dex, lp-306, lp-308, lp-137, p3q-corona, the precompile engineering sections and the FHE orderbook application. Paper builds, 23 pages, no errors. Co-authored-by: Hanzo Dev <[email protected]>
64 lines
2.6 KiB
TeX
64 lines
2.6 KiB
TeX
\section{Current Status}
|
|
\label{sec:current}
|
|
|
|
\subsection{Architecture Evolution}
|
|
|
|
The Lux exchange architecture has evolved from AMM-first
|
|
(QuantumSwap, 2024) to a hybrid CLOB + AMM design:
|
|
|
|
\begin{center}
|
|
\begin{tabular}{lll}
|
|
\toprule
|
|
\textbf{Component} & \textbf{2024 (QuantumSwap)} & \textbf{2026 (Production)} \\
|
|
\midrule
|
|
Matching engine & AMM bonding curves & CLOB (\texttt{luxfi/dex}) \\
|
|
AMM contracts & Proposed & Deployed (V1--V4) \\
|
|
Order privacy & TFHE on all orders & TFHE on Z-Chain only \\
|
|
Stablecoin & Gold/uranium-backed & USD-backed (USDL) \\
|
|
Cross-chain & ZK teleport & Warp messaging + MPC bridge \\
|
|
\bottomrule
|
|
\end{tabular}
|
|
\end{center}
|
|
|
|
\subsection{What Shipped}
|
|
|
|
\begin{itemize}[nosep]
|
|
\item \textbf{AMM contracts} in \texttt{luxfi/standard/contracts/amm/}
|
|
implement V1 (constant-product), V2 (multi-asset), V3
|
|
(concentrated liquidity), and V4 (hook-extensible) designs.
|
|
The bonding curve algorithms from Sections~2--3 are implemented
|
|
in the V1/V2 pair contracts.
|
|
\item \textbf{CLOB engine} (\texttt{luxfi/dex}) provides billions of
|
|
byte-exact \texttt{uint256} orders/sec of GPU-accelerated matching
|
|
(9.13\,B/s on an NVIDIA GB10, 12.76\,B/s on an AMD Radeon 8060S,
|
|
5.60\,B/s on an Apple M4 Max), used as the primary exchange engine.
|
|
AMM pools serve as passive liquidity that the CLOB can route
|
|
through.
|
|
\item \textbf{USDL}: The stablecoin shipped as a straightforward
|
|
USD-backed ERC-20, not the RWA-collateralized multi-asset
|
|
design. Physical commodity backing (gold, uranium) was deferred
|
|
due to regulatory complexity around commodity-backed tokens.
|
|
\item \textbf{Mixed FT/NFT pools}: The \texttt{LUXRWAPair} contract
|
|
is deployed for RWA token trading, including SecurityToken
|
|
(ERC-20) swaps.
|
|
\end{itemize}
|
|
|
|
\subsection{What Changed}
|
|
|
|
\begin{itemize}[nosep]
|
|
\item \textbf{CLOB over AMM}: For securities trading, a CLOB provides
|
|
price discovery, order types (limit, stop, market), and
|
|
regulatory compliance (best execution obligations) that AMMs
|
|
cannot. AMM pools remain available for DeFi use cases.
|
|
\item \textbf{Warp + MPC over ZK teleport}: The production bridge
|
|
uses Warp messaging with BLS aggregation and 2-of-3 MPC
|
|
threshold signing, which is simpler to audit and maintain than
|
|
a full ZK bridge circuit.
|
|
\item \textbf{USD-backed over commodity-backed}: USDL is 1:1
|
|
USD-backed via ACH deposits. The interest rate mechanism
|
|
from Section~\ref{sec:interest} was not needed for a
|
|
fiat-backed stablecoin.
|
|
\end{itemize}
|
|
|
|
%% ============================================================
|