Trezor firmware

This commit fixes a UI bug in how the Trezor hardware wallet counts and displays the last character of a passphrase when it contains multi-byte UTF-8 characters (such as emoji or accented letters). Previously, the code measured length in bytes and sliced the string by byte position, which could split a multi-byte character and produce a broken or incorrect last-character display. The change adds proper character-based counting and a safe way to retrieve the last character. It is a correctness/robustness fix rather than a clear security vulnerability, and there is no evidence it was disclosed or exploited as a security issue.

This is a routine cleanup change that removes an unused visual border feature from the Trezor firmware's Delizia user interface. It does not change any security-sensitive behavior; it only simplifies the code by deleting a function that always returned zero-width borders and updating two places that called it to no longer use a border wrapper.

This commit changes how Trezor devices reveal a passphrase on screen while typing. Previously, the revealed passphrase would hide again if the user's finger slid outside a specific extended area below the input box. Now, the passphrase stays visible until the user simply lifts their finger anywhere on the screen. This is a user-experience refinement, not a security fix or vulnerability.

This commit changes how Trezor hardware wallets display passphrase entry on screen. Previously, the passphrase characters were shown in plain text as the user typed them. After this change, already-typed characters are hidden (shown as dots or asterisks), with only the most recently typed character briefly visible. The user can press and hold in the input area to reveal the full passphrase for verification. This is a security/usability improvement to reduce shoulder-surfing risk, not a fix for an exploitable vulnerability.

This commit is a straightforward code cleanup: it takes one large Rust source file for the Trezor hardware wallet's homescreen and splits it into three smaller, logically organized files (header, notification center, and helpers) plus a module entry point. No user-facing behavior, security logic, or data handling changed.

This commit only adds three new user-facing text strings for an existing hardware feature called N4W1 (likely a near-field communication tag workflow). It adds error messages for empty, non-empty, and damaged tags, plus updates translation indexes and a signature file. There is no code logic change, no bug fix, and no security-relevant behavior.

This commit only changes the text label on a bootloader button from 'INSTALL FIRMWARE'/'INSTALL FW' to 'INITIATE CONNECTION'/'Init connection' on three Trezor hardware wallet models. It is a user-interface wording improvement with no security or functional code changes.

This commit simply removes an unused Monero hashing helper (the 'Hasher' class and related C functions) from the Trezor firmware codebase. It deletes dead code, tests, and type stubs. There is no indication this fixes or introduces a security vulnerability.

This commit is a simple renaming cleanup. It changes identifiers like 'EthereumERC7730DisplayFormatInfo' to 'EthereumDisplayFormatInfo' and 'ETHEREUM_ERC7730_DISPLAY_FORMAT' to 'ETHEREUM_DISPLAY_FORMAT' across protobuf definitions, generated code, and tests. There are no functional changes to how data is validated, parsed, or displayed.

This commit only adds new user-facing text strings for a wallet backup feature called 'N4W1' (for example, prompts asking the user what kind of backup they want and a 'Reading tag...' message). It updates translation files, generated Rust translation code, and a mock file used for testing. There is no executable logic change, no bug fix, and no security-related change.

This commit reverts an earlier design change in Trezor's Ethereum message handling. It changes the protocol so that only a single token definition can be passed up-front with a transaction, instead of a list of multiple tokens. The change is described as a routine cleanup ('chore') to restore a previous simpler design. There is no direct evidence in the commit that this fixes an active security bug, but it removes complexity that could in principle reduce the attack surface for malformed or conflicting token definitions.

This commit changes how Trezor handles Ethereum transactions with large amounts of embedded data. Previously, the device always tried to 'clear sign' (show human-readable details on screen) for every transaction. Now, if the transaction data is larger than an internal storage limit, it skips clear signing and falls back to 'blind signing' (showing a generic warning). The change is described as a workaround because the clear-signing parser cannot fetch additional data chunks, and enabling it would remove the ability to fall back to blind signing. This is a defensive/hardening change rather than a fix for an active vulnerability, but it reduces the chance that a large malicious transaction could confuse the parser or the user.

This commit adds support for a new Ethereum feature called ERC-7730, which lets a computer (like a wallet app) tell a Trezor device how to display and interpret smart-contract transaction data in a human-friendly way. It also changes the message format so apps can send multiple token definitions instead of just one. The change is large and touches many generated files, but it appears to be a feature addition rather than a fix for an existing security bug. Because it introduces new code that parses untrusted data from a host computer and uses it to format what the user sees on screen, it could create security risks if the parsing or formatting logic has flaws, but the diff itself does not show an obvious vulnerability.

This commit is a simple code cleanup in Trezor's Ethereum transaction signing. It extracts a repeated chunk of code that confirms transaction data and shows a summary into a shared helper function, then uses that helper in both legacy and EIP-1559 transaction signing paths. There is no security bug being fixed here.

This commit only adds and updates automated tests for Trezor's Ethereum 'clear signing' feature (ERC-7730 display formats). It does not change the firmware's security logic, so it is not a security patch. The tests verify that malformed or mismatched definitions are rejected, which is a normal defensive testing activity.

This commit only adds stronger checks to existing automated tests for Ethereum 'clear signing' on Trezor devices. It does not change any firmware, wallet, or production code, so it cannot introduce a security vulnerability or fix one in shipped software.

This commit is a simple rename from 'Struct' to 'Tuple' in the Ethereum clear-signing code. It changes only variable, class, and type alias names to better reflect that the code accesses fields by index. No behavior, logic, or security properties are changed.

This commit is a routine code cleanup for the Ethereum app in Trezor firmware. It replaces several hand-written number-parsing functions with a single factory that generates them automatically, and moves the address parser earlier in the file. There is no indication this fixes a security bug or introduces a vulnerability.

This commit removes two unused symbolic labels, TO and CHAIN_ID, from an internal Ethereum clear-signing data-format definition. It is a cleanup change with no functional code logic altered and no security relevance.

This commit is a code cleanup (refactor) that moves ButtonRequest handling logic out of the UI layout class and into a dedicated ButtonRequestHandler class. It does not appear to change security behavior; it reorganizes existing logic to make the code easier to maintain. There is no indication this fixes or introduces a security vulnerability.

This commit is a routine synchronization of translated user-interface text strings for the Trezor hardware wallet firmware. It updates wording in Czech, German, Spanish, French, Portuguese, and the translation signature file. There are no code, logic, cryptographic, or security behavior changes.

This commit is a routine translation update for the French language. It changes the capitalization of one word ('fragment' to 'Fragment') and removes the word 'n°' (number) from two French text strings shown on the device during SLIP39 backup/recovery flows. The accompanying files are just updated translation signatures and UI test fixture hashes. There is no code logic change and no security relevance.

This commit adds the degree symbol (°) to French font files used on Trezor hardware wallets. It is a routine translation/localization update with no security relevance. There is no code change that could be exploited or affect device security.

This commit is a routine synchronization of translated user-interface text for the Trezor hardware wallet. It updates Czech, German, Spanish, French, and Portuguese translation files, refreshes the cryptographic signature that protects those translations, and updates the expected screen hashes used by automated UI tests. There is no change to security logic, cryptography, or how the device handles private keys or transactions.

This commit fixes a bug in the Trezor hardware wallet's low-level crash handler for STM32F4 devices. The handler decides whether a memory fault is a stack overflow by checking the wrong stack pointer due to an inverted branch condition. Before the fix, the device could fail to recognize or recover from a stack overflow on the main stack, potentially leaving it in a crashed or unresponsive state instead of resetting safely.