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

Lower-priorityci: fix download-emulators.sh after switching to flakesby Martin Milata · e5bc3693 · Oct 29, 2026 · 1 fileMessage 62 · AdequateTriage 0Details
Commit message · Martin Milata

ci: fix download-emulators.sh after switching to flakes

62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Lower-prioritychore: update UI fixturesby Roman Zeyde · e1eb1d7e · Oct 29, 2026 · 1 fileMessage 62 · AdequateTriage 0Details
Commit message · Roman Zeyde

chore: update UI fixtures

[no changelog]

(cherry picked from commit 89388f6e0008b2b178799644f70f2ae5bd5b624c)

62/100 · AdequateMessage clarity
✓ Descriptive subject✓ Uses a recognizable type or scope✓ Provides an explanatory body
Lower-prioritychore(core): update fixtures.jsonby obrusvit · ad4ba137 · Oct 28, 2026 · 1 fileMessage 57 · ThinTriage 0Details
Commit message · obrusvit

chore(core): update fixtures.json

[no changelog]

57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Lower-priorityci: reproducible build of nRF firmwareby Martin Milata · f158cb46 · Oct 28, 2026 · 1 fileMessage 57 · ThinTriage 0Details
Commit message · Martin Milata

ci: reproducible build of nRF firmware

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
documentation-only discount
Lower-priorityfix(build-docker): fix broken nRF buildby Martin Milata · f60eb23f · Oct 28, 2026 · 2 filesMessage 57 · ThinTriage 0Details
Commit message · Martin Milata

fix(build-docker): fix broken nRF build

57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Lower-priorityfix(build-docker): avoid root-owned output dirsby Martin Milata · 81edbaa7 · Oct 28, 2026 · 1 fileMessage 57 · ThinTriage 0Details
Commit message · Martin Milata

fix(build-docker): avoid root-owned output dirs

57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Lower-priorityfix(build-docker): flake.nix supportby Martin Milata · a2313f51 · Oct 28, 2026 · 3 filesMessage 57 · ThinTriage 0Details
Commit message · Martin Milata

fix(build-docker): flake.nix support

57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
AI review queuedfix(core/caesar): make CS prompt fit on 1 screenby obrusvit · 0a400887 · Oct 28, 2026 · 3 filesMessage 57 · ThinInformational 15Details
Commit message · obrusvit

fix(core/caesar): make CS prompt fit on 1 screen

