Trezor firmware

This commit fixes how Trezor displays details for certain 1inch cryptocurrency swap transactions. Previously, the device tried to interpret a parameter called 'pools' as a list of plain numbers, but it actually contains packed binary data. The change makes the device show the raw bytes as hexadecimal instead of trying to decode them as numbers. This is a display/clarity fix rather than a direct theft-of-funds bug, but mis-displaying swap details could in theory help an attacker trick a user into approving a malicious transaction.

This commit only adds new test cases for Ethereum transaction signing on Trezor hardware wallets. It includes sample swap transactions from services like 1inch, LiFi, and Uniswap, plus a large-data test case. There is no change to the actual firmware or wallet code—only test data and a test list are added. It does not introduce or fix a security vulnerability.

This commit is a code refactor that reorganizes how Trezor handles Ethereum transaction display logic. It splits existing code into new modules for 'clear signing' and staking, and changes how token amounts and addresses are formatted before being shown to the user. There is no direct evidence in the commit that this fixes a security vulnerability; it appears to be preparation for supporting a new Ethereum standard (ERC-7730). However, because it touches the code that decides what users see on screen before signing transactions, any bug introduced here could affect how clearly users understand what they are approving.

This commit adds human-readable labels for certain cryptocurrency swap transactions on Trezor hardware wallets. It does not change how transactions are validated or signed; it only improves what the user sees on the device screen. There is no direct security vulnerability in the change itself, but any mistake in the labels could mislead a user about what a transaction does.

This commit is a code cleanup that moves the on-screen confirmation flow for Ethereum 'clear signing' into the device's UI layout modules. It also adds a final summary screen showing the maximum transaction fee. There is no direct evidence of a security vulnerability being fixed; it appears to be a user-interface refactor. However, adding the fee summary screen is a security-relevant improvement because it gives users more complete information before they approve a transaction.

This commit simply adds two new countries, South Africa and the United Arab Emirates, to the regulatory information screen on Trezor's Eckhart hardware wallet layout. It includes new flag icons, updates the list of regulatory zones, and refreshes automated test snapshots. There is no security-relevant change.

This is a routine build-fix refactor for the Trezor hardware wallet's bootloader UI. It removes the 'const' keyword from a few Rust functions and splits a battery icon rendering helper so the bootloader build succeeds. There is no security-relevant change visible in the diff.

This commit makes small visual adjustments to the Trezor hardware wallet's homescreen layout. It tweaks pixel alignment of status icons and fixes how a shadow behind a scrolling label moves during animation. There is no security-relevant change.

This commit is a straightforward performance optimization for the user interface on Trezor's newer 'Eckhart' layout. It pre-calculates and stores values like battery percentage text and page counter positions so they don't have to be recomputed every time the screen is redrawn. It also fixes a minor visual alignment issue with a small connection indicator dot. There is no indication this change fixes a security vulnerability.

This commit is a user-interface polish change for the Trezor hardware wallet's homescreen. It changes when notification-related buttons and hints appear on screen, making them show up only after a small LED indicator toggles, unless animations are disabled or the notification is an alert. There is no security-relevant behavior in the change.

This commit is a user-interface feature for the Trezor hardware wallet. It adds a small visual indicator (a connection icon) next to the 'Connected' / 'Disconnected' status in the device menu and makes the menu refresh when USB or Bluetooth connection state changes. There is no evidence in the diff of a security vulnerability, exploit, or bug fix.

This commit is a routine user-interface cleanup for the Trezor hardware wallet's battery icon. It removes an older 'HomescreenBar' display mode and replaces it with a simpler 'AlwaysIconOnly' mode, while also dropping an alignment option. There is no indication in the commit that this fixes a security bug or changes security behavior.

This is a routine UI layout fix for the Trezor hardware wallet. It adds missing width-calculation helpers to a 'Hint' widget, removes an unused background padding object, and tidies how a page-counter is rendered. There is no security-relevant change visible in the diff.

This commit is a user-interface refresh for the Trezor T3W1 device homescreen. It adds a battery icon, a connection indicator, and makes notification labels interactive when relevant. There is no direct evidence of a security vulnerability being fixed or introduced; the changes are primarily cosmetic and structural.

This commit is a simple internal rename of a field called 'method' to 'backup_method' across several files. It does not change how the device works, what data it stores, or how users interact with it. There is no security issue visible in this change.

This commit adds a new 'BackupMethod' setting to Trezor's device communication protocol. It lets the wallet software tell the device how to handle backup or recovery of the secret recovery words. The change only defines the new enum and wires it into three messages (ResetDevice, BackupDevice, RecoveryDevice); it does not add any actual backup/recovery behavior. There is no security fix or vulnerability visible in this patch.

This commit adds a smoother, momentum-based scrolling effect to long menus on the Trezor T3W1 hardware wallet. It is a user-experience improvement, not a security fix. There is no indication it addresses a vulnerability or that an attacker could exploit it.

This commit only changes the protocol definitions (the message formats) used for listing WebAuthn resident credentials. It adds an optional batch size, a flag indicating whether more credentials are available, and a new acknowledgment message so the host can request the next batch. There is no actual implementation of the pagination logic in the firmware or host code in this commit, and nothing in the commit suggests a security vulnerability. It appears to be a normal feature addition to support paginated credential listing.

This commit adds pagination support for listing WebAuthn (FIDO2) resident credentials stored on a Trezor device. Previously, the device returned all credentials in one message, which could hit size limits. Now the host can request credentials in smaller batches. There is no obvious security bug in the change; it is a feature addition with a small, well-scoped protocol change.

This commit fixes a memory corruption bug in the code that caches Bitcoin-style key derivation paths inside Trezor's cryptographic library. When a derivation path was too deep to be cached, the code could store the derived key under the wrong path label. Later, a wallet or app asking for a different deep path could receive the wrong private key, which could lead to sending funds to an attacker-controlled address or signing with the wrong key. The fix stops the cache from storing these too-deep paths, and a new test confirms the wrong-key behavior no longer happens.

This commit is purely a documentation update: it generates the official changelog for bootloader version 2.1.16 and moves four pending changelog snippets into the published CHANGELOG.md file. No source code, firmware logic, or security behavior is changed.

This commit replaces pre-built bootloader binary files for several Trezor hardware wallet models and updates their recorded cryptographic hashes. The change is presented as a routine version bump from older bootloader versions to version 2.1.16.0. The actual code inside the new bootloader binaries cannot be inspected from this commit, and there is no statement that the update fixes a security problem. On its own, this is a normal maintenance action rather than evidence of a vulnerability.

This commit only updates the written changelog for Trezor legacy firmware version 1.14.1. It deletes three small draft changelog entries and adds their text to the published CHANGELOG.md file. No program code, firmware logic, or security behavior is changed. The security note about warning on long Ethereum data is a documentation of a prior change, not a new fix in this commit.

This update changes how older Trezor devices (the 'legacy' T1B1 model) display long Ethereum transaction data before signing. Previously, the device only showed one screen of data, which could hide malicious content appended later in the same transaction. Now it shows up to five pages of data, and if there is still more data left, it shows a clear warning telling the user that not all data can be viewed and to proceed with caution. This is a security improvement that reduces the chance of a user approving a transaction whose full contents they have not seen.

This commit updates the embedded QA (quality assurance) bootloader binaries and their recorded cryptographic hashes for five Trezor hardware wallet models. QA bootloaders are internal test artifacts, not the production bootloaders shipped to end users. There is no indication in the commit that this fixes or introduces a security vulnerability.