SS
← All projectsSeedSigner

SeedSigner

Stateless, air-gapped Bitcoin signing software for Raspberry Pi hardware.

BitcoinHardware walletsNormal
Repository coverage

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

168security candidates28second-pass queue223AI analyses
14commits · 30 days
40commits · 60 days
60commits · 180 days
204commits · 365 days
Backfill bands
Aug 5 → Feb 6150 seen8 candidatesComplete
Feb 6 → Jun 629 seen0 candidatesComplete
Jun 6 → Jul 60 seen0 candidatesComplete
Jul 6 → Aug 57 seen1 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.

49/100 average clarity
15Strong · 80–100
56Adequate · 60–79
92Thin · 40–59
66Opaque · 0–39
44security 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.
Nick Klockenga282324268
kdmukai141100141145
okaybro191619064
PROWLERx15101010020
alvroble12711055
FazleRabbbiferdaus172868061
biel414037
securesigner111050
Chaitanya-Keyal111057
Kshitij111033
Advait111060
S1DDHEY111045
Analysis record

Published AI watches

Last scanned 28 minutes ago

Informational 15 AI analysisMessage 73 · Adequate
SS SeedSignerSeedSigner BitcoinHardware wallets

Merge pull request #722 from Chaitanya-Keyal/psbt-huge-fee-warning

This commit adds a new user-facing safety feature: a warning screen when a Bitcoin transaction's fee is unusually high compared to the amount being sent. It does not fix a bug or vulnerability; it helps users notice potentially costly mist…

New user-facing warning for high transaction feesThreshold-based fee check computed from PSBT outputsVisual warning mark and color change on fee display
088b144eby Nick Klockenga+238−55 files
No security note in commit
Informational 20 AI analysisMessage 68 · Adequate
SS SeedSignerSeedSigner BitcoinHardware wallets

Settle is_high_fee once in parse()

This commit is a performance cleanup, not a security fix. It calculates the 'is this fee unusually high?' flag once during transaction parsing instead of recalculating it every time a screen asks. The actual fee-checking logic and warning …

No security-relevant logic change: the same fee threshold and calculation are usedPerformance optimization only: eliminates repeated transaction re-summationNo input validation, cryptography, or authorization changes
2195adfdby okaybro+32−53 files
No security note in commit
High 80 AI analysisMessage 88 · Strong
SS SeedSignerSeedSigner BitcoinHardware wallets

Merge pull request #1032 from kdmukai/psbt_output_ownership

This commit fixes a security flaw in SeedSigner, a small hardware-wallet-like device used to sign Bitcoin transactions. Previously, the software trusted the PSBT file's own claim about which 'change' outputs belong back to the user's walle…

Fixes change-output ownership verification against PSBT coordinator claimsAdds independent scriptPubKey reconstruction from seed-derived keysAdds rejection of contradictory ownership claims (claim-ours/pay-other and pay-ours/claim-other)
b225ae77by Nick Klockenga+1756−2636 files
Vendor flagged security relevance
Moderate 63 AI analysisMessage 83 · Strong
SS SeedSignerSeedSigner BitcoinHardware wallets

Count an unresolved output cosigner set as a mismatch

This commit fixes a bug in SeedSigner's PSBT parser that could misclassify a payment to a different multisig wallet as 'change' (money going back to the user's own wallet). The bug occurred when the output's cosigner list could not be reso…

Change-vs-spend misclassification in multisig PSBT parsingCosigner resolution failure previously skipped instead of treated as mismatchFingerprint matching removed in favor of derivation-path + derived-key verification
45a5eabbby kdmukai+102−462 files
Vendor flagged security relevance
Low 34 AI analysisMessage 100 · Strong
SS SeedSignerSeedSigner BitcoinHardware wallets

Compare cosigners before presuming multisig change

This commit tightens how SeedSigner decides whether a multisig payment back to the user is real 'change' or actually a payment to a different wallet. Before, if an output contained the user's key and looked like the same kind of multisig (…