[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 removes a stray line-break from a Czech translation string so that a 'new wallet created' message fits on a single screen of the Trezor Safe 3 (Caesar) device. It is a cosmetic UI/layout fix with no security relevance.

Lower-prioritychore(core): update fixtures.jsonby obrusvit · de8badca · Oct 28, 2026 · 1 fileMessage 72 · AdequateTriage 0Details
Commit message · obrusvit

chore(core): update fixtures.json

- all fixtures related to the Caesar menu navigation

72/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body
Lower-priorityfix(python): improve BLE error handlingby Martin Milata · f05a23d2 · Oct 27, 2026 · 1 fileMessage 80 · StrongTriage 0Details
Commit message · Martin Milata

fix(python): improve BLE error handling

* don't send arbitrary exceptions over pipe as they may be mangled or
fail to pickle
* keep device in the connected list if it fails to pair or subscribe
notifications
* do not unsubscribe notifications before disconnect as it can raise
exception and is done automatically anyway

[no changelog]

80/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Lower-priorityfix(python): improve BLE process lifecycleby Martin Milata · f7349204 · Oct 27, 2026 · 1 fileMessage 92 · StrongTriage 0Details
Commit message · Martin Milata

fix(python): improve BLE process lifecycle

Use multiprocessing forkserver method to prevent the child process from
inheriting both sides of the pipe, which makes it impossible to detect
parent disconnection.

[no changelog]

92/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Explains rationale or failure mode
Lower-priorityfix(python): fix BLE peripheral-side disconnectionby Martin Milata · d6d23d7a · Oct 27, 2026 · 1 fileMessage 62 · AdequateTriage 0Details
Commit message · Martin Milata

fix(python): fix BLE peripheral-side disconnection

[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
Lower-prioritychore(core): update fixturesby Michal Kazda · 43941929 · Oct 27, 2026 · 1 fileMessage 47 · ThinTriage 0Details
Commit message · Michal Kazda

chore(core): update fixtures
[no changelog]

47/100 · ThinMessage clarity
✓ Descriptive subject✓ Uses a recognizable type or scope! No meaningful explanatory body
Security candidateci: hw: check-usb-permissions: add lspci outputby Martin Milata · 05422a3e · Oct 27, 2026 · 2 filesMessage 57 · ThinInformational 15Details
Commit message · Martin Milata

ci: hw: check-usb-permissions: add lspci output

[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
credential or privilege state
AI analysis · Informational 15/100

This commit adds extra diagnostic commands to a hardware CI test script. It collects more information about USB ports and PCI devices when a Trezor hardware test fails, to help engineers debug permission or connectivity issues. There is no change to the firmware, wallet logic, cryptography, or any user-facing security behavior.

AI review queuedfix(tools): make changelog.py ignore dirsby M1nd3r · dba808db · Oct 27, 2026 · 1 fileMessage 72 · AdequateInformational 15Details
Commit message · M1nd3r

fix(tools): make changelog.py ignore dirs

- Previously, having a subdir in one of `.changelog.d/` made the `changelog_check` crash.

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

This is a minor developer tooling fix. The changelog-checking script previously crashed if someone accidentally created a subdirectory inside a hidden changelog folder. The patch simply skips directories and only looks at files. It has no security relevance for users of the Trezor device or wallet software.

Security candidatechore(python): tighten device authenticity checksby M1nd3r · 21732fc2 · Oct 27, 2026 · 2 filesMessage 57 · ThinLow 43Details
Commit message · M1nd3r

chore(python): tighten device authenticity checks

[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
authentication path
AI analysis · Low 43/100

This commit tightens how the Trezor Python library checks whether a connected hardware wallet is genuine. It adds stricter rules: certificates must now include a device model name, revoked and allowed keys cannot be mixed, signature types must match the chip that produced them, and older firmware that lacks new MCU-style proof support is rejected with a clear error. These are defensive hardening changes rather than a fix for a known active attack.

Lower-prioritychore(core): update fixtures.jsonby obrusvit · 8df6163c · Oct 27, 2026 · 1 fileMessage 57 · ThinTriage 0Details
Commit message · obrusvit

chore(core): update fixtures.json

[no changelog]

57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
AI review queuedfix(translations): fix failing tests in CS and updates to DE ES FR PTby Michal Kazda · 8f2a9bcc · Oct 27, 2026 · 6 filesMessage 72 · AdequateInformational 15Details
Commit message · Michal Kazda

fix(translations): fix failing tests in CS and updates to DE ES FR PT
[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 pathtranslation-only discountsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit updates translation text files for Czech, German, Spanish, French, and Portuguese. It fixes wording inconsistencies and updates a signature file that records which translation version is current. There is no code change and no security relevance.

Security candidatefix(core/caesar): use Marquee in HS notifby obrusvit · b3fb1bde · Oct 27, 2026 · 2 filesMessage 57 · ThinInformational 18Details
Commit message · obrusvit

fix(core/caesar): use Marquee in HS notif

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

This is a user-interface polish change for the Trezor hardware wallet's Caesar homescreen layout. It makes long notification messages scroll smoothly using a 'Marquee' component instead of being cut off or overlapping warning icons. There is no security-relevant behavior change; it is purely about how text is displayed on screen.

AI review queuedchore(translations): sync Crowdin translationsby Thalarion · e5d5b4a2 · Oct 27, 2026 · 7 filesMessage 57 · ThinInformational 15Details
Commit message · Thalarion

chore(translations): sync Crowdin translations

[no changelog]

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

This commit is a routine synchronization of translated user-interface text strings from the Crowdin translation platform. It only changes wording in Czech, German, Spanish, French, Indonesian, and Portuguese translation files, plus the corresponding translation signature metadata. There is no code, logic, or security behavior change.

Lower-prioritychore(core): update fixturesby Michal Kazda · a81805fb · Oct 27, 2026 · 1 fileMessage 47 · ThinTriage 0Details
Commit message · Michal Kazda

chore(core): update fixtures
[no changelog]

47/100 · ThinMessage clarity
✓ Descriptive subject✓ Uses a recognizable type or scope! No meaningful explanatory body
Security candidatechore(python): add root debug keys for T3W1 authenticationby M1nd3r · f9f28143 · Oct 27, 2026 · 1 fileMessage 67 · AdequateInformational 18Details
Commit message · M1nd3r

chore(python): add root debug keys for T3W1 authentication

[no changelog]

67/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Names security-relevant behavior explicitly! No meaningful explanatory body
Why it was queued
access controlauthentication path
AI analysis · Informational 18/100

This commit adds two extra public debug root keys (Ed25519 and ML-DSA-44) to the Python trezorlib library so it can authenticate the upcoming T3W1 hardware variant during development. Debug keys are already public, non-production trust anchors; adding more of them is a routine key-list update and does not by itself create a vulnerability.

Security candidaterefactor(python): use ML-DSA-44 OID from cryptographyby M1nd3r · 2f97f951 · Oct 27, 2026 · 1 fileMessage 93 · StrongInformational 15Details
Commit message · M1nd3r

refactor(python): use ML-DSA-44 OID from cryptography

- `SignatureAlgorithmOID.ML_DSA_44` is available since cryptography v49.0.0, introduced in https://github.com/pyca/cryptography/pull/14884.

[no changelog]

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

This is a minor code cleanup in the Python Trezor library. It replaces a hard-coded identifier for the ML-DSA-44 signature algorithm with the official constant provided by the cryptography library. There is no security bug being fixed and no change in behavior for users.

Security candidatefix(core): flash F4 firmware parts to their own addressesby tychovrahe · 5718d0aa · Oct 27, 2026 · 5 filesMessage 85 · StrongModerate 57Details
Commit message · tychovrahe

fix(core): flash F4 firmware parts to their own addresses

- split the F4 firmware upload image into part 1 and part 2 when
flashing or combining, part 2 belongs at FIRMWARE_P2_START
- writing it in one piece put part 2 over the secret sector
- fix the misleading split_pad_to comment

[no changelog]

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

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

This commit fixes a bug in Trezor's internal firmware flashing tools. Previously, when flashing or combining firmware for STM32F4-based devices, the second half of the firmware image was written to the wrong flash address (0x08100000) and could overwrite the 'secret sector'—a protected area that holds sensitive device secrets. The fix splits the firmware image into two parts and writes part 2 to its correct address (0x08120000). The bug is in developer/flash tooling, not in the device firmware itself, so ordinary users are not directly affected unless they use these internal tools.

Lower-priorityfix(core/bolt): two-line HS notificationby obrusvit · 847c103b · Oct 27, 2026 · 1 fileMessage 57 · ThinTriage 0Details
Commit message · obrusvit

fix(core/bolt): two-line HS notification

[no changelog]

57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body