The 6 Bitcoin L2 architectures explained
Two parties open a bilateral channel funded by an L1 transaction. They settle thousands of transactions off-chain; only open + close hit L1. Trust: counterparty within an unsettled channel only. Scaling: ~10,000+ transactions per second across the network.
A 15-member federation controls peg-in / peg-out of BTC. Liquid offers 2-minute settlement, confidential transactions (hidden amounts), and asset issuance. Used by exchanges (Bitfinex, Bullish) for fast cross-exchange BTC moves.
A separate chain whose consensus references Bitcoin (Stacks PoX) or merge-mines with Bitcoin (Rootstock). Stacks adds sBTC for self-custodial BTC-equivalent on its chain. Rootstock supports EVM smart contracts.
EVM-compatible chains using Bitcoin DA + optimistic challenges. Fast (instant block time), full smart contracts, but rely on multisig escape hatch for trust-minimisation in 2026. Aiming for true BitVM-secured rollups by 2027.
First true zero-knowledge rollup using Bitcoin for DA + BitVM verification. Theoretically Bitcoin-equivalent security. Mainnet 2025; significant adoption ramp in 2026.
Newer architectures avoiding Lightning's liquidity-management overhead. Ark uses VTXOs in shared UTXOs. Spark provides asset-issuance + payments. Trust-minimised but still maturing.
Every Bitcoin L2 worth knowing in 2026
| L2 | Architecture | Trust model | TVL (May 2026) | Best use case | Asian adoption |
|---|---|---|---|---|---|
| Lightning Network | Payment channels | Channel counterparty + LSP | ~$2.1B locked | Payments, remittance, zaps | ★★★★★ (PH leads) |
| Stacks (with sBTC) | Anchored sidechain | Signer set + Bitcoin ordering | $1.4B | Self-custodial DeFi, lending | ★★★★ (SG, HK, JP) |
| Liquid Network | Federation | 15-member federation | ~$340M | Institutional settlement | ★★★ (HK exchanges) |
| Rootstock (RBTC) | Merge-mined sidechain | Federation + merge-mining | $280M | EVM smart contracts | ★★★ (PH, latam-pivot) |
| BOB (Build on Bitcoin) | Hybrid rollup | Multisig + BitVM (2026) | $820M | EVM + BTC liquidity | ★★★ (SG, HK) |
| Bitlayer | Optimistic rollup | Multisig escape hatch | $640M | EVM + BTC liquidity | ★★★ (HK, JP, KR) |
| Merlin Chain | Optimistic rollup | Multisig escape hatch | $540M | BRC-20 + Ordinals trading | ★★ (CN-leaning) |
| Citrea | ZK rollup (BitVM) | BitVM + Bitcoin DA | $160M (early) | True Bitcoin-equivalent EVM | ★★ (growing in 2026) |
| Ark Protocol | Channel-free | Operator (limited window) | $60M (early) | Payments without LN complexity | ★★ (devs in SG, JP) |
| Spark | Statechain-style | SE operators + multi-sig | $45M (early) | Asset issuance + payments | ★ (early) |
| RGB Protocol | Client-side validation | Bitcoin-equivalent + DLC | n/a (no TVL model) | Asset issuance, privacy | ★★ (devs) |
| Fedimint | Federated mint | Guardian quorum | $28M | Community banking, Cashu-style privacy | ★★★ (PH, BH) |
| Taproot Assets | Anchored to L1 | Bitcoin-equivalent | n/a (asset layer) | USDT-on-Lightning, RWA tokens | ★★ (rollout 2026-27) |
Picking an L2 by your Asian use case
Lightning via Strike (sender) + Coins.ph (receiver). Settles in ~3 seconds, fees <$0.01. The remittance use case where Lightning has clearly won.
Stacks + sBTC. Self-custodial, on-chain transparent, yields 4-9% via Bitflow/ALEX. Or Babylon for native BTC staking without bridging.
Liquid Network. 2-minute settlement, confidential amounts, federation includes major Asian exchanges. Used daily by HK trading firms.
BOB or Bitlayer. EVM-compatible, growing BTC TVL, decent dev tooling. Use BOB for higher liquidity; Bitlayer for lower fees.
Taproot Assets via Lightning Labs ecosystem. Watch 2026-27 rollout — USDT-on-LN will likely dominate Asian retail stablecoin movement once available.
Fedimint or Cashu. Federation/mint-based; Chaumian privacy. Best for small amounts. Combine with Lightning for liquidity bridge.
Trust model honesty check
⚠️ "Bitcoin L2" is a marketed term, not a strict spec
Strict L2 means the chain inherits Bitcoin's full security model — only Bitcoin L1 validators can finalize state. By this strict definition, only Lightning, Ark, and emerging BitVM-secured rollups (Citrea, future BOB) qualify in 2026.
Stacks, Rootstock, BOB (current), Bitlayer, Merlin, Liquid are sidechains, federations, or anchored chains — they're useful, but they introduce trust assumptions beyond Bitcoin L1. Use them for what they're good at; don't assume Bitcoin-equivalent security.
- Lightning: trust your channel counterparty + watchtower (or your own monitoring)
- Stacks: trust the sBTC signer set + Bitcoin ordering
- Liquid: trust the 15-member federation
- BOB / Bitlayer / Merlin: trust the multisig escape hatch and rollup operator
- Citrea: trust BitVM verification cryptography
- Ark: trust the operator within a limited interactive window
FAQ
Why do so many L2s exist if Lightning is the answer?
Lightning handles payments efficiently but doesn't support arbitrary smart contracts. Stacks, Rootstock, BOB, Bitlayer fill the smart-contract / DeFi gap. Liquid serves institutional settlement. Each L2 solves a specific problem Lightning doesn't address. They're complementary, not competitive.
Will Bitcoin L1 fees stay low because of L2s?
Probably not. As Bitcoin's halving subsidy declines, miners need transaction fees to maintain security. Ordinals + Runes already demonstrate that demand for L1 block space will keep fees meaningful. L2s reduce per-user fees by aggregating — but L1 fees themselves will rise. Use Lightning + L2s for everyday spending; reserve L1 for settlement.
Are L2 tokens (STX, RBTC, etc.) good investments?
Different question from L2 utility. STX has appreciated alongside Stacks adoption. RBTC tracks BTC value. EVM-rollup tokens (BTLR, MERL, BOB) trade speculatively. Treat L2 tokens as separate from the L2's actual utility — they're priced on speculation about future fees and ecosystem growth.
What happens if a federation L2 like Liquid fails?
Users would need to coordinate to recover funds via the federation's emergency procedure. In Liquid's case, 11 of 15 federation members must cooperate to peg-out L-BTC back to BTC. If the federation deadlocks or colludes, users may have limited recourse. Don't keep large balances on federations long-term.
Should I bridge my BTC to multiple L2s?
Only if you have specific use cases on each. Bridging carries risk per L2; multiplying L2s multiplies exposure. Most Asian users do well with: 80% L1 cold storage, 15% Lightning for spending, 5% on Stacks/L2 for DeFi exploration.