CommitWatch RSS
EL
← All projectsElectrum

Electrum

Long-running lightweight Bitcoin wallet for desktop and mobile platforms.

BitcoinSoftware walletsNormal
Source repository ↗
Repository coverage

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

64security candidates205second-pass queue164AI analyses
55commits · 30 days
108commits · 60 days
454commits · 180 days
924commits · 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.

65/100 average clarity
191Strong · 80–100
409Adequate · 60–79
285Thin · 40–59
39Opaque · 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.
ThomasV72213156
SomberNight3492559063
f321x3712166070
Sander van Grieken981018057
user322062
Roman Zeyde511053
Sasha Zykov413076
Aaron Fiore411068
Ferdinando Ametrano111096
Oren200043
Ilya Artemov200050
Felipe Micaroni Lalli100050
Analysis record

Published AI watches

Last scanned 51 minutes ago

Informational 19 AI analysisMessage 96 · Strong
EL ElectrumElectrum BitcoinSoftware wallets

wallet: sign_message: strip whitespaces in GUIs, do not strip in CLI

This commit tidies up how Electrum handles extra spaces around Bitcoin addresses, messages, and signatures when signing or verifying messages. Previously, different parts of the program (desktop GUI, mobile-style GUI, command line) behaved…

Behavior normalization across GUI and CLI interfacesNo cryptographic primitive changedNo privilege boundary crossed
4c3064f5by SomberNight+27−185 files
No security note in commit
Open full analysis →Source commit ↗
Informational 22 AI analysisMessage 50 · Thin
EL ElectrumElectrum BitcoinSoftware wallets

wallet: decrypt_message: nicer error msg if pubkey is unrelated

This commit improves the error handling in Electrum's message decryption feature. Previously, if a user tried to decrypt a message using a public key that did not belong to their wallet, the code could proceed and likely fail with a confus…

Input validation added for public key before cryptographic operationUser-facing exception replaces potential internal failureDefensive check prevents use of unrelated key material
92e938f4by SomberNight+5−01 file
No security note in commit
Open full analysis →Source commit ↗
Low 29 AI analysisMessage 35 · Opaque
EL ElectrumElectrum BitcoinSoftware wallets

wallet: sign_message: force kwargs

This commit changes how Electrum's message-signing function is called so that callers must explicitly name each argument (address, message, password) rather than passing them by position. The main practical effect is to prevent accidental …

API hardening: keyword-only arguments prevent positional argument swapNo explicit security bug fix or vulnerability disclosure in commit message or diffNo changes to cryptographic logic, password handling, or message parsing
e1eb2a34by SomberNight+9−44 files
No security note in commit
Open full analysis →Source commit ↗
Low 39 AI analysisMessage 45 · Thin
EL ElectrumElectrum BitcoinSoftware wallets

wallet: sign_message: consolidate checks from UIs

This commit moves input-validation checks for signing, verifying, encrypting, and decrypting messages out of the user-interface code and into the shared wallet logic. It also adds type checks so that non-text inputs are rejected earlier. T…

Input validation moved from UI controllers into core wallet logicType checks added at the CLI command entry points for message-crypto operationsUserFacingException used consistently for address, wallet, script-type, and key-format errors
48893760by SomberNight+89−396 files
No security note in commit
Open full analysis →Source commit ↗
Low 27 AI analysisMessage 50 · Thin
EL ElectrumElectrum BitcoinSoftware wallets

wallet: decrypt_message: consolidate checks from UIs

This commit moves input-validation and wallet-type checks for message decryption out of the user-interface and command-line layers and into the core wallet code. It also removes a faster, separate decryption path for imported wallets so al…

Input validation consolidated into a single core methodWatching-only wallet check moved from UI to wallet layerMultisig wallet unsupported-operation check moved from UI to wallet layer
9a0cc0d6by SomberNight+25−173 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 50 · Thin
EL ElectrumElectrum BitcoinSoftware wallets

wallet: refactor: add encrypt_message method, consolidated from UIs

