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 37 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.

Security candidaterefactor(core/rtl): add rust bindings for ts_tby Martin Milata · b72e8540 · Sep 30, 2026 · 14 filesMessage 57 · ThinInformational 17Details
Commit message · Martin Milata

refactor(core/rtl): add rust bindings for ts_t

[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
boot or update path
AI analysis · Informational 17/100

This commit is a code cleanup that adds Rust-language bindings for an existing internal error/status type used inside the Trezor firmware. It does not change how user funds or secrets are handled. The main observable effect is that Rust code can now check and report low-level device errors more cleanly, and one screen callback now handles errors more carefully instead of crashing. There is no direct security fix here, but it improves future error-handling hygiene.

AI review queuedfeat(ethereum): Unknown vaults fetch relevant token defintion from hostby PrisionMike · a130a694 · Sep 30, 2026 · 4 filesMessage 62 · AdequateLow 36Details
Commit message · PrisionMike

feat(ethereum): Unknown vaults fetch relevant token defintion from host

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 36/100

This commit changes how Trezor handles Ethereum 'vault' transactions (like deposits and withdrawals from yield-bearing token vaults). Previously, the device only supported a fixed list of known vaults and rejected or blindly signed unknown ones. Now, for unknown vaults, it asks the connected computer (host) for token and display definitions so it can show clearer signing information. The change also removes a hard safety check that rejected transactions where the receiver or owner did not match the signer for known vaults, and instead lets the UI display the receiver/owner explicitly. This is a feature addition, but it introduces new trust in host-provided data and relaxes a previously strict safety rule.

Security candidaterefactor(core): add Rust bindings for noise_xxpsk3by Martin Milata · e99982b2 · Sep 30, 2026 · 8 filesMessage 62 · AdequateInformational 11Details
Commit message · Martin Milata

refactor(core): add Rust bindings for noise_xxpsk3

[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
cryptography-sensitive pathboot or update path
AI analysis · Informational 11/100

This commit adds Rust programming-language wrappers around an existing C library for a secure communication protocol called Noise XXpsk3. It does not change the underlying cryptographic logic or fix any bug; it is a code organization (refactoring) change that lets other parts of the Trezor firmware call the Noise XXpsk3 routines from Rust. There is no direct security problem visible in the change itself.

AI review queuedchore(translations): sync Crowdin translation fixesby Michal Kazda · 9c4fed59 · Sep 30, 2026 · 4 filesMessage 62 · AdequateInformational 15Details
Commit message · Michal Kazda

chore(translations): sync Crowdin translation fixes
[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 German, French, and Portuguese, plus the translation signature metadata. There are no code or security changes.

AI review queuedfix(ethereum): Remove hardcoded names for registry known addressesby PrisionMike · 5f1c1003 · Sep 30, 2026 · 4 filesMessage 62 · AdequateInformational 24Details
Commit message · PrisionMike

fix(ethereum): Remove hardcoded names for registry known addresses

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

This commit removes a long list of hardcoded friendly names (like 'Lido', 'Morpho', 'WalletConnect') that Trezor devices previously showed when signing Ethereum transactions to certain smart contracts. After the change, only a few built-in names remain (mainly 'WETH' and a test address), and most contracts will be shown to the user as raw addresses instead of recognizable labels. The change is framed as a cleanup to rely on an external registry rather than hardcoded names. It is not a direct security fix for a vulnerability, but it reduces the risk that a wrong or misleading hardcoded label could trick a user into trusting a malicious contract.

Security candidatefix(core/delizia): passphrase prompt marqueeby obrusvit · 72b73928 · Sep 30, 2026 · 2 filesMessage 57 · ThinInformational 15Details
Commit message · obrusvit

fix(core/delizia): passphrase prompt marquee

[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
access controlauthentication path
AI analysis · Informational 15/100

This commit is a user-interface polish fix for the Trezor hardware wallet's passphrase entry screen. It replaces a static text label with a scrolling 'marquee' so that longer prompts fit on the small device screen. There is no security-relevant change here.

Security candidatefeat(clear_signing,test): added script to update the latest definitions from prodby PrisionMike · fab3bea4 · Sep 30, 2026 · 3 filesMessage 72 · AdequateInformational 15Details
Commit message · PrisionMike

feat(clear_signing,test): added script to update the latest definitions from prod

[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 boundary
AI analysis · Informational 15/100

This commit adds two helper scripts for Trezor's internal testing workflow. They download or convert signed Ethereum/Solana definition files and verify their digital signatures before converting them into JSON test fixtures. There is no change to the firmware that runs on customer devices, no change to how signatures are verified in production code, and no disclosed security issue.

Security candidatetest(clear_signing): use jsons for testing external defintionsby PrisionMike · 7bd70549 · Sep 30, 2026 · 3 filesMessage 72 · AdequateInformational 15Details
Commit message · PrisionMike

test(clear_signing): use jsons for testing external defintions

- Updated readme
[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 boundarysigning or wallet path
AI analysis · Informational 15/100

This commit only changes test code. It switches the way Trezor's automated tests store and load Ethereum 'clear signing' definitions from pre-generated binary files to plain JSON files that are converted and signed on the fly during tests. There is no change to the actual firmware or wallet behavior, and no security fix or vulnerability is present.

AI review queuedchore(tests,definitions): switch from .dat to .jsonby PrisionMike · 85e91e74 · Sep 30, 2026 · 160 filesMessage 87 · StrongInformational 15Details
Commit message · PrisionMike

chore(tests,definitions): switch from .dat to .json

- Used a simple script to convert the .dat to .json
- Maxed out timestamp.
- version 2 only.
[no changelog]

87/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body✓ Mentions testing or verification
Why it was queued
second-pass: unusually broad change
AI analysis · Informational 15/100

This commit is a routine maintenance change in the Trezor firmware repository. It converts Ethereum test fixture files from a binary .dat format to a human-readable .json format. The actual content of the definitions (token names, contract addresses, display formats) appears unchanged; only the file format is switched. There is no indication this fixes or introduces a security vulnerability.

Security candidatetest(clear_signing): move .dat files to json fixtures directoryby PrisionMike · a81c9975 · Sep 30, 2026 · 81 filesMessage 87 · StrongInformational 15Details
Commit message · PrisionMike

test(clear_signing): move .dat files to json fixtures directory

We'll have them converted into jsons in a subsequent commit.
[no changelog]

87/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body✓ Mentions testing or verification
Why it was queued
signing boundary
AI analysis · Informational 15/100

This commit only moves existing test data files (.dat files used for Ethereum clear-signing tests) from one directory to another inside the test fixtures area. No code, firmware logic, or user-facing behavior was changed. It is purely a housekeeping/test reorganization change.

AI review queuedchore(translations): sync Crowdin translationsby Thalarion · f312dca2 · Sep 29, 2026 · 7 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 synchronization of translated user-interface text strings from the Crowdin translation platform. It only changes wording, grammar, capitalization, and missing translations in JSON files for several languages. There is no code change, no change to security logic, and no indication of a security fix or vulnerability.

Security candidatetest(clear_signing): add binaries for external device testby PrisionMike · 7867262d · Sep 29, 2026 · 4 filesMessage 72 · AdequateInformational 15Details
Commit message · PrisionMike

test(clear_signing): add binaries for external device test
[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 boundary
AI analysis · Informational 15/100

This commit only adds test data files for Ethereum clear-signing tests. It includes a token definition for DAI on Ethereum mainnet and a fake network/token definition for chain ID 223, plus updates to UI test fixtures. There is no change to production firmware code, no security fix, and no vulnerability.

Security candidatefeat(core/bolt): allow back in multishare setupby obrusvit · 42d13264 · Sep 29, 2026 · 10 filesMessage 80 · StrongInformational 15Details
Commit message · obrusvit

feat(core/bolt): allow back in multishare setup

- checklist has an up arrow on the left when going back is possible
- number prompt has a menu button in the header ("More info" handled
in Python) and an up-arrow back button instead of the info icon

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
boot or update path
AI analysis · Informational 15/100

This commit is a user-interface feature change for Trezor hardware wallets. It adds an on-screen 'back' arrow during multi-share backup setup so users can return to a previous step, and moves the 'More info' help into a menu button. There is no indication of a security bug or vulnerability fix in the code or commit message.

Security candidatefix(ethereum): reword contract address label.by PrisionMike · 7ed8ff9b · Sep 29, 2026 · 15 filesMessage 72 · AdequateInformational 15Details
Commit message · PrisionMike

fix(ethereum): reword contract address label.

We don't need to call it Provider. It's not stardard lingo. Interaction contract is a much better word.
[no changelog]

72/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body
Why it was queued
cryptography-sensitive path
AI analysis · Informational 15/100

This commit only rewords user-facing labels in the Trezor Ethereum user interface. It replaces the term 'Provider contract address' with 'Contract address' and removes the separate 'Interaction contract' label, using one consistent label across all device layouts and translations. There is no code behavior change, no cryptographic change, and no security fix.

Security candidatefeat(core/caesar): allow back in multishare setupby obrusvit · ce193b55 · Sep 29, 2026 · 8 filesMessage 80 · StrongInformational 18Details
Commit message · obrusvit

feat(core/caesar): allow back in multishare setup

- checklist has an up arrow instead of the cancel button, emitting BACK
- number carousel has a BACK item as the leftmost choice

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
cryptography-sensitive pathboot or update path
AI analysis · Informational 18/100

This commit adds a 'go back' navigation feature to the backup setup screens on Trezor's older 'Caesar' device layout. It lets users step backward through the multi-share backup checklist and number-selection carousels, matching behavior already available on newer layouts. There is no indication this fixes a security vulnerability; it is a user-experience improvement.

Security candidatefeat(clear_signing): show chain name or number in all flowsby PrisionMike · 7c586094 · Sep 29, 2026 · 6 filesMessage 62 · AdequateInformational 15Details
Commit message · PrisionMike

feat(clear_signing): show chain name or number in all flows

[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 boundarycryptography-sensitive pathsigning or wallet path
AI analysis · Informational 15/100

This commit is a user-interface improvement for Trezor hardware wallets when approving Ethereum transactions. It makes sure the wallet always shows which blockchain network (for example Ethereum mainnet, Polygon, or an unknown chain ID) is being used during 'clear signing' flows. There is no security vulnerability here; it is a defensive feature that helps users avoid mistakes.

AI review queuedfix(translations): Shorten provider contract address for french stringby PrisionMike · 7c4107bc · Sep 28, 2026 · 2 filesMessage 77 · AdequateInformational 15Details
Commit message · PrisionMike

fix(translations): Shorten provider contract address for french string

- Recommended dropping `Provider`altogether.

[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 simply shortens a French translation string on Trezor hardware wallets. The phrase 'Provider contract address' is changed to just 'Contract address' in French, and the translation signature file is updated accordingly. There is no security issue here.

Security candidatefeat(core/delizia): allow back in multishare setupby obrusvit · 3193cf5b · Sep 28, 2026 · 4 filesMessage 77 · AdequateInformational 19Details
Commit message · obrusvit

feat(core/delizia): allow back in multishare setup

- swipe down on the checklist and number prompt screens goes back
- new "Go back" item in the number prompt menu

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
boot or update path
AI analysis · Informational 19/100

This commit adds a "go back" option during the multi-share backup setup on Trezor's Delizia user interface. It lets users return to a previous step if they made a mistake while choosing the number of shares or thresholds. There is no indication this fixes a security vulnerability; it is a usability improvement.

Security candidatefeat(core): allow back in multishare setupby obrusvit · 486cd24a · Sep 28, 2026 · 16 filesMessage 72 · AdequateInformational 19Details
Commit message · obrusvit

feat(core): allow back in multishare setup

- implements the state machine in python files
- implements the UI for Eckahrt

72/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body
Why it was queued
cryptography-sensitive pathboot or update path
AI analysis · Informational 19/100

This commit changes the on-device backup setup flow for newer Trezor devices so users can go back and revise choices such as the number of shares or the threshold. It is a user-experience improvement, not a security fix. The code removes the ability to cancel out of certain setup screens and instead adds a back button. There is no indication in the commit that this addresses a security vulnerability.

Security candidatetest(clear_signing): add device tests for more registry providersby PrisionMike · b7cf4f92 · Sep 27, 2026 · 56 filesMessage 95 · StrongInformational 15Details
Commit message · PrisionMike

test(clear_signing): add device tests for more registry providers

36 sign-tx cases built from real on-chain transactions, each with its
dev-signed display-format definition.

[no changelog]

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

95/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
signing boundarysigning or wallet path
AI analysis · Informational 15/100

This commit only adds new test cases and test data files for Trezor's Ethereum 'clear signing' feature. It does not change any firmware, wallet, or production code. There is no security vulnerability here.

Security candidatefeat(ethereum): add receiver and owner addressby PrisionMike · e65b9f51 · Sep 25, 2026 · 5 filesMessage 57 · ThinInformational 19Details
Commit message · PrisionMike

feat(ethereum): add receiver and owner address

[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
cryptography-sensitive path
AI analysis · Informational 19/100

This commit changes how Trezor hardware wallets display Ethereum vault transactions. It adds extra on-screen confirmation steps showing the 'receiver' and 'owner' addresses for certain vault operations, and it makes address values easier to read by chunking them. The change appears to be a user-interface improvement that increases transparency rather than a security fix. There is no evidence in the commit of a vulnerability or exploit.

AI review queuedchore(ethereum): add owner address string for vault transactionsby PrisionMike · 22331960 · Sep 25, 2026 · 7 filesMessage 62 · AdequateLow 26Details
Commit message · PrisionMike

chore(ethereum): add owner address string for vault transactions

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

This commit adds a new on-screen label, 'Owner address,' for Ethereum vault transactions on Trezor hardware wallets. It also updates test comments and adds new test cases for situations where the vault transaction's owner or receiver differs from the wallet's own address. The change appears to be a user-interface improvement that makes previously hidden address details visible during transaction confirmation, rather than falling back to 'blind signing.' It is not obviously a security fix, but it improves transparency and may reduce the risk of users approving misleading transactions.

Security candidatefix(solana): never hide account self-assignmentby Jakub Janků · 9922785e · Sep 25, 2026 · 4 filesMessage 100 · StrongHigh 75Details
Commit message · Jakub Janků

fix(solana): never hide account self-assignment

- Assign hid both the assigned account and the new owner when they
equal the signer, so a self-assignment showed no instruction screen
at all and could be appended to an otherwise visible transfer.

- The owner is a program ID, not an authority. Assigning a wallet to
its own non-executable address permanently locks its lamports: only
the current owner program can debit lamports or change the owner.
- https://solana.com/docs/core/accounts#key-facts
- https://github.com/anza-xyz/agave/blob/8acf2b352b9768b2b96f283400d8b9393c6c6e40/transaction-context/src/instruction_accounts.rs#L91-L103

- Always show both fields for consistency with "Assign With Seed".

(cherry picked from commit 2894b1ec7a20e51614eaa79881a39f37a0b33c75)

100/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Links an issue, advisory, or supporting reference
Why it was queued
signing boundarysigning or wallet path
AI analysis · High 75/100

This fix prevents a Trezor hardware wallet from silently approving a specific Solana 'Assign' instruction. Previously, when a user assigned their own account as the new owner program, both key details were hidden from the device screen, so the instruction produced no visible prompt at all. An attacker could tack this silent self-assignment onto an otherwise normal-looking transfer, tricking the user into signing a transaction that permanently locks their Solana account's funds. The patch now always displays both the account being assigned and the new owner program.

Security candidaterefactor(clear_signing): renamed variables for code comprehensionby PrisionMike · 8201638c · Sep 25, 2026 · 1 fileMessage 62 · AdequateInformational 15Details
Commit message · PrisionMike

refactor(clear_signing): renamed variables for code comprehension

[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 boundarysigning or wallet path
AI analysis · Informational 15/100

This commit is a simple code cleanup: it renames the variable `address_bytes` to `contract_address` and `f` to `display_format` in one Ethereum clear-signing file to make the code easier to read. No behavior changes, no security fixes, and no bug fixes are visible in the diff.

Security candidatefix(core): add new line on Eckhart address mismatch screenby Michal Kazda · 99cb0ffd · Sep 25, 2026 · 1 fileMessage 77 · AdequateInformational 15Details
Commit message · Michal Kazda

fix(core): add new line on Eckhart address mismatch screen
- ensures addr_mismatch__support_url starts on a new line
[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
boot or update path
AI analysis · Informational 15/100

This commit is a cosmetic UI fix for the Trezor hardware wallet's Eckhart layout. It adds a line break so that a support URL appears on its own line when the device shows an address mismatch warning. There is no security-relevant change to how addresses are validated, compared, or displayed to the user.