EL
← All projectsElectrum

Electrum

Long-running lightweight Bitcoin wallet for desktop and mobile platforms.

BitcoinSoftware walletsActive incident
Repository coverage

1361 commits in the local evidence base

Every captured commit receives deterministic security triage and a separate communication-quality score. Security candidates and broader second-pass signals receive full-patch Ollama analysis.

108security candidates322second-pass queue1084AI analyses
90commits · 30 days
200commits · 60 days
570commits · 180 days
1124commits · 365 days
Backfill bands
Aug 5 → Feb 6470 seen11 candidatesComplete
Feb 6 → Jun 6346 seen10 candidatesComplete
Jun 6 → Jul 653 seen2 candidatesComplete
Jul 6 → Aug 554 seen3 candidatesComplete
Commit communication

Does the history explain itself?

Message quality measures whether a commit identifies its scope, purpose, rationale, testing, and supporting references. It does not change the security-severity score.

66/100 average clarity
252Strong · 80–100
675Adequate · 60–79
388Thin · 40–59
46Opaque · 0–39
2security candidates with opaque commit messaging
Read the scoring rubric →
Developer activity

Who is changing the project?

Public Git author strings; identities are not independently verified.

DeveloperCommitsCandidatesAnalyzedHigh riskMessage avg.
SomberNight42533373163
ThomasV16511104163
ghost4376626170
f321x44128400070
Sander van Grieken12412112057
Felix54720070
user323062
ekzyis222053
accumulator28111072
Roman Zeyde515053
Sasha Zykov515075
Aaron Fiore414068
Analysis record

Published AI watches

Last scanned 47 minutes ago

Informational 19 AI analysisMessage 73 · Adequate
EL ElectrumElectrum BitcoinSoftware wallets

Merge pull request #11172 from accumulator/qml_crash_reporter_threading

This is a small bug-fix patch for Electrum's QML (mobile-style) graphical interface. The crash reporter was not correctly handling exceptions that come from Python's threading system, which could cause the crash reporter itself to misbehav…

Fixes incorrect exception argument handling in crash reporterPrevents potential secondary failure in error-reporting pathNo security boundary crossed; no input from untrusted source is processed
45ad42f7by Felix+4−11 file
No security note in commit
Informational 19 AI analysisMessage 73 · Adequate
EL ElectrumElectrum BitcoinSoftware wallets

qml: crash reporter: handle threading.excepthook arguments

This commit fixes a bug in Electrum's mobile-style QML crash reporter. When an uncaught exception occurred inside a background thread, the crash reporter itself would break because it expected three pieces of information but received one b…

Crash reporter failure could hide or obscure real runtime errors in background threadsNo input validation, privilege boundary, or cryptographic issue presentFix improves diagnostic fidelity but does not close an attack vector
2e7fe460by Sander van Grieken+4−11 file
No security note in commit
Low 40 AI analysisMessage 73 · Adequate
EL ElectrumElectrum BitcoinSoftware wallets

Merge pull request #11154 from spesmilo/make_unsigned_tx_with_base_tx

This commit changes how Electrum creates unsigned Bitcoin transactions when an existing 'base transaction' is provided. Previously, the wallet wrongly demanded spendable coins even when the caller supplied a base transaction that already c…

Relaxation of input-source preconditionAddition of consensus-level invariant assertion (at least one input)Addition of empty-input guard before PartialTransaction construction
ff273162by ThomasV+4−11 file
No security note in commit
Low 29 AI analysisMessage 68 · Adequate
EL ElectrumElectrum BitcoinSoftware wallets

wallet: make_unsigned_tx: follow-up prev

This commit fixes a crash in Electrum's transaction builder. If a user had only one on-chain coin (UTXO) that was just enough to meet a reserve requirement, clicking 'Max' in the send tab would hit an internal assertion and fail instead of…

Denial-of-service-like crash path triggered by user action in normal wallet stateAssertion failure reachable through GUI send flowFix converts assertion crash into handled NotEnoughFunds exception
462f631dby SomberNight+2−01 file
No security note in commit
Low 28 AI analysisMessage 73 · Adequate
EL ElectrumElectrum BitcoinSoftware wallets

