Trezor firmware

This commit tightens security for a new Ethereum feature (EIP-7702 account delegation) in Trezor hardware wallets. Previously, the wallet would recognize certain smart-contract delegate addresses on any chain, and would allow signing on unknown chains with only a generic warning. Now it checks that both the chain ID and the delegate address match an approved list, and it refuses to sign on unknown chains entirely. This prevents a malicious app or website from tricking a user into authorizing a delegate on an unexpected network.

This commit fixes a filename-renaming step in the project's automated nightly build pipeline. It ensures ARM64 emulator files get the correct name expected by another testing tool. There is no change to the actual Trezor firmware code, device behavior, or security-sensitive logic.

This is a routine housekeeping change to reduce clutter in Git's status output for a third-party component (the MicroPython submodule). There is no indication it changes any code that runs on the Trezor device or affects security.

This commit removes a feature in Trezor's Ethereum signing code that allowed users to sign EIP-7702 authorization messages with chain_id set to 0, which previously made the signature valid on all EVM networks. The change now rejects chain_id 0 with an explicit error. This is a defensive security hardening step: a universally valid authorization signature could let an attacker or malicious application reuse a single signed authorization across unexpected chains, potentially changing what account controls a user's address on another network. The commit itself does not describe a specific attack or credit an external reporter.

This commit adds a 135 millisecond delay during startup of the Tropic secure chip inside Trezor hardware wallets. The delay works around a bug where the chip briefly reports it is in 'maintenance mode' right after power-on, which causes an unnecessary reboot and slows down startup. It is a performance fix, not a security vulnerability fix, and it only affects non-production-test firmware builds.

This commit simply updates documentation and a code comment to remove outdated references to Travis CI and replace them with current CI references. It does not change any executable code, cryptographic logic, or security behavior.

This commit only updates test data. It corrects the capitalization (checksum) of Ethereum addresses used in automated tests and refreshes the expected screen-shot hashes those tests compare against. There are no changes to the actual Trezor firmware code that users run, so this cannot affect real devices or user funds.

This commit changes the Trezor Python library so that, when setting up a Trezor Model One (the original Trezor 1 device), it now performs an entropy check by default if the device runs firmware 1.13.1 or newer. Previously, the library only enabled this check on newer Trezor models and treated all Model One devices as not supporting it. An entropy check helps verify the device is generating randomness properly during wallet setup. The change is a defensive fix to enable a security feature on a previously excluded device line, not a patch for an active vulnerability.

This commit changes how a Trezor hardware wallet handles failures when generating strong random numbers. Previously, the function could return 'false' when an entropy source failed, and callers might ignore that failure. Now the device deliberately halts (shows a fatal Red Screen of Death) if any entropy source fails. This is a defensive hardening change, not an active bug fix for a known exploit, but it removes a class of safety issues where weak or predictable randomness could be used by mistake.

This commit is a straightforward internal code cleanup in the Ethereum transaction signing module. It moves existing digest-calculation logic into two new helper functions, _start_digest() and _finish_digest(), without changing what data is hashed or how the transaction is signed. There is no indication of a security fix or behavior change.

This commit is a small code cleanup in the Ethereum signing module for Trezor hardware wallets. It replaces a manual, step-by-step RLP (a data-encoding format used by Ethereum) header-and-field writing process with a single helper call that does the same thing. There is no indication of a security bug being fixed.

This commit is a routine cleanup that removes the old SCons build system files from the Trezor Core firmware repository. It deletes Makefiles, SConscripts, and related Python helper scripts, but does not change any firmware source code, cryptographic logic, or runtime behavior. The commit message explicitly says it is a chore with no changelog entry, indicating it is not a security fix.

This commit is a code cleanup (refactor) for how Trezor's Ethereum app builds the transaction hash for EIP-1559 transactions. It moves the existing hashing steps into two helper functions and removes a duplicated list of transaction fields. There is no change to what data is signed or how it is signed, and no security bug is introduced or fixed.

