BB
← All projectsBitBox

BitBox02 firmware

Firmware and bootloader for BitBox02 signing devices.

BitcoinHardware walletsNormal
Repository coverage

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

314security candidates186second-pass queue827AI analyses
88commits · 30 days
150commits · 60 days
340commits · 180 days
723commits · 365 days
Backfill bands
Aug 5 → Feb 6335 seen28 candidatesComplete
Feb 6 → Jun 6265 seen19 candidatesComplete
Jun 6 → Jul 619 seen5 candidatesComplete
Jul 6 → Aug 526 seen3 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.

59/100 average clarity
86Strong · 80–100
381Adequate · 60–79
381Thin · 40–59
90Opaque · 0–39
27security candidates 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.
Marko Bencun504157459656
benma's agent15566140267
Niklas Dusenlund17151144057
Cedric Wiese24919051
NickeZ Agent1669077
cedwies12512063
Sebastian Sutter655060
Tomas Vrba12410068
Yasser Aziza333070
Jad14210060
benma312069
Niklas211054
Analysis record

Published AI watches

Last scanned 35 minutes ago

Informational 12 AI analysisMessage 50 · Thin
BB BitBoxBitBox02 firmware BitcoinHardware wallets

Merge remote-tracking branch 'agent/benma-agent/remove-aes-hmac-c-exports'

This commit removes unused C-language export functions for AES encryption/HMAC from the BitBox02 firmware's Rust code. It is a cleanup change: the functions are deleted, the crate is no longer included in firmware builds, and simulators st…

Reduction of C FFI attack surface by removing no_mangle AES/HMAC exportsDependency cleanup: bitbox-aes no longer linked into firmware or simulatorsNo patch of an identified vulnerability in cryptographic logic
0b6365c6by Marko Bencun+2−5913 files
No security note in commit
Low 43 AI analysisMessage 50 · Thin
BB BitBoxBitBox02 firmware BitcoinHardware wallets

Merge remote-tracking branch 'agent/benma-agent/btc-root-xpub-m49'

This firmware update makes two changes to how the BitBox02 hardware wallet handles Bitcoin-related requests. First, it blocks apps from exporting the wallet's master public key (the 'root xpub') at the top-level path 'm/'. Second, it allow…

Root xpub export blocked at empty keypath (m/)Changelog describes root-xpub restriction as a security-relevant changeExternal service message signing expanded to m/49 unhardened purpose
5294645cby Marko Bencun+79−195 files
Vendor flagged security relevance
Informational 17 AI analysisMessage 78 · Adequate
BB BitBoxBitBox02 firmware BitcoinHardware wallets

cipher: remove unused AES-HMAC C exports

This commit removes two unused C-language bridge functions that wrapped an AES-HMAC encryption/decryption module. The functions themselves were not called from C code; the firmware now calls the same encryption logic directly from Rust. Re…

Removal of C FFI wrappers that could panic on malformed inputsCommit message acknowledges potential panic conditions (invalid IV length, undersized output buffer)No functional change to the underlying AES-HMAC implementation
090a263fby benma's agent+2−5913 files
Vendor flagged security relevance
Low 34 AI analysisMessage 85 · Strong
BB BitBoxBitBox02 firmware BitcoinHardware wallets

u2f: bound DER signature component reads

This commit fixes a small but real bug in how U2F signature components are converted to DER format. The old code could strip too many leading zeros and then read past the end of a 32-byte signature piece, potentially producing an invalid o…

Out-of-bounds read at component boundary during DER encodingPotential malformed DER output for all-zero signature componentDefensive hardening in U2F signature handling
dd17bed7by benma's agent+21−43 files
Vendor flagged security relevance
Low 30 AI analysisMessage 78 · Adequate
BB BitBoxBitBox02 firmware BitcoinHardware wallets

btc: allow message signing under m/49

This commit expands the BitBox02 hardware wallet's Bitcoin message-signing feature to also accept key paths starting with the unhardened purpose 'm/49'. Previously only hardened m/45' and m/48' were treated as valid 'external service' keyp…

Relaxation of keypath allowlist for message signingUnhardened purpose m/49 added to external-service signing namespaceUser confirmation prompt still required ('External service key')
1f377f72by benma's agent+63−194 files
No security note in commit
High 72 AI analysisMessage 73 · Adequate
BB BitBoxBitBox02 firmware BitcoinHardware wallets

btc: reject master xpub exports