Merge pull request #11097 from SomberNight/202610_bump_deps

This is a routine maintenance commit that updates many of Electrum's software building blocks (dependencies) and raises the minimum required Python version from 3.10 to 3.11. It also refreshes the Linux distribution snapshots used to build…

Dependency version bumps for security-sensitive libraries (cryptography, cffi, libffi, sqlite)Removal of an embedded PGP public key and switch to hash verification for Windows Python installer downloadsBase image refresh from EOL/near-EOL Debian bullseye to bookworm for AppImage builds
84345fdcby ghost43+934−103048 files
No security note in commit
Informational 15 AI analysisMessage 73 · Adequate
EL ElectrumElectrum BitcoinSoftware wallets

Merge pull request #11139 from accumulator/consolidate_platform_checks

This commit is a straightforward internal cleanup: it moves repeated checks like 'are we running on Windows?', 'are we on Android?', and 'are we inside an AppImage?' into a single new helper module called platform.py. The actual behavior o…

22e24580by ghost43+87−7619 files
No security note in commit
Informational 15 AI analysisMessage 45 · Thin
EL ElectrumElectrum BitcoinSoftware wallets

consolidate platform checks into platform.py

This commit is a straightforward internal cleanup: it moves repeated operating-system checks (Windows, macOS, Linux, Android, AppImage) into a single new helper module called platform.py and updates the rest of the code to use those helper…

9715f882by Sander van Grieken+87−7619 files
No security note in commit
Informational 15 AI analysisMessage 38 · Opaque
EL ElectrumElectrum BitcoinSoftware wallets

version: bump to 4.8.4

This commit only changes the software version number from 4.8.3 to 4.8.4 in a single file. It contains no security-related changes, no bug fixes, and no functional code modifications.

0c661eb8by f321x+1−11 file
No security note in commit
Low 29 AI analysisMessage 73 · Adequate
EL ElectrumElectrum BitcoinSoftware wallets

make_unsigned_transaction: do not require coins if there is a base_tx

This commit relaxes a wallet check when creating a new Bitcoin transaction. Previously, Electrum refused to create a transaction if the user had no spendable coins and no explicit inputs. The change allows creation to continue if a 'base t…

Relaxation of input/coin availability guardAddition of post-construction input count assertionPotential workflow: Replace-By-Fee (RBF) or transaction bumping using base_tx inputs
876360deby ThomasV+2−11 file
No security note in commit
Informational 17 AI analysisMessage 73 · Adequate
EL ElectrumElectrum BitcoinSoftware wallets

Merge pull request #11111 from accumulator/qml_bip39recovery_task_refactor

This commit is a code cleanup in Electrum's mobile-style QML wallet wizard. It replaces an older thread-based background scan for BIP39 seed accounts with a newer asyncio-based task approach, and makes the recovery dialog destroy itself wh…

Refactor of async task lifecycle and cancellation handlingDialog lifecycle cleanup with onClosed: destroy()Use of ignore_if_destroyed to avoid callbacks on destroyed QML objects
896a68d7by Felix+44−332 files
No security note in commit
Informational 12 AI analysisMessage 73 · Adequate
EL ElectrumElectrum BitcoinSoftware wallets

qml: refactor BIP39 account scan to asyncio tasks.

This commit is a code cleanup in Electrum's mobile-style QML wallet wizard. It replaces an extra background thread with a simpler asyncio-based callback for scanning BIP39 seed accounts. There is no indication this fixes a security bug; it…

00ed883aby Sander van Grieken+44−332 files
No security note in commit
Moderate 59 AI analysisMessage 73 · Adequate
EL ElectrumElectrum BitcoinSoftware wallets

qt: paytoedit: complete contacts to their key, not 'name <key>'

This commit fixes a bug in Electrum's Qt 'Send' tab where selecting a contact from the autocomplete dropdown could briefly leave the wrong recipient active. Previously, the payment field was set to a display name like 'Alice <alice@example…

