Lightning Network
A peer-to-peer network of Bitcoin payment channels that settles many updates off-chain and enforces final ownership on-chain.
LNSOURCE-LED TOPIC GUIDE
Explore payment channels, routing, inbound and outbound capacity, and the differences between self-custody and custodial services. Payment speed, cost and success depend on conditions.
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. 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 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. Routing nodes may charge base and proportional fees. Opening, closing and managing liquidity can add costs; Lightning is not always free or cheaper.
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. Unilateral closure may involve timelock delays, waiting for confirmations and paying base-layer fees. Linked entries have their own sources and reviews.
A curated path from first principles to the details that matter.
A peer-to-peer network of Bitcoin payment channels that settles many updates off-chain and enforces final ownership on-chain.
A two-party contract whose latest signed state reallocates locked bitcoin without publishing every update on-chain.
HTLC conditions payment on knowledge of a preimage and provides a timed path for returning funds. In Lightning it connects obligations across channels; expiry alone neither refunds the payment nor disables the preimage branch.
Lightning Routing selects one or more channel paths whose directional liquidity, forwarding policies and time constraints may deliver a particular payment.
Lightning liquidity is the directional amount a channel can currently send or receive, not its total advertised capacity.
BOLT 12 separates a published offer from requesting a specific invoice. A reusable QR code does not transfer money by itself.
Definitions, mechanisms, people and source data connected to this field.