Trezor firmware

This commit changes how Trezor hardware wallets pick which private key to use when signing Ethereum-style transactions on non-Ethereum networks. Previously, only testnet-like or alt-networks could fall back to the standard Ethereum key (the one derived from path m/44'/60'/...). Now every network except Ethereum mainnet itself is allowed to use that same Ethereum key. The stated reason is to support newer networks such as Hyperliquid that share a chain ID with an already-registered network and therefore cannot get their own SLIP-44 coin type. The change is described as a workaround, not as a security fix, and it slightly relaxes the boundary between alt-network keys and the main Ethereum key.

This commit only adds new test cases for the Ethereum signing feature. It does not change any production firmware code, so it cannot introduce a security vulnerability by itself. The tests verify that the Holesky Ethereum testnet can be signed using both a testnet-style and a mainnet-style derivation path.

This commit removes a debug-only shortcut that could skip the user-visible pairing dialog on a Trezor device. The shortcut was already unused because the flag that enabled it was always set to True, meaning the dialog was always shown. The change is a cleanup with no functional effect on normal or debug builds.

This commit is a simple code cleanup: it removes two small helper methods from a class and replaces their calls with direct calls to the underlying user-interface functions. There is no change in behavior, no bug fix, and no security-related change.

This commit is a simple code cleanup: it moves the function that displays the on-screen pairing confirmation dialog from one internal file to another. The actual user-facing behavior and security checks remain exactly the same.

This commit removes leftover debug logging from production firmware builds. In non-debug builds, two log messages will no longer be emitted. This is a routine code-quality change with no direct security impact visible in the diff.

This commit fixes the order of arguments in a mock type stub for a timing function. It only changes a Python interface declaration used for testing/type-checking, not the actual device firmware code. The real security risk is minimal, but if the stub had misled developers, it could theoretically contribute to subtle timing bugs in firmware.

This commit is a routine code cleanup that renames and reorganizes error/exception types used in Trezor's Python library, particularly for the new THP (Trezor Host Protocol) transport. It does not change security behavior; it only makes error handling more specific and easier to maintain. For example, a generic 'device locked' exception is renamed and moved under a new THP error family, and THP error codes now raise distinct exception classes instead of generic strings.

This commit adds a user-facing setting to turn the device's RGB LED on or off. It is a routine feature addition (a 'chore') with no apparent security relevance. There are no changes that introduce memory corruption, bypass authentication, leak secrets, or alter cryptographic behavior.

This commit updates Trezor's Python library so it can recognize and verify digital signatures for a new 'secure monitor' (secmont) firmware component. It fixes a mismatch where the secmon image verifier was accidentally returning bootloader keys instead of secmon keys, and adds the correct public keys and signature-count rules for two development hardware models. There is no direct evidence this is a security vulnerability fix; it reads as a routine key-registry update for a new feature.

This commit is a routine UI translation update for the Trezor hardware wallet's device menu. It replaces hard-coded English text strings with references to the device's translation system so the menu can be displayed in multiple languages. There are no security fixes or functional behavior changes.

This commit is a routine UI code cleanup. It introduces a new medium-length menu size (10 items) and updates the device menu screen to use it instead of the previous short size (5 items). There is no security-relevant change here.

This commit is a routine user-interface update for the Trezor hardware wallet. It changes the 'About' screen in the device menu to show more information—firmware version, firmware type (Bitcoin-only or Universal), and a Bluetooth version number—instead of only the firmware version. There is no security-relevant change; it is purely a display/layout improvement.

This commit is a routine feature expansion of the Trezor hardware wallet's on-device settings menu for the upcoming 'Eckhart' model. It adds new menu options and result codes for Bluetooth pairing, PIN/wipe-code management, screen brightness, haptic feedback, and LED toggles. Most of the new menu items are not yet wired to real functionality and are marked with 'TODO implement' placeholders. There is no indication this change fixes or introduces a security vulnerability.

This commit is a routine user-interface polish change for the Trezor hardware wallet. It updates the on-screen button label and color when changing the device's name, and adds a short 'Device name changed' confirmation screen afterward. There is no security fix or vulnerability here.

This is a routine user-interface cleanup for the upcoming Trezor 'Eckhart' device layout. It makes menu divider lines always appear instead of requiring each screen to opt in. There is no security change, no bug fix, and no handling of secrets or sensitive data.

This is a routine user-interface cleanup for the upcoming Trezor Safe 5 (Eckhart layout). It makes header buttons slightly larger and easier to tap, and switches several screens to use a shared 'close button' helper. The only functional change visible in the code is a larger touch target and a small visual radius on header icon buttons; there is no evidence this affects security-sensitive behavior such as transaction confirmation, PIN entry, or seed handling. The huge list of changed test hashes is simply because every screen screenshot changed by a few pixels.

This is a cosmetic user-interface tweak for the Trezor hardware wallet's new 'Eckhart' layout. It makes the up/down pagination buttons the same size and updates the expected screen snapshots used in automated tests. There is no indication it fixes or introduces any security vulnerability.

This commit is a routine user-interface styling change for the Trezor hardware wallet's QR-code display screen. It swaps the foreground and background colors (inverts them) and adjusts the layout code accordingly. There is no indication this change affects security, cryptography, private keys, or transaction signing. The large number of changed test hashes is simply because the on-screen appearance changed, which is expected for a visual update.

This commit replaces a pre-built bootloader binary file for the T3W1 hardware model and updates the matching cryptographic hashes in a header file. The change itself is a routine binary refresh with no source-code diff, no changelog entry, and no stated security relevance. There is no visible evidence of a vulnerability or malicious change, but the opaque binary blob cannot be independently verified from the commit alone.

This small patch fixes a bug in the Trezor hardware wallet's message-handling code where certain errors could cause the device to loop forever instead of stopping. Before the fix, if a specific kind of error happened while processing a message, the code would just log it and continue running, potentially retrying the same failing work endlessly. The patch makes the handler return after logging, breaking the loop. This could prevent device lock-ups or unresponsiveness, but the change alone does not clearly enable remote theft of funds or private keys.

This is a one-character logging fix in a Trezor firmware debug message. It adds a colon and space to a log string so the formatting reads correctly. There is no security relevance: no behavior changes, no crash, no data exposure, and no vulnerability is introduced or fixed.

This commit fixes a bug where opening the device menu on a Trezor hardware wallet would crash with a red screen of death (RSOD) if a Bluetooth device was connected. The fix simply increases the maximum number of subscreens the menu system can handle from 8 to 10, because the Bluetooth menu entries push the count over the previous limit. There is no evidence this is exploitable by an attacker.

This commit is a routine maintenance update to the project's Python dependency lock file (poetry.lock). It was generated because the team upgraded their Poetry tool version from 1.8.5 to 2.1.3, matching the version available in their Nix development environment. The file changes are purely metadata format differences produced by the newer Poetry version, plus one local package version bump (tvl from 0.10.1 to 2.2). There is no indication of a security fix, vulnerability patch, or code behavior change.

This is a tiny user-interface fix in the Trezor Python command-line library. When a user runs a command on a brand-new, uninitialised Trezor, the tool now prints 'Device is not initialized.' instead of falling through to a generic 'Failed to find a Trezor device.' message. It does not change device firmware, crypto handling, or any security boundary; it only makes the error text clearer.