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
1762commits · 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 3 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(core): correct Rust UI chunkification logic for non-ASCII textby Roman Zeyde · 958ce98a · Aug 25, 2026 · 1 fileMessage 89 · StrongLow 44Details
Commit message · Roman Zeyde

fix(core): correct Rust UI chunkification logic for non-ASCII text

Otherwise, `text[..final_index]` would panic.

[no changelog]

89/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body✓ Explains rationale or failure mode
Why it was queued
second-pass: broader security terminology
AI analysis · Low 44/100

This commit fixes a bug in the Trezor hardware wallet's Rust UI code that splits text into chunks for display. The old code used byte positions instead of character positions when handling non-ASCII text (like accented letters or non-Latin scripts). This could cause the device to crash with a panic when trying to display certain international characters, because Rust would reject a slice that cut through the middle of a multi-byte character. The fix makes the chunking logic respect character boundaries. There is no direct evidence in the commit that this is exploitable as a security attack, but any device panic during rendering of user-facing text is at minimum a denial-of-service concern.

AI review queued fix(monero): reject sweep change aliasing money-carrying outputsby Petr Susil · 18507cfc · Aug 25, 2026 · 2 filesMessage 97 · StrongHigh 71Details
Commit message · Petr Susil

fix(monero): reject sweep change aliasing money-carrying outputs

Prevent the sweep-shape exemption from accepting an unvalidated change
address that aliases a money-carrying output.

Honest sweeps remain valid because the fake output carries amount 0,
while the primary-address exception is preserved because step 6 derives
the same one-time key either way.

(cherry picked from commit 8e2e0b27ba0fdc0dd47cb94fc019405ea48b0a7e)

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
defensive validationsigning or wallet pathsecond-pass: near security thresholdsecond-pass: security-sensitive path
AI analysis · High 71/100

This update fixes a flaw in how Trezor handled certain Monero 'sweep' transactions. In a sweep, the device normally skips checking whether the change address truly belongs to the user, because the change output is supposed to carry zero coins and go to a random address. A malicious computer or wallet software could have reused that unvalidated change address for an output that actually holds money. The device would then treat that money as change and lock it with a key the user might not control, effectively freezing or misdirecting funds. The fix rejects such transactions unless the address is the user's own primary address, where the math happens to be safe either way.

AI review queuedfix(core): avoid race condition when collecting qstrsby Roman Zeyde · 083bc87f · Aug 24, 2026 · 2 filesMessage 62 · AdequateInformational 21Details
Commit message · Roman Zeyde

fix(core): avoid race condition when collecting qstrs

