TZ
← All projectsTrezor

Trezor firmware

Firmware monorepo for Trezor One, Model T, and Safe devices.

BitcoinHardware walletsNormal
Repository coverage

3768 commits in the local evidence base

Every captured commit receives deterministic security triage and a separate communication-quality score. Security candidates and broader second-pass signals receive full-patch Ollama analysis.

1328security candidates435second-pass queue3191AI analyses
201commits · 30 days
450commits · 60 days
1759commits · 180 days
2832commits · 365 days
Backfill bands
Aug 5 → Feb 61298 seen115 candidatesComplete
Feb 6 → Jun 6775 seen58 candidatesComplete
Jun 6 → Jul 6217 seen13 candidatesComplete
Jul 6 → Aug 5360 seen54 candidatesComplete
Commit communication

Does the history explain itself?

Message quality measures whether a commit identifies its scope, purpose, rationale, testing, and supporting references. It does not change the security-severity score.

68/100 average clarity
841Strong · 80–100
1731Adequate · 60–79
1189Thin · 40–59
7Opaque · 0–39
1security candidate with opaque commit messaging
Read the scoring rubric →
Developer activity

Who is changing the project?

Public Git author strings; identities are not independently verified.

DeveloperCommitsCandidatesAnalyzedHigh riskMessage avg.
tychovrahe394164355667
Jakub Janků1023067681
Roman Zeyde721230639372
obrusvit333135281364
cepetr301111228259
PrisionMike153101149271
Andrew Kozlik893885267
Petr Susil1159286
Martin Pastyřík291025175
M1nd3r292106248071
Ioan Bizău23076230059
Lukas Bielesch1067592066
Analysis record

Published AI watches

Last scanned 38 minutes ago

Informational 15 AI analysisMessage 90 · Strong
TZ TrezorTrezor firmware BitcoinHardware wallets

ci(core): reuse HW tests Slack webhook

This is a routine GitHub Actions workflow fix. It changes which Slack webhook secret is used for nightly test failure notifications and removes a now-unnecessary safety check. There is no security vulnerability in the change itself.

abfe74f9by Michal Kazda+1−51 file
No security note in commit
Informational 15 AI analysisMessage 90 · Strong
TZ TrezorTrezor firmware BitcoinHardware wallets

test(clear_signing): name the skipped cases

This commit only improves a test report for Trezor's clear-signing feature. It changes how skipped test cases are listed in a nightly summary, showing each skipped case's source file and calldata size instead of just counting them by reaso…

98deb5b0by PrisionMike+25−92 files
No security note in commit
Informational 15 AI analysisMessage 95 · Strong
TZ TrezorTrezor firmware BitcoinHardware wallets

test(clear_signing): run the cases without display format

This commit only changes test scripts and documentation for the Trezor firmware clear-signing test suite. It makes the tests run more registry cases—specifically those where the developer definitions do not yet have a display format—so the…

05c1f4efby PrisionMike+63−225 files
No security note in commit
Informational 15 AI analysisMessage 72 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

fix(translations): fix failing tutorial test in FR and small update to PT

