TZ
← All projectsTrezor

Trezor firmware

Firmware monorepo for Trezor One, Model T, and Safe devices.

BitcoinHardware walletsNormal
Repository coverage

3768 commits in the local evidence base

Every captured commit receives deterministic security triage and a separate communication-quality score. Security candidates and broader second-pass signals receive full-patch Ollama analysis.

1328security candidates435second-pass queue3191AI analyses
201commits · 30 days
450commits · 60 days
1759commits · 180 days
2832commits · 365 days
Backfill bands
Aug 5 → Feb 61298 seen115 candidatesComplete
Feb 6 → Jun 6775 seen58 candidatesComplete
Jun 6 → Jul 6217 seen13 candidatesComplete
Jul 6 → Aug 5360 seen54 candidatesComplete
Commit communication

Does the history explain itself?

Message quality measures whether a commit identifies its scope, purpose, rationale, testing, and supporting references. It does not change the security-severity score.

68/100 average clarity
841Strong · 80–100
1731Adequate · 60–79
1189Thin · 40–59
7Opaque · 0–39
1security candidate with opaque commit messaging
Read the scoring rubric →
Developer activity

Who is changing the project?

Public Git author strings; identities are not independently verified.

DeveloperCommitsCandidatesAnalyzedHigh riskMessage avg.
tychovrahe394164355667
Jakub Janků1023067681
Roman Zeyde721230639372
obrusvit333135281364
cepetr301111228259
PrisionMike153101149271
Andrew Kozlik893885267
Petr Susil1159286
Martin Pastyřík291025175
M1nd3r292106248071
Ioan Bizău23076230059
Lukas Bielesch1067592066
Analysis record

Published AI watches

Last scanned 45 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-priorityfix(core/embed): reject optiga metadata item longer than 255 bytesby Ondřej Vejpustek · 89c98f6a · Oct 21, 2026 · 1 fileMessage 97 · StrongTriage 0Details
Commit message · Ondřej Vejpustek

fix(core/embed): reject optiga metadata item longer than 255 bytes

The item length is stored in a single byte, but `optiga_metadata_item`
holds a `uint16_t`, so `optiga_serialize_metadata()` truncated the
length byte of an oversized item. This was unobservable, because a
single such item always trips the final payload length check, but the
length byte should not rely on a check that far away.

[no changelog]

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
Lower-prioritychore(python): update typing syntax in `emulator.py`by M1nd3r · cf6cef42 · Oct 21, 2026 · 1 fileMessage 62 · AdequateTriage 0Details
Commit message · M1nd3r

chore(python): update typing syntax in `emulator.py`

