Trezor firmware

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 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 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 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 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 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 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 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 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 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 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.

This commit re-enables a security feature called 'MCU device attestation' for the T3W1 hardware wallet model. It is not a vulnerability fix; it restores a previously removed capability that lets the device cryptographically prove its microcontroller is genuine using a modern quantum-resistant signature scheme (ML-DSA-44).

This commit adds a new optional 'streaming' mode for retrieving device authenticity proofs on Trezor hardware wallets. Instead of sending all attestation data (certificates and signatures) in one large message, the device can now send it in smaller chunks. This is intended to improve reliability over lossy transports like Bluetooth Low Energy. The old one-shot mode is kept for backward compatibility. There is no direct evidence in the commit that this fixes a security vulnerability; it reads as a reliability/feature improvement.

This commit changes the Trezor hardware wallet so that a large secondary device-attestation proof (the MCU attestation) is only sent when the caller explicitly requests streaming support. The goal is to avoid sending one oversized response. It is a defensive hardening change rather than a fix for an active vulnerability, and the commit message does not claim it resolves a security issue.

This commit only changes the protocol definitions (the 'language' the Trezor device and apps use to talk to each other). It adds a new optional streaming mode for requesting device-authenticity proofs, so large proofs can be sent in smaller chunks instead of one big message. There is no actual device firmware logic shown here—only generated message bindings—so it is not a security fix or vulnerability by itself. It is a feature addition that could, in theory, introduce new attack surface once the corresponding firmware code is implemented, but that code is not present in this commit.

This commit only adds and reorganizes automated tests for the device-authentication feature on Trezor hardware wallets. It does not change the firmware code that runs on the device, so it cannot introduce a security vulnerability or fix one in the shipped product. The changes make the test suite exercise both the Optiga and Tropic authentication flows, test chunking sizes, and verify that invalid requests are rejected with proper error messages.

This is a tiny test-only change that adds a new optional keyword argument named 'wait' to a type definition used in Trezor's debug/testing tooling. It does not change any runtime behavior, device firmware, or security logic. There is no security issue here.

This commit is a pure code cleanup: it rewrites two small internal helper functions from Python generator style (`yield from`) to modern async/await style (`await`). The author verified that the compiled firmware bytecode is identical, meaning the device behaves exactly the same as before. There is no security-relevant change.

This commit is a build-system cleanup: it wraps a Trezor-Host Protocol (THP) credential confirmation screen so it is only compiled into firmware builds that actually have THP enabled. For non-THP builds, only the simpler non-THP confirmation is kept. There is no direct evidence in the commit that this fixes an active security bug; it appears to be a refactor to avoid including unused THP code in builds where the feature is disabled.

This commit simply restores a missing Python test dependency called pytest-retry. It only affects the project's testing environment and does not change any code that runs on the Trezor device or any production software. There is no security issue here.

This change only adjusts a test configuration file to silence a harmless deprecation warning coming from a third-party UI library called dominate. It does not modify any firmware, wallet, or security-related code, and there is no indication it fixes or hides a real security problem.

This commit only changes the wording of a test-result message in the project's internal testing tools. It splits one message into two so that missing expected test snapshots are labeled 'UI_MISSING' rather than 'UI_FAILED'. There is no change to the firmware, wallet behavior, cryptography, or any user-facing security feature.