The Bitcoin Lightning Network crossed 8,400 BTC in total channel capacity this month, an all-time high and a roughly 30% increase year-over-year. The capacity number is genuine. The interpretation that gets attached to it usually is not.
What the Capacity Number Actually Measures
Lightning's "network capacity" measures the total Bitcoin locked in payment channels. It is, at most, an upper bound on the network's payment-throughput capacity at any given moment. It is not a measure of usage, transaction volume, or economic activity routed through the network.
A meaningful share of that 8,400 BTC sits in channels operated by a small number of large nodes — exchanges, payment processors, and custodial wallet operators. River Financial, Strike, Cash App, Wallet of Satoshi, and a handful of others hold the bulk of capacity. Their channels are sized for operational headroom, not because they are routing through it continuously.
The peer-to-peer Lightning network — individual users running their own nodes, opening channels with each other, routing payments via gossip-discovered paths — remains a much smaller fraction of the total than the headline number suggests.
The Custodial Shift
The more important shift in the last 12 months is the consolidation of Lightning usage behind custodial frontends.
Wallet of Satoshi, which holds custody of user funds and routes Lightning payments on their behalf, is now the largest Lightning interface by transaction volume. Cash App's Lightning integration, similarly custodial, has driven a meaningful share of in-app Bitcoin volume. Strike's remittance business, which uses Lightning as a settlement layer between fiat sending and receiving endpoints, has scaled substantially.
In each case, the user-facing experience is custodial: the user does not run a Lightning node, does not manage channels, and does not see the routing complexity. The custodian operates Lightning infrastructure on the user's behalf and presents a simple "send Bitcoin" experience above it.
This is not what Lightning was originally designed to enable. The original Lightning vision emphasized self-custody, peer-to-peer channels, and trust-minimized routing. The reality of how most Lightning volume gets transmitted today is a small number of large custodians moving funds between themselves on behalf of users who never touch the underlying protocol.
Why This Happened
The honest answer: running a Lightning node well is operationally hard. Channel management, liquidity rebalancing, fee optimization, and uptime requirements are non-trivial even for technically sophisticated users. The user experience of self-custodial Lightning has improved markedly in the last few years, but it remains demonstrably more complex than custodial alternatives.
Most users, given the choice, choose simpler. The existence of high-quality custodial Lightning frontends made Lightning usable at scale; that same usability has shifted the network's center of gravity toward custodial usage.
The Remittance Story
Where Lightning genuinely matters as a payments rail is in cross-border remittances. Strike's corridor between the U.S. and several Latin American countries, Bitnob's African remittance routes, and similar services in Southeast Asia have demonstrated that Lightning-based dollar-to-dollar (or dollar-to-local-currency) remittance can offer materially lower fees and faster settlement than legacy alternatives.
Volume on these corridors is real, growing, and economically meaningful in markets where remittance fees of 5-10% have been the norm for decades. Whether or not those flows show up in self-custodial Lightning routing tables, they are happening.
The structure of these corridors is important: Bitcoin and Lightning serve as the settlement bridge, but the user experience on both ends is fiat. The sender deposits dollars; the receiver withdraws local currency; the Lightning rails in between are invisible. Functionally, Lightning is competing with SWIFT and traditional remittance networks rather than with cash.
What to Watch
Two trends matter for the next phase.
First, the development of "Lightning service providers" — businesses that offer managed Lightning liquidity and infrastructure to other businesses. These intermediaries are building the institutional plumbing that lets non-crypto-native companies adopt Lightning settlement without operating their own nodes. If that infrastructure matures, the use case for Lightning as a B2B settlement rail expands considerably.
Second, the relationship between Lightning and stablecoin payment rails. PYUSD on Solana, USDC on various L2s, and a growing set of stablecoin payment networks are competing directly with Lightning for the cross-border settlement use case. Stablecoins arguably have the better product-market fit for dollar-denominated remittance, while Lightning remains stronger where the value being transmitted is genuinely Bitcoin rather than a dollar wrapped in Bitcoin.
The 8,400 BTC capacity milestone is real. The story it tells about Lightning's role in the broader payments stack is more complicated than the headline implies.