Trezor firmware

This commit only changes a test file and its expected screen-capture hashes. It adds a 0.1-second delay in an automated test to make the test fail less often. There is no change to the actual Trezor firmware or wallet security code, so it does not affect real users or devices.

This is a routine test-infrastructure change. It moves a helper that clicks menu items in automated tests into a shared debug-link action and updates many test scripts to use it. There is no change to the firmware's security behavior, no fix for a vulnerability, and no user-facing feature.

This commit adds test helper code for reading and interacting with vertical menus on Trezor hardware wallet screens. It only touches the Python test/debugging library and does not change any firmware security logic, cryptography, or user-facing behavior. There is no security issue here.

This commit fixes a test script, not the actual Trezor firmware. The test was performing the wrong on-screen action for a newer Trezor model (Eckhart) when simulating a user cancelling a backup. It now clicks the cancel button instead of navigating through a menu. This is a test-only correction and does not change device security.

This is a routine maintenance update that bumps the version of a third-party GitHub Action used to install the Nix package manager during automated CI builds. There is no indication of a security fix or vulnerability in the commit itself.

This commit is a simple renaming from 'device ID' to 'device serial number' across labels, command names, comments, and a constant. There is no functional code change and no security relevance.

This is a large internal refactoring of how Trezor's user-interface passes key-value display data from Python apps to the Rust firmware. It replaces two-element string tuples with a new three-element 'PropertyType' that adds a flag indicating whether a value is raw data. The change touches many coin apps and UI layouts but is described by the vendor as a routine chore with no changelog entry. There is no direct evidence in the commit of a security vulnerability or fix.

This commit is a user-interface layout tweak for Trezor hardware wallets. It adds configurable vertical spacing between key/value property pairs shown on device screens. There is no security-relevant change, no bug fix, and no handling of secrets or memory.

This is a routine code cleanup in the Trezor hardware wallet's user interface layer. It moves default font and spacing choices for a UI component called PropsList into each device's theme file, so callers can use a simpler constructor. There is no change to security logic, cryptography, or how user data is handled.

This commit fixes a bug in the Trezor hardware wallet's vibration motor (haptics) driver for the T3T1 model. Previously, the standard haptic_play() function checked whether haptics were disabled before running, but the custom haptic_play_custom() function did not. The patch adds the same safety checks to haptic_play_custom(), so it now returns early if the driver is not initialized or if haptics are disabled. This is a consistency/bugfix change rather than a critical security patch; the main risk is that a disabled haptic motor could still be activated unexpectedly, which is primarily a user-experience or device-behavior issue rather than a code-execution or asset-theft vulnerability.

This commit is a cosmetic/user-interface change. It updates the text and styling shown on the hardware wallet's red error screens (RSOD), such as when a wipe code is entered or too many PIN attempts occur. The messages are rewritten in sentence case instead of all capitals, and some fonts/layouts are adjusted. There is no indication this fixes or introduces a security vulnerability.

This commit adds read-only functions that expose Bluetooth Low Energy (BLE) connection and pairing status to Python code running on the Trezor device. It does not change how BLE behaves, how it is paired, or how data is protected. It only makes existing internal state information visible to higher-level software.

This commit only adds a set of named color constants for an LED color palette in a user-interface theme file. It is a straightforward visual design change with no security relevance.

This commit is a cosmetic UI change for the Trezor hardware wallet's Eckhart design. It makes the device's RGB LED light up with specific colors on the homescreen and during red-screen error states, matching the screen's theme. There is no security-relevant change to how data is protected, how keys are handled, or how the device communicates.

This commit adds a new optional 'app_name' field to Trezor's Trusted Host Pairing (THP) credentials. It lets the device display both the application name and the host/browser name during pairing and connection prompts, making it clearer to users which app is requesting access. There is no direct evidence in the commit that this fixes an active security vulnerability; it reads as a user-experience and metadata improvement.

This commit only adds a new hardware model code name ('t3w1') to an internal test skip list. It does not change any firmware behavior, cryptographic code, or user-facing functionality. There is no security relevance.

This commit adds support for SLIP-24 payment requests when signing Solana transactions on Trezor devices. It is a feature implementation, not a security fix. The code introduces verification of payment request data against the transaction details and rejects cases with multiple token transfers when a payment request is present. There is no direct evidence in the commit of a vulnerability or security incident.

This commit adds a new feature to Trezor hardware wallets: SLIP-24 payment requests for Cardano transactions. It lets a merchant or service provider attach a signed payment request to a Cardano transaction, which the device then displays to the user for confirmation. The change is a feature addition, not a documented security fix. It includes a restriction that payment requests can only be used with single-output transactions, and it reuses an existing payment-request verification framework already present in the firmware.

This is a routine cleanup commit that removes unused code from a bootloader UI header component in the Trezor firmware. It deletes an unused left-button feature and switches one screen to use a standard close-button helper. There is no security fix or behavior change visible in the diff.

This commit simply renames the T3W1 hardware model's display name from 'T3W1' to 'Safe 7' and updates the corresponding UI test snapshot hashes. There is no security-relevant code change.

This commit is a code cleanup and refactoring change in Trezor firmware. It replaces the old storage_init() function, which required callers to fetch their own random entropy (salt), with a new storage_setup() helper that fetches entropy internally. It also removes the direct entropy_get() system call from the non-secure kernel interface. There is no direct evidence in the commit that this fixes an active security vulnerability; it appears to be architectural preparation for future initialization changes.

This commit simply removes an unused compiler flag named USE_SVC_SHUTDOWN from the firmware build script. There is no functional code change, no bug fix, and no security-relevant behavior altered. It is a routine cleanup.

This commit is a code cleanup: it renames the 'entropy' module to 'storage_salt' and moves it into the storage subsystem. The same device-unique salt logic (CPU ID plus one-time-programmable randomness block, or a master-key-derived salt on newer devices) is preserved, just called at a different point during storage setup rather than at boot. There is no indication this fixes a security bug or changes cryptographic behavior.

This is a large internal code reorganization in Trezor's embedded firmware. It moves flash/storage headers and build flags around so different firmware images (bootloader, kernel, production test, etc.) declare more explicitly which features they need. There is no obvious security bug introduced, but the change touches low-level memory-layout and storage code, so any mistake could in principle affect how secrets are stored. The commit itself is labeled a refactor and includes no changelog.

This commit simply deletes a leftover translation diff file that had been accidentally added to the repository earlier. It contains only string/label changes for user interface text and does not modify any executable code, cryptographic logic, or security behavior. There is no security issue here.