Files
zeekay abf99d05fc papers: reorganize into per-paper dirs, add Antje Worring as co-author
Restructured from flat .tex/.pdf files into per-paper subdirectories.
Added Antje Worring as co-author on all papers.
Synced PDFs to pdfs/ for download site.
2026-04-18 21:50:07 -07:00

63 lines
2.5 KiB
TeX

\section{Multi-Token Support}
\label{sec:multitoken}
\subsection{Token Registry}
LITP maintains a token registry mapping source-chain tokens to their destination-chain representations:
\begin{definition}[Token Registry Entry]
\begin{equation}
\mathsf{Registry}(\mathsf{srcChain}, \mathsf{tokenAddr}) = (\mathsf{wrappedAddr}, \mathsf{decimals}, \mathsf{symbol}, \mathsf{paused})
\end{equation}
The registry is governance-managed, with token additions requiring DAO approval.
\end{definition}
\begin{table}[H]
\centering
\caption{Supported token types and transfer patterns.}
\label{tab:tokentypes}
\begin{tabular}{llll}
\toprule
\textbf{Token Type} & \textbf{Standard} & \textbf{Pattern} & \textbf{Notes} \\
\midrule
Native coin & ETH, LUX & Lock-and-mint & Bridge vault holds native \\
Fungible token & ERC-20 & Lock-and-mint & Approval required \\
Wrapped token & wETH, wBTC & Lock-and-mint & Double-wrapped \\
Stablecoin & USDC, USDT & Lock-and-mint & Special rate handling \\
LST & sLUX, stETH & Lock-and-mint & Rebasing awareness \\
\bottomrule
\end{tabular}
\end{table}
\subsection{Canonical Bridge Selection}
For each token, exactly one bridge serves as the ``canonical'' bridge to prevent fragmentation:
\begin{definition}[Canonical Bridge]
The canonical bridge for token $T$ on chain $C$ is the bridge whose wrapped token is designated as the standard representation of $T$ on $C$. DeFi protocols integrate against canonical wrapped tokens only.
\end{definition}
\begin{proposition}[Liquidity Concentration]
Canonical bridge designation concentrates liquidity, reducing slippage for users. Without canonicality, $k$ bridges each hold $1/k$ of the available liquidity, increasing price impact by factor $k$.
\end{proposition}
\subsection{ERC-20 Batch Transfers}
For efficiency, LITP supports batching multiple token transfers in a single warp message:
\begin{algorithm}[H]
\caption{Batch Token Transfer}
\label{alg:batch}
\begin{algorithmic}[1]
\Require $m$ transfers $\{(\mathsf{token}_j, \mathsf{amount}_j, \mathsf{recipient}_j)\}_{j=1}^m$
\State Lock all tokens on source chain
\State Encode batch as single warp payload
\State Single BLS aggregate proof covers all transfers
\State Destination processes batch atomically (all-or-nothing)
\State Mint all wrapped tokens in one transaction
\end{algorithmic}
\end{algorithm}
Batching reduces per-transfer cost: a batch of 20 transfers costs approximately $100{,}000 + 20 \times 30{,}000 = 700{,}000$ gas, versus $20 \times 100{,}000 = 2{,}000{,}000$ gas for individual transfers.