Keystone 3 firmware

Open-source device firmware for Keystone 3 hardware wallets.

BitcoinHardware walletsNormal

Repository coverage

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

111security candidates287second-pass queue418AI analyses

117commits · 30 days

159commits · 60 days

276commits · 180 days

535commits · 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

204Thin · 40–59

233Opaque · 0–39

38security 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 Tucker931156163

aaron30413148

ww351268717652165026

soralit1153477048

willwang15214025

John Boyd624088

Soralit321058

Qkin-Keystone26123036

qkin12111050

Greg Pfeil412071

Daira-Emma Hopwood211085

bianminyan45042032

Analysis record

Published AI watches

Last scanned 48 minutes ago

Moderate 59 AI analysisMessage 58 · Thin

1 day, 15 hours ago

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

Open full analysis →Source commit ↗

Moderate 59 AI analysisMessage 28 · Opaque

1 day, 15 hours ago

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

2 days, 7 hours ago

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 ↗

Moderate 62 AI analysisMessage 57 · Thin

2 days, 7 hours ago

KS KeystoneKeystone 3 firmware BitcoinHardware wallets

fix: improve Solana message handling

This commit hardens how Keystone 3 handles Solana signing requests. Previously, the device partly trusted an external 'sign type' flag from the wallet app to decide whether a QR code contained a transaction or a plain message. The patch no…

Replaces trust in external sign-type metadata with byte-level payload classificationRejects malformed transactions that contain a valid transaction prefix followed by hidden trailing dataPrevents a transaction from being displayed and signed as a plain message

756df0e7by soralit+151−387 files

No security note in commit

Open full analysis →Source commit ↗

Low 49 AI analysisMessage 57 · Thin

2 days, 8 hours ago

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

2 days, 9 hours ago

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

2 days, 9 hours ago

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 19 AI analysisMessage 57 · Thin

6 days, 8 hours ago

KS KeystoneKeystone 3 firmware BitcoinHardware wallets

feat: rename matic to pol

This commit simply renames the cryptocurrency token symbol from MATIC to POL in two places in the user-interface code for the Keystone 3 hardware wallet. Polygon officially rebranded its native token from MATIC to POL, so this is a routine…

88132d72by soralit+2−21 file

No security note in commit

Open full analysis →Source commit ↗

Informational 10 AI analysisMessage 40 · Thin

6 days, 8 hours ago

KS KeystoneKeystone 3 firmware BitcoinHardware wallets

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

1 week, 3 days ago

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 15 AI analysisMessage 40 · Thin

1 week, 6 days ago

KS KeystoneKeystone 3 firmware BitcoinHardware wallets

chore: update change log

This commit only edits the project's changelog text. It rewrites the release notes for version 3.0.2, removing detailed bug-fix descriptions and replacing them with a shorter note about Zcash Ironwood support. No source code, build scripts…

c224a7f5by soralit+12−232 files

No security note in commit

Open full analysis →Source commit ↗

Informational 15 AI analysisMessage 40 · Thin

1 week, 6 days ago

KS KeystoneKeystone 3 firmware BitcoinHardware wallets

chore: bump version

This commit only changes two version numbers in a header file: the build number is increased from 1 to 2, and the beta flag is turned off (set to 0). There is no code change, no bug fix, and no security-related content in the diff or commi…

62a5d952by soralit+2−21 file

No security note in commit

Open full analysis →Source commit ↗

Low 37 AI analysisMessage 45 · Thin

1 week, 6 days ago

KS KeystoneKeystone 3 firmware BitcoinHardware wallets

Fix Zcash wallet preparation on unlock

This commit fixes a bug in a helper function that checks whether a text string is a valid hexadecimal value of the expected length. The changelog frames the user-visible fix as 'preventing Zcash public information from being regenerated on…

Input validation hardening in a shared utility functionChangelog describes a Zcash wallet preparation/unlock behavior fixPotential off-by-one length check corrected

dd034199by Adam Tucker+8−44 files

No security note in commit

Open full analysis →Source commit ↗

Informational 3 AI analysisMessage 45 · Thin

2 weeks ago

KS KeystoneKeystone 3 firmware BitcoinHardware wallets

Use released UR crates 1.0.8

This commit simply switches two software building blocks (called 'crates') from a development Git snapshot to a published release version (1.0.8) on the official Rust package registry. The change itself does not add, remove, or modify any …

fa0add39by Adam Tucker+8−102 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 queuedmodify changelogby bianminyan · dc3a3b28 · Aug 14, 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 two changelog files, removing a line that said a WebUSB upgrade issue was fixed. No actual code, firmware logic, or security behavior is changed. It is a documentation-only edit.

AI review queuedmodify changelogby bianminyan · a7307b6e · Aug 14, 2025 · 1 fileMessage 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 changes a version number and date in a Chinese-language changelog file. It does not modify any code, configuration, or security-related content. There is no security issue to report.

