Skip to content

Shelf 6 · Scaling · 40 / 45

Layer 2 & Scaling

Beyond Lightning: BitVM, Rootstock, Stacks, Babylon, and other Bitcoin Layer 2s, their design philosophies and their real-world progress.

Check this article’s sources (24)
Contents

Article brief

Move quickly above the base chain and return to it only when you need to. Layer 2 design determines what remains on the base chain.

See it as city planning above a crowded central square: subways, passageways, and depots each solve a different movement problem.

Where the analogy stops

Layer 2 is not one technology. Security, data availability, operators, and exit paths differ, and no system automatically inherits every base-layer property.

Structure

  1. 1Base-layer constraints
  2. 2Families of Layer 2 design
  3. 3Trust and exit conditions

Beyond a claim of speed, you will ask what stays on-chain, who can interrupt it, and how a user can exit.

Open the glossary

1Why Layer 2?

Figure 1 Using Lightning as an example, the diagram shows frequent off-chain balance updates and settlement recorded on Bitcoin. Custody, exit mechanisms and security assumptions differ among systems called L2s.

Bitcoin's base layer puts one goal first: "anyone in the world can run a full node." The block limit is defined in weight units, 4,000,000 WU, which in practice yields blocks of roughly 1-2MB with a theoretical maximum near 4MB. That limit and the 10-minute block interval follow from the same design philosophy.

Transactions per second depend heavily on transaction weight, so 7-14 is not a fixed theoretical maximum. Consensus limits block weight, constraining how many payments can be recorded individually on the base layer.

A Layer 2 (L2) is a protocol built on top of Bitcoin's base layer. Most transactions happen on the L2, and only the final settlement is recorded on the base layer, which is where the extra capacity comes from.

How much Bitcoin security a system uses depends on its design. Speed, privacy and smart-contract features can come with additional dependence on operators, signers, monitoring or exit deadlines.

Unlike Ethereum's L2s (Arbitrum, Optimism, and others), Bitcoin's L2s take widely different technical approaches, and no single standard has emerged.

One caveat belongs up front: "Bitcoin Layer 2" is not itself a technically agreed category. There is no common standard for how much of the base layer's security a system must inherit before it earns the name, and in practice the label covers chains with their own consensus and even arrangements where funds are simply handed to an operator. The term is a marketing convenience as much as anything. This article therefore judges projects not by whether they are "L2s" but by the categories set out next and by each one's trust assumptions.

2Reading them by category

What gets lumped together as "Layer 2" in fact divides into distinct categories. The name tells you less than two questions do: where do the funds sit, and whose approval do you need to get them back.

Payment channels: two parties lock funds and update balances off-chain. The defining property is that you can exit on-chain unilaterally, without the counterparty's consent (Lightning).

Sidechains: a separate chain with its own consensus. Movement to and from the base layer runs through a "peg," and whoever secures that peg, whether a federation or merge-mining, becomes the party you have to trust (Liquid, Rootstock).

Federations / threshold signatures: several parties hold shares of a key and move funds on the agreement of some number of them. Collusion above the threshold can take the funds (Liquid's functionaries, the sBTC signer set, Fedimint's guardians).

Rollup and bridge verification: off-chain execution can be checked with validity proofs or fraud proofs. Citrea publishes ZK proofs of execution results to Bitcoin, while its Clementine bridge uses optimistic verification through BitVM. Producing a ZK proof and verifying a bridge on Bitcoin are distinct parts of the design. Deployment status and trust assumptions vary by implementation.

Client-side validation: an asset's validity is established not by the chain but by validation data passed between the parties, with only a minimal commitment placed on the blockchain (RGB, Taproot Assets). Nodes do not recognize the asset, so losing the validation data means losing the asset.

Bridges: mechanisms for moving assets between chains. The largest losses of funds in crypto have happened at bridges, again and again. The danger in "moving funds onto an L2" is, in most cases, concentrated in the bridge design. The record of those incidents is covered in "Major Incidents & Lessons."

3Lightning Network (payment channels)

The design was published in 2015, and major implementations reached mainnet in 2018. Built on payment channels, it supports small payments and rapid off-chain settlement.

Public capacity, channel count, and node count all move week to week. This site keeps those figures in one place, in "Lightning Network Primer"; see that article for current statistics. Duplicating them here would guarantee that the two pages contradict each other after any update.

January 2025: Tether announced plans to bring USDT to the Lightning Network through Taproot Assets, aiming at dollar-denominated stablecoin payments on a Bitcoin L2.

LSPs (Lightning Service Providers) help with liquidity and channel management, but using one does not itself imply custody. Check whether users hold their keys and can exit on-chain themselves. A custodial wallet, where the provider controls the keys, also requires trust in that provider's management of the funds.