This commit closes a security gap in the BitBox02 hardware wallet's Bitcoin API. Previously, a host app could ask the device to export the 'master xpub' (the public key at the very top of the wallet, keypath m/). Combined with any leaked p…

Master xpub export preventedPrivate-key derivation risk described in commit messageUnhardened path key compromise scenario
c4524b15by benma's agent+16−02 files
Vendor flagged security relevance
Informational 15 AI analysisMessage 50 · Thin
BB BitBoxBitBox02 firmware BitcoinHardware wallets

Merge branch 'nickez-agent/configure-stage1-embedding'

This commit is a build-system refactor for the BitBox02 hardware wallet firmware. It replaces a set of separate 'bootloader upgrade' firmware images with a configurable option to embed the same bootloader update data into the normal firmwa…

70a32f5bby Niklas Dusenlund+152−33111 files
No security note in commit
High 70 AI analysisMessage 50 · Thin
BB BitBoxBitBox02 firmware BitcoinHardware wallets

Merge remote-tracking branch 'agent/benma-agent/merge-firmware-v9.29.0'

This firmware update hardens how the BitBox02 handles SwapKit-style cryptocurrency swaps and Bitcoin multisig addresses. It adds a new 'refund memo' to payment requests so the device can verify that any refund address belongs to the same w…

CHANGELOG labels prior changes as 'Bitcoin security fixes (multisig keypath and previous-transaction hash length validation)'CHANGELOG labels v9.29.0 as 'Require wallet-owned refund addresses for SwapKit'New RefundMemo protobuf message with address and optional derivation info
9b16af63by Marko Bencun+867−12411 files
Vendor flagged security relevance
Moderate 60 AI analysisMessage 50 · Thin
BB BitBoxBitBox02 firmware BitcoinHardware wallets

Merge remote-tracking branch 'agent/benma-agent/merge-bootloader-v1.2.3'

This commit hardens the BitBox02 bootloader's stored version-rollback protection data. It adds a SHA-256 checksum over the firmware and signing-key version 'floors' and a one-time migration marker, so the device can detect tampering or cor…

Adds integrity checksum (SHA-256) for anti-rollback version floors in bootloader flash dataIntroduces one-time migration marker to prevent repeated downgrade/migration windowsProduction bootloader now aborts on invalid bootdata instead of silently reinitializing it
a4ddb764by Marko Bencun+2124−3123 files
Vendor flagged security relevance
Informational 15 AI analysisMessage 50 · Thin
BB BitBoxBitBox02 firmware BitcoinHardware wallets

Merge remote-tracking branch 'agent/benma-agent/high-fee-wording-v9.27.2'

This commit only updates test data and test expectations to reflect that a wording change for high Bitcoin transaction fees was released in firmware version 9.27.2 instead of 9.28.0. It does not change any device firmware code, security lo…

00f9eb22by Marko Bencun+65−1123 files
No security note in commit
Informational 15 AI analysisMessage 68 · Adequate
BB BitBoxBitBox02 firmware BitcoinHardware wallets

btc: fix high-fee wording cutoff in vectors

This commit only updates test data and test expectations for the BitBox02 firmware. It changes which firmware versions are expected to show an old versus new high-fee warning message, because the real firmware already started showing the n…

dc5702d0by benma's agent+65−1123 files
No security note in commit
High 77 AI analysisMessage 50 · Thin
BB BitBoxBitBox02 firmware BitcoinHardware wallets

Merge remote-tracking branch 'agent/benma-agent/stage0-reject-zero-signatures'

This update hardens the BitBox02 hardware wallet's bootloader so it refuses to accept a firmware update signed with an all-zero signature. Previously, the cryptographic verification routine could treat a zero-filled signature as valid unde…

Rejects all-zero ECDSA signatures that may verify as validAdds volatile signature read to mitigate LTO-based read eliminationORs all signature bytes without early exit to ensure full-byte inspection
aec4595dby Marko Bencun+81−22 files
No security note in commit
Low 35 AI analysisMessage 50 · Thin
BB BitBoxBitBox02 firmware BitcoinHardware wallets

Merge remote-tracking branch 'agent/benma-agent/stage1-pairing-lifecycle'

This update fixes a Bluetooth pairing bug in the BitBox02 Nova hardware wallet. When the device switched from Bluetooth back to USB mode, it could keep an old pairing request active. The fix clears that stale pairing state so the device do…

