KX
← All projectsKrux

Krux

Open-source signing firmware for Kendryte K210 devices.

BitcoinHardware walletsNormal
Repository coverage

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

61security candidates45second-pass queue223AI analyses
2commits · 30 days
4commits · 60 days
101commits · 180 days
169commits · 365 days
Backfill bands
Aug 5 → Feb 6116 seen6 candidatesComplete
Feb 6 → Jun 639 seen3 candidatesComplete
Jun 6 → Jul 622 seen1 candidatesComplete
Jul 6 → Aug 538 seen5 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
64Strong · 80–100
76Adequate · 60–79
96Thin · 40–59
16Opaque · 0–39
6security 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.
Odudex291429272
odudex923090159
Tads361036063
qlrd20216083
Jean Do1928067
kdmukai424066
tadeubas414038
Naman0151707059
kkdao12012083
bitcoisas505066
joaozinhom402067
Naman Gupta202079
Analysis record

Published AI watches

Last scanned 35 minutes ago

Informational 15 AI analysisMessage 62 · Adequate
KX KruxKrux BitcoinHardware wallets

chore: updates MaixPy glyphs (adds: 49, removes: 4)

This commit only updates a Git submodule pointer for the MaixPy firmware dependency. The actual code changes are stored in the linked submodule repository, not in this commit. There is no visible security-relevant change here.

f963e035by Jean Do+1−11 file
No security note in commit
Informational 4 AI analysisMessage 57 · Thin
KX KruxKrux BitcoinHardware wallets

fix: use latest MaixPy w/ pr_57

This commit only updates a submodule pointer for MaixPy, a firmware dependency. The actual code changes are not visible in this diff because they live in the separate MaixPy repository. Without seeing what changed in MaixPy, we cannot dete…

31754785by Jean Do+1−11 file
No security note in commit
Informational 15 AI analysisMessage 72 · Adequate
KX KruxKrux BitcoinHardware wallets

test: cover Back and failure paths for SD card and QR loading

This commit only adds and updates automated tests. It does not change any production code, so it cannot introduce a security vulnerability or directly fix one in the shipped firmware. The tests verify that pressing 'Back' or cancelling a c…

7a2fcd9eby notTanveer+297−89 files
No security note in commit
Informational 21 AI analysisMessage 62 · Adequate
KX KruxKrux BitcoinHardware wallets

fix: do not report "Failed to load" when the user backs out

This commit is a user-experience fix: it stops the Krux bitcoin hardware-wallet firmware from showing a scary 'Failed to load' error when the user simply presses Back or leaves the camera/SD-card picker. The change also moves SD-card error…

No memory-safety, cryptographic, or authorization changesError-message UX change onlyNo new attack surface introduced
1e9ea474by notTanveer+54−509 files
No security note in commit
Informational 15 AI analysisMessage 57 · Thin
KX KruxKrux BitcoinHardware wallets

fix(i18n): add scan and manual labels

This commit simply adds two missing translated labels, 'manual' and 'scan', to the project's user-interface language files. It is a routine internationalization (i18n) fix with no security relevance.

00e82270by Naman015+46−023 files
No security note in commit
Low 26 AI analysisMessage 100 · Strong
KX KruxKrux BitcoinHardware wallets

docs: TC-code - warn about privacy when filling flash with entropy from camera

This commit does not fix a software bug. It adds documentation warnings and an on-screen reminder telling users to read the docs before using the TC Code tamper-detection feature. The underlying behavior being warned about is that Krux can…

Privacy warning added for unscrambled camera frames stored in flashOn-device prompt added to read documentation before TC Code setupNo cryptographic or storage-behavior change in the diff
1cb1cc0cby odudex+33−225 files
Vendor flagged security relevance
Informational 15 AI analysisMessage 57 · Thin
KX KruxKrux BitcoinHardware wallets

docs: update mnemonic loading flow

This commit only updates user documentation and simulator test scripts to match a reorganized menu for loading a wallet recovery phrase. No actual wallet or security code was changed, so it does not create or fix a security vulnerability.