Working deployments include Strike in the U.S. and tipping across Nostr. El Salvador's Chivo wallet also used Lightning, but on October 1, 2026, the IMF reported that majority ownership and control had been transferred to a private operator. In its October 8 announcement, Linguard Labs also disclosed its acquisition of a majority stake and plans to relaunch Chivo. Unwinding the remaining public-sector exposure is still required, and these announcements alone do not establish whether Lightning is currently in use.

See the dedicated "Lightning Network Primer" topic for a deeper treatment.

4Liquid Network (federated sidechain)

A federated sidechain launched in 2018 by Blockstream, a major Bitcoin Core development company.

It uses L-BTC (Liquid Bitcoin), a version of bitcoin pegged 1:1, with a two-way peg to mainnet Bitcoin.

Features: fast 1-minute blocks (final after two confirmations), Confidential Transactions for privacy, and Issued Assets for multiple currencies and tokens.

Governance has two tiers. The Liquid Federation had roughly 87 participating organizations as of Q1 2026, but block signing and custody of the peg are performed by the 15 nodes known as functionaries. The two-way peg with mainnet Bitcoin is secured by an 11-of-15 multisig across those 15 keys.

L-BTC's backing therefore rests on two premises: that 11 functionaries do not collude, and that fewer than five go offline at once. This 11-of-15 is the core of Liquid's trust assumption, a design that knowingly accepts less decentralization than Bitcoin itself in exchange for speed and confidential transactions.

Tether issues USDT-Liquid, used for OTC settlement between major exchanges.

5Rootstock (RSK) and Stacks

Rootstock (RSK): an EVM-compatible sidechain merge-mined with Bitcoin, launched in 2018. It runs Ethereum-compatible smart contracts on Bitcoin.

Stacks: uses its own Proof of Transfer (PoX) consensus. Stacks miners send BTC to stackers (STX stakers) in exchange for STX block rewards.

Stacks 3.0 (Nakamoto Release, 2024) tightened its integration with Bitcoin finality. Stacks transactions are "anchored" into Bitcoin blocks and inherit its security.

sBTC is the implementation for handling BTC on Stacks. Deposits, and only deposits, went live on mainnet in December 2024, with withdrawals following on April 30, 2025. The peg is secured by an initial signer set of 15 institutions, with funds moved by threshold signature.

It is sometimes described as "non-custodial," but users cannot recover funds on their own: the design assumes the signer set keeps operating correctly, which places it closer to a federation in trust terms. Trustlessness and a more decentralized signer set are stated as staged goals.

Though called Bitcoin L2s, these have their own consensus and their own tokens; "affiliated chain" describes them more accurately.

6BitVM (proposed 2023)

October 2023: Robin Linus published a novel idea for verifying arbitrary computation on Bitcoin.

Rather than adding new Bitcoin Script operations, it uses "fraud proofs" for optimistic execution. On-chain verification runs only when results are disputed.

The mechanism resembles Ethereum's Optimistic Rollups and in theory allows Turing-complete computation on a Bitcoin L2.

Development has continued through BitVM1, BitVM2, and later work since 2023. Citrea announced its mainnet on January 27, 2026, describing a Clementine bridge using BitVM. Launching a mainnet does not remove trust assumptions; guarantees and limitations must be checked for each implementation.

Practical deployment has its problems, including the many on-chain transactions a worst case may require, but the idea opened new ground in Bitcoin L2 design.

7Babylon (BTC staking)

Founded in 2022, with mainnet launched in 2024. It pledges BTC as security for other PoS chains while the coins stay on the Bitcoin mainchain.

To be precise, what is time-locked is not a private key but the staking output, a UTXO. The user sends their funds to a script carrying several spending conditions: (1) the owner can withdraw after a set period, (2) the owner can unbond early with signatures from a quorum of the covenant committee, and (3) a slashing transaction can confiscate the funds if misbehavior occurs.

What makes that slashing possible is EOTS (Extractable One-Time Signature). A finality provider signs each block height exactly once, using randomness committed in advance. Signing two different blocks at the same height reuses that randomness, and from the two signatures anyone can reconstruct the provider's private key. The recovered key is then used to sign the pre-arranged slashing transactions, confiscating the BTC delegated to that provider.

So "self-custody staking" is accurate in the sense that the funds never move to a third party's address. But if the finality provider you delegated to double-signs, your stake is cut even though you did nothing wrong, and the correctness of the scripts and the behavior of the covenant committee are part of the premise too.

BTC staking spread rapidly between 2024 and 2026, and "Restaking" projects built on Babylon (Lorenzo, Pendle, and others) have appeared.

It provides a new yield source for BTC holders, while drawing criticism from those who hold that having no yield is precisely the point of Bitcoin.

8Ark, Fedimint, and the new generation

Ark: a protocol aiming at instant payments through a different mechanism than Lightning. Instead of long-lived channels, it uses a shared-UTXO model of joint holdings.

Fedimint: a federated Bitcoin custody system based on Chaumian ecash. Privacy is high, and it works as a community- or family-scale Bitcoin bank. The funds are actually held by operators called guardians, however, and collusion above the threshold takes them. Structurally, it is custody.

