Trezor firmware

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 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 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 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 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 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 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 only adds a new test helper and one extra test case for Ethereum token payloads in the device's test suite. It does not change any firmware, wallet, or production code. There is no indication this fixes or introduces a security issue.

This commit only adds a new testing helper that lets test code run an extra check on every screen page during automated button-press flows. It does not change the device firmware, wallet logic, or any production code. There is no security issue here.

This commit only adds a new automated test case for Ethereum token decoding. It does not change any production code, fix any bug, or alter device behavior. There is no security relevance.

This commit only adds new expected test result hashes (called 'fixtures') for Ethereum 'clear signing' tests across multiple languages and device models. It does not change any firmware code, cryptographic logic, or user-facing behavior. There is no indication of a security fix or vulnerability.

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 product update: it adds a new device capability flag called N4W1 to the list of features a Trezor device can report to connected computers. It does not change any security logic, cryptography, or user data handling. It simply lets software know that a particular hardware model supports this feature.

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 minor translation-processing fix. It changes a script that cleans translated text so it keeps a special non-breaking space before colons (':') in addition to question marks and exclamation points. This is purely a localization/punctuation formatting tweak and has no security relevance.

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 changes the Trezor hardware wallet's screen-lock/suspend behavior so that during two sensitive setup tasks—creating a wallet backup and recovering a wallet—the device stays awake for at least 2 minutes instead of using the normal 40-second battery timeout. This only affects the battery-powered T3W1 model. It is a usability/usability-safety feature, not a fix for a known exploitable vulnerability.

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.

This commit increases the kernel's main stack size from 8 KB to 10 KB on several Trezor hardware wallet models that use STM32F4 microcontrollers. To make room, it slightly shrinks a separate auxiliary RAM region (AUX2). The change is a defensive hardening fix: a stack that is too small can overflow, which on these devices triggers a memory-protection fault and may crash or reset the device. The commit itself does not describe a specific attack, but insufficient stack space is a known reliability and security concern in embedded systems.

This commit adds support for ERC-4626 vault reward claims and changes how Trezor handles Ethereum transactions with extra trailing bytes (calldata suffix). Previously, vault transactions with any trailing bytes were rejected as errors. Now, the device accepts them but shows the extra bytes to the user as a 'Calldata suffix' screen. The change also introduces a new 'claim' function path, but the actual claim UI is stubbed out and returns None (disabled) for now. The commit is a feature addition, not a documented security fix, but it touches transaction parsing and user confirmation flows.

This commit is a routine language and translation update for the Trezor hardware wallet firmware. It changes English wording (for example, 'Input data' becomes 'Data', 'Access passphrase wallet' becomes 'Access Passphrase wallet'), removes some trailing colons from prompts, and updates the generated translation tables and test fixtures accordingly. There is no code behavior change, no security fix, and no vulnerability.

This commit is a code cleanup in the Trezor firmware's bootloader startup system. It replaces a fixed-size on-stack certificate buffer with a new 'reserve/commit/discard' API that lets the bootloader allocate space for the MCU attestation certificate directly in the shared startup-arguments buffer. There is no indication in the commit or supplied references that this fixes a security bug; it appears to be a defensive refactor to avoid large stack buffers and make the API more flexible.