Trezor firmware

This commit is a routine build tooling change. It switches the Python packaging tool for Trezor's internal developer utilities from Poetry to uv, updates the pyproject.toml configuration format, and adds an empty __init__.py file. There is no indication of any security fix, vulnerability, or behavior change in the actual tools.

This commit only updates the README documentation for the Python trezorlib package. It changes supported Python and firmware version wording, removes an optional installation extra for device authentication, switches the recommended development tool from Poetry to uv, and reorganizes some sections. There are no code or security changes.

This commit is purely a code-style update. It reformats Python source files to match the latest version of the Black formatter, changes uppercase hex escapes in byte strings to lowercase, removes unnecessary 'global' declarations, and adjusts some 'with' statements and trailing commas to satisfy updated flake8 rules. There are no functional changes to the firmware, tests, or tooling.

This commit is a routine build-system housekeeping change for the Trezor firmware repository. It replaces the Python Poetry package manager with the `uv` package manager across CI workflows, build scripts, and documentation. No device firmware code, cryptographic logic, or security-sensitive behavior is modified. The change is purely about how development dependencies are installed and invoked.

This commit is a straightforward internal code cleanup that reduces the memory footprint of a text-layout helper struct by switching from larger integer types to smaller ones. There is no security-relevant change: it does not alter how data is validated, how memory is allocated, or how user input is handled. It only changes the size of fields used to count characters and rows on screen.

This commit is a straightforward internal code cleanup that reduces the memory used by swipe gesture settings. It replaces a flexible but bulky structure storing animation duration with a simple on/off-style enum that only supports the two durations actually used (normal 333 ms and immediate 0 ms). There is no user-visible behavior change and no security relevance.

This commit fixes a USB communication bug in Trezor hardware wallets that use a high-speed USB chip running in full-speed mode. The device was incorrectly advertising a 512-byte packet size when it should have used 64 bytes. This mismatch could cause USB data corruption or connection failures, but the change is a straightforward buffer-size correction with no direct evidence of exploitability for theft of funds or private keys.

This commit changes the build scripts for Trezor hardware wallets so that when building in a non-optimized debug mode (PYOPT=0), a USB debug interface feature is automatically requested. This debug interface is normally used only during development and testing to control and inspect the device. The change itself is small and appears intentional, but enabling debug interfaces in production-like builds can be a security concern if misused. There is no evidence in the commit that this fixes a known security vulnerability; it looks like a build configuration fix.

This is a small internal cleanup change in the Trezor hardware wallet firmware. It changes how the on-device menu is closed when the user cancels: instead of throwing an internal exception, the menu now returns a normal 'cancelled' result code. There is no indication this fixes a security bug or changes user-visible behavior.

This commit adjusts how text labels are positioned and rendered on the bootloader screen of a Trezor hardware wallet model. It changes the vertical position of progress text, switches from a low-level text-drawing call to a reusable UI label component that supports multi-line wrapping, and adds explicit line breaks in two user-facing messages. There is no security-relevant change visible in the diff.

This is a one-line bug fix in the Bluetooth Low Energy (BLE) driver for Trezor hardware wallets. When the device went to sleep and later woke up, it was incorrectly deciding whether to accept incoming BLE messages based on whether it was currently connected. The fix makes it remember and restore the previous 'accept messages' setting instead. This could have caused the device to ignore legitimate Bluetooth messages after waking up, potentially affecting connectivity or user experience, but there is no direct evidence it enables theft of funds or unauthorized access.

This commit tweaks a Bluetooth Low Energy (BLE) connection timing setting used when a Trezor device is suspended. It halves the minimum and maximum connection intervals and raises the supervision timeout. The change is presented as a fix, but the commit message gives no details about what problem it solves or whether there is any security relevance. There is no evidence in the diff or references that this is a security vulnerability.

This commit only updates a documentation file (OPTIONS.rst) for the Trezor Python command-line tool. It adds a new 'evolu' command section and a new 'sign-message' entry under Cardano commands. There are no code changes, no security fixes, and no behavior changes.

This commit only adds new unit tests for an existing string buffer slicing feature. It does not change any production code, fix a bug, or introduce new functionality. There is no security relevance.

This commit adds a new helper method called prefix() to a Rust string buffer used inside the Trezor firmware. It lets code safely take the first N bytes of a string, but only if the cut point lands on a valid UTF-8 character boundary. There is no bug fix, no security patch, and no indication this change addresses a vulnerability.

This commit adds a small Rust utility that parses simple placeholder strings like '{0}' or '{1}' into text and argument tokens. It is a new feature with no obvious security relevance; it does not change existing behavior or fix any reported issue.

This is a tiny internal code cleanup in Trezor firmware. It changes the way the code reports an error when there is no active communication context, switching from a generic 'Exception' to a more specific 'NoWireContext' error type. The behavior is essentially the same; it just uses a clearer internal error label. There is no indication this fixes or introduces a security problem.

This commit fixes a bug in the Trezor hardware wallet firmware where a function called try_get_ctx_ids() would crash when triggered through the device's user interface rather than over the wire protocol. The crash blocked device wipe from completing on the T3W1 model if a recovery process was aborted. The fix catches the missing-wire-context case and returns no IDs instead of raising an exception, allowing the wipe to proceed. There is no direct evidence in the commit that this is exploitable by an attacker; it appears to be a reliability/functional bug fix.

This commit fixes a security gap in the Trezor hardware wallet's device-wipe feature. Previously, when a user chose to wipe their device, the secure secrets were erased but Bluetooth Low Energy (BLE) pairing records ('bonds') stored on the Bluetooth chip were left behind. Those leftover bonds could let a previously paired phone or computer reconnect to the wiped device, which is a privacy and minor security concern. The change now erases those BLE bonds during the wipe process.

This commit only increments version numbers in four header files after an internal release. There are no code, logic, or security changes visible in the diff.

This commit adds a standard Bluetooth 'Device Information' service to Trezor's Nordic BLE firmware. It advertises the manufacturer name ('Trezor Company s.r.o'), device model ('Trezor Safe 7'), and firmware/software version strings over Bluetooth. There is no direct vulnerability in the diff, but it increases the amount of identifiable information a nearby attacker could read from Bluetooth scan/advertising data, which can aid targeted attacks or fingerprinting.

This commit adds support for SLIP-24 payment requests to Stellar transactions on Trezor devices. It lets a merchant or service provider attach a signed payment request to a Stellar transaction, which the device verifies and shows on screen before signing. The change is a feature addition, not a fix for a known vulnerability, and it includes safeguards such as rejecting payment requests that contain multiple operations.

This commit fixes a display bug in the Trezor hardware wallet where the Bluetooth (BLE) MAC address was shown backwards on the device menu. The internal code stored the address bytes in reverse order, but the screen formatter was not flipping them back before showing them to the user. This is a user-interface correctness fix, not a cryptographic or access-control vulnerability.

This commit removes an extra 'Continue in the app' confirmation screen that appeared on the T3W1 Trezor model after the user changed the device label. It is a user-interface consistency cleanup, not a security fix. The change only affects screen flow and updates the corresponding visual test snapshots.

This commit changes how the Bluetooth Low Energy (BLE) connection behaves on Trezor hardware. It adds a way to request a faster BLE connection (used in the bootloader to speed up firmware uploads) and a slower, more power-efficient mode for normal wallet use. The change is a feature, not a fix for a known vulnerability. There is no direct evidence in the commit that it addresses an active security flaw, but changing connection timing parameters can have side effects on wireless reliability and power use.