Clearing of stale Bluetooth pairing state on mode switchPairing code/request flag left set across BLE->USB transition before fixBluetooth pairing lifecycle change in bootloader startup path
1047430dby Marko Bencun+7−65 files
Vendor flagged security relevance
Low 47 AI analysisMessage 50 · Thin
BB BitBoxBitBox02 firmware BitcoinHardware wallets

Merge remote-tracking branch 'agent/benma-agent/silent-payment-constant-time-ecdh'

This commit changes how the BitBox02 hardware wallet computes a secret value used in Bitcoin silent payments. Previously, the device used a function that could leak timing information about the secret key through how long the calculation t…

Constant-time cryptographic operation addedVariable-time secret-key multiplication removedSide-channel hardening for silent payments
c1590222by Marko Bencun+21−122 files
No security note in commit
Moderate 59 AI analysisMessage 68 · Adequate
BB BitBoxBitBox02 firmware BitcoinHardware wallets

btc: use constant-time ECDH for silent payments

This commit hardens the BitBox02 hardware wallet's silent-payments feature against a side-channel attack. Previously, the device multiplied a secret key with a public key using a routine whose execution time could leak information about th…

Constant-time cryptographic operation introduced to replace variable-time secret-key multiplicationVariable-time scalar multiplication retained only on public operandsSilent payments private input key material (a_sum) no longer used in variable-time path
7e741cfdby benma's agent+21−122 files
Vendor flagged security relevance
Informational 15 AI analysisMessage 50 · Thin
BB BitBoxBitBox02 firmware BitcoinHardware wallets

Merge branch 'nickez-agent/pin-protobuf-generators'

This commit is a build-system and developer-environment change. It pins the protobuf compiler and related Python tools to specific versions via a project-managed Python virtual environment, instead of relying on whatever version a develope…

Pinning build tools to exact versions reduces non-determinism in generated codeMoves protobuf compiler from system/Docker-installed binary to a version-locked Python wheelNo changes to firmware, cryptography, authentication, or device protocol logic
d072b0f9by Niklas Dusenlund+107−6411 files
No security note in commit
Informational 15 AI analysisMessage 92 · Strong
BB BitBoxBitBox02 firmware BitcoinHardware wallets

build: prefer local protoc for Rust bindings

This commit changes the build script that generates Rust code from protobuf definitions. It makes the build prefer a specific local copy of the protobuf compiler (protoc) installed in the repository's virtual environment, rather than relyi…

de8be632by NickeZ Agent+4−01 file
No security note in commit
Informational 15 AI analysisMessage 80 · Strong
BB BitBoxBitBox02 firmware BitcoinHardware wallets

build: use IPv4 for container downloads

This change forces the build system to use IPv4 instead of IPv6 when downloading tools and software packages during Docker image creation. It is a build reliability fix for GitHub Actions CI runners that lack IPv6 connectivity, not a secur…

bc434dcfby NickeZ Agent+6−41 file
No security note in commit
Informational 15 AI analysisMessage 80 · Strong
BB BitBoxBitBox02 firmware BitcoinHardware wallets

build: check regenerated protobuf bindings

This change improves a build/CI script that checks whether automatically generated protobuf binding files are up to date. It now also checks Python bindings and deletes old generated files before regenerating them, so stale files cannot hi…

No security-relevant code changeBuild/CI hardening onlyNo vulnerability fix or exploit mitigation present in diff
ff3f7474by NickeZ Agent+13−22 files
No security note in commit
Informational 15 AI analysisMessage 45 · Thin
BB BitBoxBitBox02 firmware BitcoinHardware wallets

Merge branch 'translate-passphrase-on-host'

This commit is a localization (translation) update for the BitBox02 hardware wallet. It replaces hard-coded English text strings in the passphrase unlock feature with calls to the device's internationalization system, so the same messages …

4dfa26b4by Marko Bencun+33−103 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.

AI review queuedMerge remote-tracking branch 'agent/benma-agent/btc-root-xpub-m49'by Marko Bencun · 5294645c · Nov 20, 2026 · 5 filesMessage 50 · ThinLow 43Details
Commit message · Marko Bencun

Merge remote-tracking branch 'agent/benma-agent/btc-root-xpub-m49'

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Low 43/100

This firmware update makes two changes to how the BitBox02 hardware wallet handles Bitcoin-related requests. First, it blocks apps from exporting the wallet's master public key (the 'root xpub') at the top-level path 'm/'. Second, it allows signing Bitcoin messages using keypaths that start with 'm/49' (unhardened) for external services, in addition to the already allowed 'm/45'' and 'm/48'' paths. The changelog explicitly frames the root-xpub restriction as a security improvement, while the m/49 change is described as a feature expansion.

