Keystone 3 firmware

This commit is a build fix that restructures conditional compilation blocks for different firmware variants (Web3, Cypherpunk, BTC-only). It does not appear to change runtime behavior for any single firmware build; it mainly ensures the correct code paths compile under each build configuration. There is no clear security-relevant change.

This commit only changes one number in a version header, bumping the build version from 10 to 12. There is no functional code change, no bug fix, and no security-related content visible in the diff.

This commit only reformats a single Rust test file using a code formatter (rustfmt). It changes whitespace and line breaks in an existing test assertion but does not alter any executable logic, constants, or behavior. There is no security relevance.

This commit adds support for the SLIP39 standard (a way to split a wallet backup into multiple shares) to the Cardano wallet features of a Keystone hardware wallet. It is a feature addition, not a clear security fix. The code changes how Cardano master keys are derived when a SLIP39 wallet is used, and removes several UI blocks that previously disabled Cardano for SLIP39 users. There is no vendor statement or external report saying this commit fixes a vulnerability.

This commit simply swaps the on-screen icon for the BSC (Binance Smart Chain) wallet connection in the Keystone hardware wallet firmware. It updates the PNG source image, its converted embedded C array, the image hash file, and a widget reference. There is no change to security logic, cryptography, transaction handling, or user confirmation flows.

This commit simply changes one number in a version file, lowering the build version from 10 to 9 for a beta test. It does not modify any security-related code, fix any bug, or introduce any vulnerability.

This commit fixes a bug in the 'forget password' screen of a Keystone hardware wallet. It resets a global flag called g_isTonMnemonic to false when leaving that screen. Without this reset, the wallet might incorrectly remember that it was handling a TON (The Open Network) style recovery phrase even after the user navigates away. That leftover state could lead to wrong behavior, confusion, or possibly security-relevant mistakes if the flag later influences how secrets are parsed or stored.

This commit fixes two related bugs in the Keystone 3 hardware wallet's handling of TON (The Open Network) mnemonic phrases. First, when a user tried to verify or recover a wallet in the settings screen, the device always ran a TON-specific check even if the wallet was a standard multi-coin (BIP39) wallet. Second, when a user forgot their password and tried to reset it with a recovery phrase, the device could misidentify a BIP39 phrase as a TON phrase and then erase the wrong wallet data. The patch adds logic to distinguish TON-only from BIP39/multi-coin wallets and to choose the correct recovery path and reset flow for each.

This commit changes the on-screen message shown when the device's Rust code crashes ('panics'). It now first reassures the user that their assets are safe and blames a 'failed data request,' then prints the technical Rust panic details in gray text instead of showing only the raw panic message. There is no direct evidence this fixes a security vulnerability; it appears to be a user-experience improvement that may also reduce information leakage from panic messages.

This commit fixes how the Keystone hardware wallet generates Monero 'key images' for transactions that use extra one-time public keys (subaddresses or additional transaction keys). Before the fix, the code always used the main transaction public key to derive key images, even when Monero rules say it should use an additional key. This mismatch could cause the wallet to generate the wrong key image, which in a hardware wallet context most likely means a transaction would fail to build or be rejected, rather than funds being stolen. The commit adds logic to pick the correct additional key based on subaddress major/minor indices and the output index.

This commit only adds two function declarations (a setter and a getter for an 'extendable' flag) to a header file. There is no executable code change, no bug fix, and no security-relevant behavior visible in the diff. It appears to be a straightforward build fix to satisfy a compiler or linker error caused by missing declarations.

This commit changes how the Monero signing code in the Keystone 3 firmware handles failures when computing cryptographic key images. Previously, the code used `.unwrap()`, which would cause the firmware to panic (crash) if key-image generation failed. The patch replaces those unwraps with proper error propagation (`Result<...>`), so failures are returned as errors instead of crashing. For a hardware wallet, a panic during transaction signing could potentially be triggered by a malformed transaction and might be used to deny service or, in the worst case, leak sensitive state through crash behavior. The patch is a defensive hardening fix.

This commit simply bumps a build number in a version header file from 8 to 10. There are no code changes, no bug fixes, and no security-related modifications visible in the diff.

This commit adjusts the vertical positioning of a divider line and a button on the device's 'About' info screen. It is purely a cosmetic user-interface fix with no security relevance.

This commit removes a UI button that displayed the device's public key (labeled as device UID) from the 'About' info screen of a Keystone hardware wallet. It is a user-interface change, not a fix for a code vulnerability. The change reduces information exposure through the screen but does not alter any cryptographic or security logic.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.