CommitWatch RSS
KS
← All projectsKeystone

Keystone 3 firmware

Open-source device firmware for Keystone 3 hardware wallets.

BitcoinHardware walletsNormal
Source repository ↗
Repository coverage

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

109security candidates287second-pass queue368AI analyses
117commits · 30 days
157commits · 60 days
274commits · 180 days
533commits · 365 days
Backfill bands
Aug 5 → Feb 6260 seen14 candidatesComplete
Feb 6 → Jun 6117 seen7 candidatesComplete
Jun 6 → Jul 639 seen4 candidatesComplete
Jul 6 → Aug 5115 seen4 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.

42/100 average clarity
35Strong · 80–100
64Adequate · 60–79
203Thin · 40–59
232Opaque · 0–39
37security 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.
Adam Tucker931142163
aaron30412148
ww351268717551163026
soralit1153469048
willwang1523025
John Boyd623088
Qkin-Keystone26123036
qkin12111050
Greg Pfeil412071
Daira-Emma Hopwood211085
Soralit210058
bianminyan45031032
Analysis record

Published AI watches

Last scanned 15 minutes ago

Moderate 59 AI analysisMessage 28 · Opaque
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

replace lvgl rand

This commit swaps out the LVGL graphics library's pseudo-random number generator for the device's hardware true random number generator (TRNG) in two places: shuffling the on-screen numeric keypad and shuffling recovery-word lists. The old…

Replacement of non-cryptographic PRNG with hardware TRNG in security-sensitive shuffle routinesFisher-Yates shuffle of on-screen PIN keypad now uses TrngGetFisher-Yates shuffle of mnemonic word array now uses TrngGet
f7d64fb8by ww3512687+8−32 files
No security note in commit
Open full analysis →Source commit ↗
Informational 19 AI analysisMessage 85 · Strong
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

fix(simulator): return password error on PIN mismatch in SimulatorLoadAccountSecret

This commit fixes a bug in the firmware's simulator (a software stand-in used for testing, not the real hardware wallet). When checking a stored account password/PIN, the simulator was accidentally returning 'success' even when the passwor…

Incorrect success return on authentication failure in simulator-only codeMismatch between simulator and real-device authentication error semanticsFunctional regression in multi-account PIN creation in simulator builds
6bec6930by soralit+4−11 file
No security note in commit
Open full analysis →Source commit ↗
Low 49 AI analysisMessage 57 · Thin
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

fix: address Solana review findings

This commit improves how Keystone 3's Solana app recognizes and displays certain transaction types. It adds support for the Solana Compute Budget program so those instructions are no longer labeled as 'Unknown,' and it adds parsing for Sol…

Previously unknown Compute Budget instructions are now parsed and labeled, reducing the chance a user approves a transaction they cannot understand.Off-chain signing messages are parsed with format and length validation, so wallet-connect-style sign-in messages are shown as text rather than misinterpreted as transactions.Unknown program accounts are surfaced explicitly in the UI instead of being hidden inside a generic 'Unknown' instruction list.
e1752174by soralit+343−5711 files
No security note in commit
Open full analysis →Source commit ↗
Informational 12 AI analysisMessage 47 · Thin
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

chore: remove implementation plan

This commit only deletes a planning document from the repository's docs folder. No firmware code, build scripts, or cryptographic logic were changed. The deleted file described a previously completed security-hardening task about removing …

