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.
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.
Security candidateMerge pull request #11111 from accumulator/qml_bip39recovery_task_refactorby Felix · 896a68d7 · Nov 5, 2026 · 2 filesMessage 73 · AdequateInformational 17Details
Commit message · Felix
Merge pull request #11111 from accumulator/qml_bip39recovery_task_refactor
qml: refactor BIP39 account scan to asyncio tasks.
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
secret or key materialcryptography-sensitive pathmerge-commit duplicate discount
AI analysis · Informational 17/100
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 when closed. There is no direct evidence in the diff of a security vulnerability being fixed.
Security candidateqml: refactor BIP39 account scan to asyncio tasks.by Sander van Grieken · 00ed883a · Nov 4, 2026 · 2 filesMessage 73 · AdequateInformational 12Details
Commit message · Sander van Grieken
qml: refactor BIP39 account scan to asyncio tasks.
The thread around waiting on a Future was unnecessary, and can simply be done using the Future's done_callback.
This also allows better handling of the scan's lifecycle, e.g. when the wizard starts a scan, goes back a page, then next and scan again. The extra thread was more complex to clean up.
73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
secret or key materialcryptography-sensitive path
AI analysis · Informational 12/100
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 appears to be a maintainability and lifecycle-handling improvement.
Security candidateqt: paytoedit: complete contacts to their key, not 'name <key>'by f321x · dd1b50fb · Nov 4, 2026 · 2 filesMessage 73 · AdequateModerate 59Details
Commit message · f321x
qt: paytoedit: complete contacts to their key, not 'name <key>'
The contact completer lists 'name <key>', and QLineEdit put that text into the edit when an item was highlighted or chosen. That is not a payment identifier, so after 1s the edit timer set an invalid one. If the key of a chosen contact was still being resolved then, the result was dropped and the spinner never stopped.
Highlighting or choosing a contact now puts its key into the edit. While the list is open nothing is looked up, so browsing it doesn't resolve every highlighted contact. The edit is read within 1s after the list is closed, or right away when a contact is chosen.
When the text is edited, the old payment identifier is dropped until the new one is set, so Pay, Save and Max are disabled meanwhile. Before, Pay could pay the previous recipient for up to 1s after a new one was typed.
73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
privacy or spend-authorization protocol
AI analysis · Moderate 59/100
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.com>' for up to about one second, and during that window the 'Pay' button could still use the previous recipient. The patch makes the field immediately switch to the actual payment identifier (e.g. alice@example.com), pauses lookups while the dropdown is open, and disables Pay/Save/Max while the recipient text is being edited. It also fixes a related UI spinner that could keep spinning forever.
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.
Lower-priorityMerge pull request #11106 from accumulator/qml_addresses_restore_search_on_openby accumulator · 27ea125e · Nov 3, 2026 · 1 fileMessage 73 · AdequateTriage 0Details
Commit message · accumulator
Merge pull request #11106 from accumulator/qml_addresses_restore_search_on_open
qml: restore active search text when opening Addresses page
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-priorityqml: restore active search text when opening Addresses pageby Sander van Grieken · 3bb15166 · Nov 3, 2026 · 1 fileMessage 50 · ThinTriage 0Details
Commit message · Sander van Grieken
qml: restore active search text when opening Addresses page
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-priorityMerge pull request #11104 from accumulator/qml_passworddialog_avoid_doubletapby accumulator · 49db4fd8 · Nov 3, 2026 · 1 fileMessage 73 · AdequateTriage 0Details
Commit message · accumulator
Merge pull request #11104 from accumulator/qml_passworddialog_avoid_doubletap
qml: avoid potential Ok signal by tapping while dialog is closing
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 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.
Lower-priorityMerge pull request #11103 from f321x/bump_python_for_androidby ghost43 · 5ce8d156 · Nov 2, 2026 · 1 fileMessage 73 · AdequateTriage 0Details
Commit message · ghost43
Merge pull request #11103 from f321x/bump_python_for_android
android: bump python-for-android checkout
73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Pump p4a to latest commit. I checked that intents are still working (e.g. opening Electrum by clicking on a bitcoin:bc1... address on a website). Also ran the build on a Pixel 10 emulator.
68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
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
✓ 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.
✓ 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.
Lower-priorityutil: is_hex_str to optionally support odd-len stringsby SomberNight · b23af1da · Oct 30, 2026 · 3 filesMessage 81 · StrongTriage 0Details
Commit message · SomberNight
util: is_hex_str to optionally support odd-len strings
- extracted from https://github.com/spesmilo/electrum/pull/10627 - but also in https://github.com/spesmilo/electrumx/commit/792780c7f5d0231f7b0784cfcad3106982b57c89
81/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Lower-priorityMerge pull request #11095 from f321x/gossip_reject_selfloop_chan_annby ghost43 · f829e382 · Oct 30, 2026 · 2 filesMessage 73 · AdequateTriage 0Details
Commit message · ghost43
Merge pull request #11095 from f321x/gossip_reject_selfloop_chan_ann
channel_db: stricter channel announcement parsing
73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Skip channel_announcement gossip messages if node_ids are equal.
65/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
Lower-priorityMerge pull request #11087 from f321x/qml_txinput_click_addressby accumulator · d9eef974 · Oct 30, 2026 · 6 filesMessage 73 · AdequateTriage 0Details
Commit message · accumulator
Merge pull request #11087 from f321x/qml_txinput_click_address
qml: TxInput: allow clicking on is_mine addresses
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-priorityqml: TxInput: tap short id to open the funding txby f321x · 3323d64a · Oct 30, 2026 · 6 filesMessage 68 · AdequateTriage 0Details
Commit message · f321x
qml: TxInput: tap short id to open the funding tx
Tapping the short id of an input now opens the TxDetails of the transaction that created the coin, like the prevout link in the Qt tx dialog. It is only enabled if that transaction is in the wallet db.
Rename allowClickAddress to allowClick, as it now gates both links.
68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
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.
Lower-priorityMerge pull request #10749 from accumulator/qml_address_historyby Felix · 051ed068 · Oct 29, 2026 · 3 filesMessage 58 · ThinTriage 0Details
Commit message · Felix
Merge pull request #10749 from accumulator/qml_address_history
qml: add new page; history for address
58/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body