r/lightningnetwork

What is happening with the Lightning Network? Feels completely different than 2019 ...

Hey folks,

I’ve been well out of the loop for a few years now. Back around 2019, I remember going to Rotate Bar in London and actually paying for a beer using Lightning. Was cool. Back then, we had all those fun LApps like Pollo Feed and Satoshi's Place. There were all these card games and casinos, and this like blog platform. Oh and a big tipping system on Twitter.

Fast forward to today, and it feels like a lot of that stuff is gone. BlueWallet doesn't even seem to have a Lapp marketplace etc anymore.

But the network is still alive as far I can tell from some quick Googling, still being developed, etc. So what's going on? Has it gone more enterprise / backend?

reddit.com

u/CertifiedHeelStriker — 5 days ago

▲ 19 r/lightningnetwork+1 crossposts

Boltz shut down all Bitcoin swap services on August 3, saying attackers now iterate faster than a small team can patch. It's the clearest AI-vs-defense story I've seen in this space yet.

Boltz is the non-custodial swap provider connecting Bitcoin mainchain, Lightning, and Liquid, used as backend infrastructure by ZEUS, Aqua, and Bull Bitcoin. On August 3 they pulled the plug on everything, not because of a breach, nobody lost funds since they never hold custody, but because they said months of AI-assisted probing had escalated to a pace their small team couldn't keep patching against.

Their statement was blunt: "Attackers now iterate faster than a team our size can find and patch. This is not a response to a single incident."

Three wallets lost swap functionality within hours with basically no warning. Blockstream announced Blockstream Swaps a week later, on August 10, clearly moving to fill the gap.

Worth being honest that this is Boltz's own account, no independent technical report has been published yet, but the broader pattern lines up with other recent data points. Blockaid reported over a billion dollars lost to hacks in just the first half of 2026, already surpassing all of 2025. Coinbase scaled back its own bug bounty payouts because AI tooling flooded it with low quality duplicate submissions.

I also went back and checked the Coldcard vulnerability I covered a few weeks ago, the loss figure has climbed from 38 million to over 111 million since then. Not clear if that's newly identified historical losses or ongoing exploitation, and I didn't want to guess, so I flagged the uncertainty directly in the piece.

Full writeup connecting both stories:

https://davidebtc186.substack.com/p/ai-vs-ai-how-boltzs-shutdown-reveals

u/Large-Cress900 — 7 days ago

▲ 11 r/lightningnetwork

My Lightning nodes are closed and shutdown while the 110 stuff resolves itself. How many of you are doing the same?

I have been looking at the possible failure modes of lightning while a possible fork (however short) could happen. I don't want the hassle of watching 2 separate chains while this plays out. Any precautions that you are taking or am I just being paranoid?

reddit.com

u/Billkr — 11 days ago

▲ 10 r/lightningnetwork

BIP110 question

I have a long running lightning node. Mostly for small payments but I also have some channels opened with random nodes (most of them are more than a year old). I also run my own bitcoin node. I didn't signal bip110, and I really don't care about it. My question is if I have to do something to keep my lightning node funds safe. I don't really want to close my channels just in case. Is there really any hard fork risk (i mean for my on chain funds)? How my nodes (core lightning - bitcoin core 30) will behave?

reddit.com

u/RevolutionaryPick241 — 13 days ago

▲ 14 r/lightningnetwork

BIP-110's failure this week is a good case study in what real consensus actually requires, relevant if you're thinking about any future Lightning-adjacent protocol changes too

Not directly a Lightning story, but the mechanics here are relevant to anyone who cares about how Bitcoin base layer changes actually happen, since Lightning depends entirely on that layer staying stable and predictable.

BIP-110 tried restricting non-financial data, mainly Ordinals and BRC-20 tokens, from Bitcoin transactions. Used a user-activated soft fork, same mechanism as SegWit in 2017, with a 55 percent signaling threshold instead of the usual 95 percent supermajority.

Support never got anywhere close. Around 0.42 percent of hashrate signaled between May and early August. When the mandatory window started August 7, it was around 2.5 percent. The chain split off anyway. Because Bitcoin's difficulty only adjusts every 2016 blocks, the minority chain inherited full mainnet difficulty with almost no hashrate behind it. Within two days it was 48 blocks behind mainnet, producing blocks every 6.9 hours instead of ten minutes.

What's actually instructive here: 2017's SegWit UASF worked because of economic alignment that already existed before the formal activation, exchanges, wallets, and businesses had effectively already agreed. BIP-110 used the identical mechanism without anything close to that alignment first. Adam Back called it out directly for lacking both technical and ecosystem consensus. Jameson Lopp flagged the risk of unspendable UTXOs through Taproot edge cases specifically.

For anyone running LND or thinking about base layer dependencies for Lightning infrastructure, this is a decent real-world reminder that the base layer's stability isn't guaranteed by good intentions or a procedurally valid mechanism, it requires actual broad buy-in across miners, node operators, and the wider ecosystem before anything changes.

Full writeup, also connects this to a hardware wallet vulnerability from the same week with a similar underlying failure pattern:

https://davidebtc186.substack.com/p/two-bitcoin-failures-one-week-apart

u/Large-Cress900 — 10 days ago