Community Trust ScoreLikely Real
Bitcoin’s Lightning Network can’t shake a years-old problem. Node operators won’t take the first step to rebalance liquidity routes, leaving channels lopsided and partially useless.
The standoff centers on channel depletion. Funds move mostly one direction, leaving routing nodes with BTC piled up on one side. Channels that should handle two-way traffic basically become one-way streets. In December 2025, the network hit a capacity peak of 5,600 BTC, boosted by institutional money flowing in from Binance and OKX. Since then, things have slid backward. Capacity dropped to 4,884 BTC. Active channels fell from over 80,000 down to 45,000. The numbers tell a pretty clear story about nodes giving up or getting squeezed out.
Years of research haven’t cracked it.
Alex Bosworth rolled out submarine swaps back in 2018, letting operators shuffle BTC between on-chain wallets and Lightning channels to top things off. Seemed smart. But every swap needs a real Bitcoin transaction fee, and that cost killed adoption fast. Lightning Labs tried their own fixes with Loop and Pool, creating markets where nodes could trade liquidity. Amboss Technologies launched Magma with the same goal. None of them really took off. Activity on these platforms stayed low or dropped off entirely, leaving the core problem untouched.
Why Coordination Keeps Failing
René Pickhardt, a researcher who’s spent years studying this mess, thinks the two-party channel design creates the whole problem. His recent paper floats ideas like symmetric fees or coordinated replenishment across multiple nodes. Sounds reasonable on paper. But getting nodes to agree on protocol changes? That’s a different fight. Many operators will probably reject anything that adds complexity or costs them money upfront.
The network was built to avoid depending on cooperation between nodes. That was kind of the point. Now fixing the liquidity crisis seems to need exactly that kind of coordination. It’s a contradiction the Lightning community hasn’t figured out how to square.
Tools exist but nobody wants to move first. C-Otto’s rebalance-lnd script and Bosworth’s Balance of Satoshis let operators manually manage their channels through loops and swaps. They work fine technically. The catch is someone has to pay transaction fees and take time to run the rebalancing. Most node operators would rather wait for someone else to do it. So everyone waits. And the imbalance gets worse.
Core Lightning introduced Liquidity Ads as a protocol-native way to trade channel capacity. It seemed like a breakthrough at launch. In practice, fulfillment has been sporadic at best. Nodes advertise liquidity for sale, but buyers don’t show up consistently. Or sellers back out. The marketplace never reached the critical mass needed to make a real dent in the problem.
Structural Tension Won’t Go Away
A new proposal making the rounds wants to build coordination incentives directly into the protocol. The idea is to make cooperation less painful by spreading costs across participants or rewarding nodes that help rebalance the network. Previous attempts at protocol-level fixes haven’t stopped these standoffs, though. The Lightning Network’s design philosophy clashes with solutions that require trust or collective action. Nodes operate independently by design. Asking them to suddenly work together feels like trying to retrofit a different system onto existing infrastructure.
The decline in active channels shows the real-world impact. Fewer channels means fewer routing options. That makes payments less reliable and pushes users toward centralized alternatives or back to on-chain transactions. The network was supposed to solve Bitcoin’s scaling problem, but liquidity bottlenecks create new friction.
Pickhardt’s research keeps coming back to the same tension. Solutions that might work require changes many nodes won’t accept. Solutions that nodes might accept don’t fully solve the problem. The network sits in this uncomfortable middle ground where everyone sees the issue but nobody wants to bear the cost of fixing it.
Institutional deposits briefly masked the problem last year when Binance and OKX moved funds onto Lightning. That capital injection pushed capacity to record highs. But it didn’t change the underlying dynamics. Channels still drained in one direction. New liquidity just gave the network more runway before hitting the same wall again.
Transaction fees remain the sticking point for most rebalancing solutions. Every time a node wants to move funds around, they’re paying on-chain fees that eat into whatever they might earn from routing payments. The math often doesn’t work out, especially for smaller operators. Bigger nodes with more traffic can justify the expense. Everyone else just deals with unbalanced channels or shuts them down entirely.
No Clear Path Forward
The marketplace solutions all ran into similar problems. Magma, Loop, Pool—they offered ways to buy and sell liquidity, but creating a functioning market turned out harder than building the tech. Buyers and sellers need to find each other at the right price at the right time. Liquidity needs shift constantly as payment flows change. By the time a trade gets arranged, the need might have moved elsewhere.
Rebalancing scripts gave operators more control but didn’t change the incentive structure. Running these tools takes time and attention. Most node operators run Lightning as a side project or small business. They can’t babysit channels all day. Automated rebalancing sounds good until you look at the fee costs piling up.
The network’s capacity drop from 5,600 BTC to 4,884 BTC represents more than just numbers. Each BTC of lost capacity means fewer payment routes, longer paths, higher fees for users. The channel count falling from 80,000 to 45,000 shows nodes either closing up shop or consolidating into fewer, larger channels. That centralization trend runs against Lightning’s original vision of a distributed payment network.
Pickhardt’s symmetric fee proposal tries to split rebalancing costs more evenly. Instead of one party eating the whole expense, both sides of a channel contribute. Makes sense in theory. Getting nodes to adopt a new fee structure means coordinating a protocol change across thousands of independent operators. Good luck with that.
Node operators keep waiting for someone else to blink first. Everyone knows channels need rebalancing. Nobody wants to pay for it alone. So the standoff continues, capacity keeps sliding, and the Lightning Network’s liquidity problem grinds on with no resolution in sight.
Frequently Asked Questions
What caused Bitcoin’s Lightning Network capacity to drop recently?
Capacity fell from a December 2025 peak of 5,600 BTC to 4,884 BTC as channels became imbalanced from one-directional fund flows, with active channels dropping from over 80,000 to 45,000.
Why haven’t existing solutions like submarine swaps fixed the liquidity problem?
Solutions like Alex Bosworth’s submarine swaps and Lightning Labs’ Loop require paying Bitcoin transaction fees for each rebalancing operation, making them too expensive for most node operators to use regularly.
What does René Pickhardt propose to solve the coordination problem?
Pickhardt’s research suggests symmetric fees or coordinated replenishment across nodes, but these solutions require protocol changes that contradict Lightning’s design principle of operating without requiring trust or cooperation.
