“THORChain: A Decentralised Liquidity Network” is the 2018–2021 whitepaper by the anonymous THORChain Core Team describing a cross-chain decentralized exchange protocol that enables native asset swaps without wrapping: users can swap Bitcoin (native BTC) for Ethereum (native ETH) without bridging through WBTC or any wrapped token. THORChain achieves this using Threshold Signature Schemes (TSS) to manage multi-chain vaults — distributed signing keys that let a supermajority of validators co-sign Bitcoin and Ethereum transactions without any single party controlling the private key.

> Whitepaper: Available at THORChain GitHub Resources.

---

Publication and Context

In 2018–2020, “cross-chain DeFi” meant wrapping native assets into synthetic tokens: WBTC (ERC-20 wrapped Bitcoin) requires trusting BitGo to custody BTC. Bridged assets require trusting bridge validators. Both are centralization points.

THORChain’s differentiator: use TSS to create distributed vaults on each chain — Bitcoin addresses, Ethereum addresses, etc. — where the vault private key is never assembled in one place. A 2/3 supermajority of THORChain validators must collectively sign to move funds in/out of these vaults.

---

Bifrost Protocol: Multi-Chain Observation

THORChain nodes run Bifrost — a chain client daemon that observes multiple chains simultaneously:

• Each THORChain validator runs a BTC full node, ETH full node, BNB full node, etc.
• Bifrost watches incoming deposits to the relevant vault addresses
• When a user sends BTC to the THORChain BTC vault, Bifrost observes the transaction and reports it to the THORChain consensus layer
• Once 2/3+ validators confirm the observation, the deposit is credited on THORChain

Bifrost ensures that THORChain’s AMM pool state reflects native asset balances — every pool is backed by real native assets held in TSS-secured vaults.

---

Continuous Liquidity Pools (CLPs)

THORChain uses a symmetric liquidity pool model based on a constant-product formula — similar to Uniswap but with RUNE as the universal pairing asset:

Every pool is paired with RUNE: BTC/RUNE, ETH/RUNE, etc.

Swap routing: A BTC→ETH swap:

1. BTC → RUNE (via the BTC/RUNE pool)
2. RUNE → ETH (via the ETH/RUNE pool)

RUNE is the settlement asset — it flows through the network on every swap. This requires RUNE to have at least 1:1 value with each pool’s pooled assets (the network’s 3:1 RUNE overcollateralization rule).

Slip-based fees: THORChain uses slip-based fees (not percentage fees) — the fee is proportional to the price impact of the swap. Large swaps relative to pool depth pay more; small swaps pay less. This disincentivizes large single-block manipulations.

---

TSS and Vault Security

Threshold Signature Scheme (TSS): THORChain uses a GG-20 threshold ECDSA scheme (similar to Axelar) where:

• Validators collectively hold key shares for each chain vault
• A 2/3+ threshold must participate in a signing round to authorize a vault transaction
• Key generation happens via a distributed key generation (DKG) ceremony — the private key is never in any single location

Churning: Vault keys are rotated periodically (every ~21 days). At each churn, the top-N validators by bond (staked RUNE) are retained; lower-ranked validators exit. New key generation ceremonies produce new vault addresses. Funds are moved from old vaults to new vaults by the exiting set signing the final transactions.

---

RUNE Token Mechanics

RUNE serves four functions:

1. Settlement asset: All pool pairs are RUNE-denominated
2. Governance staking: Validators bond RUNE (minimum 1M RUNE) for network security
3. Fee payment: Swap fees are paid in RUNE
4. Insurance: If a vault is hacked, the RUNE bonded by misbehaving validators is slashed to compensate liquidity providers

1:3 bond/liquidity ratio: For every 1 RUNE bonded by validators, the protocol requires 3 RUNE worth of pooled assets. This ensures that attacks (which would result in slashing bonded RUNE) cannot be economically profitable versus the potential vault theft.

---

Reality Check

THORChain’s native asset swap design is unique and genuinely valuable — the ability to swap BTC for ETH without custodial intermediaries is a meaningful DeFi capability. In production (2021+), THORChain processed billions in native cross-chain volume.

Caveats:

• Three major hacks (2021): THORChain suffered three separate exploits in 2021 totaling ~$13M. All were smart contract/Bifrost implementation bugs, not TSS key compromises. The team halted and patched the network each time.
• Complexity risk: THORChain runs full nodes for 9+ chains simultaneously. Bugs in any chain client or the Bifrost observer can create systemic risk.
• RUNE centralization: Core development is by Thorchain’s core team (pseudonymous); significant RUNE token concentration among early investors.
• Lending protocol risk (2023): THORChain’s native lending protocol (no collateral liquidation design) created systemic risk flagged by the community.

---

Legacy

THORChain demonstrated in production that native cross-chain asset swaps (not wrapped) were technically achievable using TSS vaults. The Bifrost multi-chain observer pattern influenced later cross-chain protocol designs. The slip-based fee model is used by several AMMs inspired by THORChain.

---

Related Terms

• Cross-Chain Bridge
• Threshold Signature
• Automated Market Maker
• Axelar Whitepaper

---

Research

• THORChain Core Team. (2020). THORChain: A Decentralised Liquidity Network. THORChain Resources.

— Primary whitepaper. Section 4 covers CLPs; Section 5 describes vault management; Section 6 details the RUNE economics.

• Gennaro, R., & Goldfeder, S. (2020). One Round Threshold ECDSA with Identifiable Aborts. IACR ePrint 2020/540.

— GG-20 threshold ECDSA protocol; the TSS scheme used by THORChain for multi-chain vault signing.

• Adams, H., Zinsmeister, N., & Robin, D. (2020). Uniswap v2 Core. Uniswap.

— Uniswap v2’s constant-product AMM; THORChain’s CLP model uses a similar constant-product formula adapted for single-asset pool pairing via RUNE.