[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
second-pass: broader security terminology
AI analysis · Informational 21/100

This commit fixes a build-time race condition in the script that generates a list of internal string identifiers (called 'qstrs') used by the Trezor firmware. Previously, the generator could read a generated translation file while it was being updated, potentially producing an inconsistent list. The fix makes the generator read translation string names directly from the source translation file instead of from a generated file, and also excludes generated files from the grep search. This is a build-system reliability fix, not a runtime security vulnerability in the device itself.

AI review queuedchore(translations): sync Crowdin translationsby Thalarion · c8626c70 · Aug 24, 2026 · 6 filesMessage 57 · ThinInformational 15Details
Commit message · Thalarion

chore(translations): sync Crowdin translations

[no changelog]

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

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

AI review queuedfeat(solana): warn about hooks on Transfer Checked with trailing accountsby Jakub Janků · 7b89aa4c · Aug 24, 2026 · 9 filesMessage 100 · StrongModerate 51Details
Commit message · Jakub Janků

feat(solana): warn about hooks on Transfer Checked with trailing accounts

Token-2022 mints can carry the transfer hook extension, which makes
Transfer Checked CPI into a mint-configured hook program. The hook
program (and any extra accounts it requires) is passed to the
instruction as trailing accounts after the owner/multisig signers, so
a transfer that executes a hook always carries at least one trailing
account; conversely, without trailing accounts the hook CPI cannot
succeed (see add_extra_accounts_for_execute_cpi in
spl-transfer-hook-interface, which requires the hook program account
among the additional accounts).

Warn the user before displaying the trailing accounts of a Token-2022
Transfer Checked instruction: a hook may impose additional
restrictions or fees on the transfer and would otherwise execute
without any indication that a third-party program runs. The deprecated
Transfer instruction needs no warning, as it can never execute hooks
(Token-2022 aborts with MintRequiredForTransfer when the source
account carries the hook extension and no mint is provided).

The warning is defined in programs.json as a new optional
per-instruction field `trailing_accounts_warning`, displayed only when
the instruction carries trailing accounts. This mirrors the existing
`is_deprecated_warning` mechanism: the warning text lives in the
instruction definitions and is rendered via confirm_metadata under the
instruction's title.

Partially fixes: https://github.com/satoshilabs/trezor-firmware/issues/325

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
(cherry picked from commit ee443c5d09bdfd867c7cd93c812a9e4abc5460ed)

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

This commit adds a new on-screen warning for Trezor users when they are about to sign a specific Solana token transfer that includes extra accounts. Those extra accounts can mean a third-party 'transfer hook' program is triggered, potentially adding hidden fees or restrictions. The change is a user-interface improvement to prevent users from unknowingly approving such transfers, not a fix for a code execution bug in Trezor itself.

AI review queuedrefactor(translations): remove solana__instruction_is_multisigby Jakub Janků · 2552d6d3 · Aug 23, 2026 · 10 filesMessage 67 · AdequateInformational 15Details
Commit message · Jakub Janků

refactor(translations): remove solana__instruction_is_multisig

[no changelog]

(cherry picked from commit 5d3c70305675df729620c4f29a780f9cd008f130)

67/100 · AdequateMessage clarity
✓ Specific, 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 · Informational 15/100

This commit removes a single unused translation string about Solana multisig instructions from the Trezor firmware. It is a cleanup/refactoring change with no visible security relevance. There is no code behavior change, no bug fix, and no vulnerability patch.

AI review queuedfeat(core/ethereum): allow EIP-7702 delegation under strict safety checksby Roman Zeyde · 4f3ad296 · Aug 22, 2026 · 3 filesMessage 62 · AdequateLow 40Details
Commit message · Roman Zeyde

feat(core/ethereum): allow EIP-7702 delegation under strict safety checks

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

This commit changes how Trezor hardware wallets handle a new Ethereum feature called EIP-7702, which lets users temporarily delegate control of their account to another smart contract. Previously, Trezor only allowed this delegation if the user lowered their safety settings. Now, it allows delegation under the strictest safety settings, but only for a pre-approved list of delegate addresses. Revocation (removing a delegate) was already allowed under strict settings and remains allowed. The change is framed as adding 'strict safety checks' rather than removing protections entirely.

AI review queuedfix(core/ethereum): disallow non-zero ETH value on SLIP-24 ERC-20 swapsby Roman Zeyde · eefd32c3 · Aug 21, 2026 · 3 filesMessage 77 · AdequateHigh 70Details
Commit message · Roman Zeyde

fix(core/ethereum): disallow non-zero ETH value on SLIP-24 ERC-20 swaps

(cherry picked from commit 2c769ec0f61026d3472f5d2d261bf0ed043ab5c9)

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

This update fixes a logic flaw in Trezor's Ethereum signing code. When a user was doing an ERC-20 token swap using a SLIP-24 payment request, the device could also be instructed to send native ETH at the same time. That combination is not expected in a normal token swap and could let an attacker trick the user into authorizing an unintended ETH transfer alongside the token swap. The fix now rejects such transactions outright.

AI review queuedtest(core/ethereum): fix SLIP-24 payment request for ERC-20 tokensby Roman Zeyde · 3d24462d · Aug 21, 2026 · 2 filesMessage 72 · AdequateInformational 12Details
Commit message · Roman Zeyde

test(core/ethereum): fix SLIP-24 payment request for ERC-20 tokens

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

This commit only adds a new automated test case for signing an Ethereum ERC-20 token transfer using a SLIP-24 payment request. It does not change any production firmware code, so it cannot introduce a security vulnerability or directly fix one in shipped software. The change is purely in the test suite and its recorded expected screen outputs.

AI review queuedrefactor(core/ethereum): simplify `test_signtx_payment_req_long_value`by Roman Zeyde · 1e897557 · Aug 21, 2026 · 1 fileMessage 62 · AdequateInformational 15Details
Commit message · Roman Zeyde

refactor(core/ethereum): simplify `test_signtx_payment_req_long_value`

[no changelog]

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

This commit only refactors a single automated test file for Ethereum transaction signing on Trezor hardware wallets. It extracts duplicated code into a helper function and updates how the test checks for an expected error message. There is no change to the actual firmware, wallet logic, or security behavior.

AI review queuedfix(l10n): fix German recover button textby Michal Kazda · d975b58f · Aug 20, 2026 · 2 filesMessage 57 · ThinInformational 15Details
Commit message · Michal Kazda

fix(l10n): fix German recover button text
[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 German translation update. It changes the wording on a wallet recovery button and refreshes the translation signature file that verifies the translations are authentic. There is no security issue here.

AI review queuedfix(core): limit protobuf nesting depthby Martin Milata · dd7afbc3 · Aug 20, 2026 · 3 filesMessage 57 · ThinModerate 66Details
Commit message · Martin Milata

fix(core): limit protobuf nesting depth

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

This commit adds a hard limit on how deeply nested Protobuf messages can be when the Trezor device decodes them. Without such a limit, a malicious or malformed message could nest messages inside messages indefinitely, potentially crashing the device or causing other problems. The change caps nesting at 16 levels and adds a test to confirm that deeper nesting is rejected.

AI review queuedrefactor(python): faster serialization of nested protobufby Martin Milata · 83947a18 · Aug 20, 2026 · 1 fileMessage 77 · AdequateInformational 18Details
Commit message · Martin Milata

refactor(python): faster serialization of nested protobuf

The function was exponential in the nesting depth. Changed to use more
memory while not blowing up CPU.

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

This is a routine performance refactor in Trezor's Python library. It replaces a slow, CPU-heavy way of measuring nested protobuf message sizes with a faster approach that builds the message in memory once. There is no indication this fixes a security vulnerability; it is described purely as a speed improvement.

AI review queuedstyle(core/rust): clippyby matejcik · 6f96a4d4 · Aug 20, 2026 · 8 filesMessage 28 · OpaqueInformational 15Details
Commit message · matejcik

style(core/rust): clippy

28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100

This commit is a routine code cleanup to satisfy the Rust Clippy linter. It removes unnecessary reference symbols (&), rewrites a small match block to assign a value directly, and removes an unused import. There is no functional change and no security relevance visible in the diff.

AI review queuedfix(solana): correct misleading account labels in token instruction UIby Jakub Janků · 5a424238 · Aug 19, 2026 · 4 filesMessage 93 · StrongModerate 53Details
Commit message · Jakub Janků

fix(solana): correct misleading account labels in token instruction UI

Fix wrong role labels in the SPL Token / Token 2022 UI definitions
(the classic Token Program declares identical account lists):

- Burn: "Mint authority" -> "Owner" (the account is the owner/delegate)
https://docs.rs/spl-token-2022-interface/3.1.1/spl_token_2022_interface/instruction/enum.TokenInstruction.html#variant.Burn
- Freeze/Thaw Account: "Owner" -> "Freeze authority"
https://docs.rs/spl-token-2022-interface/3.1.1/spl_token_2022_interface/instruction/enum.TokenInstruction.html#variant.FreezeAccount
- Mint to Checked: "Owner" -> "Mint authority"
https://docs.rs/spl-token-2022-interface/3.1.1/spl_token_2022_interface/instruction/enum.TokenInstruction.html#variant.MintToChecked
- Revoke: "Revoke delegate" -> "Revoke delegate for" (the shown account
is the source token account, not the delegate); also fix "Rewoke" typo
https://docs.rs/spl-token-2022-interface/3.1.1/spl_token_2022_interface/instruction/enum.TokenInstruction.html#variant.Revoke

Paritally fixes: https://github.com/satoshilabs/trezor-firmware/issues/325

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
(cherry picked from commit e38b1ac28b1ebef85166360c3e1db1192d4b0699)

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

This commit fixes incorrect on-screen labels shown to Trezor users when they confirm Solana token operations such as burning tokens, freezing accounts, minting tokens, or revoking a delegate. The labels wrongly described whose account or authority was involved, which could trick a user into approving a transaction they did not understand. The actual blockchain instructions and account handling were not changed—only the text the user sees on the device screen.

AI review queuedtest(solana): predefined staking flow classifiersby Jakub Janků · 1422a017 · Aug 19, 2026 · 2 filesMessage 82 · StrongInformational 15Details
Commit message · Jakub Janků

test(solana): predefined staking flow classifiers

[no changelog]

(cherry picked from commit 21cc27648ce794817622bb2207ee520d5d5fad38)

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 automated tests for Solana staking transaction detection. It does not change any production wallet code, so it cannot directly introduce a security vulnerability or fix one in shipped firmware.

AI review queuedrefactor(solana): separate staking tx format check from confirmationby Jakub Janků · 012f9768 · Aug 19, 2026 · 1 fileMessage 95 · StrongInformational 15Details
Commit message · Jakub Janků

refactor(solana): separate staking tx format check from confirmation

This will allow us to unit test the decision mechanism that switches
between the predefined and the generic confirmation flow.

Token transfer code is structured in a similar way.

[no changelog]

(cherry picked from commit 17297513cf54f8c286df02ce81ba510c8a354df6)

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 · Informational 15/100

This commit is a code cleanup for Trezor's Solana staking transaction handling. It splits one large function into smaller helper functions that decide whether a transaction should use a simplified, user-friendly confirmation screen. The actual security checks and confirmation behavior are unchanged; the change only makes the code easier to test.

AI review queuedfix(solana): avoid re-confirmation in staking flowsby Jakub Janků · c195cec9 · Aug 19, 2026 · 1 fileMessage 85 · StrongLow 35Details
Commit message · Jakub Janků

fix(solana): avoid re-confirmation in staking flows

Decide whether to use the predefined flow or whether to fall back
to the generic flow before requesting any confirmation from the user.

[no changelog]

(cherry picked from commit 4d3b5a5a64ea0fcaf34934d9a61e3ee70eb06449)

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

This change fixes a logic bug in how Trezor handles Solana staking transactions. Previously, the device could ask the user to confirm a staking detail before it had fully verified that the transaction matched a safe, predefined pattern. The fix moves that confirmation check to after all safety checks are complete, so the device only asks for confirmation when it is confident the transaction is a known, legitimate staking flow. This prevents a potentially malicious or malformed transaction from tricking the user into confirming something risky.

AI review queuedfeat(tron): core edits to include `call_value` in `TriggerSmartContract`by PrisionMike · f476eaec · Aug 19, 2026 · 3 filesMessage 62 · AdequateLow 44Details
Commit message · PrisionMike

feat(tron): core edits to include `call_value` in `TriggerSmartContract`

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

This commit changes how Trezor hardware wallets handle Tron smart-contract calls that include native TRX tokens. Previously, the device did not display or validate the `call_value` field, which means a user could be tricked into sending TRX along with a contract call without seeing it on the device screen. The patch adds a safety check that rejects oversized values and shows the TRX amount during transaction confirmation. It is a defensive fix rather than an exploit.

AI review queuedfix(core/ethereum): fix SLIP-24 payment request for ERC-20 tokensby Roman Zeyde · b13a17f9 · Aug 19, 2026 · 2 filesMessage 62 · AdequateLow 38Details
Commit message · Roman Zeyde

fix(core/ethereum): fix SLIP-24 payment request for ERC-20 tokens

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

This commit fixes a bug in the Trezor hardware wallet's Ethereum transaction signing flow. When using SLIP-24 payment requests with ERC-20 token transfers, the device could incorrectly skip the user-confirmation step for the transaction details. The fix ensures that 'clear signing' mode (which bypasses some confirmations) is checked before the payment-request path, so users still see and approve the token transfer details.

AI review queuedchore(translations): sync additional Crowdin translationsby Michal Kazda · a2b756fb · Aug 19, 2026 · 6 filesMessage 62 · AdequateInformational 15Details
Commit message · Michal Kazda

chore(translations): sync additional Crowdin translations

[no changelog]

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

This commit only updates translated text strings in Czech, German, Spanish, French, and Portuguese translation files, plus the corresponding translation signature metadata. There are no code changes, no security fixes, and no behavior changes. It is a routine localization sync.

AI review queuedfix(core): improve confirmation UX in super-shamirby obrusvit · c97383ba · Aug 19, 2026 · 14 filesMessage 77 · AdequateInformational 15Details
Commit message · obrusvit

fix(core): improve confirmation UX in super-shamir

- confirm groups setup
- confirm individial group thresholds

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 improves the on-screen confirmation experience when creating an advanced Shamir backup on a Trezor device. It adds extra prompts that show the user how many backup groups exist, how many groups are needed to recover the wallet, and the threshold for each individual group. There is no security vulnerability here; it is purely a user-interface improvement to help people verify their backup settings.

AI review queuedchore(translations): sync Crowdin translationsby Thalarion · 883edebe · Aug 19, 2026 · 6 filesMessage 57 · ThinInformational 15Details
Commit message · Thalarion

chore(translations): sync Crowdin translations

[no changelog]

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

This commit is a routine translation update for the Trezor hardware wallet firmware. It only changes user-facing text strings in Czech, German, Spanish, French, and Portuguese translation files, plus the translation signature metadata. There are no code logic changes, no security fixes, and no functional changes to how the device operates.

AI review queuedrefactor(translations): remove unused stellar_timeboundsby Jakub Janků · 725b3eb0 · Aug 18, 2026 · 10 filesMessage 77 · AdequateInformational 15Details
Commit message · Jakub Janků

refactor(translations): remove unused stellar_timebounds

[no changelog]

(cherry picked from commit f4ad393ee8c8ec03a73ff89e23adec48e77dbbc5)

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 removes an unused translation string called 'stellar__timebounds' from the Trezor firmware's translation system. It is a cleanup/refactoring change with no visible effect on device behavior or security. The signatures.json file was also updated because removing a string changes the cryptographic hash (merkle root) used to verify translation files.

AI review queuedfix(l10n): add generated filesby Michal Kazda · 107d49e1 · Aug 18, 2026 · 5 filesMessage 57 · ThinInformational 15Details
Commit message · Michal Kazda

fix(l10n): add generated files
[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 regenerates translation files after some text labels were moved from one category to another (for example, 'Authenticate' and 'Wipe' were changed from general words to button labels). There is no code behavior change, no bug fix, and no security relevance visible in the diff.