AI review queuedMerge remote-tracking branch 'agent/benma-agent/high-fee-wording-v9.27.2'by Marko Bencun · 00f9eb22 · Nov 19, 2026 · 3 filesMessage 50 · ThinInformational 15Details
Commit message · Marko Bencun

Merge remote-tracking branch 'agent/benma-agent/high-fee-wording-v9.27.2'

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit only updates test data and test expectations to reflect that a wording change for high Bitcoin transaction fees was released in firmware version 9.27.2 instead of 9.28.0. It does not change any device firmware code, security logic, or user-facing behavior. There is no security issue here.

AI review queuedbtc: fix high-fee wording cutoff in vectorsby benma's agent · dc5702d0 · Nov 19, 2026 · 3 filesMessage 68 · AdequateInformational 15Details
Commit message · benma's agent

btc: fix high-fee wording cutoff in vectors

Firmware v9.27.2 already displays the revised high-fee warning. The Bitcoin transaction
vectors use v9.28.0 as the cutoff, so they expect the old wording when run against v9.27.2.

Move the cutoff to v9.27.2 for both the send-amount and total-input warnings. Earlier firmware
versions keep their existing screen expectations.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit only updates test data and test expectations for the BitBox02 firmware. It changes which firmware versions are expected to show an old versus new high-fee warning message, because the real firmware already started showing the new wording in version 9.27.2, not 9.28.0. There is no change to the actual device firmware or to user-facing security behavior.

AI review queuedMerge branch 'nickez-agent/pin-protobuf-generators'by Niklas Dusenlund · d072b0f9 · Nov 16, 2026 · 11 filesMessage 50 · ThinInformational 15Details
Commit message · Niklas Dusenlund

Merge branch 'nickez-agent/pin-protobuf-generators'

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
parser or protocol pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit is a build-system and developer-environment change. It pins the protobuf compiler and related Python tools to specific versions via a project-managed Python virtual environment, instead of relying on whatever version a developer or CI worker happens to have installed. There is no change to firmware code, device behavior, or security logic, and no security vulnerability is being fixed.

AI review queuedbuild: prefer local protoc for Rust bindingsby NickeZ Agent · de8be632 · Nov 12, 2026 · 1 fileMessage 92 · StrongInformational 15Details
Commit message · NickeZ Agent

build: prefer local protoc for Rust bindings

Direct Cargo builds invoke protobuf generation without the Makefile's
local virtualenv PATH setup, so they can select a different protoc version.

Set PROTOC to the repository's .venv/bin/protoc when it is executable.
Otherwise, retain prost's existing PROTOC override and PATH lookup so
container and global installations continue to work without bootstrapping.

92/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Explains rationale or failure mode
Why it was queued
parser or protocol pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit changes the build script that generates Rust code from protobuf definitions. It makes the build prefer a specific local copy of the protobuf compiler (protoc) installed in the repository's virtual environment, rather than relying on whatever version happens to be found on the developer's system. This is a build reproducibility and consistency improvement, not a security fix for a vulnerability.

AI review queuedbuild: check regenerated protobuf bindingsby NickeZ Agent · ff3f7474 · Nov 12, 2026 · 2 filesMessage 80 · StrongInformational 15Details
Commit message · NickeZ Agent

build: check regenerated protobuf bindings

CI only checked Rust protobuf bindings, leaving committed Python modules
and type stubs unchecked. Existing output files could also hide bindings
that are no longer generated.

Delete both generated output directories before regenerating Rust and
Python bindings. Fail on modified, deleted or untracked files and print
the diff and affected paths so missing regeneration is visible in CI.

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
parser or protocol pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This change improves a build/CI script that checks whether automatically generated protobuf binding files are up to date. It now also checks Python bindings and deletes old generated files before regenerating them, so stale files cannot hide missing updates. There is no runtime security fix here—only a stronger development safeguard.

AI review queuedMerge remote-tracking branch 'agent/benma-agent/set-password-seed-test'by Marko Bencun · 8e418585 · Nov 12, 2026 · 1 fileMessage 60 · AdequateInformational 14Details
Commit message · Marko Bencun

Merge remote-tracking branch 'agent/benma-agent/set-password-seed-test'

60/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
merge-commit duplicate discountsecond-pass: broader security terminology
AI analysis · Informational 14/100

This commit only adds a new unit test to the BitBox02 firmware. It verifies that the set-password API correctly derives a wallet seed from host entropy, device randomness, a salt, and the user's password. No production code was changed, and no bug or security weakness is present in the diff.