Multisig change-output presumption logic changed to compare input vs output cosigner listsOptional/unauthenticated PSBT global xpubs used only as a hygiene check, not a hard security controlMismatch demotes output from change to spend rather than raising an error
ff133966by kdmukai+244−62 files
Vendor flagged security relevance
Informational 15 AI analysisMessage 58 · Thin
SS SeedSignerSeedSigner BitcoinHardware wallets

Rename is_change to is_presumed_change

This commit only renames a variable from 'is_change' to 'is_presumed_change' and updates comments/docstrings to make it clearer that multisig outputs are only suspected—not proven—to belong to the user's wallet. The code logic is unchanged…

No functional code changeVariable rename and documentation clarification onlyCommit message explicitly states 'No behavior change'
321bf14dby kdmukai+19−131 file
No security note in commit
Moderate 60 AI analysisMessage 83 · Strong
SS SeedSignerSeedSigner BitcoinHardware wallets

Match policy types exactly and refuse an unsupported one

This commit fixes a bug in how SeedSigner parses Bitcoin transaction outputs. Previously, the code guessed script types using partial string matches (like checking if 'pkh' appears anywhere in the type name) and had no fallback for unknown…

CWE-20: Improper Input Validation - substring matching allowed ambiguous/unsupported script type handlingCWE-248: Uncaught Exception - unsupported script types caused bare TypeError instead of controlled failureCWE-754: Improper Check for Unusual or Exceptional Conditions - missing else branch for unsupported policy types
a929b8b3by kdmukai+38−112 files
No security note in commit
Moderate 59 AI analysisMessage 85 · Strong
SS SeedSignerSeedSigner BitcoinHardware wallets

Set is_change only after each branch's own checks

This commit fixes a logic bug in how SeedSigner decides whether a Bitcoin transaction output is 'change' coming back to the user's wallet. Previously, the code marked an output as change as soon as it looked like it paid to the user's seed…

Logic bug: default-true flag inside a conditional arm with branches responsible for undoing itPotential UI deception: unverified output could be displayed as user changeDefensive refactor: flag set only after branch-specific verification
12c72391by kdmukai+23−71 file
Vendor flagged security relevance
High 79 AI analysisMessage 78 · Adequate
SS SeedSignerSeedSigner BitcoinHardware wallets

Verify that change outputs actually pay this seed

