What is Bitcoin's Lightning Network?

Bitcoin is the most secure monetary network ever built. It's also, by design, not built for speed. The base layer confirms a new batch of transactions every 10 minutes and can handle roughly 7 transactions per second globally. Visa processes around 1,700 per second. For large settlements and long-term savings, Bitcoin's deliberate slowness is a feature. For paying for your morning coffee, it's a problem.

The Lightning Network was built to solve this. And in November 2025, it crossed $1.17 billion in monthly transaction volume for the first time, a quiet milestone that most people outside of Bitcoin barely noticed.

Here's what Lightning actually is, how it works, and why it matters.

Why Bitcoin needed a second layer

Bitcoin's blockchain is a public ledger. Every transaction ever made is recorded on it permanently. Every full node on the network downloads and verifies every transaction. This is what makes Bitcoin trustless and resistant to tampering: there's no central server to hack, no company whose database can be altered, no authority who can reverse a transaction.

But that design comes with a hard constraint. You can't record every coffee purchase, every streaming micropayment, every cross-border remittance on a public ledger that every computer on Earth has to verify. The network would be overwhelmed. Bitcoin's block size is deliberately limited to keep node operation accessible to ordinary people worldwide. If running a node required a data center, only corporations would do it, and the decentralization that makes Bitcoin valuable would erode.

So the solution wasn't to change Bitcoin's base layer. It was to build on top of it.

This is the same model that underpins most of the financial world. Your bank doesn't record every card swipe on a government ledger. It maintains its own books and periodically settles net balances with other banks. Lightning applies this logic to Bitcoin, while preserving something banks cannot offer: neither party can cheat, because the rules are enforced by cryptography, not by trust in an institution.

How payment channels work

The core building block of Lightning is the payment channel. Understanding channels is understanding Lightning.

Here's the simplest version. Suppose Alice and Bob transact with each other frequently; maybe Bob runs a coffee shop Alice visits every morning. Instead of broadcasting every coffee purchase to the entire Bitcoin network, they open a payment channel between them. This involves one on-chain transaction to lock up some funds. Think of it as both parties putting money into a shared safe.

One on-chain transaction to open. Unlimited transactions in between. One on-chain transaction to close. If Alice bought a coffee every day for a year, that's 365 purchases settled with just two on-chain fees.

The cryptographic magic that makes this safe is a system called Hash Time-Locked Contracts (HTLCs). At any point during the channel's life, either party can close it unilaterally by broadcasting the most recent signed state to the blockchain. The protocol makes it economically irrational to cheat: if Alice tried to broadcast an old state (one where she has more bitcoin than she actually does), Bob's software would catch this and claim all the funds as a penalty. Lightning nodes watch for this automatically.

Routing: transacting with people you don't have a channel with

Payment channels between two people are useful but limited. The real power of Lightning is what happens when channels connect into a network.

Suppose Alice has a channel with Bob, and Bob has a channel with Carol. Alice can pay Carol through Bob, without opening a direct channel with Carol. Bob acts as a routing node, forwarding the payment and earning a tiny fee for doing so.

This is why the network topology matters. As more nodes and channels are added, more payment paths become available. A payment from Alice in London to a merchant in Buenos Aires might route through three or four hops in milliseconds, with each routing node earning a small fee (often fractions of a satoshi) for their role.

The security mechanism that makes multi-hop routing trustless is also HTLCs. The payment is structured so that each intermediate node can only collect its fee if the payment reaches the final recipient. Nobody along the route can steal the funds. The math guarantees it.

Lightning in numbers

As of early 2026, the Lightning Network has grown significantly from its experimental early days. The numbers paint a picture of a network that has moved from proof-of-concept to genuine infrastructure.

That $1.17B figure deserves context. It's not a speculative market cap or a theoretical ceiling. It represents actual payments that cleared through Lightning in a single calendar month: remittances, purchases, micropayments, salary payouts, and more. Three years prior, monthly volume was a fraction of that. The trend line is clear.

What Lightning is actually used for

Lightning use cases have expanded well beyond the "coffee payment" thought experiment that launched a thousand conference slides.

Remittances are one of the most compelling real-world applications. Sending money from the United States to El Salvador, the Philippines, or Nigeria through traditional services typically costs 5–10% in fees and takes days. Lightning makes the same transfer in seconds for less than a cent. For people sending small amounts home regularly, this is a meaningful difference in their actual lives.

Micropayments, payments too small to be practical on any traditional payment rail, become viable on Lightning. Fractions of a cent can be sent programmatically. This enables entirely new models: pay-per-article reading, streaming payments where you pay by the minute rather than the month, tipping creators fractions of a cent as you scroll. None of these work on Visa or on Bitcoin's base layer. Lightning makes them economical.

Bitcoin payroll and rewards are growing. Companies in high-inflation economies pay workers in Bitcoin over Lightning, bypassing the local banking system entirely. Loyalty programs are being built where points are replaced with actual satoshis (fractions of a bitcoin) that users can spend or save.

Machine-to-machine payments are an emerging frontier. As AI agents and IoT devices proliferate, Lightning provides a native payment layer for software to pay software (routing fees, API calls, compute costs) without any human involvement.

Is Lightning safe?

