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
1758commits · 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 2 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 candidatechore: bump versionsby Roman Zeyde · 18da22f8 · Sep 15, 2026 · 12 filesMessage 63 · AdequateInformational 15Details
Commit message · Roman Zeyde

chore: bump versions

$ tools/bump-version.py core 2.12.6
$ tools/bump-version.py core/embed/projects/secmon 1.0.15
$ tools/bump-version.py core/embed/projects/prodtest 0.3.10
wrote 357 error codes across 25 modules to /home/rzeyde/src/trezor-firmware/core/embed/projects/prodtest/error_codes.json

[no changelog]

63/100 · AdequateMessage clarity
✓ Subject identifies a change✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Why it was queued
signing or wallet pathboot or update path
AI analysis · Informational 15/100

This commit only updates version numbers and translation metadata. It changes no actual code, logic, or security behavior. There is no security issue here.

Security candidatetest(clear_signing): registry examples for unit tests.by PrisionMike · a4807724 · Sep 15, 2026 · 3 filesMessage 72 · AdequateInformational 15Details
Commit message · PrisionMike

test(clear_signing): registry examples for unit 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 boundarysigning or wallet path
AI analysis · Informational 15/100

This commit only adds new unit tests and device tests for the Ethereum clear-signing feature. It does not change any production firmware code. The tests verify that complex ABI shapes from real-world contract registries are parsed correctly and that nesting limits are enforced. There is no security fix or vulnerability introduced here.

Security candidatetest(clear_signing): recursion depth tests.by PrisionMike · 7e8aad05 · Sep 15, 2026 · 1 fileMessage 67 · AdequateInformational 12Details
Commit message · PrisionMike

test(clear_signing): recursion depth tests.

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

This commit only adds new unit tests for the Ethereum clear-signing feature. It checks that deeply nested data structures are rejected and that shallow-but-wide structures are accepted. No production code is changed, so it cannot by itself introduce or fix a security bug. It does confirm that two existing limits—`_MAX_NESTED_ARRAYS` (2) and `_MAX_ABI_NESTING` (8)—are enforced by the parser.

Security candidatefeat(clear_signing): support deeper structures.by PrisionMike · b9f125a0 · Sep 15, 2026 · 3 filesMessage 57 · ThinModerate 51Details
Commit message · PrisionMike

feat(clear_signing): support deeper structures.

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

This commit expands the Ethereum clear-signing parser in Trezor firmware to support nested tuples and arrays, while adding explicit safety limits on recursion depth and array nesting. The change itself is defensive: it replaces a hard-coded shallow decoder with a recursive one that caps how deep and how many array layers it will accept. The README explains why nested arrays are dangerous—an attacker can craft small transaction data that expands into a huge number of values in memory, potentially exhausting the device. The commit therefore reduces the risk of denial-of-service or memory-exhaustion attacks during transaction decoding, rather than introducing a new vulnerability.

Security candidatechore(core): production feature cleanupby cepetr · e122517a · Sep 14, 2026 · 2 filesMessage 57 · ThinLow 26Details
Commit message · cepetr

chore(core): production feature cleanup

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

This is a small build-configuration cleanup in the Trezor firmware. It changes which internal feature flag the 'production' build mode depends on, removing one old reference and switching another. There is no direct evidence in the commit that this fixes a security vulnerability; it appears to be routine maintenance to keep production builds using the correct set of features.

AI review queuedtest(solana): create account from a foreign baseby Jakub Janků · 2eb57298 · Sep 14, 2026 · 2 filesMessage 82 · StrongInformational 15Details
Commit message · Jakub Janků

test(solana): create account from a foreign base

[no changelog]

(cherry picked from commit 5b037becd0fd6306150fe2d99ec752e96a98223a)

82/100 · StrongMessage clarity
✓ 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 or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit only adds a new test case for Solana transaction signing. It does not change any production firmware code, so it cannot directly introduce a security vulnerability. The test checks that the device can sign a 'create account with seed' transaction where the base account is different from the funding account (a 'foreign base').

AI review queuedrefactor(core): improve internal representation of protobuf definitionsby cepetr · 2b4214cc · Sep 14, 2026 · 5 filesMessage 62 · AdequateLow 30Details
Commit message · cepetr

