Files
papers/lux-gchain-graphql/sections/05-horizontal-scaling-architecture.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

75 lines
2.0 KiB
TeX

\section{Horizontal Scaling Architecture}
\subsection{Node Types}
G-Chain supports three node deployment models:
\begin{enumerate}
\item \textbf{Full Sync Nodes}: Complete network state across all chains
\item \textbf{Chain Sync Nodes}: Specific chains only (e.g., D-Chain + C-Chain for DEX matching and settlement)
\item \textbf{App Sync Nodes}: Application-specific subgraphs (e.g., DeFi protocols only)
\end{enumerate}
\begin{algorithm}[H]
\caption{Selective Synchronization}
\begin{algorithmic}[1]
\Function{SyncNode}{$config$}
\State $syncMode \gets config.syncMode$
\State $chainFilter \gets config.chainFilter$
\If{$syncMode = \text{FULL}$}
\State Subscribe to all chain events
\ElsIf{$syncMode = \text{CHAIN}$}
\For{each $chain$ in $chainFilter$}
\State Subscribe to $chain$ events
\EndFor
\ElsIf{$syncMode = \text{APP}$}
\State $subgraph \gets$ Load application subgraph definition
\State Subscribe to events matching $subgraph$ filters
\EndIf
\State Process incoming blocks and update GraphDB
\State Commit Verkle trie state
\State Publish state root to consensus
\EndFunction
\end{algorithmic}
\end{algorithm}
\subsection{Custom Indexing}
Applications can define custom indexes for optimized queries:
\begin{lstlisting}[language=YAML, basicstyle=\small\ttfamily]
# config.yaml
customIndexes:
- name: "token_transfers"
chains: [C, X]
nodeType: "Transfer"
fields:
- name: "from"
type: "address"
indexed: true
- name: "to"
type: "address"
indexed: true
- name: "amount"
type: "uint256"
indexed: false
- name: "defi_positions"
chains: [C]
nodeType: "Position"
fields:
- name: "user"
type: "address"
indexed: true
- name: "protocol"
type: "string"
indexed: true
- name: "collateral"
type: "uint256"
indexed: false
\end{lstlisting}