UI state desynchronization between displayed recipient and active PaymentIdentifierStale PaymentIdentifier usable for ~1 second after recipient text changesPay/Save/Max buttons enabled while recipient is being edited
dd1b50fbby f321x+47−132 files
No security note in commit
Informational 18 AI analysisMessage 73 · Adequate
EL ElectrumElectrum BitcoinSoftware wallets

Merge pull request #11092 from f321x/qml_address_history_labels

This commit fixes a UI bug in Electrum's QML (mobile-style) interface where transaction and address labels could become stale or fail to update after editing. It replaces a fragile manual callback system with a proper event listener so the…

No security-relevant signals in diff: no privilege escalation, injection, cryptographic, or authentication changes.Fixes a UI consistency bug (stale labels) that could mislead users but does not enable direct exploitation.Adds event-listener lifecycle management (register/unregister on destroy) to prevent dangling callbacks and potential use-after-free patterns.
9242c505by Felix+334−8412 files
No security note in commit
Low 34 AI analysisMessage 73 · Adequate
EL ElectrumElectrum BitcoinSoftware wallets

qml: avoid potential Ok signal by tapping while dialog is closing,

This commit fixes a bug in Electrum's mobile-style QML password dialog. If a user tapped the OK/confirm button while the dialog was already closing, the app could emit an extra 'password entered' signal. That extra signal triggered a crash…

Crash in authentication-related code path (AuthMixin)Duplicate signal emission during UI state transitionUser-interaction race condition (tap while dialog closing)
00f981edby Sander van Grieken+8−01 file
No security note in commit
Informational 21 AI analysisMessage 73 · Adequate
EL ElectrumElectrum BitcoinSoftware wallets

Merge pull request #11091 from f321x/fix_num_parents_perf_simple

This commit is a performance fix for a wallet function that traces where a transaction's funds came from. It replaces a slow, repeatedly-recursive approach with a more efficient loop and removes an old cache. The change also fixes how the …

Performance fix for wallet history traversalAddress-reuse uncle detection logic changedCache removed in favor of iterative computation
4ec70746by ThomasV+82−463 files
No security note in commit
Informational 24 AI analysisMessage 73 · Adequate
EL ElectrumElectrum BitcoinSoftware wallets

Merge pull request #11047 from fametrano/old-seed-odd-length

This commit fixes a bug where Electrum wallets created with unusual, hand-crafted 'old-style' seed phrases could not be opened or used. These seeds decode to an odd number of hex characters, which the program previously rejected. The chang…

Input validation relaxed for legacy data (odd-length hex strings)New user-facing error path prevents seed display when mnemonic encoding is impossibleGUI exception handling narrowed: UserFacingException shown as str, other Exception as repr
fc31115eby ghost43+93−157 files
No security note in commit
Informational 19 AI analysisMessage 73 · Adequate
EL ElectrumElectrum BitcoinSoftware wallets

Merge pull request #11096 from f321x/followup_11094

This commit is a small follow-up cleanup. It translates several user-facing error messages into different languages and makes the Qt GUI handle one specific file-read/write error (StorageReadWriteError) more gracefully, showing a warning d…

Exception-handling path changed in GUIUser-facing error messages internationalizedNo changes to encryption, wallet parsing semantics, or permissions
54c355feby Felix+9−75 files
No security note in commit
Informational 23 AI analysisMessage 73 · Adequate
EL ElectrumElectrum BitcoinSoftware wallets

Merge pull request #11094 from devdavidejesus/fix-10760-storage-not-utf8

This commit improves Electrum's error handling when a user tries to open a file that is not a valid Electrum wallet. Previously, if the file contained bytes that were not valid UTF-8 text, the program would crash with a confusing technical…

Error-handling hardeningUser-facing exception message improvedNo cryptographic or parsing logic changed
2a20256fby Felix+10−12 files
No security note in commit
Informational 20 AI analysisMessage 65 · Adequate
EL ElectrumElectrum BitcoinSoftware wallets

qt: show StorageReadWriteError to user instead of crash reporting it

This is a small user-interface fix in Electrum's Qt desktop app. Previously, if the wallet file was on a read-only folder or an unplugged drive, the app treated the resulting StorageReadWriteError as an unexpected crash and sent a crash re…

