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.
Message quality measures whether a commit identifies its scope, purpose, rationale, testing, and supporting references. It does not change the security-severity score.
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
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
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
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
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
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…
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…
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.
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
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
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…
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
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.
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)
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
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
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
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
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
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
Expand any commit for its author, full message, clarity score, changed files, triage signals, analysis, and source link.
Lower-priorityMerge pull request #11178 from SomberNight/202611_qml_sweep_loggingby ThomasV · c957528f · Nov 22, 2026 · 1 fileMessage 58 · ThinTriage 0Details
Commit message · ThomasV
Merge pull request #11178 from SomberNight/202611_qml_sweep_logging
qml: sweep: sanitize logging
58/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
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.
Lower-priorityMerge pull request #11167 from SomberNight/202611_contrib_freeze_cont_distroby Felix · 3751cc7e · Nov 20, 2026 · 1 fileMessage 73 · AdequateTriage 0Details
Commit message · Felix
Merge pull request #11167 from SomberNight/202611_contrib_freeze_cont_distro
contrib: harden freeze_containers_distro.sh against webserver
73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Lower-priorityMerge pull request #11168 from SomberNight/202611_interface_cpby ThomasV · 4a26b604 · Nov 20, 2026 · 1 fileMessage 73 · AdequateTriage 0Details
Commit message · ThomasV
Merge pull request #11168 from SomberNight/202611_interface_cp
interface: check earlier that server height is above checkpoint
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 discount
Lower-priorityQt: force QTextEdit to display plain textby ThomasV · ba6fa42e · Nov 20, 2026 · 1 fileMessage 45 · ThinTriage 0Details
Commit message · ThomasV
Qt: force QTextEdit to display plain text
keep a pointer to the original setText
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-priorityinterface: check earlier that server height is above checkpointby SomberNight · 4e4e94ae · Nov 19, 2026 · 1 fileMessage 73 · AdequateTriage 0Details
Commit message · SomberNight
interface: check earlier that server height is above checkpoint
check height before updating self.tip, as other tasks (e.g. get_block_headers) rely on self.tip, and they might still run for a bit after we raise here.
73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Lower-priorityMerge pull request #11160 from spesmilo/fix_batch_39by ghost43 · 278c3cf1 · Nov 18, 2026 · 1 fileMessage 73 · AdequateTriage 0Details
Commit message · ghost43
Merge pull request #11160 from spesmilo/fix_batch_39
txbatcher: do not bump a CPFP whose ctxs are mined (BATCH-39)
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 discount
Lower-priorityMerge pull request #11159 from spesmilo/fix_batch_23by ghost43 · f324568a · Nov 18, 2026 · 4 filesMessage 73 · AdequateTriage 0Details
Commit message · ghost43
Merge pull request #11159 from spesmilo/fix_batch_23
txbatcher: check timelocks against the tip of the main server (BATCH-23)
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 discount
Lower-prioritytests: toyserver: toynetwork to have sep. local_height/server_heightby SomberNight · 98558a2e · Nov 18, 2026 · 1 fileMessage 60 · AdequateTriage 0Details
Commit message · SomberNight
tests: toyserver: toynetwork to have sep. local_height/server_height
60/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
AI review queuedqml: crash reporter: handle threading.excepthook argumentsby Sander van Grieken · 2e7fe460 · Nov 18, 2026 · 1 fileMessage 73 · AdequateInformational 19Details
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.
Lower-priorityMerge pull request #11153 from spesmilo/do_not_batch_swap_inputsby ghost43 · fd9bf038 · Nov 17, 2026 · 2 filesMessage 58 · ThinTriage 0Details
Commit message · ghost43
Merge pull request #11153 from spesmilo/do_not_batch_swap_inputs
swaps: do not batch claims and refunds
58/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
merge-commit duplicate discount
Lower-priorityMerge pull request #11157 from f321x/fix_receive_history_quadraticby ghost43 · 60f90d05 · Nov 17, 2026 · 1 fileMessage 73 · AdequateTriage 0Details
Commit message · ghost43
Merge pull request #11157 from f321x/fix_receive_history_quadratic
adb: receive_history_callback: fix quadratic lookup in history
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 discount
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.
has regression in bridge. ref: https://github.com/trezor/trezor-firmware/issues/8317
95/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
documentation-only discount
Lower-priorityMerge pull request #11156 from f321x/limit_server_bannerby ghost43 · f155dfb3 · Nov 17, 2026 · 2 filesMessage 73 · AdequateTriage 0Details
Commit message · ghost43
Merge pull request #11156 from f321x/limit_server_banner
interface: limit length and characters of server banner
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 discount
Lower-priorityMerge pull request #11155 from spesmilo/txbatcher_test_helpersby Felix · e822c926 · Nov 17, 2026 · 1 fileMessage 73 · AdequateTriage 0Details
Commit message · Felix
Merge pull request #11155 from spesmilo/txbatcher_test_helpers
test_txbatcher: add helpers to mine a tx and to add swap funding 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