CryptoSlate
Electrum released version 4.8.2 on Sept. 11, patching a Lightning backup defect that affects some users' ability to recover funds after a remote channel close. The fix targets a narrow backup type: older individual channel exports and full-wallet backups whose Lightning keys are non-deterministic and that involve anchor channels, a modern channel type, after the counterparty force-closes. Wallets using BIP39 seeds or imported extended private keys (xprvs) always have non-deterministic Lightning keys, and the fix only flows through to freshly produced exports.
Why it matters
The defect is narrow in scope but unblockable without user action. PR 10851 repairs wallet-file exports by retaining a randomly generated Lightning private key that the export previously deleted, so future backups from 4.8.2 onward will carry the payment key needed to sweep anchor-channel outputs on Bitcoin. Re-enabling Lightning in an existing backup, maintainer SomberNight explained, would generate different keys, leaving the old records insufficient to spend the funds. Affected wallets display a startup warning pointing users to the replacement flow.
Market impact
For most Electrum users running standard seed-based wallets created in 4.1 or later, the Lightning keys are deterministic and the issue does not apply. The risk concentrates in two populations: wallets built on BIP39 seeds or imported xprvs, and files created in 4.0.x that would not retroactively benefit from the upgrade. The patch also hides the option to request a remote force-close when the backup cannot sweep the resulting output, preventing users from triggering a close they cannot claim. The documented remedy is a fresh export with the original wallet data retained, since installing newer software does not recover key material already lost with that data.
Frequently asked questions
-
What does Electrum 4.8.2 actually fix?
It patches a Lightning backup defect that stripped a payment key needed to claim anchor-channel funds after a remote close. PR 10851 retains the previously deleted key in wallet-file exports.
-
Which Electrum wallets are affected?
Wallets with non-deterministic Lightning keys that involve anchor channels. This covers BIP39-seed wallets, imported extended private key (xprv) wallets, and Electrum-seed wallet files created in version 4.0.x.
-
How do users know if their backup is at risk?
Affected wallets display a startup warning on launch. On desktop, the channel info marks Lightning channels as non-recoverable from the seed; on Android, the channel-opening dialog warns the channel cannot be recovered from the seed.
-
Can users recover funds from an already-broken backup?
Only if they still have the original wallet data needed to produce a fresh export. Installing newer software does not recover key material that was already lost with the old backup.
-
What changed in the individual-backup fix specifically?
The update hides the option to request a remote force-close when the backup cannot sweep the resulting output, so a backup cannot trigger a close whose funds it cannot claim. It also retains the Lightning payment key in exported backups going forward.
Benjamin Cowen
CoinTelegraph
Glassnode
Lookonchain
CoinDesk