Files
papers/lp-225-xss-x-chain-settlement-spine/lp-225-xss-x-chain-settlement-spine.tex
zeekayandHanzo Dev 178febad68 papers: reconcile T-Chain -> M-Chain / F-Chain / B-Chain per LP-134
Every rendered "T-Chain" / "ThresholdVM" / "teleportvm" reference across
the paper corpus is rewritten to the correct canonical chain by concern:
threshold signing / MPC / bridge custody / key recovery -> M-Chain (MVM);
FHE / encrypted compute / threshold decryption -> F-Chain (FVM); teleport
/ cross-chain messaging -> B-Chain (bridgevm); consensus Pulsar stays
Q-Chain. Section lux-trust-kernel/03-t-chain-threshold-governance.tex
renamed -> 03-f-chain-encrypted-policy.tex (with \input + xref fixes).
Braided "T-Chain" sections split by concern (M vs F). Only lp-020's
chain-separation rationale and the shared lux/chains/thresholdvm library
path retain the name, to record the removal. All changed papers rebuilt
(pdflatex, rc=0, no undefined refs).

ยง09 of lux-dao-governance-framework reframed: fabricated "production
deployment" metrics ($50M/$240k/$12M, survey %s, "as of Oct 2024")
relabeled as illustrative design configurations with no invented
replacements; reality noted (DAO treasury is a 1/1 Safe); conclusion
echo + one "first production" overclaim softened.

This commit also captures concurrent corpus workstreams on the same tree.

Co-authored-by: Hanzo Dev <[email protected]>
2026-07-02 00:57:09 -07:00

102 lines
3.9 KiB
TeX

\documentclass[11pt,a4paper]{article}
\usepackage{../shared/luxcover}
\usepackage[utf8]{inputenc}
\usepackage[T1]{fontenc}
\usepackage{amsmath,amssymb,amsfonts}
\usepackage{amsthm}
\newtheorem{theorem}{Theorem}
\usepackage{graphicx}
\usepackage{hyperref}
\usepackage{booktabs}
\usepackage{enumitem}
\usepackage{xcolor}
\usepackage{siunitx}
\usepackage{listings}
\hypersetup{colorlinks=true,linkcolor=black,citecolor=blue,urlcolor=blue}
% Absorb the few overfull boxes from long unbreakable \texttt{} identifiers
% (NewMeteredUTXOState, executeWithdraw, ContractP3QVerifyAddress) without
% loosening normal lines.
\emergencystretch=3em
\lstset{
basicstyle=\ttfamily\scriptsize,
breaklines=true,
frame=single,
showstringspaces=false,
}
% Status macros: mark every claim IMPLEMENTED vs DESIGN-ONLY inline.
\newcommand{\IMPL}{\textcolor{black}{\textbf{[IMPLEMENTED]}}}
\newcommand{\DESIGN}{\textcolor{black}{\textbf{[DESIGN-ONLY]}}}
\newcommand{\CRYPTO}{\textcolor{black}{\textbf{[CRYPTO-REVIEW]}}}
\title{XSS --- The X-Chain Settlement Spine:\\
One Economic Ledger, Many Computing Chains}
\author{Lux Industries, Inc. \\
\texttt{[email protected]}}
\date{}
\begin{document}
\luxcoverpage
\begin{abstract}
Today every Lux chain keeps a parallel spendable ledger. The X-Chain
owns a UTXO set; the P-Chain owns a \emph{second}, independent UTXO set
plus locked staking outputs; the D-Chain DEX owns a third, an
available/locked per-account balance ledger. Value shuttles between
them through atomic \texttt{ImportTx}/\texttt{ExportTx} over shared
memory --- a faithful but duplicative rail in which the same coin is
represented, conserved, and double-checked in several places at once.
This LP specifies the \emph{X-Chain Settlement Spine} (XSS): collapse
the parallel ledgers into one. The core rule is \textbf{other chains
compute, X settles}. X-Chain becomes the single canonical economic
ledger --- the visible settlement spine: it owns UTXOs, asset IDs,
operator-capability NFTs, lock state, the total ordering of all asset
movements, and the conservation invariant. Z-Chain is its shielded
counterpart: a private value pool (commitments/nullifiers, Zcash-shaped)
reachable by shielding a visible X UTXO into a Z note and unshielding
back, with validity crossing the boundary through the P3Q
(ML-DSA-65 attestation, precompile \texttt{0x012205}) and starkfri
(STARK/FRI, precompile \texttt{0x012220}) verifiers into Z's ZKVM.
P, D, B, C, and Q stop maintaining independent balances; they become
execution state machines holding \emph{claims} over X-locked value and
\emph{settle} their results to a visible X UTXO or a shielded Z note.
We define the object every app-chain references --- an X settlement
\textbf{lock}, not a raw UTXO --- and the five X-level primitives
(\texttt{LockTx}, \texttt{UnlockTx}, \texttt{SettleTx},
\texttt{RequireNFT}, \texttt{VerifyChainCommitment}) with wire shape,
preconditions, postconditions, and conservation effect each. Per the
CTO directive, XSS is built \emph{alongside} the working parallel model,
selectable by flag, so both can be run, tested, compared, and validated
against each other before any migration; we specify the comparison
harness. We give a five-phase migration that never jumps directly, the
safety properties to prove, and the items requiring cryptographer
sign-off. This is a design specification grounded in the current code
with explicit \textbf{[IMPLEMENTED]} / \textbf{[DESIGN-ONLY]} marks; it
does not implement the wire.
\end{abstract}
\tableofcontents
\newpage
\input{sections/01-motivation}
\input{sections/02-model}
\input{sections/02b-access-model}
\input{sections/03-xlock}
\input{sections/03b-xappcommitment}
\input{sections/04-primitives}
\input{sections/05-shielded-bridge}
\input{sections/06-per-chain}
\input{sections/07-coexistence}
\input{sections/08-migration}
\input{sections/09-safety}
\input{sections/09b-validation-properties}
\input{sections/10-open-questions}
\bibliographystyle{plain}
\bibliography{biblio}
\end{document}