This commit is a simple code cleanup: it moves the message-encryption logic from two separate places (the command-line tool and the Qt graphical interface) into a single shared method on the wallet class. The actual encryption behavior is …

No change to cryptographic primitives or parametersNo change to trust boundaries or input sourcesPure refactor consolidating duplicate code
5e9c8df0by SomberNight+26−183 files
No security note in commit
Open full analysis →Source commit ↗
Informational 13 AI analysisMessage 50 · Thin
EL ElectrumElectrum BitcoinSoftware wallets

wallet: refactor: add verify_message method, consolidated from UIs

This commit is a routine code cleanup: it moves message-signature verification out of three user-interface files into a single shared helper method in the wallet module. There is no security-relevant behavior change visible in the diff. Th…

No security-relevant functional changeRefactoring only: code deduplicationException handling broadened safely (ValueError covers binascii.Error and unicode errors)
ff5bbb04by SomberNight+26−304 files
No security note in commit
Open full analysis →Source commit ↗
Informational 19 AI analysisMessage 96 · Strong
EL ElectrumElectrum BitcoinSoftware wallets

qml: strip whitespace from message before signing, as in qt gui

This commit fixes a minor consistency bug in Electrum's newer QML (mobile-style) user interface. When signing a message, the app now removes accidental spaces at the start or end of the message and address, just like the older desktop Qt i…

Behavioral inconsistency between GUI implementations could cause user confusion or failed verificationNo cryptographic weakness introduced; change is input normalizationNo memory-unsafe code, no privilege changes, no network changes
72507328by Ferdinando Ametrano+3−01 file
No security note in commit
Open full analysis →Source commit ↗
Moderate 52 AI analysisMessage 93 · Strong
EL ElectrumElectrum BitcoinSoftware wallets

lnwallet: don't blacklist htlc failures without channel update

This change fixes how Electrum's Lightning wallet reacts when a payment route fails but the failing node no longer provides a channel update message, as now allowed by the Lightning protocol spec. Previously, Electrum would permanently bla…

Denial-of-service via over-blacklisting: prior behavior could cause legitimate channels to be blacklisted, degrading payment success and potentially isolating the wallet from usable routes.Spec compliance fix: aligns Electrum with updated Lightning BOLT protocol behavior.No cryptographic bypass or funds theft signal: the change is about routing policy, not key leakage or transaction authorization.
a865e336by f321x+48−142 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 35 · Opaque
EL ElectrumElectrum BitcoinSoftware wallets

hww/qt: followup 898a4c270

This commit simply renames an internal variable from `dialog_label` to `_dialog_label` to mark it as private. It is a minor code cleanup with no visible behavior change and no security relevance.

f3af41deby f321x+4−41 file
No security note in commit
Open full analysis →Source commit ↗
Low 25 AI analysisMessage 68 · Adequate
EL ElectrumElectrum BitcoinSoftware wallets

trezor: drop session after closing it

This commit fixes a bug in Electrum's support for Trezor hardware wallets. After a Trezor session times out or is closed, Electrum now forgets the old session ID. Previously it kept the stale session ID, so the next attempt to sign a trans…

Fixes a stale-session reference that caused InvalidSessionError on re-authenticationEnsures PIN re-prompt after session timeout/closureFailure mode was denial-of-service (transaction signing crash), not unauthorized signing
071b1e24by f321x+8−51 file
No security note in commit
Open full analysis →Source commit ↗
Informational 12 AI analysisMessage 83 · Strong
EL ElectrumElectrum BitcoinSoftware wallets

test_lnwallet: add unittest for unchanged channel update from failed htlc

This commit only adds a new unit test to Electrum's Lightning wallet test suite. It checks that when a payment fails due to a temporary lack of liquidity (TEMPORARY_CHANNEL_FAILURE) and the accompanying channel policy update is identical t…

Lightning payment routing failure handling behavior is being testedTEMPORARY_CHANNEL_FAILURE no longer (or is confirmed not to) blacklist channels when the channel update is unchangedLiquidity hints are used as an alternative to blacklisting for retry amounts
1f5b9adbby f321x+61−21 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 83 · Strong
EL ElectrumElectrum BitcoinSoftware wallets

