Lightning Network: What Changed in 10 Years

Bitcoin processes 7 transactions per second. Visa processes 24,000. Here is what the Lightning Network achieved and what changes now that stablecoins have arrived.

The Bitcoin block size debate of 2015 to 2017 was the most divisive conflict in Bitcoin’s history. It led to the Bitcoin Cash hard fork, but it began with a single question: How does a peer-to-peer electronic cash system scale to serve billions of people?

One side argued for increasing Bitcoin’s block size limit so the main chain could process more transactions. The other argued for keeping blocks small and building a second layer. This network of payment channels would operate on top of Bitcoin’s blockchain, handling large numbers of small transactions while the base layer settled larger, final transactions. As documented in our Bitcoin history research, the debate ended with SegWit’s activation in August 2017 and the Bitcoin Cash fork. The Bitcoin development community chose the second-layer approach.

The Payment Layer

The Lightning Network was the main result of that decision. Joseph Poon and Thaddeus Dryja introduced the concept in a February 2015 whitepaper. Lightning Labs, Blockstream, and ACINQ spent the next three years building the protocol. In March 2018, Lightning launched on Bitcoin’s mainnet as a live payment layer that could route Bitcoin payments between connected nodes in less than a second for fees measured in fractions of a cent.

Since then, Lightning has been both more successful and less successful than its supporters and critics expected. In November 2025, the network processed $1.17 billion in monthly payment volume. It had 18,000 active nodes, 5,400 BTC in capacity, and 12 million monthly transactions. Public Lightning payment volume grew 266 percent year over year. These figures show how far the network has come in eight years. They also remain a small fraction of what Lightning’s most optimistic supporters expected.

This article tells the full story. It explains how Lightning works, how developers built it, what went right, what went wrong, what the network’s concentration data reveals, and what the arrival of stablecoins means for its future.

How the Lightning Network Works

Understanding Lightning’s limitations starts with understanding how it works. Many critics confuse genuine technical limitations with misunderstandings about payment channels.

A Lightning payment channel is a relationship between two participants that begins with a funding transaction on Bitcoin’s main chain. When Alice wants to open a channel with Bob, she creates a multisignature Bitcoin transaction. It locks funds, for example, 0.01 BTC, in a shared address controlled by both of their keys. The funding transaction is then broadcast to Bitcoin’s blockchain and pays the normal network fee.

Once the channel is open, Alice and Bob can send Bitcoin back and forth as often as they like. Payments are almost instant and cost only a fraction of a cent because they do not touch the blockchain. Instead, each payment updates a shared balance that both parties sign without broadcasting it. The blockchain only becomes involved when they close the channel and settle the final balance.

Payment Routing

Payment channels are only the first step. Lightning’s strength is its routing system. Alice does not need a direct channel with Carol to pay her. If Alice has a channel with Bob, and Bob has a channel with Carol, Alice can route the payment through Bob.

Bob’s node automatically forwards the payment and collects a small routing fee. The transaction settles in less than a second. Bob never takes custody of the funds. Instead, the payment uses a cryptographic mechanism called Hashed Timelock Contracts (HTLCs). HTLCs guarantee one of two outcomes. Either Carol receives the payment and Bob collects the routing fee, or the network cancels the transaction and every participant keeps their funds. At no point can Bob or any other routing node take control of the Bitcoin being transferred.

In theory, any two participants on the Lightning Network can pay each other if a connected path of channels exists and the network has enough liquidity in the right direction. In practice, finding efficient routes with enough liquidity remains one of Lightning’s biggest routing challenges. As a result, the network has become more concentrated around large, well-capitalized routing nodes instead of the decentralized mesh network described in the original whitepaper.

Lightning Network: The Building Years (2015–2018)

The Lightning Network whitepaper, written by Joseph Poon and Thaddeus Dryja, was published in February 2015 during the most intense phase of the Bitcoin block size debate. The timing was no accident. The paper presented Lightning as an alternative to larger Bitcoin blocks. Instead of increasing the block size, it argued that payment channels could handle high transaction volumes without changing Bitcoin’s base layer.

