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 43 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 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.

AI review queuedqml: qeaddresslistmodel mark self dirty on {new,removed}_transaction eventsby Sander van Grieken · c74e790b · Oct 28, 2026 · 2 filesMessage 50 · ThinInformational 17Details
Commit message · Sander van Grieken

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

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 small UI cleanup in Electrum's QML (mobile/desktop modern interface) code. It moves responsibility for refreshing the address list when transactions arrive or are removed from one file to another, so the address list model refreshes itself instead of relying on the wallet object to tell it to refresh. There is no indication this fixes a security vulnerability; it appears to be a maintainability or correctness fix for UI consistency.

AI review queuedMerge pull request #11072 from SomberNight/202610_fixesby ghost43 · b774e151 · Oct 23, 2026 · 9 filesMessage 58 · ThinHigh 80Details
Commit message · ghost43

Merge pull request #11072 from SomberNight/202610_fixes

adb/txbatcher: assorted 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 · High 80/100

This commit hardens Electrum so that incoming transactions spending the user's own coins are checked for valid signatures before being accepted into the wallet. Previously, a malicious or buggy server could feed the wallet a transaction that appeared to spend the user's funds but had an invalid or forged signature, causing balance confusion, incorrect history, or unsafe follow-on transactions. The patch also fixes related bugs in the transaction-batching (RBF) code so the wallet does not accidentally pay outputs introduced by someone else's transaction replacement.

AI review queuedinterface: skip stale header notifications in run_fetch_blocksby f321x · c009a3a0 · Oct 23, 2026 · 1 fileMessage 73 · AdequateInformational 18Details
Commit message · f321x

interface: skip stale header notifications in run_fetch_blocks

run_fetch_blocks processed every queued headers notification in turn,
each one costing a backward search and a catch-up request. Only the
newest notification matters, as _process_header_at_tip fetches any
missing headers up to it, so drop the older ones.

This showed up on regtest when bitcoind mines slowly (slow fsync):
for `new_blocks 300` e-x sent a notification every ~5 blocks, and as
its padded transport holds small responses for up to 1s, catching up
took ~100s, timing out test_lnwatcher_waits_until_fees_go_down.
With this change it takes ~2s.

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 18/100

This commit is a performance optimization, not a security fix. It changes how Electrum handles notifications about new Bitcoin blocks so that if several notifications pile up, only the newest one is processed. This avoids wasting time re-checking older blocks and prevents test timeouts on slow systems. There is no indication it fixes a vulnerability or protects against an attack.

AI review queuedci: regtest: bump electrumx to 2.0.0by f321x · 1bf86a3c · Oct 23, 2026 · 1 fileMessage 80 · StrongInformational 15Details
Commit message · f321x

ci: regtest: bump electrumx to 2.0.0

Use the latest electrumx release in the regtest CI. Since 2.0.0
plyvel is no longer a default dependency, so install the leveldb extra.

80/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Why it was queued
documentation-only discountsecond-pass: broader security terminology
AI analysis · Informational 15/100

This is a routine update to Electrum's automated testing setup. It changes which version of ElectrumX (a separate server component used only in tests) is installed during continuous integration runs. There is no user-facing change and no security issue visible in the commit.

AI review queuedMerge pull request #11068 from f321x/get_full_history_labelsby ghost43 · 3dbf0ba8 · Oct 23, 2026 · 2 filesMessage 73 · AdequateInformational 18Details
Commit message · ghost43

Merge pull request #11068 from f321x/get_full_history_labels