[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-priorityfeat(core): add language to the app headerby Lukas Bielesch · 1b822e37 · Oct 21, 2026 · 1 fileMessage 57 · ThinTriage 0Details
Commit message · Lukas Bielesch

feat(core): add language to the app header

[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-prioritychore(core): update fixturesby Michal Kazda · 64dfbebe · Oct 21, 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
Lower-priorityfix(core): carry the screen-recording refresh index as uint32_t [no changelog]by tychovrahe · 821b08da · Oct 21, 2026 · 2 filesMessage 85 · StrongTriage 0Details
Commit message · tychovrahe

fix(core): carry the screen-recording refresh index as uint32_t [no changelog]

DebugLinkRecordScreen.refresh_index is a uint32 on the wire; the
recording API took an int and printed it signed, so a value at or
above 2^31 would have produced a negative file prefix.

Co-Authored-By: Claude Fable 5.1 <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
Security candidaterefactor(core/bootloader): commit the firmware version separately from checking it [no changelog]by tychovrahe · 81fe6aec · Oct 21, 2026 · 3 filesMessage 95 · StrongModerate 63Details
Commit message · tychovrahe

refactor(core/bootloader): commit the firmware version separately from checking it [no changelog]

fw_check() committed the header's monotonic version to the rollback
counter as a side effect, before it verified the image contents. Every
status query that called it wrote to the device: GetFeatures over the
wire, and now the debug link too, which is serviced during an upload
when the image in flash is half-written.

fw_check() is read-only now and reports version_trusted and monotonic
in its result; the boot path commits them through fw_commit_min_version()
right after the check, under the same condition and at the same point
as before. The pre-jump re-verification keeps its own commit. The update
flow never committed, so after an install the version is committed by
the reboot that follows, as it always was when the host sent no
GetFeatures in between.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

95/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
update trustdefensive validationboot or update path
AI analysis · Moderate 63/100

This bootloader change fixes a side effect where simply asking the device for its status could permanently change a security counter on the device. Before, a routine called fw_check() both inspected the firmware and updated the rollback counter. Now the inspection is read-only, and the actual update is done only at deliberate points such as booting. This prevents a half-written firmware update or a status query from locking the device to a version before the firmware is fully verified and installed.

Security candidatefeat(core): start apps via coreapp_app_entry()by Lukas Bielesch · 37d70ad8 · Oct 21, 2026 · 8 filesMessage 57 · ThinLow 27Details
Commit message · Lukas Bielesch

feat(core): start apps via coreapp_app_entry()

[no changelog]

57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
boot or update path
AI analysis · Low 27/100

This commit changes how apps are launched on Trezor hardware wallets. Instead of jumping directly into an app's main function, the firmware now first runs a small Core-provided entry point that sets up the app's memory allocator and then calls the app's main function. This is a structural improvement that lets Core control more of the app's startup environment, but the commit itself does not fix a known bug or vulnerability.

Lower-priorityrefactor(core): drop the APP_GET_HEAP syscallby Lukas Bielesch · 1c45b625 · Oct 21, 2026 · 13 filesMessage 57 · ThinTriage 0Details
Commit message · Lukas Bielesch

refactor(core): drop the APP_GET_HEAP syscall

[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-priorityfeat(core): add IPC inbox size to the app headerby Lukas Bielesch · 2e13bf16 · Oct 21, 2026 · 4 filesMessage 57 · ThinTriage 0Details
Commit message · Lukas Bielesch

feat(core): add IPC inbox size to the app header

[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-priorityfeat(core): systask_push_data() for the emulatorby Lukas Bielesch · e288ade9 · Oct 21, 2026 · 2 filesMessage 57 · ThinTriage 0Details
Commit message · Lukas Bielesch

feat(core): systask_push_data() for the emulator

[no changelog]

57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Security candidatetest(core): test chacha20poly1305 state machineby Andrew Kozlik · 40e4bdb3 · Oct 21, 2026 · 1 fileMessage 82 · StrongInformational 12Details
Commit message · Andrew Kozlik

test(core): test chacha20poly1305 state machine

[no changelog]

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

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

This commit only adds new automated tests for the ChaCha20-Poly1305 encryption helper in Trezor's firmware. It checks that the code correctly rejects wrong key lengths, wrong nonce lengths, and invalid calling sequences (for example, calling auth twice or feeding data after the stream has finished). There are no changes to the actual encryption implementation, so this commit does not introduce or fix a security vulnerability by itself.

Security candidatefeat(core): reject chacha20poly1305 data after a partial blockby Andrew Kozlik · 06a69589 · Oct 21, 2026 · 1 fileMessage 85 · StrongLow 40Details
Commit message · Andrew Kozlik

feat(core): reject chacha20poly1305 data after a partial block

Add a LAST state to the ChaCha20Poly1305 context, which is set by encrypt()
and decrypt() when the input is a partial block. Any further calls to
encrypt() or decrypt() raise RuntimeError in the LAST state.

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

This commit tightens the rules for a cryptographic helper (ChaCha20-Poly1305) inside Trezor hardware wallets. Previously, after you fed it a partial block of data, you could keep calling encrypt/decrypt with more data. Now the code enters a 'LAST' state after any partial block and refuses further encrypt/decrypt calls, only allowing the final finish call. This is a defensive correctness fix that prevents misuse of the cipher's streaming API, which could otherwise lead to nonce reuse or authentication failures. There is no claim in the commit that an actual exploit exists, and no CVE or vendor security advisory is supplied.

Security candidatechore: expose chacha20poly1305 size constantsby Andrew Kozlik · 34fde603 · Oct 20, 2026 · 9 filesMessage 57 · ThinInformational 15Details
Commit message · Andrew Kozlik

chore: expose chacha20poly1305 size constants

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

This commit is a routine code cleanup: it replaces hard-coded numbers like 32, 12, 64, and 16 with named constants for the ChaCha20-Poly1305 encryption algorithm. The behavior of the code does not change; it only becomes easier to read and maintain. There is no security vulnerability being fixed here.

Security candidatefeat(trezorlib): run a bootloader firmware update in the background [no changelog]by tychovrahe · b3af0805 · Oct 20, 2026 · 1 fileMessage 95 · StrongInformational 15Details
Commit message · tychovrahe

feat(trezorlib): run a bootloader firmware update in the background [no changelog]

An update onto installed firmware waits for an on-screen confirmation,
so it has to run beside the test that confirms it.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

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

This commit is a small internal test-utility change. It adds a configurable timeout and a background-thread helper to the Python test library that emulates a Trezor bootloader during firmware updates. There is no indication it fixes a security bug or introduces a vulnerability; it appears to be a test-infrastructure convenience feature.

Security candidatefeat(trezorlib): add stop_and_connect boot args [no changelog]by tychovrahe · 802bc25d · Oct 20, 2026 · 1 fileMessage 85 · StrongInformational 15Details
Commit message · tychovrahe

feat(trezorlib): add stop_and_connect boot args [no changelog]

STOP_AND_CONNECT lands the bootloader on the host-waiting screen, the
one that polls the wire.

Co-Authored-By: Claude Fable 5.1 <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
update trust
AI analysis · Informational 15/100

This commit simply adds a new named option in the Trezor Python library that tells a Trezor bootloader to stop at the 'wait for host' screen. There is no bug, no vulnerability, and no security fix visible in the change.

Lower-prioritychore(core/prodtest): adjust prodtest to use modified noise_xxpsk3 apiby M1nd3r · 1fd1bf2f · Oct 20, 2026 · 1 fileMessage 62 · AdequateTriage 0Details
Commit message · M1nd3r

chore(core/prodtest): adjust prodtest to use modified noise_xxpsk3 api

[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
Security candidatechore(crypto): adjust noise_xxpsk3 apiby M1nd3r · c04409e9 · Oct 20, 2026 · 3 filesMessage 72 · AdequateLow 29Details
Commit message · M1nd3r

chore(crypto): adjust noise_xxpsk3 api

- Remove static_private_key from handshake state. Pass it as a parameter where needed instead.

[no changelog]

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

This commit changes how a secure-handshake library (used to set up encrypted connections) stores sensitive keys. Previously, the long-term private key, public key, and pre-shared key were copied into a handshake state structure at initialization and kept there for the whole handshake. Now they are passed only to the specific functions that actually need them. This reduces the window during which those secrets sit in memory inside the handshake object, which is a defensive hardening improvement rather than a fix for an active bug. There is no claim by the vendor that this resolves a reported security vulnerability.

Security candidatetest(core): record bootloader UI fixtures for the install tests [no changelog]by tychovrahe · 596afe0a · Oct 20, 2026 · 1 fileMessage 87 · StrongInformational 15Details
Commit message · tychovrahe

test(core): record bootloader UI fixtures for the install tests [no changelog]

T2T1, T3B1, T3T1 and T3W1.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

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

This commit only adds pre-recorded test snapshots (called 'fixtures') for bootloader firmware-install tests on four Trezor device models. It does not change any executable code, security logic, or user-facing behavior. There is no security issue.

Security candidatetest(core): add bootloader firmware install tests [no changelog]by tychovrahe · c392ec65 · Oct 20, 2026 · 3 filesMessage 95 · StrongInformational 15Details
Commit message · tychovrahe

test(core): add bootloader firmware install tests [no changelog]

Install of a trusted image on an empty device (no confirmation, reboot,
storage erased), upgrade of installed firmware (confirmation, reboot,
seed kept) and boot with the image preloaded (jump, command cleared,
storage retained). The confirm helper is shared with the wipe test;
on Caesar a confirmation with an info page confirms with both buttons.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

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

This commit only adds and reorganizes automated test code for the Trezor bootloader. It does not change any firmware, bootloader, or production code. The new tests verify normal, expected behavior: installing firmware on an empty device, upgrading existing firmware with user confirmation, and booting preloaded firmware. There is no security-relevant code change here.

Security candidatefeat(trezorlib): accept a bootloader run that ends before the debug link answers [no changelog]by tychovrahe · a5fd7788 · Oct 20, 2026 · 1 fileMessage 85 · StrongInformational 15Details
Commit message · tychovrahe

feat(trezorlib): accept a bootloader run that ends before the debug link answers [no changelog]

A boot into trusted firmware takes the bootloader no time at all, so the
process can be gone before the readiness probe gets an answer. That is
an outcome, not an error: start() returns without a context and
wait_exit() reports it.

Co-Authored-By: Claude Fable 5.1 <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
update trustboot or update path
AI analysis · Informational 15/100

This commit changes an internal test helper in Trezor's Python library so that when a simulated bootloader finishes very quickly (because it immediately boots into trusted firmware), the test code treats that as a normal result instead of throwing an error. It is a testing/QA reliability fix, not a security patch for user-facing code.

Security candidatetest(core): synthesize dev-key signed firmware images for the bootloader tests [no changelog]by tychovrahe · ac1e2c39 · Oct 20, 2026 · 3 filesMessage 95 · StrongInformational 19Details
Commit message · tychovrahe

test(core): synthesize dev-key signed firmware images for the bootloader tests [no changelog]

make_firmware() builds an image from a checked-in dev vendor header, a
firmware header with the requested version and model, and filler code,
rehashed and signed the way headertool does it. On secmon models a signed
TSEC image is embedded at the aligned offset. The runner fills the model
specifics in from the emulator's -p output.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

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

This commit adds test-only code that creates fake Trezor firmware images signed with the project's public development keys. The images are used only in automated bootloader tests and never contain real firmware code. It does not change any production bootloader, firmware, or signing process, and it does not introduce a vulnerability in shipped devices.

Security candidatefeat(core/bootloader_emu): report secmon verification and code alignment with -p [no changelog]by tychovrahe · b0450b54 · Oct 20, 2026 · 1 fileMessage 95 · StrongInformational 15Details
Commit message · tychovrahe

feat(core/bootloader_emu): report secmon verification and code alignment with -p [no changelog]

A test harness building firmware images for the emulator needs to know
whether the bootloader expects a secure monitor inside the image and at
which alignment it looks for it.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

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

This commit adds diagnostic output to the Trezor bootloader emulator. When run with a special flag, it now prints two extra pieces of information: whether the bootloader expects a 'secure monitor' component in firmware images, and what memory alignment it requires for firmware code. This is purely a testing/debugging convenience for the emulator and does not change how real devices verify or load firmware.

Security candidatetest(core): add bootloader emulator tests [no changelog]by tychovrahe · 8661109f · Oct 20, 2026 · 8 filesMessage 95 · StrongInformational 15Details
Commit message · tychovrahe

test(core): add bootloader emulator tests [no changelog]

A suite with one emulator run per test, recorded from the first frame
when UI fixtures are on, and a first test: a host wipe of an empty
device, confirmed on screen, checked through the exit record.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

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

This commit only adds new automated test code for the Trezor bootloader emulator. It introduces a test suite, supporting fixtures, documentation, and Makefile targets to run bootloader tests. There is no change to firmware, bootloader, or production code, and no security fix or vulnerability is present in the diff.

Security candidatetest(core): record bootloader UI fixtures [no changelog]by tychovrahe · caafb3dd · Oct 20, 2026 · 1 fileMessage 87 · StrongInformational 15Details
Commit message · tychovrahe

test(core): record bootloader UI fixtures [no changelog]

T2T1, T3B1, T3T1 and T3W1.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

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

This commit only adds new test fixture hashes to a JSON file used for automated UI testing of the bootloader. It records expected screen outputs for a device-wipe test on four Trezor models. There are no code changes, no user-facing behavior changes, and no security fix or vulnerability present.

Security candidateci: run the bootloader emulator tests [no changelog]by tychovrahe · 4c64bb7b · Oct 20, 2026 · 3 filesMessage 95 · StrongInformational 15Details
Commit message · tychovrahe

ci: run the bootloader emulator tests [no changelog]

The job builds its own emulator with the development keys and
debuglink, runs the suite with UI fixtures and reports through the
ui-report action. The PR comment and the fixture updater know the job.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

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

This commit adds a new automated test job to the project's continuous integration (CI) pipeline. It builds and runs bootloader emulator tests for several Trezor hardware wallet models and updates helper scripts so the new test job is included in pull-request reports and fixture updates. There is no change to the firmware code that runs on user devices, no fix for a vulnerability, and no security-relevant behavior change.