Bitcoin’s Lightning Network: Is the ecosystem living up to expectations?

Bitcoin developers are once again debating whether the Lightning Network’s progress has translated into a payment experience that everyday users actually want. This time, the argument was sparked by Paul Sztorc, who described Lightning’s real-world usability as far worse than many in the Bitcoin community portray.

In an October 4 post on X, Sztorc claimed there is “a vast, years long” effort to mislead people about the Lightning Network user experience, arguing that custodial Lightning services handle more than 80% of payments. Because Lightning is designed to preserve privacy and runs in a way that doesn’t expose all payment details to outsiders, he acknowledged that proving custodial share from public network data alone may be difficult. Still, his remarks have resurfaced a longer-running question for Bitcoiners: has Lightning truly made Bitcoin easier to use, or has the ecosystem’s focus on Layer 2 capabilities outpaced mainstream usability?

Key takeaways

• Paul Sztorc argues Lightning’s user experience is worse than advertised and claims custodial services process over 80% of payments, but the privacy model limits what can be verified from public data.
• Lightning’s routing depends on liquidity and can fail, creating a different experience than traditional “tap to pay” systems.
• Infrastructure providers and Lightning-focused developers say usability has improved in recent years as wallet and app layers abstract away channel and liquidity complexity.
• Network-level metrics like transaction volume and capacity show activity, but they don’t directly measure how often payments succeed for typical users.

Why critics say Lightning still feels unlike “one-click” payments

Lightning was built to move transactions off the main Bitcoin blockchain so payments can be faster and cheaper, without requiring every transfer to be settled on-chain. But the mechanisms that make that possible introduce their own constraints—especially around how liquidity is provisioned across payment routes.

Unlike consumer payments that typically succeed through near-universal infrastructure, Lightning payments can require multiple hops through different nodes. If the network lacks sufficient capacity along the chosen path at the time of payment, transactions can fail or require retries. That reality clashes with the expectations created by traditional financial rails.

Lightning’s head of liquidity, Alex Bosworth, also weighed in this month, saying that “the painful truth” is that, in a setup combining privacy and peer-to-peer requirements, Lightning can be “extremely slow compared to tap to pay.” For Sztorc and others, this isn’t just an engineering detail—it’s the user experience.

The core friction, critics argue, is that managing a Lightning payment environment is technically demanding. Running a node, opening channels, and maintaining inbound liquidity are not tasks most users want to perform for routine spending. This is one reason custodial solutions—where a trusted intermediary handles routing and liquidity—have grown: they can provide a smoother “it just works” experience, but at the cost of introducing custody.

What success rates do data providers claim—and what users can’t verify

Jesse Shrader, co-founder and chief executive of Lightning infrastructure provider Amboss, acknowledged that liquidity requirements are “challenging” at first. However, he argued they are “trivial to solve” using existing tools or automation services.

According to Shrader, for “everyday payments of around $100,” most users can achieve roughly 99% reliability within the core network. Amboss simulations reportedly put success rate for $100 payments at 99.66%.

Yet even if those numbers are achievable in controlled settings, they are not the same as a confirmed measure of everyone’s experience across all environments. The article notes an important limitation: Lightning payments are private by design, which makes network-wide conclusions about real-world success and custody shares difficult to establish from public data alone—meaning “results may vary” in practical terms.

A separate thread from a Reddit discussion in April 2026 captured the skepticism many merchants and consumers express about everyday usage. The comment, while not presented as formal analysis, pointed to a basic practical problem: people don’t run Lightning nodes at points of sale, and standard retail payment workflows are still dominated by Visa or Mastercard terminals using NFC tap-to-pay. That gap between what the network can do and what businesses actually deploy remains central to the usability debate.

Developers argue the UX criticism is outdated—abstracted complexity changes the equation

Danny Stagg, marketing lead at Bitcoin payments infrastructure provider Breez, said that the strongest usability criticisms are “not fair in 2026.” He argued that for years, both users and developers were required to understand Lightning’s complexity—particularly concepts like channels and inbound liquidity—just to receive payments.

Stagg’s position is that the ecosystem has improved over the past two years as newer infrastructure abstracts away much of that operational work. In his framing, non-custodial user experiences are now “comparable” with custodial services, because wallet and application layers can handle routing and liquidity management underneath rather than forcing end users to do the heavy lifting.

Breez CEO Roy Sheinfeld also pointed to developer tooling as a factor, saying inquiries from potential partners increased and that more partners add Bitcoin “every quarter.” In practice, that may support a broader expansion of Lightning-enabled integrations—but the existence of developer interest still doesn’t prove mainstream adoption. The question remains whether these integrations deliver the same reliability and speed expectations that people associate with traditional payments.

Adoption metrics track activity—not necessarily usability or custody

Even as debate continues over user experience, there are measurable indicators of Lightning activity. According to River’s 2026 Bitcoin adoption report, Lightning processed $1.17 billion in transaction volume across 5.22 million transactions in November 2025 alone. However, the article highlights that this is still below Lightning’s August 2023 peak of 6.6 million transactions, suggesting that transaction counts may not be keeping pace with the value moving through the network.

Other payment data adds a partial view. CoinGate reported 782,403 paid crypto orders across its customer base in the first half of 2026, up 21.4% year over year. It also said Lightning accounted for 9.6% of Bitcoin payments processed through its service.

For investors and builders, the key point is how these figures should be interpreted. On the one hand, transaction volume, capacity, and service-level adoption show that Lightning infrastructure is active. On the other hand, none of these metrics alone can answer whether Lightning is easy and reliable for the average user, or whether custodial intermediaries dominate outcomes.

Shrader, in particular, rejected Sztorc’s claim that more than 80% of Lightning payments are custodial. He said he “distrust[s] anyone who claims they can prove an 80% custodial share either way from public data alone.” Stagg likewise suggested Sztorc’s criticism “describes yesterday’s Lightning,” when custodial offerings were easier and non-custodial UX hadn’t fully caught up.

Together, these positions underscore a tension that’s likely to persist: Lightning’s privacy and architecture make certain claims hard to verify publicly, while ecosystem improvements may be real but unevenly felt across users, merchants, and deployment models. Transaction volume and developer activity can rise even if mainstream usability lags.

What readers should watch next is whether the community can produce clearer, testable evidence about real-world payment reliability and custody usage—especially as newer wallet and payment layers continue to abstract Lightning’s complexity for end users.