TZ
← All projectsTrezor

Trezor firmware

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

BitcoinHardware walletsNormal
Repository coverage

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

916security candidates311second-pass queue1301AI analyses
339commits · 30 days
583commits · 60 days
1358commits · 180 days
2650commits · 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.

66/100 average clarity
473Strong · 80–100
1318Adequate · 60–79
860Thin · 40–59
5Opaque · 0–39
Read the scoring rubric →
Developer activity

Who is changing the project?

Public Git author strings; identities are not independently verified.

DeveloperCommitsCandidatesAnalyzedHigh riskMessage avg.
PrisionMike945978273
Andrew Kozlik712432265
Roman Zeyde571177251171
tychovrahe292104121161
Jakub Janků19915184
Martin Pastyřík23810173
cepetr19682102059
Ioan Bizău23076140059
obrusvit21376106064
M1nd3r2067194071
Lukas Bielesch846771067
Martin Milata1744670063
Analysis record

Published AI watches

Last scanned 32 minutes ago

Informational 18 AI analysisMessage 57 · Thin
TZ TrezorTrezor firmware BitcoinHardware wallets

chore(core): remove sha1 from regular FW

This commit removes the SHA-1 hashing function from the regular Trezor firmware. SHA-1 is an old, weak hash algorithm that is no longer considered secure for sensitive uses. The change deletes the code that exposes SHA-1 to apps running on…

Removal of a deprecated cryptographic primitive (SHA-1) from the firmware API surfaceReduction of attack surface and prevention of future misuse of a collision-vulnerable hashNo direct vulnerability patch or memory-safety bug is present in the diff
16d15774by M1nd3r+0−2006 files
No security note in commit
Low 27 AI analysisMessage 62 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

refactor(crypto): pass static public key to `noise_xxpsk3_*_init()`

This commit changes how a cryptographic library sets up secure connections. Previously, the code automatically calculated the public key from the private key. Now, the caller must provide the public key directly. This is a code-quality ref…

Cryptographic key handling changed: public key is now supplied rather than derivedPotential reduction of key-mismatch risk if caller provides correct public keyNew null-pointer check added for static_public_key
1b3128a4by Ondřej Vejpustek+20−92 files
No security note in commit
Informational 15 AI analysisMessage 57 · Thin
TZ TrezorTrezor firmware BitcoinHardware wallets

refactor(crypto): change order of parameters

This commit simply reorders the arguments of an internal function called dh() and updates every place that calls it. The actual math and security behavior are unchanged; it is a code cleanup with no security effect.

33a119eeby Ondřej Vejpustek+15−151 file
No security note in commit
Informational 15 AI analysisMessage 47 · Thin
TZ TrezorTrezor firmware BitcoinHardware wallets

refactor(crypto): prefix enums

This commit simply renames two groups of internal status labels (called enums) in the Trezor firmware's cryptographic code. The old names like WAITING_FOR_REQUEST1 were shared between two different parts of the code, so the developer gave …

f1c74046by Ondřej Vejpustek+26−222 files
No security note in commit
Low 37 AI analysisMessage 57 · Thin
TZ TrezorTrezor firmware BitcoinHardware wallets

fix(crypto): prevent calling `memzero(NULL, ...)`

This commit fixes three places in the Trezor firmware's cryptographic code where a memory-clearing function could be called with a NULL pointer. In practice, passing NULL to memzero is harmless on Trezor's platform (it does nothing), but i…

NULL pointer passed to memory-zeroing helper in cryptographic codeUndefined behavior in C standard library contractDefensive hardening in Noise protocol implementation
0394e934by Ondřej Vejpustek+11−51 file
No security note in commit
Informational 18 AI analysisMessage 62 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

refactor(crypto): return remote static key from `noise_xxpsk3_*_handle_*()`

This commit is a code cleanup (refactor) for the cryptographic handshake code used in Trezor devices. It changes how the other party's long-term public key is returned to the caller: instead of storing it inside an internal state structure…

Removal of long-term public key storage from internal handshake stateCaller-supplied output buffer for remote static public key reduces internal secret retentionError-path memzero of returned key material on failure
3ead1aa6by Ondřej Vejpustek+79−423 files
No security note in commit
Informational 15 AI analysisMessage 62 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

refactor(xtask): rename ProjectProfile to ProjectConfig

This commit is a simple rename from 'ProjectProfile' to 'ProjectConfig' in two Rust source files. It only changes variable names, struct names, and error messages. There is no change to program logic, security behavior, or how data is hand…

