Electrum

This is a small bug-fix for how Electrum handles a setting called 'forgetconfig'. Previously, the command-line default of 'false' always overrode the value stored in the user's config file, making it impossible to enable the setting inside the config file. The change lets users set it in the config file as intended. It is not a security vulnerability fix; it is a usability/config fix.

This is a small performance cleanup in Electrum's Lightning code. It moves a save-to-database operation outside a loop so the wallet writes once instead of after every individual payment chunk. There is no direct security bug being fixed; the change reduces database writes and may make crashes during batch processing slightly cleaner, but it does not patch a vulnerability.

This commit fixes a display bug in the Electrum wallet. If a wallet was created or restored and then quickly closed, the database did not record the last known block height. Later, opening that wallet in offline mode made all transactions appear 'unconfirmed' because the wallet had no saved height to compare against. The fix immediately saves the current block height when a wallet is opened, not just when new blocks arrive.

This commit fixes a data-integrity bug in Electrum's Lightning payment handling. A particular data structure was supposed to be immutable, but it secretly contained a mutable list. When the list changed, Electrum's storage system did not notice, so the change might not be saved to disk—especially when partial writes are enabled. That could leave the wallet's record of incoming Lightning payments inconsistent after a restart or crash, potentially causing funds to appear stuck or payments to be mishandled. The fix makes the list truly immutable and updates the code to create new copies whenever it changes, so the storage layer reliably saves the state.

This commit tightens the user interface for fee editing in Electrum's mobile/QML wallet. Previously, users could freely type either a fee rate or a total absolute fee when bumping or cancelling transactions. Now, the app restricts which of those two inputs is shown depending on the operation, matching the rules already enforced by the underlying wallet code. This reduces the chance that a user accidentally creates an invalid or exploitable transaction by entering a fee value the wallet logic does not expect.

This commit adds a single type hint comment to a QML GUI file. It does not change any executable code, logic, or behavior. There is no security relevance.

This commit fixes a state-handling bug in Electrum's mobile/QML interface when scanning or processing payment invoices. Specifically, when a user scanned a Lightning invoice, leftover data from a previous LNURL-pay interaction could remain in the invoice parser, causing the app to think it should still act as an LNURL-pay and potentially pay immediately without showing the normal confirmation. The fix resets parser state when loading a new invoice, except when intentionally continuing an LNURL-pay flow.

This commit fixes the Android QR scanner in Electrum so it checks which app-request ID is returned before processing a scanned result. Previously the scanner used a hardcoded request code of 0, which could let a malicious or confused app feed fake QR scan results into Electrum by returning an activity result with the same default code. The fix gives Electrum a unique, randomly chosen request code and ignores any result that does not match it.

This commit adds optional fingerprint unlock to the Electrum Android app. It stores an encrypted copy of the wallet password on the device, protected by Android's built-in biometric/keystore system. The change is a feature addition, not a fix for a known bug or attack. There are some design choices worth reviewing—such as how the encrypted password is stored and what happens if a user adds a new fingerprint—but nothing in the commit itself shows an active vulnerability being exploited.

This commit only adds a missing stub method to a mock object used in unit tests. It does not change any production code, network behavior, or wallet security logic. It is a test-only follow-up fix with no security relevance.

This commit fixes a Lightning Network code path where Electrum would try to wait on a peer that had not finished initial setup. The change skips uninitialized peers instead of calling a method on them. This likely prevents a hang or crash during channel operations, but the commit message does not frame it as a security fix and no exploit details are provided.

This is a small defensive fix in Electrum's currency-conversion code. Previously, if an exchange rate was reported as zero, the code treated it the same as a missing rate and returned zero. Other parts of the program could then crash with a 'division by zero' error when converting amounts. The change makes zero rates return a special 'not a number' value instead, so callers can handle it safely. It is a robustness improvement rather than a clear-cut security vulnerability.

This commit is a user-interface tweak for Electrum's mobile/QML fee selector. It hides a 'Target' label when the user is manually entering a fee, and uses text color to show which of the two manual inputs (fee rate vs absolute fee) was edited last. There is no security-relevant change.

This commit is a minor code cleanup in Electrum's mobile-style QML user interface. It replaces two hardcoded text labels ('sat/vbyte' and 'sat') with references to centrally defined constants. There is no security relevance: no logic, calculations, permissions, or data handling changed.

This is a one-line fix in Electrum's test suite. A previous change accidentally used the real network Peer class instead of a special test-only version (PeerInTests) in a Lightning network test. The test-only version processes messages immediately, which a specific test needs to avoid timing-related failures. This commit restores the test-only class, fixing a flaky unit test. It is not a security fix and does not affect production code.

This commit only adds a new automated test file for an existing Lightning wallet utility function. It does not change any production code, add new features, or fix any bugs. There is no security relevance.

This is a tiny user-interface fix for the Electrum mobile app's QR-code scanner. A QML screen was trying to call a 'close' method that did not exist, causing a harmless JavaScript type error in the log. The developer added an empty 'close' method so the call succeeds and no error is printed. There is no security issue here.

This commit is a minor user-interface improvement, not a security fix. It simply sorts the tabs shown in the wallet information window by the keystore's root fingerprint so that multi-signature wallet tabs appear in a consistent order across different computers. There is no vulnerability or security-relevant change here.

This commit fixes a display-only bug in Electrum where, under certain timing conditions, a transaction that already had one blockchain confirmation could briefly be shown as 'unconfirmed' in the wallet balance. The fix adds a cache refresh right after a transaction is SPV-verified, so the balance is recalculated with the correct confirmation count. It does not allow theft, transaction manipulation, or remote code execution.

This is a minor code cleanup in Electrum's transaction handling. A developer removed a redundant loop that was calling the same cache-clearing function multiple times, replacing it with a single call. There is no security issue visible in the change.

This is a small compatibility fix for Electrum's Coldcard hardware wallet plugin. A newer version of the underlying Coldcard communication library (ckcc-protocol v1.5.0) renamed a constant used to locate the Coldcard simulator. Electrum now tries the new name first and falls back to the old name, so the plugin works with both old and new library versions. There is no indication this is a security vulnerability or that it introduces one.

This commit only adds a more helpful error message when the Coldcard hardware wallet cannot be opened because of missing Linux USB device permissions (udev rules). It does not change any security behavior, permissions, or access controls; it simply logs a hint before re-raising the same error.

This commit simply removes an unused helper function from a test file. It does not change any production code, user-facing behavior, or security-sensitive logic. There is no security issue here.

This commit only changes the project's internal unit tests. It makes test-only mock Lightning wallets get created and cleaned up in a more centralized way so temporary files and background tasks are reliably removed after each test. There is no change to the actual Electrum wallet or Lightning code that end users run, so this does not affect real-world security.

This is a code-cleanup change inside Electrum's Lightning channel handling. It removes the special case where a channel object could exist without a linked Lightning wallet worker (lnworker). Previously, unit tests and some code paths allowed lnworker to be None, which forced many methods to check 'if self.lnworker:' before doing anything. The patch makes lnworker mandatory, simplifies those checks, and adds a developer note that one related cleanup call is currently broken. There is no direct security fix for end users here; it is mostly defensive maintenance that reduces the chance of future bugs in test or edge-case code.