Keystone 3 firmware

This commit changes how the Keystone hardware wallet reports its firmware version when pairing with Zcash wallets. Previously it used a function that returned a display-formatted version string (with a flavor suffix). Now it formats the raw major/minor/build numbers directly. The goal is to make the pairing QR code's version string match the version bytes stamped by the PCZT signer, so wallets can use one consistent minimum-version check. There is no direct security vulnerability in the diff itself; it is a compatibility/consistency fix.

This commit adds a new 'expiration' field to a Tron transaction data structure used inside the Keystone hardware wallet firmware. The change only initializes the field to an empty string in a few places and does not, by itself, appear to fix or introduce any security vulnerability. It looks like a routine data-structure update to support an expiration value that may be shown or used elsewhere.

This tiny code-quality patch addresses two minor issues found during a pull-request review: one removes an unnecessary `.clone()` call in Tron transaction handling, and the other adds a missing memory-field cleanup for a new Ethereum/Swapkit display field. Neither change is clearly a security fix, but the missing `free_str_ptr!(self.raw_value)` could in theory leave a small amount of heap memory unreleased when a struct is destroyed.

This commit adds a new on-screen display for Tron cryptocurrency swaps that use a memo starting with '=:' (called 'SwapKit' style). It shows the user extra details such as the destination asset, destination address, raw amount, memo, and expiration time before signing. The change is mostly a UI feature, but it also parses and displays user-controlled memo text, which could be abused to mislead the user if the memo contains crafted text. There is no evidence in the commit that this is a security fix or that the vendor called it a vulnerability.

This commit only adds a new test assertion to existing Rust test code. It checks that the transaction memo matches the raw_data.data field in a Tron transaction test. There is no change to production code, no bug fix, and no security-relevant behavior change.

This commit only reformats a single Rust test file by splitting a long assert_eq! line into multiple lines. It does not change any executable code, logic, or security behavior.

This commit adds a new test case for parsing TRON swap transactions that include a memo field. It does not change any production code; it only verifies that an existing parser can correctly extract a memo from a specific transaction payload. There is no indication of a security fix or vulnerability.

This commit is a routine build-system cleanup. It moves a Sui blockchain dependency from being declared in one specific app file to being declared once at the workspace level, and then references it from the app and C-binding crates. It also reformats some Zcash feature flags onto single lines. There is no visible security fix or vulnerability being patched.

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 appears to be a routine CI (Continuous Integration) configuration update with no visible security relevance. Only one file was changed with a single-line addition and deletion. The actual code diff is unavailable, so no security-relevant content can be assessed.

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.