Trezor firmware

This commit fixes a crash in the Trezor device's on-screen 'About device' menu when the device lacks a serial number. It wraps the serial-number lookup in a try/except block and displays 'N/A' instead of crashing. There is no indication this can be exploited by an attacker; it is a robustness fix for a user-interface screen.

This commit only adds new automated tests for the 'tap to wake' feature on the T3W1 hardware model. It does not change any firmware code that runs on the device, so it cannot introduce a security vulnerability or fix one. The tests verify that the setting is on by default, that the checkbox toggles it, and that the option is hidden on an uninitialized device.

This commit adds a new optional sanity-check layer to the Python code that parses Trezor firmware files. It verifies that re-encoding a parsed firmware image produces the exact same bytes, and that any 'reserved' fields are all zeroes. The change is defensive: it can help detect malformed or tampered firmware images during analysis, but the strict mode is off by default, so existing behavior is preserved unless a caller explicitly opts in.

This commit only renames a single JSON key from '_reserved' to 'reserved' across 14 vendor header configuration files. No security settings, permissions, or values are changed. It appears to be a routine cleanup to match a naming convention elsewhere in the build tooling.

This commit is a straightforward internal code cleanup in the Trezor firmware's user interface code. It moves header-related helper methods (like title alignment, cancel/menu buttons, and styling) from the Frame component to the Header component. All existing call sites are updated to build a Header first and then pass it into a Frame. There is no change to user-visible behavior or security logic.

This commit only changes the project's automated testing configuration. It adds a nightly CI job that runs Python unit tests against a Bitcoin-only firmware build in addition to the existing universal build. There is no change to the actual firmware code, no bug fix, and no security-relevant behavior change.

This commit only adjusts how long automated test jobs are allowed to run in GitHub Actions for one Trezor hardware model (T3W1). It extends a pytest session timeout from 40 minutes to 50 minutes and the overall CI job timeout from 50 minutes to 60 minutes, but only for the T3W1 model. There is no change to firmware code, cryptography, user data handling, or device behavior. It is purely a CI configuration tweak to prevent false timeout failures when running tests with two workers.

This is a routine code cleanup that fixes a Python import cycle (two files importing each other) by moving one import to happen only when a specific function runs. There is no security-relevant change visible in the diff.

This commit simply moves a small helper function that checks whether a string contains only normal printable characters from one file to another shared location. No behavior changes, no bug fixes, and no security implications are visible in the code change itself.

This commit only adds new automated tests for a Solana feature that signs and verifies off-chain messages. It does not change the actual wallet firmware code that users rely on, so it cannot by itself introduce a security vulnerability or fix one. The tests exercise parsing, signing, and verification logic and include checks for invalid inputs.

This commit adds a new Trezor feature: signing and verifying Solana off-chain messages. It is a feature implementation, not a fix for a known vulnerability. The code introduces new message types, parsing logic, user confirmation screens, and client helpers. There is no direct evidence in the commit of a security bug, but any new signing path increases the attack surface and must be reviewed carefully for parsing mistakes or user-interface spoofing.

This commit updates the Trezor firmware's Solana support so that the standard 'Transfer' instruction can be used with multi-signature accounts. Previously, the firmware treated this instruction as non-multisig, which likely caused it to reject or mis-handle legitimate Solana transactions that required multiple signers. The change is a feature/fix to broaden supported transaction shapes, not a patch for an active vulnerability.

This commit changes one German translation string to add the word 'ist' (is) for consistency, and updates the corresponding translation signature metadata. There is no code or security change.

This commit only updates expected test result hashes (called 'fixtures') in a single test data file. It does not change any firmware, application, or cryptographic code. The hash changes are consistent with updated screen snapshots or translated text strings used by the test suite. There is no indication of a security fix or vulnerability.

This commit only updates translated text strings in Czech, German, Spanish, French, and Portuguese for the Trezor hardware wallet firmware. It changes wording for things like Ethereum transaction prompts, Bluetooth device labels, backup/recovery instructions, and passphrase prompts. There are no code logic changes, no new features, and no security fixes.

This commit adds new regulatory certification screens for Brazil, Ghana, and Nigeria to the Trezor hardware wallet's user interface. It is purely a compliance/labeling change: new image files are included and a list of regulatory regions is updated. There is no indication of any security bug, vulnerability, or behavior change affecting funds or device security.

This commit is a routine user-interface update for the Trezor hardware wallet's 'About' screen. It adds a 'Made in Ostrava, Czechia' label and, on devices that use serial numbers, displays the serial number. There is no security-relevant change.

This commit only adds new test cases for Ethereum transaction signing. It does not change any production code, so it cannot introduce a security vulnerability by itself. The test data includes sample transactions and their expected signatures, used to verify the device signs complex DeFi transactions correctly.

This commit only updates the expected test result hashes (called 'fixtures') for the user-interface test suite. It adds new test cases for LiFi token-swap/bridge transactions and refreshes a few existing pagination test hashes. There is no change to the actual Trezor firmware code that runs on the device, so this cannot introduce a security vulnerability by itself.

This is a small internal tuning change for Trezor's Ethereum app. It increases the amount of transaction data the device preloads from 4 KB to 6 KB before asking the user to confirm. The only visible effect is fewer back-and-forth data requests for Ethereum transactions with large data payloads. There is no direct security fix or vulnerability being patched.

This patch fixes a bug in how Trezor's Ethereum app checked whether a transaction was meant for the claim.xyz rewards distributor. Previously it compared a lowercase hex string (like '0xabc...') against raw address bytes, which would never match. The fix compares raw bytes to raw bytes. The practical effect is that the special claim.xyz user interface and safety checks now actually trigger for the intended contract, instead of silently being skipped for all transactions.

This is a routine Python code change in Trezor's firmware handling library. It adds support for a new Nordic (NRF) firmware header type and helper methods to insert cryptographic signatures into firmware image structures, plus a minor formatting tweak. There is no indication of a security vulnerability or fix.

This commit fixes how Trezor's Python library validates signatures for a new bootloader image format (BootloaderV2). Before the fix, the code ignored the signature bitmask and simply checked every signature against every public key in order. This could let an invalid or mismatched signature slip through, or cause validation to fail incorrectly. The patch makes the library read the bitmask, count signatures correctly, and only verify the signatures the image actually claims to have signed with. It also adds a missing signature-status line to the printed header. The change is in developer/CLI tooling, not the device firmware itself, so a direct attack on a real device is unlikely, but the library is used to inspect and validate firmware files.

This commit simply reserves an unused number (27) in a list of device capabilities so it cannot accidentally be reused later. It does not change any running code, fix a bug, or introduce a security issue.

This is a minor user-interface cleanup for the Trezor hardware wallet's Eckhart layout. It removes the warning header from a screen when the title text is empty, so users don't see a blank header. There is no security-relevant change.