AI review queuedMerge remote-tracking branch 'agent/benma-agent/bitcoin-coin-enabled'by Marko Bencun · 71f4f535 · Nov 12, 2026 · 3 filesMessage 50 · ThinLow 49Details
Commit message · Marko Bencun

Merge remote-tracking branch 'agent/benma-agent/bitcoin-coin-enabled'

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Low 49/100

This commit adds a new check called coin_enabled() at the start of several Bitcoin-related operations in the BitBox02 firmware, including registering script configurations, signing messages, and signing transactions. The change appears to enforce whether a particular Bitcoin coin type (such as mainnet, testnet, or regtest) is currently enabled before allowing those operations to proceed. Without seeing the implementation of coin_enabled(), it is unclear whether this is a hardening improvement or a fix for a security-relevant bypass, but the pattern suggests it closes a gap where disabled coins could previously be used.

AI review queuedMerge remote-tracking branch 'agent/benma-agent/checked-rust-translations'by Marko Bencun · 1db22746 · Nov 11, 2026 · 15 filesMessage 50 · ThinLow 29Details
Commit message · Marko Bencun

Merge remote-tracking branch 'agent/benma-agent/checked-rust-translations'

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Low 29/100

This commit hardens how translated user-facing messages are selected in the BitBox02 hardware wallet firmware. It introduces compile-time checks that reject messages missing from the English translation catalog and that verify the number of placeholders in formatted strings. The change prevents accidental silent fallback to English and mismatched format arguments, which could otherwise confuse users or make security prompts misleading. It is a defensive hardening patch rather than a fix for a known exploitable vulnerability.

AI review queuedrust: restore variable-output Blake2bby benma's agent · 316c2779 · Nov 10, 2026 · 5 filesMessage 68 · AdequateInformational 12Details
Commit message · benma's agent

rust: restore variable-output Blake2b

The earlier crypto update replaced Blake2bVar with generic, fixed-output
Blake2b instances for Cardano, increasing the firmware size.

Restore variable-output hashing on the upgraded API with a small buffered
wrapper around Blake2bVarCore. Preserve the 20-, 28- and 32-byte digests while
recovering 472 bytes of ROM in the BitBox02 Multi firmware.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 12/100

This commit is a code-size optimization for the BitBox02 hardware wallet's Cardano support. It replaces several fixed-output Blake2b hash implementations with a single small wrapper that can produce different output lengths at runtime. The change is framed as saving 472 bytes of firmware storage and includes unit tests verifying the new wrapper matches the old outputs exactly. There is no indication in the commit that this fixes a security bug or changes security behavior.

AI review queuedrust: update time and anyhowby benma's agent · f835df71 · Nov 10, 2026 · 235 filesMessage 68 · AdequateLow 33Details
Commit message · benma's agent

rust: update time and anyhow

The pinned time and anyhow versions have RustSec advisories. Upgrade these independent
dependencies and time's support crates while leaving the crypto dependency graph
unchanged.

Keep the lockfile and vendored sources in sync with the selected versions.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
signing or wallet pathsecond-pass: broader security terminologysecond-pass: unusually broad changesecond-pass: security-sensitive path
AI analysis · Low 33/100

This commit updates two helper Rust libraries (anyhow and time) inside the BitBox02 firmware source tree because those libraries had published security advisories (RustSec). The change is a routine dependency upgrade, not a fix for a new bug in BitBox's own code. It mostly swaps in newer, already-public library versions and refreshes the vendored copies and lockfiles. The security benefit is removing known-vulnerable dependency versions from the build, but the commit itself does not introduce or patch any exploit in BitBox02 firmware.

AI review queuedui: speed up BB02 text renderingby benma's agent · 75e0346e · Oct 26, 2026 · 3 filesMessage 68 · AdequateInformational 19Details
Commit message · benma's agent

ui: speed up BB02 text rendering

The LVGL font renderer repeatedly validates every character map,
resolves each glyph separately for width and drawing, and clears pixels
before painting their foreground. This extra work slows BitBox02
counters and animations whose progress depends on the frame rate.

Validate only the selected character map and reuse the glyph descriptor
when drawing. Render glyphs inside their character cell in one pass,
reading packed bitmap bytes sequentially and clearing the surrounding
margins. Keep the general renderer for glyphs that extend beyond their
cell. Use the selected font's line height for fallback positioning and
background clearing.

