Files
papers/lux-teleport-architecture/lux-teleport-architecture.tex
zeekay f4ee7a0525 Publish under the org, not a person
Bylines, paper authorship, correspondence addresses and the founder blurb under
each post named an individual. They name the organisation that published the
work instead: the brand on posts and pages, the research byline on papers, and
research@ in place of a personal address. Both are what these repositories
already used elsewhere — nothing new was coined.

Co-authors are untouched. Where a paper named someone else alongside, they stay
named; only the one byline changed. Bibliography entries, running heads,
PDF metadata and affiliations move with it, so a citation still resolves to
whoever the cited paper names.

Sample and fixture data uses the placeholder name these tests already use
elsewhere, so no assertion changed meaning.
2026-09-01 08:58:10 -07:00

79 lines
3.8 KiB
TeX

\documentclass[11pt]{article}
\usepackage{../shared/luxcover}
\usepackage{amsmath, amssymb, amsthm}
\usepackage{mathtools}
\usepackage{graphicx}
\usepackage{booktabs}
\usepackage{hyperref}
\usepackage{enumitem}
\usepackage{algorithm}
\usepackage{algpseudocode}
\usepackage{xcolor}
\usepackage{listings}
\usepackage{tikz}
\usepackage{float}
\usepackage{array}
\usepackage{multirow}
\input{../shared/lstlang}
\usetikzlibrary{arrows.meta,positioning,shapes.geometric,fit,calc}
\hypersetup{colorlinks=true,linkcolor=black,citecolor=blue,urlcolor=blue}
\lstset{
basicstyle=\ttfamily\scriptsize,
breaklines=true,
frame=single,
numbers=left,
numberstyle=\tiny\color{gray},
keywordstyle=\color{blue!70!black}\bfseries,
commentstyle=\color{green!50!black}\itshape,
stringstyle=\color{red!60!black},
showstringspaces=false,
}
\newtheorem{theorem}{Theorem}
\newtheorem{lemma}[theorem]{Lemma}
\newtheorem{proposition}[theorem]{Proposition}
\newtheorem{corollary}[theorem]{Corollary}
\newtheorem{definition}{Definition}
\newtheorem{property}{Property}
\newtheorem{invariant}{Invariant}
\title{Teleport Universal Bridge Architecture:\\Frozen Wire Format, Pluggable Chain Adapters,\\and Multi-Tenant Deployment}
\author{
Lux Research\thanks{Corresponding author: [email protected]}
\quad
Vishnu Seesahai\\
\textit{Lux Industries, Inc.}\\
\texttt{[email protected]}
}
\date{2025}
\begin{document}
\luxcoverpage
\begin{abstract}
We describe the engineering architecture of Lux Teleport, a universal cross-chain bridge serving 270+ chains through a single protocol binary. The design separates concerns into four layers: (1)~a \emph{frozen wire protocol} comprising four canonical proof tags---\texttt{DEPOSIT}, \texttt{YIELD}, \texttt{BACKING}, \texttt{RELEASE}---encoded as \texttt{bytes32}-tagged \texttt{abi.encode} payloads with MPC-signed proofs, per-\texttt{srcChainId} replay protection, and monotonic backing attestations with configurable staleness windows; (2)~a \emph{chain-agnostic Teleporter contract} that implements the wire protocol against an abstract chain adapter interface, enabling a single audited contract to serve all EVM deployments; (3)~a \emph{pluggable chain adapter} layer supporting four support classes---Lux-native (Warp, no MPC hop), external EVM (\texttt{TeleportVault} template), Bitcoin-family script chains (watcher-first: OP\_NET, Litecoin, Dogecoin), and non-EVM account-model chains (Solana Ed25519, TON Ed25519, XRP secp256k1); and (4)~a \emph{multi-tenant architecture} where hostname-based routing, per-tenant manifests, and shared MPC infrastructure enable white-label bridge deployments from a single binary. We specify the threshold signing interface unifying CGGMP21 (ECDSA/secp256k1 for EVM), FROST (Schnorr for Bitcoin Taproot), and BLS (Lux Warp internal) under \texttt{github.com/luxfi/crypto/threshold}. We formalize the security model including per-chain confirmation depths, backing attestation monotonicity, sequential withdraw nonces, peg oracle auto-pause thresholds, and hot wallet / MPC key separation. We describe the yield composition pipeline through which bridged assets earn layered returns via Babylon staking, D-Chain LP, and bridge fees through the xLUX instrument. Finally, we specify the 6-artifact conformance testing framework that gates chain onboarding through CI/CD.
\end{abstract}
\tableofcontents
%% =========================================================================
\input{sections/01-introduction}
\input{sections/02-wire-protocol}
\input{sections/03-teleporter-contract}
\input{sections/04-chain-support-classes}
\input{sections/05-threshold-signing-architecture}
\input{sections/06-security-model}
\input{sections/07-multi-tenant-architecture}
\input{sections/08-yield-composition}
\input{sections/09-conformance-testing}
\input{sections/10-related-work}
\input{sections/99-conclusion}
\end{document}