Keystone 3 firmware

This commit adds support for Litecoin (LTC) native SegWit addresses (the 'ltc1...' format) to the Keystone 3 hardware wallet firmware. It is a feature addition: it lets users generate and display a new type of LTC address and export the corresponding public key. There is no indication in the commit that it fixes a security bug or vulnerability.

This commit adds support for a Litecoin native SegWit extended public key (xpub) when preparing public keys for transaction parsing. It shifts the array indexes for DASH and BCH to make room. There is no direct evidence in the commit that this fixes an exploitable security vulnerability; it appears to be a missing-currency-support bug that could cause address derivation or transaction display issues for Litecoin native SegWit users.

This commit only changes one number in a version header file, bumping the build version from 0 to 2. There is no functional code change, no bug fix, and no security-related modification. It appears to be a routine version update for testing or release tracking.

This commit adds support for a new wallet partner called Jupiter to the Keystone 3 hardware wallet firmware. It is a routine feature addition: a new logo image, an updated image hash, a new entry in the wallet connection list, and related UI label updates. There is no indication of a security fix or vulnerability.

This commit simply adds a Litecoin (LTC) icon to a list of coin icons shown in the wallet connection screen. It is a cosmetic UI change with no security relevance.

This commit is a routine product update for the Keystone 3 hardware wallet firmware. It refreshes the list of supported software wallets shown in the UI, updates translated text strings, and adds new font glyphs (Chinese, Japanese, Korean) needed for those strings. There is no visible security-relevant code change in the diff.

This commit fixes a bug in the Keystone 3 hardware wallet firmware where Litecoin (LTC) transactions using the newer Native SegWit address format (path m/84'/2'/0') could not be properly parsed or verified. The fix adds the missing LTC Native SegWit extended public key (xpub) to the list of keys used when decoding transaction data. Without this key, the device might fail to recognize the user's own addresses in a transaction, which could lead to incorrect display, signing failures, or in a worst-case scenario, tricking the user about where funds are going. The change is small and appears to be a straightforward missing-key fix rather than a full security patch.

This commit adds support for Litecoin (LTC) native SegWit addresses (the 'ltc1...' format) to the Keystone 3 hardware wallet firmware. It is a feature addition: it lets users generate and display LTC native SegWit receive addresses, export the corresponding extended public key, and includes new UI labels and a tutorial. There is no indication in the commit that this fixes a security bug or introduces a vulnerability.

This commit fixes build errors in the simulator (non-production) build of the Keystone 3 firmware. It removes an unused public-key derivation step in Bitcoin PSBT handling, relaxes a hardware flash-read assertion when compiling for the simulator, and adds a simulator-only header include. There is no evidence of a security vulnerability being patched.

This commit changes how the Keystone 3 hardware wallet displays Bitcoin transaction recipients. Specifically, it hides the 'change' label on outputs that return bitcoin to the user's own wallet when the transaction comes from a 'legacy' format. This is a user-interface change, not a fix for stealing funds. It may reduce user clarity during transaction review, but it does not by itself allow an attacker to move coins.

This commit only adds text to two changelog files describing a new firmware version (2.3.2). It does not change any source code, so it cannot introduce or fix a security vulnerability by itself. The changelog mentions a bug fix for TON-only message signing, but the actual code change is not present in this commit.

This commit is a purely cosmetic user-interface tweak for the Bitcoin transaction review screen. It changes how the 'Receive' and 'Change' labels are drawn—adding a rounded background container, adjusting colors and alignment, and fixing the layout height calculation so the new container fits. There is no security-relevant behavior change.

This commit changes how the Keystone hardware wallet labels Bitcoin transaction outputs on its screen. It adds a new 'is_mine' flag and shows 'Change' or 'Receive' labels next to outputs that belong to the user's own wallet. The goal appears to be helping users more easily recognize their own change outputs during transaction review, which is a usability and anti-confusion improvement rather than a fix for an exploitable vulnerability.

This commit is a routine build fix for the firmware simulator. It adds a helper macro that lets a function return NULL on error, fixes a function name typo in a MetaMask wallet helper, and adjusts safe-string macros so they return 0 like their standard-library counterparts. None of these changes appear to be security fixes.

This commit fixes how the Keystone 3 hardware wallet parses Bitcoin PSBT (Partially Signed Bitcoin Transaction) outputs. The change adds verification that an output's Bitcoin address actually matches the public key and derivation path claimed in the transaction, rather than trusting the PSBT's output metadata blindly. If the previous code accepted incorrect or attacker-controlled output data, a user could be tricked into approving a transaction that sends funds to an unexpected address. The commit also refactors some address-calculation code into a shared helper.

This commit only changes a single software version number (the build counter from 0 to 2) in a header file. There is no functional code change, no bug fix, and no security-related content visible in the diff.

This commit adds support for a new software wallet called Nabox to the Keystone 3 hardware wallet firmware. It is a routine feature addition: new icon images, generated image source files, and registration of the wallet in UI lists. There is no indication of a security fix or vulnerability.

This commit is a user-interface cleanup for the 'connect wallet' screen. It removes many unused wallet-list image files and their generated C code, updates one remaining icon (Backpack) to a larger size, and refreshes an image-hash file. There is no visible change to security-sensitive code, cryptography, transaction handling, or communication logic.

This commit fixes a single-character bug in the hardware wallet's 'connect wallet' screen. The original code used a single equals sign (=) instead of a double equals sign (==), which in C means it assigned a value rather than checking it. As a result, the code always treated the wallet as a Bitcoin wallet and ran the Bitcoin-specific tutorial branch, regardless of which wallet the user actually selected. The fix changes it to a proper comparison (==).

This commit fixes a crash in the TON (The Open Network) signing code for the Keystone 3 hardware wallet. Previously, if a user had not set a custom derivation path, the code would blindly copy the seed bytes into a fixed 32-byte secret key buffer. If the seed was shorter than 32 bytes, this would read past the end of the seed data, causing a crash or undefined behavior. The fix checks the seed length first and returns a controlled error if it is too short.

This commit is a routine user-interface update for the Keystone 3 hardware wallet firmware. It swaps in a larger Zeus wallet icon, adds a new Bitcoin wallet-list icon, updates the corresponding image asset files, refreshes an image-hash file, and adjusts a few UI labels and status-bar resources. There is no change to cryptographic code, transaction signing, key handling, parsing of untrusted data, or any other security-sensitive logic.

This commit only changes one line in a Chinese-language changelog, correcting the heading 'Bug Fixes' to 'Bug 修复' (Chinese for 'Bug Fixes'). No code, configuration, or documentation with security implications was modified.

This commit only edits the formatting and wording of a product changelog. It adds blank lines and changes headings like 'BTC-ONLY' to 'BTC Only' and 'CYPHERPUNK' to 'Cypherpunk'. No code, configuration, or security-related content was changed.

This is a tiny UI bug fix for the Solana screen shown when creating a Squads multi-signature wallet. The original code accidentally showed the Squads logo and label for every transaction *except* the Squads multisig creation address, because it used the wrong comparison. The fix makes the logo and label appear only when the destination actually is the Squads multisig creation contract. It does not change transaction signing logic, address validation, or cryptographic checks.

This commit is a user-interface fix for the Squads multisig creation screen. It removes a few unused Chinese and Japanese font glyphs and updates translated text strings. There is no indication this changes any security-critical code, cryptography, transaction parsing, or user confirmation logic.