Keystone 3 firmware

This commit is purely a code-formatting cleanup. It rewrites a single match arm in a Rust function so the condition and function call are split across multiple lines, matching the style of the surrounding code. No logic, constants, or behavior changed.

This commit removes an accidentally duplicated constant definition for Solana's BIP44 derivation path prefix. In Rust, defining the same constant twice in the same scope is a compile-time error, so the duplicate would have prevented the code from compiling. The fix simply deletes the extra line, restoring normal compilation. There is no runtime security risk.

This commit adds Cardano (ADA) support to the Keystone wallet connection/export feature. It simply includes an additional public key path and an icon in two UI lists. There is no security-relevant change visible in the diff.

This commit adds support for the Cardano (ADA) cryptocurrency to the Keystone hardware wallet's 'Keystone Connect' feature. It introduces a new derivation path and a helper function to format ADA extended public keys for wallet connection. There is no indication in the commit of a security bug or fix; it appears to be a routine feature addition.

This commit fixes translation and font display issues for Japanese and German languages in the Keystone 3 hardware wallet firmware. It updates translated text strings, corrects a corrupted Japanese string, and adds a missing Japanese percent sign character to the font file. There is no security-relevant code change.

This commit fixes Spanish-language display issues in the wallet's user interface. It updates several Spanish translations to be shorter or clearer, and slightly increases the height of two UI containers so the longer Spanish text fits without being cut off. There is no security vulnerability here—it's purely a localization and layout bug fix.

This commit is a build-system fix, not a security patch. It wraps a Zcash-related condition in a compile-time feature flag so that firmware builds that do not include the Web3 feature can compile. There is no direct evidence in the commit that this change fixes a vulnerability; it appears intended to restore continuous integration builds.

This commit removes conditional code that previously hid Spanish, German, and Japanese language support when building a Bitcoin-only firmware variant. After the change, all firmware builds expose the same set of languages. There is no security-relevant change in the diff: no cryptographic, authentication, parsing, memory-handling, or access-control code is modified.

This commit adds support for the Nabox wallet app in Keystone 3 firmware. It changes which cryptocurrency account data is shared with Nabox, switches the data format to a newer 'Keystone Connect' style, and exposes the device's serial number and firmware version during pairing. There is no direct evidence this is a security fix or vulnerability; it appears to be a routine wallet-integration update.

This commit only adds a new version entry to the changelog files and bumps the software build version number from 5 to 6. It does not change any functional code, fix any bug, or alter any security behavior. There is nothing here that affects the security of the device or its users.

This is a tiny code-movement patch that shifts a variable declaration earlier in a function so the code compiles under CI. It does not change what the program does, only where a local variable is declared. There is no security relevance visible in the commit.

This commit is purely a code-formatting cleanup. It removes one debug-print logging statement and adjusts brace style to match Rust's standard formatter. There is no functional change, no bug fix, and no security-relevant behavior change.

This commit changes the Keystone hardware wallet firmware so that Zcash features are hidden or blocked when the wallet was created using a SLIP39 seed (a type of multi-share recovery phrase). The code now returns an 'unsupported' error for Zcash transaction checks on SLIP39 wallets and swaps in a wallet-list image that does not show Zcash. There is no evidence in the commit of a vulnerability being fixed; it reads as a product-level feature restriction.

This commit only changes one number in a version file, increasing the build version from 4 to 5. There is no code change that affects security, functionality, or user data. It is a routine housekeeping update.

This commit fixes a product limitation: Keystone 3 hardware wallets using a SLIP39-style recovery phrase could not connect to the Keystone mobile app for Zcash. The patch removes Zcash from the list of coins shared when a SLIP39 wallet is used, and it makes the underlying Rust code accept a missing Zcash seed fingerprint. There is no direct evidence this is a security vulnerability; it appears to be a compatibility/functional bug fix.

This commit only updates a single hash value in a text file used for image assets. There is no code change, no security fix, and no behavior change visible in the diff. It appears to be a routine update to make unit tests pass after image assets changed.

This commit fixes a display issue by adding the Zcash (ZEC) coin logo to the list of icons shown for the Keystone wallet connection screen. It also removes a few leftover blank lines and an outdated 'todo' comment. There is no security-relevant change in this patch.

This commit only changes a single hash value in a text file that tracks image assets. There is no code change, no user-facing behavior change beyond a possible image refresh, and no security relevance visible in the diff or commit message.

This commit fixes a build-configuration bug that could prevent creating or saving public key information when using a SLIP39 passphrase. The old code accidentally skipped the normal key-derivation path for certain crypto types in non-Bitcoin-only builds, which could leave required public key data unset and cause account setup to fail. The patch restructures the conditional compilation so each build variant (Cypherpunk, Web3, Bitcoin-only) follows the correct derivation branch.

This commit changes how the Keystone hardware wallet checks Zcash transparent inputs when using multi-coin firmware. Previously, Zcash transaction checking was completely disabled for SLIP39/passphrase wallets via a 'disabled' flag. The patch removes that blanket disable and instead adds a runtime check that at least one transparent input actually belongs to the wallet account being used. If none do, it returns a new 'PcztNoMyInputs' error. The change also slightly lowers code-coverage thresholds for the Zcash Rust module.

This commit only fixes and adds unit tests. It changes test-only dependencies, adds new test cases for Bitcoin address encoding and Zcash address generation/PCZT signing, and slightly adjusts code-coverage thresholds in CI. There is no change to production firmware behavior, no bug fix in shipped code, and no security-relevant change visible in the diff.

This commit fixes a user-interface bug for Zcash in the Keystone 3 hardware wallet firmware. It adds a missing UI handler so the Zcash transaction overview screen can be displayed, and adds the Zcash icon to the status bar. There is no indication this changes security-sensitive code or fixes a vulnerability.

This commit fixes a bug in how the Keystone 3 hardware wallet stores a Zcash 'seed fingerprint.' The function that saves the fingerprint forgot to record which account it belongs to. That could cause the wallet to mix up or misidentify which Zcash account the fingerprint is for, potentially leading to wrong address derivation, export of incorrect account data, or user confusion when verifying accounts. It is a data-association bug, not a classic remote exploit.

This commit fixes a misspelled build flag (CYBERPUNK_VERSION vs CYPHERPUNK_VERSION) in the Zcash transaction handling code. Because the wrong flag was used, the Cypherpunk-specific Zcash code path was never compiled in, while the Web3 path may have been active instead. The commit also adds a debug printf showing the mnemonic type. The typo fix could affect which Zcash transaction parser and checker runs, potentially changing how Zcash transactions are validated or displayed, but the commit itself is small and does not show an active exploit.

This is a routine build-fix commit. It corrects a typo in a function name (GetXpubPath to GetXPubPath) and adds a missing newline at the end of a hash file. There is no security-relevant change.