Trezor firmware

This commit adds a new hardware-based device authentication feature for the Trezor T3W1 model. It lets the device prove its identity using a cryptographic certificate and signing key stored in the microcontroller (MCU). The change is a feature addition, not a fix for a known vulnerability. There is no evidence in the commit or supplied references that this resolves an active security issue or introduces a new attack path.

This commit adds a new debug-only protocol message called DebugLinkSetBatteryState. It lets developers or test tools tell the Trezor emulator (a software version of the device used for testing) what battery and charging state to simulate. The change only touches protocol definitions and generated code; it does not add any logic that runs on a real device or handles secrets. It is marked for debug use only and is skipped in the legacy firmware build.

This commit adds a debug-only feature to the Trezor firmware emulator that lets software tests fake the device's battery and charging state. It does not change real hardware behavior. The new function is only compiled into emulator builds and only when Python optimization is disabled (debug builds). It is intended for automated testing, not for end-user devices.

This commit adds a debug-only feature that lets developers or automated tests tell the Trezor emulator what battery state to report (charge level, charging, temperature, etc.). It only works when the device is compiled in debug mode and is running in the software emulator, not on a real hardware wallet. There is no indication this is a security fix or that it exposes real user funds to risk.

This commit only adds automated user-interface tests for the battery indicator on one Trezor device model. It does not change any firmware code that users run, so it cannot introduce a security vulnerability or fix one.

This commit only adds a new test marker called 'emulator' so that certain automated tests can be skipped when running on real Trezor hardware instead of the software emulator. It does not change any wallet, firmware, or security code that end users rely on.

This commit adds a new Python helper and command-line tool to control the emulated battery state on Trezor hardware simulators (emulators). It does not change firmware running on real devices. The feature is intended for testing only and is gated behind the existing debug-link mechanism, which already requires special debug access to the device or emulator.

This is a routine developer tooling change that improves how code-coverage reports are generated for the Trezor firmware. It makes coverage measurements more accurate by using the same preprocessed source files that are actually compiled into test builds, and avoids redundant rebuilds in CI. There is no user-facing change and no security relevance.

This commit simply updates a Python testing tool called 'coverage' from version 5.5 to 7.13.5. The coverage tool is only used during software testing to measure which parts of the code were executed by tests. It is not part of the actual Trezor device firmware or wallet software that users interact with. There is no indication this update fixes or introduces any security issue.

This is a harmless build-system cleanup. It teaches the firmware build scripts to remove haptic (vibration) and RGB LED code from devices that do not have those hardware features, and it sorts the list of feature flags alphabetically for easier reading. There is no security bug being fixed here.

This commit is a code refactor in Trezor's Rust THP (Trezor Host Protocol) library. It moves responsibility for assigning channel IDs from the internal library mux to the application using the library. The change also removes the requirement that credential stores/cloners implement the Clone trait, and adds a helper allocator for consecutive channel IDs. There is no direct evidence in the commit or supplied references that this fixes an active security vulnerability; it appears to be an architectural cleanup that may make misuse harder but also places more correctness burden on the application.

This commit is a straightforward code cleanup in the Trezor firmware's Rust implementation of the Trezor Host Protocol (THP). It replaces repeated uses of a generic type `Channel<Host, B>` or `Channel<Device, B>` with shorter type aliases `Channel<B>` inside the host and device channel modules. No behavior of the code changes, and there are no security implications.

This commit adds a new 'reset' method to two internal Rust channel objects in the Trezor firmware's THP (Trezor Host Protocol) code. The method simply restores the channel to its freshly-created state, discarding any pending messages or connection bookkeeping. There is no indication in the commit that this fixes a security bug; it reads as a routine code cleanup or preparation for future use.

This commit is a code cleanup in Trezor's secure transport layer. It centralizes how error messages are sent and removes an outdated workaround where the device had to manually craft an error packet. The change also makes decryption failures on the device side send a proper error response instead of silently closing the channel. There is no indication this fixes an active security vulnerability; it appears to be a refactoring and robustness improvement.

This commit refactors how a Trezor hardware wallet's Rust-based secure channel code remembers whether a pairing handshake succeeded. It moves the pairing-state information from a temporary handshake object into the long-lived channel object, adds a check that the handshake is fully done before completing, and exposes the remote device's public key and pairing state to the rest of the application. The changes look like a defensive cleanup rather than an active vulnerability fix, but they close a small window where pairing state could be lost or queried incorrectly.

This commit refactors the internal state tracking of the Trezor hardware wallet's THP (Trezor Host Protocol) Rust code so the channel can count how many times it has retransmitted a message. It also exposes that retry count to callers and adds a helper function for calculating how long to wait before retrying. The change is defensive: it makes the protocol more observable and easier to limit in the future, but it does not by itself fix a known exploitable bug.

This commit only changes how numbers appear in log messages for the Trezor hardware protocol (THP) Rust code. It switches decimal formatting (e.g., '123') to hexadecimal formatting (e.g., '0x7b') for control bytes, channel IDs, and error codes. There are no functional code changes, no security fixes, and no behavior changes.

This commit only fixes typos and duplicated words in code comments. No actual program code was changed, so it cannot affect device behavior or introduce security issues.

This commit simply adds a new firmware version number (2.11.1) to a release metadata file. It is a routine administrative update with no code changes and no security relevance visible in the diff.

This commit simply adds a new digital signature entry to a JSON file that records approved translation bundles for the Trezor hardware wallet. There is no code change, no bug fix, and no visible security issue. It appears to be routine release housekeeping: signing the translation data for firmware version 2.11.1.0.

This commit only updates a timestamp and a matching version number used for Ethereum network definition files. There are no code logic changes, no bug fixes, and no security-related modifications visible in the diff.

This commit replaces a binary file called secmon.bin for the T3W1 hardware model. The file is a compiled security monitor firmware image, but the actual code changes inside it are not visible in the commit. There is no description of any security fix or vulnerability, so we cannot determine from this commit alone whether it addresses a security issue.

This commit is purely a documentation change: it assembles the release notes for Trezor firmware version 2.11.1 by moving text fragments from temporary changelog files into the final Markdown changelogs. No source code, cryptographic logic, or device behavior is modified, so it cannot introduce or fix a security vulnerability on its own.

This commit moves an Ethereum feature called "stablecoin yielding" from debug-only mode into production. It adds user-interface flows for certain ERC-4626 vault interactions, such as depositing USDC into a yield-bearing vault. The change itself is a feature promotion, not a fix for a known security flaw. There is no evidence in the commit that it addresses an active vulnerability or that it introduces one.

This commit expands Trezor's Ethereum 'clear signing' support to include ERC-4626 vault withdraw and redeem transactions, not just deposits. For transactions where the receiver or owner differs from the signer on an unknown vault, the device now falls back to blind signing instead of refusing outright. For known Trezor-listed vaults, mismatches still trigger a hard error. The change is a feature addition with intentional security trade-offs rather than a clear-cut vulnerability patch.