L2SOURCE-LED ANSWER
How does the Bitcoin Lightning Network work?
From payment channels and liquidity to routing, invoices and on-chain enforcement.
Lightning moves bitcoin through payment channels without publishing every payment to the blockchain. Participants update signed channel states; routed payments use conditional contracts so intermediaries cannot simply take the funds. Bitcoin’s base layer remains the court of final settlement.
Payment Channel — A channel locks bitcoin on-chain
Two parties create an on-chain funding output and exchange newer signed states that divide the locked amount differently. Unilaterally publishing the current commitment starts closure; payouts may wait for timelocks and confirmations.
Payments can cross several channels
A sender does not need a direct channel with the recipient. Nodes forward a conditional payment along a route. The recipient reveals a secret that completes the linked conditions, while timelocks protect participants if the route fails.
Liquidity is the central operating constraint
A channel can send only from the balance available on its outgoing side and receive only into available inbound capacity. Wallets hide some complexity, but routing, backups, uptime and channel management remain real trade-offs.
A channel begins with a real Bitcoin output
Opening a channel creates an on-chain funding transaction whose output can be spent only under the channel’s agreed script. The parties then exchange commitment transactions that divide that fixed balance. Lightning does not create additional bitcoin; it changes who can claim the locked bitcoin under enforceable conditions.
New signed states replace publication of every payment
A payment updates the channel balance by exchanging new signatures instead of broadcasting a transaction. The protocol makes old states dangerous to publish through revocation and penalty mechanics used by today’s commitment design. Either party retains a path to close unilaterally if cooperation stops.
HTLCs connect channels into an atomic route
A sender does not need a direct channel to the receiver. HTLC (Hashed Timelock Contract) agreements make each hop’s payment conditional on the same secret, with decreasing timeouts along the route. The receiver reveals the preimage to claim the final hop, enabling every intermediary to claim its incoming hop; otherwise funds can be reclaimed after the relevant timelocks expire.
Onion routing limits what intermediaries learn
The sender wraps instructions in layers so each forwarding node normally learns only its predecessor, successor, amount to forward and timing data. This improves privacy but does not create perfect anonymity: timing, channel balances, endpoint behavior and network observation can still leak information.
Liquidity is capacity in a direction, not a global balance
After opening a channel with all funds on your side, you can send but initially cannot receive through that channel. Receiving moves balance toward you and creates future outbound capacity; sending does the reverse. Wallets use channel selection, splicing, swaps, liquidity services and multi-part payments to manage this constraint, always with some fees and trade-offs.
Routing can fail without anyone stealing funds
A route may lack capacity, fees may exceed the payer’s limit, a node may be offline or channel information may be stale. Wallets retry alternative paths, sometimes splitting a payment. Fast everyday success is an emergent network property, not a guarantee that every invoice always completes.
Wallet design determines the user’s custody model
A self-custodial Lightning wallet gives the user enforceable channel claims but must manage backups, chain monitoring and emergency fees. A custodial wallet can hide all channel operations while making the provider the actual controller of funds. The Lightning label alone does not reveal who holds the keys.
Lightning is not a separate coin and not a promise to settle later in an unrelated system. Its channel claims are constructed so disputes can ultimately be enforced with Bitcoin transactions.
01Are Lightning payments recorded on Bitcoin?+
Channel opening and eventual settlement are on-chain. Individual intermediate balance updates normally remain off-chain unless a dispute or close requires publication.
02Are payments final instantly?+
A successful recipient can usually treat the fulfilled conditional payment as final within the channel system, while ultimate dispute enforcement remains anchored to Bitcoin and its confirmation process.
03Can I receive without inbound liquidity?+
Not through a route that has no capacity moving toward you. A wallet may obtain inbound capacity through spending, swaps, a liquidity provider or a peer opening a channel.
04Is Lightning always self-custodial?+
No. Both self-custodial and custodial wallets use Lightning. Check who controls the keys and whether you can close or withdraw without the provider’s permission.