e264e2f5by Naman015+139−9522 files
No security note in commit
Moderate 66 AI analysisMessage 45 · Thin
KX KruxKrux BitcoinHardware wallets

Merge branch 'release-26.08.0'

This is a routine release merge for Krux firmware (version 26.08.0). It includes several genuine security fixes: a heap buffer overflow in camera-based entropy generation for a discontinued device, stricter fee calculation when signing Bit…

Heap buffer overflow fix in camera entropy module (discontinued Maix Bit only)PSBT fee calculation stricter checks and unverified-input-amount warningStored mnemonic file corruption now preserved instead of overwritten
be5eda28by odudex+4335−3028123 files
Vendor flagged security relevance
Informational 15 AI analysisMessage 40 · Thin
KX KruxKrux BitcoinHardware wallets

docs: update CHANGELOG

This commit only updates three date lines in the CHANGELOG.md file, changing '2025' to '2026' for three release entries. It does not modify any source code, build scripts, or documentation with security implications. The change is purely c…

ec058d86by odudex+3−31 file
No security note in commit
Moderate 66 AI analysisMessage 85 · Strong
KX KruxKrux BitcoinHardware wallets

fix: bind BBQr parts to the first part of the stream

This commit fixes Krux's QR code scanner so that when it reads a series of animated BBQr codes, every later frame must match the encoding and file type announced by the first frame, must agree on the total number of frames, and cannot over…

Input validation added for multi-part BBQr streamsMemory exhaustion mitigation via accumulated payload capAnti-splicing: parts must agree with first part's encoding and file type
0b3e01b7by odudex+86−13 files
No security note in commit
Informational 15 AI analysisMessage 40 · Thin
KX KruxKrux BitcoinHardware wallets

docs: update CHANGELOG

This commit only updates the project's CHANGELOG.md file. It adds text describing several bug fixes and improvements that were apparently made in prior code changes, but no actual code is changed in this commit. By itself, this documentati…

4c05cefbby odudex+9−11 file
No security note in commit
Informational 0 AI analysisMessage 40 · Thin
KX KruxKrux BitcoinHardware wallets

chore(Maixpy): bump cUR

This commit appears to be a routine version bump of a component called 'cUR' inside the MaixPy firmware build. No actual code changes are visible in the provided diff, and the commit message gives no indication of a security fix or vulnera…

74d6ed40by odudex+1−11 file
No security note in commit
Informational 15 AI analysisMessage 57 · Thin
KX KruxKrux BitcoinHardware wallets

chore: bump version to 26.08.0

This commit is a routine version bump from 26.04.0 to 26.08.0. It only updates version strings in documentation, build files, and source metadata. No code behavior changes. The changelog text mentions a previously fixed heap buffer overflo…

Changelog references a prior heap buffer overflow in Shannon entropy module (camera frame copy into fixed 320x240 RGB565 buffer)No actual code or security fix present in this commit
dea991dfby odudex+5−55 files
Vendor flagged security relevance
Informational 2 AI analysisMessage 57 · Thin
KX KruxKrux BitcoinHardware wallets

chore: bump MaixPy with updated glyphs

This commit appears to update a submodule or dependency called MaixPy to a newer version that includes updated visual glyphs (small icons/symbols). The title and message describe it as a routine maintenance chore, not a security fix. No ac…

a9329228by odudex+1−11 file
No security note in commit
Informational 15 AI analysisMessage 85 · Strong
KX KruxKrux BitcoinHardware wallets

fix: register embed_fire in the bdftokff device list

This commit fixes a build-time font-generation script so that a newly supported device ('embed_fire') is recognized. Before the fix, the script printed an error but still produced the same font files. There is no security issue.

f15308e4by odudex+1−01 file
No security note in commit
Moderate 63 AI analysisMessage 57 · Thin
KX KruxKrux BitcoinHardware wallets

docs: add PSBT input amount fixes to CHANGELOG

This commit only updates the project's CHANGELOG.md to document earlier fixes related to PSBT (Partially Signed Bitcoin Transaction) fee and amount handling. It does not contain any code changes itself. The changelog entries describe secur…

