The Bitcoin Lightning Network is a payment layer built above Bitcoin that moves frequent transactions away from the base blockchain. Rather than waiting for every individual payment to enter a Bitcoin block, participants exchange updated balances through payment channels anchored to the main network. The result is a system designed for fast, low-cost BTC payments without creating a separate cryptocurrency. A recent MetaMask educational guide describes Lightning as particularly suited to smaller and recurring payments where normal onchain confirmation and fee requirements can become inefficient.
A Lightning channel locks bitcoin into an arrangement jointly controlled by its participants. They can then exchange signed state updates reflecting how that bitcoin is divided without broadcasting each update to miners. Those offchain updates can occur repeatedly while the channel remains open, but they are constrained by the liquidity available within the channel rather than Bitcoin’s blockspace. Opening the channel requires an onchain transaction, and eventually closing it returns the final enforceable state to Bitcoin.
How Lightning Routes Bitcoin Without Onchain Transactions
Lightning does not require every sender to maintain a direct channel with every recipient. A payment can travel through multiple connected nodes, with the sender calculating a route across channels capable of carrying the required amount. This multi-hop architecture turns thousands of individual payment channels into a broader peer-to-peer payment network. Routing nodes can charge a base fee plus a proportional fee for forwarding successful payments.
Hashed Time-Locked Contracts, or HTLCs, coordinate those payments across multiple hops. The recipient reveals a cryptographic secret that allows the payment to complete, while time locks provide a path for funds to return if the necessary conditions are not met. HTLCs make routed payments atomic, meaning the payment either completes through the route or fails rather than leaving part of the amount stranded with an intermediary. Ideally, these contracts resolve between Lightning peers without requiring Bitcoin’s blockchain.
Routing also provides a degree of privacy. Lightning uses onion-encrypted routing so each intermediate node generally knows only where a payment arrived from and where it must go next, rather than seeing the entire path. The sender retains knowledge of the full route while individual forwarding nodes receive only the information needed for their hop. That does not make Lightning completely anonymous, but it creates a different visibility model from ordinary Bitcoin transactions recorded publicly onchain.
The infrastructure is increasingly available without requiring companies to operate every component themselves. BitGo, for example, has integrated managed Lightning payments into its Crypto-as-a-Service platform, with Voltage handling functions such as channel and liquidity management. That model illustrates how Lightning’s technical complexity can be abstracted from end users even though channels, routing and liquidity still exist underneath the interface.
Liquidity and Custody Define Lightning’s Trade-Offs
Lightning’s speed does not eliminate capital constraints. Every channel has finite liquidity in each direction, and a payment can fail when no route contains enough usable capacity. Multipath payments can divide larger transfers among several routes, but routing success still depends on network conditions. Lightning therefore scales payments by reusing committed liquidity rather than by making channel capacity unlimited.
Self-custody introduces another operational requirement. A participant needs to monitor the blockchain for attempts by a counterparty to close a channel using an outdated state. Watchtowers can perform that monitoring on the user’s behalf and broadcast a previously prepared penalty transaction when a breach is detected. Watchtowers reduce the need for a self-custodial user to remain continuously online, but they are a protective service rather than a prerequisite for every Lightning transaction.
Custodial Lightning wallets remove much of that channel-management burden but change the trust model because the service provider controls the underlying funds and infrastructure. Self-custodial implementations preserve direct control while placing more responsibility on software, backups and liquidity management. The user experience can look almost identical while the custody and security boundaries underneath it remain materially different.
Lightning consequently does not replace Bitcoin’s base layer. Bitcoin continues to provide the onchain transactions that establish and ultimately enforce channel balances, while Lightning handles repeated payments between those settlement events. Its core trade-off is straightforward: it exchanges some liquidity and operational complexity for dramatically faster payment execution and reduced reliance on scarce Bitcoin blockspace. That makes Lightning most useful as a payment network layered on Bitcoin rather than as an alternative to Bitcoin settlement itself.
Liam Foster follows crypto markets from France, with a close eye on Bitcoin, Ethereum, Layer 1 assets, derivatives, sentiment and smart money flows. His coverage looks past the daily price move to understand what is happening underneath: liquidity, leverage, positioning and the behavior of larger players.
Liam’s style is calm, sharp and deliberately anti-crystal-ball. He does not frame every market move as a breakout or collapse. Instead, he focuses on what the data can actually support, where traders may be crowded and when a signal deserves attention without becoming a prediction.
