Keystone 3 firmware

This commit only adds explanatory comments and reformats code for readability. It does not change any program logic, cryptographic operations, or security checks.

This commit removes two unused test data strings from a Rust unit test in the Avalanche transaction handling code. The strings were declared with underscores (let _input_bytes), meaning they were intentionally unused. No executable code, logic, or security behavior changed. It is a routine cleanup with no security relevance.

This commit reviews and hardens the IOTA cryptocurrency support in the Keystone 3 hardware wallet firmware. It removes unused dependencies, fixes several places where the code would crash if given empty or malformed input, and improves handling of the secret seed so it is wiped from memory even when an error occurs. There is no explicit statement from the vendor that this fixes a security vulnerability, but the changes reduce the chance of a crash or information leak when signing IOTA transactions.

This commit is a purely cosmetic code-formatting change. It removes an extra space in an 'if' statement in the Sui blockchain app so that the code follows Rust style rules. There is no functional change and no security impact.

This commit simply deletes a Chinese-language technical documentation file describing how the Sui blockchain is supported in the Keystone 3 firmware. No code, configuration, or cryptographic implementation was changed. It is a documentation cleanup with no direct security impact on the device or its users.

This commit only updates a Rust test file for TON (The Open Network) mnemonic handling. It adjusts an existing test to expect a different error message and adds a second test case for an 11-word mnemonic. There is no change to production code behavior, no security fix, and no vulnerability introduced.

This commit is a routine code cleanup that runs the Clippy linter. It only changes how error messages are formatted in two Rust files—switching from older format!() argument styles to newer inline variable syntax. There is no functional change, no bug fix, and no security relevance.

This commit only adds new automated tests for the Sui blockchain app in the Keystone hardware wallet firmware. It checks that address generation rejects invalid or wrong-length public keys and that transaction-intent parsing rejects empty input and invalid scope bytes. No production code behavior was changed.

This commit only adds a new section to two changelog files describing version 2.2.20. It contains no code changes, no bug fixes, and no security-related content. It is purely documentation.

This commit changes only the Chinese translation of the word 'Restart' from '重新开始' (start over) to '重启' (reboot/restart) in a translation data file and its generated C source. It is a wording update with no functional or security effect.

This commit only changes a single number in a version header file, bumping the firmware build version from 18 to 20. There is no code change that affects security, functionality, or behavior. It is a routine version update with no security relevance visible in the diff.

This commit simply adds two new Ethereum-compatible networks to a list of known chain IDs inside the Keystone hardware wallet firmware. It is a routine configuration update with no visible security bug or vulnerability.

This commit fixes a crash in the Solana transaction review screen on the Keystone 3 hardware wallet. The old code kept a large array of copied account addresses and tried to free them later, which could cause memory corruption or a crash. The patch removes that bookkeeping and instead passes the original address pointer directly to the click handler. It also simplifies how instruction accounts are displayed, likely avoiding a null-pointer or layout crash when an instruction has no accounts.

This commit simply adds five new Ethereum token contract addresses to a built-in list used by the Keystone hardware wallet's user interface. It is a routine data update with no code logic changes and no apparent security relevance.

This commit fixes a Korean translation error and removes two stray trailing whitespace characters. The Korean text for a Permit signing setting previously said the device would 'enable or enable' the feature; it now correctly says 'enable or disable.' There are no code behavior changes.

This commit fixes a crash in the TON (The Open Network) jetton token display code on Keystone 3 hardware wallets. Previously, when a token amount was too large to fit in a 64-bit integer, the firmware would panic and crash. The fix switches to a larger 128-bit integer and formats the amount more carefully. A crafted transaction with an oversized amount could have caused the device to crash, potentially disrupting transaction signing or user experience.

This is a one-line build fix in a simulator-only header file. It adds a missing function declaration (random_buffer) so the simulator code compiles. There is no indication of a security bug, vulnerability, or runtime behavior change in the actual hardware firmware.

This commit only updates a documentation file (docs/verify.md) that explains how users can build and verify the firmware. It adds instructions for a new 'Cypherpunk' firmware variant and corrects the filename used in verification steps from 'mh1903.bin' to 'mh1903_full.bin'. There are no code changes and no security fix or vulnerability introduced.

This commit removes a single duplicate Rust import statement that caused a compiler error. It is a routine build fix with no security relevance.

This commit fixes compile errors triggered by a stricter compiler setting that treats non-literal format strings as potentially insecure. The changes wrap translated UI text strings with a safe "%s" placeholder so they are treated as plain text rather than format strings. In theory, the old code could have allowed a malicious or malformed translation string to be interpreted as a format specifier, possibly causing crashes or information leaks, but there is no evidence that any such attack was possible or exploited in practice. The commit message frames the change as a build fix, not a security fix.

This is a minor build-fix change for the software simulator. It wraps a call to a hardware-specific random-number function so the simulator can compile. It does not change real-device behavior or introduce a security vulnerability.

This commit is a build-system hardening change, not a security fix. It pins the Rust build output directory to the default 'target' folder so that individual developer settings cannot accidentally break the firmware build. There is no indication it addresses a vulnerability or malicious behavior.

This commit only edits the release changelog text. It updates the release date and adds bug-fix descriptions for version 2.2.18. No source code, build scripts, or firmware logic were changed, so it cannot introduce or fix a security vulnerability by itself.

This commit is a test-only refactor that makes random number generation injectable so unit tests can use a fixed seed and produce deterministic results. It does not change the production code path: the firmware still uses the hardware random number generator (OsRng) when signing real Monero transactions. The expected test output was updated because the deterministic test RNG now produces different, predictable values.

This commit is purely a code-style cleanup: it runs the Rust formatter (rustfmt) across 32 files. The changes only reformat whitespace, line breaks, import ordering, and similar stylistic details. No program logic, security checks, or behavior were changed.