Trezor firmware

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 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 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 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 is a hardening change to Trezor's build tooling. It tells the Python package manager 'uv' not to use any package uploaded to PyPI in the last 30 days, which reduces the risk of accidentally pulling in a freshly compromised dependency. It also downgrades the 'Mako' template library from 1.3.12 to 1.3.10 and switches the build system from 'hatchling' to 'flit' in several sub-projects. The commit message explicitly says the goal is to limit supply-chain compromise exposure.

This commit adds support for displaying human-readable confirmation screens when users claim rewards through the Merkl/claim.xyz rewards distributor on Ethereum. It replaces a placeholder that previously forced blind signing for these transactions. The change lets the Trezor show the token and amount being claimed instead of just raw transaction data, but only for a specific known distributor address and only when the claim is for the signer themselves.

This commit adds support in Trezor's Ethereum 'clear signing' feature for two new data shapes: nested arrays (arrays inside arrays) and fixed 32-byte values (bytes32). It also renames an internal helper function from `_request_definitions` to `request_definitions`. The changes are framed as a normal feature addition with no changelog entry. There is no direct evidence in the commit that this fixes a security vulnerability, but any change to transaction parsing logic can affect how the device interprets maliciously crafted data.

This commit only changes Python unit tests for the ChaCha20-Poly1305 encryption code in the Trezor firmware test suite. It does not modify the actual cryptographic implementation, device firmware, or any production code. The changes add test cases to verify that decryption correctly requires and validates the authentication tag (MAC). There is no security vulnerability in this commit itself.

This commit is a routine code cleanup that splits one combined AES-GCM encryption/decryption class into two separate classes: one for encryption and one for decryption. It does not fix a security bug or introduce a new vulnerability. The change makes the API clearer and prevents accidental misuse, such as trying to decrypt with an encryption-only object.

This commit is a code cleanup, not a security fix. It creates a new, more specific error type called AuthenticationError and changes AES-GCM and ChaCha20-Poly1305 decryption to throw that error instead of a generic RuntimeError when authentication fails. It also updates the Python code that catches those errors to catch the new type. The cryptographic behavior itself is unchanged.

This commit only changes Python unit tests for the AES-GCM cryptography code in the Trezor firmware. It updates existing tests to pass an expected authentication tag to the finish() method and adds new tests that check the code correctly rejects missing, wrong-length, or invalid tags. There is no change to the actual cryptographic implementation or firmware behavior, so this commit does not introduce or fix a live security vulnerability by itself.

This commit hardens how Trezor devices verify AES-GCM authentication tags during decryption. Previously, callers computed the tag and then compared it separately using a constant-time helper. Now the comparison is performed inside the cryptographic finish routine itself, using a constant-time equality check. This reduces the risk that a future caller forgets to verify the tag or uses a non-constant-time comparison, which could allow an attacker to tamper with encrypted messages or recover secrets through timing analysis.

This commit hardens how a Trezor hardware wallet checks the authentication tag when decrypting data protected by the ChaCha20-Poly1305 cipher. Previously, the Python caller compared the expected tag with the computed tag using a helper called utils.consteq. Now the comparison is done inside the low-level C module using a constant-time equality function, and decryption callers must pass the expected tag directly to finish(). This reduces the risk of a developer forgetting to verify the tag or using a non-constant-time comparison, which could let an attacker tamper with encrypted secrets.

This commit adds a new utility function called `consteq` that compares two chunks of memory in a way that takes the same amount of time regardless of how similar the chunks are. It is intended to help prevent timing-based attacks in the future, but the commit itself only extracts and compiles the helper; it does not change any existing security-sensitive comparison or fix a known vulnerability.

This commit is a routine code cleanup (chore) that splits one combined ChaCha20-Poly1305 encryption/decryption class into two separate classes: one for encryption and one for decryption. It does not fix a security bug, add a new feature, or change cryptographic behavior. All existing callers are updated to use the appropriate new class. The change is purely structural and makes the API clearer.

This is a tiny user-interface bug fix. It moves a translation lookup so that the 'Enter PIN' message is shown in the correct language on the boot screen instead of always appearing in English. There is no security vulnerability here.

This commit simply removes two unused Ethereum address and chain-list constants from a Python file. There is no functional code change, no bug fix, and no security relevance.

This commit is a simple revert that brings back previously removed display definitions for the LiFi decentralized exchange aggregator on Trezor hardware wallets. It restores human-readable transaction labels (such as 'Amount to Send' and 'Recipient') when users sign LiFi swap transactions. There is no indication of a security bug, vulnerability, or malicious change in the code itself.

This commit removes the special on-screen 'clear signing' definitions for LiFi swap transactions on Trezor hardware wallets. From now on, LiFi transactions will be shown as generic contract interactions rather than nicely labeled swaps. There is no indication this fixes a security vulnerability; it appears to be a product decision to stop supporting LiFi's specific transaction formatting.

This is a routine code reorganization in the Python trezorlib library. It moves two helper classes into a new module and moves a user-interface file into the command-line interface package. No security-sensitive behavior is changed, no bugs are fixed, and no vulnerabilities are introduced.

This commit removes a feature that would have sent a 'MCU attestation'—a cryptographic proof signed by the device's microcontroller—during device authentication. The change itself is a simple deletion of the attestation code and its changelog entry. There is no direct evidence in the commit of a security vulnerability; it appears to be a product decision to stop sending this proof, possibly because the feature was not ready or was being reconsidered. It reduces the amount of identity information the device exposes during authentication.

This is a routine automated dependency update by Dependabot, bumping the Python Mako templating library from version 1.3.11 to 1.3.12. The change only updates version numbers and package hashes in the project's dependency files. There is no indication in the commit itself that this fixes a security issue, and no security advisory or incident details were provided.

This commit fixes a bug in the Rust Trezor client library used to talk to Trezor hardware wallets. When signing a large Ethereum transaction, the device may ask the user to confirm by sending a 'button request' in the middle of streaming the transaction data. Previously, the client did not handle that mid-stream request, so the signing process could hang or fail. The fix wraps each streamed chunk's response with the existing interaction handler so button requests are processed correctly. A new example and a regression test for a 10 KB transaction are added.

This commit is a cleanup of how the word 'const' is used in the Trezor firmware's ed25519 cryptographic code. Previously, the code defined a custom 'CONST' macro that meant 'const' on newer compilers and nothing on older GCC versions. The commit removes that macro and uses plain 'const' everywhere. It also adjusts a Rust build script comment and compiler flag. There is no indication in the commit that this fixes a security vulnerability or changes runtime behavior.

This commit is a straightforward internal code refactor. It renames a build feature flag from 'applet' to 'applets' and replaces the KERNEL preprocessor guard with a new USE_APPLETS guard in the relevant source files. There is no change to actual security logic, no bug fix, and no indication of a vulnerability being addressed.