The paper introduced a key technical idea: using Hashed Timelock Contracts (HTLCs) in a network of payment channels. This allowed users to route payments across multiple hops without trusting the intermediate routing nodes. Earlier payment channel proposals already existed, but they either relied on trusted intermediaries or supported only limited routing. Lightning’s HTLC design solved the multi-hop problem with cryptography.

SegWit and Lightning

Building the Lightning Network required two protocol changes that Bitcoin did not yet have: a fix for transaction malleability and Segregated Witness (SegWit). Transaction malleability allowed third parties to change a transaction ID before confirmation. That created a security problem because Lightning channels depend on the funding transaction ID remaining unchanged. SegWit, activated in August 2017, fixed transaction malleability and made Lightning’s secure deployment possible. Without SegWit, Lightning could not have launched safely on Bitcoin’s mainnet.

Three Independent Implementations

Three development teams built the first Lightning implementations. Lightning Labs developed LND (Lightning Network Daemon) in Go. Blockstream developed Core Lightning (formerly c-lightning) in C, while ACINQ developed Eclair in Scala.

All three implementations followed the Basis of Lightning Technology (BOLT) specifications. As a result, they remained interoperable. A node running LND could open channels and route payments through nodes running Core Lightning or Eclair. This approach reflected Bitcoin’s own multi-client philosophy. No single team controlled the software, which reduced the risk of a single point of failure.

Mainnet Launch

The Lightning Network launched on Bitcoin’s mainnet in March 2018. Developers took a cautious approach. Lightning Labs recommended a maximum channel size of 0.167 BTC, about $1,000 at the time, to limit the financial risk for users testing early software.

That caution proved justified. Early Lightning releases contained bugs that could, in some cases, cause users to lose funds locked in payment channels. As a result, one piece of advice became standard across the community: do not put more Bitcoin into Lightning than you can afford to lose.

Lightning Network: The Growth Era (2019–2022)

The Lightning Network grew slowly in its early years. Growth came mainly from enthusiasts and developers, not businesses. Running a Lightning node required technical knowledge. Managing payment channels took time. Routing was inconsistent, and using Lightning was more difficult than sending Bitcoin on the main chain.

Larger Channels and Liquidity Markets

The 0.167 BTC channel limit was removed in early 2021. This introduced Wumbo channels, which removed the upper limit on channel size for users who opted in. Larger channels made commercial payments easier. They also helped liquidity providers build more efficient routing infrastructure.

Lightning Labs launched the Lightning Pool marketplace in 2020. It allowed routing nodes to buy and sell inbound liquidity. Operators no longer had to open new channels every time they needed additional inbound capacity. This reduced one of the biggest challenges of running a routing node.

El Salvador’s National Rollout

El Salvador adopted Bitcoin as legal tender in September 2021. It became the first country to deploy the Lightning Network at a national level. The government developed the Chivo wallet and distributed it to every Salvadoran citizen. The wallet used Lightning for most small payments because processing millions of retail transactions on Bitcoin’s base layer would have cost far more.

Chivo did not meet its original adoption targets. Even so, the rollout showed that the Lightning Network could support a national payment system. It also showed that people with no previous cryptocurrency experience could use Lightning through a well-designed mobile app.

Commercial Adoption

During 2021 and 2022, Strike, built by Jack Mallers, became the most successful commercial Lightning application. The service kept payments simple. Users deposited US dollars. Strike converted the funds into Bitcoin, sent the payment over Lightning, and allowed recipients to receive either Bitcoin or their local currency.

The model worked especially well for cross-border remittances. Sending money from the United States to El Salvador costs about 0%. Traditional remittance providers often charged 8% to 10%. Users never interacted with the Lightning infrastructure. They simply paid less.

Growth Slows

The Lightning Network reached its highest public node count in 2022. The network had about 16,000 to 18,000 public nodes and more than 80,000 payment channels. Public capacity also exceeded 4,000 BTC.