581b37bcby cepetr+18−182 files
No security note in commit
Informational 15 AI analysisMessage 47 · Thin
TZ TrezorTrezor firmware BitcoinHardware wallets

refactor(xtask): introduce ResolvedBuildArgs

This commit is a straightforward internal code refactor in Trezor's build tooling. It introduces a new ResolvedBuildArgs structure that centralizes default values for command-line build options before they are used. There is no change to u…

c24d1be8by cepetr+99−295 files
No security note in commit
Informational 15 AI analysisMessage 57 · Thin
TZ TrezorTrezor firmware BitcoinHardware wallets

refactor(xtask): make build args tristate

This commit is a straightforward internal refactor of the Trezor firmware build tool's command-line argument handling. It changes many on/off flags from plain booleans to optional booleans so they can explicitly be set to true, false, or l…

271e249aby cepetr+57−561 file
No security note in commit
Informational 15 AI analysisMessage 57 · Thin
TZ TrezorTrezor firmware BitcoinHardware wallets

refactor(xtask): introduce build options

This commit is a straightforward internal code reorganization in Trezor's build tooling. It moves build-option definitions from one Rust source file to a new module and adds the ability to load those options from a configuration file. Ther…

75085e2aby cepetr+275−2007 files
No security note in commit
Informational 15 AI analysisMessage 57 · Thin
TZ TrezorTrezor firmware BitcoinHardware wallets

feat(xtask): introduce build presets

This commit is a developer tooling change for the Trezor firmware build system. It introduces 'build presets'—named configuration bundles stored in TOML files—so developers can select common build settings with a single command-line flag i…

eefe8f7fby cepetr+397−419 files
No security note in commit
Informational 15 AI analysisMessage 62 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

feat(xtask): upgrade manifest.yaml for tf-tools 0.3.0

This commit is a routine update to a build-system manifest file used by Trezor's internal tooling. It reorganizes and re-labels feature flags (for example, moving options between 'Features', 'Debugging', and 'Signing' groups and simplifyin…

57b28b89by cepetr+86−1351 file
No security note in commit
Informational 15 AI analysisMessage 62 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

feat(core): add tf-tools 0.3.1+ configuration file

This commit adds a single configuration file for a Trezor developer tool (a VS Code extension). It only points the tool to existing folders in the repository and contains no executable code, no secrets, and no changes to firmware behavior.…

e554f618by cepetr+8−01 file
No security note in commit
Informational 15 AI analysisMessage 62 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

refactor(xtask): rename ResolvedBuild to ResolvedBuildFeatures

This commit is a simple internal code cleanup: it renames a Rust data structure called ResolvedBuild to ResolvedBuildFeatures and updates the places that use it. There are no functional changes, no security fixes, and no changes to how the…

aaa2780bby cepetr+5−52 files
No security note in commit
Informational 15 AI analysisMessage 57 · Thin
TZ TrezorTrezor firmware BitcoinHardware wallets

fix(core): fix up clippy warnings in storage.rs

This is a tiny code cleanup commit that replaces two calls to `ptr::null()` with Rust's `unwrap_or_default()` to silence automated Clippy lint warnings. It does not change what value is produced (still a null pointer when no salt is provid…

62354461by cepetr+2−21 file
No security note in commit
Informational 15 AI analysisMessage 47 · Thin
TZ TrezorTrezor firmware BitcoinHardware wallets

refactor(xtask): simplify dependencies

This commit is a straightforward internal code cleanup in Trezor's build tooling. It moves a data structure and two helper methods from one Rust source file to another and updates callers accordingly. There is no change to user-facing beha…

6268349fby cepetr+9−193 files
No security note in commit
Informational 15 AI analysisMessage 47 · Thin
TZ TrezorTrezor firmware BitcoinHardware wallets

docs: add xtask documentation

This commit only adds documentation. It updates the table of contents and adds a new markdown page plus a diagram explaining the project's 'xtask' build helper. No code, build scripts, or firmware logic was changed, so it cannot introduce …

4879dababy cepetr+296−03 files
No security note in commit
Informational 17 AI analysisMessage 57 · Thin
TZ TrezorTrezor firmware BitcoinHardware wallets

feat(xtask): introduce project-toml build-options

This commit is a build-system refactoring for Trezor firmware. It moves the mapping of command-line build options to Rust/cargo features out of hard-coded Rust logic and into per-project TOML files. It also adds a small change so debug bui…

