Trezor firmware

This commit only reorganizes existing text in a changelog file. It moves one security-related bullet point from a standalone 'Security' section into another 'Security' section lower down, with no changes to actual firmware code or behavior. There is no functional change to review from a security perspective.

This commit changes a GitHub Actions CI workflow so that firmware artifact sizes are reported separately for 'normal' and 'debuglink' builds instead of being merged into one list. It is purely a reporting/visibility tweak in the build pipeline and does not touch any firmware code, cryptography, or device behavior.

This commit adds a developer-only mock/emulator for a new hardware component called N4W1. It is gated behind debug builds (PYOPT='0') and only for the T3W1 device model. It does not change normal user-facing wallet behavior; it only provides a way for engineers to simulate the N4W1 chip during testing.

This commit only adds new message definitions for a debug-only feature called N4W1 emulator. It does not change any firmware logic, cryptographic code, or user-facing behavior. The messages are marked as DebugLink traffic, which is intended for testing and emulator use, not for production devices. There is no direct security vulnerability visible in this change, but adding debug interfaces always slightly increases the attack surface if those interfaces are accidentally reachable in production.

This commit is a user-experience polish change for the Trezor hardware wallet's touchscreen interface. It changes when the device vibrates (haptic feedback) in scrollable menus so that the vibration happens when the user lifts their finger and confirms a tap, rather than when they first touch the screen. This prevents confusing vibrations while the user is merely scrolling through a long menu. There is no security-relevant change here.

This is a routine code cleanup commit that removes or conditionally compiles unused Rust imports in two user-interface files. It does not change program behavior, fix a bug, or alter any security-relevant logic.

This commit adds a new automated CI job that reports the sizes of built firmware binary files. It does not change any firmware code, crypto logic, or device behavior. There is no security-relevant change.

This commit is a routine synchronization of translated user-interface text strings for Trezor hardware wallets. It updates wording in Czech, German, Spanish, French, and Portuguese translation files. There are no code changes, no security fixes, and no functional behavior changes.

This commit is a routine maintenance update for translation files and test snapshots. It changes one Spanish tutorial sentence to be clearer, updates the cryptographic signature metadata for the translation files, and refreshes many expected visual-test hashes. There is no code that runs on the device or handles secrets, and nothing in the commit suggests a security fix or vulnerability.

This commit only adds two new user-facing text strings ('Confirm contract' and 'Intent') to the Trezor firmware's translation system. It does not change any code logic, security checks, or transaction handling. There is no indication this is a security fix or introduces a vulnerability.

This commit only adds a new automated test case for the Trezor hardware wallet's backup/recovery feature. It checks that a specific SLIP-39 advanced setup (2 groups of 16-of-16 shares) works correctly. There are no changes to the actual wallet firmware, user-facing behavior, or security-sensitive code.

This commit fixes a deadlock in the Trezor hardware wallet's USB communication protocol (THP). Previously, when sending data, the device would stop reading incoming USB messages while waiting to re-send data, which could cause both sides to get stuck. The fix makes the device keep reading incoming messages in parallel with retransmissions, so delayed acknowledgments no longer freeze communication.

This commit fixes a small logic ordering bug in the Trezor hardware wallet's on-device menu. Previously, the special 'RefreshMenu' action was checked only after the code tried to find a normal handler for the action. If 'RefreshMenu' had no handler, the device could raise a runtime error instead of refreshing the menu. The fix moves the refresh check before the handler lookup, so Bluetooth Low Energy (BLE) events that trigger a menu refresh work correctly. There is no direct evidence this is a security vulnerability; it appears to be a UI/functional bug.

This is a small compatibility fix in the Trezor Python library. Older Trezor firmware versions did not return the wallet's 'root fingerprint' in one specific place, so the library was failing or warning users. The change makes the library read the same fingerprint from an older, always-available field instead. It is a bug fix for backward compatibility, not a security vulnerability patch.

This commit fixes a low-level bug in how the Trezor firmware converts small integers into an internal MicroPython object representation. Previously, when converting a signed integer, the left-shift operation could discard the top (most significant) bit because it was done on a signed type before being cast to an unsigned type. The fix casts the value to an unsigned type first, preserving all bits. This is a correctness fix in the Rust/MicroPython bridge; it could affect any code path that passes integers to or from MicroPython, but the commit itself does not describe a specific security vulnerability or exploit.

This commit only changes user-facing text strings and the rules that allow certain strings to be blank for specific Trezor device layouts. There is no code that handles secrets, cryptography, memory, network, or user authorization. It is a routine localization and UI-label update with no security relevance.

This commit is a routine regeneration of translation files and UI test fixtures. It updates on-screen text strings (for example changing 'Hidden wallet' to 'Passphrase wallet' and adjusting wording for some prompts), removes one unused translation key, and refreshes the expected UI screenshots used by automated tests. There is no code that handles secrets, cryptography, user input validation, or device behavior—only text labels and test expectations.

This commit simply turns a build-time compiler error message into a plain comment. The file is a generated helper used to add missing text labels (Qstrings) to the device's MicroPython frozen string pool. The change removes a noisy but harmless '#error' directive that was being printed during every build. There is no security relevance.

This commit simply raises the minimum supported Python version for the Trezor firmware build tooling from Python 3.9 to Python 3.10. It updates documentation, the project configuration file, and the dependency lock file to remove Python 3.9-specific package wheels. There is no change to the firmware code, device behavior, or security-sensitive logic.

This is a routine vendor dependency bump (updating a tracked submodule called ts-tvl) with no visible code changes, security claims, or incident details in the provided materials. There is nothing here that can be independently assessed as a security issue.

This commit updates two widely used Python helper libraries, 'cryptography' and 'cffi', in the project's dependency lock file. It is a routine maintenance change. The newer versions may fix security bugs in those libraries, but the commit itself does not describe any specific vulnerability, attack, or exploit. There is no direct evidence in the commit that Trezor devices or user funds are at risk.

This commit adds the initial protocol and code-generation scaffolding for a new Tron blockchain feature: voting for Super Representatives (called VoteWitnessContract). It defines the new message types in protobuf, regenerates the corresponding Python and Rust message bindings, adds translation strings, and includes test fixtures. It does not contain the actual firmware logic that would parse, validate, display, or sign these votes, so there is no directly exploitable security issue in this patch alone.

This commit adds support for a new TRON blockchain operation called VoteWitnessContract to Trezor hardware wallets. It lets users vote for up to 9 TRON network validators (called Super Representatives) directly from the device, with on-screen confirmation before signing. There is no indication this fixes a security bug; it is a feature addition.

This is a small bugfix in the Trezor Python command-line tool's debug-only commands. Two debug helpers were trying to reach the device's debug transport through an outdated path (session.client.protocol.transport) and were updated to the correct path (session.client.transport). These commands are only used in development/testing and do not affect normal wallet operations or end-user security.

This commit only updates a documentation file to turn a plain text reference into a clickable hyperlink. No code, logic, or security behavior changed.