Electrums latest security update fixes a Lightning backup defect, but some Bitcoin wallet users still need to replace saved backups.
Related Asset Bitcoin #1 BTC · $85,435.87 24-hour change: up 1.91% Loading price history… 24H Up 1.91% 7D Up 2.11% 30D Up 10.74%
Older backups from wallets with non-deterministic Lightning keys lack information needed to reclaim funds from anchor channels, a Lightning channel type, after a remote close.
Version 4.8.2, dated Sept. 11, remains the latest release listed on Electrums official website as of Oct. 1.
The individual-backup fix adds payment-key information needed to claim the users balance from an anchor channel closed by the peer. Without that information, an affected backup lacks the key needed to sweep the output, meaning claim the coins on the Bitcoin blockchain.
Which wallets need attention？
Electrums release notes define two conditions that must coincide: the wallet has non-deterministic Lightning keys, and the backup concerns an anchor channel.
Non-deterministic keys cannot be recreated from the wallets seed. The warning covers individual channel exports and exported full-wallet backups concerning Lightning recovery.
Lightning wallets based on BIP39 seeds or imported extended private keys (xprvs) always have non-deterministic Lightning keys. Electrum-seed wallets differ: their Lightning keys are deterministic when the wallet file was created in version 4.1 or later. Files created in 4.0.x do not qualify merely because the software is now newer.
On desktop, wallet information marks the Lightning channels as non-recoverable from the seed, while the channel-opening dialog warns that a channel cannot be recovered from the seed on Android. Anchor-channel use remains the additional condition for this backup defect.
The individual-backup fix also hides the option to request a remote force-close when the backup cannot sweep the resulting output. The restriction keeps that backup from requesting a close whose output it cannot claim.
PR 10851 repairs wallet-file exports by retaining a randomly generated Lightning private key that the export previously deleted. Maintainer SomberNight explains that re-enabling Lightning in such a backup would generate different keys, leaving its older channel-backup records insufficient to spend anchor-channel funds.
Electrum 4.8.2 fixes future backup exports, but old files may still need replacement.
An upgrade changes the software that produces and reads backups. Electrums documented remedy therefore requires fresh exports, and affected wallets display a startup warning.
The replacement step depends on retaining the original wallet data needed for a fresh export. Installing newer software does not guarantee recovery of key material already lost with that data.