KS
← All projectsKeystone

Keystone 3 firmware

Open-source device firmware for Keystone 3 hardware wallets.

BitcoinHardware walletsNormal
Repository coverage

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

119security candidates294second-pass queue551AI analyses
7commits · 30 days
37commits · 60 days
279commits · 180 days
504commits · 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
72Adequate · 60–79
211Thin · 40–59
235Opaque · 0–39
39security 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.
soralit11634116248
Adam Tucker931193263
aaron30430248
Soralit959154
ww351268717652176026
willwang15215025
John Boyd626088
github-actions[bot]323076
Aaron Chen222068
Qkin-Keystone26126036
qkin12112050
Greg Pfeil414071
Analysis record

Published AI watches

Last scanned 10 minutes ago

Low 42 AI analysisMessage 58 · Thin
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

Merge pull request #2293 from KeystoneHQ/merge/v3.1.0

This is a large firmware release merge (v3.1.0) for the Keystone 3 hardware wallet. The visible changes are mostly a major FreeRTOS kernel upgrade (from v10.x to v11.3.0), build-system improvements, and user-facing feature tweaks such as b…

FreeRTOS kernel major version upgrade (10.x -> 11.3.0) with MPU hardeningSwitch from ARM_CM4F non-MPU port to ARM_CM4_MPU portNew MPU configuration flags: configTOTAL_MPU_REGIONS=8, configENFORCE_SYSTEM_CALLS_FROM_KERNEL_ONLY=1, configALLOW_UNPRIVILEGED_CRITICAL_SECTIONS=0
0c0ae467by stone+59616−26981300 files
Vendor flagged security relevance
Informational 15 AI analysisMessage 48 · Thin
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

