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
tests: lnhtlc: add testcase for get_all_not_irrevocably_removed_htlcs
60/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
Lower-priorityversion.py: bump version to 4.8.2by f321x · f2629366 · Sep 10, 2026 · 1 fileMessage 45 · ThinTriage 0Details
Commit message · f321x
version.py: bump version to 4.8.2
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-priorityadd release notes for version 4.8.2by f321x · c48cc100 · Sep 10, 2026 · 1 fileMessage 45 · ThinTriage 0Details
Commit message · f321x
add release notes for version 4.8.2
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI review queuedMerge pull request #10945 from accumulator/stale_utxo_data_fixesby Felix · e20b24c0 · Sep 10, 2026 · 9 filesMessage 58 · ThinLow 46Details
Commit message · Felix
Merge pull request #10945 from accumulator/stale_utxo_data_fixes
Stale utxo data fixes
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
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Low 46/100
This commit fixes cases where Electrum's wallet cache could hold onto outdated information about coins and transactions after blockchain reorganizations or mempool changes. For example, if a transaction was previously thought to be mined but later returned to the mempool, the wallet might still treat it as confirmed and display an incorrect 'short ID' for it. The patch adds cache invalidation calls and makes the code consistently check whether a transaction is actually mined before showing a compact short ID. It is a correctness/bug-fix change rather than a direct remote-exploitable vulnerability, but stale cached state could mislead users or downstream logic about confirmation status.
...to deduplicate setting the block_height and block_txpos attributes on a txin from a TxMinedInfo.
60/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit is a simple code cleanup: it replaces two repeated lines that set a transaction input's block height and position with a single helper method called set_mined_info. There is no change in behavior, no bug fix, and no security relevance visible in the diff.
Consolidate a bit the assembly of short_id from tx_height and tx_pos across the qt and util code.
60/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This is a small internal code cleanup in the Electrum Bitcoin wallet. It moves the logic that builds a compact transaction identifier (like '123x4') into one shared helper method, and removes a duplicate helper class. There is no user-facing behavior change and no security fix.
Lower-priorityMerge pull request #10912 from sashazykov/fix-feerate-quantizationby Felix · 1c0bc235 · Sep 10, 2026 · 2 filesMessage 73 · AdequateTriage 0Details
Commit message · Felix
Merge pull request #10912 from sashazykov/fix-feerate-quantization
fee_policy: don't quantize explicitly set feerates
73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
The `NWCServer` was still catching `asyncio.CancelledError` however this is not neccessary anymore since 9b425692 (#10689). Catching the `CancelledError` made it block daemon shutdown: ``` 24.48 | I | daemon.Daemon | stopping plugins 24.48 | I | plugin.Plugins | stopped 24.48 | I | daemon.Daemon | removing lockfile 24.48 | I | daemon.Daemon | stopped 24.48 | D | plugins.nwc.nwcserver.NWCServer | Restarting nwc event handler ^CException ignored while joining a thread in _thread._shutdown(): Traceback (most recent call last): File "/usr/lib64/python3.14/threading.py", line 1583, in _shutdown _thread_shutdown() KeyboardInterrupt: ```
76/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
contrib: build appimage: fetch ca-certificates from pinned sources
Fetch ca-certificates from the pinned sources similar to the other packages. This needs to be done because the default sources of debian 11 stopped working. Because the pinned sources are https they need to be patched to http before using them to get ca-certificate, as https requires ca-certificates. This is safe as packages are signed by debian (the previous way of installing ca-certificates also used http).
85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode
Why it was queued
second-pass: broader security terminology
AI analysis · Informational 19/100
This commit changes how the Electrum AppImage build container first obtains trusted web certificates. Because the build's pinned Debian package sources use HTTPS, the container needs certificates before it can talk to them. The old method stopped working on Debian 11, so the patch temporarily switches the package source to plain HTTP just long enough to install the certificate bundle, then switches back. The packages are still verified by Debian's own signatures, so this is a build-fix rather than a security vulnerability, though it does introduce a brief HTTP download step inside the isolated build environment.
Lower-prioritypi: assert script_to_string result always parses to its input bytesby Sander van Grieken · fe38a34d · Sep 9, 2026 · 1 fileMessage 50 · ThinTriage 0Details
Commit message · Sander van Grieken
pi: assert script_to_string result always parses to its input bytes
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Merge pull request #10871 from accumulator/hww_deprecation_bb01_archos
hww: add a deprecation message popup at get_xpub time for bitbox01 and safe-t
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 adds user-facing warning popups that appear when Electrum interacts with two older hardware wallets: the Digital Bitbox (BitBox01) and the Archos Safe-T mini. The message tells users these devices are being deprecated, are no longer supported by their manufacturers, and that users should move their coins to a modern device. It is a notification-only change, not a security fix or vulnerability.
Merge pull request #10947 from fametrano/btclib-666-error-messages
descriptor: fix two incorrect error messages
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 #10953 from accumulator/fix_6791by Felix · 73ffb292 · Sep 9, 2026 · 1 fileMessage 83 · StrongTriage 0Details
Commit message · Felix
Merge pull request #10953 from accumulator/fix_6791
qt: fix regression for #6791 introduced in 48916f56b
83/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
qt: fix onchain invoice dialog exc for script outputs
Fixes exception when double clicking on saved invoice (`show_onchain_invoice()`) for an invoice containing a script output (invoice.address is None).
``` 17.57 | E | gui.qt.exception_window.Exception_Hook | exception caught by crash reporter Traceback (most recent call last): File "/var/home/user/code/code_vm/electrum/electrum/gui/qt/my_treeview.py", line 341, in mouseDoubleClickEvent self.on_double_click(idx) ~~~~~~~~~~~~~~~~~~~~^^^^^ File "/var/home/user/code/code_vm/electrum/electrum/gui/qt/invoice_list.py", line 88, in on_double_click self.show_invoice(key) ~~~~~~~~~~~~~~~~~^^^^^ File "/var/home/user/code/code_vm/electrum/electrum/gui/qt/invoice_list.py", line 150, in show_invoice self.main_window.show_onchain_invoice(invoice) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^ File "/var/home/user/code/code_vm/electrum/electrum/gui/qt/main_window.py", line 1672, in show_onchain_invoice outputs_str = '\n'.join(map(lambda x: x.address + ' : ' + self.format_amount(x.value)+ self.base_unit(), invoice.outputs)) File "/var/home/user/code/code_vm/electrum/electrum/gui/qt/main_window.py", line 1672, in <lambda> outputs_str = '\n'.join(map(lambda x: x.address + ' : ' + self.format_amount(x.value)+ self.base_unit(), invoice.outputs)) ~~~~~~~~~~^~~~~~~ TypeError: unsupported operand type(s) for +: 'NoneType' and 'str' ```
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 21/100
This commit fixes a simple user-interface crash in Electrum's desktop (Qt) wallet. When a user double-clicked a saved invoice that pays to a raw Bitcoin script (rather than a normal address), the invoice details dialog threw an error and failed to open. It is a UI-only bug, not a way to steal funds or bypass security.
Merge pull request #10847 from SomberNight/202608_contrib_release_sh_mget_resume
contrib/release.sh: do not re-download full dist/ after gpg errors
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: fix regression for #6791 introduced in 48916f56bby Sander van Grieken · e7792e3b · Sep 9, 2026 · 1 fileMessage 68 · AdequateTriage 0Details
Commit message · Sander van Grieken
qt: fix regression for #6791 introduced in 48916f56b
68/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
AI review queuedadb: add missing cache invalidation sites for transitions to/from unverifiedby Sander van Grieken · b5a54166 · Sep 8, 2026 · 2 filesMessage 50 · ThinModerate 57Details
Commit message · Sander van Grieken
adb: add missing cache invalidation sites for transitions to/from unverified
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 · Moderate 57/100
This commit fixes missing cache invalidation in Electrum's wallet history code. When a transaction's status changed—such as when a confirmed transaction returned to the mempool after a blockchain reorganization—the wallet's internal caches were not always cleared. This could leave the wallet showing stale or inconsistent information, such as an outdated balance, an outdated transaction height, or a now-invalid 'short ID' used to identify coins. The fix adds explicit cache clearing at several state-transition points and includes tests demonstrating the problem.
AI review queuedwallet: keep height and txpos in sync in wallet.add_input_info()by Sander van Grieken · 4d66088b · Sep 8, 2026 · 5 filesMessage 85 · StrongLow 35Details
Commit message · Sander van Grieken
wallet: keep height and txpos in sync in wallet.add_input_info()
a change in funding tx status (e.g. from verified to back in mempool due to reorg) can change both height and txpos, but txpos was not kept in sync here. match what adb.get_transaction() does.
also guard TxInput.short_id on both height and txpos
85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 35/100
This commit fixes a bookkeeping bug in the Electrum Bitcoin wallet. When a transaction's status changes due to a blockchain reorganization (for example, a confirmed transaction temporarily returns to the unconfirmed mempool), the wallet was updating a coin's 'block height' but forgetting to update its 'position within the block' (txpos). The two values were getting out of sync, which could make the wallet display or identify coins incorrectly. The fix keeps both values together and adds a safety check so the short display ID is only used when both height and position are valid.
Lower-priorityMerge pull request #10944 from accumulator/qt_send_tab_pi_usable_consistencyby Felix · 722f7023 · Sep 8, 2026 · 2 filesMessage 73 · AdequateTriage 0Details
Commit message · Felix
Merge pull request #10944 from accumulator/qt_send_tab_pi_usable_consistency
qt: keep send button enabled/disabled using same 'pi is usable' check.
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 #10943 from accumulator/qt_new_channel_cap_check_fixby Felix · 8fa2c8f4 · Sep 8, 2026 · 2 filesMessage 73 · AdequateTriage 0Details
Commit message · Felix
Merge pull request #10943 from accumulator/qt_new_channel_cap_check_fix
qt: fix new channel option for old wallets that have lightning enabled,
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: keep send button enabled/disabled using same 'pi is usable' check.by Sander van Grieken · 44d04dc2 · Sep 8, 2026 · 2 filesMessage 73 · AdequateTriage 0Details
Commit message · Sander van Grieken
qt: keep send button enabled/disabled using same 'pi is usable' check.
before, a non-lightning wallet could inadvertently enable the Send button for lightning invoice via missing pi-is-usable check in on_amount_changed. (practical for LNURLp with amount-range, and amountless bolt11)
73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Lower-priorityMerge pull request #10931 from SomberNight/202609_lnutil_chantype_commentsby Felix · 05808484 · Sep 8, 2026 · 1 fileMessage 73 · AdequateTriage 0Details
Commit message · Felix
Merge pull request #10931 from SomberNight/202609_lnutil_chantype_comments
lnutil: LocalConfig.from_seed: add more asserts
73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference