Keystone 3 firmware

This commit is a large refactor of how the Keystone 3 firmware handles Zcash transactions. It splits the code into two build flavors: a 'multi-coins' build that supports only transparent (public) Zcash addresses using a normal xpub, and a 'cypherpunk' build that also supports shielded Orchard addresses using a unified full viewing key (UFVK). The change reorganizes feature flags, renames functions, and adjusts how Zcash account data is cached when wallets are created or unlocked. There is no explicit security fix or vulnerability disclosure in the commit message, and the diff itself is mostly structural. A few small items stand out as worth checking: a typo in a feature-guard macro (CYBERPUNK_VERSION vs CYPHERPUNK_VERSION) could leave the cypherpunk UI path disabled, and a debug printf was left in production key-handling code. On its own, this commit does not appear to introduce a clear exploitable vulnerability, but it is a partial refactor and the new multi-coins transparent-only path is simpler and exposes less shielded-key material than before.

This commit only updates Zcash unit tests and feature flags to match a renamed internal function. No user-facing behavior, wallet logic, or cryptographic handling changed. It is a test-only maintenance fix.

This commit is a routine Zcash update and test-coverage improvement. It renames a misspelled function, splits a large signing routine into transparent-only and orchard-only variants, and adds unit tests for wallet integrations. There is no direct evidence in the commit that this fixes an active security vulnerability, but the change to Zcash shielded signing logic is security-adjacent and should be reviewed carefully.

This commit is a straightforward code cleanup that renames two internal signing functions to avoid a naming conflict. It does not change what the code does, only how it is organized. There is no indication of a security bug being fixed.

This commit is a work-in-progress 'temp commit' that refactors Zcash support in the Keystone 3 firmware. It moves Zcash UI code from a 'cypherpunk' build variant into the standard multi-coin build, splits a combined Zcash UFVK/seed-fingerprint getter into separate functions, adds a new Zcash seed fingerprint parameter to the Keystone Connect wallet QR/UR generation, and enables the 'zcash' feature in the Rust multi-coins build. There is no clear security fix or vulnerability being patched; it appears to be feature plumbing and code reorganisation.

This commit reorganizes Zcash support in a hardware-wallet firmware so that advanced privacy features (the 'Orchard' shielded pool) are only included when a special 'cypherpunk' build feature is enabled. The default build keeps only transparent and Sapling support, which shrinks the firmware binary. The changes are mostly compile-time feature flags and duplicated code paths for the smaller default build. There is no direct evidence in the commit that this fixes an exploitable security bug; it is a build-size and feature-gating change.

This commit adds support for the Zcash (ZEC) cryptocurrency to the Keystone 3 hardware wallet firmware. It introduces address generation, derivation path handling, UI elements, and wallet connection data for Zcash. There is no indication of a security fix or vulnerability being patched.

This commit adds Zcash cryptocurrency support to the Keystone 3 hardware wallet firmware. It registers a new Zcash unified full viewing key type, enables encryption of that key, wires up the user-interface handlers for Zcash transactions, and adjusts build flags so Zcash support is available in non-Bitcoin-only firmware builds. There is no direct evidence in the diff of a security vulnerability; it reads as a feature addition.

This commit adds a new wallet integration for Nabox in the Keystone 3 hardware wallet firmware. It changes which public keys (extended public keys, or xpubs) are shown when the user selects Nabox from the wallet list, switching from Ethereum-only data to a broader set covering Bitcoin, Ethereum, Tron, Solana, Litecoin, Dogecoin, and Bitcoin Cash. There is no security vulnerability visible in the diff; it appears to be a normal feature update.

This commit changes a single displayed wallet name from 'Blue Wallet' to 'BlueWallet' in the status bar UI. It is a cosmetic string correction with no security relevance visible in the code.

This commit is a routine UI cleanup for a hardware wallet firmware. It adds a new wallet icon for Jupiter, removes unused wallet-list icons, and reorganizes the list of supported wallets in one source file. There is no indication of any security bug or vulnerability being fixed.

This commit only changes the display names of wallet options shown on the device screen (for example, 'Blue Wallet' to 'BlueWallet', 'Core' to 'Core Wallet', and 'Bitcoin Wallet' to 'Bitcoin Wallets'). It also slightly adjusts when a 'more coins' icon appears for two specific wallets. There is no security-relevant change here.

This commit adds a single debug printf statement that prints a wallet name to the console when a status-bar wallet icon is set. It does not change program logic, access controls, memory handling, or user-facing behavior. There is no apparent security relevance.

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 wallet icon size, and refactors the widget code that draws the wallet connection screen. There is no indication this changes security logic, cryptography, transaction handling, or how the device protects private keys.

This commit changes which wallet icons and names appear in the status bar depending on which product version is being built (Web3, Cypherpunk, or Bitcoin-only). It is a user-interface adjustment, not a security fix.

This commit fixes a build error in a special firmware variant called 'cypherpunk' (also referred to as BTC_ONLY). It changes which cryptocurrency address settings are used when the firmware is compiled without certain optional features. There is no direct evidence this is a security vulnerability; it appears to be a build-breakage fix that could affect which coin's receive/address settings appear in the UI.

This commit changes how wallet names are listed in the status bar for different product build variants (Web3, Cypherpunk, Bitcoin-only). It also adds a debug printf statement that prints a wallet name to the console. There is no clear security issue visible in the diff itself.

This commit only changes on-screen wallet names and a minor UI display rule. There is no security issue here—it is a cosmetic/branding update.

This commit fixes a build error in the Bitcoin-only version of the Keystone 3 firmware. It wraps Litecoin-specific code with a compile-time flag so that code is excluded when building the firmware variant that only supports Bitcoin. There is no direct security vulnerability being patched; it is a build-configuration fix.

This commit only adds a new changelog entry for firmware version 2.3.4 and bumps the build number from 2 to 4. It contains no code changes, bug fixes, or security-related content. There is nothing in the diff that affects device security or user funds.

This commit only adds and updates unit tests for the Bitcoin Rust module. It does not change any production code behavior. There is no security-relevant change to the firmware itself.

This commit only updates test code so that automated Rust tests compile and pass again. It does not change any production wallet code, so it cannot directly affect user funds or device security.

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 on the device, updates related icons and translated text, and changes the default Bitcoin address type to the wallet's native/default format. There is no indication of a security vulnerability or fix in the changes.

This commit fixes the firmware's build for a software simulator. It removes an unused public-key derivation step in Bitcoin PSBT handling, relaxes a hardware-only flash-read assertion when compiling the simulator, and adds a simulator-only header. There is no clear security fix for real hardware; the changes are build-compatibility adjustments.