Treat tabs as one space in the font adapter and pass only the resolved
glyph and selected line height to the drawing function. Tabs now use the
space glyph and advance, including the visible mask glyph in password
fonts. Previously, tabs were blank with twice the space advance.

For the same centered text, "Confirm address", both the SH1107 and
SSD1312 screen drivers give identical instruction counts in this build
(emulated Cortex-M4 instructions, ARM GCC 15.2.1, -Os, LTO):

| Font | Before LVGL | Current LVGL | With optimizations |
| --- | ---: | ---: | ---: |
| regular_9 | 39,677 | 76,687 | 39,096 |
| regular_11 (default) | 49,033 | 87,809 | 47,757 |
| regular_12 | 66,522 | 104,584 | 62,895 |
| password_9 | 41,540 | 81,345 | 43,036 |
| password_12 | 69,005 | 110,131 | 67,464 |
| monogram_16 | 47,410 | 62,037 | 47,594 |

This brings instruction counts back to roughly the pre-LVGL level for
this sample (-5.5% to +3.6%). These are emulated instruction counts, not
hardware timings or frame rates; display transfers and other work in a
frame are excluded.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
defensive validationsecond-pass: broader security terminology
AI analysis · Informational 19/100

This commit is a performance optimization for drawing text on the BitBox02 hardware wallet screen. It makes text rendering faster by reducing repeated work and changing how tabs are displayed (now a single space width instead of double). The changes are accompanied by new unit tests. There is no clear security vulnerability here, but any change to low-level screen drawing code carries a small risk of visual glitches or unexpected behavior.

AI review queuedMerge remote-tracking branch 'agent/benma-agent/btc-prevtx-input-hash-length'by Marko Bencun · 8023d571 · Oct 22, 2026 · 1 fileMessage 50 · ThinModerate 59Details
Commit message · Marko Bencun

Merge remote-tracking branch 'agent/benma-agent/btc-prevtx-input-hash-length'

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Moderate 59/100

This commit adds a safety check in the BitBox02 hardware wallet's Bitcoin transaction signing code. When the device processes a previous transaction supplied by the host computer, it now verifies that each input's previous-output hash is exactly 32 bytes long before using it. Without this check, a malformed or attacker-crafted hash of the wrong length could have been fed into the transaction hasher, potentially leading to incorrect transaction signatures or unexpected device behavior. The change is defensive and includes new tests covering hash lengths of 0, 31, and 33 bytes.

AI review queuedbtc: validate prevtx input hash lengthby benma's agent · 7ae83b0d · Oct 21, 2026 · 1 fileMessage 78 · AdequateModerate 59Details
Commit message · benma's agent

btc: validate prevtx input hash length

Previous transaction inputs were hashed without checking that their
previous output hashes were 32 bytes. This allowed malformed transaction
data to pass verification when the host supplied the matching transaction
hash.

Reject these inputs with InvalidInput before hashing their fields.

78/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
defensive validationsigning or wallet pathsecond-pass: near security thresholdsecond-pass: security-sensitive path
AI analysis · Moderate 59/100

This commit fixes a missing length check in the BitBox02 hardware wallet's Bitcoin transaction signing code. When verifying a previous transaction supplied by the host computer, the device was hashing the previous output hash without first confirming it was the expected 32 bytes. A malicious or buggy host could supply a shortened or lengthened hash that still matched a transaction hash the device itself computed, letting malformed data pass verification. The patch now rejects any hash that is not exactly 32 bytes before hashing it.

AI review queuedMerge remote-tracking branch 'agent/benma-agent/unstable-key-sorting'by Marko Bencun · ae548ef4 · Oct 19, 2026 · 2 filesMessage 50 · ThinInformational 24Details
Commit message · Marko Bencun

Merge remote-tracking branch 'agent/benma-agent/unstable-key-sorting'

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Informational 24/100

This commit replaces Rust's stable sort with an unstable sort in three places inside the BitBox02 firmware. Stable and unstable sorts produce the same output when all items are different, but can differ when there are duplicate items. In two places (multisig xpub hashing and pkscript building), the sorted data is hashed or turned into a Bitcoin script, so any change in ordering could change the resulting wallet fingerprint or transaction address. In the third place (Cardano signing keypaths), the list is deduplicated right after sorting, so duplicates are removed anyway. The change is likely intended to save a small amount of memory or runtime, but it is a partial patch: the commit message gives no explanation, and there is no visible follow-up to ensure callers never rely on stability for duplicate entries.

