Trezor firmware

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 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 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 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 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 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.

This is a routine dependency update that bumps the Python urllib3 library from version 2.6.3 to 2.7.0. It only changes package metadata files (pyproject.toml and uv.lock) and contains no code changes. There is no indication in the commit of any security issue being fixed.

This commit adds a third-party diagram-drawing library (Mermaid) to the project's documentation build. It only touches documentation configuration and static JavaScript files used to render diagrams in the generated docs. There is no change to the Trezor firmware, wallet code, or any security-sensitive component.

This commit is a routine housekeeping update to the project's Python dependency lock file. It upgrades four development or utility packages to newer versions that no longer need certain sub-dependencies, so those sub-packages are removed. There is no indication of a security fix or vulnerability being addressed.

This commit updates the list of recognized Tron TRC-20 tokens in Trezor firmware. It adds six new tokens (WBT, WTRX, SUNOLD, AINFT, sTRX, Klever), restructures how token addresses are stored, and adds internal checks that the stored byte addresses match the public TronScan addresses. There is no security vulnerability visible in the change itself.

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 is a routine cleanup of the project's automated build and test configuration. It removes unnecessary uses of a special 'full dependencies' mode in the Nix shell for some CI jobs, while explicitly adding it where it is actually needed. There is no change to the Trezor firmware code that runs on devices, and no security issue is present.

This is a routine internal cleanup of the project's automated testing setup. It changes how a test-support program (the 'Tropic model server') is started during continuous integration (CI) runs, switching from a Poetry-based Python environment inside a vendored dependency directory to the project's own 'uv' Python environment. There is no change to the firmware, wallet logic, cryptography, or any code shipped to users.

This commit fixes a misleading error message in the Monero key image sync feature on Trezor hardware wallets. Previously, when the cryptographic hash check failed, the device incorrectly reported 'Invalid number of outputs' instead of 'Invalid hash'. This is a user-facing string correction with no direct security vulnerability in the underlying check itself.

This commit only changes a user-facing label on Trezor hardware wallets. The old text 'Review details to claim rewards.' is replaced with 'Claim rewards from Merkl.xyz' in translation files and generated Rust code. There is no code behavior change, no bug fix, and no security relevance.

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 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 a new automated CI check that verifies the project's Python dependency lock file (uv.lock) is up-to-date. It does not change any firmware code, fix a bug, or alter security-critical behavior. It is purely a build/development hygiene improvement.

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 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.