test_lnwallet: add unittest for single channel mpp split config

This commit adds a new automated test to the Electrum project. It does not change any production wallet or Lightning code. The test verifies that when Electrum splits a multi-part payment across a single channel, all payment parts actually…

14f7fa0bby f321x+22−01 file
No security note in commit
Open full analysis →Source commit ↗
Low 47 AI analysisMessage 80 · Strong
EL ElectrumElectrum BitcoinSoftware wallets

json_db: set_modified after incomplete data

This commit fixes a bug in Electrum's wallet storage recovery. If a wallet file was partially corrupted (a 'patch' was cut off mid-write), the app could recover the old data but then fail to mark the wallet as changed. As a result, later u…

Data-loss / integrity failure in wallet storage recovery pathMissing dirty flag after fallback data recoveryAppend-only storage file not rewritten after corruption cleanup
f75f1958by f321x+22−12 files
No security note in commit
Open full analysis →Source commit ↗
Low 44 AI analysisMessage 58 · Thin
EL ElectrumElectrum BitcoinSoftware wallets

wallet_db: register onion_keys converter

This commit fixes a bug in Electrum's Lightning wallet database handling. After a wallet restart, a specific type of encryption key used in Lightning payments was being loaded as a text string instead of raw bytes. This mismatch could caus…

Type confusion between str and bytes in cryptographic key handlingLightning payment error path affected after wallet restartMissing data converter in wallet database layer
5b2eb060by f321x+2−02 files
No security note in commit
Open full analysis →Source commit ↗
Informational 18 AI analysisMessage 58 · Thin
EL ElectrumElectrum BitcoinSoftware wallets

qml: update ConfirmTxDialog onValidChanged

This is a small user-interface fix for the Electrum mobile/QML app. When sweeping private keys, the confirmation dialog that shows how much money will be moved initially displayed an amount of 0 because it did not refresh after the transac…

bd776e24by f321x+3−01 file
No security note in commit
Open full analysis →Source commit ↗
Informational 18 AI analysisMessage 73 · Adequate
EL ElectrumElectrum BitcoinSoftware wallets

qml: emit a single dataChanged when updating blockchain height

This change is a performance cleanup in Electrum's mobile/QML user interface. When the wallet learns that the Bitcoin blockchain has grown taller, it now refreshes the transaction list with a single 'everything changed' signal instead of s…

No security-relevant logic changePerformance/efficiency optimization onlyNo input validation, parsing, cryptography, or network changes
fbe9e2d8by f321x+8−41 file
No security note in commit
Open full analysis →Source commit ↗
Informational 20 AI analysisMessage 85 · Strong
EL ElectrumElectrum BitcoinSoftware wallets

qml: don't compute notification balance delta for large tx batches

This commit is a performance fix, not a security patch. It stops the Electrum mobile/QML wallet from calculating the total balance change when more than 20 new transactions arrive at once, because that calculation could freeze the user int…

No security-relevant signal present in the diff or commit messagePerformance/DoS mitigation against accidental UI freezing from large transaction batches
7b4759c5by f321x+5−21 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 60 · Adequate
EL ElectrumElectrum BitcoinSoftware wallets

qml: change event callback logs to debug

This commit simply changes two logging messages from 'info' level to 'debug' level in the mobile/QML wallet interface. It reduces routine log output when many transactions occur. There is no security-relevant change.

a6cc4e08by f321x+2−21 file
No security note in commit
Open full analysis →Source commit ↗
Informational 18 AI analysisMessage 73 · Adequate
EL ElectrumElectrum BitcoinSoftware wallets

qml: don't force-build address model from tx event handlers

This is a performance and responsiveness fix for the Electrum mobile/QML wallet. It stops the app from doing heavy work (building the address coin list) every time a new transaction arrives, which was causing the user interface to freeze. …

35fc4a13by f321x+4−21 file
No security note in commit
Open full analysis →Source commit ↗
Repository ledger

Explore captured commits

Expand any commit for its author, full message, clarity score, changed files, triage signals, analysis, and source link.