Cashu: a similar ecash protocol, lighter and friendlier to developers than Fedimint, but the funds are held by a single mint. If the mint absconds, users have no way to recover them. It suits small amounts held with an operator you trust.

Fedimint and Cashu combine operator custody with ecash privacy and simple transfers. Ark provides a path to exit shared UTXOs on-chain. Out-of-round payments add an assumption that the sender and server do not collude before the received funds are refreshed. Check this alongside implementation-specific exit deadlines and data requirements.

Still experimental as of 2026, but gaining ground in privacy-focused communities.

9Layer 2 comparison

Comparing these by "fast or slow" tells you less than comparing who can cause you to lose funds and whether you can exit on-chain without that party's consent. What follows is a contrast of trust assumptions, not a recommendation.

Table for Layer 2 comparison
ProtocolPrimary useTrust assumption (who can cause loss of funds)Unilateral exitSmart contracts
LightningMicro-payments, instant settlementThe channel counterparty (if you or your delegate fail to catch a fraudulent broadcast within the window)Yes — close the channel yourself and exit on-chain✗
LiquidInstitutional trading, OTC settlementCollusion of 11 of the 15 functionariesNo — peg-out runs through the federation△
RootstockEVM-compatible DeFiThe federation securing the peg (plus the effective concentration of merge-mining)No✓ (EVM-compatible)
Stacks / sBTCNFTs and appsThe sBTC signer set (threshold signature)No✓ (Clarity language)
FedimintCommunity-scale custody and paymentsCollusion of guardians above the thresholdNo✗
CashuSmall private paymentsA single mint (absconding is structurally possible)No✗
BabylonBTC stakingDouble-signing by the finality provider you delegated to; the covenant committeeYes — the owner can withdraw after the timelock expires✗ (an asset-utilization protocol rather than an L2)
BitVM familyGeneral computation (deployment stage varies)Varies by implementation (most current designs still depend on an operator)Implementation-dependentYes (arbitrary computation)

On speed: Lightning settles in seconds, Liquid on 1-minute blocks (final after two confirmations, about two minutes), Rootstock and Stacks in tens of seconds to minutes, and BitVM-family systems depend on the implementation. In practice this difference rarely decides anything; the second and third columns above matter far more.

Privacy has no single verdict either. Lightning keeps transactions off the public ledger, but the channel graph is public and information reaches counterparties along the route and any provider you use. Liquid's confidential transactions hide amounts and asset types from parties other than the sender, receiver, and anyone given the relevant blinding keys. Fedimint and Cashu offer strong privacy against the operator while the operator holds the funds.

10Outlook

Making up for the falling miner reward after each halving is a long-term problem for the layers that depend on on-chain fees. L2 development is one of the pillars holding up the wider Bitcoin economy.

Ironically, Ordinals and Runes livened up the Bitcoin fee market in 2023-2024 and supported miner revenue, though demand has since cooled and the fee share of miner revenue has fallen sharply.

If cross-L2 atomic swaps become practical, interoperability across Lightning ↔ Liquid ↔ Stacks improves.

Some BitVM-family L2 implementations offering Ethereum-compatible DeFi have launched, but their usefulness and fund security depend on each bridge and its operating assumptions.

Critics argue that a proliferation of L2s sacrifices Bitcoin's "simplicity." Which L2 comes out on top will be settled by competition over the coming years.

Primary sources

Read next

Forks & Chain Divergence6 min read
Share

Citation

Operator-owned article text, original diagrams, and public data may be used for citation, summarization, indexing, search, RAG, machine analysis, and AI model training. When content is presented to readers, identify Bitcoin Library and the applicable canonical URL where technically practicable.

Revision history

  1. Distinguished L2 security, custody and exit conditions, corrected the diagram caption, and separated rollup execution proofs from bridge verification.
  2. Updated the Chivo transfer and removed an unsupported claim about its current Lightning operation. Added the October announcement by Chivo's new majority owner. Clarified Ark exits, Liquid confidentiality, Citrea deployment, and transaction capacity. Replaced unsupported L2 adoption and maturity rankings with Lightning architecture and payment uses.
  3. Corrected Babylon's early unbonding to match the specification, which requires both the owner's signature and a quorum of the covenant committee. Replaced the documentation-homepage citation with the staking output specification and updated the EOTS Manager link, which had moved and returned 404.
  4. Corrected Liquid's block interval to one minute and the BitVM start year; put the Ordinals/Runes fee statement in the past tense; corrected the USDT statement to Tether's January 2025 announcement.
  5. Added a bilingual layer stack connecting P2P and proof of work, Bitcoin consensus, Layer 2, and applications.
  6. Babylon's mechanism corrected to timelocked staking outputs plus EOTS, trust-assumption and unilateral-exit columns added to the comparison table, new taxonomy section, custodial nature of Fedimint/Cashu plus Liquid 11-of-15 and the sBTC signer set stated explicitly, Lightning statistics consolidated into the dedicated article