Trezor firmware

This commit is a routine test-code cleanup. It moves helper functions used only in automated device tests from one test file into a shared test helper file so they can be reused. No firmware behavior, cryptography, or user-facing functionality is changed.

This change wraps the wallet backup step during device setup in a helper that ignores unexpected messages. It likely prevents a setup/backup flow from being disrupted or aborted by stray or malicious messages sent to the Trezor while a backup is in progress, which could otherwise leave the device in an inconsistent state or confuse the user.

This is a small internal code cleanup in the Trezor firmware. It moves a debug-only helper function call directly to where it is used and removes an unnecessary wrapper. There is no user-facing change and no security fix.

This is a routine code cleanup change in the Trezor firmware's Ethereum transaction signing module. It renames several internal constants to start with an underscore and wraps them with MicroPython's `const()` helper so the interpreter can optimize them. The numeric values and program logic are unchanged. There is no security fix or vulnerability here.

This commit fixes several small bugs in Trezor's Python library for Bluetooth (BLE) communication. The main fix prevents a crash when scanning for BLE devices multiple times, caused by a typo that iterated over dictionary values instead of items. Other changes add safety checks before reading or writing to a BLE device and improve error messages. There is no clear security vulnerability being patched; it looks like ordinary bug fixing and hardening.

This commit is a routine translation and user-interface wording update for the Cardano cryptocurrency flow on Trezor hardware wallets. It rephrases on-screen labels such as changing 'key hash' to 'Key hash' and replacing some message-signing prompts with a new credential description template. There is no indication of a security vulnerability being fixed or introduced.

This commit is a routine metadata update for Trezor's protocol-buffer message definitions. It adds directional labels (wire_in/wire_out) and a bitcoin-only flag to a set of Trezor-Host Protocol (THP) pairing and credential messages, plus regenerates the matching Rust code. There is no change to actual message handling logic, cryptography, or device behavior.

This is an automated dependency update by Dependabot that bumps the Python syntax-highlighting library Pygments from version 2.19.2 to 2.20.0 in the project's lock file. There is no indication in the commit that this fixes a security issue, and Pygments is an indirect development-only dependency used for documentation or code display, not for handling secrets, cryptography, or user input in the hardware wallet firmware itself. On its own, this change does not present a security concern.

This is a small internal cleanup in the Trezor firmware that replaces direct access to a global variable (CURRENT_CONTEXT) with a safer helper function (get_context()). The change is described by the developers as a code hygiene improvement, not a security fix. It slightly reduces the risk of future bugs by making context access more controlled, but there is no direct evidence it fixes an exploitable vulnerability.

This commit only removes unused Python imports and simplifies a few conditional import blocks in unit test files. It does not change any production firmware code, cryptographic logic, or device behavior. There is no security issue here.

This commit is a test-code cleanup only. It moves repeated setup and teardown code for unit tests into a shared helper class, TestCaseWithContext. There are no changes to the actual firmware, wallet logic, cryptography, or any code that runs on a real Trezor device. It cannot affect user funds, device security, or real-world attacks.

This commit is a simple code cleanup: it moves a small list of known Ethereum contract addresses and their human-readable names from one file to a new dedicated file. The actual addresses and names remain exactly the same, and no security behavior changes.

This commit only adds new test cases and fixes whitespace indentation in a test fixture file for Ethereum transaction signing. It does not change any firmware code that runs on the Trezor device or any production software. The new test cases include edge-case and fuzz-style scenarios (e.g., zero slippage, very large amounts, unknown tokens) to verify how transaction data is displayed to users. There is no security vulnerability introduced here.

This commit changes how Trezor handles Ethereum transaction data (calldata). Previously, clear signing only worked if the entire calldata fit in the first chunk sent by the host. Now the device actively requests and stores up to 4 KB of calldata so it can try clear signing on larger transactions. If clear signing succeeds, the user sees a human-readable confirmation instead of raw hex data. The change refactors the code to collect initial data before deciding whether to clear sign or fall back to blind signing. There is no direct evidence in the commit of a security vulnerability being fixed; it reads as a feature improvement.

This commit only updates a test data file (fixtures.json) that stores expected screen hashes for automated user-interface tests. It does not change any firmware, application, or cryptographic code that runs on Trezor devices. There is no security issue in this commit itself.

This commit fixes a minor bug in the Trezor command-line tool (trezorctl) used to manage paired device credentials. Previously, when listing saved credentials, the tool would try the oldest saved credential first. If that older credential had been invalidated on the device, the tool could get stuck trying to use it instead of a newer, still-valid one. The fix simply reverses the order so the most recently added credential is tried first. It is a usability/reliability fix rather than a security vulnerability that allows an attacker to steal funds or keys.

This commit only updates version numbers and translation metadata. It changes the firmware version from 2.11.1 to 2.11.2, the security monitor version from 1.0.8 to 1.0.9, and updates the translation files' version headers and signature metadata. There are no code changes that affect security or functionality.

This commit adds a new command-line option to the Trezor Python library that lets users choose between two backup methods (display on device screen, or a new 'N4W1' method) when setting up or backing up a hardware wallet. It is a feature addition, not a security fix.

This commit refactors how the Trezor firmware selects a backup handler when creating or restoring a wallet backup. Previously the device always used a display-based backup handler. Now it accepts a 'method' parameter from the host and routes to the appropriate handler, with only display-based backup implemented today and a placeholder for a future method. There is no direct security fix here; it is a feature/refactoring commit that adds a TODO for user prompting when no method is specified.

This commit is a straightforward internal code reorganization (refactor) for how the Trezor device displays wallet backup instructions. It introduces a 'BackupHandler' abstraction so that different backup methods can reuse the same display logic. There is no change to security behavior, no bug fix, and no indication of a vulnerability.

This is a small internal cleanup in the Trezor firmware's backup setup screens. It removes an unnecessary 'single_share' flag from a function and instead decides which text to show based on whether a word count is provided. There is no visible security change.

This commit is a straightforward internal code cleanup in the Trezor firmware's recovery flow. It moves display-related logic into a new helper class without changing what the recovery process actually does or how it protects user data. There is no indication this fixes or introduces a security problem.

This commit is a code cleanup (refactor) of the wallet recovery flow in Trezor firmware. It moves the recovery loop into a new helper function and changes how the SLIP-39 recovery state is represented internally. There is no indication in the commit that this fixes a security bug or changes security behavior.

This is a routine automated dependency update by Dependabot. It bumps the Python 'requests' library used in an internal battery-testing tool from version 2.32.4 to 2.33.0. There is no indication in the commit or supplied references that this fixes a security issue, and the affected tool is not part of the Trezor firmware that runs on user devices.

This commit only changes how the Black code formatter is run during style checks. It adds a `--fast` flag to suppress a warning in local developer runs, while keeping the slower, stricter check in CI. There is no change to the actual Trezor firmware, wallet logic, or anything users interact with.