No memory safety, cryptographic, or authorization changesException handling change only; no new attack surface introducedCrash-reporting no longer triggered for expected I/O failure scenarios
5a971b11by f321x+2−11 file
No security note in commit
Low 26 AI analysisMessage 45 · Thin
EL ElectrumElectrum BitcoinSoftware wallets

keystore: follow-up prev: small clean-up

This commit is a small follow-up cleanup in Electrum's keystore code. It renames an internal helper function, makes the code accept certain unusual 'old' seed phrases that some users created by hand, improves an error message shown to user…

Refactoring of seed validation helperUser-facing error handling improvement in seed displayGrandfathering of non-standard old seed phrases
ead42d09by SomberNight+35−154 files
No security note in commit
Repository ledger

Explore captured commits

Expand any commit for its author, full message, clarity score, changed files, triage signals, analysis, and source link.

AI review queuedMerge pull request #11172 from accumulator/qml_crash_reporter_threadingby Felix · 45ad42f7 · Nov 20, 2026 · 1 fileMessage 73 · AdequateInformational 19Details
Commit message · Felix

Merge pull request #11172 from accumulator/qml_crash_reporter_threading

qml: crash reporter: handle threading.excepthook arguments

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
merge-commit duplicate discountsecond-pass: broader security terminology
AI analysis · Informational 19/100

This is a small bug-fix patch for Electrum's QML (mobile-style) graphical interface. The crash reporter was not correctly handling exceptions that come from Python's threading system, which could cause the crash reporter itself to misbehave or fail to report a crash. There is no indication this allows an attacker to take control, steal funds, or bypass security; it is a reliability fix in error-handling code.

AI review queuedqml: crash reporter: handle threading.excepthook argumentsby Sander van Grieken · 2e7fe460 · Nov 18, 2026 · 1 fileMessage 73 · AdequateInformational 19Details
Commit message · Sander van Grieken

qml: crash reporter: handle threading.excepthook arguments

Exception_Hook.handler is installed as both sys.excepthook, which passes
(type, value, traceback), and threading.excepthook, which passes a single
ExceptHookArgs. For uncaught exceptions in threads the logger could not format
exc_info and get_traceback_groupid_hash() raised a TypeError, so the crash
reporter showed that TypeError instead of the actual exception. Unpack
ExceptHookArgs first.

Also include the exception in the log message.

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
second-pass: broader security terminology
AI analysis · Informational 19/100

This commit fixes a bug in Electrum's mobile-style QML crash reporter. When an uncaught exception occurred inside a background thread, the crash reporter itself would break because it expected three pieces of information but received one bundled object. As a result, users would see a confusing secondary error instead of the real crash details. The fix unpacks the bundled object correctly and also logs the actual exception message. It is a reliability/usability fix, not a security vulnerability.

AI review queuedMerge pull request #11154 from spesmilo/make_unsigned_tx_with_base_txby ThomasV · ff273162 · Nov 17, 2026 · 1 fileMessage 73 · AdequateLow 40Details
Commit message · ThomasV

Merge pull request #11154 from spesmilo/make_unsigned_tx_with_base_tx

make_unsigned_transaction: do not require coins if there is a base_tx

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Low 40/100

This commit changes how Electrum creates unsigned Bitcoin transactions when an existing 'base transaction' is provided. Previously, the wallet wrongly demanded spendable coins even when the caller supplied a base transaction that already contained inputs. The fix removes that requirement and adds a safety check to ensure the final transaction still has at least one input. In plain terms: it stops the wallet from refusing to build certain valid transactions and makes sure it cannot accidentally build a transaction with no inputs, which the Bitcoin network would reject anyway.

AI review queuedwallet: make_unsigned_tx: follow-up prevby SomberNight · 462f631d · Nov 17, 2026 · 1 fileMessage 68 · AdequateLow 29Details
Commit message · SomberNight

wallet: make_unsigned_tx: follow-up prev

