Trezor firmware

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 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 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 updates the Monero ChaCha20-Poly1305 decryption helper in Trezor firmware to use the cryptographic library's built-in tag verification instead of a custom comparison. The old code computed the authentication tag and compared it to the expected tag using a helper called monero.ct_equals. The new code passes the expected tag directly into cipher.finish(), letting the library verify it. This is a defensive hardening change that reduces the risk of subtle timing or comparison bugs in authentication-tag checking, which could theoretically allow forged or tampered data to be accepted.

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 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 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 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 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 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 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 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 is a minor user-interface cleanup for the Trezor hardware wallet's Eckhart layout. It changes one default button label parameter from a hardcoded translated string to the system's default confirmation verb, and updates the corresponding screen-shot test hashes. There is no security-relevant change visible in the code.

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