KS
← All projectsKeystone

Keystone 3 firmware

Open-source device firmware for Keystone 3 hardware wallets.

BitcoinHardware walletsNormal
Repository coverage

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

125security candidates296second-pass queue559AI analyses
5commits · 30 days
9commits · 60 days
185commits · 180 days
402commits · 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.

43/100 average clarity
39Strong · 80–100
75Adequate · 60–79
213Thin · 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
Soralit11711154
ww351268717652176026
github-actions[bot]656074
willwang15215025
John Boyd626088
Aaron Chen222068
Qkin-Keystone26126036
qkin12112050
Greg Pfeil616074
Analysis record

Published AI watches

Last scanned 37 minutes ago

Moderate 56 AI analysisMessage 81 · Strong
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

Stop the wallet-prep countdown when its label goes (#2324)

This commit fixes a firmware crash and a timer-doubling bug in a cryptocurrency hardware wallet. If a user scanned a transaction too quickly after unlocking, a countdown timer could keep running after its on-screen label was destroyed, cau…

Use-after-free/dangling reference in UI timer callbackOrphaned timer leak causing accelerated countdown behaviorFirmware crash triggered by user timing (quick unlock → scan)
7da0b941by Greg Pfeil+0−00 files
No security note in commit
Informational 15 AI analysisMessage 100 · Strong
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

fix(zcash): Fix regression in 3.2.2, improve performance by 15-18%, reduce firmware size by 4.4% (#2330)

This commit updates a Zcash cryptography dependency and changes compiler hints to fix a firmware performance regression and reduce firmware size. There is no security-relevant change visible in the diff.

36859d27by Jack Grigg+4−22 files
No security note in commit
Low 28 AI analysisMessage 81 · Strong
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

Send the whole `g_checkResult` to the UI task (#2323)

A firmware fix for a data-passing bug between internal tasks. The code was accidentally sending only the memory address size of a result structure, not the full result. Right now this only affects the rarely-used error_message field, but i…

Incorrect size passed in inter-task message (sizeof pointer instead of sizeof structure)Structure member truncation could leak partial or stale data to UI taskCrash observed by developer when accessing the omitted error_message field
6f0fb82bby Greg Pfeil+0−00 files
No security note in commit
Low 45 AI analysisMessage 61 · Adequate
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

release 3.2.2 (#2327)

This is a routine firmware release (version 3.2.2) for the Keystone 3 hardware wallet. The main user-visible change is adding support for the Zcash NU7 network upgrade. The code changes mostly update Zcash-related Rust libraries to newer v…

Zcash dependency major-version upgrades and API migration for NU7 compatibilityLock-screen countdown timer now initialized to NULL and explicitly stopped on label deletion, reducing dangling-timer riskTransaction-check-fail signal fixed to pass correct struct size instead of pointer size
08150faeby github-actions[bot]+1032−90129 files
No security note in commit
Informational 19 AI analysisMessage 65 · Adequate
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

chore(release): 3.2.0 (#2315)

This commit is a routine version-bump release (3.2.0) for the Keystone 3 firmware. The visible changes are almost entirely code formatting/indentation, removal of unused imports and dead code, adding 'deprecated' annotations to legacy Bitc…

No security-relevant signals detected in the diff.No mention of CVE, security fix, vulnerability, audit, or bug bounty in commit message or changelog.Changes are cosmetic, dead-code removal, feature gating, and version bump.
3690bf1fby Soralit+674−51576 files
No security note in commit
Moderate 61 AI analysisMessage 80 · Strong
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

chore: release 3.1.4 (#2311)

This is a large routine firmware release (version 3.1.4) for the Keystone 3 hardware wallet. The visible changes add support for signing Bitcoin Cash, Dash and Dogecoin PSBTs, improve Solana and Tron transaction parsing, add Zcash shielded…

FreeRTOS MPU peripheral region narrowed to PSRAM-only and unprivileged peripheral access now disallowed by compile-time errorNew PSBT signing paths for BCH/DASH/DOGE with custom validation and sighash rulesSolana parser changes and addition of an overflow test fixture (squads-overflow.hex)
d2987b99by github-actions[bot]+18413−6376240 files
No security note in commit
Informational 23 AI analysisMessage 76 · Adequate
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

Merge release v3.1.2 (#2306)

This is a routine firmware release merge (version 3.1.2). The only functional code change visible in the diff adds one more allowed cryptocurrency derivation path prefix, 'm/44'/9000'', for Avalanche (AVAX) X/P-chain addresses when the dev…

Additive change to a path-prefix allowlistNo input validation, parsing, or memory-safety changes visibleNo vendor statement of security relevance in commit or references
f95101fbby github-actions[bot]+23−25 files
No security note in commit
Informational 15 AI analysisMessage 48 · Thin
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

chore: update ci (#2302)

This commit only updates a Git submodule pointer (a reference to another repository) in a release-related file. There are no code changes visible in the diff, no description of any security issue, and no references provided. It appears to …

6ef9ddd3by Soralit+1−11 file
No security note in commit
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
Repository ledger

Explore captured commits

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

Security candidatefix buildby ww3512687 · 5c6b0014 · Apr 24, 2026 · 1 fileMessage 0 · OpaqueInformational 15Details
Commit message · ww3512687

fix build

0/100 · OpaqueMessage clarity
! Very short subject! Too few words to establish purpose! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
boot or update path
AI analysis · Informational 15/100

This commit is a straightforward build fix for a firmware configuration file. It adds conditional preprocessor definitions so that different product build variants (Web3, BTC-only, Cypherpunk) each define a required constant, LEGACY_USB_PAD_LEN, with values of either 1 or 2. Without this change, some build configurations would fail because the constant was missing. There is no security-relevant change in behavior visible in the diff.

Lower-priorityfix: btc multisig styleby soralit · 3ae41290 · Apr 23, 2026 · 1 fileMessage 40 · ThinInformational 15Details
Commit message · soralit

fix: btc multisig style

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

This commit is a visual layout fix for the Bitcoin multi-signature transaction screen. It changes how a 'signing status' box is positioned so it appears below the previous element instead of always starting at the top-left corner. There is no security-relevant change.

Security candidatefix buildby ww3512687 · 6917368e · Apr 23, 2026 · 1 fileMessage 0 · OpaqueInformational 15Details
Commit message · ww3512687

fix build

0/100 · OpaqueMessage clarity
! Very short subject! Too few words to establish purpose! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
boot or update path
AI analysis · Informational 15/100

This is a one-line build fix that changes a default padding length constant from 1 to 2 in a legacy USB web-update feature. There is no indication of a security problem, and the change itself does not introduce or fix any vulnerability visible in the diff.

Lower-priorityfix avax from error message displayby ww3512687 · 13033fe4 · Apr 23, 2026 · 1 fileMessage 45 · ThinInformational 18Details
Commit message · ww3512687

fix avax from error message display

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI analysis · Informational 18/100

This commit fixes a simple UI bug in the Avalanche (AVAX) transaction review screen. The code was accidentally passing the recipient's address length where the sender's address length should go, which could cause the sender's address to be displayed incorrectly or truncated on the hardware wallet screen. It does not appear to affect transaction signing logic or funds security.

Lower-prioritydocs: update changelog for v2.4.2by bianminyan · 88104548 · Apr 21, 2026 · 2 filesMessage 57 · ThinInformational 15Details
Commit message · bianminyan

docs: update changelog for v2.4.2

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
AI analysis · Informational 15/100

This commit only updates the project's changelog documents (in English and Chinese) to describe features and improvements included in firmware version 2.4.2. No source code, configuration, or executable files were changed. There is no security-relevant code modification to review.

Lower-priorityfix: zcash checksby soralit · c619fa58 · Apr 21, 2026 · 2 filesMessage 40 · ThinModerate 67Details
Commit message · soralit

fix: zcash checks

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

This commit fixes a missing security check in the Zcash PCZT (Partially Created Zcash Transaction) verifier for the Keystone 3 hardware wallet. Previously, when a transaction output could be decrypted with an internal outgoing viewing key (a key meant for change/internal addresses), the code did not verify that the output actually belonged to the wallet. This could allow a maliciously crafted transaction to trick the wallet into accepting an external output as if it were internal/change. The patch now checks that any output recoverable with an internal OVK is actually a wallet-owned Orchard address, and also considers the transparent internal OVK. The commit message is just 'fix: zcash checks' and does not disclose this as a security issue.

Lower-prioritychore: bump version to 2.4.2by bianminyan · d7791c39 · Apr 21, 2026 · 1 fileMessage 57 · ThinInformational 15Details
Commit message · bianminyan

chore: bump version to 2.4.2

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 only changes a single version number in a header file, bumping the firmware build version from 2.4.0 to 2.4.2. There are no code changes, no bug fixes, and no security-related content in the diff.

AI review queuedfeat(zcash): use raw firmware version in ZcashAccounts pairing QRby Adam Tucker · e9d96460 · Apr 16, 2026 · 1 fileMessage 85 · StrongInformational 19Details
Commit message · Adam Tucker

feat(zcash): use raw firmware version in ZcashAccounts pairing QR

Switch from GetSoftWareVersionNumber() (display major, flavor suffix) to
the raw [MAJOR, MINOR, BUILD] formatted inline, so the pairing string
matches the byte-level stamp produced by the PCZT signer. Wallets can
now use a single minimum-version constant for both checks.

85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 19/100

This commit changes how the Keystone hardware wallet reports its firmware version when pairing with Zcash wallets. Previously it used a function that returned a display-formatted version string (with a flavor suffix). Now it formats the raw major/minor/build numbers directly. The goal is to make the pairing QR code's version string match the version bytes stamped by the PCZT signer, so wallets can use one consistent minimum-version check. There is no direct security vulnerability in the diff itself; it is a compatibility/consistency fix.

Lower-priorityfix: don't translate keywordby soralit · 44fd1676 · Apr 16, 2026 · 3 filesMessage 57 · ThinInformational 19Details
Commit message · soralit

fix: don't translate keyword

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

This commit changes several Bitcoin-related user-interface labels from translated text to fixed English strings. It removes translation entries for technical terms like 'Outpoint', 'Input Reference', 'Unknown', 'Input Ref', and 'Sighash' so they always display in English regardless of the user's language setting. This is a localization/usability fix, not a security patch.

Lower-priorityfix: ui styleby soralit · a925605d · Apr 16, 2026 · 4 filesMessage 40 · ThinInformational 15Details
Commit message · soralit

fix: ui style

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

This commit is a user-interface styling fix. It adds a more compact QR-code popup layout, switches one Bitcoin screen to use that compact layout, tweaks a label font style, and comments out a simulator-only macro. There is no indication of any security bug being fixed.

AI review queuedfix avax parseby ww3512687 · 576282c3 · Apr 16, 2026 · 3 filesMessage 28 · OpaqueLow 42Details
Commit message · ww3512687

fix avax parse

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

This commit fixes how Keystone 3 hardware wallets parse Avalanche (AVAX) transactions. Previously, the code only handled a single derivation path and a single sender address. The update supports multiple input addresses/paths, correctly matches displayed 'from' addresses to their derivation paths, and fixes a UI layout and memory cleanup issue. The main security risk is that a malformed or multi-input AVAX transaction could have been displayed misleadingly, potentially tricking a user into approving a transaction they did not intend to sign.

AI review queuedfont scriptsby ww3512687 · 81db0727 · Apr 14, 2026 · 13 filesMessage 18 · OpaqueInformational 15Details
Commit message · ww3512687

font scripts

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 is a routine regeneration of font glyph data for the device's user interface. It removes a few unused Chinese characters from the symbol lists and updates the corresponding bitmap tables and translation data. There is no indication of any security fix or vulnerability being addressed.

AI review queuedfix warningby ww3512687 · eb771ee3 · Apr 14, 2026 · 1 fileMessage 0 · OpaqueInformational 17Details
Commit message · ww3512687

fix warning

0/100 · OpaqueMessage clarity
! 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 17/100

This is a one-line type-name correction in the Avalanche (AVAX) transaction display code. The developer changed a variable declaration from a TON (Telegram Open Network) transaction result type to the correct AVAX transaction result type. It appears to fix only a compiler warning and has no visible functional effect, because the underlying pointer types are likely identical in memory layout.

AI review queuedfix merge conflict bugby Qkin-Keystone · 333badc3 · Apr 14, 2026 · 1 fileMessage 28 · OpaqueLow 25Details
Commit message · Qkin-Keystone

fix merge conflict bug

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

This commit fixes a merge conflict in a firmware file for the Keystone 3 hardware wallet. The change adds a missing memory cleanup function (FreeTrxMemory) and restores a missing user-interface entry for TRX swap transactions. Without the cleanup function, memory used during transaction review might not be released, which could contribute to memory leaks or instability over time. The missing UI entry could have caused the TRX swap screen to be absent or misaligned. There is no direct evidence in the commit of an exploitable security vulnerability such as theft of funds or bypass of confirmation.

AI review queuedadd expiration for warpped tron instanceby Qkin-Keystone · 3f277a90 · Apr 14, 2026 · 1 fileMessage 45 · ThinInformational 11Details
Commit message · Qkin-Keystone

add expiration for warpped tron instance

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

This commit adds a new 'expiration' field to a Tron transaction data structure used inside the Keystone hardware wallet firmware. The change only initializes the field to an empty string in a few places and does not, by itself, appear to fix or introduce any security vulnerability. It looks like a routine data-structure update to support an expiration value that may be shown or used elsewhere.

Lower-priorityfix TRX swap to asset mapping bugby Qkin-Keystone · 82866b9a · Apr 14, 2026 · 1 fileMessage 45 · ThinLow 35Details
Commit message · Qkin-Keystone

fix TRX swap to asset mapping bug

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI analysis · Low 35/100

This commit fixes a bug in how the Keystone 3 hardware wallet classifies certain Tron (TRX) transactions. Previously, only memos starting with '=:' were recognized as swap transactions. Now memos beginning with 'SWAP:' (case-insensitive) are also recognized as swaps. This is a UI/flow correction rather than a cryptographic fix, but misclassification could cause a user to review a swap transaction on the wrong screen, potentially hiding important swap-specific warnings or safety checks.

AI review queuedfix pr reviewby Qkin-Keystone · 31e9649f · Apr 14, 2026 · 2 filesMessage 28 · OpaqueInformational 14Details
Commit message · Qkin-Keystone

fix pr review

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

This tiny code-quality patch addresses two minor issues found during a pull-request review: one removes an unnecessary `.clone()` call in Tron transaction handling, and the other adds a missing memory-field cleanup for a new Ethereum/Swapkit display field. Neither change is clearly a security fix, but the missing `free_str_ptr!(self.raw_value)` could in theory leave a small amount of heap memory unreleased when a struct is destroyed.

AI review queuedfix TRX swap to assetby Qkin-Keystone · a48b77e6 · Apr 14, 2026 · 3 filesMessage 38 · OpaqueLow 34Details
Commit message · Qkin-Keystone

fix TRX swap to asset

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

This commit changes how a Keystone hardware wallet displays the destination asset for TRON (TRX) swap transactions. It adds a mapping from short/raw asset codes (like 'b' for BTC, 'e' for ETH) to human-readable names, normalizes case, strips suffixes, and handles chain/asset separators. The change is a UI/display fix for swap transaction memos, not a core cryptographic or signing change. There is no explicit security claim in the commit or supplied references.

AI review queuedupdate code formatby Qkin-Keystone · cca2aca6 · Apr 14, 2026 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · Qkin-Keystone

update code format

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 reformats existing source code. It changes line breaks and indentation in a single Rust file so that a long expression and an if-statement are split across multiple lines. No logic, behavior, or security checks were changed.

AI review queuedfix code reviewby Qkin-Keystone · c2fdab1b · Apr 14, 2026 · 2 filesMessage 28 · OpaqueLow 37Details
Commit message · Qkin-Keystone

fix code review

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

This commit moves a memory-freeing operation from one cryptocurrency display structure (Ethereum Swapkit) to another (Tron). It appears to fix a code review finding about a string pointer being freed in the wrong place, which could otherwise lead to a use-after-free or double-free memory bug. The actual security impact depends on whether the affected field is heap-allocated and how the structures are used after freeing.

AI review queuedupdate tron swapkit memo uiby Qkin-Keystone · d063c974 · Apr 14, 2026 · 13 filesMessage 45 · ThinLow 27Details
Commit message · Qkin-Keystone

update tron swapkit memo ui

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathparser or protocol pathsecond-pass: security-sensitive path
AI analysis · Low 27/100

This commit adds a new on-screen display for Tron cryptocurrency swaps that use a memo starting with '=:' (called 'SwapKit' style). It shows the user extra details such as the destination asset, destination address, raw amount, memo, and expiration time before signing. The change is mostly a UI feature, but it also parses and displays user-controlled memo text, which could be abused to mislead the user if the memo contains crafted text. There is no evidence in the commit that this is a security fix or that the vendor called it a vulnerability.

AI review queuedtest: verify memo in raw_data and fix formattingby qkin · 2f90d5ff · Apr 14, 2026 · 1 fileMessage 67 · AdequateInformational 15Details
Commit message · qkin

test: verify memo in raw_data and fix formatting

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

This commit only adds a new test assertion to existing Rust test code. It checks that the transaction memo matches the raw_data.data field in a Tron transaction test. There is no change to production code, no bug fix, and no security-relevant behavior change.

AI review queued update code formatby qkin · dc988b09 · Apr 14, 2026 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · qkin

update code format

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 only reformats a single Rust test file by splitting a long assert_eq! line into multiple lines. It does not change any executable code, logic, or security behavior.

AI review queued fix:add memo for tron swap txby qkin · 468eff30 · Apr 14, 2026 · 1 fileMessage 45 · ThinInformational 11Details
Commit message · qkin

fix:add memo for tron swap tx

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

This commit adds a new test case for parsing TRON swap transactions that include a memo field. It does not change any production code; it only verifies that an existing parser can correctly extract a memo from a specific transaction payload. There is no indication of a security fix or vulnerability.

Lower-priority update tron parse raw messageby Qkin-Keystone · e749ef3b · Apr 14, 2026 · 1 fileMessage 45 · ThinInformational 15Details
Commit message · Qkin-Keystone

update tron parse raw message

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI analysis · Informational 15/100

This commit only changes the user-facing warning text shown when a TRON raw message cannot be parsed. It is a wording update with no functional or security change.