Keystone 3 firmware

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 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 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.

This commit only updates unit tests for the Avalanche transaction parser. It swaps test blockchain IDs from mainnet to testnet values, removes debug print statements, fixes an import order warning, and replaces placeholder assertions with real ones. There is no change to production code that handles user funds or device security.

This is a large cleanup commit titled 'chore: fix warning'. It removes compiler warnings across many Rust modules by deleting unused imports, switching to modern Rust syntax, and fixing minor style issues. The most notable functional change is in the Monero code, where randomness for key-image generation and encryption now comes from the operating system's secure random source (OsRng) instead of a deterministic seed derived from the request data. That change is a security improvement, not a vulnerability. There is no clear evidence in the commit of an exploitable security bug.

This commit only adds a changelog entry for firmware version 2.2.18. It describes two new features (DOGE transaction/PSBT parsing) and one bug fix (XMR Key Image generation error), but it does not modify any source code, cryptographic logic, or configuration. There is nothing in the diff that introduces or fixes a security vulnerability.

This commit is a routine cleanup of Rust compiler warnings (Clippy lints). It removes unused imports, rewrites idiomatically cleaner code, fixes variable naming, and updates a few function signatures. There is no indication it fixes a security vulnerability or changes security-critical behavior.

This commit simply comments out a single automated test for Monero transaction signing. It does not change any production code, so it cannot directly introduce or fix a security vulnerability in the firmware that users run. The test is disabled, which means the code it exercises is no longer automatically verified, but the commit itself does not alter how Monero transactions are signed.

This commit simply bumps a build number in a version header from 16 to 18. There are no code changes, no bug fixes, and no security-related modifications visible in the diff.

This commit simply switches two internal Rust library dependencies from a development branch to a numbered release tag (0.0.52). It is a routine dependency pinning change with no visible security fix or vulnerability in the diff itself.

This commit removes leftover debugging code from the Keystone 3 firmware. The most notable change is that in production builds, the device's debug UART output is now replaced with harmless '-' characters instead of potentially leaking real data. Other changes remove hard-coded test values and re-enable a normal boot-version check that had been bypassed. These are cleanup fixes that reduce the chance of sensitive information leaking through debug interfaces or test code being active in production.

This commit is purely a code cleanup: it runs the Rust formatter (fmt) and applies Clippy lint suggestions. The changes are cosmetic—reformatting lines, reordering imports, removing unused imports, and adding 'unsafe' markers to functions that already contained unsafe operations. There is no functional change to how the firmware handles keys, transactions, or user data, and no security vulnerability is introduced or fixed.

This commit is purely a code-formatting change ('cargo fmt') in a Monero signing utility. It rewraps a single function call onto one line instead of multiple lines without changing any logic, values, or behavior. There is no security relevance.

This commit is a routine code cleanup. It removes two blank lines and replaces a length check (`len() == 0`) with the idiomatic Rust method `is_empty()`. These changes do not alter how the Monero app works and do not fix or introduce any security issue.

This commit only edits a Chinese-language changelog file, adding a blank line and a stray backslash. No code, configuration, or security behavior is changed.