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 1 minute 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 queuedeth/sign: add missing mock_unlock in testsby Marko Bencun · 0d7cabab · Apr 14, 2026 · 1 fileMessage 55 · ThinInformational 15Details
Commit message · Marko Bencun

eth/sign: add missing mock_unlock in tests

55/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit only adds missing test setup calls to two automated unit tests in the Ethereum signing code. It does not change any production firmware behavior, user-facing functionality, or security logic. There is no indication this fixes a vulnerability or affects real devices.

AI review queuedapi/payment_request: serialize ETH value as little endianby Marko Bencun · be2d62c8 · Apr 14, 2026 · 2 filesMessage 73 · AdequateModerate 60Details
Commit message · Marko Bencun

api/payment_request: serialize ETH value as little endian

SLIP-24:

> amount (coinType-dependent length): fixed-length encoding of the amount of the requested output in little-endian byte order, expressed in the smallest unit of the given cryptocurrency (satoshis, wei, etc.). The length of the encoding is equal to the length used natively for the given coinType to encode amounts, e.g. 8 bytes for Bitcoin-like coins and 32 bytes for EVM assets.

73/100 · AdequateMessage clarity
✓ Specific, 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 · Moderate 60/100

This commit fixes a serialization bug in the BitBox02 firmware's payment request validation for Ethereum transactions. Previously, Ethereum payment amounts were encoded as big-endian (most-significant-byte-first), but the SLIP-24 standard requires them to be little-endian (least-significant-byte-first). Because the device signs the payment request using one byte order but the validation code used another, a payment request could be generated that the device would accept even if the actual transaction amount did not match what the user saw on screen. The fix changes the code to serialize Ethereum amounts as 32-byte little-endian values, matching the standard and preventing amount mismatches.

AI review queuedCHANGELOG: add swapsby Marko Bencun · a200c9bf · Apr 13, 2026 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · Marko Bencun

CHANGELOG: add swaps

28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
documentation-only discountsecond-pass: opaque commit message
AI analysis · Informational 15/100

This commit only adds a single line to the product changelog describing a new feature: support for swaps in payment requests. There are no code changes, no bug fixes, and no security-related content in the diff.

AI review queuedui: add swap componentby Marko Bencun · 3948cb63 · Apr 13, 2026 · 15 filesMessage 43 · ThinInformational 12Details
Commit message · Marko Bencun

ui: add swap component

Similar to confirm_transction.c, dedicated to the swap screen.

43/100 · ThinMessage clarity
✓ Subject identifies a change✓ Provides an explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 12/100

This commit adds a new on-screen user-interface component for confirming cryptocurrency swaps. It is a feature addition that refactors how swap confirmations are displayed, replacing a generic confirmation screen with a dedicated swap screen. There is no direct evidence in the commit that this fixes a security vulnerability or introduces a new attack path.

AI review queuedadd bitbox-securechip-sys bindings crate add bitbox-securechip crateby Marko Bencun · a92647ce · Apr 8, 2026 · 21 filesMessage 65 · AdequateInformational 12Details
Commit message · Marko Bencun

add bitbox-securechip-sys bindings crate add bitbox-securechip crate

Safe/idiomatic wrappers around bitbox-securechip-sys.

65/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
Why it was queued
second-pass: unusually broad change
AI analysis · Informational 12/100

This commit is a code reorganization: it moves the Rust bindings and wrappers for the BitBox02's secure chip (ATECC/Optiga) out of the general bitbox02-sys crate into two new dedicated crates, bitbox-securechip-sys and bitbox-securechip. It does not change the underlying C secure-chip implementation or add new user-facing behavior. The change is architectural cleanup, not a security fix or vulnerability.

AI review queuedbtc/payment_request: fix error status iconby Marko Bencun · dd28e0ea · Apr 7, 2026 · 2 filesMessage 45 · ThinInformational 20Details
Commit message · Marko Bencun

btc/payment_request: fix error status icon

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

This commit fixes a tiny user-interface bug on the BitBox02 hardware wallet. When a Bitcoin or Ethereum payment request was invalid, the device was accidentally showing a success icon (checkmark) instead of an error icon. The change flips one boolean argument so the screen now correctly shows an error icon. It does not change whether the transaction is rejected—the device still refuses to sign.

AI review queuedCHANGELOG: mark v9.26.0by Marko Bencun · 916c12fc · Apr 7, 2026 · 1 fileMessage 38 · OpaqueInformational 15Details
Commit message · Marko Bencun

CHANGELOG: mark v9.26.0

38/100 · OpaqueMessage clarity
✓ Subject identifies a change✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
documentation-only discountsecond-pass: opaque commit message
AI analysis · Informational 15/100

This commit only updates the CHANGELOG.md file to mark the release of firmware version 9.26.0. It does not change any source code, configuration, or executable files. There is no security-relevant change in the diff itself.

AI review queuedfix unit testby Marko Bencun · 3593da89 · Apr 7, 2026 · 1 fileMessage 38 · OpaqueInformational 15Details
Commit message · Marko Bencun

fix unit test

Regression from e39367090.

38/100 · OpaqueMessage clarity
✓ Subject identifies a change✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100

This is a one-line change updating a public key value inside a unit test. It is not a security fix and does not change any production code. The commit message says it fixes a unit test regression from an earlier commit.

AI review queuedpayment_request: update swapkit pubkeyby Marko Bencun · e3936709 · Apr 7, 2026 · 1 fileMessage 35 · OpaqueInformational 17Details
Commit message · Marko Bencun

payment_request: update swapkit pubkey

35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 17/100

This commit simply swaps out one public key for another in a list of trusted payment-request identities used by the BitBox02 hardware wallet's swap feature. There is no code change beyond replacing the hard-coded key. On its own, the diff does not show a vulnerability being fixed; it is best understood as a routine key rotation or partner update.

AI review queuedpayment_request: remove "send to" screenby Marko Bencun · cde7286c · Apr 7, 2026 · 3 filesMessage 78 · AdequateLow 28Details
Commit message · Marko Bencun

payment_request: remove "send to" screen

Redundant with the coin purchase memo info, except for the account
number, but we choose to not show that for better UX. Keypath is still
validated.

The removed tests are redundant with tests of test_validate().

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 · Low 28/100

This commit removes an on-screen confirmation that told users which account would receive funds during a cryptocurrency swap. The remaining screen still shows the amount and destination coin type, but no longer shows the specific account number. The underlying cryptographic keypath validation is still performed, so the technical security check remains. The change is presented by the developer as a user-experience improvement, not as a security fix.

AI review queuedeth: drop needless RefCell in sign typed msg unit testsby Marko Bencun · 1452594b · Apr 6, 2026 · 1 fileMessage 60 · AdequateInformational 15Details
Commit message · Marko Bencun

eth: drop needless RefCell in sign typed msg unit tests

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

This commit only cleans up internal unit tests for Ethereum typed-message signing. It removes an unnecessary Rust borrow-checking wrapper (RefCell) from test code, with no change to the actual firmware behavior that users interact with. There is no security fix or vulnerability here.

AI review queuedrust: route delays through HAL timerby Niklas Dusenlund · f99cf2f4 · Apr 2, 2026 · 22 filesMessage 68 · AdequateInformational 11Details
Commit message · Niklas Dusenlund

rust: route delays through HAL timer

Add a Timer interface to bitbox-hal and pass timer handles into
startup and UI flows instead of calling device-local delay modules.

Move the simulator thread-based timer implementation into
bitbox-platform-host, remove the old bitbox02 and bitbox03 delay
modules, and drop the leftover LVGL timer wrapper.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
second-pass: unusually broad change
AI analysis · Informational 11/100

This commit is a routine internal refactoring of how the BitBox02/BitBox03 firmware handles delays. It moves delay logic behind a new shared 'Timer' interface and removes old device-specific delay modules. There is no indication in the commit that this fixes a security bug or introduces a vulnerability; it appears to be a code-cleanup and architecture change.

AI review queuedbitbo03/ui: unlock_animation stubby Marko Bencun · 291bc936 · Apr 2, 2026 · 1 fileMessage 35 · OpaqueInformational 15Details
Commit message · Marko Bencun

bitbo03/ui: unlock_animation stub

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

This commit replaces a Rust 'todo!()' placeholder with a stub that displays a 'TODO' status message during an unlock animation. It is a routine development stub, not a security fix or vulnerability. There is no evidence of malicious behavior or security relevance.

AI review queuedbitbox03/ui: status stubby Marko Bencun · fb8bd4c3 · Apr 2, 2026 · 8 filesMessage 28 · OpaqueInformational 15Details
Commit message · Marko Bencun

bitbox03/ui: status stub

28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100

This commit is a routine feature implementation for the BitBox03 hardware wallet. It adds a new status screen (success/error) and an internal delay/timer helper used to show that screen for two seconds. There is no security fix or vulnerability present in the diff.

AI review queuedbitbox03/ui: password stubby Marko Bencun · 478fac57 · Apr 2, 2026 · 2 filesMessage 35 · OpaqueInformational 15Details
Commit message · Marko Bencun

bitbox03/ui: password stub

35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
second-pass: broader security terminologysecond-pass: opaque commit message
AI analysis · Informational 15/100

This commit replaces a placeholder 'not yet implemented' stub with a working on-screen keyboard for entering text and passwords on the BitBox02/03 hardware wallet. It is a normal feature implementation, not a security fix or vulnerability.

AI review queuedbitbox03/ui: implement reset()by Marko Bencun · 38e728ad · Mar 31, 2026 · 1 fileMessage 35 · OpaqueInformational 19Details
Commit message · Marko Bencun

bitbox03/ui: implement reset()

35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 19/100

This commit replaces an unimplemented placeholder ('todo!()') for a screen reset function with actual code that clears the user-interface stack. It is a normal completion of missing functionality. There is no direct evidence in the commit that this fixes an exploitable security bug, but leaving a reset operation unimplemented could previously have left stale UI state in place during sensitive workflows.

AI review queuedpy/bitbox02: add BitBox03 to platform enum and info parsingby Marko Bencun · bcd3c558 · Mar 31, 2026 · 1 fileMessage 50 · ThinInformational 15Details
Commit message · Marko Bencun

py/bitbox02: add BitBox03 to platform enum and info parsing

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

This commit simply teaches the BitBox Python library to recognize a new hardware device model, the BitBox03. It adds the model name to an internal list and tells the library how to interpret the device-info bytes sent by a BitBox03. There is no security fix or vulnerability here—just routine support for a new product variant.

AI review queuedAdd Rust U2FHID HWW transportby Niklas Dusenlund · 635c9609 · Mar 31, 2026 · 24 filesMessage 68 · AdequateLow 37Details
Commit message · Niklas Dusenlund

Add Rust U2FHID HWW transport

Introduce a new `bitbox-u2fhid` crate that reassembles U2FHID
reports and routes vendor commands to the HWW async USB flow.

Update the async USB executor to hand out owned responses, reset
stale state on cancel, and size the report queue for a full worst-
case U2FHID message.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
second-pass: unusually broad change
AI analysis · Low 37/100

This commit adds a new Rust-based USB transport layer for BitBox hardware wallets. It reassembles U2F HID messages and routes vendor commands to the existing async USB task system. The change also hardens the async executor by handing out owned responses instead of copying into caller buffers, and by resetting stale state when a task is cancelled or times out. There is no vendor statement that this fixes a security bug; it reads as a feature/refactoring commit with defensive hardening.

AI review queuedethereum: support payment requests for eip1559by Cedric Wiese · 38d26b42 · Mar 30, 2026 · 5 filesMessage 45 · ThinLow 28Details
Commit message · Cedric Wiese

ethereum: support payment requests for eip1559

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 28/100

This commit adds support for EIP-1559 Ethereum transactions in the BitBox02's payment-request (swap) feature. It lets users verify and sign Ethereum and ERC-20 token swaps that include a merchant payment request, similar to what already existed for Bitcoin. The change is a feature addition, not a fix for a known vulnerability.

