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 queuedstorage: add get_path methodby ThomasV · 6797e917 · Jun 6, 2026 · 7 filesMessage 35 · OpaqueInformational 15Details
Commit message · ThomasV
storage: add get_path method
35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: opaque commit messagesecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit is a simple internal code cleanup. It adds a new helper method called get_path() to the wallet storage class and updates various parts of the program to use that method instead of reading the storage path directly. There is no security fix or vulnerability here.
AI review queuedlnchan: if funding tx is coinbase tx, wait for maturityby SomberNight · 08f39f89 · Jun 5, 2026 · 2 filesMessage 73 · AdequateLow 42Details
Commit message · SomberNight
lnchan: if funding tx is coinbase tx, wait for maturity
✓ 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 · Low 42/100
This commit adds a check so that if a Lightning channel is funded by a coinbase transaction (newly created bitcoins from mining), Electrum waits for the standard 100-block maturity period before treating the funding as settled. Before this change, Electrum might have accepted an immature coinbase funding transaction too early, which could lead to an invalid channel state or forced channel closure if the coinbase output later becomes invalid or reorganized. The fix follows a recent update to the Lightning protocol specification.
AI review queuedModify the 'stored_at' syntax, so that it includes the full pathby ThomasV · 5494e827 · Jun 5, 2026 · 5 filesMessage 85 · StrongLow 27Details
Commit message · ThomasV
Modify the 'stored_at' syntax, so that it includes the full path
This may prevent collisions. More importantly, it also makes it possible to cache the subdict of 'registered_names' that is relevant to a given StoredDict, so that we do not need to walk the path on every conversion. (performance optimization, not part of this commit)
This is a backport from the levelDB branch
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 27/100
This commit changes how Electrum tracks where certain data objects live in the wallet database. It switches from short names like 'invoices/*' to full paths like '/invoices/*', and updates the internal registry to handle these full paths. The stated goal is to prevent naming collisions and to enable future performance improvements. There is no direct evidence in the commit that this fixes an active security vulnerability, but path-collision bugs in serialization code can sometimes lead to wrong data being read or written, which could have security implications.
AI review queuedsimplify prevby SomberNight · 6a89dd30 · Jun 3, 2026 · 1 fileMessage 18 · OpaqueInformational 11Details
Commit message · SomberNight
simplify prev
18/100 · OpaqueMessage clarity
✓ Subject identifies a change! Too few words to establish purpose! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: opaque commit messagesecond-pass: security-sensitive path
AI analysis · Informational 11/100
This is a small code cleanup in Electrum's transaction handling. It simplifies how raw transaction bytes are converted to hex strings. There is no obvious security bug being fixed here; it appears to be a follow-up simplification to a previous change.
AI review queuedtx_from_any: make sanitization optionalby ThomasV · 271f079d · Jun 3, 2026 · 3 filesMessage 58 · ThinInformational 17Details
Commit message · ThomasV
tx_from_any: make sanitization optional
re.sub is expensive (calls re.sub), it is not necessary to call it when instantiating transactions from the wallet file.
defensive validationsigning or wallet pathsecond-pass: near security thresholdsecond-pass: security-sensitive path
AI analysis · Informational 17/100
This change is a performance optimization, not a security fix. It makes whitespace removal from transaction data optional, skipping it when loading transactions from the wallet's own stored files. The default behavior for user-provided input still removes whitespace. There is no direct security issue in the patch itself, though any future code that calls tx_from_any with untrusted input must remember to leave sanitization enabled.
AI review queuedunit tests: do not mock save_dbby ThomasV · f2ece0f4 · May 21, 2026 · 2 filesMessage 78 · AdequateInformational 15Details
Commit message · ThomasV
unit tests: do not mock save_db
Create in-memory wallets instead.
The logic of calling save_db() at specific places is specific to the current JsonDB backend, and it does not generalize well.
78/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit only changes unit tests. It removes the practice of mocking (faking) the wallet save function and instead creates in-memory wallets that don't touch disk. There is no change to the actual Electrum wallet application or its security behavior.
AI review queuedtests: move create_test_channels to lnhelpers.pyby SomberNight · cf91aa86 · May 20, 2026 · 4 filesMessage 55 · ThinInformational 15Details
Commit message · SomberNight
tests: move create_test_channels to lnhelpers.py
55/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit is a simple code cleanup in the project's test suite. It moves a helper function used to create fake Lightning payment channels from one test file into a shared test-utility file, and updates other test files to import it from the new location. No production wallet code is changed, and there is no security fix or vulnerability introduced.
AI review queuedtest_lnwallet: unittest channel rebalancingby f321x · b183a529 · May 20, 2026 · 1 fileMessage 60 · AdequateInformational 15Details
Commit message · f321x
test_lnwallet: unittest channel rebalancing
Add some unittest coverage for the channel rebalance flow.
✓ Descriptive subject✓ Provides an explanatory body✓ Mentions testing or verification
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit only adds new automated tests for an existing Lightning channel rebalancing feature in Electrum. It does not change any production wallet or network code, so it cannot introduce a security vulnerability or directly fix one.
AI review queuedlnwatcher: introduce loop to trigger callbacksby f321x · 2460b030 · May 20, 2026 · 3 filesMessage 68 · AdequateInformational 24Details
Commit message · f321x
lnwatcher: introduce loop to trigger callbacks
Introduce a taskgroup and polling loop to LNWatcher to guarantee the callbacks get called at least once every LNWatcher.MAX_CALLBACK_TRIGGER_DELAY_SEC (10 min). This should prevent callbacks that operate on time instead of blockheight from becoming (very) stale if there are no blockchain events triggering the callbacks for a longer time. Not entirely set about the 10 min delay, might as well be 5/2/1 min?
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 24/100
This commit adds a background polling loop to Electrum's Lightning watcher so that time-sensitive callbacks still run even when no new blockchain events occur for a while. It is a defensive reliability fix, not an obvious security patch, but stale watcher callbacks could in theory delay detection of channel problems. The change itself does not introduce a known vulnerability.
AI review queuednew 'stored_at' syntaxby ThomasV · 5f6a491f · May 14, 2026 · 7 filesMessage 28 · OpaqueInformational 12Details
Commit message · ThomasV
new 'stored_at' syntax
backported from levelDB branch
28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: opaque commit messagesecond-pass: security-sensitive path
AI analysis · Informational 12/100
This commit is a pure internal refactoring of how Electrum marks which Python classes correspond to which parts of the wallet database. It replaces two old decorators (`stored_in` and `stored_as`) with a single new decorator (`stored_at`) and updates the registration tables that convert database keys and values. There is no user-facing change, no new feature, and no obvious security fix or vulnerability introduced in the diff itself.
AI review queuedbuild: support blacklisting dependencies for deterministic buildsby matejcik · 74615623 · May 11, 2026 · 4 filesMessage 85 · StrongInformational 14Details
Commit message · matejcik
build: support blacklisting dependencies for deterministic builds
The method works as follows: 1. for every blacklisted dependency, as listed in ghost.txt, create and install an empty ghost package which will satisfy the dependency resolver 2. before hash resolution step, remove those ghosts to make hashin happy
This required converting find_restricted_dependencies to use locally installed package metadata instead of looking it up online on pypi. But that seems to be a good idea anyway.
85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Why it was queued
second-pass: broader security terminology
AI analysis · Informational 14/100
This commit changes Electrum's internal build tooling. It introduces 'ghost packages'—empty placeholder packages used only during the build process to satisfy dependency resolvers—so that certain unwanted dependencies can be excluded from final deterministic builds. The change also makes a helper script read package metadata from the local build environment instead of downloading it from PyPI. There is no direct evidence in the commit that this fixes an active security vulnerability; it appears to be a build-hygiene improvement.
AI review queuedMove StoredDict class into new 'stored_dict' moduleby ThomasV · d0860ed7 · May 11, 2026 · 7 filesMessage 65 · AdequateInformational 15Details
Commit message · ThomasV
Move StoredDict class into new 'stored_dict' module
This commit is only moving code, no functional change
65/100 · AdequateMessage clarity
✓ Specific, 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 simply moves the StoredDict, StoredObject, StoredList, and related helper code from one file (json_db.py) into a brand-new file (stored_dict.py). It then updates other files to import from the new location. The commit message and the diff itself show no changes to how the code works—only where it lives. There is no security fix or vulnerability introduced here.
AI review queuedwallet: encrypt the keystore before adding it to dbby ThomasV · b15be1fa · May 7, 2026 · 2 filesMessage 73 · AdequateHigh 71Details
Commit message · ThomasV
wallet: encrypt the keystore before adding it to db
adding keystore to db may result in a disk write, and we should never write unencrypted keys to disk (except lightning_xprv)
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 · High 71/100
This commit fixes a bug where Electrum could write unencrypted private keys to disk while creating or restoring a wallet, even when the user asked for password protection. The change rearranges the wallet setup so that the keystore is encrypted before it is placed into the wallet database, and the database storage is encrypted before any writes happen. It also moves the address-import step to happen after the keystore is saved, reducing the chance of plaintext key material touching disk.
AI review queuedqewallet: replace some threads with coroutinesby f321x · 0505ef59 · May 6, 2026 · 1 fileMessage 60 · AdequateInformational 12Details
Commit message · f321x
qewallet: replace some threads with coroutines
Allows to simplify a bit and has less overhead.
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 12/100
This commit is a routine code cleanup in Electrum's mobile/QML user interface. It replaces two background threads with lightweight coroutines (async functions) for broadcasting Bitcoin transactions and paying Lightning invoices. There is no indication this change fixes or introduces a security vulnerability.
AI review queuedwallet: make_unsigned_transaction: nicer error msg for bad outputsby SomberNight · b9cb44db · May 5, 2026 · 1 fileMessage 65 · AdequateInformational 15Details
Commit message · SomberNight
wallet: make_unsigned_transaction: nicer error msg for bad outputs
traceback was hard to understand if outputs was a list of TxOutputs (as opposed to PartialTxOutput)
65/100 · AdequateMessage clarity
✓ Specific, 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 adds a clearer error message inside Electrum's wallet code when a developer passes the wrong kind of transaction output object to a function that builds unsigned transactions. It is a defensive programming/debugging improvement, not a security fix. There is no indication it addresses a vulnerability or changes user-facing behavior beyond producing a more informative error.
✓ Descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit only changes test code. It makes anchor channels the default setting for Electrum's Lightning test suite and removes the need to pass an explicit 'has_anchors' flag when creating mock wallets in tests. There is no change to the actual wallet or Lightning code that users run, so it does not affect real-world security.
AI review queuedtests: lnpeer: simplify anchorsby SomberNight · 02847771 · May 4, 2026 · 4 filesMessage 60 · AdequateInformational 15Details
Commit message · SomberNight
tests: lnpeer: simplify anchors
there were too many degrees of freedom - sometimes the fields were actually inconsistent
60/100 · AdequateMessage clarity
✓ Descriptive subject✓ Provides an explanatory body✓ Mentions testing or verification
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This is a test-only cleanup commit. It removes a redundant 'anchor_outputs' parameter from helper functions used in Lightning Network tests and instead derives the channel type from a wallet configuration flag. It also re-enables an internal assertion that was previously commented out. There is no change to production wallet behavior or user-facing security.
AI review queuedLNWallet: set OPT_ANCHOR_REQ for peer, rm config.ENABLE_ANCHOR_CHANNELSby SomberNight · 193ea6da · May 4, 2026 · 6 filesMessage 95 · StrongLow 34Details
Commit message · SomberNight
LNWallet: set OPT_ANCHOR_REQ for peer, rm config.ENABLE_ANCHOR_CHANNELS
- require the OPTION_ANCHORS peer feature - rm the config.ENABLE_ANCHOR_CHANNELS config var, which some users might have set (maybe even forgot they did) - instead add a new config.TEST_LN_OPEN_SRK_CHANNELS, explicitly for testing
---
As @f321x said, the intention is: > This will prevent opening new outgoing and incoming SRK channels. > It will also prevent connecting to peers that don't signal anchor support at all (INIT features), so existing channels to them would need to get force closed or the peer needs to be bullied into updating their node software. > Existing SRK channels with peers that signal anchor support (e.g. SRK channel opened to Electrum Trampoline) remain usable.
However the part re preventing new incoming SRK channels is not correct AFAICT. I am fixing that in a later commit in the branch. This is because, AFAIU BOLT-02, just because we negotiated OPTION_ANCHORS as a peer feature, setting channel_type to an SRK channel in open_channel is still technically valid.
95/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Mentions testing or verification
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 34/100
This commit changes Electrum's Lightning wallet so it now requires anchor-style channels by default and removes the old user-facing setting that let people opt out. It replaces the opt-out with a hidden testing-only flag for older channel types. The change is a deliberate protocol hardening step, not a fix for an active exploit, though the commit message notes a follow-up is needed to fully block incoming old-style channels.
commands: export_lightning_preimage: add comment about wallet password
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
second-pass: broader security terminology
AI analysis · Informational 15/100
This commit only adds a documentation comment to the export_lightning_preimage command explaining that exporting a Lightning payment preimage does not require the wallet password. It changes no code behavior, no access controls, and no security logic. There is no vulnerability in this patch.
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100
This commit is a simple code cleanup that renames leftover references from 'LnAddr' to 'BOLT11Addr' and 'lndecode' to 'decode_bolt11_invoice' in comments and docstrings. It makes no functional changes to the code and has no security relevance.
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100
This is a one-character typo fix in a user-interface file for Electrum's QML (mobile-style) GUI. The button that starts a Lightning swap was checking the wrong property name, which likely meant the button stayed disabled even when a Lightning receive balance existed. There is no security issue here—just a UI bug that may have prevented users from clicking a swap button.
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100
This commit removes unused Python imports from two files: a Qt channel details dialog and a watchtower server plugin. It is a routine code cleanup with no functional changes and no security relevance.
The LnAddr, lndecode and lnencode naming didn't imply that it is bolt 11 specific, making it confusing to work with, now that there are also bolt 12 "lnaddr". Renaming it to *bolt11* creates a clear separation to bolt 12 things and reduces mental load.
This commit is pure renaming (using the PyCharm IDE refactor function), except for the removal of the `object` inheritance of LnAddr/BOLT11Addr, this is Python 2 legacy.
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit is a large but purely cosmetic rename in the Electrum Bitcoin wallet. It renames the internal module `lnaddr.py` to `bolt11.py` and renames classes/functions from names like `LnAddr` and `lndecode` to `BOLT11Addr` and `decode_bolt11_invoice`. The goal is to avoid confusion with the newer BOLT 12 Lightning invoice format. The actual code logic is unchanged, apart from removing the obsolete `object` base class from one class. There is no security fix or vulnerability introduced here.
crash_reporter: detect more altcoin-forks, don't send reports
A new crash report [0] looks to be from a fork where the altcoin has the same genesis block [1] as Bitcoin. But ofc "branding" is important, so they updated the URLs to point to their fork -- so we could also test against that.
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
second-pass: broader security terminology
AI analysis · Informational 23/100
This commit tightens a check in Electrum's crash reporter so it refuses to send crash reports to Electrum's servers when the software is an altcoin fork. Previously, forks that kept Bitcoin's genesis block but changed the project's source-code URL could still spam Electrum with crash reports. The change adds a URL check to catch more forks. It is a defensive hardening patch, not a fix for a vulnerability in Electrum itself.
Send more types of exceptions happening during daemon.load_wallet in `ElectrumGui.start_new_window()` to the crash reporter to catch e.g. assertion failures instead of showing them to the user as a warning dialog.
68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
second-pass: broader security terminology
AI analysis · Informational 19/100
This is a small user-experience improvement in the Electrum Bitcoin wallet's Qt desktop interface. It changes how certain wallet-loading errors are handled: instead of showing some unexpected errors to the user as a warning dialog, they are now sent to Electrum's crash reporter. It does not change how funds are stored, signed, or transmitted, and there is no indication it fixes a security vulnerability.