Lightning is cryptographically robust. The HTLC mechanism means neither party can steal from the other, and the penalty system means cheating attempts are economically self-defeating. But "safe" involves tradeoffs worth understanding honestly.

Your funds are hot while in a channel. Bitcoin held in a Lightning channel is, by design, accessible quickly. That's what makes instant payments possible. This is different from holding bitcoin in cold storage, where the private key never touches an internet-connected device. For day-to-day spending, this is acceptable. For large savings, it's not the right tool.

You need to be online. A fully self-sovereign Lightning node needs to be online to monitor channels and route payments. If your node goes offline for an extended period, a malicious channel partner could theoretically try to close the channel with an outdated state. Watchtower services exist to monitor channels on your behalf, but it adds complexity.

Channel liquidity matters. A payment can only route through a path if each hop has enough bitcoin on the right side of its channel. In a young, growing network, this can occasionally cause payment failures. Routing has improved dramatically as the network has matured, but it's not identical to the reliability of, say, a Visa payment.

For most practical purposes (spending bitcoin regularly, sending remittances, experimenting with micropayments), Lightning works well. The software has improved enormously since the 2018 mainnet launch, and custodial Lightning wallets (where a service handles the channel management for you) have made it accessible to non-technical users.

Lightning vs. other "fast" payment systems

Lightning is sometimes compared to existing fast payment rails: Visa, PayPal, M-Pesa, UPI. The comparisons are instructive but imperfect.

Visa is fast and reliable, but it's also a closed network owned by a company that can and does decline transactions, charge merchants 1.5–3% per sale, and exclude users and businesses it deems undesirable. Lightning is a protocol. There's no company that can terminate your access to it.

M-Pesa and UPI work brilliantly within their geographic and currency constraints. Neither can easily route a payment from Kenya to Argentina without going through a chain of correspondent banks. Lightning is a single global protocol. A payment from Lagos to Los Angeles routes through the same network as a payment across the street.

The comparison that matters most isn't speed. Many payment systems are fast. It's the combination of: open access, final settlement in a censorship-resistant asset, near-zero fees, and programmability. No existing payment rail offers all four.

The road ahead

Lightning is still maturing. User experience remains a genuine barrier for non-technical users managing their own channels. Routing reliability, while improved, can still fail on large payments. And the network's public channel graph represents only part of the actual payment volume. Significant Lightning usage happens through custodial wallets and enterprise rails that don't appear in on-chain or public node data.

Protocol improvements are active. Taproot Assets (formerly Taro) is a protocol that lets other assets (stablecoins, other currencies) be issued on Bitcoin and transferred over Lightning. This could significantly expand Lightning's use case from purely bitcoin payments to a global value-transfer layer for any asset. Early deployments are live as of 2026.

Splicing, the ability to add or remove funds from a channel without closing it, is being implemented across major Lightning implementations. This makes channel management far more flexible and reduces the friction of maintaining adequate liquidity.

The network that just crossed $1 billion in monthly volume is not the finished product. It's a version of the finished product that already works well enough for millions of people to use it for real money.

Common questions

Do I need to run a node to use Lightning?

No. Custodial Lightning wallets like Wallet of Satoshi or Strike handle all the channel management for you. You download an app, fund it with bitcoin, and you can send and receive Lightning payments immediately. The tradeoff is that you're trusting the service with your funds, the same way you trust a bank. For small day-to-day amounts, most people find this acceptable. For larger holdings, self-custody is worth learning.

What's the maximum payment size on Lightning?

In practice, Lightning is best suited for smaller payments: from fractions of a cent up to a few thousand dollars. Very large payments are possible but require significant channel liquidity and can struggle with routing. Large bitcoin transfers are still generally handled on-chain, where fees are a tiny percentage of a multi-bitcoin transaction rather than the whole economics of a coffee purchase.

Can Lightning payments be reversed?

No. Lightning payments are final, like cash. Once the payment settles (which happens in milliseconds), it cannot be reversed by any party. This is a feature for recipients and merchants who want to eliminate chargebacks, and it's a reason to be careful sending Lightning payments to the wrong address. There is no customer service line to call.

Is Lightning the same as Bitcoin?

Lightning is a second-layer protocol built on top of Bitcoin. All funds on Lightning are bitcoin. There is no separate "Lightning coin." The underlying asset is always BTC. Lightning is just a way of moving it faster and cheaper, with the security guarantee that you can always fall back to the Bitcoin base layer to settle your final balance.

The bottom line

Bitcoin's base layer is optimized for security, immutability, and decentralization. It was never meant to process millions of retail transactions per second. The Lightning Network is the answer to that constraint: a second layer that handles everyday payments at internet speed, settled in bitcoin, with no intermediary capable of stopping or reversing them.

It crossed $1 billion in monthly volume in November 2025. It will cross multiples of that as the infrastructure matures, as wallets improve, and as more of the world's financial activity searches for rails that don't require a bank account, a company's approval, or a 3% toll.

Lightning is not competing with Bitcoin. It's what makes Bitcoin practical at scale.

Want to go deeper? Read our issue on the month Lightning crossed $1 billion, including the River data behind the milestone. Or read our explainer on what Bitcoin is for the foundation that Lightning is built on.