Every captured commit receives deterministic security triage and a separate communication-quality score. Security candidates and broader second-pass signals receive full-patch Ollama analysis.
Message quality measures whether a commit identifies its scope, purpose, rationale, testing, and supporting references. It does not change the security-severity score.
This is a routine GitHub Actions workflow fix. It changes which Slack webhook secret is used for nightly test failure notifications and removes a now-unnecessary safety check. There is no security vulnerability in the change itself.
This commit only improves a test report for Trezor's clear-signing feature. It changes how skipped test cases are listed in a nightly summary, showing each skipped case's source file and calldata size instead of just counting them by reaso…
This commit only changes test scripts and documentation for the Trezor firmware clear-signing test suite. It makes the tests run more registry cases—specifically those where the developer definitions do not yet have a display format—so the…
This commit updates French and Portuguese translation strings in the Trezor firmware and refreshes the translation signature metadata. The changes are purely wording adjustments (for example, replacing abbreviations like 'nº' with the full…
This commit changes a code-coverage tracking map inside the Trezor firmware from a claimed capacity of 1,048,576 entries down to 65,536 entries. The commit message says the old capacity was never truly that large because the heapless libra…
No cryptographic or secret-handling code changedNo input parsing, deserialization, or memory allocator changesChange is in a debug/test instrumentation module (coverage)
This commit is a routine update of translated user-interface text strings for the Trezor hardware wallet. It adds new translations (for example, warnings about exporting public keys and Solana blind-signing prompts), updates existing wordi…
This commit only adds new test cases for Ethereum clear-signing array parsing. It does not change any production code, so it cannot introduce a new security vulnerability on its own. The tests verify that malformed arrays (out-of-bounds of…
test-only changeno production code modifiedadds defensive test coverage for ABI decoding edge cases
This commit hardens the Trezor firmware's task scheduler against fault-injection attacks. These attacks use physical techniques like voltage glitches or laser pulses to trick the device into executing code with higher privileges than inten…
Fault-injection hardening (FIH) explicitly mentioned in commit title and code commentsPrivilege-level transition split into multiple guarded stepsAdded runtime invariant check that only the kernel task may run privileged
This commit only removes an unused parameter called `is_dynamic` from test helper functions and from test data in three test files. It does not change any production firmware code, wallet behavior, or security logic. It is a cleanup of the…
This commit updates the data-format definitions used by Trezor devices for Ethereum 'clear signing' (showing human-readable details of smart-contract interactions). It adds support for more numeric types, new path-step structures, and extr…
Schema expansion increases attack surface for future clear-signing parser logic, but no new parser logic is present in this commit.Replacement of NotImplementedError with InvalidFormatDefinition is a defensive change that turns unimplemented paths into a handled error rather than a crash/DoS vector.New optional fields and deprecated old fields (is_dynamic, lookup_address) are backward-compatible changes.
This is a bug-fix patch in the Python Trezor client library. It changes how the software probes whether a connected device uses the older protocol v1. Previously, the probe tried to read and throw away leftover data, but that read could ac…
No security-relevant signal in commit message or diffFix is described as a connectivity/functional bug, not a vulnerabilityNo mention of CVE, researcher credit, or security advisory
This commit is a user-interface improvement, not a security fix. It changes the language-change confirmation prompt on Trezor devices so that it shows a human-readable language name (for example, 'French') instead of a raw code like 'fr-FR…
This commit updates Spanish and French translation strings in the Trezor firmware and refreshes the translation signature file. The changes are purely textual wording adjustments (for example, changing 'Mostrar palab.' to 'Mostrar palabras…
This commit hardens cryptographic code in Trezor firmware against two potential side-channel leaks. First, it simplifies how a secret condition value is checked inside an assert statement so the compiler produces only one branch instead of…
Side-channel hardening in constant-time cryptographic primitivesReplacement of double-evaluation volatile assert with single-branch assertElimination of secret-dependent memory access in elliptic-curve scalar multiplication
This commit adds a new nightly automated testing workflow for Ethereum 'clear signing' on Trezor hardware wallets. It does not change any wallet firmware code that users run; it only adds test scripts, CI configuration, documentation, and …
This commit is a routine code cleanup. It removes a small helper function called keccak_32 from a shared crypto utility file and places an equivalent helper directly inside the only test file that still uses it. There is no change to how t…
This commit removes support for a cryptocurrency called SmartCash from Trezor hardware wallets. It deletes coin definitions, support entries, and a custom cryptographic curve used only by SmartCash. There is no security vulnerability being…
No security-relevant signals detectedPure feature removal / code cleanup
This commit removes all support for the Groestlcoin cryptocurrency from Trezor firmware. It deletes coin definitions, the custom Groestl hash algorithm code, related address/transaction handling, and tests. There is no security vulnerabili…
No security-relevant change: pure feature removalNo new attack surface introducedNo vulnerability patched or created
This commit removes all support for the Tezos cryptocurrency from Trezor firmware, software libraries, and documentation. It is a feature-removal change, not a security fix or vulnerability patch. There is no indication in the commit that …
This update reduces the longest allowed screen-lock timeout on older Trezor devices from about 6 days down to 149 hours (just over 6 days). It makes the legacy firmware behave the same as newer Trezor firmware and prevents users from setti…
Bounds enforcement added for a configurable security-relevant timeoutAlignment of security policy between legacy and core firmware variantsTest coverage added for boundary values above and below new maximum
- Send nightly clear-signing failures via SLACK_HW_TESTS_WEBHOOK, the secret core-hw.yml already uses, instead of a separate SLACK_CLEAR_SIGNING_WEBHOOK that was never set up. - Drop the check that skipped the notification when the secret was missing, matching core-hw.yml.
[no changelog]
90/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
signing boundarysigning or wallet pathdocumentation-only discount
AI analysis · Informational 15/100
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.
Security candidatetest(clear_signing): name the skipped casesby PrisionMike · 98deb5b0 · Nov 20, 2026 · 2 filesMessage 90 · StrongInformational 15Details
Commit message · PrisionMike
test(clear_signing): name the skipped cases
- List every skipped case in the summary, with its registry test file and calldata size, not only the count per reason, e.g. which descriptor has calldata over 6144 bytes.
[no changelog]
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
90/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
signing boundarysigning or wallet path
AI analysis · Informational 15/100
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 reason. There is no change to firmware, wallet logic, cryptography, or any user-facing security behavior.
Security candidatetest(clear_signing): run the cases without display formatby PrisionMike · 05c1f4ef · Nov 20, 2026 · 5 filesMessage 95 · StrongInformational 15Details
Commit message · PrisionMike
test(clear_signing): run the cases without display format
- Run the registry cases that the dev definitions have no display format for, of all providers, instead of skipping them. The firmware blind-signs them (or clear-signs them with a built-in format), and the summary lists the blind-signed ones as "blind-signed, no format": the cases that the definitions do not cover.
[no changelog]
Co-Authored-By: Claude Opus 5.5 <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
signing boundarysigning or wallet path
AI analysis · Informational 15/100
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 nightly summary can list them as 'blind-signed, no format.' It does not change the firmware itself, the signing logic, or any user-facing behavior. There is no security fix or vulnerability here.
- Reduced to 64 K after heapless update. Note that the capacity was never actually 1 M entries, it would silently overflow with heapless 0.9.2.
[no changelog]
95/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Names security-relevant behavior explicitly
Why it was queued
memory safety
AI analysis · Informational 10/100
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 library version in use would silently overflow. The change only affects internal test/debug instrumentation and is not a security fix for user funds or device secrets. It is marked with '[no changelog]', meaning the project did not treat it as a user-visible change.
Security candidatetest(clear_signing): edge cases for arraysby PrisionMike · dcdf3068 · Nov 18, 2026 · 1 fileMessage 67 · AdequateInformational 12Details
Commit message · PrisionMike
test(clear_signing): edge cases for arrays
[no changelog]
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
Why it was queued
signing boundarysigning or wallet path
AI analysis · Informational 12/100
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 offsets, truncated data, oversized lengths) are rejected rather than parsed incorrectly.
refactor(core): harden task switching against fault injections
[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
secure hardware boundarydefensive validation
AI analysis · High 70/100
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 intended. The change ensures the processor starts in a lower-privilege state before deciding whether to elevate the kernel task, and adds a safety check that halts the device if a non-kernel task somehow ends up privileged. It is a defensive hardening patch rather than a fix for a known remotely exploitable bug.
Security candidatefeat(clear_signing): update proto defs for features to be supported.by PrisionMike · 84cb6a4b · Nov 18, 2026 · 9 filesMessage 62 · AdequateInformational 21Details
Commit message · PrisionMike
feat(clear_signing): update proto defs for features to be supported.
[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 boundarysigning or wallet path
AI analysis · Informational 21/100
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 extra formatting options, while making some older fields optional. The code changes are mostly additions to generated protocol files and a small update to the Python parser. There is no direct evidence in the commit of a security vulnerability being fixed or introduced.
chore(crypto): hardening against potential side-channel leakage
Two issues - Using `volatile cond` twice in a single `assert`, i.e. `assert(cond == 0 | cond == 1)` results in two conditional branches (potentially distinguishable). - Memory access is (potentially) dependent on the secret exponent. This is not an expoitable issue, as Trezor does not utilize a memory cache.
Solution - Using `cond` only once in the `assert` (`assert(cond <= 1)`), which is compiled into a single branch. - Using `point_select` makes the memory access independent of the secret exponent.
Note that all `assert`s in the C code are compiled into production core firmware, so the first issue DOES affect the production code.
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Why it was queued
defensive validationcryptography-sensitive path
AI analysis · Low 47/100
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 two, reducing the chance that timing or power analysis could reveal whether the value was 0 or 1. Second, it replaces direct table lookups that depended on a secret scalar with a constant-time selection helper that always reads every table entry. The commit message explicitly says the memory-access issue is not exploitable on Trezor because the device has no cache, but the assert issue does affect production firmware because asserts are compiled in.
Security candidatefeat(ci, clear_signing): add clear signing device tests as a nightly run.by PrisionMike · fea125ba · Nov 15, 2026 · 17 filesMessage 72 · AdequateInformational 15Details
Commit message · PrisionMike
feat(ci, clear_signing): add clear signing device tests as a nightly run.
[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 boundarysigning or wallet path
AI analysis · Informational 15/100
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 reporting improvements. There is no indication this commit fixes or introduces a security vulnerability.
Security candidatechore(core): move `keccak_32` to unittestsby Roman Zeyde · f3225451 · Nov 12, 2026 · 2 filesMessage 57 · ThinInformational 15Details
Commit message · Roman Zeyde
chore(core): move `keccak_32` to unittests
[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 15/100
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 the device handles user data, no bug fix, and no security-related behavior change.
Security candidatechore: remove SmartCashby Roman Zeyde · b6d65c00 · Nov 12, 2026 · 16 filesMessage 63 · AdequateInformational 15Details
Commit message · Roman Zeyde
chore: remove SmartCash
- drop SmartCash (SMART, tSMART) coin definitions and support entries - remove secp256k1-smart curve from crypto, core coininfo and cointool
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
63/100 · AdequateMessage clarity
✓ Subject identifies a change✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Why it was queued
cryptography-sensitive pathboot or update path
AI analysis · Informational 15/100
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 fixed here; it is simply cleanup of an unused or unsupported coin.
Security candidatechore(common,core,legacy,crypto): remove Groestlcoinby Roman Zeyde · e22d597d · Nov 12, 2026 · 45 filesMessage 77 · AdequateInformational 15Details
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
cryptography-sensitive pathsigning or wallet pathboot or update path
AI analysis · Informational 15/100
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 vulnerability here—this is a feature-removal cleanup.
✓ Descriptive subject✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
signing or wallet pathboot or update path
AI analysis · Informational 15/100
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 it addresses any security issue.
Security candidatefix(legacy): lower maximum auto-lock delay to 149 hoursby Ondřej Vejpustek · c108f275 · Nov 11, 2026 · 4 filesMessage 85 · StrongInformational 24Details
Commit message · Ondřej Vejpustek
fix(legacy): lower maximum auto-lock delay to 149 hours
This aligns the limit with the core firmware.
`config_getAutoLockDelayMs()` clamps the stored value, so a device that already stores a longer delay starts using the new maximum after the update. The stored value itself is not rewritten.
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 · Informational 24/100
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 setting an extremely long auto-lock delay. Devices that already had a longer delay stored will silently use the new lower limit after updating, without changing the saved value.
Security candidatefeat(vendor): zero memory freed by the MicroPython GCby Martin Pastyřík · 2dae13d5 · Nov 11, 2026 · 3 filesMessage 97 · StrongLow 45Details
Commit message · Martin Pastyřík
feat(vendor): zero memory freed by the MicroPython GC
Bump MicroPython and enable `MICROPY_GC_CLEAR_ON_SWEEP` and `MICROPY_GC_CLEAR_ON_FREE`, so that memory freed by the GC sweep or released by `gc_free()` and `gc_realloc()` is zeroed.
[no changelog] Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
boot or update path
AI analysis · Low 45/100
This commit updates the MicroPython interpreter used in Trezor hardware wallets so that memory freed by the garbage collector is overwritten with zeros. The goal is to reduce the risk that leftover secrets (such as private keys or PIN data) remain in memory after they are no longer needed. It is a defensive hardening change, not a fix for a known exploitable bug.
✓ Descriptive subject✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
cryptography-sensitive pathsigning or wallet path
AI analysis · Informational 15/100
This commit is a routine regeneration of font files used by the Trezor hardware wallet's user interface. It updates glyph bitmaps, spacing values, and comments across many font source files, but does not change any executable logic, cryptographic code, or security-sensitive behavior. There is no indication this is a security fix or introduces a vulnerability.
Co-authored-by: onvej-sl <38104856+onvej-sl@users.noreply.github.com> Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
95/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Names security-relevant behavior explicitly
Why it was queued
access controlauthentication path
AI analysis · Informational 15/100
This commit only adds a new Python unit-test file for Trezor's device-authentication logic. It does not change any production code, cryptographic checks, or firmware behavior. There is no security vulnerability introduced or fixed here.
Security candidaterefactor(python): add `signature_unsafe_expanded` into `_ed25519`by M1nd3r · 0b6f470b · Nov 10, 2026 · 1 fileMessage 85 · StrongInformational 18Details
Commit message · M1nd3r
refactor(python): add `signature_unsafe_expanded` into `_ed25519`
[no changelog]
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Co-authored-by: onvej-sl <38104856+onvej-sl@users.noreply.github.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
signing boundary
AI analysis · Informational 18/100
This commit adds a new helper function for creating Ed25519 digital signatures when the secret key has already been expanded into its internal components. It is explicitly marked as unsafe and for testing only, and it does not change any existing security behavior. The change appears to be a code refactor to support a specific key-storage format used by another project (Tropic).
✓ 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✓ Names security-relevant behavior explicitly
Why it was queued
access control
AI analysis · Informational 23/100
This commit improves error messages in the Trezor Python command-line library when a user tries to run device authentication on hardware models that do not support it, or when the installed library version lacks the needed root certificates for a model. It does not change cryptographic behavior; it only fails earlier with clearer messages instead of potentially confusing downstream failures.
Security candidateci(core): tweak MemBrowse workflowsby Martin Milata · f62fe43e · Nov 6, 2026 · 4 filesMessage 72 · AdequateInformational 21Details
Commit message · Martin Milata
ci(core): tweak MemBrowse workflows
- Pin actions to commit hashes. - Don't run on forks.
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
access controldocumentation-only discount
AI analysis · Informational 21/100
This commit hardens Trezor's GitHub CI workflows that run a third-party memory-analysis tool called MemBrowse. It pins the MemBrowse action to a specific commit hash instead of a moving version tag, prevents the workflows from running on forked repositories, adds a job timeout, and fixes a minor condition placement. These are defensive supply-chain and hardening improvements, not a fix for an active vulnerability in the firmware itself.
Security candidateci(core): tighten permissionsby Martin Milata · df815315 · Nov 6, 2026 · 1 fileMessage 47 · ThinLow 39Details
Commit message · Martin Milata
ci(core): tighten permissions
47/100 · ThinMessage clarity
✓ Descriptive subject✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
credential or privilege statedocumentation-only discount
AI analysis · Low 39/100
This commit tightens the GitHub Actions workflow permissions for the Trezor firmware repository. Previously, the entire workflow had broad permissions: it could write OIDC tokens, read repository contents, and write pull-request comments. Now those permissions are removed from the top level and granted only to the specific jobs that actually need them. This is a defensive hardening change that reduces the damage if a malicious or compromised step were abused, but it does not by itself fix an active vulnerability.
✓ Subject identifies a change✓ Uses a recognizable type or scope✓ Provides an explanatory body
Why it was queued
signing or wallet pathboot or update path
AI analysis · Informational 15/100
This commit only updates version numbers and translation metadata across Trezor firmware files. There are no code changes, no bug fixes, and no security-related modifications visible in the diff.
Security candidatefix(core): lower maximum auto-lock delay to 149 hoursby Ondřej Vejpustek · 7cc12064 · Nov 6, 2026 · 7 filesMessage 97 · StrongLow 41Details
Commit message · Ondřej Vejpustek
fix(core): lower maximum auto-lock delay to 149 hours
Setting the auto-lock delay to the maximum crashed the firmware on every boot. The old maximum of `0x2000_0000` ms is exactly half the MicroPython tick period on 32-bit MCUs, which is the smallest delta that `utime.ticks_add()` rejects with `OverflowError`.
A device that already stores the old maximum recovers after the update, because `get_autolock_delay_ms()` clamps the stored value. The stored value itself is not rewritten.
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
memory safety
AI analysis · Low 41/100
This update fixes a bug in Trezor hardware wallets where setting the screen auto-lock delay to its maximum value caused the device to crash every time it restarted. The old maximum was chosen so that it hit a limit inside the device's timekeeping code, triggering an overflow error. The fix lowers the maximum allowed auto-lock delay to 149 hours and adds a safety check so the device cannot accept a value that would cause the crash. A device already stuck with the old maximum will recover after updating because the firmware clamps the stored value down to a safe range.
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
cryptography-sensitive pathboot or update path
AI analysis · Informational 15/100
This commit is a code cleanup that standardizes the names used for page-number debugging output across different parts of the Trezor user interface. It does not change any user-visible behavior, security logic, or device functionality. There is no security issue here.
Security candidatetest(core): use more time-efficient passphrase pattern on touch layoutsby Roman Zeyde · 09b86896 · Nov 5, 2026 · 4 filesMessage 100 · StrongInformational 15Details
Commit message · Roman Zeyde
test(core): use more time-efficient passphrase pattern on touch layouts
Otherwise, some click tests takes >2 minutes (because they need to wait for ~1 second between consecutive clicks on the same button).
[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✓ Mentions testing or verification
This commit only changes automated test code for the Trezor hardware wallet. It swaps the long passphrase test string from repeated 'W' characters to an alternating 'AD' pattern so the automated click tests run faster on touch-screen layouts. There is no change to the actual firmware, wallet behavior, or security logic.