if the only onchain funds in the wallet is a single UTXO that covers config.LN_UTXO_RESERVE, clicking "Max" in the GUI send tab triggers the assert

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 29/100

This commit fixes a crash in Electrum's transaction builder. If a user had only one on-chain coin (UTXO) that was just enough to meet a reserve requirement, clicking 'Max' in the send tab would hit an internal assertion and fail instead of showing a proper 'not enough funds' error. The fix adds a check that raises a normal NotEnoughFunds exception before the code reaches the assertion.

AI review queuedMerge pull request #11097 from SomberNight/202610_bump_depsby ghost43 · 84345fdc · Nov 17, 2026 · 48 filesMessage 73 · AdequateLow 28Details
Commit message · ghost43

Merge pull request #11097 from SomberNight/202610_bump_deps

build: bump some deps, bump min python to 3.11

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathparser or protocol pathmerge-commit duplicate discountsecond-pass: unusually broad changesecond-pass: security-sensitive path
AI analysis · Low 28/100

This is a routine maintenance commit that updates many of Electrum's software building blocks (dependencies) and raises the minimum required Python version from 3.10 to 3.11. It also refreshes the Linux distribution snapshots used to build the Android, AppImage, Wine, and source-distribution packages. The changes are mostly build-system and packaging housekeeping. There is no direct evidence in the commit of a security vulnerability being fixed, but keeping dependencies current is a normal defensive practice that can close off known weaknesses in older libraries.

AI review queuedMerge pull request #11139 from accumulator/consolidate_platform_checksby ghost43 · 22e24580 · Nov 13, 2026 · 19 filesMessage 73 · AdequateInformational 15Details
Commit message · ghost43

Merge pull request #11139 from accumulator/consolidate_platform_checks

consolidate platform checks into platform.py

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit is a straightforward internal cleanup: it moves repeated checks like 'are we running on Windows?', 'are we on Android?', and 'are we inside an AppImage?' into a single new helper module called platform.py. The actual behavior of the program is intended to stay exactly the same; the code just becomes easier to maintain. There is no indication this change fixes a security bug or introduces a new vulnerability.

AI review queuedconsolidate platform checks into platform.pyby Sander van Grieken · 9715f882 · Nov 13, 2026 · 19 filesMessage 45 · ThinInformational 15Details
Commit message · Sander van Grieken

consolidate platform checks into platform.py

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit is a straightforward internal cleanup: it moves repeated operating-system checks (Windows, macOS, Linux, Android, AppImage) into a single new helper module called platform.py and updates the rest of the code to use those helpers. There is no change in behavior, no bug fix, and no security-relevant change visible in the diff.

AI review queuedversion: bump to 4.8.4by f321x · 0c661eb8 · Nov 6, 2026 · 1 fileMessage 38 · OpaqueInformational 15Details
Commit message · f321x

version: bump to 4.8.4

38/100 · OpaqueMessage clarity
✓ Subject identifies a change✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100

This commit only changes the software version number from 4.8.3 to 4.8.4 in a single file. It contains no security-related changes, no bug fixes, and no functional code modifications.

AI review queuedmake_unsigned_transaction: do not require coins if there is a base_txby ThomasV · 876360de · Nov 5, 2026 · 1 fileMessage 73 · AdequateLow 29Details
Commit message · ThomasV

make_unsigned_transaction: do not require coins if there is a base_tx

The inputs of base_tx can pay for its replacement, by lowering its
change, so we should not rause NotEnoughFunds even with no coin and
no inputs.

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 29/100

This commit relaxes a wallet check when creating a new Bitcoin transaction. Previously, Electrum refused to create a transaction if the user had no spendable coins and no explicit inputs. The change allows creation to continue if a 'base transaction' is provided, because the new transaction can re-use the inputs from that base transaction (for example, to create a replacement transaction or bump the fee). The commit also adds a safety check that the final transaction still has at least one input. It appears to be a bug fix for a legitimate wallet workflow rather than a security vulnerability.

AI review queuedMerge pull request #11092 from f321x/qml_address_history_labelsby Felix · 9242c505 · Nov 4, 2026 · 12 filesMessage 73 · AdequateInformational 18Details
Commit message · Felix

