CommitWatch RSS
KS
← All projectsKeystone

Keystone 3 firmware

Open-source device firmware for Keystone 3 hardware wallets.

BitcoinHardware walletsNormal
Source repository ↗
Repository coverage

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

107security candidates287second-pass queue212AI analyses
116commits · 30 days
155commits · 60 days
272commits · 180 days
532commits · 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.

41/100 average clarity
35Strong · 80–100
64Adequate · 60–79
201Thin · 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 Tucker931134163
aaron3046148
ww35126871755182026
soralit1143359048
willwang1522025
John Boyd622088
Qkin-Keystone26113036
qkin12110050
Greg Pfeil411071
Daira-Emma Hopwood211085
bianminyan4500032
stone wang301038
Analysis record

Published AI watches

Last scanned 1 minute ago

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 ↗
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 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 ↗
Low 35 AI analysisMessage 45 · Thin
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

Release Zcash batch review widgets before signing

This commit fixes a potential memory/resource issue in the Zcash batch signing flow on the Keystone 3 hardware wallet. Before opening the signature view, the code now explicitly frees (destroys) the on-screen review widgets. Without this c…

Resource cleanup before sensitive signing operationUI object destruction to prevent memory pressure during cryptographic signing flowPotential UI state inconsistency mitigated by explicit widget release
2982da56by Adam Tucker+4−01 file
No security note in commit
Open full analysis →Source commit ↗
Low 30 AI analysisMessage 50 · Thin
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

fix the verifying ps hang on wrong password in btc only multi-sig

This commit fixes a user-interface bug in the Bitcoin-only multi-sig wallet screens of the Keystone 3 hardware wallet firmware. If a user entered the wrong device-unlock password while the lock screen was shown over these multi-sig views, …

UI lock-up / denial of usability on wrong passwordIncorrect routing of password verification result between overlapping viewsMissing handling for SIG_LOCK_VIEW_SCREEN_GO_HOME_PASS in password error path
2037a16aby aaron+20−02 files
No security note in commit
Open full analysis →Source commit ↗
Moderate 64 AI analysisMessage 50 · Thin
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

fix the issue of uvfk not changed if changed password

This commit fixes a bug in the Keystone 3 hardware wallet's Zcash support: when a user changed their login password, the encrypted Zcash 'unified full viewing key' (UFVK) was not re-encrypted with the new password. That meant the stored UF…

Credential/key material desynchronization after password changeZcash UFVK ciphertext keyed by login passwordAutomatic migration/recovery of stale encrypted key material
6d8e2d9dby aaron+137−464 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 40 · Thin
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

feat: modify Lace Wallet

This commit is a routine user-interface update for the Lace wallet integration. It moves the Lace wallet icon into the 'Bitcoin Wallets' submenu, removes a separate Lace entry that previously showed both Bitcoin and Cardano support, and no…

468209b6by soralit+4−81 file
No security note in commit
Open full analysis →Source commit ↗
Repository ledger

Explore captured commits

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

AI review queuedfeat: update ada export to keystoneby soralit · 9940188d · Feb 2, 2026 · 2 filesMessage 57 · ThinInformational 15Details
Commit message · soralit

feat: update ada export to keystone

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 adds Cardano (ADA) support to the Keystone wallet connection/export feature. It simply includes an additional public key path and an icon in two UI lists. There is no security-relevant change visible in the diff.

AI review queuedfeat: add ADA to keystone nexusby soralit · ff5b52d6 · Feb 2, 2026 · 2 filesMessage 57 · ThinInformational 17Details
Commit message · soralit

feat: add ADA to 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
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 17/100

This commit adds support for the Cardano (ADA) cryptocurrency to the Keystone hardware wallet's 'Keystone Connect' feature. It introduces a new derivation path and a helper function to format ADA extended public keys for wallet connection. There is no indication in the commit of a security bug or fix; it appears to be a routine feature addition.

AI review queuedfix spanish bugby ww3512687 · 65119e48 · Feb 2, 2026 · 3 filesMessage 28 · OpaqueInformational 19Details
Commit message · ww3512687

fix spanish bug

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

This commit fixes Spanish-language display issues in the wallet's user interface. It updates several Spanish translations to be shorter or clearer, and slightly increases the height of two UI containers so the longer Spanish text fits without being cut off. There is no security vulnerability here—it's purely a localization and layout bug fix.

AI review queuedbtc only language completeby ww3512687 · ecff8ede · Jan 21, 2026 · 5 filesMessage 35 · OpaqueTriage 0Details
Commit message · ww3512687

btc only language complete

35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI review queuedupdate the wallet list to support Naboxby ww3512687 · 50d0a669 · Jan 21, 2026 · 5 filesMessage 45 · ThinInformational 18Details
Commit message · ww3512687

update the wallet list to support Nabox

45/100 · ThinMessage clarity
✓ 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 18/100

This commit adds support for the Nabox wallet app in Keystone 3 firmware. It changes which cryptocurrency account data is shared with Nabox, switches the data format to a newer 'Keystone Connect' style, and exposes the device's serial number and firmware version during pairing. There is no direct evidence this is a security fix or vulnerability; it appears to be a routine wallet-integration update.

AI review queuedadd 2.3.6 changelogby bianminyan · aae1dd50 · Jan 21, 2026 · 3 filesMessage 38 · OpaqueTriage 0Details
Commit message · bianminyan

add 2.3.6 changelog

38/100 · OpaqueMessage clarity
✓ Subject identifies a change✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI review queuedfix: ci buildby soralit · 7533e107 · Jan 21, 2026 · 1 fileMessage 40 · ThinInformational 15Details
Commit message · soralit

fix: ci 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 tiny code-movement patch that shifts a variable declaration earlier in a function so the code compiles under CI. It does not change what the program does, only where a local variable is declared. There is no security relevance visible in the commit.

AI review queuedstyle: run cargo fmtby soralit · ff1edce8 · Jan 21, 2026 · 2 filesMessage 28 · OpaqueInformational 15Details
Commit message · soralit

style: run cargo fmt

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 is purely a code-formatting cleanup. It removes one debug-print logging statement and adjusts brace style to match Rust's standard formatter. There is no functional change, no bug fix, and no security-relevant behavior change.

AI review queuedfeat: hide zcash on slip39 wallet for keystoneby soralit · 2443c20a · Jan 21, 2026 · 5 filesMessage 57 · ThinInformational 19Details
Commit message · soralit

feat: hide zcash on slip39 wallet for keystone

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

This commit changes the Keystone hardware wallet firmware so that Zcash features are hidden or blocked when the wallet was created using a SLIP39 seed (a type of multi-share recovery phrase). The code now returns an 'unsupported' error for Zcash transaction checks on SLIP39 wallets and swaps in a wallet-list image that does not show Zcash. There is no evidence in the commit of a vulnerability being fixed; it reads as a product-level feature restriction.

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.

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.

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

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

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 · OpaqueTriage 0Details
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 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 · OpaqueTriage 0Details
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 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 · OpaqueTriage 0Details
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 review queuedfix cypherpunk buildby ww3512687 · 1eaf6501 · Jan 6, 2026 · 1 fileMessage 28 · OpaqueTriage 0Details
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 review queuedfix ui bugsby ww3512687 · b01d5444 · Jan 6, 2026 · 1 fileMessage 0 · OpaqueTriage 0Details
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 review queuedfixby ww3512687 · 91f8ed5e · Jan 6, 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 on-screen wallet names and a minor UI display rule. There is no security issue here—it is a cosmetic/branding update.