Trezor firmware

This commit only changes a test file for the Tron cryptocurrency signing feature. It adds 'yield' statements to the test's simulated button-pressing sequence so the test properly waits between simulated user actions. There is no change to the actual Trezor firmware code that users run, and no security fix or vulnerability is present in the diff.

This commit is a routine version bump from 2.10.2 to 2.11.0 for the Trezor firmware. It only changes version numbers in a header file and translation metadata, plus updates the signed translation package fingerprint. There are no code behavior changes, bug fixes, or security patches in this diff itself.

This commit reorganizes how Trezor firmware handles secret keys and the 'secret' subsystem. It splits key-handling code into a new optional component (secret_keys), adds compile-time flags (USE_SECRET and USE_SECRET_KEYS) so different device models can include or exclude these features, and updates the build configuration for every supported model. The change is a structural refactor, not a direct security fix, but it touches sensitive code paths that protect device secrets and storage encryption.

This commit adds a new factory-testing command called secrets-reset that erases the device's secret storage area. It is only compiled into non-production (debug/test) builds, so it cannot be used on normal consumer Trezor devices. The change exposes an internal erase function so the test tool can call it.

This is a routine build-system cleanup for the Trezor hardware wallet firmware. It makes sure that certain device-specific source files (for example, code that talks to a security chip called Optiga, or code that adjusts screen backlight) are only included in firmware builds for devices that actually have those hardware features. There is no indication this fixes a security vulnerability or changes runtime behavior on supported devices.

This commit only updates a test data file (tests/ui_tests/fixtures.json) containing expected hash values for automated UI tests. It does not change any actual firmware, application, or security code. There is no indication this is a security fix or that it affects any user-facing behavior.

This commit is a routine synchronization of translated user-interface text strings for the Trezor hardware wallet firmware. It updates Czech, German, Spanish, French, and Portuguese translation files, plus their signature file, with wording changes, additions, and removals. There is no code logic change, no security fix, and no indication of a vulnerability.

This commit adds a test-only debug feature that lets automated tests restart the Trezor device's main software loop. It is not a normal user feature and only works through the special DebugLink interface used during testing. The change is explicitly for improving backup-failure tests and is marked with '[no changelog]', meaning it is not intended for end users.

This update changes how the Trezor hardware wallet handles unexpected messages while creating a seed backup. Previously, stray or hostile messages (such as a 'Cancel' command) could interrupt the backup process and leave the wallet in an unclear or partially-backed-up state. The fix wraps the backup flow in a new 'continue on errors' mode that ignores unexpected traffic and tells the host the device is busy, so the backup runs to completion. The change is defensive and improves reliability, but it also means a user can no longer cancel a backup from the host side once it has started.

This commit updates Trezor's GitHub CI automation so that branches whose names start with 'secfix/' are treated the same as release branches. It also tightens a couple of upload jobs so they only run in the official repository, and changes one commit-message check to run on any push. The change itself is about build/release plumbing, not a fix for a security bug in the firmware.

This commit only changes the on-screen label shown to Trezor users when confirming TRON transactions. The text 'Maximum Fees' is replaced with 'Fee limit' to match TRON-specific terminology. No transaction logic, fee calculation, or security behavior is changed.

This commit simply turns on Tron (TRX) support in Trezor firmware for all users. It moves Tron code from debug-only builds into normal production builds, updates support lists, and refreshes test snapshots. There is no bug fix or security patch here—just a feature release.

This commit simply renames internal labels used for Tron transaction confirmation screens across different Trezor device layouts. The old names like 'confirm_tron_send' are replaced with newer names like 'tron/send'. There is no visible security change—just keeping naming conventions consistent.

This commit only updates expected visual test snapshots (hashes) for pairing-code entry screens in the Trezor firmware test suite. No actual product code was changed, so it cannot introduce or fix a security vulnerability on its own.

This commit temporarily disables a performance feature called 'THP ACK piggybacking' in Trezor firmware to reduce the chance of triggering an unrelated bug referenced as issue #6506. It is described as a workaround, not a complete fix. The underlying bug can still occur, but only if a network acknowledgment is delayed by more than 200 milliseconds. The change lowers the protocol version minor number from 1 to 0 and stops the device from enabling ACK piggybacking during the handshake. There is no direct evidence in the commit that this is a security vulnerability, and no changelog entry is added.

This commit only changes an automated test for the Trezor hardware wallet. It simplifies how the test puts the device into a 'backup failed' state by starting from a pre-configured test fixture instead of manually running and cancelling a backup. No actual wallet firmware code or user-facing behavior is changed.

This is a minor cleanup change in the Python Trezor library. It removes an internal, underscore-prefixed flag called `_skip_init_device` that was not being used anywhere. The function now always refreshes device features after loading a device. There is no security issue here.

This commit adds a new test-only debug option called `unfinished_backup` to the Trezor hardware wallet's device-loading tools. It lets developers set an internal storage flag that marks a backup as incomplete. The change only affects debug/test code paths and does not alter normal user-facing wallet behavior. There is no indication in the commit that this fixes or introduces a security vulnerability.

This commit changes how Trezor handles Tron cryptocurrency smart-contract payments. Previously, the device used a programming assertion to assume that certain address-padding bytes were zero. Now it checks those bytes at runtime and rejects the transaction if the padding is wrong. The change likely prevents a malformed Tron token-transfer request from being misinterpreted or from causing the device to behave unexpectedly. It is a defensive hardening fix rather than a clear-cut remote exploit patch.

This commit only adds Python type annotations to two internal functions. It does not change any runtime behavior, logic, or security checks in the Trezor firmware.

This commit removes a single duplicate TypeVar definition in a Python file used only during type checking. It has no effect on the actual running firmware and no security relevance.

This commit is a code cleanup that moves the handling of on-screen button prompts into a separate helper function and adds a way to tell the message-reading code to reject any unexpected message. The change itself does not appear to fix a specific security bug, but it touches the code that decides which messages the device accepts while a user is confirming an action. There is no vendor statement that this is a security fix, and no independent researcher is credited.

This commit is a routine GitHub Actions workflow update for Trezor firmware. It adds new build jobs that produce emulator binaries with a feature called 'Tropic' enabled, and uploads them to a separate folder. There is no indication of a security fix, vulnerability, or malicious change in the diff.

This is a one-line UI label change. The Trezor device screen previously showed a generic 'Account info' menu label when confirming a transaction summary; now it shows a caller-supplied account title if one is provided, falling back to the generic label otherwise. There is no security-relevant behavior change visible in the diff.

This commit only changes automated test helper code for Trezor hardware wallets. It adds a way for test scripts to run small callback steps while the test framework clicks through on-screen menus, and updates a few Ethereum transaction test flows to use that mechanism. There is no change to the actual wallet firmware, cryptography, user-facing behavior, or security boundaries.