What Is the Lightning Network?

The Scalability Problem Lightning Was Built to Solve

Bitcoin’s blockchain processes transactions in batches called blocks, each appended roughly every ten minutes. The network is designed for security and decentralisation, not throughput. At peak demand, transactions can take hours to confirm, and fees — denominated in satoshis, the smallest unit of bitcoin — can rise sharply as users compete for limited block space.

For small everyday payments, these economics are impractical. Paying a few dollars for a coffee makes no sense if the on-chain fee exceeds the purchase amount, or if the merchant must wait for confirmations. The Lightning Network was proposed in a 2016 white paper by Joseph Poon and Thaddeus Dryja as a solution: a second layer that handles most of the transactional load off-chain, settling only the net result on Bitcoin‘s base layer.

How Payment Channels Work

Lightning operates through payment channels — bilateral agreements between two parties that are opened by committing a funding transaction to the Bitcoin blockchain. Once open, the two parties can exchange bitcoin back and forth an unlimited number of times without broadcasting each individual transaction to the network. They are updating a shared ledger between themselves, cryptographically signed, that records the current balance split.

When both parties are done transacting, they close the channel by broadcasting the final balance to the Bitcoin blockchain. Only two transactions ever touch the base layer: the opening and the closing. Everything in between is instant and essentially free.

The clever extension is routing. A user does not need a direct channel with every counterparty. Lightning nodes form a network graph, and payments can be routed through intermediate nodes, each of which earns a tiny forwarding fee. Using a technique called Hash Time-Locked Contracts (HTLCs), payments are cryptographically enforced such that intermediate nodes cannot steal funds — they either pass the payment along and earn their fee, or the entire route fails and funds are returned.

Current State and Real-World Use

Lightning has grown considerably since its mainnet launch in 2018. Network data tracked by public monitoring tools shows thousands of nodes and significant aggregate channel capacity, though the total remains a fraction of on-chain bitcoin in circulation. Adoption has concentrated in specific corridors: remittances in countries with limited banking infrastructure, micropayments for content creators, and point-of-sale payments in merchants that accept bitcoin.

El Salvador’s Chivo wallet used Lightning as its primary payment rail after the country adopted bitcoin as legal tender in 2021, providing one of the largest real-world stress tests the network has undergone. Several major exchanges and payment apps have integrated Lightning wallets, reducing the friction of using it for end-users who do not want to manage channels manually.

Limitations and Open Questions

Lightning is not a complete solution to all of Bitcoin’s scaling challenges. Receiving payments on Lightning requires that a user have inbound liquidity — channel capacity directed toward them — which can be technically complex to set up for non-technical users. Routing failures occur, particularly for larger payments that must traverse multiple hops without sufficient channel capacity at each step.

Channel management remains demanding for merchants and node operators who want to maximise reliability. Services called Lightning Service Providers (LSPs) have emerged to abstract away this complexity, but they reintroduce a degree of custodial reliance. There are also open research questions around channel jamming attacks and the long-term fee market that will sustain routing nodes.

Nevertheless, Lightning represents the most mature and widely deployed second-layer solution in Bitcoin. For those exploring how bitcoin is held and transacted, understanding the Lightning layer is increasingly relevant as the ecosystem builds payment infrastructure on top of the settlement base.