Build-option mapping now lives in project.toml files, increasing the attack surface for supply-chain/build-configuration tamperingMakefile change automatically enables debug-link for PYOPT=0 debug buildsValidation added to reject storage_insecure_testing_mode in production builds
d44de007by cepetr+681−40817 files
No security note in commit
Informational 15 AI analysisMessage 57 · Thin
TZ TrezorTrezor firmware BitcoinHardware wallets

ci(core): fix nightly ARM emulator filename

This commit fixes a filename-renaming step in the project's automated nightly build pipeline. It ensures ARM64 emulator files get the correct name expected by another testing tool. There is no change to the actual Trezor firmware code, dev…

ab95f08fby Martin Milata+3−01 file
No security note in commit
Informational 12 AI analysisMessage 62 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

chore(vendor): avoid micropython submodule noise in git status

This is a routine housekeeping change to reduce clutter in Git's status output for a third-party component (the MicroPython submodule). There is no indication it changes any code that runs on the Trezor device or affects security.

06cab32bby Martin Milata+1−11 file
No security note in commit
Repository ledger

Explore captured commits

Expand any commit for its author, full message, clarity score, changed files, triage signals, analysis, and source link.

Security candidatebuild(core): avoid unused variable warning in rng_fill_buffer_strongby matejcik · 690a69f3 · Jul 3, 2026 · 1 fileMessage 97 · StrongInformational 15Details
Commit message · matejcik

build(core): avoid unused variable warning in rng_fill_buffer_strong

When neither USE_OPTIGA nor USE_TROPIC, rng_fill_buffer_strong is just
rng_fill_buffer with extra steps.
Make that explicit in code; otherwise the `dst` variable is never read
from and we get a warning under clang.

97/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Explains rationale or failure mode
Why it was queued
entropy or randomnessseed or entropy path
AI analysis · Informational 15/100

This is a minor build cleanup. A developer added a compile-time branch so that when neither the Optiga nor Tropic security chips are used, the 'strong' random-number wrapper simply calls the normal random-number function and returns. The only reason for the change is to silence a compiler warning about an unused variable. There is no functional security change.

Lower-prioritychore(core): ignore some ancillary directoriesby matejcik · bc5f0914 · Jul 3, 2026 · 1 fileMessage 72 · AdequateTriage 0Details
Commit message · matejcik

chore(core): ignore some ancillary directories

that vscode-tf-tools extension uses to inject clangd configuration

72/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body
Lower-prioritybuild(core): replace -fsingle-precision-constant with explicit castsby matejcik · 03e661ce · Jul 3, 2026 · 8 filesMessage 85 · StrongTriage 0Details
Commit message · matejcik

build(core): replace -fsingle-precision-constant with explicit casts

The option -fsingle-precision-constant is unsupported in clang. Instead,
I'm adding -Wdouble-promotion (no hits in the codebase) and
-Wfloat-conversion (fixing the warning sites).

-fsingle-precision-constant ensures that all double literals without 'f'
suffix are treated as floats. But we don't care about literals per se,
we care about silent double promotions for calculations. The new set of
warnings is portable and more closely matches the intent.

85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Security candidatefeat(ethereum): allow approve and transfer to send ethby PrisionMike · e785f6c6 · Jul 2, 2026 · 8 filesMessage 62 · AdequateModerate 64Details
Commit message · PrisionMike

feat(ethereum): allow approve and transfer to send eth