Merge pull request #11092 from f321x/qml_address_history_labels

qml: use callback for label updates, fix stale label

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Informational 18/100

This commit fixes a UI bug in Electrum's QML (mobile-style) interface where transaction and address labels could become stale or fail to update after editing. It replaces a fragile manual callback system with a proper event listener so the wallet's label-change notifications automatically refresh the displayed labels. There is no direct security vulnerability here; it is a correctness and usability fix for label synchronization.

AI review queuedqml: avoid potential Ok signal by tapping while dialog is closing,by Sander van Grieken · 00f981ed · Nov 3, 2026 · 1 fileMessage 73 · AdequateLow 34Details
Commit message · Sander van Grieken

qml: avoid potential Ok signal by tapping while dialog is closing,
which led to a crash from AuthMixin.

ref #9138

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
second-pass: broader security terminology
AI analysis · Low 34/100

This commit fixes a bug in Electrum's mobile-style QML password dialog. If a user tapped the OK/confirm button while the dialog was already closing, the app could emit an extra 'password entered' signal. That extra signal triggered a crash inside the authentication code (AuthMixin). The fix adds a guard so taps during closing are ignored. It is a reliability/crash fix rather than a clear-cut security vulnerability, though crashes in authentication flows can sometimes have security implications.

AI review queuedMerge pull request #11091 from f321x/fix_num_parents_perf_simpleby ThomasV · 4ec70746 · Nov 3, 2026 · 3 filesMessage 73 · AdequateInformational 21Details
Commit message · ThomasV

Merge pull request #11091 from f321x/fix_num_parents_perf_simple

wallet: fix get_tx_parents performance for large wallets

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Informational 21/100

This commit is a performance fix for a wallet function that traces where a transaction's funds came from. It replaces a slow, repeatedly-recursive approach with a more efficient loop and removes an old cache. The change also fixes how the code detects 'uncles' (earlier transactions that reused the same address). There is no direct evidence in the commit that this is a security fix, and no exploit path is described. It appears to be a performance and correctness improvement.

AI review queuedMerge pull request #11047 from fametrano/old-seed-odd-lengthby ghost43 · fc31115e · Oct 30, 2026 · 7 filesMessage 73 · AdequateInformational 24Details
Commit message · ghost43

Merge pull request #11047 from fametrano/old-seed-odd-length

keystore: Old_KeyStore: allow odd-length hex seeds

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Informational 24/100

This commit fixes a bug where Electrum wallets created with unusual, hand-crafted 'old-style' seed phrases could not be opened or used. These seeds decode to an odd number of hex characters, which the program previously rejected. The change allows such legacy wallets to work again, while preventing the program from trying to display the seed as words when it cannot. It is a compatibility fix for a narrow set of user-created wallets, not a remote attack vector.

AI review queuedMerge pull request #11096 from f321x/followup_11094by Felix · 54c355fe · Oct 30, 2026 · 5 filesMessage 73 · AdequateInformational 19Details
Commit message · Felix

Merge pull request #11096 from f321x/followup_11094

storage: translate exception str (i18n), handle StorageReadWriteError in qt

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Informational 19/100

This commit is a small follow-up cleanup. It translates several user-facing error messages into different languages and makes the Qt GUI handle one specific file-read/write error (StorageReadWriteError) more gracefully, showing a warning dialog instead of a crash report. There is no direct evidence of a security vulnerability being fixed.

AI review queuedMerge pull request #11094 from devdavidejesus/fix-10760-storage-not-utf8by Felix · 2a20256f · Oct 30, 2026 · 2 filesMessage 73 · AdequateInformational 23Details
Commit message · Felix

Merge pull request #11094 from devdavidejesus/fix-10760-storage-not-utf8

storage: clear error for a file that is not an Electrum wallet

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Informational 23/100

This commit improves Electrum's error handling when a user tries to open a file that is not a valid Electrum wallet. Previously, if the file contained bytes that were not valid UTF-8 text, the program would crash with a confusing technical error. Now it shows a clearer message suggesting the file may not be an Electrum wallet. This is a minor user-experience and robustness improvement, not a fix for a serious security vulnerability.

