mirror of
https://github.com/lux-apps/papers.git
synced 2026-10-30 18:15:21 +00:00
zeekayandHanzo Dev
178febad68
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]>
44 lines
1.6 KiB
TeX
44 lines
1.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 "F-Chain MPC" / "F-Chain threshold governance" /
|
|
%% "F-Chain TFHE" / "F-Chain custody", read as M-Chain (MPC) or F-Chain (FHE).
|
|
%% ===================================================================
|
|
|
|
\section{EVM Integration}
|
|
|
|
|
|
FHE operations are exposed as EVM precompiles on Lux C-Chain:
|
|
|
|
\begin{table}[h]
|
|
\centering
|
|
\small
|
|
\begin{tabular}{@{}ll@{}}
|
|
\toprule
|
|
\textbf{Precompile} & \textbf{FHE Operation} \\
|
|
\midrule
|
|
FHEAdd, FHESub, FHEMul & Encrypted integer arithmetic \\
|
|
FHEEq, FHELt, FHEGt, FHELe, FHEGe & Encrypted comparison \\
|
|
FHEAnd, FHEOr, FHEXor, FHENot & Encrypted bitwise \\
|
|
TrivialEncrypt & Plaintext $\to$ ciphertext (public value) \\
|
|
Decrypt, Reencrypt & Async decryption via F-Chain \\
|
|
\bottomrule
|
|
\end{tabular}
|
|
\caption{FHE EVM precompiles at addresses \texttt{0x0200...0080}--\texttt{0x0200...0083}.}
|
|
\label{tab:precompiles}
|
|
\end{table}
|
|
|
|
Solidity developers interact via the \texttt{@luxfi/contracts} library:
|
|
|
|
\begin{lstlisting}[language=Java]
|
|
import "@luxfi/contracts/FHE.sol";
|
|
euint32 a = FHE.asEuint32(encrypted_input);
|
|
euint32 b = FHE.add(a, FHE.asEuint32(10));
|
|
\end{lstlisting}
|
|
|