[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
cryptography-sensitive pathsigning or wallet path
AI analysis · Moderate 64/100

This commit changes how Trezor devices display Ethereum transactions when someone sends ERC-20 token approval or transfer calls that also include native ETH. Previously, the device might not clearly show the attached ETH, so a user could unknowingly approve sending tokens plus real ETH. The patch makes the device surface that native ETH amount on the confirmation screen. It is a defensive fix that improves transparency rather than introducing a vulnerability.

Lower-prioritychore(translations): update fixturesby Michal Kazda · f8d3ebf1 · Jul 2, 2026 · 1 fileMessage 47 · ThinTriage 0Details
Commit message · Michal Kazda

chore(translations): update fixtures

[no changelog]

47/100 · ThinMessage clarity
✓ Descriptive subject✓ Uses a recognizable type or scope! No meaningful explanatory body
AI review queuedchore(translations): sync Crowdin update translationsby Michal Kazda · 7aac81d8 · Jul 2, 2026 · 6 filesMessage 62 · AdequateInformational 15Details
Commit message · Michal Kazda

chore(translations): sync Crowdin update translations

[no changelog]

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

This commit only updates translated text strings in the Trezor firmware. It changes wording in Czech, German, Spanish, French, and Portuguese translation files, plus the translation signature metadata. There are no code changes, no security fixes, and no behavior changes.

AI review queuedchore(translations): sync Crowdin fixing French failing testsby Michal Kazda · 1c84feca · Jul 2, 2026 · 3 filesMessage 72 · AdequateInformational 15Details
Commit message · Michal Kazda

chore(translations): sync Crowdin fixing French failing tests

[no changelog]

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

This commit updates translation files for Czech and French, plus the corresponding signed metadata. It changes wording on device screens (for example, how a 'hold to confirm' button is labeled and how a backup-fragment title is formatted) and refreshes the cryptographic fingerprint that protects those translations from tampering. There is no code change and no security vulnerability is present in the diff.

AI review queuedchore(translations): sync Crowdin fixing more French failing testsby Michal Kazda · 13b41359 · Jul 2, 2026 · 2 filesMessage 72 · AdequateInformational 15Details
Commit message · Michal Kazda

chore(translations): sync Crowdin fixing more French failing tests

[no changelog]

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

This commit updates French translation strings in the Trezor firmware and refreshes the corresponding translation signature metadata. The changes are purely cosmetic wording adjustments for on-screen text (for example, changing one French phrasing of a backup-recovery prompt to match another variant). There is no code behavior change, no cryptographic change, and no security fix.

AI review queuedchore(translations): sync Crowdin translationsby Thalarion · 700ef9ac · Jul 2, 2026 · 6 filesMessage 57 · ThinInformational 15Details
Commit message · Thalarion

chore(translations): sync Crowdin translations

[no changelog]

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

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

Security candidatefeat(clear_signing, ethereum) add new provider names.by PrisionMike · 230cfe37 · Jul 2, 2026 · 2 filesMessage 50 · ThinInformational 15Details
Commit message · PrisionMike

feat(clear_signing, ethereum) add new provider names.

[no changelog]

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing boundarysigning or wallet path
AI analysis · Informational 15/100

This commit is a routine feature update for Trezor's Ethereum 'clear signing' feature. It adds human-readable names for more DeFi and staking providers (like Lido, Morpho, Kiln) and makes the address lookup aware of which blockchain network (chain ID) an address belongs to. There is no security vulnerability or bug fix here.

AI review queuedfeat(core): set tropic configurationby Martin Pastyřík · 4a93242c · Jul 2, 2026 · 28 filesMessage 80 · StrongLow 32Details
Commit message · Martin Pastyřík

feat(core): set tropic configuration

Set the configuration of Tropic to the value excpected by the firmware.

The current version of tropic configuration is stored in slot 6 of Tropic R memory data. During the setting process, slot 7 is temporarily used to store a backup of the configuration version.

Also refactor tropic configuration from prodtest into firmware and enable sensors setting in model_server.

[no changelog]

80/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Why it was queued
second-pass: unusually broad change
AI analysis · Low 32/100

This commit moves the configuration settings for the Tropic secure chip out of the production-test tool and into the main firmware. At boot, the device now checks whether the Tropic chip's configuration matches the version expected by the firmware, and can update or repair it if needed. It also adds a version number stored in a Tropic memory slot and uses a backup slot during updates. The change is a feature/refactoring patch; there is no direct evidence in the commit that it fixes a known security vulnerability, but misconfiguration of a security chip is a security-sensitive operation.

Lower-priorityfeat(core/prodtest): Add Tropic tests.by Andrew Kozlik · e0d8f274 · Jul 2, 2026 · 6 filesMessage 82 · StrongTriage 0Details
Commit message · Andrew Kozlik

feat(core/prodtest): Add Tropic tests.

Co-Authored-By: Claude Opus 4.8 <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
Lower-priorityfeat(core/prodtest): Reboot Tropic in tropic-set-sensors.by Andrew Kozlik · 9bad5744 · Jul 2, 2026 · 4 filesMessage 62 · AdequateTriage 0Details
Commit message · Andrew Kozlik

feat(core/prodtest): Reboot Tropic in tropic-set-sensors.

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/prodtest): Add tropic-tests-cleanup.by Andrew Kozlik · dbe34907 · Jul 2, 2026 · 5 filesMessage 67 · AdequateTriage 0Details
Commit message · Andrew Kozlik

