Electrum

This commit is a purely cosmetic user-interface tweak. It adds extra spacing at the top of a text box that displays Nostr relay web addresses, so the first line no longer looks cut off. There is no security relevance.

This commit fixes the Windows uninstaller so it removes leftover registry entries for Lightning payment links (lightning, lnurlp, lnurlw), not just Bitcoin links. Before the fix, uninstalling Electrum left these entries behind, which could make Windows still think Electrum was the program to handle those links even after the software was gone.

This commit fixes two email/domain recognition patterns so they no longer treat the vertical bar character '|' as a valid letter. Before the fix, a string like 'example.c|m' could be accepted as a domain or email ending, which could let malformed payment identifiers slip through validation. The change is a small correctness fix in input parsing, not a dramatic security hole on its own.

This commit adds support for a new style of LNURL web link (so-called LUD-17 format, e.g. lnurlp://example.com or lnurlw://example.com) in Electrum. It also registers Electrum as the handler for these new link types on Android, Windows, macOS, and Linux. The change is a feature addition, not a fix for a known vulnerability. There is no evidence in the commit or supplied references that this is a security patch or that it addresses any reported security issue.

This commit only adds a plain-code comment listing where Electrum registers 'bitcoin:' and 'lightning:' URI scheme handlers across different operating systems. No code behavior changes, no security fix or vulnerability introduced.

This commit adds a feature that lets users rename their wallet file from the mobile-style QML user interface. It is a normal feature addition, not a security fix. The code does include some safety checks, but there are small gaps that could theoretically allow a misnamed or clashing wallet file. There is no evidence this was released as a security patch or credited to a security researcher.

This is a bug-fix patch for Electrum's exchange-rate feature. CoinGecko began sending a 'null' price for the Honduran Lempira, which caused Electrum to crash while converting exchange rates and made the entire CoinGecko price feed unusable. The fix simply skips any currency whose value is missing. There is no security vulnerability here—just a reliability fix.

This commit fixes a small bug in Electrum's NWC (Nostr Wallet Connect) plugin where a client sending 'params: null' in a request could cause the server to crash or behave unexpectedly. The fix treats null the same as missing or empty parameters, and improves the error message if something still goes wrong.

This commit fixes a known Bitcoin weakness (CVE-2012-2459) in Electrum's light-client verification. Because Bitcoin's Merkle tree duplicates the last hash when a level has an odd number of items, an attacker can craft a block proof that makes a transaction appear to be at a different position than it really is. The patch rejects proofs where a duplicated value appears on the left side of a hash pair, which only happens in forged proofs. The commit also adds tests for the fix and re-labels an existing related defense for CVE-2017-12842.

This commit only adds explanatory comments and a developer TODO note. It does not change any actual encryption logic, access controls, or behavior of the Electrum wallet. There is no security fix or vulnerability introduced by this change.

This is a small build-script fix for Electrum's release process. It changes how the release script handles Android APK files when a non-release-manager runs it. Previously, the script would always rebuild an unsigned APK even if one already existed, which could waste time or cause confusion. Now it checks whether an unsigned APK already exists and, if so, skips the rebuild and just renames it. There is no direct security vulnerability in the changed code itself.

This commit only updates the project's release notes and bumps the version number from 4.7.1 to 4.7.2. It does not change any executable code, so it cannot introduce or fix a security vulnerability by itself. The release notes do mention several prior fixes and changes that were made in other commits, but this particular change is purely documentation and versioning.

This commit changes how Electrum builds private Lightning Network routing hints called 'blinded paths.' It lets the wallet choose which channels to include in a blinded path, and when channels are explicitly chosen, it publishes a short channel ID (a public network identifier) instead of just the next node's public key. The commit message itself warns that this 'might have privacy issues, as this can be used to probe channel capacity.' In plain terms, a payment sender could learn more than intended about a receiver's channel balances, which is a known Lightning privacy concern. The change is not a full fix; it is a partial implementation that introduces a new probing risk while trying to solve a payment-reliability problem.

This commit adds an optional way to decode Bech32 strings without verifying their checksum. It is a small, controlled API change in Electrum's address-decoding helper, not a fix for a known vulnerability. The new option is off by default and only used in tests, so it does not appear to weaken normal wallet behavior on its own.

This commit simply moves an existing helper function called blinding_privkey from one file (onion_message.py) to another (lnonion.py) and updates the import statements and tests accordingly. There is no change to what the function does, no bug fix, and no security patch.

This commit fixes how Electrum builds encrypted routes for sending private messages over the Lightning network. Previously, the code accidentally included the sender's own first hop in the encrypted onion path, which could cause message delivery to fail or produce an invalid route. The fix removes that unnecessary first hop and adds a unit test to confirm the route is built correctly.

This commit refactors how Electrum builds private (blinded) communication and payment paths through the Lightning network. It splits a reply-path helper into a more general helper that can also build payment paths, and adds the routing/fee details required by the Lightning protocol for payment blinded paths. There is no direct evidence in the commit that this fixes a security bug; it appears to be feature/protocol-completion work.

This commit is a simple code cleanup: it moves a block of route-building logic into a new helper function without changing what the program actually does. There is no security fix or behavior change visible in the diff.

This commit only adds a new unit test for an existing Lightning Network feature. It does not change any production code, fix a bug, or alter security behavior. There is no security issue here.

This commit only adds and updates a test file. It checks that when Electrum cannot find a Lightning route to a peer for an onion message, the error includes the peer's network address. There is no production code change and no security fix or vulnerability evident in the diff.

This commit only changes a test file. It adds a mock (a fake stand-in) for a Lightning Network wallet function so that a test of onion message handling doesn't crash when the code tries to fall back to a direct peer connection. There is no change to production code and no security fix or vulnerability is indicated.

This commit finishes a previously unfinished feature in Electrum's Lightning onion-message handling. Before, when sending an onion message, the code only tried a single destination or blinded path. Now it can accept a list of paths and try them one by one (round-robin) if a request needs to be retried. This is a robustness improvement, not a fix for an active security bug. There is no evidence in the commit or supplied references that this addresses a disclosed vulnerability.

This change makes Electrum create files and folders with stricter default permissions, so other users on the same computer cannot read or modify them. The developer noticed the RPC socket was being created with overly permissive permissions (0o775, meaning group members had full access), and decided to tighten the default for all files rather than fixing each case individually. It is a proactive hardening patch, not a fix for a reported exploit.

Electrum's background daemon runs a local control server using a Unix domain socket. Previously, that socket file was created with permissions 0775, meaning any user in the same group could connect to it and potentially control the wallet. This commit changes the permissions to 0600, so only the wallet's owner can access the socket. The commit itself notes a possible race condition: for a brief moment after the socket is created and before the permissions are tightened, other users might still be able to connect.

This commit adjusts a CI (continuous integration) configuration so that an automated LLM security-review task is triggered automatically only for users with write or admin permissions, while a manual trigger is used for everyone else. It is a workflow tweak with no direct effect on Electrum's wallet code, cryptography, or user-facing security.