Bitcoin on-chain confirms roughly 5 to 7 transactions per second globally. That is by design: the security-first architecture trades throughput for finality. The Lightning Network is a second layer that batches millions of off-chain payments between participants, settling the final balances on-chain. Here is how it works and what it changes.
READING TIME: ~8 MIN
Lightning is a second-layer network built on Bitcoin. Two parties open a payment channel with a single on-chain transaction, then send any number of near-instant, near-free payments between themselves off-chain. The channel is eventually closed with another on-chain transaction that records the final balance. Thousands of channels linked together form a mesh that can route payments across strangers. The result: Bitcoin settles large value on-chain and moves small frequent payments through Lightning, without sacrificing custody or security.
Lightning is a Layer 2 protocol on top of Bitcoin. "Layer 2" means it derives its security from the underlying Layer 1 chain (Bitcoin) without requiring its own token, consensus, or validators. The payments happen off-chain, but every Lightning channel is anchored by real Bitcoin that sits in a 2-of-2 multisig address on the main chain.
If on-chain Bitcoin is like a bank wire (slow, final, expensive per transaction, fine for large sums), Lightning is like cash in your pocket (instant, cheap, fine for small sums, you keep physical custody). The key point is that Lightning does not require trusting a company. The cryptography enforces the channel rules, and the underlying Bitcoin chain is the enforcement court of last resort.
A Lightning channel is created by two parties jointly funding a 2-of-2 multisig Bitcoin address. That funding transaction hits the Bitcoin blockchain once and costs a normal on-chain fee. After confirmation, the channel is open.
Inside the channel, the two parties can update the balance between them millions of times without touching the chain. Each update is a new signed balance sheet that replaces the last one. Either party can at any time publish the most recent balance sheet to the Bitcoin blockchain, which closes the channel and pays out to each party according to that final balance. Closing the channel is another on-chain transaction.
A channel with a million payments going through it only ever creates two on-chain transactions: one to open, one to close. This is where the scaling gain comes from. Lightning turns one on-chain event into potentially unlimited off-chain payments between the same parties.
The corollary: Lightning is for frequent small payments, not one-time large ones. A single $10,000 transfer between two strangers is still better done on-chain. A thousand $1 payments to the same coffee shop over a year is better done over Lightning.
You do not need a direct channel with every person you want to pay. If Alice has a channel with Bob and Bob has a channel with Carol, Alice can pay Carol by routing through Bob. The protocol uses hashed time-locked contracts so that Bob cannot steal the funds in transit; either the payment succeeds end-to-end or it reverts.
In practice this looks a lot like packet routing on the internet. Most users connect to a few well-connected hub nodes, which hold channels with many other hubs, which in turn reach the rest of the network. Routing fees are tiny (often single-digit satoshis) and the path is found automatically by the wallet software.
Those numbers cover only public, discoverable nodes. Private channels (used by consumer wallets like Phoenix and Muun) do not announce themselves and are not counted. True network capacity is meaningfully larger than the public figures suggest.
For any real balance, prefer a non-custodial wallet. Custodial Lightning wallets are convenient but they reintroduce the "trust the company" model that Bitcoin was built to eliminate.
Lightning is no longer a research project. Real, at-scale use cases in 2026 include:
To receive a payment over Lightning you need inbound liquidity: a channel partner with enough balance on their side of the channel. This is a solved problem for most wallets (Phoenix handles it automatically, services like LNBig provide paid liquidity) but it is not free.
Onion routing hides intermediate hops, but a hub node that processes your payments can build a pattern-of-life picture over time. Use multiple wallets and occasional on-chain breaks if privacy matters to you.
If a channel counterparty tries to cheat by publishing an old balance sheet, you have to catch it and publish the newer one. A watchtower is a service that does this for you when your node is offline. Several are free and open-source.
For a deeper hands-on walkthrough, including node setup and channel management, see Lightning Network Practical.
Last updated 2026-04-14. Not financial advice. Do your own research.