Trezor firmware

This commit is a routine version bump for the Python 'trezor' package from 0.20.2 to 0.20.3 after a release. It only changes two version strings in packaging files and contains no functional code changes.

This is a cosmetic user-interface change for the Trezor hardware wallet. It adds a trailing colon to labels shown when a user is reviewing Ethereum EIP-7702 authorization or revoke actions. There is no security impact: no code logic, cryptography, transaction parsing, or signing behavior is changed. The only side effect is that on-screen text labels now end with a colon, and the corresponding UI test snapshots (fixtures.json) were updated to match the new appearance.

This commit adds a build-time check to ensure that a documentation file (OPTIONS.rst) for the trezorctl command-line tool is up to date. It does not change any security-sensitive code, cryptography, device firmware, or user-facing behavior. It is purely a developer tooling and documentation freshness check.

This is a routine internal code cleanup in the Python Trezor library. It moves the logic that answers the hardware wallet's mid-transaction definition requests from one module to another and changes the public API from accepting a callback function to accepting a definition source object. There is no indication this fixes or introduces a security vulnerability; it is a refactor to make the code easier to test and maintain.

This is a one-character typo fix in a Monero progress message. A missing backslash meant the text 'hashing inputs' and the progress counter were joined on the same line instead of appearing on separate lines. It has no security relevance.

This commit updates a design document for Trezor's new 'Trezor Hello Protocol' (THP) pairing flow. It adds checks intended to stop a malicious computer from sending specially crafted X25519 public keys (so-called low-order points) that would make the shared secret predictable or all-zeroes, potentially allowing the computer to skip the user code-entry step and pair with the device without authorization. The change is only to documentation/specification; no actual firmware code is modified in this commit, so the real-world risk depends on whether the implementation already follows or ignores the new checks.

This commit only regenerates a documentation file (OPTIONS.rst) listing available command-line options. It adds two newly supported commands to the help text: one for signing Ethereum EIP-7702 authorizations and one for signing Stellar Soroban authorizations. There are no code changes, no security fixes, and no functional changes in this commit.

This commit is a large internal refactoring that moves time-related code (Duration, Instant, sleep, tick counters) from one Rust module to another shared system module so it can be reused more cleanly. It does not change what the code does; it only reorganizes where the definitions live. There is no obvious security bug introduced, but any big refactor carries a small risk of accidental behavior changes.

This commit changes a single on-screen label in the Trezor bootloader from lowercase 'Change fw vendor' to uppercase 'Change FW vendor'. It is purely a cosmetic wording fix with no security relevance.

This commit simply bumps a local vendor package called 'ts-tvl' from version 2.4 to 2.5 in a Python lock file. There is no code change shown, no description of any security issue, and no supplied references indicating this is a security fix. On its own, this looks like a routine dependency/version maintenance task.

This commit adds support in Trezor's Ethereum clear-signing feature for transactions that contain multiple embedded subcalls (like a multicall). Previously, only a single embedded call could be clearly displayed. The change lets the device show each subcall separately with labels like "(Subcall #1)" and handles both a single shared recipient address or a parallel list of recipients. It is a feature addition, not a fix for a known vulnerability.

This commit only adds new automated tests for Trezor's Ethereum 'clear signing' feature. It includes a test case for an Aave multi-call transaction, a matching test data blob, and expected screen snapshots for different device models and languages. There are no changes to the actual firmware code that runs on the device, so this commit does not introduce or fix a security vulnerability.

This commit only updates translated text strings in five language files and refreshes the translation signature metadata. There are no code, logic, or security-related changes.

This commit only updates a test data file (tests/ui_tests/fixtures.json) containing expected screenshot hashes for automated UI tests. It does not change any firmware, application, or cryptographic code. The hash changes are expected when the device's on-screen appearance changes for any reason (text, layout, language, or unrelated code changes). There is no indication of a security fix or vulnerability in this commit itself.

This commit is a routine synchronization of translated user-interface text for the Trezor hardware wallet. It only changes wording in Czech, German, Spanish, French, and Portuguese translation files. There is no code change, no security fix, and no behavior change.

This commit only updates expected test result hashes (called 'fixtures') in a single test data file. It does not change any actual device firmware code, cryptographic logic, or user-facing behavior. The hash changes are consistent with a routine refresh of screen-shot-style UI test baselines after unrelated code or translation updates. There is no indication of a security fix or vulnerability.

This commit simply updates a metadata file that records a digital signature (a 'merkle_root') for translation data in a Trezor hardware wallet. There is no code change, no bug fix, and no security issue visible in the diff. It appears to be a routine administrative update to keep the signature record in sync with the latest translation content.

This commit is purely scaffolding for a new Ethereum clear-signing feature. It adds a new data type (FORMATTER_CALLDATA), two new optional fields (callee_path and selector) to message definitions, and two new user-facing text labels ('Subcall' and 'Subcall to'). There is no actual implementation of parsing, validation, or display logic here, and no security vulnerability is visible in the diff.

This commit fixes a user-interface bug in Trezor's Ethereum 'clear signing' flow where the transaction's native ETH amount could be shown twice on the device screen. The old code tried to avoid duplication by checking whether an 'AmountFormatter' field was present, but that check missed cases where the same amount was rendered by other field types. The new code compares the actual rendered strings and suppresses the summary amount only when it exactly matches a field already displayed. There is no security vulnerability here; it is purely a display-quality fix.

This commit is a routine maintenance update labeled 'chore: update fixtures'. It adds new expected test result hashes for Ethereum transaction display tests, updates a translation signature metadata file, and reverts a dependency version number in a lock file. There are no code changes that affect how the Trezor device operates or secures funds.

This commit only adds new data structures and an enum value for a future 'enum formatter' feature in Trezor's Ethereum clear-signing support. It does not change any existing behavior, add parsing logic, or fix a bug. There is no security issue visible in this change.

This commit adds a new display formatter for Ethereum clear signing. It lets a transaction descriptor map numeric enum values (like 1 or 2) to human-readable labels (like 'stable' or 'variable') on the Trezor screen. The change is purely additive and includes tests. There is no indication it fixes a security bug or introduces a vulnerability; it is a feature implementation.

This commit only adds a new automated test case for an existing Ethereum transaction display feature. It does not change any production firmware code, so it cannot introduce a security vulnerability or fix one. It is purely a test-data addition.

This commit adds a new Trezor firmware feature called 'clear signing' for nested Ethereum calls. It lets the device understand when a transaction wraps another contract call (like a router or multicall) and tries to show the user readable details about the inner call instead of just a blob of hex. The change is a feature addition with built-in safeguards: nested parsing is limited to one level, ambiguous fields like sender and value are blocked inside nested calls, and failures fall back to showing raw hex rather than aborting the whole transaction. There is no indication in the commit that this fixes a known security bug; it reads as a defensive new capability.

This commit is a test-only addition for Trezor's Ethereum 'clear signing' feature. It adds new test cases and makes a small production-code tweak so that enum display-formatters can accept byte values (converted to integers). The change is not described as a security fix, and the production change is minor and defensive: it broadens accepted input types rather than fixing a crash or bypass. There is no evidence of a disclosed vulnerability or exploit.