Bitcoin Lightning Network: 2026 Adoption vs Promise 🚀
Discover 2026 Bitcoin Lightning Network adoption vs promise: usability, Bitcoin payments, custody claims, and non-custodial crypto wallets—what it takes to succeed.

Bitcoin Lightning Network: Adoption vs. Promise
Bitcoin's Lightning Network: Progress Is Not the Same as Adoption
The Lightning Network was supposed to make Bitcoin practical for fast, low-cost payments. The core idea is straightforward: move routine payments off Bitcoin's base layer into payment channels, then settle channel openings and closings on-chain. The real question is whether this works smoothly for everyday people - outside the usual crypto bubble.
That question flared up again after Bitcoin developer Paul Sztorc argued that the community is overstating Lightning's usability and that custodial services handle most payments. The "most payments" claim can't be confirmed from public network data, because Lightning payments are private and outsiders can't reliably observe how custody is split. Still, his broader point lands: technical activity - capacity growing, volume moving, developers building - doesn't automatically mean the average user has a simple, reliable payment experience.
This article separates those issues. We'll look at where Lightning is genuinely easier or harder to use, what recent activity figures can and can't tell you, and a practical way to judge whether the network is meeting its promise. The goal isn't to declare Lightning a failure or a breakthrough. It's to spell out what evidence would actually support either conclusion.
Why Lightning's Promise Is Still Contested
Lightning is a payment network that runs on top of Bitcoin. Instead of recording every payment directly on the blockchain, participants transact through payment channels. The base layer stays important for opening and closing channels, while payments inside channels can be faster and cheaper than on-chain transactions.
That design solves a real bottleneck. Bitcoin's base layer isn't built to handle every small purchase from everyone all over the world. But shifting payments off-chain brings its own constraints. A payment has to find a route through connected participants, and that route needs enough available liquidity in the right direction. It's not enough for liquidity to exist somewhere on the network; it has to be reachable along the path the payment takes.
This is why Lightning, historically, has felt more involved than tapping a card. Users may need to manage channels, ensure enough inbound or outbound liquidity, or troubleshoot failed routes. That's manageable for operators and technically comfortable users - but it's friction for someone who just wants to open a wallet and pay for coffee.
Sztorc's criticism is blunt. He claimed that people have been misled about Lightning's quality and that custodial services account for more than 80% of payments. His Theranos comparison is an accusation, not a measured finding. And because Lightning payments are private, public data can't be used to establish a custody share with confidence. The source report also says Sztorc didn't respond to the publication's requests for comment.
The limitation cuts both ways. It means the "80%" figure isn't proven - but it also means the opposite claim can't be proven from public network observations either. Privacy is a feature, not a bug, but it makes sweeping adoption claims harder to verify. If someone wants to cite a precise custody estimate, they should be ready to show how the estimate was produced and what data it depends on.
There's another source of confusion: people mean different things by "success." A developer might care whether the protocol can route a payment. A business might care whether payments are cheap and easy to accept. A user might care whether paying "just works," without learning what channels or liquidity are. Those outcomes are related, but they aren't interchangeable.
So the real issue isn't whether Lightning can work at all. It's whether it's reliable and simple enough for the use cases its advocates have pointed to - and whether the evidence actually measures those outcomes instead of just counting technical activity.
Has Lightning Become Easier to Use?
Lightning's critics usually point back to earlier years, when users dealt with channel setup, liquidity management, and routing mechanics. That history matters, but it doesn't automatically describe what users get today.
Over time, developers and infrastructure providers have moved more of the day-to-day operational work away from end users. A wallet can lean on external services for liquidity, routing, and channel management. Some users no longer need to run their own node or manually configure channels just to send a Lightning payment. From the user's side, the experience can start to resemble a conventional mobile wallet.
Danny Stagg, marketing lead at Breez, argued that some criticism reflects an older version of the user experience. He said non-custodial usability has improved as infrastructure has abstracted away channel and liquidity complexity. That's a meaningful shift: self-custody doesn't have to mean every user manually managing the underlying network.
But abstraction doesn't erase complexity. It shifts it to someone else, and it changes what the service depends on. A wallet can still be non-custodial while relying on infrastructure providers to route payments smoothly. That can be perfectly reasonable, but it introduces dependencies that should be understood and disclosed. "Non-custodial" tells you who controls the funds; it doesn't fully describe the service's reliability, privacy, or availability story.
The trade-off here will look familiar to anyone who's followed fintech: custodial services can make onboarding and recovery easier because an intermediary handles more of the workflow. The cost is trust - in that intermediary's security, uptime, and policies. Non-custodial services can offer more direct control, but recovery and continuity may be less forgiving. This isn't about which model is "better" in a moral sense. It's about which one fits the user and the use case, and whether the trade-off is clearly communicated.
Lightning infrastructure provider Amboss CEO Jesse Shrader acknowledged that liquidity can be hard to understand, while also saying tools and automation can make it easier to manage. Amboss simulations put the success rate for payments of around $100 at 99.66%. That's an encouraging technical benchmark, but it's still a simulation - not an independently verified, network-wide measure of what every user experiences in real shops, with real wallets, across different regions.
Real payments also involve more than successful routing. A person needs a wallet they can trust, a way to acquire and hold funds, a merchant willing to accept Lightning, and a clear process for what happens when something goes wrong. In the US and UK, card terminals and contactless payments are already embedded in everyday commerce. Lightning has to compete with that whole experience, not just demonstrate that a payment can settle quickly.
So, has Lightning improved? There's evidence for better abstraction and developer tooling. That supports a narrower claim: using Lightning may be simpler than it used to be. It doesn't, by itself, prove Lightning is ready for mainstream usability. To really judge it, you have to look across the whole journey - from funding a wallet to completing a payment and handling failures.
What the Adoption Numbers Actually Show
Adoption data can be useful, but only if you're clear about what each number is measuring. It becomes misleading when transaction volume, capacity, payment counts, and user experience get blended into one "score."
River's 2026 Bitcoin adoption report estimated that Lightning processed $1.17 billion in transaction volume across 5.22 million transactions in November 2025. Those figures point to real activity. What they don't answer is how many unique people used the network, how often they returned, whether payments were consumer purchases or transfers between services, or how many payment attempts failed before one succeeded.
The report also noted that the November transaction count was below an August 2023 peak of 6.6 million. Tracking that kind of change is reasonable, but it needs context. A lower transaction count alongside higher value moved could reflect different payment sizes, different mixes of activity, or changes in how people are using the network. It doesn't automatically mean adoption is rising or falling. The underlying data and method are what determine what conclusions you can responsibly draw.
CoinGate, a crypto payment processor, reported 782,403 paid crypto orders across its customer base in the first half of 2026, up 21.4% year over year. Lightning accounted for 9.6% of the Bitcoin payments processed through its service. This tells you about activity on one processor, not the entire market. It also reflects payments accepted by merchants using that processor, not all Bitcoin users or all possible merchants.
Other commonly cited measures have similar limitations:
- Network capacity: how much value channels can hold. It doesn't tell you how often funds move or whether users can route a payment when they need to.
- Transaction volume: the value transferred. It may not distinguish retail purchases from business transfers or other types of activity.
- Transaction count: payment events. It doesn't tell you the number of people, repeat use, or unsuccessful attempts.
- Developer interest: a sign that tooling is improving. It isn't proof that customers have adopted the products.
- Payment success rate: useful only if the sample, payment size, routing conditions, and measurement method are clear. A simulation isn't the same as a measured, universal real-world rate.
Privacy adds another complication. Because Lightning payments are designed not to be publicly recorded like on-chain transactions, there isn't a straightforward public ledger that reveals every payment and its custody setup. Network analytics can offer partial views, and payment providers can share data from their own systems. Neither should be presented as a complete census of the network.
That's why one headline number rarely settles the debate. A billion dollars in volume may matter for infrastructure, but a consumer deciding whether to use Lightning also needs to know whether payments work at the point of sale. A developer deciding whether to integrate Lightning needs to understand implementation cost, support burden, and whether customers are actually asking for it. A merchant needs to know settlement behavior, accounting, and refund handling.
The numbers aren't useless. They're evidence - but evidence for specific claims. River's estimate supports the idea that substantial value moved through Lightning in the period it covered. CoinGate's numbers describe activity in CoinGate's processing business. Neither, on its own, proves that everyday users adopted Lightning at scale - or that they haven't.
A Better Framework for Judging Success
A more useful way to assess Lightning is to separate the system into four layers: technical performance, user experience, merchant utility, and durable adoption. Each layer answers a different question. A win in one area doesn't automatically cover up a weakness in another.
1. Technical performance
Can users complete payments reliably under realistic conditions? Better reporting should include payment amounts, routing conditions, geography, wallet types, failure definitions, and whether results are simulated or observed. A single average can hide meaningful differences: smaller payments may route well while larger payments fail, and performance may vary by wallet and liquidity conditions.
For product teams, that means measuring the full payment flow - not just successful settlements. Track failed attempts, retries, time to completion, support requests, and how often a user has to take an unexpected action. Those are closer to the real operational experience than channel capacity alone.
2. User experience and control
Can someone receive, hold, and spend funds without needing to understand how the network works internally? Does the wallet explain who controls the funds, what external services it depends on, and how recovery works? Can users tell the difference between a temporary service outage and a problem with their own wallet?
This is where the custody debate belongs. The label matters, but the full service design matters too. If a product relies on a provider for connectivity or liquidity, say so. If it gives users direct control, spell out recovery responsibilities. A product shouldn't imply that removing a custodian eliminates every operational trade-off.
3. Merchant utility
Can a business accept Lightning without adding more cost and friction than the payment channel removes? Merchants think about processing fees, settlement timing, point-of-sale integration, exchange-rate exposure, bookkeeping, refunds, and customer demand. Being technically able to accept Lightning is only part of the decision.
This comparison should be made against the merchant's real alternatives. In many US and UK businesses, contactless card acceptance is already fast and familiar. Lightning needs a clear advantage for a particular merchant or customer segment - maybe settlement characteristics, payment economics, or cross-border use - so adding another workflow is actually worth it.
4. Repeat use and adoption
Do people come back to use Lightning for a real job, and do businesses keep accepting it after a trial? Better indicators connect payment activity to repeat users and merchants over time, and explain how the data is collected and what's excluded. Because privacy limits public measurement, providers may be able to share narrower datasets more transparently instead of pretending they can produce an unknowable network-wide total.
A practical scorecard should ask:
- What exact claim is being made: capacity, volume, reliability, ease of use, or adoption?
- What data supports it, and who collected it?
- Is the result observed, estimated, or simulated?
- Which users, payment sizes, wallets, and regions are included?
- What does the metric leave out, especially failures and repeat use?
- What trust or infrastructure trade-offs does the product require?
This framework avoids two unhelpful extremes. Lightning isn't proven simply because payments can be routed and developers are building tools. It also isn't disproven just because some users still hit friction - or because other payment networks show more activity. The right conclusion depends on the claim, the use case, and the evidence.
The conclusion: judge the experience, not the slogan
Lightning appears to have made real technical and product progress. Infrastructure can hide more of the complexity, and reported activity suggests the network is being used. At the same time, public data can't settle the custody share, simulations aren't universal benchmarks for real users, and transaction volume doesn't tell you how effortless the payment experience feels.
For builders, the test is simple: evaluate Lightning with the same discipline you'd apply to any payment system. Run tests with real users, real amounts, real failure scenarios, and real merchant workflows. For readers weighing adoption claims, start by asking what the metric is actually measuring before treating it as proof.
The key distinction is between what Lightning can do and what people reliably do with it. Until those are measured separately, both the strongest criticisms and the most confident adoption claims deserve scrutiny. For more context, see the original report on the Lightning Network debate.
Final Takeaway
Lightning shouldn't be judged by its original promise or by the loudest critics. The useful test is whether it delivers reliable payments for specific users and use cases, with trade-offs that are actually visible and acceptable. If you're evaluating a wallet, an integration, or an adoption claim, start with the real user journey and the quality of the evidence - not a single headline metric.