Trezor firmware

This commit is a user-interface layout tweak for the Trezor hardware wallet's Bolt design. It widens the 'Continue' button and replaces some text buttons with icons in certain confirmation dialogs. There is no security-relevant change visible in the code diff.

This commit only updates the expected hash values (called 'fixtures') used by the project's automated user-interface tests. No actual product code was changed, so there is no direct security risk in this commit itself. The updated hashes likely reflect normal changes in screen layouts, text, or rendering from earlier development work.

This commit changes one Czech translation string for the word 'Continue' from 'Pokračujte' to 'Pokračovat', and updates the corresponding translation signature metadata. There is no security relevance.

This commit adjusts a GitHub Actions workflow that synchronizes code between two Trezor repositories. The changes remove a leftover default authentication token, explicitly request only the write permission needed for contents, and drop an unnecessary git command. These are hardening improvements rather than a fix for an active vulnerability.

This commit fixes a validation bug in Trezor's Ethereum transaction signing. Previously, the device only checked whether the initial data chunk was too large when the transaction also contained non-zero data length. Now it always rejects an oversized initial chunk, even when the declared data length is zero. The change is defensive and closes a path where malformed input could slip past validation.

This commit only adds a one-line changelog note saying a host-disconnection handling bug was fixed for the T3W1 device. There is no actual code change in the commit, so it cannot by itself introduce or fix a security issue. It merely documents a fix that happened in an earlier pull request (#6676).

This is a developer tooling change for Trezor hardware wallets. It improves an internal Python script that checks whether signed firmware images are correctly built. The script now also validates a special 'secmon-wrapped' production-test image used on at least one Trezor model. There is no change to device firmware, no runtime security fix, and no evidence of a vulnerability being patched.

This commit is a routine vendor dependency update, bumping the internal ts-tvl package from version 2.4 to 2.5. The diff only changes one version number in a lock file. There is no visible security fix, vulnerability description, or code change in the supplied materials.

This commit removes a custom YAML loader that was used only in production-test helper code. The custom loader accepted special Python object tags so it could read model config files. It is being replaced with the standard safe YAML loader because an upstream dependency now writes files in a simpler format. The change reduces the risk of accidentally reintroducing unsafe YAML parsing in test tooling, but it is in test code rather than the wallet firmware itself.

This commit is a code-quality cleanup that changes many function parameters from signed integers (`int`) to unsigned size types (`size_t`) where only non-negative lengths or sizes make sense. It also removes some now-unnecessary negative-value checks and adjusts callers/tests accordingly. The change is defensive: using `size_t` prevents accidental negative lengths from being interpreted as huge positive values, which can cause memory corruption or information leaks. The commit itself does not claim to fix a specific vulnerability, and no external security advisory is supplied.

This commit only changes the on-screen text labels shown when a Trezor device asks the user to confirm a Stellar blockchain authorization. It renames labels from formats like 'Authorization 2' and '1-2-1' to 'Authorization #2' and '#2.1.1'. There is no security vulnerability or fix here; it is a user-interface clarity improvement.

This commit adds a new Trezor feature that lets users sign Stellar Soroban smart-contract authorization entries. The device now supports a new message type where it derives the user's Stellar address, shows confirmation screens, and produces an Ed25519 signature over a protocol-defined authorization payload. The change is a feature addition rather than a bug fix, and the signing flow includes user confirmation steps.

This commit only adds new automated tests for signing Stellar Soroban authorizations. It does not change any production firmware, wallet logic, or cryptographic code. There is no security vulnerability here.

This commit is a routine maintenance update for the Stellar feature in Trezor firmware. It adds three new user-facing text strings (for device screen prompts), updates translation signatures, refreshes expected test screenshot hashes, and adjusts dependency version-locking rules for the Stellar SDK. There is no indication of a security fix or vulnerability in the changes themselves.

This commit is a straightforward code cleanup: it moves several Stellar Soroban serialization helper functions from an operation-specific file into a shared writers module so both transaction signing and standalone authorization signing can use the same code. No behavior changes, bug fixes, or security fixes are visible in the diff.

This commit is a straightforward code cleanup: it moves helper functions for formatting Stellar Soroban smart-contract values and showing confirmation screens from one file to another shared file. No security behavior changes are visible in the diff. The only functional tweak is narrowing an exception handler from a broad 'except Exception' to 'except OverflowError' when formatting timestamps, which is a minor hardening improvement, not a vulnerability.

This commit updates Trezor's Stellar/Soroban smart-contract support to match a newer Stellar protocol version (Protocol 27). It renames the credential type from the older SOROBAN_CREDENTIALS_ADDRESS to SOROBAN_CREDENTIALS_ADDRESS_V2 and updates the related field name from address to address_v2 across the firmware, Python library, Rust client, and tests. The older credential type is intentionally no longer supported. There is no direct evidence in the commit of a security vulnerability being fixed; it reads as a routine protocol compatibility update.

This is a purely cosmetic change to how firmware binary file sizes are displayed in GitHub CI build summaries. It swaps the order of columns (size first, filename second) and adjusts alignment/sorting so the output is easier to read. There is no change to firmware code, build artifacts, or security behavior.

This commit is a user-interface polish change for the Trezor hardware wallet. It introduces a helper that adds colons to on-screen labels only for certain visual themes (Bolt and Caesar), and updates Solana transaction confirmation screens to use it. There is no security-relevant behavior change.

This commit is a code cleanup in the Trezor hardware wallet's user interface. It replaces hard-coded colon punctuation (like 'Amount:') with a helper function called with_colon that adds the colon in a translation-friendly way. There is no security issue here.

This commit removes an extra colon that was being added to Solana transaction confirmation screens on Trezor devices. The change is cosmetic: it stops showing a duplicate colon in front of property names (like 'Fee payer:' becoming 'Fee payer'). There is no direct evidence in the commit that this fixes a security vulnerability, but user-interface clarity on a hardware wallet can indirectly affect security if a misleading label makes a user approve something they misunderstand.

This commit removes duplicate colons from on-screen text labels in the Trezor hardware wallet's Solana app and Bolt UI layout. It is a cosmetic/user-interface cleanup with no security relevance.

This commit makes two tiny UI code cleanups: it removes an unnecessary colon from a transaction summary label and adjusts a Python type-hint return type. There is no indication these changes fix a security issue or affect how funds or secrets are handled.

This commit only updates the expected visual test snapshots (hashes of screen images) in a test data file. It does not change any firmware, application, or cryptographic code. There is no direct security relevance visible in the commit itself.

This commit is a minor code cleanup that changes type annotations in a Solana-related layout file. It removes an unused import and switches three variable type hints from a broader type (PropertyType) to a narrower one (StrPropertyType). There is no functional code change, no behavior change, and no security fix.