Photo by Brian J. Tromp on Unsplash

Back in 2019, Lightning Network evangelists were practically giddy. The scaling solution would finally free Bitcoin from its 10-minute block times and $30 transaction fees. By now, in 2024, we'd all be buying lattes with Bitcoin and merchants would be running on Lightning nodes. Fast forward to today, and you still can't pay for that latte at your local café without your barista asking, "Bitcoin? You mean... that internet money thing?"

The Lightning Network hasn't failed, exactly. It's just failed to do what everyone promised it would do. And that's actually the more interesting story.

The Promise vs. The Reality

Let's be specific about what Lightning was supposed to solve. Bitcoin processes roughly seven transactions per second. Visa handles around 65,000. That gap is enormous. Lightning proposed a clever solution: move transactions off the main Bitcoin blockchain onto a secondary network of payment channels. Settle everything later. Problem solved, right?

On paper, it worked. Technically, Lightning can theoretically handle millions of transactions per second. The throughput ceiling isn't the bottleneck anymore. But throughput isn't actually the problem that's preventing Bitcoin adoption.

The problem is friction. Setting up a Lightning wallet requires understanding channels, liquidity management, and base layer security. You need to open a channel with someone, which costs fees and takes time. If you want to receive payments, you need inbound liquidity—basically, someone else needs to have opened a channel to you first. For merchants, this means managing node infrastructure, monitoring uptime, and handling the technical complexity that makes most people's eyes glaze over.

Meanwhile, your phone already has Apple Pay. Your neighbor uses Venmo. Both work instantly, without reading a 40-page technical guide.

Who's Actually Using It Right Now

Lightning isn't dead though. It's just niche. And that's where it's actually proving useful.

El Salvador mandated Bitcoin adoption in 2021, and Lightning became essential infrastructure there. When you're in a country with currency instability and remittance fees that eat 10-15% of money sent back home, suddenly learning Lightning's quirks doesn't seem unreasonable. El Salvador has about 70,000 active Lightning users—not massive, but it's real adoption with genuine economic necessity behind it.

The most interesting use case? Nostr. Yes, the decentralized social protocol that everyone said would be Twitter's replacement. It never replaced Twitter, but it found a home with a specific community that values censorship resistance. Lightning integration means you can tip creators instantly without intermediaries. It's small, maybe tens of thousands of users, but it's sticky. People actually use it daily.

Game developers are experimenting too. Stacks-based games and some Bitcoin gaming projects are layering Lightning on top for instant micropayments. A player defeats a boss, earns 500 satoshis instantly. No waiting. That friction reduction actually matters in gaming.

But buying coffee at Starbucks? Still not happening.

The Infrastructure Problem That Won't Go Away

Here's where Lightning's limitations get uncomfortable to discuss: it requires node operators. Lots of them. Running a Lightning node isn't as demanding as running a Bitcoin node, but it's not casual either. You're managing channels, monitoring balances, paying routing fees to send payments through the network, and potentially losing money on failed payment attempts.

Most people don't want to run nodes. They want to download an app and send money. This is why custodial solutions like Wallet of Satoshi and Strike exist—they handle the complexity server-side. But custodial solutions bring back the centralization that Bitcoin was supposed to eliminate. You're trusting a company with your funds again. When you use Strike to pay someone, you're not actually using Bitcoin's Lightning Network; you're using Strike's internal ledger.

For actual peer-to-peer transactions on Lightning, network liquidity remains the real bottleneck. If you want to send $500 but don't have a payment channel with enough capacity, you're stuck. You need to either find a route through other people's channels (and pay them routing fees), or close your current channel and open a new one (which costs fees and blockchain confirmation time).

This is why Lightning adoption has flatlined around 5,000-6,000 public nodes for the past two years. The network topology is becoming increasingly concentrated around a few well-capitalized routing nodes, defeating the decentralization purpose.

What's Actually Working Now

Lightning isn't useless—it's just good at specific things. Streaming payments, for instance. Theoretically, you could stream value second-by-second, paying for bandwidth as you consume it. Podcasters have experimented with value-4-value streaming where listeners send satoshis in real-time while they listen. It's genuinely novel and wouldn't be possible on the base layer.

Cross-border remittances in underbanked regions remain Lightning's strongest practical application. In countries where bank accounts are expensive or inaccessible, peer-to-peer Lightning transfers beat traditional remittance corridors. The fees are lower. The speed is faster. It's not mainstream adoption, but it solves real economic problems for real people.

The most honest assessment: Lightning works better than Bitcoin's base layer for specific, low-value, high-frequency transactions. It's genuinely faster and cheaper. But it doesn't work better than the payment systems that already exist for those same transactions. And it certainly doesn't work better for high-value settlements or situations where security guarantees matter more than speed.

The Road Ahead (And It's Slower Than Expected)

Developers are working on improvements. Eltoo could simplify channel mechanisms. Silent Payments could enhance privacy. Better tooling for liquidity management could make running nodes more profitable. But none of these are silver bullets that magically make Lightning competitive with centralized payment processors.

The more uncomfortable question: maybe Lightning doesn't need to be Bitcoin's everyday payment layer. Maybe that's fine. Bitcoin works well as a settlement layer and store of value. If you want payments at Starbucks speed, you use something else. If you want secure settlement of large amounts, you use Bitcoin. If you need fast payments in specific contexts with specific tradeoffs, you use Lightning.

That's not the vision evangelists promised in 2019. But it might be more honest than pretending a scaling solution can replace 60 years of payment infrastructure development.

For more on how different cryptocurrencies handle similar tradeoffs, check out Solana's MEV Problem: Why Your Transactions Aren't Safe, Even When You Think They Are—it explores how the pursuit of speed often creates entirely new problems.