feat(core/prodtest): Add tropic-tests-cleanup.

67/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Mentions testing or verification! No meaningful explanatory body
Lower-priorityfix(core): use default cancel icon in SD cardby obrusvit · 46717e08 · Jul 2, 2026 · 1 fileMessage 84 · StrongTriage 0Details
Commit message · obrusvit

fix(core): use default cancel icon in SD card

- so that the text fits on one line in Bolt layout

[no changelog]

84/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body✓ Explains rationale or failure mode
Lower-prioritychore(core): update fixtures.jsonby obrusvit · 0d2d595f · Jul 2, 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-priorityfeat(core/bolt): support two line button textby obrusvit · 39e0f0c1 · Jul 2, 2026 · 1 fileMessage 57 · ThinTriage 0Details
Commit message · obrusvit

feat(core/bolt): support two line button text

[no changelog]

57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Lower-prioritybuild: build-docker.sh: also copy out artifacts from pub/by Martin Milata · 029217de · Jul 1, 2026 · 1 fileMessage 62 · AdequateTriage 0Details
Commit message · Martin Milata

build: build-docker.sh: also copy out artifacts from pub/

62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Lower-priorityfix(core/build): include btconly in pub/ firmware filenameby Martin Milata · 9653124d · Jul 1, 2026 · 3 filesMessage 62 · AdequateTriage 0Details
Commit message · Martin Milata

fix(core/build): include btconly in pub/ firmware filename

[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-priorityfix(core/build): copy secmon to artifacts/pubby Martin Milata · 59923d50 · Jul 1, 2026 · 1 fileMessage 57 · ThinTriage 0Details
Commit message · Martin Milata

fix(core/build): copy secmon to artifacts/pub

[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-prioritybuild: build-docker.sh: copy kernel.{elf,map} to build outputby Martin Milata · 51a09aa3 · Jul 1, 2026 · 1 fileMessage 62 · AdequateTriage 0Details
Commit message · Martin Milata

build: build-docker.sh: copy kernel.{elf,map} to build output

62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Lower-priorityfix(core): raise `wire.Error` from `EvoluIndexManagement` handlerby Roman Zeyde · 01cbba57 · Jul 1, 2026 · 2 filesMessage 100 · StrongTriage 0Details
Commit message · Roman Zeyde

fix(core): raise `wire.Error` from `EvoluIndexManagement` handler

Otherwise, it is sent to the host as a `FirmwareError`, which is usually used for unexpected errors (e.g. out-of-memory errors).

See also https://docs.trezor.io/trezor-firmware/core/misc/exceptions.html.

[no changelog]

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
Security candidatefeat(core): add chunkify support for Solana SignTxby obrusvit · f52bea0a · Jul 1, 2026 · 21 filesMessage 62 · AdequateInformational 18Details
Commit message · obrusvit

feat(core): add chunkify support for Solana SignTx

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
cryptography-sensitive pathsigning or wallet path
AI analysis · Informational 18/100

This commit adds an optional user-interface feature for Solana transactions on Trezor hardware wallets. When enabled, long Solana addresses are shown on the device screen in smaller groups of characters (chunks of 4) instead of one long string, making them easier for users to read and verify. There is no indication this change fixes a security vulnerability; it is a usability improvement.

AI review queuedfeat(core): sign rotation index into Evolu sign registrationby Martin Pastyřík · 4db3a69d · Jul 1, 2026 · 8 filesMessage 77 · AdequateInformational 24Details
Commit message · Martin Pastyřík

feat(core): sign rotation index into Evolu sign registration

This enables the Quota Manager to distinguish the indices and store the current index.

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

This commit updates the Trezor firmware's Evolu (delegated identity) registration signing feature so that the device now includes a 'rotation index' in the signed registration request. The rotation index tells the Quota Manager which version of the device's delegated identity key was used. The signature format was also bumped from V1 to V2 by adding the rotation index into the signed data. This is a feature enhancement, not a fix for an obvious security vulnerability, but it touches cryptographic signing and identity-key rotation, which are security-sensitive areas.

Lower-prioritychore: add Bitcoin Safe to `docs/misc/third-parties.md`by Roman Zeyde · b10a27af · Jul 1, 2026 · 1 fileMessage 62 · AdequateTriage 0Details
Commit message · Roman Zeyde

chore: add Bitcoin Safe to `docs/misc/third-parties.md`

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
documentation-only discount