Files
papers/lux-economics/sections/10-implementation-considerations.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

57 lines
2.2 KiB
TeX

\section{Implementation Considerations}
%%==========================================================================
\subsection{P-Chain Modifications}
Implementing the full suite of appchain economic mechanisms requires the following P-Chain
changes:
\begin{enumerate}[leftmargin=1.5em]
\item New transaction type \texttt{SetAppchainEconomicsParams} allowing appchain creators
to publish their fee sharing and LWES parameters;
\item Modified \texttt{AddAppchainValidator} transaction to include capacity commitment
$K$ and opt-in reward acceptance;
\item New epoch-based reward distribution logic collecting ASF and distributing to
Primary Network validators;
\item Elastic scaling signals as P-Chain events monitored by the LRP node sidecar.
\end{enumerate}
\subsection{Smart Contract Infrastructure}
C-Chain contracts required:
\begin{enumerate}[leftmargin=1.5em]
\item \texttt{AppchainTokenFactory}: Deploys ERC-20 appchain tokens with LWES emission schedule built in;
\item \texttt{ASFCollector}: Receives security surcharge payments from appchains;
\item \texttt{CrossAppchainMEVOracle}: Monitors Lux Teleport (LP-6332) events and runs MEV auctions;
\item \texttt{ElasticScalingCoordinator}: Issues expansion/ejection signals and manages
validator admission queues.
\end{enumerate}
\subsection{Gas and Overhead Analysis}
The additional P-Chain transactions introduced by appchain economic mechanisms add
approximately 8\% overhead to P-Chain processing. Given P-Chain's current capacity,
this is well within acceptable bounds. C-Chain contract interactions cost:
\begin{table}[H]
\centering
\caption{Appchain Economics Smart Contract Gas Costs}
\label{tab:econ_gas}
\begin{tabular}{lrr}
\toprule
\textbf{Contract Function} & \textbf{Gas Used} & \textbf{Cost at 25 gwei} \\
\midrule
\texttt{deployAppchainToken} & 1,243,000 & \$0.054 (one-time) \\
\texttt{collectASF} (per epoch) & 87,400 & \$0.004 \\
\texttt{distributeASF} (50 validators) & 312,000 & \$0.014 \\
\texttt{runMEVAuction} & 234,100 & \$0.010 \\
\texttt{issueScalingSignal} & 52,300 & \$0.002 \\
\texttt{vestValidatorRewards} & 98,700 & \$0.004 \\
\bottomrule
\end{tabular}
\end{table}
%%==========================================================================