Trezor firmware

This is a code cleanup (refactor) of the on-screen button drawing and touch/hold logic for the Trezor hardware wallet's Caesar UI layout. It removes unused style-sheet abstractions, simplifies how buttons are described, and makes the hold-to-confirm component always assume it sits on the right side of the screen. The commit is tagged [no changelog] and contains no explicit security claims. The only behavior-visible change is a small simplification in the page component: when the left button is triggered on the first page, it now always returns a Cancel message instead of first checking whether a cancel button was configured. That change is a simplification based on an existing invariant, not a fix for a known vulnerability.

This commit only changes test files so that ten unit tests are skipped when running against the Bitcoin-only firmware variant. It does not modify the actual Trezor firmware code that users run, so it cannot directly affect device security or user funds.

This commit adds support for a new Ripple transaction type called AccountDelete to Trezor hardware wallets. It is a feature addition, not a security patch. The change lets users sign transactions that delete a Ripple account and send any remaining balance to a chosen destination. The code adds user-facing confirmation screens and enforces that a transaction cannot be both a payment and an account deletion. There is no direct evidence in the commit of a security vulnerability, but any new signing path deserves careful review because bugs could let an attacker trick a user into deleting an account or signing an unintended transaction.

This commit adds emulator-only support for a new Trezor device (T3W1) to wake from a simulated low-power sleep state when the user taps the emulated touchscreen. It only affects the software emulator build, not real hardware, and does not change how secrets or user data are handled. There is no indication this is a security fix.

This commit adds a new device-information field called tap_to_wake to the Trezor's Features message, which is the normal response to GetFeatures. It also adds a matching Capability_TouchWakeup flag. The change only reports whether the device supports and has 'tap to wake' enabled; it does not change how the device wakes, how it authorizes transactions, or how secrets are handled. There is no security fix or vulnerability visible in the diff.

This commit corrects the wrong GPIO pin assignment for the interrupt line of the Tropic01 secure chip on Trezor T3W1 hardware revisions A, B, and C. Previously the interrupt pin was set to the same pin as the power-control line, which does not match the hardware schematic. The commit message says this interrupt pin has not been used so far, so the practical security impact appears low.

This commit only updates expected test result hashes (called 'fixtures') in a single test data file. It does not change any firmware, application, or security code. The hashes are used by automated UI tests to verify that screen outputs match expectations after translation-related changes. There is no indication of a security fix or vulnerability being addressed.

This commit is a routine synchronization of translated user-interface text for the Trezor hardware wallet. It updates wording, adds missing translations, and removes obsolete translation keys across several language files. There are no code changes that affect security, cryptography, transaction signing, or device behavior.

This commit removes automatic test retries from the Trezor hardware test suite. It is a cleanup change: the retries were a temporary workaround for flaky USB communication during automated testing, and the underlying flakiness was fixed in a separate pull request. There is no change to the firmware that runs on user devices and no security-relevant behavior is modified.

This commit replaces a binary file called secmon.bin for the T3W1 hardware model with a newly built version. The change is described as a routine update ('chore') and there is no description of any security fix or vulnerability. Because the file is a compiled binary, the actual code changes cannot be seen in the diff, so no security issue can be identified from the commit alone.

This commit simply changes one version number in a release metadata file, from 2.11.2 to 2.12.0. There is no code change, no bug fix, and no security-related content.

This commit only updates changelog files. It renames an upcoming release version from 2.11.2 to 2.12.0 and removes one feature note about MCU device attestation from the T3W1 changelog. No code, logic, or security behavior changes are present.

This commit only edits changelog text files. It rewrites some entries for grammar and consistency, removes a few empty section headers, and changes the labels of some internal releases. No source code, firmware logic, or security behavior is modified.

This commit simply adds firmware version 2.11.2 to a list of released versions in a JSON file. It is a routine metadata update with no code changes and no apparent security relevance.

This commit only removes unused link definitions from several changelog files. It does not change any software code, behavior, or security functionality. There is no security issue here.

This commit only updates changelog files by removing issue reference numbers (like [#246], [#248], [#249]) from three existing security-related entries. It does not change any source code, firmware behavior, or fix any bug. The actual security fixes were already made in earlier commits; this is purely a documentation formatting cleanup.

This commit replaces a binary file called secmon.bin for the T3W1 hardware model with a newly built version. The diff shows only that the binary file changed; no source code or human-readable documentation is included, so we cannot determine from the commit itself whether the change fixes a security issue, adds a feature, or is routine maintenance.

This commit simply adds a new cryptographic signature entry to a JSON file that records approved translation bundles for the Trezor hardware wallet. There is no code change, no bug fix, and no visible security issue. It appears to be routine release housekeeping.

This commit simply adds a new cryptographic signature entry to a JSON file that records approved translation data for Trezor devices. There is no code change, no bug fix, and no visible security issue. It appears to be routine release housekeeping: signing the translation bundle for firmware version 2.11.2.0.

This commit simply updates a timestamp and a matching numeric version constant used for Ethereum network definitions in Trezor firmware. There is no code logic change, no security fix, and no vulnerability present in the diff.

This commit replaces the signed bootloader binary for the Trezor T3W1 hardware wallet model and updates the matching cryptographic hash list. The change is a routine version bump from bootloader version 2.1.16.0 to 2.1.17.0. The commit message and diff provide no information about why the bootloader was rebuilt or whether any security issue was fixed. Because the actual bootloader binary is a compiled blob, its contents cannot be reviewed from this diff alone.

This commit only changes release dates in seven changelog files, moving the stated release date from 21 May 2026 to 14 May 2026. No executable code, configuration, or security-related content is modified.

This commit simply changes release dates in seven changelog files from 14 May 2026 back to 21 May 2026. It is a reversion of an earlier date-change commit. There is no code change and no security relevance.

This update fixes a bug in how Trezor hardware wallets classify accounts inside Solana transactions. The bug could mislabel read-only signer accounts as writable, or writable accounts as read-only. Because Trezor uses these labels to decide what the user must approve on screen, a crafted transaction could trick the wallet into showing a harmless-looking account while actually requiring it to sign or authorizing unexpected changes. The changelog files explicitly mark this as a security fix.

This patch changes how a Trezor hardware wallet handles EIP-712 typed data signing for Ethereum. It now caches (stores) the values shown to the user for the domain's name and version fields, and reuses those same cached values when later computing the cryptographic hash. The goal is to prevent a malicious computer or app from showing the user one set of values on screen, but then tricking the device into signing a different set of values. The changelog file labels this as a security fix: 'Cache confirmed EIP-712 domain.'