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

Security candidatefix: reject PSBT inputs with non-standard sighash types before signing (#844)by Odudex · e5318112 · Mar 30, 2026 · 3 filesMessage 98 · StrongHigh 78Details
Commit message · Odudex

fix: reject PSBT inputs with non-standard sighash types before signing (#844)

Adds pre-sign validation that refuses to sign if any input requests SIGHASH_NONE, SIGHASH_SINGLE, or ANYONECANPAY, which could allow an attacker to redirect funds after signing. Addresses security audit C2 of #843

98/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference✓ Names security-relevant behavior explicitly
Why it was queued
explicit security languagesigning boundarysigning or wallet path
AI analysis · High 78/100

Krux is a small, open-source Bitcoin signing device (hardware wallet). This commit fixes a security flaw where the device would sign transactions even if the sender asked it to use unusual Bitcoin signature modes—specifically SIGHASH_NONE, SIGHASH_SINGLE, or ANYONECANPAY. Those modes can let someone else change where the money goes after the device has already signed, which could be abused to steal funds. The fix makes the device refuse to sign any PSBT (the file format used to pass a transaction around) that contains those non-standard modes. The project labels this as a security fix for an external audit finding.

Lower-prioritychore: bump release versionby odudex · 941c4dfd · Mar 24, 2026 · 3 filesMessage 47 · ThinInformational 15Details
Commit message · odudex

chore: bump release version

47/100 · ThinMessage clarity
✓ Descriptive subject✓ Uses a recognizable type or scope! No meaningful explanatory body
AI analysis · Informational 15/100

This commit only updates three version strings from a beta release to a stable release. It changes no code logic, no security settings, and no dependencies. There is nothing here that affects security.

Lower-prioritychore: Add Embed Fire and WonderK to Actions build scriptby odudex · bf72db24 · Mar 24, 2026 · 1 fileMessage 62 · AdequateInformational 15Details
Commit message · odudex

chore: Add Embed Fire and WonderK to Actions build script

62/100 · AdequateMessage clarity
✓ Specific, 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
AI analysis · Informational 15/100

This commit simply adds two new hardware device targets (Embed Fire and WonderK) to the project's automated build script. It is a routine configuration change with no security relevance.

Lower-prioritydocs: update CHANGELOGby odudex · 94760c52 · Mar 24, 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 title line of the project's CHANGELOG file, changing the placeholder version and date to a concrete release version. It does not modify any code, configuration, or documentation that affects how the software behaves or how secure it is.

Lower-priorityfix: long addresses having cropped final letters at addresses page (#837)by Odudex · a7f117f0 · Mar 24, 2026 · 1 fileMessage 70 · AdequateInformational 15Details
Commit message · Odudex

fix: long addresses having cropped final letters at addresses page (#837)

70/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
AI analysis · Informational 15/100

This is a minor user-interface layout fix. In portrait mode, the screen was adding too little vertical space below a QR code before drawing a long text label (such as a Bitcoin address), causing the last letters of very long addresses to be cut off at the bottom edge. The change swaps a font-height spacing for a larger default padding so the full address remains visible. There is no security relevance in the commit itself.

Lower-prioritychore: enable mkdocs livereload for poe docs task (restore hot reload) (#838)by Tads · 36461371 · Mar 24, 2026 · 1 fileMessage 70 · AdequateInformational 15Details
Commit message · Tads

chore: enable mkdocs livereload for poe docs task (restore hot reload) (#838)

70/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
AI analysis · Informational 15/100

This commit changes a local documentation development command to re-enable automatic browser refresh when documentation files are edited. It is a routine developer-experience tweak with no security relevance.

AI review queuedchore: add Embed Fire and WonderK to sign_release scriptby odudex · 0befce26 · Mar 20, 2026 · 1 fileMessage 62 · AdequateInformational 15Details
Commit message · odudex

chore: add Embed Fire and WonderK to sign_release script

62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit simply adds two new hardware device names ('Embed Fire' and 'WonderK') to an internal release-signing script list. It does not change any security-sensitive logic, cryptography, or user-facing behavior. There is no indication of a vulnerability or security fix.

Lower-prioritychore: fetch Embit from master branchby odudex · 274b2bc5 · Mar 20, 2026 · 1 fileMessage 57 · ThinInformational 4Details
Commit message · odudex

chore: fetch Embit from master branch

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 4/100

This commit changes a single line in a vendor dependency file to fetch the Embit library from the master branch instead of a pinned version or tag. The diff itself is not available, and there is no evidence in the commit message or supplied references that this change fixes or introduces a security issue. It appears to be a routine dependency tracking change.

Lower-prioritychore: Update python environment dependencies (#835)by Odudex · def984e7 · Mar 19, 2026 · 2 filesMessage 70 · AdequateInformational 17Details
Commit message · Odudex

chore: Update python environment dependencies (#835)

70/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
AI analysis · Informational 17/100

This is a routine dependency update for the project's Python development environment. It bumps versions of tools used to build, test, and document the software—such as the code formatter, test coverage tool, documentation generator, and libraries used by the simulator. There is no indication in the commit that this fixes a known security vulnerability, and the changes do not alter the wallet/device firmware code itself.

AI review queuedrefactor: optimization on usage of foundation-ur and urtypes libs (#825)by Tads · 1b3f30a4 · Mar 19, 2026 · 6 filesMessage 70 · AdequateInformational 12Details
Commit message · Tads

refactor: optimization on usage of foundation-ur and urtypes libs (#825)

70/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 12/100

This commit is a code cleanup that changes how the Krux firmware imports and uses two libraries for handling Uniform Resource (UR) QR codes. It replaces broad 'import urtypes' statements with specific imports of individual modules, normalizes UR type string comparisons to uppercase, and simplifies one QR parser result return. There is no direct evidence in the commit that this fixes a security vulnerability.

Lower-prioritydocs: change TZT link to find other sellers (#824)by Tads · 5897828f · Mar 19, 2026 · 1 fileMessage 70 · AdequateInformational 15Details
Commit message · Tads

docs: change TZT link to find other sellers (#824)

70/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
documentation-only discount
AI analysis · Informational 15/100

This commit simply updates a hyperlink in the project's documentation to point to a different AliExpress search page for the same hardware device. It is a documentation-only change with no code modifications and no security implications.

Lower-prioritydocs: update changelog following up #820by odudex · 5ae4ff5b · Jan 22, 2026 · 1 fileMessage 65 · AdequateInformational 15Details
Commit message · odudex

docs: update changelog following up #820

65/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
documentation-only discount
AI analysis · Informational 15/100

This commit only adds one line to the changelog file describing a previously merged feature. It does not change any code, configuration, or executable behavior. There is no security-relevant change in the diff itself.

AI review queuedrefactor: black following up #820by odudex · 7644f965 · Jan 22, 2026 · 2 filesMessage 65 · AdequateInformational 15Details
Commit message · odudex

refactor: black following up #820

65/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit is purely a code-style cleanup. It removes an extra blank line and adjusts spacing around a comment so the code matches the project's formatting rules (the 'black' formatter). No behavior of the wallet software changes, and there is no security fix or vulnerability introduced.

Security candidatefix: printer not changing TX/RX pin (#810)by Tads · 97d37c44 · Jan 22, 2026 · 2 filesMessage 65 · AdequateLow 28Details
Commit message · Tads

fix: printer not changing TX/RX pin (#810)

65/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
access control
AI analysis · Low 28/100

This commit fixes a bug where the Krux device could not switch which physical pins it uses to talk to a printer. The change forces the hardware to reassign the printer's data pins (TX/RX) even if they were already mapped to something else. This is a functional bug fix rather than a clear security patch, but incorrect pin mapping could in theory cause a printer to misbehave or leak data on the wrong pins.

AI review queuedSimplify internal key validation for taproot (#820)by Pac · 5dcab5f0 · Jan 22, 2026 · 2 filesMessage 96 · StrongLow 34Details
Commit message · Pac

Simplify internal key validation for taproot (#820)

* Simplify internal key validation for taproot

There is no standard for how to generate the taproot keypath chaincode to be used with the NUMS pubkey.
Liana does it by hashing the taptree keys;
Coldcard uses a random chaincode;
Nunchuck hashes the taptree keys, but remove duplicates and sort the keys before hashing.
This fix changes the verification logic to check only the NUMS pubkey and ignore the chaincode.

* Allow loading of non-deterministic chain code in wallet

The wallet now loads the non-deterministic chain code without raising an error, indicating it is considered valid.

96/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference✓ Names security-relevant behavior explicitly
Why it was queued
defensive validationsigning or wallet pathsecond-pass: near security thresholdsecond-pass: security-sensitive path
AI analysis · Low 34/100

This change relaxes how Krux checks the 'internal key' used in Taproot multisig wallets. Previously it required the wallet to use a specific deterministic chain code derived from the other public keys; now it only checks that the internal key is the well-known NUMS (provably unspendable) public key and ignores the chain code. This makes Krux compatible with wallets like Coldcard and Nunchuck that use different chain-code conventions, but it removes a validation step that ensured the internal key was constructed in a specific reproducible way.

AI review queuedchore: update black follow-upby odudex · 6695d325 · Jan 22, 2026 · 8 filesMessage 57 · ThinInformational 15Details
Commit message · odudex

chore: update black follow-up

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

This commit only removes blank lines between import blocks in eight Python files. It is a code-formatting cleanup with no functional changes and no security relevance.

Security candidatechore: update blackby odudex · acf84c93 · Jan 22, 2026 · 3 filesMessage 40 · ThinInformational 15Details
Commit message · odudex

chore: update black

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 15/100

This is a routine developer maintenance commit that updates the Black code formatter from version 25 to version 26, refreshes the Poetry lockfile with newer versions of many development and documentation dependencies, and applies one tiny formatting change (removing a blank line) in a font conversion script. There is no indication of any security fix or vulnerability being addressed.

Lower-priorityfix: build process (#823)by Tads · eab445b5 · Jan 22, 2026 · 1 fileMessage 55 · ThinInformational 18Details
Commit message · Tads

fix: build process (#823)

55/100 · ThinMessage clarity
✓ Descriptive subject✓ Uses a recognizable type or scope✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
AI analysis · Informational 18/100

This commit changes how a build container downloads a third-party compiler toolchain. The old command tried to clone submodules in one step from the original binutils-gdb repository, which appears to be unavailable or moved. The new approach clones the main repository first, then redirects the submodule URL to an archived copy before initializing submodules. This is a build-fix change, not an obvious security patch, but it does alter which source code is pulled into the build environment.

Lower-prioritydocs: update telegram group linkby odudex · 97d1fb3c · Jan 13, 2026 · 3 filesMessage 57 · ThinInformational 15Details
Commit message · odudex

docs: update telegram group link

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 simply updates the project's Telegram support group link from an old group name to a new one across three documentation files. It does not change any code, security settings, or functionality.

Lower-prioritydocs: update telegram group linkby odudex · bff65f4f · Jan 13, 2026 · 3 filesMessage 57 · ThinInformational 15Details
Commit message · odudex

docs: update telegram group link

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 simply updates the project's Telegram support group link from one URL (t.me/SC_Krux) to another (t.me/KruxDIY) in three documentation files. It is a routine documentation change with no security relevance.

AI review queuedfeat: Loading a Descriptor Sets Wallet Attributes (#802)by Odudex · 86340f31 · Dec 17, 2025 · 31 filesMessage 93 · StrongLow 35Details
Commit message · Odudex

feat: Loading a Descriptor Sets Wallet Attributes (#802)

*feat: loading a descriptor sets wallet attributes

*feat: remove the feature to load xpubs as they were descriptors, with or without assumptions.

93/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathsecond-pass: unusually broad changesecond-pass: security-sensitive path
AI analysis · Low 35/100

This commit changes how Krux handles wallet descriptors. Instead of requiring users to manually set wallet type (single-sig, multisig, miniscript), network (mainnet/testnet), and address format, Krux now reads these directly from the descriptor. It also removes the old feature that tried to guess these settings from raw xpubs, which could make unsafe assumptions. When a loaded descriptor doesn't match the currently configured wallet, Krux now shows a clear warning and asks the user whether to switch settings automatically. Overall this is a security-hardening and usability improvement, not an introduced vulnerability.

Lower-prioritydocs: add lavarand (#764)by Tads · b7484133 · Dec 10, 2025 · 1 fileMessage 55 · ThinInformational 15Details
Commit message · Tads

docs: add lavarand (#764)

55/100 · ThinMessage clarity
✓ Descriptive subject✓ Uses a recognizable type or scope✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
documentation-only discount
AI analysis · Informational 15/100

This commit only updates user documentation. It adds a footnote comparing Krux's camera-based mnemonic generation to an old system called Lavarand, and rewords some explanatory text about entropy quality indicators. No code, cryptography, or device behavior was changed.

Lower-priorityfix: adjust fingerprint warning message for rare case (#801)by Tads · 11791084 · Dec 10, 2025 · 2 filesMessage 70 · AdequateLow 32Details
Commit message · Tads

fix: adjust fingerprint warning message for rare case (#801)

70/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
AI analysis · Low 32/100

This commit fixes a warning message that was being shown to users at the wrong time. The Krux device signs Bitcoin transactions using PSBT files. In rare cases, the device needs to fill in a missing 'fingerprint' (a short identifier for a wallet key) with zeros before signing. The warning 'Fingerprint unset in PSBT' was being displayed whenever this zero-fill happened, even when the wallet's own fingerprint was already zero. That meant users could see a confusing or misleading security warning in a legitimate situation. The change only shows the warning when the wallet actually has a non-zero fingerprint but the PSBT still needs zero filling. This is a user-interface and correctness fix, not a direct theft-of-funds vulnerability, but misleading warnings can train users to ignore real security alerts.

Lower-prioritydocs: macaw image by odudex (#803)by Odudex · 8f0fd5ee · Dec 9, 2025 · 5 filesMessage 65 · AdequateInformational 15Details
Commit message · Odudex

docs: macaw image by odudex (#803)

65/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
AI analysis · Informational 15/100

This commit is a documentation and simulator update. It swaps in a new macaw (arara) image for screenshots and QR-code simulation sequences, and adds one harmless mock method so the simulator can handle a camera lens-correction call. There is no security-relevant change.

Lower-priorityci: add convetional commits to krux (#787)by qlrd · ab08d5f1 · Dec 8, 2025 · 1 fileMessage 65 · AdequateInformational 15Details
Commit message · qlrd

ci: add convetional commits to krux (#787)

65/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
documentation-only discount
AI analysis · Informational 15/100

This commit adds a new automated GitHub Actions check that enforces conventional commit message formatting (like 'feat:', 'fix:', 'ci:') for pull requests. It does not change any application code, cryptography, wallet logic, or user-facing behavior. There is no security relevance in the change itself.