Keystone 3 firmware

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.

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.

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.

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.

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.

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.

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.

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.

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