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.
Message quality measures whether a commit identifies its scope, purpose, rationale, testing, and supporting references. It does not change the security-severity score.
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.
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…
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…
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…
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)
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…
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
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
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…
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.
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
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…
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…
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
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 …
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…
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
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
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 …
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
Expand any commit for its author, full message, clarity score, changed files, triage signals, analysis, and source link.
AI review queuedfix(ripple): show dt even when it's 0by PrisionMike · 76faf52f · Aug 18, 2026 · 4 filesMessage 57 · ThinLow 49Details
Commit message · PrisionMike
fix(ripple): show dt even when it's 0
57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 49/100
This commit fixes a bug in Trezor's Ripple (XRP) signing code. When a payment request included a destination tag of 0, the device treated it as if no tag was set, so it did not show or verify the tag. Because destination tags are used to route funds to the correct recipient on exchanges, omitting tag 0 could let an attacker trick a user into approving a payment that looks tagless but actually sends to tag 0, potentially sending funds to the wrong account or making them hard to recover.
AI review queuedfix(core/monero): validate change address on sweep transactionsby Petr Susil · 11c2dedf · Aug 18, 2026 · 3 filesMessage 100 · StrongHigh 74Details
Commit message · Petr Susil
fix(core/monero): validate change address on sweep transactions
The sweep shape (declared change amount 0, two outputs) is exempt from the change ownership check, because on a sweep the change address is a random throwaway address, not ours. But the shape is host-controlled, so a malicious host can point change_dts.addr at the paying recipient and have the exemption accept it. That output is then keyed as change in step 6, derived from our own view key (a*R), leaving it unspendable by both the recipient and the owner.
Reject the aliasing: an address we decline to validate must never be the address of an output that carries money. Honest sweeps are unaffected -- their fake output carries amount 0.
Fixes: https://github.com/trezor/trezor-firmware/issues/7544 (cherry picked from commit ea6caf1e1875df05e983629df90d3dd217af4ab9)
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✓ Names security-relevant behavior explicitly
Why it was queued
defensive validationsigning or wallet pathsecond-pass: near security thresholdsecond-pass: security-sensitive path
AI analysis · High 74/100
This update fixes a bug in how Trezor handles certain Monero 'sweep' transactions. In a sweep, one output is a fake zero-value decoy with a random address, and the device normally skips checking that the change address belongs to the wallet. A malicious computer app could exploit that skip by claiming the real payment recipient's address is the change address. The device would then encrypt the recipient's output using the wallet's own secret view key, making the money effectively unspendable by the recipient and unrecoverable by the sender. The fix adds a check: if the unvalidated change address appears on any output that actually carries money, the transaction is rejected. Honest sweeps, where the decoy carries zero coins, still work normally.
AI review queuedfix(core): update fixturesby Michal Kazda · b30af88e · Aug 16, 2026 · 2 filesMessage 47 · ThinInformational 12Details
Commit message · Michal Kazda
fix(core): update fixtures [no changelog]
47/100 · ThinMessage clarity
✓ Descriptive subject✓ 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 12/100
This commit only refreshes test data files: it updates a translation signature metadata file and regenerates UI test fixtures. There is no code change, no security fix, and no indication of a vulnerability being addressed.
AI review queuedrefactor(translations): merge {cardano,ethereum}__networkby Jakub Janků · b0a549cd · Aug 16, 2026 · 13 filesMessage 77 · AdequateInformational 15Details
This is a preparatory commit, the string will be used for another cryptocurrency as well.
[no changelog]
77/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This is a harmless internal cleanup: the word "Network" was previously stored separately for Cardano and Ethereum, and is now merged into a single shared translation key called words__network. No user-facing text, security behavior, or transaction logic changed.
AI review queuedchore(translations): sync Crowdin translationsby Thalarion · 82264593 · Aug 15, 2026 · 4 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 only updates translated text strings in Czech, German, and Spanish language files, plus the corresponding translation signature metadata. There are no code, logic, or security-related changes.
AI review queuedtest(stellar): remove signer using StellarSetOptionsOpby Jakub Janků · 5b1837ad · Aug 14, 2026 · 1 fileMessage 87 · StrongInformational 15Details
Commit message · Jakub Janků
test(stellar): remove signer using StellarSetOptionsOp
[no changelog]
(cherry picked from commit fd5e83f9c32e3ec3e41341e1091a7fbedb2cc767)
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 or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit only adds a new test case for the Stellar cryptocurrency feature. It records an expected transaction signature for a 'remove signer' operation so the device can be tested against a known-good value. There is no code change, no bug fix, and no security-relevant behavior change.
AI review queuedfix(stellar): confirm signer weight set by StellarSetOptionsOpby Jakub Janků · 4aa20901 · Aug 14, 2026 · 2 filesMessage 93 · StrongModerate 55Details
Commit message · Jakub Janků
fix(stellar): confirm signer weight set by StellarSetOptionsOp
Fixes: https://github.com/satoshilabs/trezor-firmware/issues/312 (cherry picked from commit d1beab9790243949a972d6ddca1b297a6efa9ff7)
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 55/100
This update fixes how the Trezor hardware wallet displays a Stellar 'Set options' operation when a signer is being added or changed. Previously, the device did not show the signer's 'weight' value on its screen. Because weight controls how powerful a signer is (for example, how many signatures are needed to approve a transaction), a user could unknowingly approve a high-weight signer that gives an attacker more control over the account. The fix now shows the weight during confirmation, so users can spot suspicious changes before signing.
AI review queuedfix(solana): show optional instruction params by defaultby Jakub Janků · 0fea1482 · Aug 12, 2026 · 7 filesMessage 100 · StrongHigh 76Details
Commit message · Jakub Janků
fix(solana): show optional instruction params by default
Prior to this change, optional params of the instructions of the recognized Solana programs were never displayed when their value is None, even though None may encode an action rather than the absence of one.
This commit changes the confirmation code so that optional params of the value None are always displayed unless they are hidden using a special new modifier "default_value_to_hide": "none".
Both semantics None can have are present in the affected instructions. In the SetAuthority instructions of the Token programs, None is an action: it unsets the authority, usually irreversibly. It is now displayed, so the user can distinguish removing the authority from setting it to themselves (the latter is hidden as a safe default). In the SetLockup instructions of the Stake program, None means the field is left unchanged, so it is hidden using the "none" modifier. A lockup timestamp or epoch of 0, previously hidden as a default value, is a real value that clears the lockup constraint and is now displayed.
Set lockup impl: https://github.com/solana-program/stake/blob/68217e1e5e17d495280ef9e12243c7ebbe6e1710/interface/src/state.rs#L525-L551
Set authority impl: https://github.com/solana-program/token-2022/blob/426400f29d5f1e299be8b353fdf13f22358fbd68/program/src/processor.rs#L709-L1025
(cherry picked from commit 6058377602f6989c58bbe599aa0e5c5e85324ce4)
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 · High 76/100
This update fixes a security issue in Trezor's Solana transaction signing where important instruction details were hidden from the user. Previously, when a Solana instruction had an optional parameter set to 'None', Trezor simply did not show it at all. But 'None' can sometimes mean something important, like permanently removing an authority, not just 'nothing happens.' After the fix, Trezor now shows 'None' to the user by default, unless the developers explicitly mark that parameter as safe to hide. This helps prevent users from unknowingly approving destructive actions, such as removing their own control over tokens or clearing stake account lockups.
AI review queuedfix(core): nostr string serializationby Martin Milata · 1239c9e1 · Aug 11, 2026 · 3 filesMessage 57 · ThinModerate 60Details
Commit message · Martin Milata
fix(core): nostr string serialization
[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 · Moderate 60/100
This commit fixes a bug in how the Trezor hardware wallet builds Nostr event signatures. Previously, special characters in the event content and tags (like quotes, backslashes, tabs, and newlines) were not properly escaped when creating the JSON string that gets signed. This could cause the device to compute a signature that does not match what standard Nostr software expects, or in some cases could allow a malicious app to craft content that changes the meaning of what the user approved on screen versus what is actually signed. The fix adds proper JSON string escaping for both the main content and tag strings.
AI review queuedfix(solana): fall back to generic UI for more ALT referencesby Jakub Janků · cd6e7596 · Aug 11, 2026 · 4 filesMessage 93 · StrongModerate 61Details
Commit message · Jakub Janků
fix(solana): fall back to generic UI for more ALT references
transfer_token_instruction.token_mint and transfer_token_instruction.owner can be Address Lookup Table (ALT) references. Previously, the predefined token transfer flow would misleadingly display just the ALT address. The user thus couldn't distinguish an actual address from an ALT reference. Now, the handler falls back to the generic ALT-aware confirmation UI.
537b34f847f8e3f97e4444be9f8f50706ac34075 added a check for transfer_token_instruction.destination_account, but omitted the token_mint and owner fields which can be ALT references as well.
(cherry picked from commit b992a24a93d77066b3ac2fec1dae7129d09427d1)
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 61/100
This update fixes a display bug in Trezor's Solana token-transfer confirmation screen. When a token transfer uses Solana Address Lookup Tables (ALTs) to refer to the token mint or the owner account, the device previously showed the lookup-table address as if it were the real account address. That could trick a user into approving a transfer they did not fully understand. The fix makes these cases fall back to a more cautious, generic confirmation screen that clearly marks ALT references.
AI review queuedfix(solana): fall back to generic UI if stake lockup setby Jakub Janků · 5a530509 · Aug 11, 2026 · 2 filesMessage 93 · StrongModerate 60Details
Commit message · Jakub Janků
fix(solana): fall back to generic UI if stake lockup set
Prior to this change, the predefined staking flow allowed lockup.custodian = _SYSTEM_PROGRAM_ID, lockup.epoch > 0, and lockup.unix_timestamp > 0. However, these values were not displayed to the user. This could lead to the user loosing access to their funds if the time values were set to distant future.
The change should not modify the behavior when working with Suite since it generates init instructions with lockup.epoch=0 and lockup.unix_timestamp=0:
(cherry picked from commit 5a12ad231741e0406f9d7f7a0b2e15a7237f0bbd)
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 60/100
This update fixes a security gap in Trezor's handling of Solana staking. Previously, if someone set up a stake account with a future unlock date (a 'lockup') using values that Trezor's normal flow didn't expect, the device would silently approve the transaction without showing those lockup details on screen. That could trap a user's funds until a far-future date. The fix makes Trezor fall back to a more detailed, generic confirmation screen whenever a lockup is present, so the user can see and approve the terms explicitly.
AI review queuedfeat(nfc): Update RFAL library to version 4.2.0 due to added presence check on ISO-DEP layerby Ludek Farsky · 6e2dbb91 · Aug 10, 2026 · 62 filesMessage 74 · AdequateLow 32Details
Commit message · Ludek Farsky
feat(nfc): Update RFAL library to version 4.2.0 due to added presence check on ISO-DEP layer
[no changelog]
74/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Explains rationale or failure mode! No meaningful explanatory body
Why it was queued
second-pass: unusually broad change
AI analysis · Low 32/100
This commit upgrades the third-party STMicroelectronics NFC middleware (RFAL) inside Trezor firmware from version 4.0.2 to 4.2.0. The stated reason is to add a 'presence check' in the ISO-DEP layer, which helps the device verify that an NFC card is still nearby during a transaction. The diff is almost entirely a bulk import of ST's updated library files, so the actual security-relevant changes are not visible in the commit itself. There is no Trezor changelog entry and no CVE or advisory referenced.
AI review queuedtest(core): drop an unused parameter of `make_payment_request()`by Roman Zeyde · 6dd19fdc · Aug 8, 2026 · 8 filesMessage 72 · AdequateInformational 15Details
Commit message · Roman Zeyde
test(core): drop an unused parameter of `make_payment_request()`
[no changelog]
72/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit only cleans up test code by removing an unused 'session' argument from a helper function used in automated tests. It does not change the actual Trezor firmware or any code that runs on the device, so it has no security impact for users.
AI review queuedbuild(core): drop stale trezor_lib dependency from kernelby matejcik · 7e64fef5 · Aug 7, 2026 · 3 filesMessage 62 · AdequateInformational 12Details
Commit message · matejcik
build(core): drop stale trezor_lib dependency from kernel
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 12/100
This is a routine build cleanup in the Trezor firmware kernel. It removes an unused Rust library dependency called 'trezor_lib' and replaces it with a reference to another module ('io') to ensure certain Rust symbols are still included during linking. There is no indication this change fixes or introduces a security vulnerability.
AI review queuedfix(build-docker): stop swallowing pub-bin copy errorsby Andrew Kozlik · d829eda8 · Aug 6, 2026 · 1 fileMessage 85 · StrongInformational 15Details
kernel never has a pub bin, and secmon has none when built only as a firmware dependency; skip the copy in those known-benign cases instead of producing "cp: cannot stat" noise and blanket-ignoring cp's exit status, so a genuine copy failure is no longer silently discarded.
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
second-pass: broader security terminology
AI analysis · Informational 15/100
This change fixes a build script that was ignoring copy errors. Previously, the script would silently ignore any failure when copying public binary files, which could hide real problems. Now it only skips the copy when the file genuinely doesn't exist for known cases (the kernel, and secmon when built as a dependency), and will report actual copy failures.
AI review queuedrefactor(core): improve composability of power managerby tychovrahe · 869b08fb · Aug 6, 2026 · 30 filesMessage 62 · AdequateInformational 17Details
Commit message · tychovrahe
refactor(core): improve composability of power manager
[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: unusually broad change
AI analysis · Informational 17/100
This is a large internal refactoring of the Trezor firmware's power-management code. It renames directories, splits the PMIC (power-management IC) interface into a core part and a charger-specific extension, and moves battery brownout logic into a chemistry-specific fuel-gauge module. There is no direct evidence this commit fixes a security vulnerability; it appears to be architectural cleanup to support future hardware variants (e.g., a power-latch board without a charger).
AI review queueddocs: fix links outside book rootby Martin Milata · 0d8d4b1b · Aug 5, 2026 · 10 filesMessage 57 · ThinInformational 15Details
Commit message · Martin Milata
docs: fix links outside book root
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 pathdocumentation-only discountsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit only fixes broken or awkward documentation links inside the project's user guide. It replaces relative links that point outside the documentation folder with internal placeholder files or direct GitHub URLs. There is no change to any firmware, software, or cryptographic code, and no security impact.
AI review queuedchore(python): bump bleak dependency to 3.0.2by Martin Milata · 914426d9 · Aug 4, 2026 · 3 filesMessage 57 · ThinInformational 16Details
Commit message · Martin Milata
chore(python): bump bleak dependency to 3.0.2
[no changelog]
57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
second-pass: broader security terminology
AI analysis · Informational 16/100
This is a routine dependency update for the Python Bluetooth library used by Trezor's developer tooling. It bumps the required version of 'bleak' from 1.1.0 to 3.0.2 and, in some optional install paths, excludes Windows and older Python versions. There is no indication in the commit that this fixes a security vulnerability, and no security advisory was supplied.
AI review queuedrefactor(core/ethereum): simplify `sign_tx()` digest flowby Roman Zeyde · e07499da · Aug 4, 2026 · 1 fileMessage 85 · StrongInformational 12Details
De-duplicate RLP `fields` definition and better encapsulate RLP length and digest computation - see `_start_digest` and `_finish_digest`.
[no changelog]
85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 12/100
This commit is a straightforward internal code cleanup in the Ethereum transaction signing module. It moves existing digest-calculation logic into two new helper functions, _start_digest() and _finish_digest(), without changing what data is hashed or how the transaction is signed. There is no indication of a security fix or behavior change.
AI review queuedrefactor(core/ethereum): simplify `sign_tx_eip1559()` digest flowby Roman Zeyde · 3d2b70cf · Aug 3, 2026 · 1 fileMessage 85 · StrongInformational 12Details
De-duplicate RLP `fields` definition and better encapsulate RLP length and digest computation - see `_start_digest` and `_finish_digest`.
[no changelog]
85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 12/100
This commit is a code cleanup (refactor) for how Trezor's Ethereum app builds the transaction hash for EIP-1559 transactions. It moves the existing hashing steps into two helper functions and removes a duplicated list of transaction fields. There is no change to what data is signed or how it is signed, and no security bug is introduced or fixed.
AI review queuedrefactor(core/rust): update obj_type! for slots-based mp_obj_type_tby Martin Milata · aba19a5a · Aug 3, 2026 · 15 filesMessage 85 · StrongInformational 19Details
Commit message · Martin Milata
refactor(core/rust): update obj_type! for slots-based mp_obj_type_t
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Why it was queued
parser or protocol pathsecond-pass: security-sensitive path
AI analysis · Informational 19/100
This is a routine internal refactoring in the Trezor firmware's Rust code. It updates how Rust code builds MicroPython object type definitions to match a newer version of MicroPython that stores type information in a 'slots' array rather than a flat structure. There is no user-facing feature change and no indication of a security fix.
AI review queuedrefactor(core): inline `data_length` into `_get_digest_length()`by Roman Zeyde · df4447c9 · Aug 3, 2026 · 1 fileMessage 62 · AdequateInformational 15Details
Commit message · Roman Zeyde
refactor(core): inline `data_length` into `_get_digest_length()`
[no changelog]
62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This is a tiny code cleanup in the Ethereum transaction signing code. It moves where a variable is defined without changing what the code actually does. There is no security issue visible in the change.
AI review queuedrefactor(core): simplify ETH access list RLP encodingby Roman Zeyde · 2d23449f · Aug 3, 2026 · 1 fileMessage 93 · StrongInformational 12Details
Commit message · Roman Zeyde
refactor(core): simplify ETH access list RLP encoding
`rlp.length()` and `rlp.write()` support handling a list of `RLPItem`s.
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 12/100
This commit is a small internal cleanup of how Ethereum transaction 'access lists' are formatted for RLP encoding in the Trezor firmware. It replaces a hand-rolled length calculation and manual header writing with higher-level helper functions that do the same job. There is no user-visible behavior change and no indication of a security fix.
AI review queuedchore(core): sign translationsby Martin Milata · 38b528f2 · Aug 3, 2026 · 1 fileMessage 62 · AdequateInformational 18Details
Commit message · Martin Milata
chore(core): sign translations
[no changelog]
(cherry picked from commit 4c4870262b85c04ba235602ba49307015118c3f5)
62/100 · AdequateMessage clarity
✓ Descriptive subject✓ Uses a recognizable type or scope✓ Provides an explanatory body
Why it was queued
signing or wallet pathtranslation-only discountsecond-pass: security-sensitive path
AI analysis · Informational 18/100
This commit adds a new cryptographic signature entry to a JSON file that records approved translation bundles for the Trezor hardware wallet. It does not change any executable code, fix a bug, or alter security logic. The signature appears to be a routine administrative update authorizing a new set of translated strings for firmware version 2.12.4.0.
fix(nordic): select correct hash algorithm for fw validation
[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 41/100
This commit fixes the firmware build scripts for Trezor's Nordic Bluetooth chip variant so the correct cryptographic hash algorithm (SHA-256) is used when validating firmware images. Previously, the nRF54L-based boards could end up using SHA-512 for the image hash, which would not match the hash algorithm expected by the rest of the Trezor firmware validation chain. That mismatch could prevent the device from accepting legitimate firmware updates or, in a worst-case scenario, create a security inconsistency in how firmware authenticity is checked. The fix moves a hash-algorithm override into a board-specific configuration file and explicitly enables SHA-256 in the bootloader configuration.