Files
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

55 lines
2.6 KiB
TeX

%% ===================================================================
%% LP-134 canonical naming (2025-12-15):
%% Per LP-134 (Lux Chain Topology), T-Chain has been split into:
%% M-Chain — MPC ceremonies for bridge custody of EXTERNAL wallets
%% (CGGMP21, FROST, Pulsar-general)
%% F-Chain — FHE compute + TFHE bootstrap-key generation (encrypted EVM)
%% T-Chain is REMOVED entirely; teleport is B-Chain (bridgevm, LP-6000). No teleportvm.
%% Where this paper says "T-Chain MPC" / "T-Chain threshold governance" /
%% "T-Chain TFHE" / "T-Chain custody", read as M-Chain (MPC) or F-Chain (FHE).
%% ===================================================================
\section{Chain Support}
\subsection{Native Chain Types}
The explorer natively indexes nine Lux chain types:
\begin{table}[H]
\centering
\begin{tabularx}{\textwidth}{llX}
\toprule
\textbf{Chain} & \textbf{Consensus} & \textbf{Indexed Data} \\
\midrule
C-Chain (EVM) & Linear & Blocks, transactions (type 0--3), internal traces, tokens (ERC-20/721/1155), smart contracts, DeFi protocols, NFT marketplaces \\
P-Chain & Linear & Validators, delegators, staking rewards, L1 chain management \\
X-Chain & DAG & UTXOs, atomic swaps, multi-asset transfers, vertices, edges \\
D-Chain (DEX) & EVM & CLOB orderbook, perpetuals, AMM pools, liquidations \\
A-Chain (AI) & DAG & Attestations, model registration, inference results \\
B-Chain (Bridge) & DAG & Cross-chain transfers, proof validation, MPC custody \\
Q-Chain (PQ) & DAG & Post-quantum finality proofs, lattice signatures \\
M-Chain (MPC) & DAG & Threshold signing ceremonies (CGGMP21 / FROST / Corona-gen), key shares, bridge custody — per LP-134 \\
F-Chain (FHE) & DAG & TFHE keygen, encrypted-EVM compute, decryption proofs — per LP-134 \\
Z-Chain (ZK) & DAG & Zero-knowledge proofs, shielded transfers, nullifier tracking \\
K-Chain (KMS) & DAG & PQ key material, certificate lifecycle, HSM bridge operations \\
\bottomrule
\end{tabularx}
\caption{Native chain indexing capabilities}
\end{table}
\subsection{External Chain Support}
For bridge, MPC, and threshold operations, the explorer indexes 100+ external chains:
\begin{itemize}
\item \textbf{EVM}: Ethereum, Polygon, Arbitrum, Optimism, Base, BSC, Avalanche, +30 more
\item \textbf{Solana}: Mainnet, Devnet (Metaplex, Magic Eden, Raydium, Jupiter protocols)
\item \textbf{Bitcoin}: Ordinals, Runes, BRC-20, Stamps, Atomicals
\item \textbf{Cosmos}: Hub, Osmosis, Injective, dYdX, Celestia, Sei
\item \textbf{Move}: Aptos, Sui
\item \textbf{Other}: NEAR, Tron, TON, Substrate/Polkadot
\end{itemize}