Trezor firmware

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.

This commit only updates expected test result fingerprints (hashes) in a single test data file. It does not change any firmware, application, or cryptographic code. There is no indication of a security fix or vulnerability.

This commit refactors how Trezor hardware wallets display transaction confirmation screens for Ethereum and Solana operations. It replaces an older Rust-based confirmation flow with a newer MicroPython-based linear flow. The change is described by the developer as a cleanup step to remove an old UI component. There is no direct evidence in the commit that this fixes a security vulnerability, but any change to transaction confirmation logic carries a risk of accidentally altering what users see or approve.

This commit removes an unused user-interface flow called ConfirmOutputWithSummary from the Trezor firmware. It is a code cleanup: no security vulnerability is fixed or introduced, and no behavior that users currently rely on is changed.

This is a minor user-interface polish change for the Trezor hardware wallet's Eckhart layout. It hides a redundant header label when the header text is identical to the title text. There is no security relevance in the commit itself or in the supplied references.

This commit adds a new option to Trezor's on-screen confirmation dialogs that lets developers hide the cancel/cross button on the new 'Eckhart' device layout. It does not remove cancel from existing layouts, and the default behavior keeps the cancel button visible. The only place it is currently used is in one voting-related screen, where the user is still shown a 'Continue' button and can navigate back via an external menu. There is no direct evidence this is a security fix or vulnerability patch.

This commit updates the user interface code for the Trezor hardware wallet's newer 'Eckhart' layout. It adds support for an optional 'external menu' on the transaction summary confirmation screen, replacing the older internal menu when requested. The change is a UI refactor and feature flag wiring; it does not appear to fix or introduce a security vulnerability.

This commit updates the user interface code for the Trezor hardware wallet's 'Eckhart' layout. It makes the optional external menu actually appear when requested, by adding a menu icon to the screen header and passing the setting through to the screen component. There is no direct evidence this fixes a security vulnerability; it appears to be a normal UI feature implementation.

This commit is a routine feature addition for the Trezor hardware wallet: it adds support for two new TRON blockchain operations (unstaking/unfreezing TRX and claiming unfrozen TRX). It updates protocol definitions, generated message bindings, translations, and test fixtures. There is no indication of a security vulnerability or fix in the changes themselves.

This commit adds support for two new TRON transaction types on Trezor hardware wallets: unfreezing staked TRX and withdrawing expired unfrozen balances. It also renames a field in the freeze/unfreeze messages from 'frozen_balance' to 'balance' and removes unused smart-contract function signatures. The changes are a routine feature addition for TRON staking operations and do not, on their own, look like a security fix or vulnerability.

This commit simply changes a reported protocol version number from 2.0 to 2.1 in Trezor's THP (Trezor Host Protocol) code and updates the corresponding automated test snapshot hashes. There is no security fix or vulnerability present in the change itself. It is a preparatory feature commit to let host software detect an upcoming capability called 'device ACK piggybacking.'

This commit changes how the Trezor Python library sends low-level acknowledgment (ACK) packets during a newer USB protocol called THP. Instead of always sending a standalone ACK, it lets the next normal message (for example a button confirmation) carry the ACK 'for free.' This is described as a performance/correctness optimization, not a security fix. There is no direct evidence in the commit that it repairs a vulnerability.

This commit updates the Trezor Python client library (trezorlib) to support a new efficiency feature in the Trezor Host Protocol (THP) version 2.1. It allows the host computer to 'piggyback' acknowledgment (ACK) flags onto normal outgoing messages rather than sending separate ACK packets. The change is a feature addition, not a fix for a vulnerability, and the code comments explicitly describe backward-compatible behavior for older firmware.

This is a one-line code cleanup in the Trezor firmware's transport protocol code. It changes how a single sync bit is read from a byte, switching from a right-shift to a bitwise AND. The old and new code should behave identically when the byte only ever holds 0 or 0x80 in that bit position. The change is labeled a 'refactor' with '[no changelog]', so the project does not present it as a security fix. There is no direct evidence of an exploitable bug, but the change removes a subtle assumption that could matter if other bits in the byte were ever set.

This commit adds a new optional efficiency feature to Trezor's THP (Trezor Host Protocol) that lets acknowledgements (ACKs) be attached to normal messages instead of sent separately. It is a feature implementation, not a fix for a known vulnerability. The change includes a compatibility handshake so older hosts fall back to non-piggybacked ACKs. There is no direct evidence in the commit that this introduces a security bug, but any protocol change carries some risk of subtle state-machine issues.

This commit fixes a visual layout bug in the Trezor Safe 3 bootloader. A warning icon was being placed at the top-left of the screen instead of the top-right. The change simply moves the icon to the intended corner. There is no security issue here—only a cosmetic correction.

This commit is a minor user-interface change in the Trezor bootloader. It simply adds the build version number to the version string shown on screen. There is no security issue here.

This commit is a routine update of translated user-interface text strings for the Trezor hardware wallet. It changes wording in Czech, German, Spanish, French, and Portuguese translation files, adds a couple of empty placeholder strings for an upcoming Ethereum feature, updates the translation signature file, and refreshes the expected UI test screenshot hashes. There is no code change that affects security, cryptography, or device behavior.

This commit is a simple code cleanup: it renames an internal debug-only flag from 'is_cancel' to 'skip_test_visit' in two hardware wallet UI layouts and in the Python test helper. The behavior is unchanged. There is no security fix or vulnerability here.