Guides · Bitcoin

Bitcoin Layer 2 solutions: Lightning, Rootstock, Stacks

Bitcoin's Layer 2 solutions, Lightning, Rootstock, and Stacks, tackle payment speed, programmability, and smart contracts in distinct ways by 2026.

Bradley Hughes 6 min read

Bitcoin Layer 2 solutions: Lightning, Rootstock, Stacks

Bitcoin’s base layer is deliberately simple: it settles transactions roughly every ten minutes and does not run smart contracts. Everything built to make bitcoin faster, cheaper to move, or programmable happens on a second layer that settles back to that base chain. In 2026, three networks dominate that conversation, each solving a different problem.

Why bitcoin needs a second layer at all

The base chain’s simplicity is not an oversight, it is a design tradeoff Bitcoin’s original architecture made deliberately in favour of security and decentralization over throughput. A block arrives roughly every ten minutes and has a limited amount of space, which caps how many transactions the base chain can process directly. That constraint is by design: allowing unlimited block size or arbitrary smart contract execution on the base layer would raise the computational and storage burden on every node validating the chain, pushing out smaller operators and concentrating validation power among fewer, better-resourced participants, the opposite of what a decentralized settlement network is meant to preserve. Layer 2 networks exist to route around that constraint without changing the base layer itself: they push the bulk of everyday activity, payments, application logic, high-frequency transfers, onto a separate system, while still relying on Bitcoin’s base chain as the final, hardest-to-attack record of who owns what. Each of the three approaches below inherits Bitcoin’s security to a different degree and in a different way, which is the real axis to evaluate them on, not just speed or fees.

Lightning Network: payments

Lightning is the oldest and most payment-focused of the three. Users open payment channels, transact instantly and near-free within them, and only touch the Bitcoin base chain to open or close a channel. By May 2026, public channel capacity sat around 4,898 BTC spread across roughly 41,080 channels and 17,438 active nodes, according to research published by Spark. That capacity had climbed from a low near 4,200 BTC in August 2025 to a peak of about 5,637 BTC in December 2025 before settling back, driven in part by institutional integrations from exchanges including Binance, OKX and Coinbase.

Node count tells a different story than capacity. Lightning had roughly 20,700 nodes at its 2022 peak and had fallen to around 17,400 by 2026. Capital and volume are concentrating into fewer, better-capitalized routing nodes rather than spreading across thousands of hobbyist machines. On the usage side, monthly payment volume hit $1.17 billion in November 2025, up roughly 266% year-over-year, and over 15% of Coinbase’s bitcoin withdrawals were routed over Lightning by mid-2025.

Mechanically, a Lightning payment channel is a two-party arrangement funded by a transaction recorded on the Bitcoin base chain, after which the two participants can exchange an unlimited number of updated balance signatures between themselves without broadcasting anything to the network until they decide to close the channel. Payments that need to reach someone without a direct channel route through a path of connected channels, with each hop taking a small routing fee, which is why capacity and connectivity across the network matter as much as raw node count: a well-connected node with deep channels can route payments cheaply and reliably, while a poorly connected one may fail to find a viable path for a given payment. That routing requirement is also Lightning’s core limitation. Unlike a simple on-chain transfer, receiving a Lightning payment generally requires the recipient to be online with sufficient inbound liquidity already allocated to them, a usability hurdle that has driven much of the shift toward institutional, custodial Lightning nodes handling routing on behalf of end users rather than individuals running their own.

Rootstock: smart contracts, secured by Bitcoin miners

Rootstock (RSK) takes a different approach: it is a sidechain that brings Ethereum-style smart contract functionality to bitcoin without altering the base layer. Bitcoin moves into Rootstock as rBTC, minted 1:1 against coins locked on the main chain through a system called PowPeg, live since early 2025 and secured by a 5-of-9 multisignature setup using hardware security modules, with plans to expand that signer set to 20 and eventually 60 members. Rootstock’s security model leans on Bitcoin’s own miners: merge-mining, where the same computational work that secures Bitcoin also secures Rootstock, covers more than 80% of Bitcoin’s total hashrate as of 2025. As of July 2026, Rootstock held about $92.18 million in DeFi TVL and $125.33 million bridged, putting it slightly ahead of Stacks on the DeFi metric.

Stacks: a separate execution layer that settles to Bitcoin

Stacks takes a third path: it runs its own execution layer with its own consensus, but settles state back to Bitcoin rather than merge-mining with it. Its bridge asset, sBTC, went live for mainnet deposits in December 2024 following the network’s Nakamoto upgrade the previous October, letting BTC move into Stacks’ ecosystem of applications. The network also runs a staking mechanism with roughly six-month bonding periods targeting a 3% yield, and has distributed over 4,200 BTC to stakers since a program that started in January 2021. Stacks held about $83.38 million in DeFi TVL as of July 2026, close behind Rootstock, with a May 2026 roadmap update focused on bridge optimization and a Clarity Wasm upgrade targeting a 100x throughput increase.

The tradeoff underneath all three

None of these networks is a drop-in replacement for the others, because they are not solving the same problem. Lightning optimizes for payment speed and cost at the expense of requiring liquidity locked in channels and online availability to receive funds. Rootstock and Stacks both add programmability that bitcoin’s base layer lacks, but each introduces a different trust assumption (a federated or merge-mined bridge for Rootstock, a separate consensus layer settling to Bitcoin for Stacks) that a holder should understand before moving coins onto either. Bitcoin itself remains the settlement layer underneath all three; none of them changes what happens on the base chain.

What to actually weigh before moving coins

The practical question for a bitcoin holder is rarely “which layer 2 is best” in the abstract, it is which tradeoff fits the specific thing they are trying to do. For someone who wants to send or receive frequent, small payments cheaply, Lightning solves that problem directly, at the cost of managing channel liquidity and needing to be online to receive. For someone who wants to interact with lending, borrowing or other DeFi applications while keeping exposure denominated in bitcoin, Rootstock or Stacks are the relevant options, and the choice between them comes down to how much a holder trusts a merge-mined, multisignature bridge secured by Bitcoin’s own miners versus a separate execution chain with its own validator set that periodically settles back to Bitcoin. Neither trust model is strictly safer than the other in every scenario; they fail differently. A bridge secured by a signer set is vulnerable if enough signers are compromised or collude, a risk category that has caused some of the largest losses in crypto’s bridge history across various blockchains. A separate execution layer is vulnerable to bugs or failures within its own consensus mechanism, independent of anything happening on Bitcoin itself. Understanding which failure mode applies to a given network, rather than assuming “settles to Bitcoin” means “as secure as Bitcoin,” is the single most useful piece of due diligence before moving meaningful value onto any bitcoin layer 2.

Sources