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
1754commits · 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 30 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 queuedfix: styleby M1nd3r · 0d8332e7 · Mar 31, 2026 · 1 fileMessage 2 · OpaqueInformational 15Details
Commit message · M1nd3r

fix: style

[no changelog]

2/100 · OpaqueMessage clarity
✓ Uses a recognizable type or scope! Very short subject! Too few words to establish purpose! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: opaque commit messagesecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit is a pure code-style cleanup in the Ethereum 'clear signing' module. It removes unnecessary extra parentheses around tuple unpacking assignments. There is no functional change, no security fix, and no behavior change to the hardware wallet's transaction handling.

AI review queuedfeat(ethereum): add erc-4626 vault flow strings [no changelog]by PrisionMike · aa2b95fe · Mar 30, 2026 · 12 filesMessage 77 · AdequateInformational 15Details
Commit message · PrisionMike

feat(ethereum): add erc-4626 vault flow strings
[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 commit only adds new user-facing text strings (labels like 'Deposit amount', 'Withdraw', 'Your address') for an upcoming Ethereum ERC-4626 vault feature. It also moves one existing word ('Deposit') from a Cardano-only string to a shared word list. There are no code logic changes, no security fixes, and no behavior changes in how the device handles transactions or private keys.

AI review queuedchore(deps): bump cbor2 from 5.8.0 to 5.9.0by dependabot[bot] · 4cde1547 · Mar 30, 2026 · 1 fileMessage 88 · StrongInformational 14Details
Commit message · dependabot[bot]

chore(deps): bump cbor2 from 5.8.0 to 5.9.0

Bumps [cbor2](https://github.com/agronholm/cbor2) from 5.8.0 to 5.9.0.
- [Release notes](https://github.com/agronholm/cbor2/releases)
- [Commits](https://github.com/agronholm/cbor2/compare/5.8.0...5.9.0)

---
updated-dependencies:
- dependency-name: cbor2
dependency-version: 5.9.0
dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>

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
automated dependency-update discountsecond-pass: broader security terminology
AI analysis · Informational 14/100

This is a routine automated update by Dependabot that bumps the Python library cbor2 from version 5.8.0 to 5.9.0 in the project's lock file (uv.lock). Only hashes and download URLs for the package changed. There is no indication in the commit itself that this fixes or introduces a security problem. Without checking the upstream cbor2 release notes, we cannot say whether the new version addresses any vulnerabilities.

AI review queuedchore(deps): bump requests from 2.32.5 to 2.33.0by dependabot[bot] · 8f41003e · Mar 30, 2026 · 1 fileMessage 88 · StrongInformational 15Details
Commit message · dependabot[bot]

chore(deps): bump requests from 2.32.5 to 2.33.0

Bumps [requests](https://github.com/psf/requests) from 2.32.5 to 2.33.0.
- [Release notes](https://github.com/psf/requests/releases)
- [Changelog](https://github.com/psf/requests/blob/main/HISTORY.md)
- [Commits](https://github.com/psf/requests/compare/v2.32.5...v2.33.0)

---
updated-dependencies:
- dependency-name: requests
dependency-version: 2.33.0
dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>

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
automated dependency-update discountsecond-pass: broader security terminology
AI analysis · Informational 15/100

This is a routine automated dependency update by Dependabot. It changes the pinned version of the Python 'requests' library from 2.32.5 to 2.33.0 in the project's lock file only. There is no indication in the commit that this fixes a security issue, and the change itself is just a version/hash update with no code modifications.

AI review queuedfix(python): skip unrelated responses when probing transportby Roman Zeyde · d7539ca0 · Mar 28, 2026 · 2 filesMessage 85 · StrongLow 38Details
Commit message · Roman Zeyde

fix(python): skip unrelated responses when probing transport

Also, simplify a bit protocol v1 magic handling flow.

Fixes https://github.com/trezor/trezor-firmware/issues/6588.

85/100 · StrongMessage clarity
✓ Specific, 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
parser or protocol pathsecond-pass: security-sensitive path
AI analysis · Low 38/100

This commit fixes a bug in the Python Trezor client library that could cause it to crash or fail to connect when probing a Trezor device. The problem happened when leftover or unrelated data packets were still sitting in the communication channel. Previously, the library would see an unexpected packet, treat it as a protocol error, and give up. Now it skips those unrelated packets and waits for the real response. This is a reliability and minor security improvement for the host-side software, not the hardware wallet firmware itself.

AI review queuedchore(core): add N4W1 backup-related translationsby Roman Zeyde · c318d637 · Mar 26, 2026 · 6 filesMessage 57 · ThinInformational 15Details
Commit message · Roman Zeyde

chore(core): add N4W1 backup-related 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 pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit only adds new on-screen text strings for a future backup feature called N4W1. It does not change any security logic, cryptographic code, or user-accessible behavior. There is no indication of a vulnerability or security fix.

AI review queuedfeat(core): Update RFAL library to version 4.0.2by kopecdav · 151ff869 · Mar 25, 2026 · 55 filesMessage 57 · ThinModerate 59Details
Commit message · kopecdav

feat(core): Update RFAL library to version 4.0.2

[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
second-pass: unusually broad change
AI analysis · Moderate 59/100

This commit updates the third-party STMicroelectronics RFAL NFC library inside Trezor firmware from version 3.0.1 to 4.0.2. The vendor's release notes for version 4.0.2 explicitly mention fixing a 'vulnerability during EMD handling on fast systems' that was introduced in version 4.0.0. EMD (Electro-Magnetic Disturbance) handling is part of the NFC radio stack, so the flaw is likely a low-level radio/communication issue rather than something that directly exposes cryptocurrency private keys. Because the commit is a large library drop (almost 8,000 lines changed across 55 files) and the actual code diff is not shown, we cannot independently verify the exact nature or severity of the vulnerability from this commit alone.

AI review queuedchore: enable SLIP-24 for ERC-20 `transfer`by Ioan Bizău · 795d5d6d · Mar 24, 2026 · 2 filesMessage 57 · ThinLow 30Details
Commit message · Ioan Bizău

chore: enable SLIP-24 for ERC-20 `transfer`

[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 pathsecond-pass: security-sensitive path
AI analysis · Low 30/100

This commit enables Trezor hardware wallets to use SLIP-24 payment requests when signing ERC-20 token transfers. Previously, payment requests were rejected for any contract interaction, including ERC-20 transfers. The change adds a new code path that verifies the token transfer amount and recipient against a signed payment request before showing the confirmation screen. It is a feature-enablement change rather than a fix for an active vulnerability, but it touches security-critical signing flow code.

AI review queuedfeat(ethereum): parsing dynamic values in calldataby Ioan Bizău · e666d62b · Mar 24, 2026 · 9 filesMessage 77 · AdequateLow 38Details
Commit message · Ioan Bizău

feat(ethereum): parsing dynamic values in calldata

* extend calldata parsing to support strings, structs, arrays and more

[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 38/100

This commit is a feature expansion for Trezor's Ethereum 'clear signing' system, which decodes smart-contract call data so users see human-readable details instead of raw hex. It adds support for dynamic Solidity types such as strings, byte arrays, structs, and arrays. The change is large and refactors how transaction data is parsed and presented. It does not appear to be a disclosed security fix, but because it handles untrusted transaction data, any parsing bugs could in principle let a malformed transaction bypass warnings or crash the device. The diff itself shows explicit bounds checks and validation, which is a positive sign, but the new code paths are complex and have not been externally audited in the provided materials.

AI review queuedfeat(ethereum): token amount native currencyby Ioan Bizău · d1760fc8 · Mar 24, 2026 · 1 fileMessage 57 · ThinInformational 16Details
Commit message · Ioan Bizău

feat(ethereum): token amount native currency

[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 pathsecond-pass: security-sensitive path
AI analysis · Informational 16/100

This commit changes how the Trezor hardware wallet formats token amounts shown on screen during Ethereum transactions. It adds support for treating certain addresses as the network's native currency (like ETH on Ethereum mainnet) rather than as ERC-20 tokens when displaying amounts. There is no indication in the commit that this fixes a security vulnerability; it appears to be a user-interface correctness feature.

AI review queuedchore: process up to 4kb of calldataby Ioan Bizău · d4609489 · Mar 24, 2026 · 1 fileMessage 57 · ThinLow 35Details
Commit message · Ioan Bizău

chore: process up to 4kb of calldata

[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 pathsecond-pass: security-sensitive path
AI analysis · Low 35/100

This commit changes how Trezor firmware handles Ethereum transaction data (calldata). Previously, the code only tried to 'clear sign' transactions where the entire calldata fit in the first chunk. Now it stores and processes up to 4 KB of calldata across multiple chunks, and gives up gracefully if the data is too large. The change appears to be a hardening/capacity improvement rather than a fix for an active exploit, but it removes a risky assumption that all data is present in the initial chunk.

AI review queuedrefactor(ethereum): multiple tokens can be unknownby Ioan Bizău · 7e66cf2b · Mar 24, 2026 · 1 fileMessage 62 · AdequateLow 27Details
Commit message · Ioan Bizău

refactor(ethereum): multiple tokens can be unknown

[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 · Low 27/100

This commit refactors how Trezor firmware handles unknown Ethereum tokens when showing transaction details on screen. Previously, if a transaction involved an unknown token, the device showed one generic warning. After this change, the code can detect and warn about multiple unknown tokens within a single transaction's data. It is a defensive code improvement rather than a fix for a known exploit.

AI review queuedfeat(ethereum): slicing inside iterable parametersby Ioan Bizău · 2c5d8b09 · Mar 24, 2026 · 1 fileMessage 62 · AdequateLow 28Details
Commit message · Ioan Bizău

feat(ethereum): slicing inside iterable parameters

[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 · Low 28/100

This commit updates the Trezor Ethereum app's 'clear signing' feature so it can handle data formats that slice inside arrays or structs (for example, taking only a portion of a list). It is a small feature addition, not a fix for a known security bug. There is no evidence in the commit or supplied references that this resolves an active vulnerability.

AI review queuedchore(tests): test ETH calldata parsingby Ioan Bizău · e3253010 · Mar 24, 2026 · 1 fileMessage 67 · AdequateInformational 12Details
Commit message · Ioan Bizău

chore(tests): test ETH calldata parsing

[no changelog]

67/100 · AdequateMessage clarity
✓ 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 12/100

This commit only adds new automated tests for Ethereum transaction data parsing. It does not change any production code, so it cannot introduce a security vulnerability by itself. The tests verify that the device correctly rejects malformed Ethereum addresses and oversized numeric values.

AI review queuedchore: drop 1inch definitions for nowby Ioan Bizău · dc1f3a1b · Mar 24, 2026 · 3 filesMessage 57 · ThinInformational 17Details
Commit message · Ioan Bizău

chore: drop 1inch definitions for now

[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 pathsecond-pass: security-sensitive path
AI analysis · Informational 17/100

This commit removes built-in 'clear signing' support for the 1inch decentralized exchange from Trezor Ethereum firmware. Clear signing makes complex crypto transactions easier to read and verify on the device screen. Removing it does not create a new security hole, but users interacting with 1inch will now see less human-readable transaction details, which can make it harder to spot malicious or mistaken transactions. It is a feature rollback, not a vulnerability fix.

AI review queuedchore(ethereum): clear sign only first data chunkby Ioan Bizău · 73eaef8c · Mar 24, 2026 · 3 filesMessage 57 · ThinLow 40Details
Commit message · Ioan Bizău

chore(ethereum): clear sign only first data chunk

[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 pathsecond-pass: security-sensitive path
AI analysis · Low 40/100

This commit changes how Trezor hardware wallets display and confirm Ethereum transactions that use 'clear signing' (human-readable descriptions of smart-contract calls). Previously, clear signing could be attempted for transactions whose data is split across multiple chunks. Now, clear signing is used only when the entire transaction data fits in the first chunk. If the clear-signing parser fails on that first chunk, the device falls back to the standard raw-data confirmation. The change is described as a feature limitation, not a security fix, but it removes a code path where multi-chunk data might be parsed before all chunks are available or confirmed.

AI review queuedchore(translations): updated fixtures [no changelog]by Michal Kazda · 800147fb · Mar 24, 2026 · 3 filesMessage 77 · AdequateInformational 15Details
Commit message · Michal Kazda

chore(translations): updated fixtures
[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 commit only updates German translation text and the corresponding test snapshots (expected screen hashes). It removes a few old variant translations for the term 'hidden wallet' and standardizes it to 'Passphrase-Wallet'. There is no code change and no security relevance.

AI review queuedchore(translations): updated fixtures [no changelog]by Michal Kazda · 32ff27b3 · Mar 24, 2026 · 3 filesMessage 77 · AdequateInformational 15Details
Commit message · Michal Kazda

chore(translations): updated fixtures
[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 commit is a routine maintenance update for translation files and test snapshots. It changes one French translation string, updates a cryptographic signature record for the translation set, and refreshes many expected visual test hashes. There is no code change that affects security functionality, and nothing in the commit suggests it fixes or introduces a vulnerability.

AI review queuedchore(translations): sync Crowdin translations [no changelog]by Michal Kazda · 0065caa1 · Mar 24, 2026 · 6 filesMessage 77 · AdequateInformational 15Details
Commit message · Michal Kazda

chore(translations): sync Crowdin translations
[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 pathtranslation-only discountsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit only updates translated text strings in the Trezor firmware. It adds new translations (for example, phrases like 'Confirm contract' and 'Intent' in several languages), fixes existing wording, and refreshes the translation signature file. There are no code changes that affect security, cryptography, or device behavior.

AI review queuedfeat(solana): SLIP-24 for native SOLby Ioan Bizău · e5af2a91 · Mar 23, 2026 · 6 filesMessage 57 · ThinLow 30Details
Commit message · Ioan Bizău

feat(solana): SLIP-24 for native SOL

[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 pathsecond-pass: security-sensitive path
AI analysis · Low 30/100

This commit adds support for native Solana (SOL) payment requests using the SLIP-24 standard on Trezor hardware wallets. It extends existing token payment-request logic to also cover plain SOL transfers, and updates tests and UI fixtures accordingly. There is no direct evidence in the commit of a security vulnerability, but any change to payment verification and confirmation flows carries a low level of implementation risk.

AI review queuedfeat(core): introduce explicit manufacturing mode exitby tychovrahe · 29431ce7 · Mar 20, 2026 · 40 filesMessage 62 · AdequateLow 30Details
Commit message · tychovrahe

feat(core): introduce explicit manufacturing mode exit

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
second-pass: unusually broad change
AI analysis · Low 30/100

This commit adds a new factory/production tool command that permanently exits 'manufacturing mode' by writing and locking a special one-time-programmable memory block. It also reorganizes how each Trezor model defines its OTP memory layout and unit properties. The change is a feature addition for the production-test firmware, not a fix for a known exploitable bug in user-facing firmware. It does not appear to introduce an obvious vulnerability, but it changes security-relevant manufacturing state logic.

AI review queuedchore(deps): bump pyasn1 from 0.6.2 to 0.6.3by dependabot[bot] · 127a5ab8 · Mar 19, 2026 · 1 fileMessage 88 · StrongInformational 15Details
Commit message · dependabot[bot]

chore(deps): bump pyasn1 from 0.6.2 to 0.6.3

Bumps [pyasn1](https://github.com/pyasn1/pyasn1) from 0.6.2 to 0.6.3.
- [Release notes](https://github.com/pyasn1/pyasn1/releases)
- [Changelog](https://github.com/pyasn1/pyasn1/blob/main/CHANGES.rst)
- [Commits](https://github.com/pyasn1/pyasn1/compare/v0.6.2...v0.6.3)

---
updated-dependencies:
- dependency-name: pyasn1
dependency-version: 0.6.3
dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>

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
automated dependency-update discountsecond-pass: broader security terminology
AI analysis · Informational 15/100

This is a routine automated dependency update by Dependabot that bumps the Python library pyasn1 from version 0.6.2 to 0.6.3 in the project's lock file. The commit itself only changes package metadata (download URLs and cryptographic hashes) and contains no code changes, bug fixes, or security claims. There is no evidence in the commit or supplied references that this update addresses a security issue.

AI review queuedrefactor: stellar confirmationsby Ioan Bizău · 663569c4 · Mar 19, 2026 · 4 filesMessage 62 · AdequateLow 32Details
Commit message · Ioan Bizău

refactor: stellar confirmations

[no changelog]

(cherry picked from commit a7f5e7200f49b390c65940638900f071258207b4)

62/100 · AdequateMessage clarity
✓ Descriptive subject✓ 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 32/100

This commit refactors how Trezor handles Stellar cryptocurrency transaction confirmations when a 'payment request' is used. Previously, the device might skip confirming individual operations during payment requests. The change ensures that only simple payment operations are allowed in payment requests, rejects invalid operation types, and still requires user confirmation. It also adds a test case for an invalid operation in a payment request. The commit appears to be a defensive hardening change rather than a fix for an active exploit.

AI review queuedchore(core): sign translationsby Roman Zeyde · e64457a0 · Mar 19, 2026 · 1 fileMessage 62 · AdequateInformational 15Details
Commit message · Roman Zeyde

chore(core): sign translations

[no changelog]

(cherry picked from commit 3d00dda8027a945857f1c3869601c035e96deaee)

62/100 · AdequateMessage clarity
✓ Descriptive subject✓ Uses a recognizable type or scope✓ Provides an explanatory body
Why it was queued
signing or wallet pathtranslation-only discountsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit simply adds a new cryptographic signature entry to a JSON file that records approved translation bundles for the Trezor hardware wallet. There is no code change, no bug fix, and no visible security issue in the diff itself.

AI review queuedfix(core): confirm Ethereum data during its hashingby Roman Zeyde · 70c9b0c0 · Mar 19, 2026 · 7 filesMessage 77 · AdequateHigh 72Details
Commit message · Roman Zeyde

fix(core): confirm Ethereum data during its hashing

(cherry picked from commit 09ab831c4eaced4e1702dd74cc6713e0b0f5975d)

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 · High 72/100

This update changes how Trezor hardware wallets confirm Ethereum transaction data. Previously, the device asked the user to approve the entire data payload before it began hashing the transaction. Now, it confirms data piece by piece while the transaction is being hashed, and only shows the final transaction summary right before signing. The change is marked as a security fix in the project's changelog, suggesting the old behavior could let a user approve data that does not match what is actually signed.