Trezor firmware

This commit only adds new on-screen text strings for a future backup feature called N4W1. It does not change any security logic, cryptographic code, or user-accessible behavior. There is no indication of a vulnerability or security fix.

This commit changes how Trezor firmware handles Ethereum transaction data (calldata). Previously, the code only tried to 'clear sign' transactions where the entire calldata fit in the first chunk. Now it stores and processes up to 4 KB of calldata across multiple chunks, and gives up gracefully if the data is too large. The change appears to be a hardening/capacity improvement rather than a fix for an active exploit, but it removes a risky assumption that all data is present in the initial chunk.

This commit is a feature expansion for Trezor's Ethereum 'clear signing' system, which decodes smart-contract call data so users see human-readable details instead of raw hex. It adds support for dynamic Solidity types such as strings, byte arrays, structs, and arrays. The change is large and refactors how transaction data is parsed and presented. It does not appear to be a disclosed security fix, but because it handles untrusted transaction data, any parsing bugs could in principle let a malformed transaction bypass warnings or crash the device. The diff itself shows explicit bounds checks and validation, which is a positive sign, but the new code paths are complex and have not been externally audited in the provided materials.

This commit updates the Trezor Ethereum app's 'clear signing' feature so it can handle data formats that slice inside arrays or structs (for example, taking only a portion of a list). It is a small feature addition, not a fix for a known security bug. There is no evidence in the commit or supplied references that this resolves an active vulnerability.

This commit changes how Trezor hardware wallets display and confirm Ethereum transactions that use 'clear signing' (human-readable descriptions of smart-contract calls). Previously, clear signing could be attempted for transactions whose data is split across multiple chunks. Now, clear signing is used only when the entire transaction data fits in the first chunk. If the clear-signing parser fails on that first chunk, the device falls back to the standard raw-data confirmation. The change is described as a feature limitation, not a security fix, but it removes a code path where multi-chunk data might be parsed before all chunks are available or confirmed.

This commit changes how the Trezor hardware wallet formats token amounts shown on screen during Ethereum transactions. It adds support for treating certain addresses as the network's native currency (like ETH on Ethereum mainnet) rather than as ERC-20 tokens when displaying amounts. There is no indication in the commit that this fixes a security vulnerability; it appears to be a user-interface correctness feature.

This commit removes built-in 'clear signing' support for the 1inch decentralized exchange from Trezor Ethereum firmware. Clear signing makes complex crypto transactions easier to read and verify on the device screen. Removing it does not create a new security hole, but users interacting with 1inch will now see less human-readable transaction details, which can make it harder to spot malicious or mistaken transactions. It is a feature rollback, not a vulnerability fix.

This commit enables Trezor hardware wallets to use SLIP-24 payment requests when signing ERC-20 token transfers. Previously, payment requests were rejected for any contract interaction, including ERC-20 transfers. The change adds a new code path that verifies the token transfer amount and recipient against a signed payment request before showing the confirmation screen. It is a feature-enablement change rather than a fix for an active vulnerability, but it touches security-critical signing flow code.

This commit only adds new automated tests for Ethereum transaction data parsing. It does not change any production code, so it cannot introduce a security vulnerability by itself. The tests verify that the device correctly rejects malformed Ethereum addresses and oversized numeric values.

This commit refactors how Trezor firmware handles unknown Ethereum tokens when showing transaction details on screen. Previously, if a transaction involved an unknown token, the device showed one generic warning. After this change, the code can detect and warn about multiple unknown tokens within a single transaction's data. It is a defensive code improvement rather than a fix for a known exploit.

This commit only updates German translation text and the corresponding test snapshots (expected screen hashes). It removes a few old variant translations for the term 'hidden wallet' and standardizes it to 'Passphrase-Wallet'. There is no code change and no security relevance.

This commit is a routine maintenance update for translation files and test snapshots. It changes one French translation string, updates a cryptographic signature record for the translation set, and refreshes many expected visual test hashes. There is no code change that affects security functionality, and nothing in the commit suggests it fixes or introduces a vulnerability.

This commit adds support for native Solana (SOL) payment requests using the SLIP-24 standard on Trezor hardware wallets. It extends existing token payment-request logic to also cover plain SOL transfers, and updates tests and UI fixtures accordingly. There is no direct evidence in the commit of a security vulnerability, but any change to payment verification and confirmation flows carries a low level of implementation risk.

This commit refactors how Trezor handles Stellar cryptocurrency transaction confirmations when a 'payment request' is used. Previously, the device might skip confirming individual operations during payment requests. The change ensures that only simple payment operations are allowed in payment requests, rejects invalid operation types, and still requires user confirmation. It also adds a test case for an invalid operation in a payment request. The commit appears to be a defensive hardening change rather than a fix for an active exploit.

This update changes how Trezor hardware wallets confirm Ethereum transaction data. Previously, the device asked the user to approve the entire data payload before it began hashing the transaction. Now, it confirms data piece by piece while the transaction is being hashed, and only shows the final transaction summary right before signing. The change is marked as a security fix in the project's changelog, suggesting the old behavior could let a user approve data that does not match what is actually signed.

This commit is a routine maintenance update for translation files and test snapshots. It changes one Spanish tutorial sentence to be clearer, updates the cryptographic signature metadata for the translation files, and refreshes many expected visual-test hashes. There is no code that runs on the device or handles secrets, and nothing in the commit suggests a security fix or vulnerability.

This commit adds the initial protocol and code-generation scaffolding for a new Tron blockchain feature: voting for Super Representatives (called VoteWitnessContract). It defines the new message types in protobuf, regenerates the corresponding Python and Rust message bindings, adds translation strings, and includes test fixtures. It does not contain the actual firmware logic that would parse, validate, display, or sign these votes, so there is no directly exploitable security issue in this patch alone.