Electrum

This commit fixes a bug in Electrum's 'sweep' feature, which lets users move funds from a private key into their wallet. Previously, if the private key's address type was unsupported (like some multi-signature or older script types), the app would crash with a confusing internal error instead of showing a friendly message. The patch catches that case and shows a proper user-facing error. It also adds a small guard in the mobile/QML interface to avoid trying to build a sweep transaction before the inputs are ready.

This commit only adds Python type hints to function parameters and return values. It does not change any actual program logic, data handling, or security behavior. There is no security issue here.

This is a small user-interface bug fix. If a user deletes a payment invoice using the command-line while the graphical wallet window still shows it, clicking to view the deleted invoice previously caused the program to crash with an error. The fix simply checks whether the invoice still exists before trying to display it, and refreshes the list if it does not. There is no security vulnerability here.

This commit tightens a check in Electrum's submarine-swap code that pulls a secret 'preimage' from a Bitcoin transaction's witness data. Previously, the code only checked whether the witness existed; now it also requires at least two witness elements before reading the second one. This prevents an index-out-of-bounds read and makes the extraction more robust, especially for unsigned or unusually constructed transactions. It is a defensive hardening fix rather than a clear-cut exploitable vulnerability.

This commit fixes a bug in Electrum where an old-style wallet with a password would incorrectly accept a blank/empty password (None) as valid. The fix makes sure that if a wallet has a password, calling check_password(None) raises an InvalidPassword error instead of succeeding. This is a security-hardening fix for a regression introduced by an earlier change.

This commit fixes a bug in Electrum's wallet setup wizard that affected multisig wallets. When a user tried to enable (reactivate) a cosigner's key in a multisig wallet, the wizard did not correctly recognize the wallet as multisig, which could cause the operation to fail or behave incorrectly. The fix moves the multisig setup logic into the wizard's start routine so it always runs, and adds a regression test. There is no direct evidence this bug could be exploited by an attacker; it appears to be a functional regression that could confuse users or prevent normal wallet management.

This commit is a straightforward internal code cleanup in Electrum's setup wizard. It merges two ways of passing starting information into the wizard so that callers now supply a single 'WizardViewState' object instead of separate 'start_viewstate' and 'initial_data' arguments. There is no user-facing change and no security relevance visible in the diff.

This is a small code cleanup change. It makes the `start()` method of several wizard classes accept its `initial_data` argument only as a named (keyword) argument, not as a positional argument. This prevents accidental misuse and makes it easier for developers to see where initial data is actually coming from. There is no security vulnerability being fixed here.

This is a one-line bug fix in Electrum's fee warning logic. The app compares the user's chosen transaction fee rate against the network's minimum relay fee. Previously, because of how Python handles decimal versus floating-point numbers, very low fee rates (below 1 satoshi per virtual byte) could be compared incorrectly, potentially causing the warning not to appear when it should. The fix forces the relay fee to be treated as a precise Decimal so the comparison works correctly. The practical effect is mainly to ensure users get warned about fees that are too low to be relayed.

This commit adds a safety check and a test for Electrum wallet setup. It ensures that if a user tries to add a seed phrase that does not match an existing watch-only wallet's public key (xpub), the wallet raises a clear error instead of silently replacing the keystore. This prevents accidental or malicious mismatches between a seed and the wallet's expected public key.

This commit fixes a bug in the Electrum wallet where disabling a keystore (a container for private key material) accidentally wiped out important key metadata called 'key origin info.' This metadata tells the wallet where a key came from in a derivation path. Losing it could cause problems when the wallet later tries to sign transactions or interact with hardware wallets, because the wallet might not be able to reconstruct the correct key path. The fix changes the internal field name used when converting a keystore to a watch-only version, and adds tests to make sure the metadata survives.

This commit only updates test data in Electrum's test suite. It replaces fake/placeholder BIP39 seed phrases with the well-known standard test seed 'abandon abandon ... about' and updates the corresponding expected public keys and Bitcoin addresses. There is no change to production wallet code, no bug fix, and no security-relevant behavior change.

This commit removes the ability to enable or disable individual keystores in Electrum's two-factor authentication (2FA) wallets. The feature was already broken for these wallets, and the change hides the buttons in the user interface and makes the underlying methods raise errors if called. It is a hardening/cleanup change rather than a fix for an active security vulnerability.

This commit fixes a visual bug in Electrum's mobile-style QML interface where very low Bitcoin transaction fees (below 1 satoshi per virtual byte) could cause the fee histogram bar colors to loop around the color wheel and display misleading colors. It also rounds fee values to two decimal places for cleaner display. There is no indication this affects funds, transactions, or wallet security.

This commit is a minor user-interface tweak in Electrum's contact list. It changes which column expands to fill available window width: previously the contact name column stretched, now the address column stretches. There is no security relevance.

This commit is purely a test improvement. It adds unit tests for a wallet feature that disables a keystore (turning a spendable wallet back into a watch-only wallet), and makes two tiny supporting changes: adding type hints to a plugin helper and adding an abstract method stub in the wallet base class. There is no security fix here and no behavior change in the actual wallet code that users run.

This commit only adds new test cases to Electrum's existing test suite. It checks that the wallet setup wizard correctly handles old-style Electrum seed phrases and stores the seed/passphrase properly. There is no change to production code, no bug fix, and no security-relevant behavior change.

This is a minor code cleanup commit. It fixes a typo in a user-facing message ('keytore' to 'keystore'), adds abstract method declarations for enable/disable_keystore in the base wallet class, updates type hints, and changes test fixture values. There is no security-relevant change.

This commit only adds a new automated test for an existing feature. It does not change any production code, so it cannot introduce a security vulnerability or fix one. The test checks that the 'show_fiat' option for the on-chain history command correctly includes fiat currency values in the output.

This commit adds support for a new Bitcoin test network called 'mutinynet signet' to the Electrum wallet. It is purely a configuration/network addition: it defines a new network class, provides a genesis block identifier, and lists some default servers and Lightning nodes. There is no indication of any security bug or vulnerability being fixed or introduced.

This is a minor cleanup commit in Electrum's plugin system. It fixes a typo in a user-facing help string ('Regdit' to 'Regedit'), removes an unused import, corrects a type hint, and fixes one function that could return nothing instead of the expected two-value result. There is no security issue here.

This commit only adds new automated tests for how transaction dates are displayed and grouped in Electrum's mobile/QML user interface. It does not change any production code, fix a bug, or alter program behavior. There is no security relevance.

This commit is a minor user-interface tweak for Electrum's QML (mobile-style) transaction history. It removes seconds from displayed timestamps, showing times only to the nearest minute, matching the older Qt desktop GUI. There is no security relevance.

This commit restores two command-line options, from_height and to_height, to Electrum's onchain_history command. It also fixes a small bug where the wallet's internal history filtering was reading the wrong variable for block height, and tightens how dates are formatted to JSON. There is no direct security vulnerability here; it is mostly a bug-fix and feature-restoration change.

This commit fixes a bug in Electrum's wallet setup wizard where two password-related screens ('wallet_password' and 'wallet_password_hardware') were accidentally only defined in the Qt desktop version, not in the shared wizard logic. The fix adds those missing view definitions to the abstract KeystoreWizard so non-Qt interfaces (like command-line or mobile builds) can complete wallet creation properly. It also adds tests verifying that a hardware wallet keystore can be enabled after setup. There is no direct evidence in the commit of a security vulnerability; it appears to be a correctness/robustness fix for wizard flow.