chore: update ci (#2292)

This commit only updates a Git submodule pointer in a release-tracking file. The actual code change is a one-line pointer update from one commit hash to another in a file named 'keystone3-firmware-release'. There is no visible security-rel…

90d1c789by Soralit+1−11 file
No security note in commit
Informational 15 AI analysisMessage 40 · Thin
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

chore: update ci

This commit only updates a Git submodule pointer (keystone3-firmware-release) from one commit hash to another. No source code, build scripts, CI configuration, or security-related files are changed in the visible diff. There is no evidence…

a7f6db29by Soralit+1−11 file
No security note in commit
Moderate 58 AI analysisMessage 28 · Opaque
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

release 3.1.0

This is a large firmware release commit (version 3.1.0) for the Keystone 3 hardware wallet. The most significant change visible in the diff is a major upgrade of the FreeRTOS real-time operating system kernel from version 10.x to 11.3.0, c…

FreeRTOS major version upgrade (10.x → 11.3.0) with MPU port enabledNew MPU sandbox task/runtime/validator files addedconfigENFORCE_SYSTEM_CALLS_FROM_KERNEL_ONLY=1 and configALLOW_UNPRIVILEGED_CRITICAL_SECTIONS=0 set
2b007a29by Soralit+59615−26980300 files
Vendor flagged security relevance
Informational 15 AI analysisMessage 76 · Adequate
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

Merge release v3.0.8 (#2291)

This commit is a routine version-bump merge for release v3.0.8. It only updates changelogs, a Git submodule pointer, and a build version number. There is no code change visible in the diff and nothing that suggests a security fix or vulner…

b5e8f9fcby github-actions[bot]+18−24 files
No security note in commit
Low 47 AI analysisMessage 76 · Adequate
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

Merge release v3.0.6 (#2290)

This firmware update adds support for Solana's new V1 transaction format and changes how oversized or malformed transaction details are displayed. The code introduces a dedicated parser for V1 messages with strict size and structure checks…

New parser enforces hard limits on V1 message fields and rejects malformed 0x81-prefix payloads instead of falling back to message signingCompute-budget instructions in V1 are explicitly ignored to prevent fee-display spoofingUI pagination change for large transaction details reduces truncation risk
87b78ae1by github-actions[bot]+564−2812 files
No security note in commit
Informational 15 AI analysisMessage 68 · Adequate
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

pin to new release config (#2285)

This commit only updates a Git submodule pointer (keystone3-firmware-release) from one commit hash to another. There is no code change visible in the diff, no description of what the new release config contains, and no security-related inf…

bc01c889by Aaron Chen+1−11 file
No security note in commit
Informational 15 AI analysisMessage 68 · Adequate
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

update the release repo (#2282)

This commit simply updates a Git submodule pointer for the project's release repository. There is no visible code change, no description of any security issue, and no indication this is anything other than a routine release-tracking update.

3ac7e802by Aaron Chen+1−11 file
No security note in commit
Moderate 59 AI analysisMessage 76 · Adequate
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

Merge release v3.0.4 (#2279)

This is a routine firmware release merge (v3.0.4) for the Keystone 3 hardware wallet. The bulk of the changes are UI tweaks, new feature support (Solana CLI, Lace Wallet), and hardening fixes found during an internal 'regular AI review'. T…

NUL-byte rejection in EIP-712 typed data parsingC-string conversion hardening against NUL bytesNull-pointer and UTF-8 validation added to UR parsing entry points
6ab436a2by github-actions[bot]+4960−548845 files
No security note in commit
Informational 13 AI analysisMessage 59 · Thin
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

Build fix (#2273)

This commit is a routine build-system and code-formatting fix. It resets cached CMake build options so each build starts from known defaults, makes cbindgen header-generation failures visible instead of silently ignored, runs Rust formatti…

8568a657by stone wang+8−145 files
No security note in commit
Low 44 AI analysisMessage 36 · Opaque
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

limit file count (#2272)

This commit adds a hard cap on how many files the device will list from its SD card when loading multi-signature Bitcoin wallet data. It also tightens up null-pointer and length checks while scanning directories. The likely goal is to prev…

Unbounded directory listing now bounded by FATFS_MAX_FILE_NUMBERNull-pointer guards added for fileName, number, and path parametersLength checks added before copying filenames into caller buffers
de6879c3by stone wang+31−146 files
No security note in commit
Low 46 AI analysisMessage 73 · Adequate
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

Merge pull request #2268 from KeystoneHQ/regular-review-fix

This commit tightens which old-style Bitcoin-like transactions the Keystone hardware wallet will accept. It now rejects raw protobuf Bitcoin (BTC) and Dogecoin (DOGE) legacy UTXO transactions, allowing only Bitcoin Cash (BCH), Dash (DASH),…

Deprecation of raw-protobuf Bitcoin transaction handlingRejection of unsupported legacy UTXO variants at multiple entry pointsShift from coin_code string matching to protobuf variant matching for legacy path eligibility
1c70d3d4by Soralit+134−166 files
No security note in commit
Moderate 61 AI analysisMessage 62 · Adequate
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

fix: mark legacy utxo transaction as deprecated and disable btc legacy transactions

This commit disables the older, raw-protobuf signing path for Bitcoin and Dogecoin transactions in the Keystone 3 hardware wallet firmware. It keeps the legacy path active only for Bitcoin Cash (BCH), Dash (DASH), and Litecoin (LTC). The c…

Disables a legacy transaction parsing/signing code path for Bitcoin and DogecoinAdds explicit rejection checks before raw transaction parsing, checking, signing, and view routingSwitches discriminator from coin_code string to protobuf transaction variant to prevent spoofing
1fcd2346by Soralit+134−166 files
No security note in commit
Moderate 63 AI analysisMessage 58 · Thin
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

Merge pull request #2264 from KeystoneHQ/regular-review-fix

This firmware update is a routine 'regular review fix' that hardens how the Keystone 3 hardware wallet checks and displays several cryptocurrency transactions before signing. The most important security changes are: (1) the sign button is …

Sign slider disabled until parse success prevents premature approvalArweave DataItem tag-count mismatch now rejected in pre-checkAvalanche transaction re-validated by type in pre-check, tampered asset ID rejected
87c7e7e2by Soralit+623−20423 files
No security note in commit
Moderate 67 AI analysisMessage 58 · Thin
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

Merge pull request #2263 from KeystoneHQ/driver-optimize

This commit updates the hardware random number generator (TRNG) driver in a cryptocurrency hardware wallet firmware. It adds detection for a physical fault/attack signal from the TRNG and, if triggered, wipes the random data and aborts via…

Added TRNG fault/attack status detection (TRNG_IT_RNG0_ATTACK)Zeroization of sensitive local buffer and output buffer on TRNG failureAssertion abort on detected TRNG attack condition
a409efe0by Soralit+29−51 file
No security note in commit
Moderate 59 AI analysisMessage 18 · Opaque
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

driver optimzie

This commit updates the hardware random number generator (TRNG) driver in a cryptocurrency hardware wallet firmware. It adds detection for a physical tamper/attack signal from the TRNG chip and, if an attack is detected, wipes the random d…

New check of TRNG_IT_RNG0_ATTACK tamper/attack interrupt statusFailure path now zeroes output and local buffer before abortingAddition of ASSERT guards and secure memset_s usage
25f3d951by ww3512687+29−51 file
No security note in commit
Moderate 61 AI analysisMessage 57 · Thin
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

fix: regular ai review fix

This firmware update for the Keystone 3 hardware wallet fixes several security and safety issues found during an internal AI-assisted review. The most important changes are: (1) the signing slider is now disabled until a transaction is ful…

Signing slider disabled until parse success prevents approval of malformed transactionsArweave DataItem tag-count mismatch rejected in pre-check before confirmation pageAvalanche transaction re-validated by type during fingerprint check
edbeae79by soralit+623−20423 files
No security note in commit
High 76 AI analysisMessage 58 · Thin
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

Merge pull request #2262 from KeystoneHQ/regular-review-fix

This firmware update fixes several security and safety issues found during a regular AI-assisted code review. The most important changes are: (1) Zcash wallet data is now encrypted with a key derived from the wallet seed and a fresh random…

Zcash UFVK encryption key changed from sha256(password) to seed-derived BIP32 keyZcash UFVK IV changed from deterministic seed-derived value to fresh TRNG-generated IV per blobZcash UFVK storage format now uses magic-prefixed blob with embedded IV and rejects legacy blobs
04d942ffby Soralit+1852−52633 files
No security note in commit
High 80 AI analysisMessage 57 · Thin
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

fix: regular AI review and fix

This firmware update fixes several security and safety issues found during an internal AI-assisted review. The most important changes are: (1) Zcash wallet data was being encrypted with a key derived from the user's login password and a fi…

Zcash UFVK encryption key changed from sha256(login password) to seed-derived BIP32 keyZcash UFVK IV changed from deterministic seed-derived value to fresh TRNG-generated IV per encryptionNew 'z2' UFVK blob format stores IV with ciphertext; legacy blobs rejected/migrated
776d8832by soralit+1852−52633 files
Vendor flagged security relevance
Moderate 59 AI analysisMessage 58 · Thin
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

Merge pull request #2260 from KeystoneHQ/replace-lvgl-rand

This commit replaces the on-screen keyboard shuffle and a word-list randomizer so they use the device's true random-number generator (TRNG) instead of LVGL's weaker pseudo-random function. The change is defensive: it removes a source of pr…

Replaced pseudo-random generator with hardware TRNG in security-sensitive shuffle operationsRemoved fixed-range modulo reduction bias source (`lv_rand(0, 2048) % n`)Changed include from LVGL UI library to device TRNG driver in utility code
230abd77by Soralit+8−32 files
No security note in commit
Repository ledger

Explore captured commits

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

AI review queuedadd mfp checkby 0xApprentice · 8726a2bd · Sep 28, 2025 · 4 filesMessage 28 · OpaqueModerate 57Details
Commit message · 0xApprentice

add mfp check

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 · Moderate 57/100

This commit removes a line that made a Bitcoin PSBT (Partially Signed Bitcoin Transaction) safety check always return success before doing any real verification. The title says 'add mfp check' (master fingerprint check), but the actual code change mostly re-enables an existing check that had been short-circuited. A master fingerprint check helps ensure the transaction was built for this specific hardware wallet, reducing the risk of signing a transaction meant for someone else's wallet. The commit also contains unrelated build and simulator tweaks.

AI review queuedrun font scriptby ww3512687 · 4e2c80d1 · Sep 26, 2025 · 4 filesMessage 28 · OpaqueInformational 15Details
Commit message · ww3512687

run font script

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 is a routine localization and font update. It adds one Chinese character (盘) to the Chinese font file, removes three Chinese characters from the Russian font symbol list, and updates translations for the 'Randomized PIN Pad' setting across multiple languages. There is no code behavior change, no security fix, and no vulnerability introduced.

Security candidatesupport random pin pad switchby ww3512687 · 4a7ed763 · Sep 24, 2025 · 17 filesMessage 50 · ThinInformational 20Details
Commit message · ww3512687

support random pin pad switch

50/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Names security-relevant behavior explicitly! No meaningful explanatory body
Why it was queued
access control
AI analysis · Informational 20/100

This commit adds a user-facing option to scramble the numeric PIN keypad layout on the Keystone 3 hardware wallet. When enabled, the digits appear in a random order each time, making it harder for someone watching or filming the screen to guess the PIN from finger positions. It is a security-hardening feature, not a fix for an active vulnerability, and it is off by default.

AI review queuedUpdate version for testby bianminyan · d3f5365f · Sep 23, 2025 · 1 fileMessage 38 · OpaqueInformational 15Details
Commit message · bianminyan

Update version for test

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

This commit only changes one number in a version header file, bumping the build version from 10 to 14. It does not modify any actual code, features, or security behavior. There is no security issue here.

Security candidateEnhance multi-signature address functionality by adding support for sorting public keys and creating multi-sig addresses for Dogecoin. Update DOGEAddressEncoding to include P2SH prefix and implement corresponding formatting. Modify address creation methods to accommodate new features.by ww3512687 · 379234b8 · Sep 23, 2025 · 4 filesMessage 55 · ThinLow 26Details
Commit message · ww3512687

Enhance multi-signature address functionality by adding support for sorting public keys and creating multi-sig addresses for Dogecoin. Update DOGEAddressEncoding to include P2SH prefix and implement corresponding formatting. Modify address creation methods to accommodate new features.

55/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Names security-relevant behavior explicitly! No meaningful explanatory body
Why it was queued
signing boundary
AI analysis · Low 26/100

This commit adds Dogecoin support for multi-signature wallet addresses in a hardware wallet firmware. It lets the device create Dogecoin multi-sig addresses and sort public keys before building the address. There is also a trivial whitespace change in a UI file. The changes look like normal feature work, but adding new address handling always carries a small risk of address-generation mistakes that could make funds hard or impossible to spend.

AI review queuedupdate cargo.tomlby ww3512687 · e560760e · Sep 22, 2025 · 2 filesMessage 28 · OpaqueInformational 15Details
Commit message · ww3512687

update cargo.toml

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 only changes how two internal Rust libraries are sourced in the project's build configuration. It switches from using local file paths on a developer's Windows machine (C:/3.git/...) to pulling the same libraries from a specific Git branch in the vendor's public repository. There is no code behavior change visible in this commit, and nothing in the commit message or diff indicates a security fix or vulnerability.

AI review queuedfix bugsby ww3512687 · b24dac9d · Sep 22, 2025 · 2 filesMessage 0 · OpaqueLow 45Details
Commit message · ww3512687

fix bugs

0/100 · OpaqueMessage clarity
! Very short 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 · Low 45/100

This commit fixes two bugs in the Bitcoin PSBT (Partially Signed Bitcoin Transaction) handling code of a hardware wallet firmware. One fix corrects the order of arguments passed between C and Rust code so they match the expected function signature. The other fix moves the array-size assignment to happen before the array is populated, ensuring all nine public keys are properly registered instead of only the first four. These are likely functional bugs that could cause transaction parsing or signing to fail or behave incorrectly, but the diff alone does not prove a direct theft-of-funds vulnerability.

Security candidatesupport psbtby ww3512687 · f3dbd61e · Sep 19, 2025 · 13 filesMessage 18 · OpaqueLow 46Details
Commit message · ww3512687

support psbt

18/100 · OpaqueMessage clarity
✓ Subject identifies a change! Too few words to establish purpose! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
signing boundarysigning or wallet path
AI analysis · Low 46/100

This commit adds support for signing extended PSBTs for several UTXO-based coins (Litecoin, Dogecoin, Dash, Bitcoin Cash) in the Keystone 3 hardware wallet firmware. It also contains several changes that look like temporary debug or development shortcuts rather than production-hardened code: a hardcoded return value that hides the real battery percentage, disabling a boot-version mismatch warning, sending real UART output in production builds, and pointing Rust dependencies to a local path on a developer's Windows machine. These shortcuts reduce the device's defensive posture but are not, by themselves, a remote exploit.

AI review queuedmodify changelogby bianminyan · 1bf44d9f · Sep 18, 2025 · 2 filesMessage 18 · OpaqueInformational 15Details
Commit message · bianminyan

modify changelog

18/100 · OpaqueMessage clarity
✓ Subject identifies a change! Too few words to establish purpose! No meaningful explanatory body
Why it was queued
documentation-only discountsecond-pass: opaque commit message
AI analysis · Informational 15/100

This commit only edits wording and spacing in two changelog files. No code, configuration, or security behavior is changed. It is a documentation-only formatting cleanup.

AI review queuedadd 2.2.14 changelogby bianminyan · 27c4dc89 · Sep 18, 2025 · 2 filesMessage 38 · OpaqueInformational 15Details
Commit message · bianminyan

add 2.2.14 changelog

38/100 · OpaqueMessage clarity
✓ Subject identifies a change✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
documentation-only discountsecond-pass: opaque commit message
AI analysis · Informational 15/100

This commit only adds a new section to the English and Chinese changelogs for firmware version 2.2.14. It describes new features (BSC transfers/swaps, randomized PIN input, IOTA Wallet support) and one bug fix (certain ADA transaction signing causing device restarts). No source code is changed, so the commit itself does not introduce, fix, or alter any security behavior.

AI review queuedupdate wallet iconby ww3512687 · 9b5f0900 · Sep 17, 2025 · 5 filesMessage 28 · OpaqueInformational 15Details
Commit message · ww3512687

update wallet icon

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 simply swaps the Petra wallet icon graphics for new versions. It changes two PNG image files and their corresponding generated C source files, plus updates a hash file used to track those assets. There is no code logic change, no security fix, and no indication this addresses a vulnerability.

AI review queuedUpdate versionby bianminyan · 2afa3902 · Sep 17, 2025 · 1 fileMessage 18 · OpaqueInformational 15Details
Commit message · bianminyan

Update version

18/100 · OpaqueMessage clarity
✓ Subject identifies a change! Too few words to establish purpose! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100

This commit only increments a software build number from 13 to 14 in a version header file. There are no code changes, no bug fixes, and no security-related modifications visible in the diff.

AI review queuediota wallet ui bugsby ww3512687 · 24d520b6 · Sep 16, 2025 · 3 filesMessage 28 · OpaqueInformational 15Details
Commit message · ww3512687

iota wallet ui bugs

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 fixes minor user-interface issues for the IOTA wallet in the Keystone 3 hardware firmware. It renames the displayed label from 'IOTA' to 'IOTA Wallet', adds a tutorial entry with a help link, and moves the IOTA wallet entry to a different position in the wallet list. There is no security-relevant change visible in the code.

Lower-priorityfix: memory issueby soralit · 09e73d60 · Sep 16, 2025 · 1 fileMessage 40 · ThinLow 42Details
Commit message · soralit

fix: memory issue

40/100 · ThinMessage clarity
✓ Subject identifies a change✓ Uses a recognizable type or scope! No meaningful explanatory body
AI analysis · Low 42/100

This commit fixes a coding mistake in the Ethereum batch transaction screen. The code was allocating memory for a token symbol, then accidentally assigning the result of a safe string-copy function back to the same pointer. On success, that function returns the destination pointer, so the bug is mostly harmless, but it makes the code confusing and could hide problems if the copy fails. The fix removes the redundant assignment so the pointer keeps the originally allocated memory address.

Lower-priorityfix: chain coin display errorby soralit · d908e40f · Sep 15, 2025 · 1 fileMessage 57 · ThinLow 32Details
Commit message · soralit

fix: chain coin display error

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

This commit fixes a UI bug in the Ethereum batch transaction screen where the wrong memory buffer was being used to store a network symbol name. Before the fix, the code allocated memory for the symbol but then wrote the symbol into a buffer sized by a different function argument, which could lead to a crash or corrupted display text when showing swap details. The fix makes the destination buffer the same one that was just allocated, matching its size.

Lower-priorityfeat: add bsc thorchain contractsby soralit · 92339df3 · Sep 15, 2025 · 2 filesMessage 57 · ThinInformational 16Details
Commit message · soralit

feat: add bsc thorchain contracts

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

This commit adds two new BNB Smart Chain (BSC) THORChain router contract definitions to the wallet's built-in list of known smart contracts, and makes a small, safe-looking code change so the swap screen can display the correct network symbol (e.g., BNB) instead of hard-coding 'ETH'. There is no obvious security vulnerability in the diff itself; it appears to be a routine feature addition to support more cross-chain swaps.

AI review queuedsupport iota walletby ww3512687 · 3806ad42 · Sep 15, 2025 · 7 filesMessage 28 · OpaqueInformational 15Details
Commit message · ww3512687

support iota wallet

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 support for the IOTA wallet in the Keystone 3 firmware. It is a routine feature addition: a new wallet icon is included, the wallet is added to the status bar and connect-wallet lists, and the firmware build number is bumped. There is no indication of a security fix or vulnerability.

AI review queuedUpdate version for beta_testby bianminyan · fe25cc1a · Sep 15, 2025 · 1 fileMessage 35 · OpaqueInformational 15Details
Commit message · bianminyan

Update version for beta_test

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

This commit simply bumps a build number in a version header from 9 to 13 for a beta test. It does not change any executable logic, fix any bug, or alter any security behavior. There is no security relevance visible in the change itself.

Lower-priorityfeat: add bsc thorchain contractsby soralit · 75a0c4fb · Sep 12, 2025 · 1 fileMessage 57 · ThinInformational 15Details
Commit message · soralit

feat: add bsc thorchain contracts

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 adds two known THORChain Router smart contract definitions for the BNB Smart Chain (BSC) network to a lookup table used by the wallet's user interface. It is a routine data update with no visible security defect.

AI review queuedfix ada crashby 0xApprentice · 8ce06467 · Sep 10, 2025 · 1 fileMessage 28 · OpaqueLow 35Details
Commit message · 0xApprentice

fix ada crash

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

This commit increases the memory stack size for a task that handles sensitive data, with the stated goal of fixing a crash related to Cardano (ADA). A too-small stack can cause memory corruption or a device crash when handling certain operations. While the change itself is defensive, the crash occurs in a security-sensitive task, so it could theoretically affect availability or stability during sensitive operations. There is no direct evidence in the commit that this is exploitable for theft or key extraction.

AI review queuedfix: buildby soralit · 5965959d · Sep 10, 2025 · 2 filesMessage 2 · OpaqueInformational 15Details
Commit message · soralit

fix: build

2/100 · OpaqueMessage clarity
✓ Uses a recognizable type or scope! Very short subject! Too few words to establish purpose! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100

This commit is a routine build fix. It updates a cached image hash file and adds a missing function declaration inside a conditional compile block for a Web3-specific version. There is no visible security relevance.

AI review queuedDisordered keyboardby willwang · 7f1be015 · Sep 5, 2025 · 5 filesMessage 18 · OpaqueModerate 50Details
Commit message · willwang

Disordered keyboard

18/100 · OpaqueMessage clarity
✓ Subject identifies a change! Too few words to establish purpose! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Moderate 50/100

This commit adds a feature that shuffles the on-screen numeric keypad layout each time the device lock screen appears. The goal is to make it harder for someone watching or recording your screen to figure out your PIN based on where your fingers tap. The change itself is a security improvement, not a vulnerability fix, but the commit message is vague and gives no explanation.

AI review queuedupdate hardware version displayby willwang · 841e50ad · Sep 4, 2025 · 1 fileMessage 35 · OpaqueInformational 15Details
Commit message · willwang

update hardware version display

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

This commit simply changes two user-facing text labels from 'Version 3.0' and 'Version 3.1' to 'V3.0' and 'V3.1'. It is a cosmetic string formatting update with no security relevance.

AI review queuedadd 2.2.12 changelogby bianminyan · 695095a4 · Sep 4, 2025 · 2 filesMessage 38 · OpaqueInformational 15Details
Commit message · bianminyan

add 2.2.12 changelog

38/100 · OpaqueMessage clarity
✓ Subject identifies a change✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
documentation-only discountsecond-pass: opaque commit message
AI analysis · Informational 15/100

This commit only adds release notes for firmware version 2.2.12. It does not change any executable code, configuration, or security controls. The changelog mentions a bug fix for Cardano passphrase message signing, but the commit itself contains only documentation updates.

AI review queuedDisordered keyboardby willwang · 9b13b0cc · Sep 3, 2025 · 1 fileMessage 18 · OpaqueLow 42Details
Commit message · willwang

Disordered keyboard

18/100 · OpaqueMessage clarity
✓ Subject identifies a change! Too few words to establish purpose! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Low 42/100

This commit adds a shuffled numeric keypad for PIN entry on a hardware wallet. Instead of always showing 0-9 in the same order, the digits now appear in a random order each time. This is a defensive measure to make it harder for someone watching or recording the screen to learn your PIN based on where you tap.