By then, Lightning supported more users, more liquidity, and more commercial applications. However, problems remained. The user experience was still difficult for non-technical users. Routing larger payments was inconsistent. Growth also slowed. Adoption became meaningful within the crypto ecosystem, but it was still small compared with the broader payments market.

The Consolidation: Fewer Nodes, More Capacity (2023–2025)

Between 2023 and 2025, the Lightning Network produced an unexpected pattern. Public node counts fell, while network capacity continued to grow. In other words, the network became more capable even as it became more concentrated.

Fewer Public Nodes

The Lightning Network had fewer public nodes than it did at its 2022 peak. The network did not continue expanding. Instead, it consolidated. Fewer operators ran public routing infrastructure for several reasons. Running a reliable Lightning node requires constant uptime, active channel management, and enough liquidity to route meaningful payments. Many hobbyists decided the time and cost were no longer worth it.

The Economics of Routing

The economics explain much of this pattern. Running a routing node is not a passive activity. Operators must manage channels, provide liquidity, maintain their software, and keep their nodes online. In return, they earn routing fees measured in satoshis, or fractions of a cent for each payment.

For small routing nodes, those fees often do not cover the time and resources needed to keep the node running. Larger operators face the same work, but they process far more payments and manage liquidity more efficiently. That gives them a much stronger economic position.

Concentration Increases

The node-capacity Gini coefficient rose to about 0.97 in 2025, showing that Lightning’s routing capacity had become highly concentrated. A small number of routing hubs controlled a large share of the network’s liquidity.

For comparison, global income inequality has a Gini coefficient of about 0.63. A score of 1.0 would mean a single entity controls all of an asset. By that measure, Lightning’s routing capacity ranks among the most concentrated distributions.

More Capacity, Fewer Operators

Public capacity reached a new high of 5,637 BTC in December 2025, even though the number of public nodes stayed mostly unchanged.

The remaining nodes were larger, held more liquidity, and were managed more actively. They provided more routing capacity than the smaller hobbyist nodes that left the network. As a result, the Lightning Network moved closer to a hub-and-spoke structure than the fully peer-to-peer mesh described in the original whitepaper.

The Trade-Off

This concentration does not prevent Lightning from routing payments. HTLCs still allow payments to move across the network without trusting intermediate nodes. However, concentration changes the network’s risk profile.

If a major routing hub goes offline, smaller nodes that depend on it lose important payment paths. As more routing flows through a small number of large operators, the network depends more on their uptime and stability.

The Exchange Integration Wave (2024–2025)

One of the biggest changes between 2024 and 2025 was the adoption of the Lightning Network by major cryptocurrency exchanges. Instead of building new applications or changing the protocol, exchanges made Lightning available for Bitcoin deposits and withdrawals. This brought its speed and low transaction fees to hundreds of millions of users.

Coinbase Joins Lightning

The largest milestone came in mid-2024, when Coinbase completed its Lightning integration through Lightspark. By mid-2025, more than 15% of Bitcoin withdrawals from Coinbase used Lightning. Binance, OKX, Kraken, and Bitget also support Lightning withdrawals.

For most of Lightning’s history, using the network required extra steps. Users had to open payment channels with an on-chain Bitcoin transaction, while much of their Bitcoin remained on exchanges.

Exchange integration removed those extra steps. A Coinbase user could send Bitcoin directly to a Lightning address without opening or managing payment channels. The exchange handled the Lightning infrastructure. The user simply selected Lightning as the withdrawal method and received funds within seconds at very low cost.

Merchant adoption also increased. CoinGate reported that Lightning accounted for more than 16% of all Bitcoin orders on its platform in 2024, up from about 6.5% two years earlier.

During 2024 and 2025, Block (formerly Square) began rolling out Lightning payments to its roughly 4 million US point-of-sale merchants. Full availability was expected in 2026. The rollout increased the number of merchants able to accept Lightning payments across the United States.

Together, exchange integration and merchant adoption completed a payment flow that had been missing for years. A user could withdraw Bitcoin from Coinbase over Lightning and spend it at a merchant using Block’s payment system, and the merchant could deposit the funds back to an exchange. The entire payment cycle stayed off Bitcoin’s main chain, making transactions faster and less expensive.

