Trezor firmware

This commit is a routine localization update. It regenerates translation files so that some on-screen text strings are left blank for certain device models or languages while keeping them present for others. There is no code behavior change, no bug fix, and no security relevance.

This commit simply removes the repository's own SECURITY.md file and updates the README to point users to the organization's default security policy on GitHub instead. It is a documentation-only change with no code modifications and no direct security impact on the firmware or device.

This commit only changes a test file. It adjusts which hardware models and protocol versions skip a test that sends a large JPEG homescreen image in a single message. The change is not a fix to product firmware and does not address a security vulnerability.

This is a routine user-interface refactor for the Trezor hardware wallet firmware. It renames a parameter from 'warning_footer' to 'footer' and allows the footer text to be shown either as a warning (red/alert style) or as a normal informational hint. The change touches many UI test snapshots because screen layouts changed slightly, but there is no evidence of a security vulnerability or fix.

This is a user-interface consistency patch for the Trezor hardware wallet's 'Eckhart' design. It moves the 'cancel' option from a small 'X' button on the action bar into a menu, matching how the newer 'Delizia' design already works. There is no security bug being fixed here; it is purely a layout and navigation change.

This commit is a routine cleanup of unused text strings in the Trezor firmware's translation system. It removes labels like 'Enter', 'Sending from account:', and 'Good to know' from generated translation files because they are no longer used anywhere in the user interface. There is no change to security logic, cryptography, or device behavior.

This commit removes the project's custom Nix-based packaging for the Pyright type-checking tool and stops using that custom package in the developer shell. It is a build/development tooling cleanup, not a security fix or vulnerability. There are no changes to the Trezor firmware code that runs on devices or to user-facing applications.

This is a routine build-environment maintenance update. It refreshes the versions of two Nix package collections used by Trezor's developer shell and updates the `uv` Python packaging tool from 0.7.14 to 0.10.10. The change does not touch the firmware code, wallet logic, cryptography, or any user-facing security feature. There is no indication of a security vulnerability being fixed.

This commit is purely a code-style cleanup. It updates the project's C source files so they match the formatting rules of a newer version of the clang-format tool (version 21.1.8 instead of 17.0.6). The changes are limited to whitespace, line breaks, comment placement, and how macros and attributes are laid out. No program logic, security checks, or behavior were changed.

This commit removes a default value for the backup_method setting used during wallet recovery on Trezor devices. Previously, if a recovery app did not explicitly choose a backup method, the device would default to 'Display' (showing shares on screen). After this change, the device will ask the user to choose instead. This is a small user-experience and behavior change, not a fix for a known security vulnerability.

This commit adds a way for the Trezor host software (trezorctl) to tell the device which backup/recovery method to use during wallet recovery. Right now only the existing display-based method is actually supported; the new parameter is mainly plumbing so the host can skip an extra user-choice screen in future versions. There is no obvious security bug in the change itself.

This is an automated dependency update by Dependabot that bumps the Python 'cryptography' library from version 46.0.6 to 46.0.7 in the project's lock file. The change only updates recorded download URLs and cryptographic hashes for the new version. There is no indication in the commit itself that this fixes a known security vulnerability, and no security advisory was supplied. It is best treated as a routine maintenance patch.

This commit changes how Ethereum addresses are visually displayed on Trezor devices. When the optional 'chunkify' feature is enabled, the '0x' prefix is now shown as a separate chunk from the rest of the address, making it easier for users to read and verify addresses. There is no direct security vulnerability being fixed here; it is a user-interface improvement that may slightly reduce the chance of user verification mistakes.

This commit fixes a small user-interface bug in Trezor's Bluetooth pairing flow. Previously, if the device name was too long for the Bluetooth advertising packet, the user saw the full name on the Trezor screen while the truncated name was actually broadcast. Now the code returns the truncated name and displays that same shortened name to the user, so what they see matches what nearby devices see.

This commit only adds new test cases for Ethereum vault deposits. It does not change any production firmware code, so it cannot introduce a security vulnerability in the device itself. The new tests check both valid deposits and cases that should be rejected, such as sending native ETH along with a deposit or a malformed transaction.

This commit adds a new user-facing feature to Trezor hardware wallets: clear signing support for ERC-4626 'vault deposit' transactions on Ethereum. It introduces code that recognizes a specific smart-contract function call, shows the user a friendly confirmation screen with the vault name and deposit amount, and only proceeds if safety checks pass. There is no indication in the commit that this fixes a security bug; it appears to be a normal feature addition.

This is a routine user-interface cleanup change. It makes one button label parameter optional across several Trezor device layouts and updates the Python helper that calls it. There is no security-relevant behavior change: the same screens are shown, only the internal plumbing for deciding whether to display an extra 'info' button is simplified.

This commit is purely a documentation update for the Trezor firmware repository. It reorganizes existing documentation, adds new documentation for the Trezor-Host Protocol (THP), and moves Bitcoin signing and protocol v1 docs to new locations. No executable code, firmware logic, or security-sensitive behavior was changed.

This commit fixes a single grammar typo in a code comment. The word 'host' was changed to 'the host' in a protobuf message description. No code behavior, security logic, or functionality was changed.

This commit only adds a human-readable comment to a protobuf message definition. It does not change any code behavior, protocol logic, or security properties.

This commit fixes a subtle cleanup bug in the Bluetooth pairing function on Trezor hardware wallets. Before the fix, if a caller supplied an advertising name that was too long, the function returned early without unlocking an important system lock (irq_lock). Leaving that lock held could freeze or crash the device. The fix moves the length check before the lock is taken, so the bad-input path no longer skips the unlock.

This commit fixes a bug in the Trezor hardware wallet's Bluetooth handling. Previously, the device name sent to the Bluetooth chip when entering pairing mode or switching Bluetooth on was not truncated to the maximum allowed length. This could cause the Bluetooth stack to receive an oversized name, potentially leading to unstable behavior, pairing failures, or memory corruption in the Bluetooth firmware. The fix ensures the name is shortened to the advertised-name limit before being passed along.

This commit is a small UI layout change for the Trezor hardware wallet. It lets a screen that normally shows three word choices display only two choices by leaving one slot blank and hiding the separator line next to it. There is no indication this fixes a security bug; it appears to be a feature tweak for a future user interface.

This commit only adds new automated tests that simulate a user cancelling the backup step during device setup (ResetDevice). It does not change the actual Trezor firmware code, wallet logic, or fix any bug. It is a testing improvement with no direct security impact on shipped devices.

This commit only updates the expected visual-output fingerprints used by the device's automated UI tests. It does not change any firmware, application, or security code. The test names were adjusted because the corresponding test code was likely refactored to add a 'normal' versus 'try_to_cancel' parameter. There is no user-facing or security-relevant change.