This commit updates French and Portuguese translation strings in the Trezor firmware and refreshes the translation signature metadata. The changes are purely wording adjustments (for example, replacing abbreviations like 'nº' with the full…

29cbc419by Michal Kazda+19−193 files
No security note in commit
Informational 10 AI analysisMessage 95 · Strong
TZ TrezorTrezor firmware BitcoinHardware wallets

chore(core/rust): reduce coverage map size

This commit changes a code-coverage tracking map inside the Trezor firmware from a claimed capacity of 1,048,576 entries down to 65,536 entries. The commit message says the old capacity was never truly that large because the heapless libra…

No cryptographic or secret-handling code changedNo input parsing, deserialization, or memory allocator changesChange is in a debug/test instrumentation module (coverage)
9bf2fc3aby M1nd3r+1−11 file
No security note in commit
Informational 15 AI analysisMessage 57 · Thin
TZ TrezorTrezor firmware BitcoinHardware wallets

chore(translations): sync Crowdin translations

This commit is a routine update of translated user-interface text strings for the Trezor hardware wallet. It adds new translations (for example, warnings about exporting public keys and Solana blind-signing prompts), updates existing wordi…

b2e8b5e6by Thalarion+141−1837 files
No security note in commit
Informational 12 AI analysisMessage 67 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

test(clear_signing): edge cases for arrays

This commit only adds new test cases for Ethereum clear-signing array parsing. It does not change any production code, so it cannot introduce a new security vulnerability on its own. The tests verify that malformed arrays (out-of-bounds of…

test-only changeno production code modifiedadds defensive test coverage for ABI decoding edge cases
dcdf3068by PrisionMike+169−01 file
No security note in commit
High 70 AI analysisMessage 62 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

refactor(core): harden task switching against fault injections

This commit hardens the Trezor firmware's task scheduler against fault-injection attacks. These attacks use physical techniques like voltage glitches or laser pulses to trick the device into executing code with higher privileges than inten…

Fault-injection hardening (FIH) explicitly mentioned in commit title and code commentsPrivilege-level transition split into multiple guarded stepsAdded runtime invariant check that only the kernel task may run privileged
2f159c6bby cepetr+16−51 file
Vendor flagged security relevance
Informational 15 AI analysisMessage 67 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

fix(tests): removed unused is_dynamic

This commit only removes an unused parameter called `is_dynamic` from test helper functions and from test data in three test files. It does not change any production firmware code, wallet behavior, or security logic. It is a cleanup of the…

2ada2691by PrisionMike+6−323 files
No security note in commit
Informational 21 AI analysisMessage 62 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

feat(clear_signing): update proto defs for features to be supported.

This commit updates the data-format definitions used by Trezor devices for Ethereum 'clear signing' (showing human-readable details of smart-contract interactions). It adds support for more numeric types, new path-step structures, and extr…

Schema expansion increases attack surface for future clear-signing parser logic, but no new parser logic is present in this commit.Replacement of NotImplementedError with InvalidFormatDefinition is a defensive change that turns unimplemented paths into a handled error rather than a crash/DoS vector.New optional fields and deprecated old fields (is_dynamic, lookup_address) are backward-compatible changes.
84cb6a4bby PrisionMike+1207−979 files
No security note in commit
Informational 19 AI analysisMessage 62 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

chore(python): fix protocol_v1 probe for bridge transport

This is a bug-fix patch in the Python Trezor client library. It changes how the software probes whether a connected device uses the older protocol v1. Previously, the probe tried to read and throw away leftover data, but that read could ac…

No security-relevant signal in commit message or diffFix is described as a connectivity/functional bug, not a vulnerabilityNo mention of CVE, researcher credit, or security advisory
46492ba4by M1nd3r+18−124 files
No security note in commit
Informational 15 AI analysisMessage 80 · Strong
TZ TrezorTrezor firmware BitcoinHardware wallets

feat(core): show language name in change confirm

This commit is a user-interface improvement, not a security fix. It changes the language-change confirmation prompt on Trezor devices so that it shows a human-readable language name (for example, 'French') instead of a raw code like 'fr-FR…

5ff5cba0by Michal Kazda+295−67 files
No security note in commit
Informational 15 AI analysisMessage 67 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

fix(translations): fix failing tests in ES and FR

This commit updates Spanish and French translation strings in the Trezor firmware and refreshes the translation signature file. The changes are purely textual wording adjustments (for example, changing 'Mostrar palab.' to 'Mostrar palabras…

9a12ab12by Michal Kazda+15−103 files
No security note in commit
Low 47 AI analysisMessage 85 · Strong
TZ TrezorTrezor firmware BitcoinHardware wallets

chore(crypto): hardening against potential side-channel leakage

This commit hardens cryptographic code in Trezor firmware against two potential side-channel leaks. First, it simplifies how a secret condition value is checked inside an assert statement so the compiler produces only one branch instead of…

Side-channel hardening in constant-time cryptographic primitivesReplacement of double-evaluation volatile assert with single-branch assertElimination of secret-dependent memory access in elliptic-curve scalar multiplication
7829d7c7by M1nd3r+27−93 files
Vendor flagged security relevance
Informational 15 AI analysisMessage 72 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

feat(ci, clear_signing): add clear signing device tests as a nightly run.

This commit adds a new nightly automated testing workflow for Ethereum 'clear signing' on Trezor hardware wallets. It does not change any wallet firmware code that users run; it only adds test scripts, CI configuration, documentation, and …

fea125baby PrisionMike+2986−2117 files
No security note in commit
Informational 15 AI analysisMessage 57 · Thin
TZ TrezorTrezor firmware BitcoinHardware wallets

chore(core): move `keccak_32` to unittests

This commit is a routine code cleanup. It removes a small helper function called keccak_32 from a shared crypto utility file and places an equivalent helper directly inside the only test file that still uses it. There is no change to how t…

f3225451by Roman Zeyde+8−122 files
No security note in commit
Informational 15 AI analysisMessage 63 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

chore: remove SmartCash

This commit removes support for a cryptocurrency called SmartCash from Trezor hardware wallets. It deletes coin definitions, support entries, and a custom cryptographic curve used only by SmartCash. There is no security vulnerability being…

No security-relevant signals detectedPure feature removal / code cleanup
b6d65c00by Roman Zeyde+5−52916 files
No security note in commit
Informational 15 AI analysisMessage 77 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

chore(common,core,legacy,crypto): remove Groestlcoin

This commit removes all support for the Groestlcoin cryptocurrency from Trezor firmware. It deletes coin definitions, the custom Groestl hash algorithm code, related address/transaction handling, and tests. There is no security vulnerabili…

No security-relevant change: pure feature removalNo new attack surface introducedNo vulnerability patched or created
e22d597dby Roman Zeyde+41−446845 files
No security note in commit
Informational 15 AI analysisMessage 47 · Thin
TZ TrezorTrezor firmware BitcoinHardware wallets

chore(core): remove Tezos

This commit removes all support for the Tezos cryptocurrency from Trezor firmware, software libraries, and documentation. It is a feature-removal change, not a security fix or vulnerability patch. There is no indication in the commit that …

433075c0by obrusvit+9531−1751964 files
No security note in commit
Informational 24 AI analysisMessage 85 · Strong
TZ TrezorTrezor firmware BitcoinHardware wallets

fix(legacy): lower maximum auto-lock delay to 149 hours

This update reduces the longest allowed screen-lock timeout on older Trezor devices from about 6 days down to 149 hours (just over 6 days). It makes the legacy firmware behave the same as newer Trezor firmware and prevents users from setti…

Bounds enforcement added for a configurable security-relevant timeoutAlignment of security policy between legacy and core firmware variantsTest coverage added for boundary values above and below new maximum
c108f275by Ondřej Vejpustek+16−64 files
No security note in commit
Repository ledger

Explore captured commits

Expand any commit for its author, full message, clarity score, changed files, triage signals, analysis, and source link.

AI review queuedrefactor(core/ethereum): simplify `request_initial_data()` loadingby Roman Zeyde · b2959408 · Jul 19, 2026 · 1 fileMessage 77 · AdequateInformational 12Details
Commit message · Roman Zeyde

refactor(core/ethereum): simplify `request_initial_data()` loading

Also, deduplicate RLP header and initial data hashing.

[no changelog]

77/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 12/100

This commit is a code cleanup in the Ethereum transaction signing module. It replaces a manual byte-copying loop with a simpler buffer extension approach and removes duplicate code that wrote the RLP header and hashed the data in two different places. There is no indication of a security bug being fixed.

AI review queuedrefactor(core/ethereum): simplify and rename `_send_request_chunk()`by Roman Zeyde · 730ea609 · Jul 19, 2026 · 1 fileMessage 77 · AdequateLow 47Details
Commit message · Roman Zeyde

refactor(core/ethereum): simplify and rename `_send_request_chunk()`

Also, check `EthereumTxAck.data_chunk` size, similar to `apps.common.chunked.get_data_chunk()`.

[no changelog]

77/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 47/100

This commit refactors how a Trezor hardware wallet asks for pieces of an Ethereum transaction's data from the host computer. It renames an internal helper and, importantly, adds a size check so the host cannot return a chunk larger than the device requested. That oversized-chunk condition could previously lead to memory corruption or unexpected behavior during transaction signing.

AI review queuedrefactor(core/ethereum): import `HashWriter` only for type-checkingby Roman Zeyde · ad23bda4 · Jul 19, 2026 · 1 fileMessage 62 · AdequateInformational 15Details
Commit message · Roman Zeyde

refactor(core/ethereum): import `HashWriter` only for type-checking

[no changelog]

62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This is a minor code cleanup in the Ethereum transaction signing module. It moves an import statement so that a helper class (`HashWriter`) is only imported during type-checking, not at runtime. There is no functional change, no bug fix, and no security relevance.

AI review queuedchore(core): add new strings for EIP-7702by Roman Zeyde · 18f1770c · Jul 17, 2026 · 6 filesMessage 80 · StrongInformational 15Details
Commit message · Roman Zeyde

chore(core): add new strings for EIP-7702

https://www.figma.com/design/3wF1eh3Ftj0XGX7wFmev8t/EIP-7702

[no changelog]

80/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit only adds and updates user-facing text strings (labels, warnings, and confirmation messages) for a new Ethereum feature called EIP-7702. It does not change any code that handles private keys, signing logic, transaction parsing, or security checks. There is no direct security issue visible in this change.

AI review queuedfix(tests): make `verify_cert_chain()` accept longer certificate chainsby Ondřej Vejpustek · c3d46193 · Jul 17, 2026 · 1 fileMessage 72 · AdequateInformational 12Details
Commit message · Ondřej Vejpustek

fix(tests): make `verify_cert_chain()` accept longer certificate chains

[no changelog]

72/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
second-pass: broader security terminology
AI analysis · Informational 12/100

This commit changes only a test helper function in the Trezor firmware test suite. It moves a common-name check to the beginning of certificate-chain verification so the function can handle chains longer than before. There is no change to the actual device firmware or to any security-critical runtime code.

AI review queuedrefactor(core/ethereum): simplify calldata streaming flowby Roman Zeyde · ca9c3caf · Jul 16, 2026 · 4 filesMessage 85 · StrongLow 31Details
Commit message · Roman Zeyde

refactor(core/ethereum): simplify calldata streaming flow

There is no need for calling `confirm_tx_data` and then `confirm_data_and_summary`,
since we can do calldata streaming (while hashing and confirming) in `confirm_tx_data`.

[no changelog]

85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 31/100

This is a code cleanup (refactor) in Trezor's Ethereum transaction signing. It merges two internal steps into one so that transaction data is streamed, hashed, and shown to the user in a single pass instead of two. The commit message says there is no functional change, and the visible code preserves the same hashing and confirmation behavior. UI test snapshots changed, which is expected because the on-screen flow order changed, but no security bug is evident from the diff alone.

AI review queuedfeat(nordic): add support for different NCS sdk versionsby tychovrahe · 253c4f87 · Jul 16, 2026 · 10 filesMessage 62 · AdequateInformational 19Details
Commit message · tychovrahe

feat(nordic): add support for different NCS sdk versions

[no changelog]

62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 19/100

This commit updates Trezor's Bluetooth firmware build system so it can compile against two different Nordic SDK versions (an older 2.9 and a newer 3.3). It adds version checks, pins the correct compiler toolchain, and renames a few Bluetooth and SPI constants so the same source code works with both SDKs. There is no obvious security bug being fixed; it is primarily a compatibility and build-reliability change.

AI review queuedrefactor(core/ethereum): handle staking/yielding in `confirm_tx_data()`by Roman Zeyde · 6c158b50 · Jul 15, 2026 · 4 filesMessage 85 · StrongLow 27Details
Commit message · Roman Zeyde

refactor(core/ethereum): handle staking/yielding in `confirm_tx_data()`

This way, we don't need to call `get_progress_indicator()`,
since all the data has been already loaded and hashed.

[no changelog]

85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 27/100

This is an internal code cleanup in Trezor's Ethereum transaction signing. It changes how staking and yield-farming transactions hand off their user-confirmation step so the confirmation happens inside the same routine instead of being returned as a separate progress indicator. The commit message says the goal is to avoid needing a progress indicator because all transaction data is already loaded and hashed. There is no direct evidence in the commit of a security bug being fixed, but the change touches the code that decides what users see before they approve high-value operations like staking and vault deposits/withdrawals. The large set of updated UI test hashes shows the on-screen flow changed, which is expected for a refactor of this kind.

AI review queuedfix(stellar): properly bound string lengthby Jakub Janků · 888aa308 · Jul 15, 2026 · 3 filesMessage 88 · StrongModerate 60Details
Commit message · Jakub Janků

fix(stellar): properly bound string length

Currently, the length of all bounded strings is checked using
len(str). This returns the number of Unicode code points. However,
the XDR spec defines string object<m> as a sequence of at most m
bytes, see https://datatracker.ietf.org/doc/html/rfc4506#section-4.11.
A single Unicode code point can consist of multiple bytes.

[no changelog]

88/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Moderate 60/100

This commit fixes a length-check bug in Trezor's Stellar cryptocurrency support. The device was measuring string length in characters (Unicode code points) instead of bytes. Because some characters use multiple bytes, a string could pass the old check yet be too long for the Stellar protocol, potentially causing malformed transaction data or unexpected device behavior when signing.

AI review queuedrefactor(core/rust): don't panic if Rust layout is unavailableby Roman Zeyde · 3c4c5ae1 · Jul 15, 2026 · 1 fileMessage 93 · StrongInformational 20Details
Commit message · Roman Zeyde

refactor(core/rust): don't panic if Rust layout is unavailable

Following https://github.com/trezor/trezor-firmware/pull/7282,
let's raise `RuntimeError` if the layout has been dropped too early
(instead of panicking).

[no changelog]

93/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
second-pass: broader security terminology
AI analysis · Informational 20/100

This commit changes how a hardware wallet's screen-layout code handles the case where a user-interface layout has been closed or dropped earlier than expected. Previously the code would panic (crash). Now it returns a controlled RuntimeError instead. It is a defensive hardening change, not a fix for an active exploit, and it follows an earlier related pull request.

AI review queuedrefactor(core/ethereum): rename and move keccak-related helper functionsby Roman Zeyde · dc2aadf6 · Jul 15, 2026 · 7 filesMessage 62 · AdequateInformational 15Details
Commit message · Roman Zeyde

refactor(core/ethereum): rename and move keccak-related helper functions

[no changelog]

62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This is a clean internal code cleanup in the Ethereum app of the Trezor firmware. It moves the Keccak hashing helper to a shared location and updates callers to use it. There is no user-facing behavior change and no security fix.

AI review queuedrefactor(core/ethereum): simplify `confirm_data_and_summary()`by Roman Zeyde · 814203e1 · Jul 14, 2026 · 2 filesMessage 77 · AdequateInformational 15Details
Commit message · Roman Zeyde

refactor(core/ethereum): simplify `confirm_data_and_summary()`

Note that `(confirm_data_chunk is None) == (confirm_summary is None)`.

[no changelog]

77/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This is a small internal code cleanup in Trezor's Ethereum transaction signing. It replaces two separate return values with a single tuple, because they are always either both present or both absent. There is no user-visible behavior change and no indication of a security fix.

AI review queuedtest(core): wait for `Cancel` response before sending `Ping`by Roman Zeyde · a6bffbca · Jul 14, 2026 · 1 fileMessage 100 · StrongInformational 15Details
Commit message · Roman Zeyde

test(core): wait for `Cancel` response before sending `Ping`

Otherwise, we may get stuck when using USB transport:
if the device is stuck sending, and not reading new messages from the
host, the first write may get stuck - and the test will deadlock.

[no changelog]

100/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Mentions testing or verification
Why it was queued
parser or protocol pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This is a test-only change to the Python Trezor client library. It fixes a potential deadlock in test synchronization code by waiting for a response to a Cancel message before sending a Ping message. There is no change to device firmware or any security-sensitive behavior, and no security vulnerability is present in the commit.

AI review queuedtests: replace repeated xfail/suppresion by decoratorsby M1nd3r · e91c588b · Jul 10, 2026 · 4 filesMessage 83 · StrongInformational 15Details
Commit message · M1nd3r

tests: replace repeated xfail/suppresion by decorators

- Replaced repeated "optiga xfail" in `evolu/test_sign_registration` by a decorator.
- Replaced repeated ephemeral key warning suppression in `thp/test-pairing` by marker alias.

[no changelog]

83/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit is a test-code cleanup only. It replaces repeated snippets in automated tests with reusable decorators and marker aliases. No firmware behavior, cryptography, or user-facing functionality is changed, so it has no security impact on Trezor devices.

AI review queuedtest(core): try to avoid old emulators' crashing during upgrade testsby Roman Zeyde · 468b7d75 · Jul 10, 2026 · 1 fileMessage 100 · StrongInformational 17Details
Commit message · Roman Zeyde

test(core): try to avoid old emulators' crashing during upgrade tests

Should help with https://github.com/trezor/trezor-firmware/issues/7052.

IIUC, #1725 was introduced to save memory, but it may crash the
emulator if debuglink and wirelink are used at the same time.

[no changelog]

100/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
second-pass: broader security terminology
AI analysis · Informational 17/100

This commit is a test-only workaround that adds a one-second sleep in an upgrade test script for older Trezor emulator versions. It avoids a known emulator crash during automated recovery tests when debug and wire communication are used simultaneously. It does not change the firmware itself or fix a security vulnerability in shipped devices.

AI review queuedchore(python): remove remaining TrezorClientDebugLink references [no changelog]by Arnold K · 64601614 · Jul 8, 2026 · 3 filesMessage 93 · StrongInformational 15Details
Commit message · Arnold K

chore(python): remove remaining TrezorClientDebugLink references [no changelog]

Fixes #6429.

- Remove stale docstring reference in debuglink.py
- Drop obsolete snippet scripts sign_tx.py and unify_test_files.py
- No changelog entry per trezor-firmware changelog guidelines

93/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit is a routine cleanup: it updates one comment in a debug helper file and deletes two old developer-only snippet scripts that referenced an outdated class name. There is no change to the firmware, wallet logic, cryptography, or any code that runs on user devices. It does not fix or introduce any security issue.

AI review queuedtest(core): don't fail codec_v1 `sync_responses()` on unexpected magicby Roman Zeyde · ddcea46b · Jul 7, 2026 · 2 filesMessage 99 · StrongInformational 18Details
Commit message · Roman Zeyde

test(core): don't fail codec_v1 `sync_responses()` on unexpected magic

Otherwise, pytest's session will be unnecessarily stopped.

Also, log the exception's traceback.

[no changelog]

99/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body✓ Explains rationale or failure mode✓ Mentions testing or verification
Why it was queued
parser or protocol pathsecond-pass: security-sensitive path
AI analysis · Informational 18/100

This is a small test-infrastructure change for the Trezor hardware wallet. It makes the test harness more tolerant of unexpected protocol responses and logs the full error trace instead of immediately stopping the entire pytest session. It does not change the device firmware or how real user transactions are validated; it only affects automated testing of the older protocol-v1 communication code.

AI review queuedchore(core): inline `SC_FUNC_APPROVE_REVOKE_AMOUNT` constant definitionby Roman Zeyde · fe564511 · Jul 7, 2026 · 2 filesMessage 62 · AdequateInformational 15Details
Commit message · Roman Zeyde

chore(core): inline `SC_FUNC_APPROVE_REVOKE_AMOUNT` constant definition

[no changelog]

62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit is a minor code cleanup: it replaces a named constant with the literal number 0 in one place and removes the constant definition. There is no functional change, no bug fix, and no security relevance visible in the diff.

AI review queuedchore(translations): sync Crowdin update translationsby Michal Kazda · 7aac81d8 · Jul 2, 2026 · 6 filesMessage 62 · AdequateInformational 15Details
Commit message · Michal Kazda

chore(translations): sync Crowdin update translations

[no changelog]

62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
signing or wallet pathtranslation-only discountsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit only updates translated text strings in the Trezor firmware. It changes wording in Czech, German, Spanish, French, and Portuguese translation files, plus the translation signature metadata. There are no code changes, no security fixes, and no behavior changes.

AI review queuedchore(translations): sync Crowdin fixing French failing testsby Michal Kazda · 1c84feca · Jul 2, 2026 · 3 filesMessage 72 · AdequateInformational 15Details
Commit message · Michal Kazda

chore(translations): sync Crowdin fixing French failing tests

[no changelog]

72/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
signing or wallet pathtranslation-only discountsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit updates translation files for Czech and French, plus the corresponding signed metadata. It changes wording on device screens (for example, how a 'hold to confirm' button is labeled and how a backup-fragment title is formatted) and refreshes the cryptographic fingerprint that protects those translations from tampering. There is no code change and no security vulnerability is present in the diff.

AI review queuedchore(translations): sync Crowdin fixing more French failing testsby Michal Kazda · 13b41359 · Jul 2, 2026 · 2 filesMessage 72 · AdequateInformational 15Details
Commit message · Michal Kazda

chore(translations): sync Crowdin fixing more French failing tests

[no changelog]

72/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
signing or wallet pathtranslation-only discountsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit updates French translation strings in the Trezor firmware and refreshes the corresponding translation signature metadata. The changes are purely cosmetic wording adjustments for on-screen text (for example, changing one French phrasing of a backup-recovery prompt to match another variant). There is no code behavior change, no cryptographic change, and no security fix.

AI review queuedchore(translations): sync Crowdin translationsby Thalarion · 700ef9ac · Jul 2, 2026 · 6 filesMessage 57 · ThinInformational 15Details
Commit message · Thalarion

chore(translations): sync Crowdin translations

[no changelog]

57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
signing or wallet pathtranslation-only discountsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit is a routine update of translated user-interface text for Trezor hardware wallets. It changes wording in Czech, German, Spanish, French, and Portuguese translation files, plus the translation signature metadata. There is no code change, no security fix, and no functional behavior change.

AI review queuedfeat(core): set tropic configurationby Martin Pastyřík · 4a93242c · Jul 2, 2026 · 28 filesMessage 80 · StrongLow 32Details
Commit message · Martin Pastyřík

feat(core): set tropic configuration

Set the configuration of Tropic to the value excpected by the firmware.

The current version of tropic configuration is stored in slot 6 of Tropic R memory data. During the setting process, slot 7 is temporarily used to store a backup of the configuration version.

Also refactor tropic configuration from prodtest into firmware and enable sensors setting in model_server.

[no changelog]

80/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Why it was queued
second-pass: unusually broad change
AI analysis · Low 32/100

This commit moves the configuration settings for the Tropic secure chip out of the production-test tool and into the main firmware. At boot, the device now checks whether the Tropic chip's configuration matches the version expected by the firmware, and can update or repair it if needed. It also adds a version number stored in a Tropic memory slot and uses a backup slot during updates. The change is a feature/refactoring patch; there is no direct evidence in the commit that it fixes a known security vulnerability, but misconfiguration of a security chip is a security-sensitive operation.

AI review queuedfeat(core): sign rotation index into Evolu sign registrationby Martin Pastyřík · 4db3a69d · Jul 1, 2026 · 8 filesMessage 77 · AdequateInformational 24Details
Commit message · Martin Pastyřík

feat(core): sign rotation index into Evolu sign registration

This enables the Quota Manager to distinguish the indices and store the current index.

[no changelog]

77/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 24/100

This commit updates the Trezor firmware's Evolu (delegated identity) registration signing feature so that the device now includes a 'rotation index' in the signed registration request. The rotation index tells the Quota Manager which version of the device's delegated identity key was used. The signature format was also bumped from V1 to V2 by adding the rotation index into the signed data. This is a feature enhancement, not a fix for an obvious security vulnerability, but it touches cryptographic signing and identity-key rotation, which are security-sensitive areas.

AI review queuedfix(core/caesar): allocate test-related formats on-demandby Roman Zeyde · 80bc85df · Jul 1, 2026 · 2 filesMessage 72 · AdequateInformational 17Details
Commit message · Roman Zeyde

fix(core/caesar): allocate test-related formats on-demand

[no changelog]

72/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 17/100

This change moves some internal test-only Ethereum transaction display definitions from being permanently added to a global list to being generated on demand only when the device is running in debug/test mode. It is a memory-footprint and code-hygiene cleanup, not a fix for an exploitable security bug. There is no indication it addresses a vulnerability.