The Lightning Network: Bitcoin's Speed Layer
Bitcoin's base layer processes approximately 7 transactions per second — by design. It was built for security and decentralisation, not for the millions of microtransactions that make a global payments network practical. The Lightning Network is a second-layer protocol built on top of Bitcoin to solve this. It is not a separate cryptocurrency, not a fork, and not a compromise on Bitcoin's security model. Bitcoin remains the settlement layer; Lightning handles the high-frequency traffic above it.
Why Bitcoin Needs a Second Layer
A Bitcoin block is created approximately every 10 minutes and can hold roughly 2,000–4,000 transactions. At that throughput — around 7 transactions per second — the base layer cannot process the volume of a modern payments network. Visa processes approximately 24,000 transactions per second.
When demand for block space exceeds supply, fees rise. During the peak congestion of 2021's bull market, the median Bitcoin transaction fee exceeded $60 at several points. For a payment of $5, a $60 fee is impractical. The base layer is economically unsuited for small, frequent payments — not because it was poorly designed, but because it was optimised for final, irreversible, trustless settlement.
The Scaling Trilemma
Any distributed network must balance three properties: decentralisation, security, and scalability. Bitcoin prioritises the first two. Lightning provides scalability without changing the base layer — it moves high-frequency activity off-chain while using on-chain Bitcoin as the ultimate settlement mechanism.
How Lightning Payment Channels Work
A Lightning payment channel is a direct connection between two parties, secured by a smart contract on the Bitcoin blockchain. Opening a channel requires one on-chain Bitcoin transaction. Once open, the two parties can send funds back and forth instantly and at near-zero cost — indefinitely — without any additional on-chain transactions.
A Worked Example
- 1.Alice opens a Lightning channel with Bob, funding it with 0.01 BTC. One on-chain transaction.
- 2.Alice sends Bob 1,000 sats (≈$0.70). The channel balance updates instantly, with no on-chain activity. Zero fees, instant.
- 3.Bob wants to pay Carol, who is not directly connected to Alice. The Lightning Network routes the payment through Bob — Alice → Bob → Carol. Intermediate nodes earn a tiny routing fee (typically <1 sat).
- 4.After thousands of transactions, Alice and Bob close the channel. The final net balance settles on-chain. One closing transaction.
The Lightning Network Today
As of early 2026, the public Lightning Network has over 14,000 nodes, more than 60,000 channels, and a total channel capacity of approximately 5,000 BTC — representing hundreds of millions of dollars in locked liquidity. These figures, tracked by 1ML.com and mempool.space, undercount the actual usage: private channels (not visible to the public network graph) are estimated to carry a significant proportion of total volume.
14K+
Public nodes
60K+
Active channels
~5,000
BTC capacity (Source: 1ML.com)
Real-world Lightning applications span payments (Strike, CashApp), streaming micropayments for podcasts and video (Value4Value — listeners pay per minute of content), merchant payments at Bitcoin conferences and in El Salvador, and cross-border remittances where traditional rails charge 5–10% fees. The protocol is increasingly integrated into mainstream financial apps.
Notable Lightning Applications
Strike
Payments and remittances, US-focused
Wallet of Satoshi
Custodial Lightning, easiest onboarding
Phoenix
Self-custodial, auto-manages channels
Breez
Self-custodial with built-in podcast player
Alby
Browser extension for web payments and Value4Value
Zeus
Advanced self-custodial, connects to your own node
Lightning's Limitations and Trade-offs
Lightning is not a universal payments solution — it has genuine constraints that make it better suited for some use cases than others. Understanding them is part of understanding the technology honestly.
A payment can only route through channels that have sufficient funds on both sides. Sending large amounts requires channels with matching liquidity, which may not always be available.
To receive lightning payments, someone else must open a channel to you with funds on their side. New users often need to purchase inbound capacity or use a service that provides it.
Multi-hop payments rely on intermediate nodes being online and having sufficient liquidity. Failed routing attempts are common, though software has improved significantly since 2019.
The easiest Lightning apps (Wallet of Satoshi, Strike) are custodial — they hold your funds. The same counterparty risk that applies to exchanges applies to custodial Lightning wallets.
Lightning and Self-Custody
The same self-custody principles that apply to on-chain Bitcoin apply to Lightning. Custodial Lightning wallets — where a company holds your funds and processes your payments — offer the simplest user experience but reintroduce the counterparty risk that self-custody is designed to eliminate.
Self-custodial Lightning wallets like Phoenix and Breez manage the complexity of channel liquidity automatically while keeping the user in control of their keys. They are considerably more technical than custodial apps, but they represent the sovereign version of Lightning — where the user retains full control over both the funds and the channel state. For users who care about the "not your keys, not your coins" principle, self-custodial Lightning is the only consistent extension of it to Layer 2.
Keep Exploring
The base layer security Lightning is built on top of
On-chain transactions, keys, and blocks explained
Self-custodial Lightning wallets and key management
On-chain fee economics and miner revenue
The on-chain node infrastructure Lightning sits above