Trezor firmware

This commit changes how the Trezor emulator (a software version of the hardware wallet used for testing) is built. It disables a MicroPython bytecode optimization called 'pyopt' for emulator builds and tweaks how the build tool handles the --pyopt flag. The change only affects the emulator/test build, not the real hardware firmware, and there is no direct evidence in the commit that this fixes a security vulnerability.

This commit is a simple code cleanup: it replaces many copies of the same 'if device not initialized, raise an error' check with a single shared helper function. There is no change to when or how the error is raised, so it does not fix or introduce any security vulnerability.

This update fixes a bug in Bitcoin-only Trezor firmware where the device would try to derive a cryptographic seed even when the device had not been set up yet. Now it correctly returns a 'NotInitialized' error instead. A test was added to confirm the behavior.

This commit moves a safety check earlier in the process of setting up a cryptographic seed on a Trezor device. The check ensures the device is properly initialized before it proceeds. By running the check earlier, it prevents a situation where a seed might already be cached or a passphrase accepted before the initialization check happens. This is a defensive hardening change, not a confirmed exploitable vulnerability, because the commit message does not describe a security issue and no exploit path is shown in the diff.

This commit changes the numeric codes used to identify Ethereum data types in Trezor's device-to-computer protocol. It also allows path numbers in one message type to be negative (signed integers) instead of only positive (unsigned integers). The changes are described as a routine cleanup ('chore') with no changelog entry. There is no direct evidence in the commit that this fixes a security vulnerability.

This commit simply turns off a hardware test job in GitHub Actions for Monero cryptocurrency features by adding an always-false condition. It is a CI/testing change, not a code change to the firmware itself, and contains no security fix or vulnerability.

This commit updates the versions of two GitHub-provided helper actions used in Trezor's automated hardware testing workflows. It also disables the 'persist-credentials' option on checkout steps, which is a security-hardening setting that prevents later workflow steps from accidentally keeping long-lived repository access tokens. The change is routine CI maintenance with a small defensive-security benefit, not a fix for an active vulnerability in the Trezor firmware itself.

This commit only updates Trezor's internal continuous-integration (CI) hardware-test configuration. It adds two new physical device models (T3B1 and T3W1) to the automated test runner list and tells the test harness how to label them during firmware flashing. There is no change to the firmware code that runs on users' devices, no change to cryptographic handling, and no security fix or vulnerability present in the diff.

This commit changes a CI (Continuous Integration) workflow file for hardware testing. It modifies the configuration so that a USB hub power-cycles all ports instead of just port 1 during automated test runs. There is no change to the actual Trezor firmware, wallet application, or any code that end users run. This is purely a test infrastructure tweak.

This commit only changes the project's internal continuous integration (CI) setup to add hardware testing runners for a new Trezor device model (T3T1 / Safe 5). It does not modify the firmware code that runs on user devices, nor does it change any security-critical logic. There is no indication this commit fixes or introduces a security vulnerability.

This commit simply renames a documentation file from README to README.md so it displays nicely in GitHub. The actual text of the document is unchanged. There is no code change and no security relevance.

This is a small user-interface cleanup change for the Trezor hardware wallet's Delizia layout. It makes warning screens hide their top title bar when the title is empty, and explicitly rejects 'danger' warnings that have no title. There is no direct evidence this fixes a security vulnerability; it appears to be a UI consistency improvement.

This commit is a simple code cleanup: it renames a Rust function from Frame::new() to Frame::with_header() and updates every place that called it. There is no change to what the code does, no bug fix, and no security-relevant behavior.

This is a small internal code cleanup in the Trezor firmware's user-interface code. It changes a variable used for screen layout margin from a larger integer type (`usize`) to a smaller one (`u8`). The actual behavior is unchanged because the value is immediately converted to the same screen-coordinate type (`i16`) used before. There is no security-relevant change visible in the commit.

This is a massive Trezor firmware commit that replaces the old SCons-based build system with Cargo (Rust's build tool) for compiling the embedded C code. It adds many new Cargo.toml files, build.rs scripts, and a custom xbuild helper crate, but does not change the actual security logic of the wallet. The main risk is that a build-system change of this size could accidentally alter compiler flags, included source files, or linker settings, which might affect the produced binary. There is no direct vulnerability shown in the diff, and the commit message explicitly says it is a feature with no changelog entry.

This commit removes the 'ipc' feature flag from three build scripts by default, and only enables it when external app loading is supported on the T3W1 model. IPC stands for inter-process communication, and these particular system calls were reportedly unused. There is no direct evidence in the commit that this fixes an active security vulnerability; it appears to be a cleanup or hardening change to reduce unused attack surface.

This commit rearranges how different pieces of the Trezor firmware are placed in the device's flash memory. It moves frozen Python data and the main code sections into one flash region, while moving the bootloader into a separate flash region. The stated purpose is to support linking Rust static libraries (rlib). There is no direct evidence in the commit that this fixes a security vulnerability.

This commit only updates a GitHub Actions CI workflow file. It adds one extra step to initialize a code submodule (QR-Code-generator) before running automated style checks. There is no change to the actual Trezor firmware code, cryptography, or anything users interact with. It is a routine build/maintenance fix with no security relevance.

This commit renames a hardware configuration flag from USE_BACKUP_RAM to USE_BACKUP_DOMAIN_RETENTION and enables it for three Trezor T3W1 hardware revisions. It appears to be a code cleanup/refactor to make startup power-retention behavior match the actual hardware capability on these boards. There is no direct evidence in the commit that this fixes a security vulnerability.

This commit is a pure code reorganization: it moves the STM32-specific bootloader header, bootloader image, and update-control block (UCB) code from a shared directory into a hardware-specific 'stm32' subdirectory, and adds a minimal Unix emulator stub for UCB. The actual logic in the moved files is byte-for-byte identical to the original. No security behavior is changed, no bugs are fixed, and no vulnerabilities are introduced based on the supplied diff.

This commit only reorders two C keywords in three places, changing 'const static' to 'static const'. This is a coding-style cleanup to silence compiler warnings and has no effect on what the code actually does or on security.

This commit fixes a missing initialization step in the Trezor hardware wallet emulator (the software version used for testing/development, not the real device). The emulator now initializes the haptic driver when haptic feedback is enabled. This is a straightforward bug fix for a feature that was not being set up correctly in the emulator build. There is no direct security relevance visible in the commit.

This commit is a routine cleanup of the GitHub Actions workflow that builds Trezor emulator releases. It removes unused matrix dimensions (like ASan variants), drops environment variables that were no longer needed, changes a default so the bootloader build step is skipped unless explicitly requested, and passes the device model into the build command. There is no change to the firmware code that runs on user devices, no fix for a vulnerability, and no security-relevant behavior change.

This commit removes the full build directory path from the firmware binary by switching from __FILE__ to __FILE_NAME__ in two error-handling locations. The change reduces information leakage but does not fix a memory corruption or logic bug. It is a hardening/information-disclosure reduction patch, not a fix for an actively exploitable vulnerability.

This commit updates a build script to look for compiled firmware files in a new directory path (`build-xtask/artifacts/...`) instead of the old path (`build/...`). It is a routine build-system path adjustment with no apparent security relevance.