Trezor firmware

This commit adds a new on-screen confirmation flow for Ripple payment requests on newer Trezor hardware wallets. It replaces a placeholder TODO with a proper user-interface that shows the recipient, memos, refund details, and trade details before signing. There is no obvious security bug in the change; it is a feature implementation that improves transparency for users.

This commit only changes test files for Trezor hardware wallet firmware. It updates which cryptocurrencies are used in automated tests, adds a new test case for a basic swap scenario, removes an outdated manual input-flow test, and adjusts which device models certain tests run on. There are no changes to the actual wallet firmware code that users rely on, so this cannot directly affect device security.

This commit only updates expected test result fingerprints (hashes) in a JSON test-fixtures file. It does not change any firmware, application, or cryptographic code. There is no direct security relevance visible in the diff.

This commit fixes a validation check in the Trezor hardware wallet's Bitcoin signing code. The device accepts 'payment request memos' that can contain different memo types, and it should reject requests where more than one type is set at once. A newly added memo type ('text details memo') was accidentally left out of the 'pick exactly one' check, so a malicious or buggy host could potentially include both a text memo and a text-details memo in the same payment request, confusing what the user sees or breaking an invariant the firmware relies on.

This commit updates the on-screen user interface shown when approving Bitcoin payment requests on a Trezor device. It replaces an older screen that merely asked whether to show details with a new screen that actually displays the payment request details (recipient, address, memos, refunds, trades, account path). There is no indication of a security bug or vulnerability fix in the change itself or the commit message.

This commit removes unused user-interface code for displaying Bitcoin payment request details (an old SLIP-24 feature) from four Trezor firmware layout files. It is a cleanup/refactoring change with no security relevance visible in the diff.

This commit is a code cleanup that moves the user-confirmation screen for SLIP-24 payment requests out of Ethereum-specific code and into shared UI code. It does not change security checks or add new features; it only reorganizes how account, network, and token details are passed to the display layer. There is no clear security bug in the change itself.

This is a code cleanup commit in Trezor's Python firmware tooling. It moves hardcoded developer-only signing keys from one internal file to a shared models file and slightly reorganizes how public keys are looked up. The keys themselves remain in the repository and are still labeled as development keys. There is no indication this fixes a security vulnerability or changes device behavior.

This commit only adds a new build step in GitHub Actions CI to compile a 'prodtest emulator' artifact for one hardware model (T3W1) and upload the resulting binary. It is a pure CI/workflow change with no modifications to firmware, bootloader, or application code. There is no security-relevant change visible in the diff.

This is a one-line rename of a function in the Unix (emulator) build of the Trezor firmware's power manager. It changes pm_set_soc_limit to pm_set_soc_target to match an updated interface elsewhere. There is no security content visible in the diff.

This commit fixes a UI flow bug in the Trezor hardware wallet (Eckhart/T3W1 layout). When a user was setting up a new PIN, opened the menu, chose 'Cancel PIN setup', and then confirmed the cancellation, the device accidentally reported 'success/confirmed' instead of 'cancelled'. This could mislead connected software into thinking the user had approved PIN setup when they actually aborted it.

This commit wraps a Bluetooth debug log message so it only appears in debug builds, not in production firmware. The change itself is minor and defensive: it prevents potentially sensitive Bluetooth connection details from being recorded in production logs. There is no direct evidence this created a practical security vulnerability, but logging internal state in production is generally considered poor security hygiene.

This is a small bug fix in Trezor's Python library. When using a special developer/debug connection to the Trezor Bridge, the code was accidentally using the normal user session ID instead of the dedicated debug session ID. That could cause debug commands to interfere with or be sent to the wrong session. It is a correctness fix rather than a clear-cut security vulnerability, but mixing debug and normal sessions could create unexpected behavior for developers.

This commit updates the Trezor Python library so it no longer tries to auto-detect a newer device protocol by sending a test message to every bridge-based device it finds. Instead, it now trusts the reported bridge version number to decide whether the newer protocol (THP/V2) is supported. The removed detection logic could briefly open a connection and send an Initialize message to each device during enumeration, which might cause minor side effects or confusion, but it is not a clear-cut security vulnerability.

This commit adds a short 0.1-second delay in a UI test helper when using a newer protocol version (THP/V2). It is a temporary test-only workaround to reduce flaky test failures caused by occasional lost screen-recording packets after an event loop restart. It does not change production firmware, wallet logic, or any security-critical code path.

This commit fixes an internal test helper so that non-debug Trezor emulator builds can complete a basic sanity check. It is purely a test-infrastructure change and does not affect the firmware that runs on real devices or any user-facing security behavior.

This commit changes the Trezor host-side Python library so that when it tries to open a new communication channel with a Trezor device, it can ignore up to 50 unexpected packets before giving up. Previously, a single stray or delayed packet would cause the channel setup to fail. The change makes the connection process more tolerant of leftover traffic, which could happen during retransmissions or after a previous session.

This commit is a cosmetic user-interface change. It replaces ordinary spaces with non-breaking spaces between numbers and their units (for example, showing '1.23 BTC' with a special space that prevents the number and 'BTC' from being split across two lines on the Trezor screen). There is no security-relevant behavior change.

This commit only changes the colors used for text and hyphenation in the user interface of a Trezor hardware wallet theme. It makes some text and hyphen colors slightly darker for visual consistency. There is no security relevance in this change.

This commit refactors how the Trezor firmware initializes and talks to the Tropic secure chip, mostly in the internal production-test tool. It removes some custom wrapper functions and switches to the vendor's libtropic library directly. The visible changes include removing a hard crash ('ensure') when a secure session cannot be started, and removing a second (apparently accidental) memzero call that was clearing the wrong key. These are code-quality and robustness improvements rather than a clear-cut security fix, but they do reduce two risky behaviors.

This commit simply adds two names to the AUTHORS file for the python-trezor package. It is a routine administrative change with no code modifications and no security relevance.

This commit is a routine maintenance change to an internal helper script. It removes the automatic insertion of the current year from a copyright notice template, so the notice now simply reads 'Copyright (C) SatoshiLabs and contributors' instead of 'Copyright (C) 2012-<current year> SatoshiLabs and contributors'. There is no change to any firmware, wallet, cryptographic, or user-facing code.

This commit only adds standard open-source copyright and license notices to the top of 21 Python files. It does not change any program logic, fix bugs, or alter security behavior.

This commit only updates copyright lines in file headers across many Python files, removing the year ranges (for example, changing '2012-2022' to just 'SatoshiLabs and contributors'). It does not change any program logic, security checks, or behavior. There are no security implications.

This commit is a routine cleanup of the project's automated build-and-test configuration. It removes references to an internal 'protocol version' (v1/v2, also labeled THP) from the names of build artifacts and job labels. There is no change to the actual Trezor firmware code, device behavior, or security features. It only affects how GitHub Actions names and organizes build outputs.