This commit updates Trezor's embedded MicroPython interpreter from an older version to 1.28.0. It pulls in several upstream MicroPython bug fixes, including stricter buffer-size checks for converting integers to bytes, a new stack-safety API, preventing Ctrl+C from interrupting frozen boot code, fixing a stdout write return value, and blocking accidental creation of bytearrays from plain strings without an encoding. The changes are mostly defensive hardening and compatibility fixes rather than a single known exploit patch. There is no vendor statement that this is a security fix, no CVE, and no credited researcher.

This commit is a simple code cleanup that replaces a common MicroPython string-creation pattern with a new helper function. It does not change what the code does, only how it is written. There is no security issue visible in the change.

This commit updates the bundled MicroPython software component from one version to another (1.28.0). No code changes within the Trezor project itself are shown, and no security-related information is provided in the commit title or message.

This is a large but straightforward internal cleanup: the project switched from using the MicroPython `ubinascii` module's `hexlify`/`unhexlify` functions to the standard Python `bytes.hex()` and `bytes.fromhex()` methods. The change removes the `ubinascii` module from the firmware build and updates many source and test files to use the new built-in methods. There is no security fix or vulnerability being patched here.

This commit is a routine code cleanup in the Trezor firmware's embedded MicroPython modules. It replaces an older, two-step object allocation pattern with a newer helper that allocates memory and sets the object type in one step. The change touches many cryptographic object constructors but does not alter security logic, input validation, or behavior. It is best understood as a maintenance refactor to stay compatible with upstream MicroPython, not a security fix.

This commit is a routine maintenance refactor. MicroPython removed its built-in 'utimeq' module, so Trezor copied the same code into its own firmware tree and renamed it to 'timeq'. There is no security bug being fixed and no new vulnerability being introduced that is visible in the diff.

This is a code cleanup change in Trezor's firmware that swaps one MicroPython internal helper for another. It replaces calls that create byte or string objects from a vstr buffer with newer, purpose-built helpers. The commit message says the new string helper also does UTF-8 validation, which can be skipped where performance matters. The change itself does not introduce a known vulnerability; it is a refactor to match upstream MicroPython conventions.

This commit is a routine internal cleanup that switches how Trezor's firmware defines built-in MicroPython object types. It replaces older, manually-written type structures with a newer macro provided by the upstream MicroPython project. There is no user-visible change, no bug fix, and no security patch in the diff.

This commit is a straightforward internal code refactor. It adds a small C wrapper file so that Rust code can call two specific internal MicroPython functions that are declared as static/inline in headers. There is no user-facing change, no bug fix, and no security-relevant behavior change visible in the diff.

This commit updates Trezor firmware code to match a renamed and slightly changed version of the micropython uzlib decompression library. It renames types (e.g., `uzlib_uncomp` to `uzlib_uncomp_t`), replaces old return-code constants (`TINF_OK` with `UZLIB_OK`), and adds a new `source_read_data` field used by the library's callback mechanism. The changes are a routine refactor to stay compatible with an upstream micropython update. There is no direct evidence in the commit that this fixes a security vulnerability, but any mismatch between firmware and its decompression library could in principle cause crashes or incorrect behavior during firmware updates.

This commit is a routine build-system update for the Trezor firmware. It changes where the build process looks for the MicroPython cross-compiler binary (mpy-cross) and synchronizes a configuration header with newer MicroPython code. There is no indication this fixes or introduces a security vulnerability.

This commit updates the Trezor firmware build system to use a newer MicroPython mechanism for tracking special memory pointers called 'root pointers.' It removes hard-coded lists of these pointers from configuration files and instead collects them automatically from source files during the build. The change itself is a build-system modernization and does not appear to fix an active security bug, but it helps prevent a class of future memory-management mistakes that could, in theory, lead to device instability or security issues.