Changelog documents prior PSBT fee/amount validation fixesMentions insufficient coordinator data as a security concernNo actual code or test changes in this commit
48920c31by odudex+4−01 file
Vendor flagged security relevance
High 78 AI analysisMessage 95 · Strong
KX KruxKrux BitcoinHardware wallets

fix: verify PSBT input amounts before showing the fee

This commit fixes a security flaw in Krux, a Bitcoin signing device. Before the fix, an attacker could trick the device into showing a low transaction fee on screen while actually signing a much higher fee. The fix makes the device verify …

Fixes fee-display/sighash amount mismatchAdds prevout txid hash verification for non_witness_utxoMandates non_witness_utxo for legacy inputs
fc808059by odudex+353−122 files
Vendor flagged security relevance
Moderate 66 AI analysisMessage 85 · Strong
KX KruxKrux BitcoinHardware wallets

fix: reject a PSBT whose outputs exceed its inputs

This commit fixes a bug in Krux, a Bitcoin signing device, where a malformed transaction whose outputs spend more than its inputs could be loaded and shown to the user. Normally such a transaction is impossible on the Bitcoin network, but …

Input validation gap in PSBT parsingUI rendering bug masking invalid transaction economicsPotential social-engineering / user-confusion attack
d6813d88by odudex+52−02 files
Vendor flagged security relevance
Informational 15 AI analysisMessage 50 · Thin
KX KruxKrux BitcoinHardware wallets

i18n: translate the unverified input amounts warning

This commit only adds translations for two existing warning messages in the Krux Bitcoin hardware wallet software. It does not change any code logic, security behavior, or fix any vulnerability. The messages warn users that displayed fees …

bdaed1a1by odudex+46−023 files
No security note in commit
Moderate 62 AI analysisMessage 90 · Strong
KX KruxKrux BitcoinHardware wallets

feat: warn when PSBT input amounts cannot be verified

This commit adds a warning screen to Krux, a hardware signing device, when it is asked to sign a multi-input Bitcoin transaction where the amounts of some inputs cannot be independently verified. The risk is that a malicious transaction co…

New user-facing warning for unverified multi-input SegWit amountsDetection logic tied to BIP143 signature semantics and inp.is_verifiedDoes not enforce previous-transaction inclusion; user can still proceed
518b3314by odudex+159−24 files
Vendor flagged security relevance
Repository ledger

Explore captured commits

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

Lower-prioritydocs: reduce mnemonic guide diff noiseby Naman015 · 8ba9a454 · Aug 10, 2026 · 2 filesMessage 57 · ThinTriage 0Details
Commit message · Naman015

docs: reduce mnemonic guide diff noise

57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
documentation-only discount
Lower-priorityfix(i18n): translate other formats menuby Naman015 · df68d12d · Aug 9, 2026 · 2 filesMessage 57 · ThinTriage 0Details
Commit message · Naman015

fix(i18n): translate other formats menu

57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Lower-prioritychore: bump embit to v0.8.2by odudex · be7da35b · Aug 8, 2026 · 1 fileMessage 57 · ThinTriage 0Details
Commit message · odudex

chore: bump embit to v0.8.2

57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
AI review queueddocs: update mnemonic loading flowby Naman015 · e264e2f5 · Aug 8, 2026 · 22 filesMessage 57 · ThinInformational 15Details
Commit message · Naman015

docs: update mnemonic loading flow

57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
documentation-only discountsecond-pass: unusually broad change
AI analysis · Informational 15/100

This commit only updates user documentation and simulator test scripts to match a reorganized menu for loading a wallet recovery phrase. No actual wallet or security code was changed, so it does not create or fix a security vulnerability.

Lower-prioritytest: cover format-first mnemonic routesby Naman015 · 4c407b3c · Aug 8, 2026 · 1 fileMessage 67 · AdequateTriage 0Details
Commit message · Naman015

test: cover format-first mnemonic routes

67/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Mentions testing or verification! No meaningful explanatory body
Lower-priorityfeat: make mnemonic loading format-firstby Naman015 · 10631763 · Aug 8, 2026 · 3 filesMessage 57 · ThinTriage 0Details
Commit message · Naman015

