Lightning Network
A layer-2 system on top of Bitcoin enabling fast, low-fee payments through off-chain channels, settling on-chain only when necessary.
The Lightning Network is a payment layer built on top of Bitcoin. It enables instant, low-fee payments by routing them through a network of pre-funded payment channels, only settling on the base chain when channels open or close.
The mechanics, simplified:
- Open a channel. Two parties create a 2-of-2 multisig on-chain Bitcoin output, funded by one or both. This is a normal on-chain transaction, pays a normal fee.
- Transact off-chain. The two parties exchange signed "balance updates" - cryptographically valid claims about the current allocation of channel funds. These updates are not broadcast; they live only between the two participants.
- Route through the network. Most channels aren't between you and your final recipient directly. The Lightning Network is a mesh of channels; payments hop through intermediate nodes using Hash Time-Locked Contracts (HTLCs) so that each hop is atomic - the whole payment succeeds, or none of it does.
- Close the channel. Either party can close at any time by broadcasting the latest mutually-signed state on-chain. The funds get distributed according to that final state. Done.
What this buys you:
- Speed. Payments confirm in seconds, not minutes.
- Cost. Sub-cent fees are typical. You can actually use Bitcoin for micropayments.
- Privacy. Lightning payments are not broadcast on the public chain. Only channel opens and closes appear; the payments in between are between the participants and the routing nodes.
- Scalability. Each channel supports unlimited transactions between its two parties without bloating the base chain.
Limitations are real:
- Liquidity. A channel can only route as much as it has on the relevant side. Inbound liquidity is a real concept and a real problem for new nodes.
- Online requirement. Nodes must be online to send, receive, and (importantly) watch for fraud attempts from a channel counterparty.
- Operational complexity. Running your own Lightning node requires more attention than just holding Bitcoin. Many users prefer custodial Lightning wallets - which, as with custodial on-chain wallets, trade self-custody for convenience.
Lightning is how Bitcoin scales without changing the base layer. The base layer optimizes for settlement security across decades; Lightning optimizes for instant payments. The two are complementary by design.
A note on BOLT-12 offers. The legacy invoice format is BOLT-11 - single-use, point-in-time payment requests. BOLT-12 ("offers") is the modern successor. An offer is reusable, because each payer's wallet uses it to request a fresh invoice over Lightning, and blinded paths let the recipient keep its node hidden. It was merged into the Lightning specification in September 2024, without the built-in recurring payments of earlier drafts.
As of October 2026 Core Lightning, eclair and LDK support offers natively. LND's released versions do not, though work has started in its development branch, and the separate LNDK project, still experimental, adds offers to an LND node.
See Lightning Channel for the building block, and Journey: Using Bitcoin for the practical user view.
Key takeaways
- Solves high on-chain fees and slow confirmations for everyday payments
- Uses payment channels to batch transactions off-chain
- Relies on a global network of LN nodes interconnected by routes
Related chapters
Corrected
-
Was: The entry's note on BOLT 12 offers said they support recurring payments.
Now: Offers were merged into the Lightning specification in September 2024 without the built-in recurring payments of earlier drafts. An offer can be reused because each payer's wallet uses it to ask for a fresh invoice. Details
Sources (5)
- BOLT #12 - Negotiation Protocol for Lightning Payments (offers)
- BOLTs PR #798 - Offers (merged September 2024)
- Bitcoin Optech - Offers (topic page and implementation history)
- LND 0.22.0 release notes (in development) - first BOLT 12 code
- LNDK - standalone daemon that adds BOLT 12 offers to LND (experimental)
External references (3)
Related terms (36)
- Atomic Multi-Path Payment (AMP)
- Audiobook Model (Lightning)
- Autopilot (Lightning)
- BOLT
- BOLT 11
- Bridge Node (Lightning)
- Churn (Lightning)
- Core Lightning (c-lightning)
- Custodial Lightning Wallet
- Delayed Payment Channel
- Eltoo
- Escrowed Lightning Channel
- Fraudulent Channel Close
- Gossip Protocol (Lightning)
- HTLC (Hashed Time-Locked Contract)
- HTLC Invoice
- HTLC Preimage Manager
- Jamming Attack (LN)
- Jammed HTLC Detector
- Lightning Channel
- Lightning Channel Capacity
- Lightning Channel Splicing
- Lightning Invoice
- Lightning Network Daemon (lnd)
- Lightning Node
- Lightning Payment
- Lightning Probe
- Lightning Refund Invoice
- Lightning Routing
- Lightning Sphinx
- Micropayment
- Off-Chain
- Onion Routing (Lightning)
- Payment Channel
- Submarine Swap
- Wumbo Channels (Lightning)
Published . Revised . One correction logged for this page.
Edit this page on GitHub