Trezor firmware

This is an automated dependency update by Dependabot that bumps the Python urllib3 library from version 2.5.0 to 2.6.3 in the project's lock file. urllib3 is a widely used HTTP client library, but it is an indirect dependency here, meaning it is pulled in by another package rather than being used directly by Trezor's firmware code. The commit itself only changes version numbers and download hashes; it does not modify Trezor's own code. Without knowing which known urllib3 vulnerabilities exist between these versions or how Trezor's tooling uses it, the direct security risk from this single commit is low.

This commit changes the nightly build workflow for Trezor hardware wallets. It adds a new build step for a component called 'secmon' (only for the T3W1 model), splits the build into separate steps, and collects build fingerprints into a dedicated folder. There is no indication this fixes or introduces a security vulnerability; it is a build-pipeline improvement.

This commit adds a new GitHub Actions workflow that builds Trezor firmware emulators, runs two selected UI tests in different languages, and uploads screenshot reports to an Amazon S3 bucket. It also adds a helper script that formats a comment with links to those reports, a list specifying which tests to run, and a minor change to slow down the animated GIF viewer from 200 ms to 1000 ms per frame. There is nothing in the changes that alters how the Trezor device handles secrets, cryptography, user input, or firmware security.

This commit is a minor internal improvement to the Python unit-test helper used in Trezor's firmware testing. It lets developers mark an entire test class as skipped rather than only individual test methods, and adds yellow coloring for skipped tests in console output. There is no change to device firmware, cryptography, wallet operations, or any user-facing security behavior.

This commit only changes how certain software tests are skipped or run. It replaces manual 'if' checks at the bottom of test files with Python's built-in '@unittest.skipUnless' decorator on test classes. This makes the test suite behave more consistently but does not change any actual product code that users interact with.

This commit is a routine internal cleanup in the Trezor firmware. It moves the SLIP21 path validation into its own helper method, adds a new function to convert SLIP21 paths to human-readable strings, and updates tests. There is no indication it fixes a security vulnerability or changes user-visible behavior in a risky way.

This commit fixes the order in which a simulated Trezor task (running on Unix/emulator) terminates itself when marked for shutdown. Previously, a killed task could briefly wake up and run again after yielding, because the 'am I killed?' check happened too late. Now the task exits immediately when it yields while killed, preventing a killed task from resuming and possibly executing unwanted code or mishandling an exception. The change is in the Unix emulator build, not the real hardware firmware, and the commit message does not call it a security fix.

This commit only changes debug log messages shown when a task ends. It makes the messages clearer and skips printing details when a task ended normally with no error. There is no change to how the device operates or to any security behavior.

This commit fixes how the Trezor emulator exits when running the core app. Previously, the emulator thread did not pass along the actual exit code from the finished task, and it skipped the normal cleanup path. Now it calls the standard `systask_exit()` function with the real exit code. This is a code-correctness fix that mainly affects testing and emulator behavior, not a security vulnerability in the hardware wallet itself.

This commit removes a factory-testing command called backup-ram-erase from production builds of Trezor hardware wallets. The command was previously available in both production and non-production (development/test) builds, but should only exist in development builds. It is a hardening/cleanup change rather than a fix for an active exploit, because reaching the production-test command interface already requires physical access and special tooling.

This commit simply deletes an unused helper function called maybe_call() from the Trezor firmware's internal communication code. The function had no remaining callers, so removing it cannot introduce or fix any security issue. It is a routine code cleanup with no user-visible or security-relevant change.

This commit only adds extra debug logging messages that record when a 'ButtonRequest' event is ignored by the Trezor device's user interface code. It does not change program behavior, fix a bug, or alter security logic. There is no indication this is a security patch.

This commit fixes a mismatch in Trezor's Bitcoin Cash address encoding. Previously, the encoder could create addresses with an overly long human-readable prefix (the part before the colon, like 'bitcoincash') that the decoder would later reject as invalid. The patch adds a length check so the encoder refuses to produce addresses that cannot be decoded. It also renames variables and updates comments for clarity, with no functional changes beyond the new length check.

This commit is a test-only UI fix that enables the on-screen menu during automated test runs for two wallet interface layouts. It does not change how real transactions are signed or approved; it only makes sure automated tests can navigate the confirmation screens properly. There is no indication this fixes a security vulnerability.

This commit fixes a UI flow issue in the Trezor firmware's Delizia layout. Specifically, it ensures that transaction summary menus are properly included in the device flow, allowing users to access the menu during confirmation. Without this fix, users may not have been able to view or interact with summary details as intended during transaction signing. There is no direct evidence in the commit that this is a security vulnerability, but missing UI steps in a hardware wallet could theoretically affect user verification of transaction details.

This commit only changes test helper code. It moves calls that exercise on-screen menu items so they happen on every page of a paginated screen, not just the last page. There is no change to the actual Trezor firmware or to how real user transactions are handled, so it does not create or fix a security vulnerability in the device itself.

This commit only updates expected test result hashes (called 'fixtures') in a single test data file. There are no code changes, no bug fixes, and no security-related modifications visible in the diff. It appears to be a routine maintenance update so automated UI tests match the current device output.

This commit is a straightforward internal code cleanup in the Trezor firmware's user-interface code. It replaces a loose pair of values (a notification text string plus a separate numeric 'level') with a single structured 'Notification' type, and gives the numeric levels named constants like ALERT, WARNING, INFO, and SUCCESS. There is no change to security behavior, no bug fix, and no externally visible functional change for users.

This is a documentation-only change inside a Protocol Buffers definition file. It corrects an annotation comment describing which message logically follows DebugLinkSetLogFilter. There is no code, no behavior change, and no security impact.

This commit simply deletes an unused constant named LOCK_TIME from a test configuration file. It does not change any device firmware, wallet logic, or security behavior. There is no security issue here.

This commit is a routine version bump for Trezor firmware and related embedded components. It only changes version numbers in header files and translation metadata. There are no code changes, no bug fixes, and no security-related modifications visible in the diff.

This commit adds new factory-test (prodtest) commands for the Tropic secure chip used in some Trezor devices. It lets authorized production-line tools read and change a reversible chip setting called 'sensors configuration,' and also erase cryptographic slots or dump the whole chip configuration. The change is intended for manufacturing/testing, not normal user wallets, and requires a privileged pairing session. The code itself is not a hidden backdoor, but it does expand what a party with prodtest access can do to the secure chip.

This commit adds a new diagnostic command called optiga-metadata-read to Trezor's production-test firmware. It lets factory/test tooling read metadata from the Optiga secure chip, such as object sizes, access rules, and lifecycle state. It is a read-only debugging feature and does not change any data or access controls. There is no indication in the commit that this fixes a security bug or introduces a vulnerability.

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 translations, refreshes the cryptographic signature that verifies those translations, and updates the expected screen hashes used in automated UI tests. There is no code that handles secrets, cryptography, network communication, or user authorization, and nothing in the changes suggests a security vulnerability.

This commit only updates expected test screenshots (called UI fixtures) for the Trezor hardware wallet's automated test suite. It adds hashes for two new test cases that check how the device handles invalid or missing credentials for an 'evolu' delegated identity key feature. There is no change to actual device firmware code, cryptography, or user-facing behavior, so it does not introduce or fix a security vulnerability on its own.