feat: make mnemonic loading format-first

57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Lower-priorityMerge pull request #920 from odudex/docs/security-contactsby Jean Do · 8afa9eed · Aug 6, 2026 · 1 fileMessage 63 · AdequateTriage 0Details
Commit message · Jean Do

Merge pull request #920 from odudex/docs/security-contacts

Add Jean Do as Security Contact

63/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference✓ Names security-relevant behavior explicitly! No meaningful explanatory body
Why it was queued
documentation-only discountmerge-commit duplicate discount
Lower-prioritydocs: add Jean Do as security contactby odudex · 1967e16b · Aug 6, 2026 · 1 fileMessage 62 · AdequateTriage 0Details
Commit message · odudex

docs: add Jean Do as security contact

62/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Names security-relevant behavior explicitly! No meaningful explanatory body
Why it was queued
documentation-only discount
Security candidateMerge branch 'release-26.08.0'by odudex · be5eda28 · Aug 4, 2026 · 123 filesMessage 45 · ThinModerate 66Details
Commit message · odudex

Merge branch 'release-26.08.0'

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 pathboot or update pathmerge-commit duplicate discount
AI analysis · Moderate 66/100

This is a routine release merge for Krux firmware (version 26.08.0). It includes several genuine security fixes: a heap buffer overflow in camera-based entropy generation for a discontinued device, stricter fee calculation when signing Bitcoin transactions, and a warning when a transaction's input amounts cannot be verified. It also swaps the QR-code encoding library for a faster native one, removes support for the discontinued Maix Bit device, and makes various reliability improvements. The commit itself is a large merge, so the exact code changes are spread across many files and not all visible in the supplied diff.

Lower-prioritydocs: update CHANGELOGby odudex · ec058d86 · Aug 3, 2026 · 1 fileMessage 40 · ThinInformational 15Details
Commit message · odudex

docs: update CHANGELOG

40/100 · ThinMessage clarity
✓ Subject identifies a change✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
documentation-only discount
AI analysis · Informational 15/100

This commit only updates three date lines in the CHANGELOG.md file, changing '2025' to '2026' for three release entries. It does not modify any source code, build scripts, or documentation with security implications. The change is purely cosmetic/correctional and introduces no security risk.

Lower-prioritydocs: refresh numeric setting screenshotsby Naman015 · 7e086e3e · Aug 2, 2026 · 5 filesMessage 57 · ThinTriage 0Details
Commit message · Naman015

docs: refresh numeric setting screenshots

57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
documentation-only discount
Lower-prioritytest: cover numeric setting contextby Naman015 · 3a605da3 · Aug 2, 2026 · 3 filesMessage 67 · AdequateTriage 0Details
Commit message · Naman015

test: cover numeric setting context

67/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Mentions testing or verification! No meaningful explanatory body
Lower-priorityfeat: show units and ranges for numeric settingsby Naman015 · 6109bd7c · Aug 2, 2026 · 4 filesMessage 57 · ThinTriage 0Details
Commit message · Naman015

feat: show units and ranges for numeric settings

57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Lower-priorityfix: bind BBQr parts to the first part of the streamby odudex · 0b3e01b7 · Aug 1, 2026 · 3 filesMessage 85 · StrongModerate 66Details
Commit message · odudex

fix: bind BBQr parts to the first part of the stream

Reject parts that disagree with the first part's encoding, file type or
total, or that conflict with content already stored at the same index.
Bound the accumulated payload at the base32 expansion of the deflate
decompression limit.

85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
AI analysis · Moderate 66/100

This commit fixes Krux's QR code scanner so that when it reads a series of animated BBQr codes, every later frame must match the encoding and file type announced by the first frame, must agree on the total number of frames, and cannot overwrite an already-scanned frame with different data. It also caps how much data the scanner will accumulate, preventing a malicious or malformed stream from making the device run out of memory. The change is defensive hardening against QR stream confusion and memory exhaustion.

