Summary: Serai is worth cataloging not as just another cross-chain DEX, but as a chain whose own validator sets form threshold multisig wallets on external networks and expose those foreign coins to applications running on Serai itself. The project’s docs and spec describe a clean architectural split between Serai consensus, per-network validator-set custody, offchain processor/coordinator services, and the AMM DEX that sits on top of the resulting asset representations. That decomposition makes Serai analytically useful because it shows a very different answer to the cross-chain exchange problem than atomic-swap systems: instead of only helping two peers coordinate a swap, Serai turns validator-governed custody plus economic stake bounds into a reusable execution layer for Bitcoin, Ethereum, DAI, and Monero.
What it does:
Runs a Substrate-based chain whose validators can manage assets on connected external networks
Forms per-network t-of-n multisigs from validator sets so Serai can custody and move external assets under protocol control
Uses processors and coordinators to scan external chains, communicate among validators, and confirm multisig creation and network actions on Serai
Mints Serai-side representations of external assets and uses them inside Serai’s applications, especially the Serai DEX AMM
Enforces an explicit economic-security bound where validator-set multisigs are only considered secure up to a fraction of the stake allocated to that set
Implements network-specific operational logic, including Monero address / instruction handling and UTXO-management logic for outbound fulfillment and fee amortization
Key claims:
The core mechanism is not merely cross-chain swapping; it is validator-operated foreign-coin control. Serai’s own spec says validators form multisig wallets for connected networks and make those coins available to applications built on Serai.
The validator-set economic bound is the sharpest reusable insight. Serai’s protocol spec says each validator set is expected to form a t-of-n multisig and that the multisig is only secure up to 33% of the validator set’s allocated stake, after which it must reject newly added coins. That makes custody capacity an explicit protocol-level risk limit rather than an implicit trust assumption.
Serai’s processors and coordinators are not implementation detail fluff. They are the service layer that actually creates multisigs, monitors external networks, and coordinates actions before results are confirmed onchain.
The UTXO-management spec is especially worth preserving because it exposes the hidden operating system behind a validator-custodied bridge/exchange. Serai explicitly models fee amortization, output-creation bottlenecks, branch-output trees for logarithmic burn fulfillment, and anti-abuse flat fees for forced input aggregation.
The Monero integration docs add another distinct comparison point. Serai adapts Monero’s address and instruction surfaces rather than flattening Monero into a generic supported asset, which helps show what it means to custody and route a privacy coin inside a validator-governed execution layer.
Serai therefore belongs in the active corpus because it gives the exchange/interoperability cluster a strong threshold-custody baseline to compare against atomic-swap DEXs, bridge-minimized exchange systems, and validator-set Bitcoin / Monero infrastructures.
Whitepaper: No canonical standalone Serai whitepaper surfaced in this pass. The strongest primary materials were the official docs, repository README, and protocol/spec documents collected in ../whitepapers/serai-primary-sources-2026-05-14.md.