AI review queuedMerge remote-tracking branch 'agent/benma-agent/compact-biguint'by Marko Bencun · 8e6b0760 · Oct 19, 2026 · 4 filesMessage 50 · ThinInformational 19Details
Commit message · Marko Bencun

Merge remote-tracking branch 'agent/benma-agent/compact-biguint'

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Informational 19/100

This commit is a code-size optimization, not a security fix. It replaces generic num-bigint decimal formatting and multiplication/division routines in the Ethereum signing code with smaller, hand-written scalar versions. The goal is to reduce the firmware binary size by avoiding large arithmetic helpers. A new CI check was added to prevent these heavy symbols from creeping back in. There is no evidence in the commit of a vulnerability, exploit, or security incident.

AI review queuedMerge remote-tracking branch 'agent/benma-agent/fee-percentage-rounding'by Marko Bencun · d15c46b3 · Oct 19, 2026 · 2 filesMessage 50 · ThinInformational 21Details
Commit message · Marko Bencun

Merge remote-tracking branch 'agent/benma-agent/fee-percentage-rounding'

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Informational 21/100

This commit fixes how the BitBox02 hardware wallet rounds a fee percentage shown on screen. The old code used a standard floating-point rounding function that could produce wrong results for values very close to a rounding boundary, and it also added unwanted floating-point code to the firmware binary. The new code does the rounding with integer arithmetic and clamps out-of-range or invalid inputs. The visible effect is a slightly different displayed fee percentage in edge cases; there is no direct evidence this could be used to steal funds or run unauthorized code.

AI review queuedMerge remote-tracking branch 'agent/benma-agent/compact-erc20-storage'by Marko Bencun · 69660056 · Oct 19, 2026 · 5 filesMessage 50 · ThinInformational 17Details
Commit message · Marko Bencun

Merge remote-tracking branch 'agent/benma-agent/compact-erc20-storage'

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Informational 17/100

This commit is a code-size optimization for how the BitBox02 hardware wallet stores ERC-20 token metadata (token symbols, decimals, and contract addresses). It replaces a simpler but larger table with a compact, bit-packed lookup table generated at build time. There is no direct evidence in the commit that this fixes a security bug; it appears to be a firmware-size reduction refactor. The only user-visible code change is switching from a static string reference to an owned String for the token unit, which is a consequence of the new packed storage format.

AI review queuedeth: reduce big-integer code sizeby benma's agent · 05e80656 · Oct 15, 2026 · 3 filesMessage 68 · AdequateInformational 12Details
Commit message · benma's agent

eth: reduce big-integer code size

Generic num-bigint formatting and multiplication retain routines for much
larger integers than Ethereum needs. Avoiding those routines saves 6,420
bytes in BitBox02 multi firmware, reducing it from 661,912 to 655,492 bytes
without changing dependencies.

Convert decimal digits with division and remainder by 10u32. Use this for
amount formatting and EIP-712 integer text, preserving the sign of signed
values. Calculate transaction fees by consuming the gas-limit bytes from
most to least significant, using shifts, scalar products, and additions.
Both changes are needed to remove the general multiplication routines,
which generic decimal conversion also uses.

Keep arbitrary-precision arithmetic, input validation, decimal placement,
trimming, and EIP-712 sign extension unchanged. The scalar loops favor
code size and can perform more iterations and temporary allocations.

Add the eliminated formatting, multiplication, and division symbols to the
firmware CI check so future call sites cannot silently bring them back.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 12/100

This commit is a code-size optimization for the BitBox02 hardware wallet firmware. It replaces generic big-integer formatting and multiplication with smaller, hand-written scalar loops specifically sized for Ethereum's needs. There is no security fix or vulnerability being patched; the goal is to reduce firmware size by about 6,420 bytes while keeping the same arithmetic results.

AI review queuedeth: cover large-number formatting and feesby benma's agent · c1375689 · Oct 15, 2026 · 2 filesMessage 78 · AdequateInformational 12Details
Commit message · benma's agent

eth: cover large-number formatting and fees

Add focused regression cases before changing large-number formatting and
fee calculations to reduce firmware size.

Compare the signed and unsigned decimal helpers directly with
num-bigint's formatting. Cover zero, digit boundaries, embedded and
trailing zeroes, large unsigned values, a 257-bit transaction total, and
negative values through the minimum signed 256-bit value.

Compare both fee formulas with direct BigUint multiplication using zero,
one, mixed bytes, and maximum inputs. Keep these cases separate from the
implementation change so they apply to both versions.

78/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 12/100