Lower-prioritydocs: update CHANGELOGby odudex · 4c05cefb · Aug 1, 2026 · 1 fileMessage 40 · ThinInformational 15Details
Commit message · odudex

docs: update CHANGELOG

40/100 · ThinMessage clarity
✓ Subject identifies a change✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
documentation-only discount
AI analysis · Informational 15/100

This commit only updates the project's CHANGELOG.md file. It adds text describing several bug fixes and improvements that were apparently made in prior code changes, but no actual code is changed in this commit. By itself, this documentation edit does not alter software behavior or introduce any security issue.

Security candidatechore(Maixpy): bump cURby odudex · 74d6ed40 · Aug 1, 2026 · 1 fileMessage 40 · ThinInformational 0Details
Commit message · odudex

chore(Maixpy): bump cUR

40/100 · ThinMessage clarity
✓ Subject identifies a change✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
boot or update path
AI analysis · Informational 0/100

This commit appears to be a routine version bump of a component called 'cUR' inside the MaixPy firmware build. No actual code changes are visible in the provided diff, and the commit message gives no indication of a security fix or vulnerability. There is nothing here that can be independently assessed as a security issue.

Lower-prioritychore: bump version to 26.08.0by odudex · dea991df · Jul 31, 2026 · 5 filesMessage 57 · ThinInformational 15Details
Commit message · odudex

chore: bump version to 26.08.0

57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
AI analysis · Informational 15/100

This commit is a routine version bump from 26.04.0 to 26.08.0. It only updates version strings in documentation, build files, and source metadata. No code behavior changes. The changelog text mentions a previously fixed heap buffer overflow, but that fix is not part of this diff.

Security candidatechore: bump MaixPy with updated glyphsby odudex · a9329228 · Jul 31, 2026 · 1 fileMessage 57 · ThinInformational 2Details
Commit message · odudex

chore: bump MaixPy with updated glyphs

57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
boot or update path
AI analysis · Informational 2/100

This commit appears to update a submodule or dependency called MaixPy to a newer version that includes updated visual glyphs (small icons/symbols). The title and message describe it as a routine maintenance chore, not a security fix. No actual code changes are visible in the supplied diff, and no security references were provided.

Security candidatefix: register embed_fire in the bdftokff device listby odudex · f15308e4 · Jul 31, 2026 · 1 fileMessage 85 · StrongInformational 15Details
Commit message · odudex

fix: register embed_fire in the bdftokff device list

The device was added in 26.03.0 but never listed, so glyph generation fell
through to the unmapped-device branch and printed an error on every run.
That branch happened to write the same 16px font, so the generated files
are unchanged by this.

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
boot or update path
AI analysis · Informational 15/100

This commit fixes a build-time font-generation script so that a newly supported device ('embed_fire') is recognized. Before the fix, the script printed an error but still produced the same font files. There is no security issue.

Security candidatedocs: add PSBT input amount fixes to CHANGELOGby odudex · 48920c31 · Jul 31, 2026 · 1 fileMessage 57 · ThinModerate 63Details
Commit message · odudex

docs: add PSBT input amount fixes to CHANGELOG

57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
signing boundarydocumentation-only discount
AI analysis · Moderate 63/100

This commit only updates the project's CHANGELOG.md to document earlier fixes related to PSBT (Partially Signed Bitcoin Transaction) fee and amount handling. It does not contain any code changes itself. The changelog entries describe security-relevant bugs where incorrect fee/amount calculations could be shown or confirmed during Bitcoin signing, which could trick a user into approving a bad transaction. However, because the actual fixes are not in this commit, we cannot inspect or verify them here.

AI review queuedi18n: translate the unverified input amounts warningby odudex · bdaed1a1 · Jul 31, 2026 · 23 filesMessage 50 · ThinInformational 15Details
Commit message · odudex

i18n: translate the unverified input amounts warning

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
translation-only discountsecond-pass: unusually broad change
AI analysis · Informational 15/100

This commit only adds translations for two existing warning messages in the Krux Bitcoin hardware wallet software. It does not change any code logic, security behavior, or fix any vulnerability. The messages warn users that displayed fees may be understated and that input amounts are unverified, but those warnings already existed in English; this change just makes them available in more languages.

