Electrum

This change makes Electrum tolerate a failure when setting restrictive file permissions on a temporary wallet file. Previously, if the operating system refused the permission change (for example on some network file systems), saving a wallet would crash. Now it logs a warning and continues. The security trade-off is that in rare cases a wallet file may be created with slightly looser permissions than intended, but the wallet data is still encrypted by the user's password if the wallet is password-protected.

This commit fixes a bug in Electrum's transaction batching feature. Previously, when suggesting which existing transactions could be combined (batched) with a new payment, the code ignored the wallet's available unspent coins. This made the batching suggestions too restrictive and could lead to suboptimal or unexpected transaction construction. The fix passes the available coins into the candidate-selection logic and documents the behavior. There is no direct evidence in the commit of a security vulnerability or exploit.

This commit fixes a crash in Electrum's command-line tool. When a user ran a plugin-provided command in offline mode (using the -o flag), the program tried to access a daemon object that didn't exist, causing an ugly AttributeError. The patch makes two changes: it automatically marks all plugin commands as requiring a daemon, and it adds an explicit check so the program fails cleanly if a plugin command is somehow run without a daemon. This is a robustness/usability fix rather than a security vulnerability.

This commit fixes a small but real bug in Electrum's handling of private key imports. Previously, when a user pasted an empty or invalid list of private keys, the function returned 'None' (meaning 'nothing'). Some parts of the code treated 'None' as if keys were present, which could let an empty or invalid import proceed unexpectedly. The fix makes the function return an empty list instead, so callers correctly recognize there are no valid keys. The direct security impact is limited because the user still has to initiate an import and supply input, but it removes a logic trap that could mishandle private key material.

This commit adds two read-only statistics commands to Electrum's swapserver plugin, allowing swap providers to view their swap history and summary. It does not change how swaps are executed, does not move funds, and does not introduce obvious security bugs. The main consideration is that these commands expose swap-related financial data through existing command interfaces, but they appear to use the same access controls as other wallet-lightning ('wl') commands.

This is a routine cleanup change that swaps one Python built-in check for an equivalent one. It removes future deprecation warnings but does not change what the program actually does or fix any security problem.

This commit is a code cleanup: it adds type hints and renames a parameter from recv_amount_sat to recv_amount_sat_or_max to reflect that it can be either a number or the special 'max' marker '!'. It also makes the run_swap_dialog method consistently return a boolean. There is no security-relevant behavior change.

This commit removes a UI restriction in Electrum's swap dialog. Previously, when opening a submarine swap from the receive tab with a pre-set amount, the amount fields and Max button were disabled, forcing the user to swap exactly that amount. The change keeps those fields editable so users can adjust the swap amount if they want a larger or different swap. It also tweaks an error message to clarify that a swap may not be possible with the current provider. There is no security issue here.

This commit only changes the project's continuous integration (CI) configuration. It adds a new automated test job that runs the existing unit tests using the exact pinned dependency versions shipped in Electrum's release binaries, in addition to the existing job that tests with the latest dependencies. There is no change to application code, no bug fix, and no security patch.

This commit is a routine cleanup of the project's automated testing setup. It removes the 'tox' tool and runs tests directly with pytest. There is no change to the Electrum wallet application itself, no bug fix, and no security-related change.

This commit hardens Electrum's daemon so that unusual or malformed wallet file paths no longer cause the program to crash with an unhandled error. It wraps a filesystem path normalization call in a try/except block and logs a warning instead of raising an exception. The change is defensive and improves robustness, but it does not appear to fix an active security vulnerability.

This commit adds missing quotation marks around variables in a collection of build and release shell scripts. In shell scripting, unquoted variables can split or be interpreted unexpectedly if paths contain spaces or special characters. The change is defensive hardening of the project's build tooling rather than a fix for a specific reported exploit. It reduces the risk of build failures or accidental command injection during release builds, but it does not patch a vulnerability in the wallet software that end users run.

This commit is a minor user-interface layout fix for the Android version of Electrum. It adds spacing so that the crash/error report dialog does not overlap the Android system status bar at the top or the navigation bar at the bottom. There is no security-relevant change in the code.

This commit only adds Python type hints and fixes a minor return-value consistency bug in the QML GUI code. It does not change runtime behavior in a security-relevant way, and there is no indication it fixes a vulnerability.

This commit is a small user-experience improvement in the Electrum Bitcoin wallet's Qt receive tab. It makes the wallet suggest a 'submarine swap' (a way to gain inbound Lightning capacity) even when the user creates a zero-amount Lightning invoice, if they currently have no incoming liquidity. It also tweaks some help messages shown to users. There is no security vulnerability here.

This commit is a simple code cleanup: it replaces a hardcoded number (20,000 satoshis) with a named constant variable. The actual value and behavior are unchanged. There is no security issue here.

This commit is a purely cosmetic UI adjustment for Electrum's mobile-style QML interface. It changes how padding is applied to the exception/error dialog so that it displays correctly on modern edge-to-edge phone screens. There is no security relevance.

This commit updates Electrum's Android build setup so the app works on newer Android devices that require 16 KB memory page alignment. It swaps the Android NDK to a special canary/CI build, adds a small patch to the barcode scanner library, and adds a helper script to apply patches. There is no direct evidence this fixes an active security vulnerability; it appears to be a compatibility/build hardening change.

This commit tightens how Electrum handles error messages coming from external LNURL services. Previously, every LNURL error was wrapped with a 'do not trust this message' warning. The change splits those errors into two kinds: errors generated from Electrum's own code now display normally, while only errors returned by untrusted LNURL servers are sanitized and flagged as untrusted. It also applies a text-safety utility to the server-provided message before showing it to the user, reducing the chance that a malicious or compromised LNURL server could trick a user through a crafted error string.

This commit is a minor code-quality refactor in Electrum's mobile/QML user interface. It changes how two internal signals (invoiceResolved and requestResolved) are declared and connected, switching from an imperative connection in Python to a declarative connection in QML. There is no visible security relevance: no input validation, cryptography, network handling, or asset-moving logic is changed.

This is a small user-interface fix in Electrum's mobile-style QML wallet. It makes the 'Withdraw' button correctly enable itself once Lightning channels finish connecting, if the user opened a withdrawal request dialog early. There is no indication this is a security fix; it appears to be a usability/bug-fix for a UI state not updating properly.

This commit is a code cleanup in Electrum's mobile/QML user interface. It splits the job of interpreting a payment string (like a Lightning invoice or LNURL link) into two parts: one that resolves/fetches remote details, and one that handles the resulting payment or withdrawal request. There is no indication in the commit that it fixes a security bug or vulnerability; it appears to be a refactor to support voucher/LNURL-withdrawal flows more cleanly.

This commit only adds new automated tests for how Electrum parses and resolves LNURL payment strings. It does not change any production wallet code, so it cannot introduce a security vulnerability or fix one on its own.

This commit adds a new feature to Electrum that lets users withdraw bitcoin from a service by scanning or pasting an LNURL-withdraw code. It is a feature addition, not a fix for a known vulnerability. The code does include some safety checks, such as only allowing HTTPS or .onion callback URLs and warning users not to trust error messages from the LNURL server. However, because this is brand-new code handling real money withdrawals and interacting with external services, it introduces new attack surface. There is no direct evidence in the commit of an exploitable bug, but the change is security-relevant by nature.

This commit is a purely cosmetic user-interface tweak. It adds 20 pixels of empty space at the bottom of a loading dialog so the spinning circle is not touching the dialog edge. There is no security relevance.