AI review queuedethereum: extract total fee verification helpersby Cedric Wiese · f3aeae28 · Mar 29, 2026 · 1 fileMessage 55 · ThinInformational 15Details
Commit message · Cedric Wiese

ethereum: extract total fee verification helpers

55/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
defensive validationsigning or wallet pathsecond-pass: near security thresholdsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit is a simple code cleanup: it moves two existing blocks of Ethereum fee-verification logic into new helper functions without changing what the code actually does. There is no visible security fix or behavior change.

AI review queuedApi: Make payment_request generic instead of bitcoin specificby Cedric Wiese · b7e8f580 · Mar 26, 2026 · 2 filesMessage 50 · ThinInformational 19Details
Commit message · Cedric Wiese

Api: Make payment_request generic instead of bitcoin specific

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

This commit is a code cleanup that makes the payment-request code less Bitcoin-specific so it can be reused for other coins in the future. It does not add new user-facing features or fix a known bug. The changes move amount formatting and coin-type handling from the shared payment-request module into the Bitcoin signing code, and adjust internal test helpers. There is no indication in the commit that this fixes a security vulnerability.

AI review queuedMove SmartEEPROM into HAL EEPROMby Niklas Dusenlund · 29e9781d · Mar 25, 2026 · 25 filesMessage 78 · AdequateInformational 17Details
Commit message · Niklas Dusenlund

Move SmartEEPROM into HAL EEPROM

Add a dedicated Eeprom trait to bitbox-hal and implement it for both the device HAL and the Rust test HAL.

Use the new trait for setup, init, disable, and unlock-attempt persistence so those responsibilities no longer sit in Memory or System.

78/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
second-pass: unusually broad change
AI analysis · Informational 17/100

This commit is a code reorganization: it moves SmartEEPROM handling (a flash-backed memory feature) out of the general Memory and System modules into a new dedicated Eeprom trait in the hardware abstraction layer. The same underlying functions are still called, and the unlock-attempt counter behavior is preserved. There is no obvious security bug introduced, but the change touches code that protects device reset and unlock-attempt limits, so it deserves careful review to confirm no behavior was accidentally dropped.

AI review queuedApi: Move payment_request from bitcoin to api moduleby Cedric Wiese · b627ca50 · Mar 24, 2026 · 4 filesMessage 50 · ThinInformational 15Details
Commit message · Cedric Wiese

Api: Move payment_request from bitcoin to api module

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

This commit is a pure code refactor: it moves the payment_request module from the bitcoin-specific directory up to the general API directory. The actual logic, security checks, and behavior of the payment request code are unchanged. No new vulnerabilities are introduced by this move.

AI review queuedbitcoin/script: inline bitcoin varint encodingby Marko Bencun · 00a1da05 · Mar 23, 2026 · 6 filesMessage 68 · AdequateInformational 15Details
Commit message · Marko Bencun

bitcoin/script: inline bitcoin varint encoding

Remove the local bitcoin::script helper module and call rust-bitcoin's
VarInt serializer directly at each Bitcoin API use site.

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 is a small code cleanup change. It removes a local helper function that wrapped rust-bitcoin's variable-length integer serializer, and instead calls rust-bitcoin's serializer directly at each place it is used. The actual bytes produced are identical, so this does not change behavior or fix a security issue.

AI review queuedSwap: Add swap ui flow (BTC/LTC -> ETH-like)by Cedric Wiese · cc45c948 · Mar 19, 2026 · 2 filesMessage 45 · ThinLow 37Details
Commit message · Cedric Wiese

Swap: Add swap ui flow (BTC/LTC -> ETH-like)

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 37/100

This commit adds a new on-device user interface flow for cryptocurrency swaps, where a user can exchange Bitcoin or Litecoin for an Ethereum-like coin through a payment request. The code adds validation rules and user confirmation screens so the hardware wallet can show what is being swapped and where the received coins will go. The change is a feature addition with defensive checks, not a clear fix for an existing vulnerability.