AI review queuedadd 2.2.8 changelogby bianminyan · 691ae4dd · Aug 14, 2025 · 2 filesMessage 38 · OpaqueInformational 15Details

Commit message · bianminyan

add 2.2.8 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 two changelog files describing version 2.2.8. It lists two bug fixes in plain language: one about custom path signing and one about WebUSB upgrade failures. No source code, configuration, or executable files were changed. The changelog entry itself does not describe any security issue, and there is no diff evidence of a vulnerability being introduced or fixed.

AI review queuedUpdate versionby bianminyan · c8425d44 · Aug 14, 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 simply bumps a build number in a version header file from 6 to 8. There are no code changes, no bug fixes, and no security-related modifications visible in the diff.

AI review queuedsupport custom pathby willwang · 800f53db · Aug 14, 2025 · 20 filesMessage 28 · OpaqueLow 35Details

Commit message · willwang

support custom path

28/100 · OpaqueMessage clarity

✓ Subject identifies a change! No meaningful explanatory body

Why it was queued

second-pass: opaque commit messagesecond-pass: unusually broad change

AI analysis · Low 35/100

This commit adds support for 'custom derivation paths' in the Keystone 3 hardware wallet firmware. In plain terms, it lets users sign transactions or messages even when the wallet cannot derive the sender's address from its own keys, by making the 'from' address optional in the display and parsing logic. The change touches Ethereum, Solana, and Cardano code, plus UI layout and translations. It is a feature addition rather than a clear security fix, but it changes how the device validates and presents the signing identity, which could affect user trust and transaction safety if not handled carefully.

AI review queuedfix raw data wake upby ww3512687 · 7416073b · Aug 13, 2025 · 1 fileMessage 38 · OpaqueLow 29Details

Commit message · ww3512687

fix raw data wake up

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 analysis · Low 29/100

This commit fixes a user-interface behavior on a cryptocurrency hardware wallet. When a user views the raw data of an Ethereum transaction, the device now temporarily prevents the screen from locking. Without the fix, the screen could lock while the user was reading the raw data, which could be annoying or cause the user to approve a transaction without fully reviewing it. The change itself is small and defensive, not a clear-cut security vulnerability fix.

AI review queuedmodify changelogby bianminyan · f822f5b9 · Aug 8, 2025 · 1 fileMessage 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 the wording of a changelog file. It changes a Chinese heading 'Bug 修复' to the English heading 'Bug Fixes' and adds a blank line. No code, firmware logic, or security behavior is modified.

AI review queuedadd 2.2.6 changelogby bianminyan · a2f49d6f · Aug 8, 2025 · 2 filesMessage 38 · OpaqueInformational 15Details

Commit message · bianminyan

add 2.2.6 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 text to two changelog files describing a new firmware version (2.2.6). It does not change any code, so it cannot introduce or fix a security vulnerability by itself. The changelog mentions routine feature updates and one bug fix for an unexpected sleep issue after signing Zcash transactions, but no security relevance is stated.

AI review queuedfeat(wallet): add IOTA chain type to check_hardware_call_path()by Thoralf-M · d6678c20 · Aug 7, 2025 · 1 fileMessage 62 · AdequateInformational 18Details

Commit message · Thoralf-M

feat(wallet): add IOTA chain type to check_hardware_call_path()

62/100 · AdequateMessage clarity

✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body

Why it was queued

signing or wallet pathsecond-pass: security-sensitive path

AI analysis · Informational 18/100

This commit adds support for the IOTA cryptocurrency to a function that checks whether a requested wallet operation matches a known, safe derivation path. It is a routine feature addition that maps the ticker 'IOTA' to the standard IOTA BIP-44 path 'm/44'/4218''. There is no direct evidence in the commit that this fixes a security vulnerability; it simply extends an allow-list to cover another chain.

AI review queuedfix scan ui bugby ww3512687 · fc85335e · Aug 7, 2025 · 1 fileMessage 28 · OpaqueInformational 11Details

Commit message · ww3512687

fix scan ui bug

28/100 · OpaqueMessage clarity

✓ Subject identifies a change! No meaningful explanatory body

Why it was queued

second-pass: opaque commit message

AI analysis · Informational 11/100

This commit adds a small 100-millisecond delay before checking Zcash transactions when a special 'Cypherpunk' firmware build is active. The stated purpose is to fix a scan-related user-interface bug. There is no direct evidence in the commit that this is a security fix; it appears to be a UI timing workaround.

AI review queuedUpdate versionby bianminyan · 9a7a438c · Aug 6, 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 changes one number in a version header, bumping the firmware build version from 4 to 6. There is no code behavior change, no bug fix, and no security-related content visible in the diff.