AI review queuedqt: show StorageReadWriteError to user instead of crash reporting itby f321x · 5a971b11 · Oct 30, 2026 · 1 fileMessage 65 · AdequateInformational 20Details
Commit message · f321x

qt: show StorageReadWriteError to user instead of crash reporting it

e.g. wallet file in a read-only directory, or on an unplugged drive.

65/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
Why it was queued
second-pass: broader security terminology
AI analysis · Informational 20/100

This is a small user-interface fix in Electrum's Qt desktop app. Previously, if the wallet file was on a read-only folder or an unplugged drive, the app treated the resulting StorageReadWriteError as an unexpected crash and sent a crash report. Now it shows a friendly warning message to the user instead. It is a quality-of-life improvement, not a security vulnerability fix.

AI review queuedkeystore: follow-up prev: small clean-upby SomberNight · ead42d09 · Oct 30, 2026 · 4 filesMessage 45 · ThinLow 26Details
Commit message · SomberNight

keystore: follow-up prev: small clean-up

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 26/100

This commit is a small follow-up cleanup in Electrum's keystore code. It renames an internal helper function, makes the code accept certain unusual 'old' seed phrases that some users created by hand, improves an error message shown to users, and adds more tests. There is no direct evidence in the commit that this fixes an active security vulnerability; it appears to be a robustness and maintainability improvement.

AI review queuedi18n: translate wallet file exceptionsby f321x · c32182e7 · Oct 30, 2026 · 4 filesMessage 45 · ThinInformational 15Details
Commit message · f321x

i18n: translate wallet file exceptions

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit only translates existing error messages into multiple languages. It does not change what the program does, how it handles files, or how it protects data. There is no security issue visible in the changes.

AI review queuedwallet: consolidate _set_label and set_label;by Sander van Grieken · f9cb4e7c · Oct 30, 2026 · 8 filesMessage 68 · AdequateInformational 12Details
Commit message · Sander van Grieken

wallet: consolidate _set_label and set_label;

Do changed check in _set_label and trigger callback there as well. Keep set_label for
the common case, which calls the hook. This is somewhat reversed, as the hook has no
influence over the label change, it is just notified. So the labels plugin does not
inhibit or change the label change, so it could do with just an event_listener.

qml: remove the label plugin specific 'labels_received' event listeners in favor of the
'label_changed' event listener (as the core backend should not have to handle plugin
specific event callbacks to keep changes in sync). The list models find the rows to
update via an index, also update rows whose label derives from the changed label, and
keep the group label of history group rows.

Co-authored-by: f321x <f@f321x.com>

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 12/100

This commit is a code-quality and UI-synchronization refactor for how wallet labels are stored and updated in Electrum. It merges two internal label-setting methods, makes the label-change notification fire consistently, and updates the QML (mobile/desktop) GUI to refresh labels more precisely instead of reloading whole lists. There is no indication this fixes a security vulnerability or introduces a new attack path.

AI review queuedMerge pull request #11090 from accumulator/self_dirty_qetransactionlistmodelby accumulator · 57e11ce0 · Oct 29, 2026 · 3 filesMessage 73 · AdequateInformational 22Details
Commit message · accumulator

Merge pull request #11090 from accumulator/self_dirty_qetransactionlistmodel

qml: mark self dirty for qetransactionlistmodel

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Informational 22/100

This commit is a code-quality refactor for Electrum's QML (mobile/light desktop) user interface. It moves responsibility for refreshing the transaction history list from one UI component into the transaction list model itself, and adds explicit 'mark dirty' calls when addresses are deleted. There is no direct evidence in the commit of a security vulnerability being fixed; it appears to address stale or missing UI updates in the transaction history view.

AI review queuedMerge pull request #11089 from f321x/qml_listmodel_parentby accumulator · a23a58b9 · Oct 28, 2026 · 2 filesMessage 73 · AdequateInformational 18Details
Commit message · accumulator

Merge pull request #11089 from f321x/qml_listmodel_parent