refactor(core): improve internal representation of protobuf definitions

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

This commit is a code cleanup that changes how Trezor firmware internally labels 32-bit versus 64-bit integer fields in its protobuf handling. It does not add or remove security checks by itself, but it makes the type system more precise so that future integer-overflow mistakes are harder to introduce. The change is described by the author as a refactor with no changelog entry.

AI review queuedfix(core): reject malformed protobuf field keysby cepetr · e05fcc98 · Sep 14, 2026 · 2 filesMessage 57 · ThinModerate 61Details
Commit message · cepetr

fix(core): reject malformed protobuf field keys

[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
parser or protocol pathsecond-pass: security-sensitive path
AI analysis · Moderate 61/100

This commit fixes the way a Trezor hardware wallet's Rust code reads protobuf message field keys. Previously, if reading a field key failed, the decoder silently stopped and treated the message as complete. Now it explicitly checks whether data remains and reports an error if a malformed or truncated field key is encountered. The change prevents an attacker from sneaking invalid or truncated protobuf data past the parser, which could lead to messages being accepted even though they contain garbage or hidden fields.

Security candidaterefactor(core/sys): make writing bootargs a privilege, not a conventionby tychovrahe · 69d3435c · Sep 14, 2026 · 7 filesMessage 97 · StrongModerate 60Details
Commit message · tychovrahe

refactor(core/sys): make writing bootargs a privilege, not a convention

The smcall surface exposed a raw bootargs setter, letting unprivileged code name
any boot command. It had no user -- firmware goes through the reboot_* calls in
bootutils.h, each of which fixes its own -- so remove it rather than filter it.
The dispatch's fatal default is then the enforcement.

Make the rule structural too: bootargs_set is declared only under SECURE_MODE,
and system_emergency_rescue is compiled only where bootargs can be written. It
linked before only because --gc-sections dropped it as unreferenced.

[no changelog]

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

97/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
Why it was queued
credential or privilege state
AI analysis · Moderate 60/100

This commit removes a low-level interface that let any software component tell the device what to do on its next reboot. The change makes reboot control a privileged operation only, so unprivileged code can no longer pick arbitrary boot commands. It is a hardening/refactoring change rather than a documented fix for a specific active bug.

Security candidatedocs(crypto): reproduce third-party license texts in crypto/LICENSE (#7529)by petrsusil · eaffadba · Sep 14, 2026 · 8 filesMessage 93 · StrongInformational 15Details
Commit message · petrsusil

docs(crypto): reproduce third-party license texts in crypto/LICENSE (#7529)

* docs(crypto): reproduce third-party license texts in crypto/LICENSE

Several components of crypto are not covered by the MIT license at the top
of crypto/LICENSE, and some of them (Gifford's SHA-2, the Monero files,
Gladman's AES) require their copyright notice and disclaimer to accompany
binary distributions as well as source. Until now that text existed only in
the individual file headers, which a binary consumer never receives.

Append to crypto/LICENSE a verbatim reproduction of every third-party
license, the files each one covers, the additional copyright holders under
the MIT terms, the public domain / CC0 components, and the GPL-licensed
files. Point at it from LICENSE.md and state that it must be distributed
together with binaries built from crypto.

No code changes; the existing MIT block is unmodified.

* chore: change licence of first-party code from GPL to MIT

(cherry picked from commit e7be2cc8cfffe6906ab7cb96958e8e67d88372f2)

* docs(crypto): add missing third-party attributions to crypto/LICENSE

Add entries for files whose authorship was missing or covered by an
over-broad glob: Dusan Klinec's monero sources, aes/aestst.c under
Brian Gladman's older non-endorsement licence variant, Andrew Moon's
poly1305-donna, and D. J. Bernstein's eSTREAM ECRYPT headers. Narrow
the chacha20poly1305/ entry to the files actually written by Will Glozer.

(cherry picked from commit e7a3c82d6d99548f428a45d5d6caf108795463ac)

* chore: fix typos in licences

(cherry picked from commit f23f9b659e3520ddd962c29b3b59e67a3d30a318)

---------

Co-authored-by: Ondřej Vejpustek <ondrej.vejpustek@satoshilabs.com>

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

This commit is purely legal and administrative housekeeping. It adds missing third-party copyright notices and license texts to the crypto/LICENSE file, fixes a typo in a few license headers, and changes the stated license of some first-party files from GPL to MIT. No executable code was changed, so it cannot introduce a security vulnerability or fix one.

Security candidatefix(core/delizia): switch title/desc in pin popupby obrusvit · 8c5c81b3 · Sep 13, 2026 · 13 filesMessage 57 · ThinInformational 20Details
Commit message · obrusvit

fix(core/delizia): switch title/desc in pin popup

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

This commit fixes a UI wording mix-up on Trezor devices when a user enters a PIN that doesn't match. Previously, the title and description in the 'PIN mismatch' popup were swapped, which could briefly confuse the user about what went wrong. There is no evidence this affects security beyond a minor user-experience issue.

Security candidatefeat(core/caesar): use Marquee in ConfirmHSby obrusvit · 74ec8983 · Sep 13, 2026 · 2 filesMessage 57 · ThinInformational 15Details
Commit message · obrusvit

feat(core/caesar): use Marquee in ConfirmHS

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

This commit is a user-interface tweak for the Trezor hardware wallet's Caesar layout. It replaces a static title label with a scrolling 'Marquee' text effect on the homescreen confirmation screen, so long device labels remain readable. There is no security-relevant change here.

Security candidatefix(core): remove double _colon strings from show_address_detailsby Michal Kazda · a50eb65e · Sep 13, 2026 · 13 filesMessage 77 · AdequateInformational 15Details
Commit message · Michal Kazda

fix(core): remove double _colon strings from show_address_details
- removes their explicit use from Rust code
- adds them to python processed by with_colon
[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
cryptography-sensitive pathboot or update path
AI analysis · Informational 15/100

This commit is a straightforward user-interface string refactor. It moves the colon that appears after labels like 'Account:' and 'Derivation path:' out of the embedded Rust translation strings and into the Python code that calls the address-details screen. There is no security-relevant change in behavior—only where the colon is appended.

Security candidatefeat(core/delizia): use Marquee in PIN promptsby obrusvit · 90cebdcf · Sep 13, 2026 · 3 filesMessage 72 · AdequateInformational 15Details
Commit message · obrusvit

feat(core/delizia): use Marquee in PIN prompts

- PIN keyboard prompts might be longer than screen width, especially
wipe code prompts

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

This commit changes the Trezor hardware wallet's PIN entry screen so that long prompt messages scroll horizontally (like a marquee sign) instead of being cut off. It is a user-interface improvement to handle longer text, such as wipe-code prompts. There is no security vulnerability visible in the code change.

Security candidatefix(core/eckhart): attempts width in PIN keyboardby obrusvit · aac05ac4 · Sep 13, 2026 · 2 filesMessage 57 · ThinInformational 19Details
Commit message · obrusvit

fix(core/eckhart): attempts width in PIN keyboard

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

This commit fixes a layout bug in the PIN entry screen on Trezor's Eckhart hardware model. Previously, the area showing how many PIN attempts remain was given a fixed width of 85 pixels, which could be too narrow for some languages and cause the text to be cut off or poorly displayed. The patch now dynamically measures the actual text width and reserves space accordingly, with a small gap between the prompt and attempts text. There is no direct security vulnerability here; it is a UI correctness and localization improvement.

Security candidatefeat(core): passphrase shown alignmentby obrusvit · ce266730 · Sep 12, 2026 · 5 filesMessage 80 · StrongInformational 20Details
Commit message · obrusvit

feat(core): passphrase shown alignment

- this commit makes the "reveal passphrase" functionality show the
latest written characters in case the whole passphrase does not fit the
screen
- as of recently, passphrases can be 128 characters long
- affects layouts Bolt, Delizia, Eckhart

[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
access controlboot or update pathauthentication path
AI analysis · Informational 20/100

This commit is a user-interface polish change for Trezor hardware wallets. When a user chooses to reveal the passphrase they are typing, and that passphrase is very long (up to 128 characters), the device now scrolls the text so the most recently typed characters remain visible instead of running off the screen. It is a usability fix, not a security bug fix, and does not change how passphrases are stored, processed, or protected.

Security candidatefeat(core): introduce app_arenaby cepetr · cd29104c · Sep 11, 2026 · 47 filesMessage 47 · ThinInformational 15Details
Commit message · cepetr

feat(core): introduce app_arena

[no changelog]

47/100 · ThinMessage clarity
✓ Descriptive subject✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
cryptography-sensitive path
AI analysis · Informational 15/100

This commit is a large internal refactor of the Trezor firmware's third-party application loading system. It replaces the old ELF-based app loader with a new 'app_arena' subsystem that uses a custom binary format, Merkle-tree header verification, and ML-DSA-44 root-of-trust signatures. The change is explicitly marked as a feature ('feat(core): introduce app_arena') with '[no changelog]' and contains no vendor statement that it fixes a security bug. It appears to be a planned architectural redesign, not a security patch.

Security candidatefeat(solana): show base account for create account with seedby Jakub Janků · 1e23f601 · Sep 11, 2026 · 4 filesMessage 95 · StrongModerate 60Details
Commit message · Jakub Janků

feat(solana): show base account for create account with seed

The base account is the field that allows the user to easily confirm
that the newly created account will belong to them. If the base account
differs from the signing account, the user may be transferring lamports
to a new attacker-controlled account. While it is true that the address
of the new account is shown already (and therefore the user doesn't
transfer assets to an unknown destination), the user cannot easily verify
ownership of this new account without the base address --- the new
address is a hash of the base address, the seed, and the owner.

(cherry picked from commit 8bda3f3a6e4b44aef47469549cdf3d62def56c2e)

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
explicit security languagesigning boundarysigning or wallet path
AI analysis · Moderate 60/100

This update improves the Trezor hardware wallet's Solana transaction confirmation screen. When a user creates a new Solana account from a seed, the device now also displays the 'base account' used to derive that new address. Without this, a malicious app could ask the device to create an account controlled by someone else while still making the destination look derived from the user's own keys. The change helps users spot when the new account won't actually belong to them before they approve the transaction.

AI review queuedfeat(solana): confirm space when creating accountsby Jakub Janků · 04ed8330 · Sep 11, 2026 · 4 filesMessage 85 · StrongLow 37Details
Commit message · Jakub Janků

feat(solana): confirm space when creating accounts

We already let the user confirm the space parameter of the Allocate
(With Seed) instruction. For consistency, do the same for the Create
Account (With Seed) instruction.

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

This commit adds an on-screen confirmation step for the 'space' (data size) parameter when creating new Solana accounts on a Trezor device. Previously, this parameter was hidden from the user during Create Account instructions, even though it was already shown for a related 'Allocate' instruction. The change improves consistency and helps users spot transactions that request unexpectedly large storage allocations, which could be a sign of a malicious or misleading transaction.

Security candidatefeat(clear_signing): tuple supports abi values instead of parsers directlyby PrisionMike · 8760d111 · Sep 10, 2026 · 4 filesMessage 62 · AdequateModerate 58Details
Commit message · PrisionMike

feat(clear_signing): tuple supports abi values instead of parsers directly

[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 · Moderate 58/100

This commit refactors how Trezor firmware parses Ethereum 'clear signing' data so that tuple/struct fields can themselves contain nested tuples or arrays, instead of only simple leaf values. The change removes a previous restriction and updates the parser to walk nested structures correctly. It also removes an old safety guard that rejected empty tuples, though the code still rejects them elsewhere. The commit is described as a feature, not a security fix, but the prior code's leaf-only limitation could have caused mis-parsing of legitimate nested ABI structures, and the old empty-tuple guard was explicitly motivated by preventing an unbounded parse loop.

Security candidatetests(clear_signing): unit tests for .from_proto()by PrisionMike · 2aec9696 · Sep 10, 2026 · 1 fileMessage 60 · AdequateInformational 15Details
Commit message · PrisionMike

tests(clear_signing): unit tests for .from_proto()

[no changelog]

60/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ 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 adds new unit tests for an existing Ethereum clear-signing decoder. It does not change any production firmware code, so it cannot introduce a security vulnerability or fix one directly. The tests document how the decoder currently handles various Ethereum ABI data shapes and which malformed inputs it rejects.

Security candidatefeat(common,core,python,tests): support creating Stellar contracts.by Jun Luo · 95adcc90 · Sep 10, 2026 · 29 filesMessage 100 · StrongInformational 15Details
Commit message · Jun Luo

feat(common,core,python,tests): support creating Stellar contracts.

Support `CREATE_CONTRACT_V2` in `InvokeHostFunctionOp` and
`CREATE_CONTRACT_V2_HOST_FN` in Soroban authorization entries.

100/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✓ Names security-relevant behavior explicitly
Why it was queued
access controlsigning or wallet pathauthentication path
AI analysis · Informational 15/100

This commit adds support for a new Stellar blockchain feature: creating smart contracts (contract deployment) on Trezor hardware wallets. It extends the messages, layouts, serialization, and tests so users can review and sign Stellar 'create contract' transactions and related authorization entries. There is no indication of a security vulnerability in the change itself; it is a feature addition with explicit user confirmation steps and deliberate exclusions of unsupported variants.

Security candidaterefactor(core/stellar): prepare for contract creation support.by Jun Luo · 8d312f5c · Sep 10, 2026 · 9 filesMessage 90 · StrongInformational 14Details
Commit message · Jun Luo

refactor(core/stellar): prepare for contract creation support.

- Share the HashIDPreimage header (envelope type and network ID) between
the Soroban authorization payload and contract address derivation.
- Move the CONTRACT_ID_PREIMAGE_FROM_ASSET writer next to the other
writers.
- Rename `sac_address_from_asset` to `contract_address_from_asset` and
move it to `helpers.py`.
- Extract `_confirm_args` and `_same_xdr` for reuse.

[no changelog]

90/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Names security-relevant behavior explicitly
Why it was queued
access controlsigning or wallet pathauthentication path
AI analysis · Informational 14/100

This commit is a routine internal code cleanup in the Stellar cryptocurrency support of Trezor firmware. It renames and moves helper functions, extracts reusable pieces, and adds tests. There is no change to user-visible behavior or security boundary, and no security issue is apparent.

Security candidatefeat(core/delizia): new MoreInfoScreenby obrusvit · 0b0a1345 · Sep 9, 2026 · 11 filesMessage 80 · StrongInformational 17Details
Commit message · obrusvit

feat(core/delizia): new MoreInfoScreen

- the new screen automatically paginates if the text overflows
- remove the usage of `flow/request_number` by uPy based main+menu flow

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

This commit refactors the user interface for entering numbers on the Trezor Safe 5 (Delizia layout). It replaces a Rust-based multi-page 'flow' with a simpler screen that hands the 'more info' menu back to Python code. It also adds a new full-screen text component that can paginate long information. There is no obvious security bug in the diff, but the change touches code that handles user confirmation during device setup and backup, so any mistake could affect what the user sees or approves.

AI review queuedfix(core): correct timestamp conversion in `time_gmtime2000()`by Roman Zeyde · d0f50b4d · Sep 9, 2026 · 4 filesMessage 95 · StrongLow 37Details
Commit message · Roman Zeyde

fix(core): correct timestamp conversion in `time_gmtime2000()`

It was working on the emulator (since `mp_int_t` is 64-bit)
but failing on HW devices.

Also, improve `test_lock_time_datetime` coverage.

Note: `2106-02-07 06:28:15` = 2**32-1 seconds from epoch.

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

This commit fixes a date-handling bug in Trezor hardware wallets. The device converts Bitcoin transaction lock-time timestamps into human-readable dates on its screen. Before the fix, the code used a 32-bit signed integer on real hardware, so any date after the year 2038 (and in practice after about 2068 in this code) would be misread and the wrong date would be shown to the user. The fix switches to a 64-bit timestamp type and adds tests for far-future dates up to the year 2106. The main risk is that a user could be tricked into approving a transaction whose real lock-time date is different from what the device displays.