What is the Lightning Network? Bitcoin's instant payment layer

The Lightning Network is a payment layer built on top of Bitcoin. It lets you send bitcoin in seconds, for a fraction of a cent, without waiting for a block to confirm. Rather than writing every payment to the blockchain, two people open a private channel between them, pay each other as many times as they like, and record only the final balance on-chain later.

Think of the base chain as a courthouse and Lightning as a bar tab. You settle the tab at the end of the night with one entry in the ledger, not a fresh receipt for every drink. That single idea is what lets Bitcoin handle the small, everyday payments that would otherwise clog and overprice the main chain.

How the Lightning Network works

Lightning runs on payment channels. A channel is a shared wallet between two people, funded by a single Bitcoin transaction that both of them sign. Say you and a coffee shop each lock in some bitcoin. That opening transaction hits the blockchain once. After it confirms, the two of you can update who owns what inside the channel as often as you want, and none of those updates touch the chain. Each payment just shifts the balance from one side to the other.

Each update is a fresh balance sheet, signed by both sides. Only the newest one counts. If either party tries to cheat by broadcasting an old balance, Bitcoin's own scripting rules let the other side sweep the funds as a penalty. That threat is what keeps both people honest without a middleman holding the money.

Closing the channel is the final step. When either side is done, they settle, and the last agreed split gets written back to the blockchain in one transaction. Open once, pay a thousand times, close once. Only two of those events ever cost an on-chain fee, no matter how many payments happened in between.

How a payment travels across the network

You do not need a direct channel with everyone you pay. Channels link up into a web, and a payment can hop across several of them to reach someone you have never dealt with. If you have a channel with a wallet app, and that app has a channel with the coffee shop, your payment can route through the app. The nodes in the middle simply pass it along and never hold it.

Those hops are secured, not trusted. Lightning uses onion routing, the same technique behind privacy tools on the internet, so each node in the path learns only the next step and nothing about the full route. A cryptographic contract called an HTLC locks every hop until the whole payment either completes end to end or fails and unwinds cleanly. No node can grab it. All or nothing.

Routing nodes earn a small fee for forwarding your payment, which is part of why people run them. A path only works if every channel along it has enough balance pointing the right way. When one does not, the payment fails and your wallet quietly tries another route before you even notice.

Where Lightning came from

Two engineers, Joseph Poon and Thaddeus Dryja, laid out the design in a 2015 paper that asked a plain question: how could Bitcoin handle coffee-sized payments at scale. The main chain confirms a new block about every ten minutes and fits only a handful of transactions per second. Their answer was to push the small, frequent payments off-chain and keep the base layer for opening and closing channels, where its security matters most.

Growth has not been a straight line. Developers launched the network on Bitcoin mainnet in 2018, and public capacity climbed for years as wallets, exchanges and payment firms plugged in. It has also dipped during quiet stretches and after large operators reshuffled their channels. The network expands and contracts with real demand rather than rising forever, which is a healthier sign than endless hype would be.

Bigger players arrived as the tooling matured. Lightning service providers, known as LSPs, now open channels on a user's behalf and supply inbound capacity, so a newcomer can receive a payment within minutes of installing a wallet. Mobile apps hide the channel management entirely. That shift, from a tool for hobbyists into something a shop or a sender can use without reading a manual, is the quieter story behind the raw capacity numbers.

What the Lightning Network looks like today

Anyone can measure part of the network, because public channels announce themselves. As of 1 October 2026, the mempool.space Lightning dashboard showed about 3,753.80 BTC of public capacity spread across 32,518 channels and 16,230 nodes, with an average channel holding roughly 11.5 million satoshis, around 0.115 BTC. Capacity is the total bitcoin locked in channels, and it sets a rough ceiling on what the network can move at any one moment.

These figures miss a lot. Private channels never announce themselves, so the real network is larger than any dashboard can show. A handful of exchanges and payment companies run some of the biggest nodes, which concentrates liquidity in relatively few hands. Node counts also drift up and down as operators join and leave, so a single snapshot is a rough guide, not a fixed score.

What it costs and how fast it is

Speed is the headline. A Lightning payment usually settles in under a few seconds, because it never waits for a block. Fees are tiny too. The routing nodes charge a small base fee plus a percentage of the amount, which on a normal payment often adds up to less than a single cent. Streaming a few sats to a podcast costs almost nothing.

Compare that to the base layer. An on-chain Bitcoin transaction waits for confirmation, which can stretch from minutes to hours when blocks are full, and the fee is roughly the same whether you send five dollars or five thousand. Lightning flips that math for small sums. Buying a coffee on-chain can cost more in fees than the coffee itself. On Lightning it rounds to nothing.

Size changes the picture, though. Lightning suits small and medium payments, not a single large transfer that no channel can hold. For a very large amount, the base chain is still the cheaper and simpler route. Match the layer to the payment and the choice tends to make itself.

What people use it for

Micropayments are the obvious fit. Lightning makes it practical to send amounts so small that on-chain fees would swallow them whole. People use it to tip writers, pay for a single article, stream sats by the second to a podcast, or settle tiny bills between apps. If you are new to bitcoin, it helps to learn how to buy it safely before loading a Lightning wallet for the first time.

Exchanges and wallets lean on it for cheap, fast deposits and withdrawals. Remittance apps use it to move money across borders in seconds rather than days, which matters most to people sending wages home. Point-of-sale tools let shops take bitcoin without the wait of a block confirmation. The common thread is speed and low cost on payments that would be clumsy or expensive on the main chain.

The trade-offs before you use it

Faster and cheaper comes with strings. Your bitcoin has to sit in channels, funded and reachable, before you can spend it. To receive a payment you need inbound capacity, which means room on the far side of a channel, and that trips up newcomers who open a channel and then find they cannot be paid into it yet.

Payments can still fail. If no route between you and the recipient has enough liquidity along every hop, the payment bounces back and you try another path or a bigger channel. Opening and closing channels are on-chain transactions, so they cost a normal fee and take time to confirm. And if your node drops offline while a channel is open, a dishonest partner could try to broadcast an old balance, which is why some people use watchtower services that watch for cheating on their behalf.

None of this makes Lightning fragile for everyday spending, but it does reward users who understand how their money is held. Custodial wallets hide the plumbing by managing channels for you, at the cost of trusting a company with your coins. Self-custody hands you control and the homework that comes with it. Where your keys live matters here, the same question behind the choice between a hot wallet and a cold wallet.