qml: set parent on list models created by QEWallet and QEAddressDetails

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Informational 18/100

This change is a small cleanup in Electrum's mobile-style QML user interface. It makes several on-screen data lists (transaction history, addresses, payment requests, invoices, and Lightning channels) properly declare their parent UI object. In Qt/QML, setting a parent helps ensure child objects are cleaned up when the parent is destroyed, which can prevent memory leaks or stale references. There is no direct evidence in the commit that this fixes an active security vulnerability, but it improves object lifetime hygiene and could indirectly prevent UI-related crashes or use-after-free issues.

AI review queuedqml: qetransactionlistmodel: refresh on payment_succeeded, request_status callbacksby Sander van Grieken · 75240bce · Oct 28, 2026 · 3 filesMessage 50 · ThinInformational 17Details
Commit message · Sander van Grieken

qml: qetransactionlistmodel: refresh on payment_succeeded, request_status callbacks

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 17/100

This commit is a UI refresh fix for the Electrum mobile/QML wallet. It moves responsibility for updating the transaction history list from one wallet component to the transaction list model itself, and adds refresh triggers when a Lightning payment succeeds or a payment request is paid. It also fixes a minor typo where the wrong wallet variable was used when checking whether an address can be deleted. There is no direct security vulnerability here; it is a correctness and consistency improvement for the user interface.

AI review queuedqml: qetransactionlistmodel mark self dirty on tx eventsby f321x · 11800932 · Oct 28, 2026 · 2 filesMessage 81 · StrongInformational 18Details
Commit message · f321x

qml: qetransactionlistmodel mark self dirty on tx events

Only QEWallet marked its own history model dirty and refreshed it, so
any other QETransactionListModel, like the per-address history model of
QEAddressDetails, was never refreshed after it got created. Removing a
local tx left it in the address history and new txs never showed up.

Move the dirty tracking on {new,removed}_transaction and
adb_tx_height_changed, and the refresh on wallet_updated, from QEWallet
into the model, as done for the address/coin list model in c74e790b5.
Lightning history changes don't come with tx events (#9856), so only
models including lightning are marked dirty on every wallet_updated.

81/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 18/100

This commit fixes a user-interface bug in Electrum's mobile/QML wallet view. Previously, address-specific transaction lists were not refreshed when transactions arrived, were removed, or changed confirmation status, so stale or missing entries could remain on screen. The fix moves the refresh logic into the transaction list model itself so all such lists update correctly. There is no indication this is a security vulnerability.

AI review queuedqml: set parent on list models created by QEWallet and QEAddressDetailsby f321x · 831041b0 · Oct 28, 2026 · 2 filesMessage 73 · AdequateInformational 21Details
Commit message · f321x

qml: set parent on list models created by QEWallet and QEAddressDetails

The list models were created without a QObject parent, so their
lifetime was only tied to the Python reference. Parent them to the
owning object so they are destroyed (and unregister their callbacks)
together with it, e.g. when an AddressDetails page is closed.

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 21/100

This change fixes how certain list-like data objects in Electrum's mobile-style QML interface are tied to their parent screens. Previously, these objects were only kept alive by Python references and might not be cleaned up promptly when a wallet or address details page was closed. By giving them a proper parent object, they are destroyed together with the page, which also removes their internal callback hooks. This is a cleanup and stability improvement rather than a direct fix for an active exploit, but poor object lifetime management can sometimes lead to crashes or subtle bugs.

AI review queuedMerge pull request #11088 from accumulator/self_dirty_qeaddresslistmodelby accumulator · 31121bef · Oct 28, 2026 · 2 filesMessage 73 · AdequateInformational 17Details
Commit message · accumulator

Merge pull request #11088 from accumulator/self_dirty_qeaddresslistmodel

qml: qeaddresslistmodel mark self dirty on {new,removed}_transaction events

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Informational 17/100

This commit moves responsibility for refreshing an address list in Electrum's QML (mobile-style) user interface. Previously, the wallet object told the address list to refresh when transactions arrived or were removed. Now the address list listens for those events itself and refreshes. This is a code-quality/refactoring change with no visible security impact.