wallet: use db instead of adb in _get_default_label_for_txid (speedup 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
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Informational 18/100

This is a small performance optimization in the Electrum Bitcoin wallet. It swaps which internal database object is used when fetching transaction data for history labels and address display. There is no obvious security bug introduced by the change itself.

Security candidateMerge "verify_sigs": adb: check sigs of is_mine txins of unconf txsby SomberNight · 90fe3082 · Oct 23, 2026 · 7 filesMessage 83 · StrongCritical 90Details
Commit message · SomberNight

Merge "verify_sigs": adb: check sigs of is_mine txins of unconf txs

verify signatures of wallet.is_mine inputs for mempool txs only

PR: SE#1 (first 3 commits)

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
Why it was queued
signing boundarysigning or wallet pathmerge-commit duplicate discount
AI analysis · Critical 90/100

This commit fixes a security flaw in the Electrum Bitcoin wallet where a malicious server could silently replace a transaction the user just broadcast with a fake version that spent the user's coins. Because the wallet trusted server-provided transaction data without checking signatures on inputs that spend the user's own coins, it could be tricked into thinking the fake transaction was valid. The attacker could then lure the user into using RBF (Replace-By-Fee) to 'bump' the fake transaction, which actually signed and sent the user's funds to the attacker. The vendor reports two victim reports and at least one loss of funds. The fix makes the wallet verify signatures for any input that spends coins belonging to the user before accepting a transaction, and it holds back server-claimed 'mined' transactions until they are independently verified.

AI review queuedMerge pull request #11069 from spesmilo/legacy_sighashesby ghost43 · 3b56d3ea · Oct 21, 2026 · 3 filesMessage 73 · AdequateLow 31Details
Commit message · ghost43

Merge pull request #11069 from spesmilo/legacy_sighashes

transaction: support all sighash types in legacy preimage

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 31/100

This commit expands Electrum's transaction-signing code to correctly handle older, rarely-used Bitcoin signature modes (SIGHASH_NONE, SIGHASH_SINGLE, and SIGHASH_ANYONECANPAY) for pre-SegWit ('legacy') transactions. Previously these modes were rejected or only partially supported, which could prevent users from signing or verifying certain valid-but-non-standard transactions. The change also adds a 'strict' flag so callers can choose between standard-wallet policy and raw consensus behavior, and imports Bitcoin Core's official test vectors to verify correctness.

Security candidatetransaction: support all sighash types in legacy preimageby ThomasV · 0e546660 · Oct 21, 2026 · 3 filesMessage 83 · StrongLow 30Details
Commit message · ThomasV

transaction: support all sighash types in legacy preimage

serialize_preimage now supports NONE, SINGLE and ANYONECANPAY for
legacy inputs. With strict=False, any sighash byte is accepted for
non-taproot inputs, as in consensus; by default, undefined sighash
bytes are rejected, as in mempool policy. verify_sig_for_txin takes
the same parameter, and handles legacy SIGHASH_SINGLE without a
corresponding output.

Tested against the legacy sighash vectors of Bitcoin Core.

83/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
consensus or confidential-proof validationsigning or wallet path
AI analysis · Low 30/100

This commit expands Electrum's transaction-signing code to correctly handle several Bitcoin 'sighash' modes that were previously unsupported for old-style (legacy) inputs. Sighash flags tell the network which parts of a transaction the signature covers. Before this change, legacy inputs using SIGHASH_NONE, SIGHASH_SINGLE, or SIGHASH_ANYONECANPAY would fail. The patch also adds a 'strict' option: by default it rejects unusual sighash bytes (matching normal network policy), but with strict=False it accepts any byte the Bitcoin consensus rules allow. It includes tests that compare Electrum's output against Bitcoin Core's official sighash test vectors. There is no indication in the commit that this fixes an active security vulnerability; it appears to be a correctness and compatibility improvement.

AI review queuedupdate localeby SomberNight · 8f2a2b22 · Oct 21, 2026 · 1 fileMessage 18 · OpaqueInformational 15Details
Commit message · SomberNight

update locale

pull in latest frozen translations

18/100 · OpaqueMessage clarity
✓ Subject identifies a change! Too few words to establish purpose! No meaningful explanatory body
Why it was queued
translation-only discountsecond-pass: opaque commit message
AI analysis · Informational 15/100

This commit only updates the project's translation files (locale) by switching a Git submodule to a newer version. There are no code changes visible in the commit, and nothing in the commit message or diff suggests any security relevance.

Security candidateandroid build: don't reinstall ca-certificates from the pinned snapshotby f321x · 29ab18fb · Oct 21, 2026 · 1 fileMessage 93 · StrongInformational 21Details
Commit message · f321x

android build: don't reinstall ca-certificates from the pinned snapshot

In the other build containers (except for AppImage due to the stale image)
we don't pin ca-certificates.
In the Android build we indirectly pinned it by re-installing it
after the apt.sources.list snapshot got installed.
To not be affected by the revoked CA (https://emudhra.we-have-a-problem.com/)
we could either manually patch it out (similar to the AppImage)
Dockerfile, or not pin the ca-authorities (and its transitive installs),
as we alredy successfully do with the other images.
Considering we trust debian the simpler solution seems to be
not pinning it as long as no reproducibility issues appear.

93/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Links an issue, advisory, or supporting reference
Why it was queued
access control
AI analysis · Informational 21/100

This commit changes how the Android version of the Electrum Bitcoin wallet is built. Previously, the build process reinstalled a specific pinned (fixed) version of the list of trusted website certificates (ca-certificates). The commit removes that pinned reinstall so the Android build instead uses the normal up-to-date certificate list from Debian. The reason given is to avoid being stuck with a revoked/removed certificate authority (emudhra) that was included in the pinned snapshot. This is a build-hygiene change rather than a fix for an active attack on users.

Security candidateappimage build: distrust emSign ECC Root CA - G3 in build containerby f321x · 78fcc560 · Oct 21, 2026 · 1 fileMessage 86 · StrongModerate 62Details
Commit message · f321x

appimage build: distrust emSign ECC Root CA - G3 in build container

Its private key leaked (https://emudhra.we-have-a-problem.com/).
The appimage container installs ca-certificates from our pinned
bullseye snapshot, and bullseye won't get a fixed ca-certificates
as it is EOL. So deselect the root manually.

The wine and sdist containers are not affected: they get
ca-certificates from the live debian repos (incl. -security), so
freshly built images already have the fixed version.

Related https://github.com/spesmilo/electrum/issues/10950

86/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference✓ Names security-relevant behavior explicitly
Why it was queued
secret or key material
AI analysis · Moderate 62/100

Electrum's AppImage build process used a Debian 'bullseye' Linux container whose built-in list of trusted web security certificates still included a root certificate from eMudhra/emSign that had its private key leaked. Because the old Debian release no longer receives updates, Electrum manually removes that certificate from the build container so that future AppImage builds do not implicitly trust it. This is a supply-chain/build-hardening fix; it does not change the Electrum wallet application itself.

AI review queuedrequirements: require certifi>=2026.10.19by f321x · 407ba521 · Oct 21, 2026 · 1 fileMessage 81 · StrongModerate 64Details
Commit message · f321x

requirements: require certifi>=2026.10.19

ensure users installing from source get a certifi that distrusts the
compromised eMudhra emSign CAs.
see https://discuss.python.org/t/information-for-python-users-regarding-emudhra-emsign-ca-certificate-security-incident/109576

81/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference✓ Names security-relevant behavior explicitly
Why it was queued
documentation-only discountsecond-pass: broader security terminology
AI analysis · Moderate 64/100

This commit updates Electrum's dependency list to require a newer version of the 'certifi' package. Certifi provides the list of trusted certificate authorities used to secure internet connections. The newer version removes trust in two certificate authorities (eMudhra/emSign) that were recently compromised. Without this update, users installing Electrum from source could trust fraudulent certificates, allowing attackers to impersonate websites or Electrum servers in man-in-the-middle attacks.

AI review queuedbuild: bump pip (25.1.1 -> 26.2.2)by f321x · c6dcedc0 · Oct 21, 2026 · 9 filesMessage 93 · StrongLow 49Details
Commit message · f321x

build: bump pip (25.1.1 -> 26.2.2)

pip vendors certifi. pip 26.2.2 is the first release whose vendored
certifi distrusts the compromised eMudhra emSign CAs.
see https://discuss.python.org/t/information-for-python-users-regarding-emudhra-emsign-ca-certificate-security-incident/109576

93/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference✓ Names security-relevant behavior explicitly
Why it was queued
documentation-only discountsecond-pass: broader security terminology
AI analysis · Low 49/100

This commit updates the bundled copy of pip used when building Electrum from version 25.1.1 to 26.2.2. The newer pip includes an updated list of trusted certificate authorities that no longer trusts two certificate authorities (eMudhra and emSign) that were recently compromised. If Electrum's build process downloads dependencies over HTTPS, an attacker who could trick the old trust list could potentially intercept or tamper with those downloads. The change is a preventive security hardening step, not a fix for a bug in Electrum's own wallet code.

AI review queuedbuild: bump certifi (2026.7.22 -> 2026.10.19)by f321x · 9529c15a · Oct 21, 2026 · 2 filesMessage 93 · StrongModerate 62Details
Commit message · f321x

build: bump certifi (2026.7.22 -> 2026.10.19)

certifi 2026.10.19 distrusts the compromised eMudhra emSign CAs.
see https://discuss.python.org/t/information-for-python-users-regarding-emudhra-emsign-ca-certificate-security-incident/109576

93/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference✓ Names security-relevant behavior explicitly
Why it was queued
documentation-only discountsecond-pass: broader security terminology
AI analysis · Moderate 62/100

This commit updates the 'certifi' package, which provides the list of trusted certificate authorities used by the software. The new version removes trust in two certificate authorities (eMudhra and emSign) that were reportedly compromised. If left unpatched, an attacker who controlled those certificate authorities could potentially issue fake security certificates and intercept or tamper with encrypted network connections made by the application. The commit itself is a routine dependency update with no direct proof of active exploitation.

AI review queuedMerge pull request #11065 from SomberNight/202610_lnsymmetry_followupsby ThomasV · 11e3aa9d · Oct 20, 2026 · 2 filesMessage 58 · ThinInformational 23Details
Commit message · ThomasV

Merge pull request #11065 from SomberNight/202610_lnsymmetry_followups

LN config symmetry followups

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 · Informational 23/100

This commit is a follow-up cleanup for Lightning Network (LN) channel configuration handling. It makes some stored fields optional, adds a warning comment about not storing a private key for certain channel types, and makes a database upgrade more robust by inlining a constant and adding a clearer error message if an old channel is missing required data. There is no direct fix for an active exploit or remote vulnerability in the diff itself.

AI review queuedwallet_db: convert_version_74: duplicate map from lnutil for robustnessby SomberNight · f1f2b611 · Oct 20, 2026 · 1 fileMessage 73 · AdequateLow 27Details
Commit message · SomberNight

wallet_db: convert_version_74: duplicate map from lnutil for robustness

Previously we assumed `DERIVED_LOCAL_BASEPOINTS` would never change in future code.

```diff
diff --git a/electrum/lnutil.py b/electrum/lnutil.py
index efded00e80..b0b400d965 100644
--- a/electrum/lnutil.py
+++ b/electrum/lnutil.py
@@ -2131,6 +2133,7 @@ DERIVED_LOCAL_BASEPOINTS = {
'htlc_basepoint': LnKeyFamily.HTLC_BASE,
'delayed_basepoint': LnKeyFamily.DELAY_BASE,
'revocation_basepoint': LnKeyFamily.REVOCATION_BASE,
+ 'xx': LnKeyFamily.FUNDING_ROOT_KEY,
}

```

```
Traceback (most recent call last):
File "/home/user/wspace/electrum/electrum/gui/qt/__init__.py", line 441, in start_new_window
wallet = self._start_wizard_to_select_or_create_wallet(path)
File "/home/user/wspace/electrum/electrum/gui/qt/__init__.py", line 513, in _start_wizard_to_select_or_create_wallet
wallet = self.daemon.load_wallet(wallet_file, password, upgrade=True)
File "/home/user/wspace/electrum/electrum/daemon.py", line 496, in func_wrapper
return func(self, *args, **kwargs)
File "/home/user/wspace/electrum/electrum/daemon.py", line 522, in load_wallet
wallet = self._load_wallet(
path, password, upgrade=upgrade, config=self.config, force_check_password=force_check_password)
File "/home/user/wspace/electrum/electrum/util.py", line 518, in do_profile
o = func(*args, **kw_args)
File "/home/user/wspace/electrum/electrum/daemon.py", line 556, in _load_wallet
db = WalletDB(storage.read(), storage=storage, upgrade=upgrade)
File "/home/user/wspace/electrum/electrum/wallet_db.py", line 1714, in __init__
JsonDB.__init__(
~~~~~~~~~~~~~~~^
self,
^^^^^
...<3 lines>...
upgrader=partial(upgrade_wallet_db, do_upgrade=upgrade),
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
)
^
File "/home/user/wspace/electrum/electrum/json_db.py", line 107, in __init__
data, was_upgraded = upgrader(data)
~~~~~~~~^^^^^^
File "/home/user/wspace/electrum/electrum/wallet_db.py", line 1698, in upgrade_wallet_db
dbu.upgrade()
~~~~~~~~~~~^^
File "/home/user/wspace/electrum/electrum/util.py", line 518, in do_profile
o = func(*args, **kw_args)
File "/home/user/wspace/electrum/electrum/wallet_db.py", line 266, in upgrade
self._convert_version_74()
~~~~~~~~~~~~~~~~~~~~~~~~^^
File "/home/user/wspace/electrum/electrum/wallet_db.py", line 1548, in _convert_version_74
check(channel_id, name, keypair.privkey, local_config[name].pop('privkey'))
~~~~~~~~~~~~^^^^^^
KeyError: 'xx'
```

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: broader security terminologysecond-pass: security-sensitive path
AI analysis · Low 27/100

This commit fixes a wallet-upgrade bug, not a security vulnerability. Electrum's database upgrade code for old Lightning wallets imported a list of 'basepoints' (cryptographic key derivation points) from another file. When that other file later gained a new entry, the upgrade code broke with a KeyError and users could not open their wallets. The fix copies the exact list of basepoints needed for the upgrade directly into the upgrade function so future changes elsewhere cannot break it. There is no attacker-controlled path and no theft or code-execution risk.

AI review queuedwallet_db: convert_version_74: handle old chans lacking channel_seedby SomberNight · c697cee6 · Oct 20, 2026 · 1 fileMessage 73 · AdequateInformational 20Details
Commit message · SomberNight

wallet_db: convert_version_74: handle old chans lacking channel_seed

ref https://github.com/spesmilo/electrum/pull/10994#discussion_r4307662947

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 pathsecond-pass: security-sensitive path
AI analysis · Informational 20/100

This commit fixes a wallet-upgrade crash. Very old Electrum Lightning channels created from pre-release code before April 2020 did not store a 'channel_seed'. The upgrade code assumed the field always existed and would crash when it was missing. The patch detects the missing field and shows a clear error message telling the user how to recover, instead of crashing silently or with a confusing error.

AI review queuedwallet_db: add comment to explain db upgrades should be self-containedby SomberNight · 7a661f9b · Oct 20, 2026 · 1 fileMessage 50 · ThinInformational 15Details
Commit message · SomberNight

wallet_db: add comment to explain db upgrades should be self-contained

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 15/100

This commit only adds a documentation comment inside the Electrum wallet database upgrade code. It explains that future database migrations should be self-contained so that later code changes do not accidentally break old upgrade paths. No code behavior is changed, and there is no security fix or vulnerability introduced.

AI review queuedMerge pull request #11060 from f321x/make_unsigned_tx_copy_base_txby ThomasV · eae6c9ba · Oct 20, 2026 · 1 fileMessage 73 · AdequateLow 47Details
Commit message · ThomasV

Merge pull request #11060 from f321x/make_unsigned_tx_copy_base_tx

wallet: make_unsigned_transaction: don't mutate 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 47/100

This commit fixes a bug where Electrum's wallet software would accidentally modify a transaction object supplied by the caller when creating a new unsigned transaction. The fix makes a private copy before stripping signatures, preventing unintended changes to the caller's original transaction. This is a defensive correctness fix rather than a clear-cut remote exploit, but it could prevent subtle wallet behavior bugs or UI inconsistencies.

AI review queuedMerge pull request #11051 from accumulator/keystore_enable_disable_fixesby Felix · 2031457d · Oct 20, 2026 · 3 filesMessage 58 · ThinModerate 59Details
Commit message · Felix

Merge pull request #11051 from accumulator/keystore_enable_disable_fixes

Keystore enable disable 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 · Moderate 59/100

This commit fixes several bugs in Electrum's feature that lets users temporarily disable or re-enable a wallet's keystore (the part that holds the private signing key). The changes prevent users from accidentally locking themselves out of Lightning funds, stop unrelated seeds from being accepted when re-enabling a keystore, ensure disabled seed material is actually removed from the wallet file, and fix password/encryption handling when only the keystore (not the whole wallet file) was protected. These are reliability and safety fixes rather than a remote-exploitable vulnerability, but mishandling of private key material and Lightning funds has real security consequences.

AI review queuedMerge pull request #11033 from f321x/android_depsby ThomasV · 38cc1dbe · Oct 19, 2026 · 2 filesMessage 68 · AdequateInformational 19Details
Commit message · ThomasV

Merge pull request #11033 from f321x/android_deps

android: rm androidx dependency, update Java 17 -> 21

68/100 · AdequateMessage clarity
✓ 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 commit updates Electrum's Android build setup by switching from a manually downloaded Java 17 to the standard Debian Java 21 package, removing an AndroidX support library dependency, and updating the python-for-android build tool version. These are build/maintenance changes rather than a fix for a known security flaw. The main security angle is that using a current, standard Java version and removing an unnecessary third-party dependency slightly reduces the attack surface and maintenance risk for the Android build environment.

Security candidatepsbt_nostr: fix button container PsbtReceiveDialog.qmlby Sander van Grieken · 363e49e1 · Oct 16, 2026 · 1 fileMessage 50 · ThinInformational 15Details
Commit message · Sander van Grieken

psbt_nostr: fix button container PsbtReceiveDialog.qml

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing boundarysigning or wallet path
AI analysis · Informational 15/100

This is a one-line UI component rename in a QML dialog used by a Bitcoin wallet plugin. The change replaces a custom 'ButtonContainer' with a 'DialogButtonContainer'. There is no security-relevant content in the commit message, title, or diff, and no references suggest otherwise.