Lightning Network: Stablecoins Arrive (2025–2026)

The latest chapter in the Lightning Network’s history also raises one of its biggest questions.  Taproot Assets, developed by Lightning Labs, allows assets other than Bitcoin to be issued on Bitcoin and transferred over Lightning channels.

Lightning Labs released Taproot Assets v0.6 in June 2025, bringing multi-asset support to Lightning on mainnet for the first time. Version 0.7, released in December 2025, added reusable addresses and auditable asset supplies. In January 2025, Tether announced that USDT would expand to Bitcoin and Lightning. The integration went live in March 2026.

USDT changes one of Lightning’s biggest limitations. In many developing markets, the main reason people use cryptocurrency is access to US dollars, not Bitcoin itself.

In countries such as Nigeria, Ghana, Kenya, and across Latin America, people often want to hold, send, and receive dollars. Bitcoin’s price can change quickly, making it less suitable for everyday payments. USDT on Lightning combines stable prices with Lightning’s fast settlement and low transaction fees.

In Africa, Bitnob supports Lightning-based salary payments for remote workers across 23 countries and reported 340% year-over-year transaction volume growth. Machankura allows people to send Lightning payments through USSD and SMS on feature phones in Ghana, Kenya, Malawi, Nigeria, South Africa, and Uganda.

As discussed in our Crypto in Africa research, many people use cryptocurrency to access US dollars and reduce the cost of cross-border payments. Stablecoins on Lightning support both use cases.

A New Direction for Lightning

Lightning was originally designed to make Bitcoin practical for everyday payments. Adding stablecoins makes the network useful for a wider range of users. It also changes what the network carries.

As stablecoin use grows, more Lightning payments may involve USDT or USDC instead of Bitcoin. If that happens, Lightning will continue to run on Bitcoin, but an increasing share of the value moving across the network could be stablecoins.

Whether that strengthens or weakens Lightning depends on its purpose. If the goal is to promote Bitcoin as a payment currency, stablecoins compete with that vision. If the goal is to build a fast and low-cost payment network secured by Bitcoin, stablecoins could bring many more users.

The Technical Progress

BOLT 12 and Reusable Payment Addresses

One of Lightning’s biggest usability challenges has been its invoice system. Traditional Lightning payments require a new invoice for every transaction. Each invoice can only be used once and expires after a set period.

That works for occasional payments, but it is less convenient for merchants, donations, and subscriptions.

BOLT 12 adds reusable payment addresses, known as Offers. A merchant can publish a single Lightning address and receive repeated payments without creating a new invoice each time.

The specification was added to the Lightning protocol in late 2024. Core Lightning, LDK, and Eclair now support BOLT 12. LND, the most widely used implementation, still does not support Offers natively as of mid-2026. As a result, most Lightning payments still use the older BOLT 11 invoice system, although the transition to BOLT 12 is underway.

Channel Splicing

Channel splicing lets users add or remove funds from an existing Lightning channel without closing and reopening it. Previously, changing a channel’s capacity required closing the channel, making an on-chain transaction, and opening a new one.

The major Lightning implementations added support for channel splicing during 2024 and 2025. It reduced the work involved in managing channels, especially for routing nodes that regularly adjust liquidity.

Multi-Path Payments

Multi-path payments improve reliability by splitting a payment across several routes. If no single route has enough liquidity, Lightning divides the payment into smaller parts and sends them at the same time. The payment succeeds only if every part reaches the recipient.

Multi-path payments are now supported by all major Lightning implementations. They helped improve payment reliability from the inconsistent experience of 2019 and 2020 to payment success rates above 99% on well-configured Lightning nodes by 2025.

The Limitations

The Lightning Network has made steady progress. Transaction volume has grown, major exchanges now support Lightning, stablecoins have arrived, and payment reliability has improved. Even so, some challenges have not been solved.

Large Payments

Lightning works best for smaller payments. Small transactions usually find enough liquidity across the network to complete successfully.