This commit fixes a security flaw in how SeedSigner decides whether a Bitcoin transaction's 'change' output really returns coins to the user's own wallet. Previously, the device trusted too much of what the transaction coordinator (or a ma…

Fixes insufficient verification of change output ownership in PSBT parsingAdds explicit rejection of ownership-claim/scriptPubKey contradictions treated as attacksAdds rejection of surplus derivation path entries and mixed ecdsa/taproot derivation maps
bb2471a6by kdmukai+1390−2406 files
Vendor flagged security relevance
Informational 15 AI analysisMessage 68 · Adequate
SS SeedSignerSeedSigner BitcoinHardware wallets

Clarify psbt_parser.py docstrings and comments

This commit only rewrites comments and docstrings in one file and renames a single function parameter for clarity. The commit message explicitly says 'No behavior change,' and the diff contains no changes to executable logic, control flow,…

0d374bc7by kdmukai+28−371 file
No security note in commit
High 78 AI analysisMessage 78 · Adequate
SS SeedSignerSeedSigner BitcoinHardware wallets

Merge pull request #1013 from kdmukai/psbt_parser_ownership_scan

This commit hardens SeedSigner's PSBT (Bitcoin transaction) parser so it no longer trusts a transaction's claim that an output belongs to the user's wallet. Previously, a malicious or buggy transaction could mark a payment to an attacker's…

Fixes fake-change / ownership-spoofing vulnerability in PSBT parsingAdds explicit rejection of false seed-ownership claims on outputs and inputsAdds user-facing warning screens for forged ownership claims
e4af6a7eby Nick Klockenga+994−516 files
Vendor flagged security relevance
Informational 15 AI analysisMessage 73 · Adequate
SS SeedSignerSeedSigner BitcoinHardware wallets

Merge pull request #1005 from kdmukai/psbt_parser_trust_vocabulary

This commit is a code cleanup that renames internal data fields from 'fingerprint' and 'derivation_path' to 'claimed_fingerprints' and 'claimed_derivation_paths'. It does not change how the software verifies Bitcoin transaction data or how…

No functional security change; only identifier renaming and documentationExpanded docstring explicitly distinguishes claimed_ vs verified_ dataNo new validation, no removed validation, no algorithm change
d70b322fby Nick Klockenga+62−383 files
No security note in commit
Informational 15 AI analysisMessage 28 · Opaque
SS SeedSignerSeedSigner BitcoinHardware wallets

Improve comment accuracy

This commit only rewrites comments and docstrings in a single Python file to make them more accurate. No code logic, behavior, or security properties were changed.

c7eacfbdby kdmukai+18−141 file
No security note in commit
Informational 15 AI analysisMessage 68 · Adequate
SS SeedSignerSeedSigner BitcoinHardware wallets

Pluralize change_data's claimed keys

This commit simply renames two internal data keys from singular to plural (e.g., 'claimed_fingerprint' becomes 'claimed_fingerprints') because they actually hold lists of values. It also removes a commented-out debug print line. There is n…

4f00d32fby kdmukai+14−153 files
No security note in commit
Informational 15 AI analysisMessage 28 · Opaque
SS SeedSignerSeedSigner BitcoinHardware wallets

Improve comment accuracy

This commit only changes a comment in the source code to make it more accurate. It does not modify any actual code behavior, so it has no security impact on its own.

622a9fedby kdmukai+2−11 file
No security note in commit
Informational 19 AI analysisMessage 73 · Adequate
SS SeedSignerSeedSigner BitcoinHardware wallets

Merge pull request #1002 from kdmukai/psbt_parser_derivation_cache

This commit is a performance improvement for parsing Bitcoin transaction files (PSBTs). It adds a cache so the wallet doesn't repeatedly recalculate the same cryptographic key derivations, and it avoids rebuilding the whole transaction obj…

Removed p2sh redeem-script handling path in change detectionNew derivation cache keyed by id(parent_key) with explicit rejection of fingerprint-based keying due to collision riskFingerprint recovery now uses root.my_fingerprint instead of root.child(0).fingerprint
861d6e3cby Nick Klockenga+419−352 files
No security note in commit
Informational 15 AI analysisMessage 68 · Adequate
SS SeedSignerSeedSigner BitcoinHardware wallets

Mark coordinator-supplied change data as claimed

This commit is a code cleanup and documentation change, not a security fix. It renames variables and dictionary keys from 'fingerprint' and 'derivation_path' to 'claimed_fingerprint' and 'claimed_derivation_path' to make it clearer that da…

Renames unverified coordinator-supplied metadata keys to 'claimed_' prefixAdds trust-boundary documentation and naming convention in class docstringExplicitly states no logic changes in commit message
fc21710bby kdmukai+47−273 files
No security note in commit
Informational 15 AI analysisMessage 78 · Adequate
SS SeedSignerSeedSigner BitcoinHardware wallets

Tighten the derivation cache guard tests

This commit only changes test code. It tightens an existing unit test so it actually exercises the cache read path, and improves comments and docstrings. No production code was modified, so it cannot introduce or fix a security vulnerabili…

65b1d3d9by kdmukai+22−131 file
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.

Security candidateRemove sleeps that cause delays exiting threadby kdmukai · 68de9fff · Dec 15, 2025 · 1 fileMessage 45 · ThinInformational 12Details
Commit message · kdmukai

Remove sleeps that cause delays exiting thread

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
seed or entropy pathsigning or wallet path
AI analysis · Informational 12/100

This commit refactors how a scrolling text display pauses at the start and end of a line. Previously the code simply slept (paused) the entire thread, which made it slow to respond when the user wanted to stop scrolling. The new code tracks pause timing with variables and checks them in the main loop, so the thread can exit promptly when asked. There is no security issue visible in this change.

Security candidatestyle: fix typos in source code comments and stringsby securesigner · d5729358 · Dec 14, 2025 · 4 filesMessage 50 · ThinInformational 15Details
Commit message · securesigner

style: fix typos in source code comments and strings

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

This commit only fixes spelling mistakes in comments and log messages. No actual program code, behavior, or security controls were changed.

Security candidateInitial Hindi supportby kdmukai · 1769938c · Dec 14, 2025 · 3 filesMessage 28 · OpaqueInformational 15Details
Commit message · kdmukai

Initial Hindi support

28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
seed or entropy pathsigning or wallet path
AI analysis · Informational 15/100

This commit adds Hindi language support to the SeedSigner wallet interface. It registers a new Hindi font, adjusts font sizes for Hindi text, and adds Hindi to the language settings list. There is no security-relevant change.

Security candidateRemove `TextArea.allow_text_overflow`by kdmukai · 1f188754 · Dec 13, 2025 · 7 filesMessage 35 · OpaqueInformational 17Details
Commit message · kdmukai

Remove `TextArea.allow_text_overflow`

35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
memory safetyseed or entropy pathsigning or wallet path
AI analysis · Informational 17/100

This commit removes a UI flag called allow_text_overflow from SeedSigner's on-screen text rendering code. Previously, the flag decided whether text that was too long should be silently allowed to spill past its box (overflow) or trigger an error. After the change, the code always allows overflow and just logs a warning. This is a code-cleanup and UI-layout change; it does not introduce a way for an attacker to steal funds or keys, but it could make some translated screens look clipped or unreadable.

Security candidateRemove now-unused `has_passphrase` attrby kdmukai · 639c2a14 · Dec 10, 2025 · 2 filesMessage 45 · ThinInformational 15Details
Commit message · kdmukai

Remove now-unused `has_passphrase` attr

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
access controlseed or entropy pathsigning or wallet path
AI analysis · Informational 15/100

This commit simply removes an unused attribute called has_passphrase from two screen classes and the two places that passed it in. There is no functional change, no bug fix, and no security relevance visible in the code change.

Security candidateRemove dead codeby kdmukai · 0736e066 · Dec 10, 2025 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · kdmukai

Remove dead code

28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
seed or entropy pathsigning or wallet path
AI analysis · Informational 15/100

This commit simply deletes an unused helper function that could generate a seed phrase from an image. There is no security fix or vulnerability here—it's routine cleanup of leftover code.

Security candidateRemove dead codeby kdmukai · dd6277b8 · Dec 10, 2025 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · kdmukai

Remove dead code

28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
seed or entropy pathsigning or wallet path
AI analysis · Informational 15/100

This commit removes unused code from a single screen file. One line that set a scroll position variable was never referenced anywhere, and an entire 'Powering Off' screen class was defined but apparently not used. There is no security-relevant change here—just cleanup.

Security candidateRemove dead code and debugging codeby kdmukai · 6fb11166 · Dec 10, 2025 · 1 fileMessage 45 · ThinInformational 15Details
Commit message · kdmukai

Remove dead code and debugging code

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
seed or entropy pathsigning or wallet path
AI analysis · Informational 15/100

This commit removes unused variables and debugging-only code from the QR code scanning screen. There is no security-relevant change; it is purely cleanup of leftover development helpers and a counter that was no longer used.

Security candidateRemove dead codeby kdmukai · aa4b84c9 · Dec 10, 2025 · 4 filesMessage 28 · OpaqueInformational 12Details
Commit message · kdmukai

Remove dead code

28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
seed or entropy pathsigning or wallet path
AI analysis · Informational 12/100

This commit removes unused code and fixes a minor variable-name inconsistency in the user interface code. There is no apparent security relevance: it deletes an unused screen class, removes an unused loading-screen flag, drops an unused selection-button setting, and renames a throwaway variable in a font-size calculation so the code is internally consistent. None of these changes affect how private keys, seeds, or transactions are handled.

Security candidateRemove dead codeby kdmukai · 2868b235 · Dec 10, 2025 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · kdmukai

Remove dead code

28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
seed or entropy pathsigning or wallet path
AI analysis · Informational 15/100

This commit removes unused variables and commented-out code from a single on-screen keyboard file. It is a routine cleanup with no visible security effect.

Security candidateRemove dead code, unused constantsby kdmukai · 74b57927 · Dec 10, 2025 · 1 fileMessage 45 · ThinInformational 15Details
Commit message · kdmukai

Remove dead code, unused constants

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
seed or entropy pathsigning or wallet path
AI analysis · Informational 15/100

This commit is a routine cleanup: it removes unused color constants, unused icon symbols, an unused helper function for centering text, and an unused empty list. There is no change to how the app behaves or to any security-sensitive logic.

Security candidateRemove dead codeby kdmukai · 060130f9 · Dec 10, 2025 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · kdmukai

Remove dead code

28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
seed or entropy pathsigning or wallet path
AI analysis · Informational 15/100

This commit simply deletes an unused helper method that could create a class instance without hardware initialization. There is no functional change to the running program because the method was not being called anywhere. It is a routine code cleanup, not a security fix.

Security candidateImprove commenting and solve minor nitsby alvroble · c565b825 · Dec 9, 2025 · 1 fileMessage 45 · ThinInformational 15Details
Commit message · alvroble

Improve commenting and solve minor nits

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
seed or entropy pathsigning or wallet pathparser or protocol path
AI analysis · Informational 15/100

This commit only rewrites comments and removes an unused variable in a single file. It does not change any program logic, security behavior, or functionality. There is no security issue here.

AI review queuedFix multisig testsby alvroble · 386ecdc3 · Dec 9, 2025 · 1 fileMessage 38 · OpaqueInformational 12Details
Commit message · alvroble

Fix multisig tests

38/100 · OpaqueMessage clarity
✓ Subject identifies a change✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
signing or wallet pathparser or protocol pathsecond-pass: opaque commit messagesecond-pass: security-sensitive path
AI analysis · Informational 12/100

This commit only changes test code. It updates a unit test so that it checks both single-signature and multi-signature PSBT inputs, and it makes the fingerprint assertions more precise by distinguishing public keys that belong to the current seed from those that don't. There is no change to the actual application code that handles seeds or transactions.

AI review queuedImprovement of tests, single-sig isolation * Better naming and code efficiency * Removed multisig from test inputs until figured outby alvroble · 0e4da284 · Dec 8, 2025 · 1 fileMessage 83 · StrongInformational 12Details
Commit message · alvroble

Improvement of tests, single-sig isolation
* Better naming and code efficiency
* Removed multisig from test inputs until figured out

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
signing or wallet pathparser or protocol pathsecond-pass: security-sensitive path
AI analysis · Informational 12/100

This commit only changes a test file. It renames a test, tightens some assertions, and temporarily removes multisig test cases from a loop so only single-signature inputs are exercised. There is no change to the actual PSBT parsing or wallet code, so it does not fix or introduce a security issue by itself.

Security candidateImprove naming, comments and code consistency * Added explanatory comments and reference to the original issue * Better variable naming and type hinting to increase clarity * Modified nested functions handling, naming and (intended) visibilityby alvroble · 725ae563 · Dec 8, 2025 · 1 fileMessage 73 · AdequateInformational 15Details
Commit message · alvroble

Improve naming, comments and code consistency
* Added explanatory comments and reference to the original issue
* Better variable naming and type hinting to increase clarity
* Modified nested functions handling, naming and (intended) visibility

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
seed or entropy pathsigning or wallet pathparser or protocol path
AI analysis · Informational 15/100

This commit is a code cleanup and documentation improvement for a previously existing fingerprint-repair feature in SeedSigner. It renames functions, adds explanatory comments, adds type hints, and refactors nested helper functions. The actual behavior—filling in missing (zero) PSBT fingerprints by deriving keys from the loaded seed—remains essentially unchanged. There is no new security fix or vulnerability introduced in this diff.

Security candidateMinor fixes to title case and consistencyby kdmukai · a2ba8603 · Nov 23, 2025 · 2 filesMessage 45 · ThinInformational 15Details
Commit message · kdmukai

Minor fixes to title case and consistency

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
seed or entropy pathsigning or wallet path
AI analysis · Informational 15/100

This commit changes three on-screen labels from one style of capitalization to another (for example, 'Load A Seed' becomes 'Load a Seed' and 'Electrum warning' becomes 'Electrum Warning'). These are purely cosmetic wording tweaks with no effect on security or functionality.

Security candidateButton text change, added TODO commentby kdmukai · 8eee5d1c · Nov 23, 2025 · 2 filesMessage 25 · OpaqueInformational 15Details
Commit message · kdmukai

Button text change, added TODO comment

25/100 · OpaqueMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body! Contains work-in-progress language! Opaque security-relevant change
Why it was queued
seed or entropy pathsigning or wallet path
AI analysis · Informational 15/100

This commit only changes a single button label from 'Select diff seed' to 'Select different seed' and adds a non-code TODO comment about future localization work. There is no security relevance.

Lower-priorityadd missing screenshots for single sig change verificationby kdmukai · ac43a8bd · Nov 22, 2025 · 1 fileMessage 60 · AdequateInformational 15Details
Commit message · kdmukai

add missing screenshots for single sig change verification

60/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
defensive validation
AI analysis · Informational 15/100

This commit only updates the test screenshot generator. It adds a new sample single-signature Bitcoin transaction and renames an existing multi-signature sample so the generator can produce screenshots for both single-sig and multi-sig change verification. There is no change to the actual wallet or security code that users rely on.

Security candidateCapitalization fix for button optionby kdmukai · 95988c93 · Nov 22, 2025 · 1 fileMessage 45 · ThinInformational 15Details
Commit message · kdmukai

Capitalization fix for button option

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
seed or entropy pathsigning or wallet path
AI analysis · Informational 15/100

This commit changes only the capitalization of a button label from 'Verify Multisig Addr' to 'Verify multisig addr'. It is a cosmetic user-interface text fix with no security relevance.

Security candidateLight reorg and simplification of `PSBTChangeDetailsScreen`by kdmukai · 71b91cfc · Nov 22, 2025 · 1 fileMessage 50 · ThinInformational 15Details
Commit message · kdmukai

Light reorg and simplification of `PSBTChangeDetailsScreen`

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

This commit is a minor UI cleanup for a screen that shows details about a Bitcoin change address. It reorders on-screen elements, changes some label text (for example from 'Change' to 'change address'), and adjusts how a success message is centered. There is no security-relevant change.

Security candidateRemove unreachable codeby kdmukai · fbfa3ce6 · Nov 22, 2025 · 1 fileMessage 28 · OpaqueInformational 12Details
Commit message · kdmukai

Remove unreachable code

28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
seed or entropy pathsigning or wallet path
AI analysis · Informational 12/100

This commit removes a leftover 'Verify address' menu option and its related code from a seed management screen. The code was never reachable because nothing in the program ever set the 'unverified_address' value it depended on. It is a cleanup change, not a security fix.

Security candidateException str does not need to be translatedby kdmukai · 1cf22a4a · Nov 22, 2025 · 1 fileMessage 45 · ThinInformational 15Details
Commit message · kdmukai

Exception str does not need to be translated

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
seed or entropy pathsigning or wallet path
AI analysis · Informational 15/100

This commit removes translation markup from an internal error message. It is a code-quality cleanup with no security relevance. The exception is raised when the program reaches an impossible state, and the message is not shown to users in normal operation.

Lower-priorityUpdating `messages.pot` to `dev` at `3455aa4`by kdmukai · b45a67ef · Nov 21, 2025 · 1 fileMessage 45 · ThinInformational 15Details
Commit message · kdmukai

Updating `messages.pot` to `dev` at `3455aa4`

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI analysis · Informational 15/100

This commit only updates a timestamp in a translation template file (messages.pot). It changes one line: the creation date/time from 14:34 to 14:39. There is no code change, no security fix, and no user-facing behavior change.

Lower-priorityUpdating `messages.pot` to `dev` at `3455aa4`by kdmukai · 7d348046 · Nov 21, 2025 · 1 fileMessage 45 · ThinInformational 15Details
Commit message · kdmukai

Updating `messages.pot` to `dev` at `3455aa4`

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI analysis · Informational 15/100

This commit is a routine update to the translation template file (messages.pot). It only changes user-visible text strings: rewording labels like 'Review PSBT' to 'Review Transaction', fixing capitalization, and updating version/date metadata. There are no code changes and no security implications.