Electrum's 4.8.2 Patch Saves Future Lightning Backups, But Your Old Ones Are Still Dead Weight

Your seed phrase isn't a backup. I know that sounds like heresy. It isn't.

Electrum pushed version 4.8.2 on Sept 11, and as of Oct 1 it's still the newest build listed on the project's site. The release patches a genuine hole in Lightning backups. But here's the part that'll make you check your own wallet: it only fixes backups you export from now on. Old files are still broken.

So if you've been sitting on a Lightning backup you made two years ago and assumed it was fine, you might want to sit down.

What Actually Broke

Here's the setup. Older backups from wallets with non-deterministic Lightning keys are missing the information needed to reclaim funds from an anchor channel after a remote close. Anchor channels are a newer channel type. They're better for fee management and they're increasingly the default. But they add a recovery wrinkle that most people never think about.

Non-deterministic keys can't be rebuilt from your wallet's seed. Read that again. The seed that you engraved on metal and buried in your backyard doesn't regenerate those keys. When Electrum's fix landed as PR 10852, it added the payment-key info required to claim your balance from an anchor channel that the peer closed. Without that key, the backup can't sweep the output. The coins just sit there.

Two conditions have to line up for you to be affected. One, your wallet uses non-deterministic Lightning keys. Two, the backup covers an anchor channel. Miss either one and you're clear.

Which wallets fall into that first bucket? Any Lightning wallet built from a BIP39 seed or an imported extended private key, or xprv. Those always run non-deterministic Lightning keys. Electrum-seed wallets are different. If the wallet file was created in version 4.1 or later, the Lightning keys are deterministic. If it dates back to 4.0.x, upgrading the software doesn't fix anything. The file itself is the problem.

On desktop, Electrum's wallet info now flags Lightning channels as non-recoverable from the seed. On Android, the channel-opening dialog warns you outright that a channel can't be recovered from the seed. That warning's been there. People click past it.

The patch also hides the option to request a remote force-close when the backup can't sweep the result. That's smart. It stops a broken backup from triggering a close it can't claim. PR 10851 handles a second piece by retaining a randomly generated Lightning private key that the export used to delete. Maintainer SomberNight explained why that matters: re-enabling Lightning in such a backup would spin up different keys, and the older channel-backup records wouldn't be enough to spend anchor-channel funds.

The Seed Phrase Myth Is Cracking

Anon, let me save you some gas fees. Stop treating your seed as a total recovery kit.

This is the alpha nobody is sharing. For years the crypto crowd has repeated one mantra: back up your seed and you're safe. That's true for on-chain Bitcoin. It's a half-truth for Lightning. A whole category of channels needs data that lives outside the seed, and most people don't know which category theirs falls into. I've been running Lightning nodes for years and I had to double-check my own setup after reading these release notes.

Who wins here? Electrum, honestly. They shipped a fix, documented exactly who's affected, and added a startup warning for impacted wallets. That's how you handle a bug. Quietly patching without telling users is how you lose trust, and Electrum didn't do that.

Who loses? Anyone who made a Lightning backup before this and thinks a software upgrade will rescue them. It won't. The upgrade changes the program that reads and writes backups. It doesn't regenerate key material that was already left out of an old file. And if your original wallet data is gone, you can't produce the fresh export you need. The coins are stuck.

Here's my hotter take. The entire Lightning UX around backups is a minefield, and anchor channels made it worse even though they made everything else better. Better fees, better fee management, more complexity at recovery time. That tradeoff needs to be front and center for every wallet, not buried in a release note that 90% of users will never read. When's the last time you actually tested a recovery instead of just assuming your backup works? Be honest.

I aped in so you don't have to. Test your recovery before you need it.

What To Do Right Now

The remedy is boring and it's the only one that works. Make fresh exports. Keep the original wallet data you'd need to generate them. If you run Lightning on a BIP39 seed wallet or imported an xprv, check whether any of your channels are anchor channels and whether your backup predates the fix. If both are true, replace it today. Not tomorrow.

And if you're one of the people who deleted the wallet file after exporting a backup, thinking the export was enough? That's the painful one. The patch can't bring back data that isn't there.

The trenches don't sleep, and neither do the edge cases that eat your bags while you're not looking. Electrum 4.8.2 is a good patch. It's just not a time machine.