Lower-priorityswaps: server_update_pairs: add named constant for MAX_SWAP_AMTby SomberNight · 8c47499b · May 5, 2026 · 1 fileMessage 50 · ThinTriage 0Details
Commit message · SomberNight

swaps: server_update_pairs: add named constant for MAX_SWAP_AMT

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-prioritytests: toyserver: calc_sh_history: impl sort order, unconf parent (-1)by SomberNight · b89898ee · May 5, 2026 · 2 filesMessage 60 · AdequateTriage 0Details
Commit message · SomberNight

tests: toyserver: calc_sh_history: impl sort order, unconf parent (-1)

60/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
Lower-prioritytests: toyserver: add tests, implement mempool replacementby SomberNight · 2ccca903 · May 5, 2026 · 2 filesMessage 60 · AdequateTriage 0Details
Commit message · SomberNight

tests: toyserver: add tests, implement mempool replacement

60/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
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.

Lower-prioritytests: toyserver: move to subdirectoryby SomberNight · 755672d0 · May 5, 2026 · 3 filesMessage 55 · ThinTriage 0Details
Commit message · SomberNight

tests: toyserver: move to subdirectory

55/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
Lower-prioritytests: toyserver: extend remove_tx to subgraph of transitive childrenby SomberNight · be9b4cbb · May 5, 2026 · 1 fileMessage 60 · AdequateTriage 0Details
Commit message · SomberNight

tests: toyserver: extend remove_tx to subgraph of transitive children

60/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
Lower-prioritytests: toyserver: add basic remove_tx/reorg functionalityby SomberNight · 62a03ff5 · May 5, 2026 · 3 filesMessage 60 · AdequateTriage 0Details
Commit message · SomberNight

tests: toyserver: add basic remove_tx/reorg functionality

60/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
Lower-prioritytests: toyserver: add faucetby SomberNight · 0811f3d7 · May 5, 2026 · 2 filesMessage 60 · AdequateTriage 0Details
Commit message · SomberNight

tests: toyserver: add faucet

on the road to have our very own shitcoin!

60/100 · AdequateMessage clarity
✓ Descriptive subject✓ Provides an explanatory body✓ Mentions testing or verification
Lower-prioritytests/toyserver: track UTXOs, and forbid conflictsby SomberNight · 86ca70d9 · May 5, 2026 · 2 filesMessage 60 · AdequateTriage 0Details
Commit message · SomberNight

tests/toyserver: track UTXOs, and forbid conflicts

60/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
Lower-prioritytests: toy_server: move start/stop logicby SomberNight · 2cb11800 · May 5, 2026 · 2 filesMessage 55 · ThinTriage 0Details
Commit message · SomberNight

tests: toy_server: move start/stop logic

55/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
Lower-prioritytests: split out toy_server from test_interface.pyby SomberNight · 4043d84f · May 5, 2026 · 2 filesMessage 60 · AdequateTriage 0Details
Commit message · SomberNight

tests: split out toy_server from test_interface.py

60/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
Lower-prioritytests: interface: split ToyServer from ToyServerSessionby SomberNight · d8159dfc · May 5, 2026 · 1 fileMessage 60 · AdequateTriage 0Details
Commit message · SomberNight

tests: interface: split ToyServer from ToyServerSession

60/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
Lower-priorityinterface: explain how to make aiorpcx log json trafficby SomberNight · c99879a7 · May 5, 2026 · 1 fileMessage 50 · ThinTriage 0Details
Commit message · SomberNight

interface: explain how to make aiorpcx log json traffic

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-prioritylnutil.ChannelType: rm "discard unknown" part from discard_unknown_and_checkby SomberNight · 621eac23 · May 4, 2026 · 4 filesMessage 81 · StrongTriage 0Details
Commit message · SomberNight

lnutil.ChannelType: rm "discard unknown" part from discard_unknown_and_check

This looks more dangerous than useful.
Added in [0], unclear what the original motivation was. Perhaps it was trying to discard the "variation flags" (46/50), which were already being discussed in a BOLTS PR [1] though not yet fully spec-ced out.

