Trezor firmware

This update fixes how Trezor displays Solana transactions that use Address Lookup Tables (ALTs). Previously, the device could misidentify or fail to show the real recipient when an ALT was involved, which might let an attacker trick a user into approving a transfer to an unexpected address. The patch also blocks ALT references in payment requests and some staking flows where the device cannot safely verify the destination.

This commit is a documentation-only changelog update for the Trezor firmware releases core 2.11.2 and bootloader 2.1.17. It does not change any code. The changelog lists several previously fixed security issues, including bugs in Solana account handling, EIP-712 domain caching, and an out-of-memory fix. Because the actual code changes happened in earlier commits, this single commit cannot introduce or directly fix a vulnerability, but it confirms the vendor considers multiple items security-relevant for the release.

This commit updates a QA/testing bootloader binary and its recorded cryptographic hash for the T3W1 hardware model. It is a routine development chore with no visible security fix or vulnerability.

This commit simply updates the version of a third-party GitHub Action used to install the Nix package manager in Trezor's automated build and test workflows. It is a routine dependency bump with no visible security relevance to the Trezor firmware or device itself.

This commit fixes a labeling error in the Trezor firmware's protocol definitions. Two message types used for device authenticity checks had their directions swapped: one was marked as outgoing when it should be incoming, and the other as incoming when it should be outgoing. The fix only changes metadata annotations and the matching generated Rust code; it does not change actual message handling logic. Because the patch is small and limited to generated descriptors, the direct security impact is low, but incorrect wire direction metadata could theoretically confuse host software or protocol validation tools.

This commit updates the on-screen confirmation prompts shown when signing Stellar transactions on Trezor hardware wallets. It does not change how transactions are validated or signed, but it reorganizes and improves the clarity of what the user sees before approving. The changes are purely user-interface related, with updated test snapshots reflecting the new screen layouts.

This commit is a user-interface improvement for Tron (TRX) transfers on Trezor hardware wallets. It changes the on-device confirmation screens to show the sending account name, derivation path, recipient address, and amount in a clearer layout. There is no indication it fixes a security vulnerability; it is a usability and consistency refactor.

This commit is a routine housekeeping change that only updates version numbers in several files. It does not change any program logic, fix any bug, or alter any security behavior. There is nothing here that could be exploited or that affects user security.

This commit adds a user-facing 'Tap to Wake' on/off toggle to the device menu on the Trezor T3W1 hardware wallet. It stores the preference in device storage and applies it at startup and when settings are reloaded after unlocking. There is no security issue visible in the change.

This commit is a straightforward build-system wiring change for the Trezor T3W1 hardware wallet. It enables a feature called USE_TOUCH_WAKEUP, which lets the device wake from a low-power suspend state when the touch screen is touched. The change only affects how firmware is compiled for specific T3W1 revisions and does not alter security-critical code, cryptographic operations, or user data handling. There is no indication this is a security fix or vulnerability patch.

This commit adds a new power-saving feature for Trezor hardware wallets: the device can now optionally wake from suspend when the touchscreen is touched. It restructures how the display and touch drivers suspend and resume, choosing between a 'light sleep' path (screen stays powered, touch sensor stays armed) and a 'full shutdown' path. The change itself is a feature implementation, not a fix for a known vulnerability, and there is no direct evidence in the commit or references that it addresses a security bug.

This commit adds a new user-facing setting called 'tap to wake' to the Trezor hardware wallet firmware. It lets users choose whether tapping the touchscreen wakes the device, and stores that preference in device memory. It also adds the low-level system calls needed for the firmware to turn the feature on or off. There is nothing in the commit that fixes a bug or addresses a security vulnerability.

This commit simply adds a way for the device's Python code to ask whether the hardware supports waking from sleep by touch, and to turn that feature on or off. It is a normal feature-exposure change with no security bug visible in the diff.

This commit only adds a help description (docstring) to an existing command-line option. No code behavior changed, so it has no security effect.

This commit is a routine translation update. It removes a few unused text strings, changes some translations to use per-device-style wording, and updates the internal offsets in generated translation tables. There is no code that handles secrets, cryptography, user authentication, or device commands being changed. It is not a security patch.

This commit only updates a JSON file that controls which on-screen text strings are allowed to be left blank (untranslated) for different Trezor device screen layouts. It adds and reorganizes string identifiers so the translation-blanking rules match the latest user interface. There is no change to security logic, cryptography, or how the device handles secrets.

This commit simply removes four unused English translation text strings from a language file. There is no code change, no functional change, and no security relevance.

This is a routine internal tooling change for managing translation files. It adjusts how translation text downloaded from the Crowdin service is cleaned up before being saved, and skips processing English-language 'translations' because they are empty and would overwrite the existing English file. There is no security relevance.

This commit only updates translated text strings in Czech, German, Spanish, French, and Portuguese, plus the translation signature metadata. There are no code, logic, or security-related changes.

This commit updates Czech translation strings and refreshes the digital signatures that authenticate those translations, plus updates expected test screenshots. There is no code change that affects security behavior, cryptography, or how the device protects secrets. It is a routine localization maintenance patch.

This commit only updates a documentation file (OPTIONS.rst) to list two newly added command-line options. It does not change any executable code, cryptographic logic, or security-sensitive behavior. There is no security issue in the commit itself.

This commit only updates documentation text. It replaces the product name 'Trezor T' with 'Trezor Core' in two README/markdown files and adds a new device model code (T3W1 for Trezor Safe 7) to a support list. No code, logic, or security behavior is changed.

This commit only changes user-visible text strings in the Trezor firmware. It adds or removes periods and makes tiny wording tweaks (for example, 'Language changed successfully' became 'Language changed successfully.') for specific device themes called Delizia and Eckhart. There is no code behavior change, no new feature, and no security fix.

This commit adds support for Bitcoin Signet, a public testing network for Bitcoin, to Trezor firmware. It is a routine feature addition with no security-relevant code changes. The commit only adds a new coin definition, updates generated coin-info tables, and adjusts internal tooling to treat Signet like the existing Testnet and Regtest networks.

This commit adds a new command-line option to the Trezor Python tool (trezorctl) that lets users request a public key (xpub) without the usual version/magic bytes being adjusted for the specific coin and script type. This is described as a convenience for working with 'output descriptors', a modern Bitcoin wallet format. There is no direct security bug here; it is a feature change in a client-side utility.