Trezor firmware

This commit adds an optional user-interface feature for Solana transactions on Trezor hardware wallets. When enabled, long Solana addresses are shown on the device screen in smaller groups of characters (chunks of 4) instead of one long string, making them easier for users to read and verify. There is no indication this change fixes a security vulnerability; it is a usability improvement.

This commit only adds test code for Trezor's Ethereum clear-signing feature. It introduces debug-only test descriptors, unit tests, device tests, and expected screen snapshots. There is no change to production behavior or any fix for a security issue.

This commit adds support in Trezor's Ethereum 'clear signing' feature for displaying array (multi-value) fields on the device screen. It also fixes a minor display quirk where booleans were being treated as numbers. There is no direct evidence in the commit that this fixes an active security vulnerability; it reads as a feature improvement with some defensive hardening against malformed display definitions.

This commit adds a new optional field to Trezor's Ethereum clear-signing protocol that lets a token amount be tied to a fixed contract address rather than pulled from transaction data. It is a feature addition, not a bug fix, and there is no evidence in the commit that it addresses a security flaw. The change does not appear to introduce an obvious vulnerability, but it slightly expands the attack surface by adding another way token addresses are resolved.

This commit adds two new ways to display Ethereum transaction details on a Trezor screen: a 'raw' formatter that shows values as-is (numbers, text, or hex bytes) and a 'date' formatter that turns a Unix timestamp into a readable date. It also wraps some existing parsing and display steps in try/except blocks so failures are logged and re-raised. There is no direct evidence this fixes an active security bug; it looks like a feature addition for clearer transaction signing.

This commit fixes a small Rust UI bug in Trezor's 'Caesar' firmware layout. When a user viewed an 'info' page during a confirmation prompt, the device previously failed to return the expected 'INFO' response and instead threw a type error. The patch adds the missing case so the info page is handled correctly. This is likely a user-experience or defensive bug fix rather than a critical security vulnerability, but it could affect how device confirmations behave.

This is a minor test-only adjustment for the Caesar user interface layout. It changes a test helper so that it only tries to open the menu on the last page of a multi-page screen, because earlier pages do not have a menu/info button. There is no change to production firmware behavior or security.

This commit is a minor user-interface polish change. After a user changes the auto-lock timeout setting on a Trezor device, the device now returns to the dedicated Auto-Lock menu instead of the broader Security menu. It does not change any security policy, cryptographic behavior, or data handling. The accompanying test updates simply expect the new screen.

This commit changes how Trezor hardware wallets derive TRON addresses. Previously, the code loaded the private key into Python memory and computed the public key from it. Now it uses a precomputed public-key hash already available from the keychain. This is a defensive hardening change that reduces the chance of private-key exposure in the Python layer, but it does not by itself fix a known exploitable vulnerability.

This commit adds support for a new Tron blockchain transaction type called WithdrawBalanceContract, which lets users claim their voting rewards. It also improves the on-device confirmation flow for claim transactions so the device warns and shows the owner address when the transaction is being signed on behalf of a different account. There is no indication of a security vulnerability in the change itself; it appears to be a normal feature addition with stronger user confirmation.

This commit fixes a visual glitch on the Trezor T3W1 device where the device menu would visibly jump or flicker when it refreshed. The fix preserves the menu's current scroll position across refreshes by passing an extra offset value through the UI API. There is no indication this change addresses a security vulnerability.

This is a code cleanup (refactor) for the device menu on a specific Trezor hardware wallet model. It changes how menu actions are represented internally (from numbers to named strings) and simplifies how the menu decides which submenu to show next. There is no indication this fixes a security bug or introduces a vulnerability.

This commit fixes a spelling mistake in a code comment ('Chcek' to 'Check'). No program logic, user interface behavior, or security properties were changed.

This is a one-line code cleanup in the user-interface code for a Trezor hardware wallet screen. It changes a mutable borrow (`deref_mut`) to an immutable borrow (`deref`) where the code only reads a value. This is a routine Rust style/refactor change with no visible security effect.

This commit only adds a development dependency called construct-typing to improve type checking and adjusts some type-checker ignore comments. It does not change how the Trezor firmware or tools behave at runtime, and it does not fix or introduce any security issue.

This commit only changes a test file so that FIDO2/WebAuthn tests are skipped on Bitcoin-only firmware builds. It does not change any production code, wallet logic, or security behavior. There is no vulnerability or security fix here.

This commit fixes a regression in the Trezor command-line tool (trezorctl). A recent earlier change accidentally removed a shortcut that skips asking the user for their passphrase when the caller explicitly says it is not needed. Because of that regression, trezorctl could prompt for or require a passphrase even in situations where it should not, such as when running commands that do not need a wallet. The patch restores the intended behavior by adding a `prompt_passphrase` flag and returning an empty passphrase when it is false.

This commit fixes the `trezorctl get-session` command in Trezor's Python library. It prevents crashes when an invalid session ID is supplied, ensures a required pairing step is completed when resuming secure (THP) sessions, and changes the meaning of `passphrase=False` from 'always use a standard wallet' to 'do not ask for a passphrase.' These are reliability and state-correctness fixes in the command-line tool, not the hardware wallet firmware itself.

This commit only updates expected test screenshots (called UI fixtures) recorded as cryptographic hashes. The firmware code itself is not changed. The message explains that a helper function called ensure_unlocked() no longer creates a new session, so tests that show a PIN keyboard afterward now produce different screen images. This is a routine test-maintenance change with no direct security impact.

This is a small optimization in the Trezor Python library. The `ensure_unlocked()` helper used to pick or create a wallet session, which forced the hardware wallet to derive the master seed just to check if the device was unlocked. The new code instead sends a harmless 'ApplyFlags(0)' command, which requires the user to enter their PIN but does not need seed derivation. This is a performance and usability improvement, not a security fix. There is no evidence in the commit of a vulnerability being patched.

This is a small internal cleanup in the Python helper library that handles Trezor One firmware files. It removes two exposed fields ('magic' and 'code_length') from a Python class and renames them to private internal names ('_magic' and '_code_length'). The actual binary parsing behavior is unchanged: the 'TRZR' magic bytes are still required, and the code length is still computed and embedded exactly as before. There is no security fix or vulnerability here.

This is a small code cleanup in Trezor's Python firmware-handling library. It removes an unused firmware header type for Nordic (NRF) chips and renames an internal 'magic' field so it is no longer treated as a user-facing header type. It also fixes two default boolean values from the integers 1 to the Python booleans True. There is no security-relevant change here.

This commit adds new Python code to the Trezor firmware tools for parsing and building Nordic Semiconductor (nRF) style firmware images. It is a feature addition, not a fix. The code handles firmware headers, TLV metadata blocks, SHA-256 digests, Ed25519 signatures, and device model identifiers. There is no indication in the commit that this resolves a security bug or is being released as a security patch.

This commit fixes a small bug in the Python Trezor library that identifies which Trezor hardware model is being used. Previously, the code would crash when it saw a valid but unrecognized model identifier. The fix makes the parser accept any valid model identifier instead of rejecting unknown ones. This is a routine robustness improvement, not a clear security vulnerability, but it could affect how firmware updates or device interactions behave if a new model is introduced.

This commit updates a bootloader linker script for a new STM32U58-based Trezor variant to support an alternative 'PQ' (post-quantum) bootloader header format. It adds a code-size symbol, a small padding section, and changes how the bootloader image is padded to its maximum size. There is no direct evidence in the commit that this fixes a security vulnerability; it reads as a build/enablement change for a new hardware configuration.