This commit only adds new automated tests for Ethereum fee calculation and large-number decimal formatting. It does not change any production code, so it cannot by itself introduce or fix a security bug. The tests are described by the author as regression tests to prepare for a future formatting and fee-calculation change that aims to reduce firmware size.

AI review queuedutil: extract big-integer decimal formattingby benma's agent · 9e999101 · Oct 15, 2026 · 2 filesMessage 78 · AdequateInformational 19Details
Commit message · benma's agent

util: extract big-integer decimal formatting

Give signed and unsigned integer-to-text conversion dedicated entry
points so it can be tested directly, separately from amount formatting
and EIP-712 message encoding.

Route existing callers through bigint_to_string() and
biguint_to_string(). Both helpers still delegate to num-bigint's
to_string(), preserving the existing behavior.

78/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 19/100

This commit is a straightforward code cleanup: it pulls out existing big-number-to-text conversion into named helper functions so they can be tested directly. The actual behavior is unchanged because the new helpers still call the same underlying library method (num-bigint's to_string()). There is no security fix or vulnerability here.

AI review queuedMerge remote-tracking branch 'agent/benma-agent/btc-validate-prevout-hash'by Marko Bencun · 5352b8b9 · Oct 13, 2026 · 1 fileMessage 50 · ThinModerate 60Details
Commit message · Marko Bencun

Merge remote-tracking branch 'agent/benma-agent/btc-validate-prevout-hash'

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
defensive validationsigning or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Moderate 60/100

This commit adds a safety check in the BitBox02 hardware wallet's Bitcoin transaction signing code. It now rejects transaction inputs whose 'previous output hash' (a transaction identifier) is not exactly 32 bytes long. Previously, only a zero-value input was rejected. The change prevents malformed or attacker-crafted inputs with wrong hash lengths from being processed during signing. A new test verifies the device correctly refuses these invalid inputs.

AI review queuedworkflow: allow displayable UTF-8 messagesby NickeZ Agent · e5db4da4 · Oct 8, 2026 · 3 filesMessage 78 · AdequateLow 36Details
Commit message · NickeZ Agent

workflow: allow displayable UTF-8 messages

Accented message text is encoded as hex or rejected even when the
BitBox02 fonts can display it. Show safe UTF-8 messages directly when
the confirmation font contains every glyph, retaining the hex
fallback for malformed or unsupported message bytes.

Apply the same character rules to Ethereum typed strings and payment
request memos. Reject typed strings when the display font lacks a
glyph, and cover accepted Unicode, unsafe characters, and missing
glyphs in the workflow tests.

78/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 36/100

This commit changes how the BitBox02 hardware wallet decides whether to show a message to the user as readable text or as hex. Previously, only plain ASCII was shown as text; accented characters and other UTF-8 were always shown as hex. Now the device checks whether each character exists in its display font. If every character can be drawn, the message is shown normally; otherwise it falls back to hex. The same font check is also applied to Ethereum typed-message strings and payment-request memos, which now reject unsupported characters instead of accepting them. The change is a user-experience improvement with a small security angle: it reduces the chance that a user is confused by hex-encoded text that they cannot read, and it prevents attackers from sneaking in invisible or misleading characters in contexts where they were previously accepted.

AI review queuedMerge branch 'nickez/high-fee-warning-wording'by Niklas Dusenlund · d2df29d1 · Oct 1, 2026 · 7 filesMessage 45 · ThinInformational 15Details
Commit message · Niklas Dusenlund

Merge branch 'nickez/high-fee-warning-wording'

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit only changes the wording of an on-screen warning shown to users when a transaction fee is unusually high. The old message read 'The fee is X%\nthe send amount.' and now reads 'Fee is X%\nof the send amount.' The same change is applied to a related warning about fees relative to all inputs. No security logic, thresholds, or calculations are modified.

AI review queuedMerge branch 'cedwies/agentsMD'by Cedric Wiese · 62e6ee12 · Oct 1, 2026 · 1 fileMessage 35 · OpaqueInformational 15Details
Commit message · Cedric Wiese

Merge branch 'cedwies/agentsMD'

35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
documentation-only discountmerge-commit duplicate discountsecond-pass: opaque commit message
AI analysis · Informational 15/100

This commit only updates the project's internal coding guidelines document (AGENTS.md). It adds advice about keeping sensitive data in heap-backed storage and avoiding reallocations after writing sensitive data, because discarded memory allocations are not automatically wiped. There is no actual code change, no bug fix, and no reported vulnerability being addressed.