Lightning Network
Fast Bitcoin payments using off chain channels.
The Lightning Network is a payment protocol built on Bitcoin that enables fast, low-cost transfers through off-chain payment channels. Participants update channel balances without placing every payment in a Bitcoin block. Opening and closing channels uses base-layer transactions, preserving a route to Bitcoin settlement.
A channel locks bitcoin under rules agreed by its participants. They exchange signed states representing the latest balance allocation. Outdated states are discouraged through enforcement mechanisms, so users or monitoring services need appropriate awareness of the chain. Modern wallet designs manage much of this complexity but do not remove backup and software risk.
Payments can travel through several connected channels. Hashed time-locked contracts coordinate the route so intermediaries either forward value under the conditions or the payment fails. A sender does not need a direct channel with the recipient. Routing nodes may earn small fees for providing liquidity and forwarding capacity.
Lightning matters because Bitcoin base-layer space is scarce and confirmation takes time. Channels support small, frequent payments, tips, commerce, and transfers that would be uneconomic on-chain. Privacy can improve because every payment is not written publicly, although routing nodes, wallet providers, timing, and network observation can still reveal information.
Liquidity must exist in the needed direction. A channel balance can send only from its available side, and receiving larger payments may require inbound liquidity. Payments can fail even when the user has enough total bitcoin. Channel management, route fees, on-chain opening cost, and node uptime affect reliability.
Wallet choice determines custody and responsibility. Custodial services simplify recovery but control funds. Self-custody wallets require secure keys and channel backups. Users should start small, verify invoices and amounts, maintain current software, and understand recovery. Lightning offers efficient Bitcoin payments, not guaranteed routing, free transactions, or immunity from custody, liquidity, and operational failures.
Merchants should define invoice expiry, confirmation, refund, and accounting procedures before accepting Lightning at scale. A payment request is usually single-purpose and time-limited, so reusing old invoices can create errors. Operators should monitor channel capacity and keep enough on-chain bitcoin available for channel management when base fees rise.
Frequently asked questions
- Participants lock bitcoin in payment channels through an on-chain transaction, then exchange signed balance updates without recording each payment on Bitcoin. Hashed time-locked contracts allow payments to route across several channels without trusting every intermediary. A later close settles the final channel state on-chain. Security depends on correct wallet operation, monitoring, liquidity, and backup design.
- No. Custodial Lightning wallets manage channels and keys for users, while self-custody wallets can automate much of node and channel management. Running a node provides greater control, privacy, and routing choices but requires uptime, liquidity, backups, software updates, and fee management. The right approach depends on payment value and the user's operational ability.
- Payments can fail from insufficient route liquidity, offline nodes, fee limits, or invoice problems. Users also face wallet bugs, lost recovery data, channel backup issues, custodial failure, phishing, and on-chain fee spikes when opening or closing channels. Keep balances proportionate, use reputable software, verify invoices, and understand whether the chosen wallet is custodial or self-custodial.