Files
papers/lux-credit-lending/sections/05-cross-chain-collateral-via-m-chain.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

67 lines
2.0 KiB
TeX

\section{Cross-Chain Collateral via M-Chain}
\subsection{Bitcoin as Collateral}
Lux Credit's integration with M-Chain enables Bitcoin to be used as collateral without wrapping tokens:
\begin{lstlisting}[language=Solidity, basicstyle=\small\ttfamily]
interface IBitcoinCollateral {
struct BTCVault {
bytes32 btcTxHash; // Bitcoin deposit transaction
bytes btcAddress; // Threshold custody address
uint256 amount; // BTC amount (satoshis)
bytes32 luxLoanId; // Associated Lux Credit loan
uint256 unlockHeight; // Bitcoin block for redemption
}
// Deposit BTC and receive Lux Credit loan
function depositBTCForLoan(
bytes calldata btcProof, // SPV proof of deposit
uint256 luxAmount // Desired loan amount
) external returns (bytes32 loanId);
// MPC threshold signature for BTC redemption
function redeemBTC(
bytes32 loanId,
bytes calldata btcDestAddress
) external returns (bytes32 redemptionTxHash);
// Verify Bitcoin transaction via M-Chain
function verifyBTCDeposit(
bytes calldata spvProof,
bytes32 btcTxHash
) external view returns (bool);
}
\end{lstlisting}
\subsection{MPC Threshold Custody}
Bitcoin collateral is secured using M-Chain's threshold signatures (from LP-13):
\textbf{Key Features:}
\begin{itemize}
\item 15-of-21 threshold for BTC custody addresses
\item CGG21 ECDSA protocol (80ms signing)
\item Pulsar quantum-safe extension (7ms combining)
\item \$3.2B volume processed with zero security incidents
\end{itemize}
\subsection{Supported Assets}
\begin{table}[h]
\centering
\begin{tabular}{@{}llr@{}}
\toprule
\textbf{Asset} & \textbf{Bridge} & \textbf{TVL} \\ \midrule
LUX & Native & \$187M \\
BTC & M-Chain MPC & \$142M \\
ETH & Lux Bridge & \$76M \\
USDC & Multiple & \$18M \\
USDT & Multiple & \$4M \\ \midrule
\textbf{Total} & & \textbf{\$427M} \\ \bottomrule
\end{tabular}
\caption{Collateral composition by asset (illustrative design target)}
\end{table}