Security candidatefix: reject a PSBT whose outputs exceed its inputsby odudex · d6813d88 · Jul 31, 2026 · 2 filesMessage 85 · StrongModerate 66Details
Commit message · odudex

fix: reject a PSBT whose outputs exceed its inputs

Such a transaction is invalid on chain, and it used to render as a small
negative fee with fee_percent clamped to 0.1, so the high fee warning
did not fire either. Fail at load instead.

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
signing boundarysigning or wallet path
AI analysis · Moderate 66/100

This commit fixes a bug in Krux, a Bitcoin signing device, where a malformed transaction whose outputs spend more than its inputs could be loaded and shown to the user. Normally such a transaction is impossible on the Bitcoin network, but Krux would display it with a tiny negative fee and skip the high-fee warning, potentially tricking a user into approving a transaction that can never be mined. The fix now rejects these PSBTs immediately when loading them.

Security candidatefix: verify PSBT input amounts before showing the feeby odudex · fc808059 · Jul 31, 2026 · 2 filesMessage 95 · StrongHigh 78Details
Commit message · odudex

fix: verify PSBT input amounts before showing the fee

Display, policy and sighash now all read inp.utxo, so the amount on the
review screen is the amount the signer commits to. Any attached previous
transaction must hash to the outpoint being spent, and legacy inputs
require one since their sighash does not commit to the amount.

95/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
signing boundarysigning or wallet path
AI analysis · High 78/100

This commit fixes a security flaw in Krux, a Bitcoin signing device. Before the fix, an attacker could trick the device into showing a low transaction fee on screen while actually signing a much higher fee. The fix makes the device verify that any attached previous transaction really matches the input being spent, and forces legacy (non-Segwit) inputs to include that previous transaction. It also makes sure the amount shown to the user is always the same amount the signature commits to. A small residual risk remains for multi-input Segwit transactions where previous transactions are not required.

Security candidatefeat: warn when PSBT input amounts cannot be verifiedby odudex · 518b3314 · Jul 31, 2026 · 4 filesMessage 90 · StrongModerate 62Details
Commit message · odudex

feat: warn when PSBT input amounts cannot be verified

BIP143 commits only to the amount of the input being signed, so a
coordinator can declare a different input truthfully in each of two
sessions and combine one valid signature per input. Warn when a
non-taproot PSBT has more than one input and any amount is unbacked
by its previous transaction.

The warning states the risk rather than instructing the user, since a
malicious retry request is indistinguishable from a failed transfer,
and signing the same transaction twice is legitimate when one person
holds more than one key of a multisig.

Translations for the two new strings are still pending.

90/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Names security-relevant behavior explicitly
Why it was queued
signing boundarysigning or wallet path
AI analysis · Moderate 62/100

This commit adds a warning screen to Krux, a hardware signing device, when it is asked to sign a multi-input Bitcoin transaction where the amounts of some inputs cannot be independently verified. The risk is that a malicious transaction coordinator could trick a user into paying a much higher fee than shown, or into signing away more money than intended, by lying about input amounts during separate signing sessions. The patch does not block signing; it only warns the user and asks whether to proceed. It also does not fix the underlying cryptographic gap in older SegWit (BIP143) signatures, which is why the warning is needed.

Lower-priorityfix: render negative amounts correctly in format_btcby odudex · c7e48ae1 · Jul 31, 2026 · 2 filesMessage 85 · StrongLow 27Details
Commit message · odudex

fix: render negative amounts correctly in format_btc

Floor division and modulo round towards minus infinity, so -1000 sats
was shown as -1.99 999 000. Take the sign out before splitting.

85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
AI analysis · Low 27/100

This commit fixes a display bug in how Krux formats negative Bitcoin amounts. Previously, a value like -1000 satoshis was shown incorrectly as roughly -1.99 bitcoins instead of -0.00001 bitcoins, because the code split the number before handling the minus sign. The fix simply removes the sign, formats the absolute value, then reattaches the minus sign. It is a user-interface bug, not a wallet-security vulnerability.