Deleted document references a prior security-hardening task (issue #2255 / PRNG fallback removal)No source-code or build-system changes in the diff
4620fe94by ww3512687+0−1041 file
No security note in commit
Open full analysis →Source commit ↗
Moderate 64 AI analysisMessage 80 · Strong
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

fix: remove insecure PRNG fallback

This commit removes a weak, predictable random-number generator that was bundled as a backup inside the firmware's SLIP-39 code. Previously, if the device's proper hardware random source was accidentally left out of a build, the firmware c…

Removal of deterministic LCG PRNG (random32)Removal of weak-symbol random_buffer fallbackRemoval of unused random helper APIs
17c78e30by ww3512687+108−693 files
Vendor flagged security relevance
Open full analysis →Source commit ↗
Informational 10 AI analysisMessage 40 · Thin
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

chore: update ci

This commit is described as a routine CI (continuous integration) update with only one line changed in a release-related file. No code changes affecting wallet security, cryptography, or user funds are visible, and no security relevance is…

39cfff13by soralit+1−11 file
No security note in commit
Open full analysis →Source commit ↗
Moderate 63 AI analysisMessage 57 · Thin
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

fix: regular AI code review and fix

This is a large, routine code-quality and hardening patch for the Keystone 3 hardware wallet firmware. It tightens how transactions are parsed and displayed for several cryptocurrencies (Arweave, Avalanche, Bitcoin, Cosmos, Ethereum, Solan…

Arweave: duplicate required tags now rejected, malformed/trailing Avro data now rejectedArweave: DataItem tag count mismatch now rejectedAvalanche: trailing transaction bytes now rejected via parsed_size checks
e2c0ef31by soralit+3998−142676 files
No security note in commit
Open full analysis →Source commit ↗
Informational 19 AI analysisMessage 85 · Strong
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

fix: guard Solana USB pubkey service for non-web3 builds

This commit fixes a firmware build problem, not a runtime security bug. The Solana USB public-key service was calling a function that only exists in the multi-coin 'web3' firmware variant, so the more limited 'cypherpunk' and 'bitcoin-only…

Build/link-time failure fix for conditional feature compilationExplicit error response added for unsupported coin type on non-web3 buildsNo input validation, memory safety, or cryptographic changes observed
9d04150dby John Boyd+10−01 file
No security note in commit
Open full analysis →Source commit ↗
Low 33 AI analysisMessage 45 · Thin
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

optimize sol derivation path allocation

This commit refactors how a Solana cryptocurrency derivation path is stored while parsing a USB request. Previously, the code dynamically allocated a small heap buffer inside a helper function and returned it to the caller, which then had …

Eliminates heap allocation for a fixed-size derivation-path bufferRemoves manual free responsibility from caller, reducing memory leak / use-after-free riskSwitches helper return type from pointer to bool to enforce explicit success/failure handling
9c3efd94by ww3512687+12−201 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 47 · Thin
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

chore: upgrade rust version

This commit upgrades the Rust compiler toolchain from one nightly version to a newer one and adjusts code to keep the project building and tests passing. It does not fix a known security bug or change how user funds are protected. Most of …

82a48133by soralit+511−1321 files
No security note in commit
Open full analysis →Source commit ↗
Low 36 AI analysisMessage 28 · Opaque
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

support sol cli

This commit adds Solana CLI support to the Keystone 3 hardware wallet firmware. It introduces a new USB command that lets a connected computer request public keys for specific Solana derivation paths, and it reworks how USB responses are s…

New USB command exposes public-key export for a specific coin type and derivation pathAdded NULL/empty checks before returning generated UR data and before using cached passwordMoved several UR result sends from synchronous to asynchronous (task-queue based) dispatch
77833f49by ww3512687+282−2016 files
No security note in commit
Open full analysis →Source commit ↗
Informational 17 AI analysisMessage 68 · Adequate
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

Preserve Zcash account firmware version (#37)

This commit is a small, non-security code change. It updates a Zcash wallet test to verify that the firmware version string is preserved when account data is encoded and decoded, and it switches two Rust library dependencies from the publi…

Dependency source changed from crates.io to a third-party Git repository (valargroup/keystone-sdk-rust)No mention of vulnerability, CVE, security fix, or researcher attribution in commit message or diffChange is limited to a unit test assertion and dependency source pinning
20d7ea2dby Adam+11−73 files
No security note in commit
Open full analysis →Source commit ↗
Low 28 AI analysisMessage 45 · Thin
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

Preserve PCZT v1 response encoding

This commit changes how the Keystone hardware wallet handles Zcash PCZT (partially-created transaction) files. Previously, after checking and signing a transaction, the device always returned the result in the newer v2 format. Now it remem…

Behavioral change in serialization format selectionNew parsing helper reads wire version from raw bytesTest coverage added for v1 preservation
acf3611aby Adam Tucker+136−245 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 62 · Adequate
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

refactor(zcash): use shielded pool display directly

This commit is a minor code cleanup in the Zcash shielded-transaction handling code. It removes temporary variables named `pool_label` and instead uses the existing `pool` value directly when building error messages. There is no change to …

9074e087by Adam Tucker+22−334 files
No security note in commit
Open full analysis →Source commit ↗
Low 37 AI analysisMessage 57 · Thin
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

fix(zcash): allow transparent-only V6 PCZTs

This commit changes how Keystone's Zcash transaction handling treats version 6 (V6) PCZTs. Previously, all V6 Zcash transactions were rejected in the non-cypherpunk (transparent-only) code path. The patch now allows V6 transactions as long…

Guard relaxation: V6 PCZTs no longer blanket-rejected in transparent-only buildsBoundary enforcement remains for shielded Sapling/Orchard/Ironwood contentUnknown transaction versions still rejected
ba4ecf28by Adam Tucker+127−954 files
No security note in commit
Open full analysis →Source commit ↗
Informational 10 AI analysisMessage 40 · Thin
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

chore: update ci

This commit is described as a routine CI (Continuous Integration) update with only one line changed in one file. No diff content is available, and there are no verified references suggesting any security relevance. It appears to be a munda…

7f2c4423by soralit+1−11 file
No security note in commit
Open full analysis →Source commit ↗
Informational 14 AI analysisMessage 62 · Adequate
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

refactor(zcash): simplify unsupported PCZT helpers

This is a simple code cleanup: three internal helper functions in the Zcash PCZT handling code are renamed to remove the word 'legacy' from their names. The actual behavior and security checks stay exactly the same. There is no functional …

0f0dc78aby Adam Tucker+6−63 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 57 · Thin
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

refactor(zcash): display shielded pool names

This commit is a small code cleanup in the Zcash transaction handling code. It replaces a custom `label()` method on the `ShieldedPool` type with Rust's standard `Display` trait, so the pool name prints the same way in error messages. Ther…

83ac1e21by Adam Tucker+16−194 files
No security note in commit
Open full analysis →Source commit ↗
Low 42 AI analysisMessage 62 · Adequate
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

fix(zcash): defer checked batch cleanup after signing

This patch changes when a Zcash batch signing screen frees a sensitive internal data structure. Instead of destroying the data immediately when the page is cleared, it now schedules the cleanup to run after the signing operation has finish…

Use-after-free / premature-free risk in cryptographic signing pathAsync deferred cleanup introduced to avoid race with FIFO signing taskInline comment explicitly describes security-relevant ordering constraint
3b8995faby Adam Tucker+32−11 file
No security note in commit
Open full analysis →Source commit ↗
Moderate 59 AI analysisMessage 57 · Thin
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

fix(zcash): size UFVK buffers for terminators

This commit fixes a buffer sizing bug in the Keystone hardware wallet's Zcash support. The code previously treated the maximum string length and the buffer size as the same number, leaving no guaranteed room for the null terminator at the …

Off-by-one buffer sizing for null terminator in Zcash UFVK handlingUse of string-length constant instead of buffer-size constant in strcpy_s and memset_s callsInconsistent buffer declarations across account manager and GUI code
5f158dd3by Adam Tucker+14−136 files
No security note in commit
Open full analysis →Source commit ↗
Repository ledger

Explore captured commits

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

AI review queuedfix: zec logo issueby soralit · 09d86c89 · Jan 21, 2026 · 1 fileMessage 40 · ThinInformational 15Details
Commit message · soralit

fix: zec logo issue

40/100 · ThinMessage clarity
✓ Subject identifies a change✓ 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 fixes a display issue by adding the Zcash (ZEC) coin logo to the list of icons shown for the Keystone wallet connection screen. It also removes a few leftover blank lines and an outdated 'todo' comment. There is no security-relevant change in this patch.

Lower-priorityfeat: check pczt transparent inputs with multi-coins firmwareby soralit · 200ee85f · Jan 21, 2026 · 7 filesMessage 62 · AdequateTriage 0Details
Commit message · soralit

feat: check pczt transparent inputs with multi-coins firmware

62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Lower-priorityfeat: update keystone nexus connection imageby soralit · 0014939c · Jan 21, 2026 · 1 fileMessage 57 · ThinTriage 0Details
Commit message · soralit

feat: update keystone nexus connection image

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: a macro typoby soralit · 1046935a · Jan 21, 2026 · 1 fileMessage 40 · ThinTriage 0Details
Commit message · soralit

fix: a macro typo

40/100 · ThinMessage clarity
✓ Subject identifies a change✓ Uses a recognizable type or scope! No meaningful explanatory body
Lower-priorityfix: zcash seed fingerprint export issueby soralit · 8c61eb6d · Jan 21, 2026 · 1 fileMessage 57 · ThinTriage 0Details
Commit message · soralit

fix: zcash seed fingerprint export issue

57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Lower-priorityfix: zcash ui issueby soralit · 14a3e2ed · Jan 21, 2026 · 2 filesMessage 40 · ThinTriage 0Details
Commit message · soralit

fix: zcash ui issue

40/100 · ThinMessage clarity
✓ Subject identifies a change✓ Uses a recognizable type or scope! No meaningful explanatory body
AI review queuedfix: unit testsby soralit · 7966cfab · Jan 21, 2026 · 22 filesMessage 50 · ThinInformational 14Details
Commit message · soralit

fix: unit tests

50/100 · ThinMessage clarity
✓ Subject identifies a change✓ Uses a recognizable type or scope✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: unusually broad changesecond-pass: security-sensitive path
AI analysis · Informational 14/100

This commit only fixes and adds unit tests. It changes test-only dependencies, adds new test cases for Bitcoin address encoding and Zcash address generation/PCZT signing, and slightly adjusts code-coverage thresholds in CI. There is no change to production firmware behavior, no bug fix in shipped code, and no security-relevant change visible in the diff.

Security candidaterefactor: zcash transparent and orchard logicby soralit · ad7f4a3d · Jan 21, 2026 · 22 filesMessage 57 · ThinInformational 24Details
Commit message · soralit

refactor: zcash transparent and orchard logic

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
cryptography-sensitive pathsigning or wallet path
AI analysis · Informational 24/100

This commit is a large refactor of how the Keystone 3 firmware handles Zcash transactions. It splits the code into two build flavors: a 'multi-coins' build that supports only transparent (public) Zcash addresses using a normal xpub, and a 'cypherpunk' build that also supports shielded Orchard addresses using a unified full viewing key (UFVK). The change reorganizes feature flags, renames functions, and adjusts how Zcash account data is cached when wallets are created or unlocked. There is no explicit security fix or vulnerability disclosure in the commit message, and the diff itself is mostly structural. A few small items stand out as worth checking: a typo in a feature-guard macro (CYBERPUNK_VERSION vs CYPHERPUNK_VERSION) could leave the cypherpunk UI path disabled, and a debug printf was left in production key-handling code. On its own, this commit does not appear to introduce a clear exploitable vulnerability, but it is a partial refactor and the new multi-coins transparent-only path is simpler and exposes less shielded-key material than before.

AI review queuedchore: update zcashby soralit · f6b8f8c0 · Jan 21, 2026 · 9 filesMessage 40 · ThinLow 26Details
Commit message · soralit

chore: update zcash

40/100 · ThinMessage clarity
✓ Subject identifies a change✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 26/100

This commit is a routine Zcash update and test-coverage improvement. It renames a misspelled function, splits a large signing routine into transparent-only and orchard-only variants, and adds unit tests for wallet integrations. There is no direct evidence in the commit that this fixes an active security vulnerability, but the change to Zcash shielded signing logic is security-adjacent and should be reviewed carefully.

AI review queuedrefactor: split sign functionalityby soralit · d187d33c · Jan 21, 2026 · 2 filesMessage 47 · ThinInformational 17Details
Commit message · soralit

refactor: split sign functionality

47/100 · ThinMessage clarity
✓ Descriptive subject✓ 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 17/100

This commit is a straightforward code cleanup that renames two internal signing functions to avoid a naming conflict. It does not change what the code does, only how it is organized. There is no indication of a security bug being fixed.

AI review queuedchore: fix buildby soralit · 089c18ca · Jan 21, 2026 · 2 filesMessage 40 · ThinInformational 15Details
Commit message · soralit

chore: fix build

40/100 · ThinMessage clarity
✓ Subject identifies a change✓ 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 is a routine build-fix commit. It corrects a typo in a function name (GetXpubPath to GetXPubPath) and adds a missing newline at the end of a hash file. There is no security-relevant change.

Lower-priorityfix: unit testby soralit · d4a93a3c · Jan 21, 2026 · 3 filesMessage 50 · ThinTriage 0Details
Commit message · soralit

fix: unit test

50/100 · ThinMessage clarity
✓ Subject identifies a change✓ Uses a recognizable type or scope✓ Mentions testing or verification! No meaningful explanatory body
Security candidatefeat: support zcash for keystone nexusby soralit · b0eb9588 · Jan 21, 2026 · 8 filesMessage 57 · ThinInformational 12Details
Commit message · soralit

feat: support zcash for keystone nexus

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
cryptography-sensitive path
AI analysis · Informational 12/100

This commit adds Zcash cryptocurrency support to the Keystone 3 hardware wallet firmware. It registers a new Zcash unified full viewing key type, enables encryption of that key, wires up the user-interface handlers for Zcash transactions, and adjusts build flags so Zcash support is available in non-Bitcoin-only firmware builds. There is no direct evidence in the diff of a security vulnerability; it reads as a feature addition.

AI review queuedfeat: adjust firmware sizeby soralit · cd6bc43f · Jan 21, 2026 · 13 filesMessage 47 · ThinInformational 18Details
Commit message · soralit

feat: adjust firmware size

47/100 · ThinMessage clarity
✓ Descriptive subject✓ 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 18/100

This commit reorganizes Zcash support in a hardware-wallet firmware so that advanced privacy features (the 'Orchard' shielded pool) are only included when a special 'cypherpunk' build feature is enabled. The default build keeps only transparent and Sapling support, which shrinks the firmware binary. The changes are mostly compile-time feature flags and duplicated code paths for the smaller default build. There is no direct evidence in the commit that this fixes an exploitable security bug; it is a build-size and feature-gating change.

Security candidatefeat: add zcashby soralit · fd8f184e · Jan 21, 2026 · 14 filesMessage 40 · ThinInformational 15Details
Commit message · soralit

feat: add zcash

40/100 · ThinMessage clarity
✓ Subject identifies a change✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
cryptography-sensitive pathsigning or wallet path
AI analysis · Informational 15/100

This commit adds support for the Zcash (ZEC) cryptocurrency to the Keystone 3 hardware wallet firmware. It introduces address generation, derivation path handling, UI elements, and wallet connection data for Zcash. There is no indication of a security fix or vulnerability being patched.

Security candidatetest: temp commitby soralit · 40cb0b51 · Jan 21, 2026 · 12 filesMessage 30 · OpaqueInformational 24Details
Commit message · soralit

test: temp commit

30/100 · OpaqueMessage clarity
✓ Subject identifies a change✓ Uses a recognizable type or scope✓ Mentions testing or verification! No meaningful explanatory body! Contains work-in-progress language! Opaque security-relevant change
Why it was queued
cryptography-sensitive pathsigning or wallet path
AI analysis · Informational 24/100

This commit is a work-in-progress 'temp commit' that refactors Zcash support in the Keystone 3 firmware. It moves Zcash UI code from a 'cypherpunk' build variant into the standard multi-coin build, splits a combined Zcash UFVK/seed-fingerprint getter into separate functions, adds a new Zcash seed fingerprint parameter to the Keystone Connect wallet QR/UR generation, and enables the 'zcash' feature in the Rust multi-coins build. There is no clear security fix or vulnerability being patched; it appears to be feature plumbing and code reorganisation.

AI review queuedupdate nabox pubkeyby ww3512687 · d4e8b377 · Jan 21, 2026 · 3 filesMessage 28 · OpaqueInformational 15Details
Commit message · ww3512687

update nabox pubkey

28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: opaque commit messagesecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit adds a new wallet integration for Nabox in the Keystone 3 hardware wallet firmware. It changes which public keys (extended public keys, or xpubs) are shown when the user selects Nabox from the wallet list, switching from Ethereum-only data to a broader set covering Bitcoin, Ethereum, Tron, Solana, Litecoin, Dogecoin, and Bitcoin Cash. There is no security vulnerability visible in the diff; it appears to be a normal feature update.

AI review queuedfix ui bugby ww3512687 · 20d8b857 · Jan 9, 2026 · 1 fileMessage 0 · OpaqueInformational 15Details
Commit message · ww3512687

fix ui bug

0/100 · OpaqueMessage clarity
! Very short subject! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100

This commit changes a single displayed wallet name from 'Blue Wallet' to 'BlueWallet' in the status bar UI. It is a cosmetic string correction with no security relevance visible in the code.

AI review queuedRefactor code structure for improved readability and maintainabilityby ww3512687 · 62253f51 · Jan 9, 2026 · 7 filesMessage 50 · ThinInformational 15Details
Commit message · ww3512687

Refactor code structure for improved readability and maintainability

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

This commit is a routine UI cleanup for a hardware wallet firmware. It adds a new wallet icon for Jupiter, removes unused wallet-list icons, and reorganizes the list of supported wallets in one source file. There is no indication of any security bug or vulnerability being fixed.

AI review queuedfix ui bugsby ww3512687 · 44ab3c34 · Jan 8, 2026 · 1 fileMessage 0 · OpaqueInformational 15Details
Commit message · ww3512687

fix ui bugs

0/100 · OpaqueMessage clarity
! Very short subject! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100

This commit adds a single debug printf statement that prints a wallet name to the console when a status-bar wallet icon is set. It does not change program logic, access controls, memory handling, or user-facing behavior. There is no apparent security relevance.

AI review queuedfixby ww3512687 · 8fc1c4a2 · Jan 8, 2026 · 3 filesMessage 0 · OpaqueInformational 15Details
Commit message · ww3512687

fix

0/100 · OpaqueMessage clarity
! Generic or placeholder subject! Too few words to establish purpose! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: opaque commit messagesecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit only changes the display names of wallet options shown on the device screen (for example, 'Blue Wallet' to 'BlueWallet', 'Core' to 'Core Wallet', and 'Bitcoin Wallet' to 'Bitcoin Wallets'). It also slightly adjusts when a 'more coins' icon appears for two specific wallets. There is no security-relevant change here.

AI review queuedrefactor connect wallet uiby ww3512687 · c9654063 · Jan 8, 2026 · 106 filesMessage 35 · OpaqueInformational 15Details
Commit message · ww3512687

refactor connect wallet ui

35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: opaque commit messagesecond-pass: unusually broad changesecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit is a user-interface cleanup for the 'connect wallet' screen. It removes many unused wallet-list image files and their generated C code, updates one wallet icon size, and refactors the widget code that draws the wallet connection screen. There is no indication this changes security logic, cryptography, transaction handling, or how the device protects private keys.

AI review queuedfix connect wallet uiby ww3512687 · c8197bcd · Jan 7, 2026 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · ww3512687

fix connect wallet ui

28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100

This commit changes which wallet icons and names appear in the status bar depending on which product version is being built (Web3, Cypherpunk, or Bitcoin-only). It is a user-interface adjustment, not a security fix.

AI review queuedfix cypherpunk buildby ww3512687 · 1eaf6501 · Jan 6, 2026 · 1 fileMessage 28 · OpaqueInformational 18Details
Commit message · ww3512687

fix cypherpunk build

28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 18/100

This commit fixes a build error in a special firmware variant called 'cypherpunk' (also referred to as BTC_ONLY). It changes which cryptocurrency address settings are used when the firmware is compiled without certain optional features. There is no direct evidence this is a security vulnerability; it appears to be a build-breakage fix that could affect which coin's receive/address settings appear in the UI.

AI review queuedfix ui bugsby ww3512687 · b01d5444 · Jan 6, 2026 · 1 fileMessage 0 · OpaqueInformational 11Details
Commit message · ww3512687

fix ui bugs

0/100 · OpaqueMessage clarity
! Very short subject! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 11/100

This commit changes how wallet names are listed in the status bar for different product build variants (Web3, Cypherpunk, Bitcoin-only). It also adds a debug printf statement that prints a wallet name to the console. There is no clear security issue visible in the diff itself.