Bitcoin’s base layer is deliberately limited: no Turing-complete scripting, ~7 transactions per second, and ~10-minute confirmation times. These constraints maximize security and decentralization but also limit expressibility. Bitcoin Layer 2s (L2s) attempt to extend Bitcoin’s utility by adding speed, programmability, or new asset types — while maintaining some relationship with Bitcoin’s security. The approaches differ dramatically: Lightning Network uses payment channels; Rootstock uses merged mining; Stacks uses a PoS-like system; and a new generation of ZK-based L2s uses BitVM to enable more trustless verification. Bitcoin L2s are distinct from Ethereum L2s — Bitcoin’s scripting limitations make it far harder to build a trustless bridge, creating significant security tradeoffs.
Why Bitcoin L2 Is Hard
The core challenge: Bitcoin can’t verify arbitrary computations. Ethereum L2s can use smart contracts to verify ZK proofs on-chain, creating trustless bridges to L2. Bitcoin can’t.
Bitcoin scripting limitations:
- No loops (no Turing completeness)
- No state outside UTXOs
- Limited data storage (OP_RETURN = 80 bytes traditionally)
- No native ability to verify ZK proofs
This means every Bitcoin L2 involves some trust assumption not present in Ethereum L2s. The question is: how much trust, and in what?
Lightning Network
The oldest and most decentralized Bitcoin L2.
Mechanism: Payment channels created by locking Bitcoin in a 2-of-2 multisig on Bitcoin L1. Payments route through a network of channels off-chain. Only channel opens, closes, and disputes go on-chain.
Trust model: Trustless — both parties hold signed transactions that can be broadcast anytime; no counterparty can steal funds if you monitor the channel (or use a watchtower service).
Capabilities: Payments only. No smart contracts. No tokens.
Status (2025): ~5,000 BTC in public channels; millions of daily transactions; major integrations (Cash App, Strike, Wallet of Satoshi). Growing but not dominant for large payments.
Limitations: Requires active channel management; routing failures on large payments; liquidity fragmentation.
Rootstock (RSK)
A Bitcoin-secured smart contract platform that’s been running since 2018.
Mechanism: Merged mining — Bitcoin miners can simultaneously mine BTC and RSK blocks with no extra work. RSK’s native token RBTC is pegged to Bitcoin via a 2-of-3 multisig federation bridge called “PowPeg.”
Trust model: Partially trusted — the bridge requires trusting the PowPeg federation signers (10+ organizations including institutional actors). Not trustless.
Capabilities: EVM-compatible smart contracts. Allows DeFi, stablecoins, DEXs on Bitcoin.
Status: Small but persistent user base. RSK DeFi TVL primarily in stablecoin lending and DEX. RSK developed Sovryn (DeFi) and DOC (Dollar on Chain stablecoin).
Stacks
The most prominent Bitcoin smart contract platform by developer activity and TVL.
Mechanism: Proof of Transfer (PoX) — Stacks miners burn BTC to mine STX blocks. STX holders can “stack” (lock) STX to earn BTC rewards. Stacks transactions ultimately settle on Bitcoin in 100-block epochs.
Trust model: The bridge between Stacks and Bitcoin is centralized (sBTC multisig with ~15 signatories in v1). Stacks has significant Bitcoin correlation without full Bitcoin security.
sBTC: Stacks’ synthetic Bitcoin peg. Users lock BTC, receive sBTC on Stacks, use in Stacks DeFi. The peg relies on signatories; not trustless.
Capabilities: Clarity smart contracts (intentionally non-Turing-complete!); can read Bitcoin state, enabling Bitcoin-triggered contracts.
Notable usage: Ordinals integration (inscriptions); NFTs; Alex DEX; orange (BRC-20 tokens via Stacks bridge)
STX token: Used for gas, stacking rewards, governance. Market cap and TVL in top 10 BTC L2s by size.
Merlin Chain
A ZK-rollup for Bitcoin that’s become one of the largest by TVL.
Mechanism: Validity proofs using ZK-SNARKs that can be verified on Bitcoin’s mainnet (using Bitcoin’s existing STARK verification capabilities, though very limited). Uses a combination of off-chain committee and BTC commitments.
Trust model: In practice, semi-trusted — uses an off-chain committee for data availability and a ZK prover for state verification. Less decentralized than Ethereum L2s.
Capabilities: EVM-compatible. Access to Bitcoin assets (BTC, BRC-20, Runes) in DeFi.
TVL peak: ~$3.5B in early 2024 during Bitcoin L2 speculation; declined significantly
Status: Active but concerns about trust model rigor vs. marketing claims (“ZK rollup on Bitcoin” implies more trustlessness than the implementation provides)
BitVM
The theoretical foundation for more trustless Bitcoin L2s.
Published: October 2023 by Robin Linus (ZeroSync)
The insight: Bitcoin can verify arbitrary computations through a challenge-response game using existing Bitcoin scripting (CHECKSIG, bit commitments):
- A prover commits to a computation result on Bitcoin
- A verifier can challenge specific steps
- Even with only 2 parties (1-of-2 honesty), fraud can be detected
Current limitations:
- Only 2-party protocols so far (1 prover + 1 verifier)
- Extremely large scripts (hundreds of MB for complex computations)
- Not production-ready for general use
BitVM2 (2024): Extension allowing n-of-n multisig for multi-party validity proofs — enabling more realistic bridge designs without trusted federation.
Significance: BitVM is the path toward genuinely trustless Bitcoin L2s. Multiple teams (ZeroSync, Citrea, BitVM-Bridge) are building with BitVM assumptions.
BEVM and Other EVM-Compatible BTC L2s
Several chains launched in early 2024 claiming to be “Bitcoin L2s”:
- BEVM: EVM chain with BTC as gas; Bitcoin PoW merge-mined; native BTC bridge
- B² Network: ZK rollup claiming Bitcoin anchoring
- BounceBit: BTC staking chain with PoS consensus
Caution: Many “Bitcoin L2s” are primarily marketing. The trustlessness of the Bitcoin bridge (how funds move between Bitcoin mainnet and the L2) is the key question. Most current implementations use trusted multisig bridges — similar to Ethereum’s older cross-chain bridges before ZK bridges existed.
Runes and the Native Asset Layer
Bitcoin Runes (April 2024): A new native token standard on Bitcoin by Casey Rodarmor (Ordinals creator)
- Uses OP_RETURN to encode token metadata in Bitcoin transactions
- Fungible tokens (like BRC-20 but more efficient)
- No L2 needed — tokens live on Bitcoin L1
- Launched at the April 2024 halving; massive immediate adoption (60%+ of Bitcoin transactions in first week)
BRC-20: Older fungible token standard using Ordinals (JSON inscriptions in OP_RETURN) — less efficient than Runes but established ecosystem: ORDI, SATS tokens
Relevance to L2s: As native Bitcoin assets proliferate (Runes, BRC-20, Ordinals NFTs), the demand for L2 smart contracts to use these assets in DeFi grows — Merlin Chain and others specifically market their BMC-20/Runes DeFi capabilities.
How to Use Bitcoin L2s
Lightning (payments):
- Download Strike, Wallet of Satoshi, or Phoenix wallet
- Fund with BTC (opens a Lightning channel)
- Send/receive instantly and cheaply
Stacks (DeFi):
- Get STX from
- Connect Leather or Xverse wallet
- Use Alex DEX for trading; Stack STX for BTC rewards
Rootstock (DeFi):
- Bridge BTC to RBTC via powpeg.rootstock.io
- Connect MetaMask to Rootstock RPC
- Use Sovryn or other RSK DeFi protocols
Secure all Bitcoin and L2 keys with a hardware wallet: .
Social Media Sentiment
Bitcoin L2s are a polarizing topic. Bitcoin maximalists view all L2s except Lightning as compromised, citing federation bridges and trust assumptions that don’t match the “trustless Bitcoin” marketing. Ethereum-native DeFi developers are skeptical of claims like “ZK rollup on Bitcoin” that don’t yet match Ethereum ZK rollup rigor. The 2024 Bitcoin L2 TVL boom was partially driven by speculation (incentivized deposits for future token airdrops) rather than genuine DeFi usage. That said, BitVM’s theoretical advances are genuine, and Lightning’s real-world usage metrics (Cash App, Strike payments) represent one of crypto’s few examples of mainstream non-speculative adoption. The honest answer is that “Bitcoin L2” means very different things — Lightning (robust, live) and early ZK attempts (promising but not ready) shouldn’t be conflated.
Research
Poon, J. & Dryja, T. (2016). The Bitcoin Lightning Network: Scalable Off-Chain Instant Payments. bitcoin.org.
Linus, R. (2023). BitVM: Compute Anything on Bitcoin. bitcoinvm.xyz.
Zamyatin, A., Harz, D., Lind, J., Panayiotou, P., Gervais, A., & Knottenbelt, W. (2019). XCLAIM: Trustless, Interoperable, Cryptocurrency-Backed Assets. IEEE S&P.
Tikhomirov, S., Pickhardt, R., Biryukov, A., & Nowostawski, M. (2020). Probing Channel Balances in the Lightning Network. arXiv.
Kiayias, A., & Litos, O. S. T. (2020). A Composable Security Treatment of the Lightning Network. arXiv.