Electrum

This commit adjusts the Android QR code scanner screen so its buttons and text don't get hidden behind the phone's status bar or navigation gestures on newer Android versions (Android 15+). It is a user-interface compatibility fix, not a security patch.

This commit adjusts on-screen spacing for the Android version of the Electrum wallet app so that dialog boxes avoid overlapping with the phone's system status and navigation bars. It is a user-interface layout fix, not a security patch. There is no indication it fixes a vulnerability or changes how funds, keys, or passwords are protected.

This commit adjusts the Electrum mobile app's main screen layout so that Android's system status bar and navigation bar do not overlap the app's toolbar or bottom controls when the operating system's 'edge-to-edge' display mode is active. It is a UI spacing fix, not a security patch.

This commit adds helper functions to Electrum's mobile QML interface so the app can measure Android status and navigation bar heights. It is a UI/layout change, not a security fix or vulnerability. There is no indication it addresses any security issue.

This commit updates a single Android build configuration number from target SDK 34 to 35. It is a routine compatibility/maintenance change with no direct security fix visible in the diff. By itself, it does not patch any vulnerability, though staying current with Android SDK targets is generally good security hygiene.

This commit fixes a bug where Electrum's command-line tool would call sys.exit() deep inside an offline command, causing the program to hang while waiting for a lock that never gets released. The fix replaces those abrupt exits with proper exception handling so the caller can clean up and exit cleanly. It is a reliability/bug-fix change rather than a security vulnerability in the traditional sense, though the hang could be annoying or disruptive.

This commit adds an extra safety check in Electrum's submarine-swap feature to make sure the on-chain refund deadline is earlier than the Lightning Network payment deadline. The commit message says this was already implicitly guaranteed by other checks, and the code change just makes it explicit. It also adds clarifying comments about Lightning invoice expiry handling and payment bundles. There is no direct evidence that a real vulnerability was exploitable before this change.

This is a tiny build-script change that sorts the list of files in the 'dist' directory alphabetically instead of using whatever order the filesystem happens to return. It makes the generated download page deterministic and easier to review, but it does not fix a vulnerability that can be directly exploited by an attacker.

This commit adds 'set -e' to four helper shell scripts used during Electrum's build and release process. 'set -e' makes a bash script stop immediately if any command fails, rather than continuing with potentially broken or incomplete results. This is a hardening improvement for the build pipeline, not a fix for an active security flaw in the wallet software itself. It reduces the risk that a failed build step goes unnoticed and produces a bad release artifact.

This commit is a routine release-preparation change. It only updates the version number from 4.6.1 to 4.6.2 and adds release notes describing many bug fixes and minor features. There is no code change that could directly introduce or fix a security vulnerability in this specific commit.

This commit is a routine update to translation/localization files (locale). It changes one line in one language file. There is no indication of any security relevance.

This commit fixes a bug in Electrum's mobile-style QML user interface where wallets protected only by a keystore password (not file encryption) could be opened without prompting for or checking the password. The change adds an optional force_check_password flag to the wallet loading code and uses it in the QML GUI so users are always asked for the password before the wallet opens. It is a defensive fix, not an active remote exploit.

This commit adds optional developer-only debugging helpers for investigating memory leaks. The new code is not used automatically by Electrum; it is only meant to be run manually from the Qt console by developers. It does not change how wallets, networking, or cryptography work, and it introduces no security vulnerability.

This commit simply moves an internal developer-only debugging helper class (DebugMem) from one file to another. It is not a security fix and does not change any user-facing behavior. The code is used only for diagnosing memory leaks during development.

This commit fixes an internal developer-only debugging tool (DebugMem) that crashes when scanning Python objects. The crash happens because some objects raise an AttributeError during Python's normal type-checking process. The fix simply catches that error and treats the object as not matching the requested type. The affected code is commented out by default and only used for memory-leak debugging, so it does not affect normal Electrum users or their wallets.

This commit is a simple variable rename from WITNESS_TEMPLATE_REVERSE_SWAP to WITNESS_TEMPLATE_SWAP, plus a comment update explaining the historical naming. The actual swap script logic, structure, and values are unchanged. There is no security issue here.

This change adds safety checks to Electrum's submarine swap feature so it refuses to create or accept swaps if the wallet's view of the Bitcoin blockchain is outdated ('stale tip'). If the wallet acted on old blockchain data, swap locktimes could be set dangerously far in the future or too close to the present, which could let an attacker lock up funds unfairly or prevent a refund. The patch is defensive and partial: it stops the risky action but does not by itself fix whatever caused the stale tip.

This commit is a performance refactor, not a security fix. It replaces a slow list-based data structure for tracking bundled Lightning payments with two dictionaries that allow faster lookups. There is no indication it addresses a vulnerability or changes security behavior.

This commit tightens safety checks in Electrum's submarine-swap (a way to move Bitcoin between on-chain and Lightning) code. It prevents the same payment hash or prepayment hash from being reused for different swaps, makes sure saved payment records aren't silently overwritten by conflicting data, and verifies the other party's refund public key before accepting a swap invoice. These are defensive hardening changes that reduce the chance of a malicious or buggy swap server/client confusing the wallet into paying or revealing funds incorrectly. The commit message does not call this a security fix, and there is no disclosed vulnerability or CVE.

This commit refactors how Electrum builds and checks the on-chain Bitcoin scripts used in submarine swaps (a way to exchange on-chain and Lightning bitcoins). It introduces a single helper function that both constructs the script and verifies it can be reconstructed exactly from its parts. The change is a defensive clean-up: it makes the code more consistent and adds a self-check that the script matches the expected template, payment hash, locktime, and public keys. There is no direct evidence in the commit that this fixes an active security bug, but it strengthens validation against a malicious or buggy swap server sending a mismatched script.

This commit tightens how Electrum converts numbers into displayed bitcoin amounts. It removes the ability to pass plain strings into a key formatting helper, and routes integer and float inputs through a safer Decimal conversion to avoid tiny rounding errors that can appear when computers handle decimal numbers. The change also makes one fee calculation explicitly use Decimal arithmetic. The patch is defensive and does not by itself fix a known exploitable bug, but it reduces the risk of incorrect amounts being shown or used in fee calculations.

This commit tidies up internal bookkeeping after a Bitcoin/Lightning submarine swap completes. It removes a watcher callback and deletes a payment bundle/hold-invoice that are no longer needed. The change appears to be a cleanup/hygiene fix rather than a direct security patch, but leaving stale callbacks and payment state around could theoretically contribute to memory growth, unexpected re-triggering of events, or minor information leakage about completed swaps.

This commit cleans up leftover data after a failed Lightning submarine swap in the Electrum wallet. Previously, failed swaps could leave stale payment information, routing-failure records, and internal index entries behind. The patch removes those leftovers so they cannot accidentally be reused or misinterpreted later. It is a defensive hardening change rather than a fix for a known active attack.

This commit only adds Python type-hints and renames a loop variable from 'v' to 'sweep_info' for clarity. It does not change any program behavior, logic, or security properties.

This commit renames and doubles a fee parameter used when doing reverse submarine swaps (a way to move funds from Lightning back to on-chain Bitcoin) in the Electrum wallet. The old name suggested it was just the swap provider's mining fee; the new name, 'prepayment', reflects that the user must pay this amount upfront over Lightning and trust the provider to return it if the swap fails. The change is mostly a terminology and parameter refactor, but it also adjusts the safety check so the allowed prepayment equals twice the mining fee rather than twice the prepayment. There is no direct evidence in the commit that this fixes an active security vulnerability.