Larger payments are more difficult. A payment of $1,000 or $10,000 depends on enough liquidity along every route it follows. If a single channel lacks capacity, the payment can fail.

Payment success rates above 99% are mainly reported for well-configured deployments and smaller transactions. Larger payments are still less reliable, which limits Lightning’s use for higher-value commercial payments.

Receiving Payments

Receiving Lightning payments depends on inbound liquidity. In simple terms, other nodes must have channel capacity available to send funds to you.

This does not happen automatically. Someone has to open a channel with liquidity directed toward your node, or you need to obtain inbound liquidity through a marketplace or service.

Services such as Lightning Pool, Voltage, and Amboss make this easier, but the process is still more involved than receiving an on-chain Bitcoin payment or using a traditional payment processor.

Nodes Must Stay Online

Lightning payments only work if the recipient’s node is online when the payment is sent.

Bitcoin’s base layer works differently. Anyone can send Bitcoin to an address while the owner is offline because the transaction is recorded on the blockchain. The owner can access the funds later.

If a Lightning node is offline, the payment fails. That makes Lightning less suitable for some situations and means merchants and other users need to keep their nodes online.

Watchtowers

Lightning protects against fraud by expecting both parties to monitor the blockchain. If someone tries to close a channel using an outdated balance, the other party must detect it and respond within a limited time.

Watchtower services help users who cannot keep their nodes online all the time. They monitor channels and respond to fraudulent channel closures when needed.

Watchtowers reduce this risk, but they also add another service that users may choose to rely on. Bitcoin’s design tries to minimize that kind of dependence, so some people see this as a trade-off.

What I’m Watching

By mid-2026, the Lightning Network has become a more mature payment network. It has not achieved the fully decentralized, peer-to-peer system described in the original whitepaper.

The network processes more than $1.17 billion in monthly payment volume and about 12 million transactions each month. Lightning adoption in Africa has grown, and stablecoins have arrived through Taproot Assets. At the same time, the node-capacity Gini coefficient has reached about 0.97, showing that much of the network’s routing capacity is concentrated in a small number of operators.

Stablecoins and Merchant Adoption

The first development I’m watching is the growth of the Taproot Assets ecosystem, especially USDT and USDC on Lightning. As covered in our RWA tokenization research, stablecoins are the most widely used on-chain financial instrument by transaction volume globally. If Taproot Assets allows Lightning to capture a larger share of stablecoin transactions, especially in markets where settlement speed and transaction costs matter most, the network could expand well beyond Bitcoin payments. It would also compete more directly with payment activity that now takes place on Tron and Ethereum.

The second is Block’s merchant rollout. Block is rolling out Lightning payments to its network of roughly 4 million US point-of-sale merchants, with full availability expected by 2026. If the rollout stays on schedule and Lightning payments reach even 5% to 10% of Block’s merchant network, Lightning usage would increase sharply. It would exceed the network’s current transaction volume. The biggest question is whether merchants find Lightning payments attractive enough to accept and whether customers choose to use them.

Alternative Approaches

The third is competition from alternative approaches. Lightning’s biggest competition from alternative approaches. Lightning’s biggest competitor in 2026 may not be another blockchain. It may be a different way of moving Bitcoin off-chain.

Spark is built on statechains. It transfers ownership of existing Bitcoin outputs by rotating keys among a sender, a recipient, and a distributed operator set using FROST threshold signatures. Unlike Lightning, statechains do not use payment channels. It is still too early to know if they can match Lightning’s routing flexibility while avoiding channel management.

Joseph Poon and Thaddeus Dryja wrote an eleven-page whitepaper in 2015 describing a payment channel network for Bitcoin. The network launched on mainnet in 2018, reached its highest public node count in 2022, became more concentrated between 2023 and 2025, integrated with major exchanges, added stablecoins through Taproot Assets, and now processes more than $1 billion in monthly payments.

Lightning is not the universal scaling solution that some early supporters expected. It is a working payment network that has solved some problems and left others unsolved. That is arguably the most accurate description of where the Lightning Network stands in 2026.

---