Keystone 3 firmware

This commit is titled 'upgrade sui sdk' and mostly swaps the Sui library dependency to a newer, slimmer package, updates the Rust compiler version used across build scripts, and adjusts code to match the new library's types. There is one notable code change in the Sui request-checking function: it now immediately returns a success result and skips all actual validation. That looks like a temporary debugging change left in the commit, but it could allow an unverified Sui transaction to be approved. The commit does not describe itself as a security fix, and there is no disclosed vulnerability or researcher attribution.

This commit adds the device's firmware version number to the QR code that a Keystone hardware wallet shows when pairing with Zcash wallet software. The change is informational only and matches what the wallet already does for other cryptocurrencies like MetaMask and OKX. There is no indication it fixes a security bug or introduces a security weakness.

This commit improves the Bitcoin transaction review screen on Keystone hardware wallets. It adds clearer warnings and labels when a transaction uses unusual signature modes (SIGHASH_SINGLE or SIGHASH_NONE) or when the fee cannot be calculated exactly (for example, with ANYONE_CAN_PAY inputs). It also fixes a small display issue where line breaks in help text were shown as raw '\r\n' characters. Overall, this is a defensive user-interface improvement rather than an attack.

This commit adds a new user-interface feature for Bitcoin transactions on the Keystone 3 hardware wallet. When a transaction input only provides a 'witness UTXO' (a lightweight proof of the coin being spent), the device now shows a warning asking the user to verify the input value, and offers a QR code that links to the transaction on a public blockchain explorer (mempool.space). This is a defensive UX improvement, not an attack or vulnerability fix. It helps users spot potentially fraudulent input amounts but does not change the underlying signing logic.

This commit adds a firmware version stamp to Zcash signed transaction QR codes so wallets can tell which Keystone firmware version produced the signature. It also fixes two simulator-only stability bugs: one in the async task queue and one in a keyboard text-area handler. There is no direct security vulnerability in the diff; the changes are defensive or feature additions.

This commit simply adds the Solana (SOL) coin icon to two lists of icons shown on the 'connect wallet' screen for the Keystone Nexus wallet. It is a cosmetic UI change with no security relevance.

This commit adds support for two Solana (SOL) public key derivation paths when connecting the Keystone hardware wallet to compatible software wallets via the 'Keystone Connect' feature. It is a routine feature addition and does not contain any obvious security fix or vulnerability.

This commit only reformats Rust source code. It moves a comment onto its own line and adjusts blank lines. No program logic, calculations, or security behavior changed.

This commit fixes a logic bug in how Tron transactions are routed based on QR code type. Previously the firmware treated 'TronSignRequest' as if it were a Keystone-style request and vice versa, which could send the wrong data to the wrong parser/signer. It also fixes a floating-point precision bug in how token amounts are formatted for display, replacing an unsafe logarithm calculation with a loop-based decimal count. A test helper and some comments were removed, but no security disclosure or researcher credit is present.

This commit removes unused serialization libraries from the Tron app and, more importantly, changes how a missing wallet derivation path is handled. Previously, a missing path was silently replaced with an empty default. Now the code returns an explicit error. This is a defensive hardening change that prevents the signing code from continuing with an invalid or unexpected path.

This commit updates Tron-related code in a hardware wallet firmware. It changes how decimal precision is calculated for token amounts, removes an 'unsupported transaction type' error fallback, and broadens the accepted derivation path prefixes. These are code-quality and review changes, but they could have subtle security implications if the new precision logic mishandles edge cases or if removing the catch-all error allows unexpected transaction types to be signed.

This commit simply updates a stored hash value in a text file used for tracking image assets. There is no code change, no bug fix, and no visible security relevance in the commit itself or the supplied materials.

This commit fixes several bugs in the Tron (TRX) signing flow of a cryptocurrency hardware wallet firmware. The changes remove an unused import, eliminate a catch-all error branch that could hide unsupported transaction types, add a missing master-fingerprint lookup, replace a hardcoded seed buffer size with a named constant, and harden string-copy helpers against NULL pointers and buffer overruns. The most user-visible risk is that the old code could crash or leak memory when displaying Tron personal-message data, and the missing master-fingerprint call could have produced incomplete or incorrect signing responses.

This commit is a small cleanup in the Tron (TRX) transaction handling code for the Keystone 3 hardware wallet. It replaces a hardcoded number (7) with a named constant (KeystoneSignRequest) and removes some debug print statements. There is no direct evidence in the commit that this fixes a security vulnerability.

This commit only adds and updates test code for error handling in the Tron app. It expands unit tests to check that various error types convert correctly and removes an unnecessary `mut` keyword from a test variable. There are no changes to production code or security-sensitive behavior.

This commit only reformats Rust source code in the Tron app. It removes blank lines, reorders imports, and adjusts line breaks to match the project's style guide. No program logic, calculations, or security behavior was changed.

This commit only adds and updates unit tests for the Tron app in the Keystone 3 firmware. It does not change any production code logic. The tests cover signing, parsing, address generation, and edge cases for transaction formatting. There is no indication of a security fix or vulnerability being addressed.

This commit adds support for including a text 'memo' field on Tron cryptocurrency swap transactions. The memo is read from an incoming transaction and later copied into the raw transaction data when building a new transaction. There is no obvious security bug in the diff itself, but the change touches how transaction data is parsed and reconstructed, which is a sensitive area in hardware wallet firmware.

This commit only reformats Rust source code and reorders import statements. There are no functional changes, no bug fixes, and no security-related modifications.

This commit is purely a code formatting cleanup. It reorders import statements alphabetically, removes extra blank lines, and fixes indentation and spacing. There are no functional changes to how the Keystone 3 firmware handles cryptocurrency transactions or private keys.

This commit is purely a code-formatting cleanup using rustfmt. It adjusts whitespace, line breaks, and removes blank lines in Tron-related Rust files. The only non-cosmetic-looking change is adding a `fragment_len` parameter to a C-exported signing function, but the diff shows it is simply passed through to an existing encoder call and does not alter security logic.

This commit only adds new automated test cases for the Tron app and removes an unused helper function. It does not change any production behavior, fix a bug, or alter how the device handles real transactions. There is nothing here that would let an attacker steal funds or bypass security.

This commit adds support for a new Tron transaction format used by the NuFi/Keystone Nexus wallet integration. It changes how the firmware parses, validates, and signs certain Tron QR-code transactions, and it adjusts how unknown TRC-20 token amounts are converted for display. There is no direct evidence in the commit that this fixes a security vulnerability; it reads as a feature/compatability update.

This commit refactors how the Keystone 3 hardware wallet handles TRON (TRX) transactions. It switches the signing pipeline from accepting a custom JSON transaction description to accepting a raw protobuf transaction, and it tightens the HD path validation. The change is mostly a feature update for NuFi TRON support, but it also removes some address-derivation checks that previously ensured the transaction's 'from' address matched the wallet's key. That removal could, in theory, make it easier for a malicious companion app to ask the device to sign a transaction that does not belong to the wallet, though the companion app still needs to pass the wallet's master fingerprint and xpub checks. There is no explicit security bug or exploit shown in the diff, but the change is security-relevant because it alters the trust boundary between the host and the device.

This commit only adds two new unit tests for Tron personal-message handling and removes two old Tron standard-request test commands from the firmware's test harness. There is no change to production code, no bug fix, and no security-related behavior change.