from https://github.com/lightning/bolts/blob/a3772650d8ebc06acf457fcadf97968ebfc4dfff/02-peer-protocol.md?plain=1#L811 :

> The sending node:
> - MUST set `channel_type`:
> - SHOULD NOT set it to a type containing a feature which was not negotiated.

[0]: https://github.com/spesmilo/electrum/commit/401a429080ec46960cb73e31f093f3970cc17683
[1]: https://github.com/lightning/bolts/pull/910

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-prioritylnpeer: refuse new incoming SRK channelsby SomberNight · 6bd6dc1f · May 4, 2026 · 3 filesMessage 45 · ThinTriage 0Details
Commit message · SomberNight

lnpeer: refuse new incoming SRK channels

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI review queuedtests: lnpeer: simplify anchors moreby SomberNight · e2ec6b3c · May 4, 2026 · 6 filesMessage 55 · ThinInformational 15Details
Commit message · SomberNight

tests: lnpeer: simplify anchors more

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

Lower-prioritylnonion: rm is_onion_message param from process_onion_packetby Sander van Grieken · 63e0258b · May 4, 2026 · 3 filesMessage 65 · AdequateTriage 0Details
Commit message · Sander van Grieken

lnonion: rm is_onion_message param from process_onion_packet

lnonion.process_onion_packet() can decide internally if the given
onion is a onion message through the tlv_stream_name.

65/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
Lower-prioritylnonion/onion_wire: encrypted_data -> encrypted_recipient_databy f321x · 323bf7b1 · May 4, 2026 · 4 filesMessage 71 · AdequateTriage 0Details
Commit message · f321x

lnonion/onion_wire: encrypted_data -> encrypted_recipient_data

Previously there were different names for the encrypted_recipient_data
field in blinded paths, depending on it being for a onion message
or a blinded payment. This has been unified in the bolts, now it is always
encrypted_recipient_data. This allows to simplify
lnonion.encrypt_hops_recipient_data.
https://github.com/lightning/bolts/commit/3c0fd9ad901eeef9ef6890c1bb85592cbf59e3d3

71/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Lower-prioritylnworker: add docstring to pay_invoiceby SomberNight · 7ccf349f · May 4, 2026 · 1 fileMessage 73 · AdequateTriage 0Details
Commit message · SomberNight

lnworker: add docstring to pay_invoice

LLM vuln report spam keeps thinking that getting a swapserver to *call* the pay_invoice method is a huge security issue.

73/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Names security-relevant behavior explicitly
Lower-prioritylnpeer: simplify channel_type, as it is now "assumed"by SomberNight · efa4d06e · Apr 30, 2026 · 1 fileMessage 50 · ThinTriage 0Details
Commit message · SomberNight

lnpeer: simplify channel_type, as it is now "assumed"

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-prioritylnpeer: add property for "config"by SomberNight · be2096f8 · Apr 30, 2026 · 1 fileMessage 68 · AdequateTriage 0Details
Commit message · SomberNight

lnpeer: add property for "config"

instead of "self.network.config" or "self.lnworker.config" (mixed),
use "self.config", which points to "self.lnworker.config"

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Lower-priorityLnFeatures: rename OPTION_ANCHORS_ZERO_FEE_HTLC to OPTION_ANCHORSby SomberNight · 4357ef2f · Apr 30, 2026 · 5 filesMessage 65 · AdequateTriage 0Details
Commit message · SomberNight

LnFeatures: rename OPTION_ANCHORS_ZERO_FEE_HTLC to OPTION_ANCHORS

- to follow the same change in the BOLTS
- both for LnFeatures and for ChannelType

65/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
Lower-priorityqml: history list: don't update fiat values during drag scollby f321x · 3d8fabac · Apr 30, 2026 · 1 fileMessage 73 · AdequateTriage 0Details
Commit message · f321x

qml: history list: don't update fiat values during drag scoll

Don't update the fiat values during scrolling through the history
with the thing on the right side (drag scrolling), this should
improve the performance of the list when doing a quick drag scroll.

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context