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
148commits · 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 48 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.

Security candidatebitbox-core-utils: make salt::hash_data return 32 bytesby Marko Bencun · 385f1773 · Apr 16, 2026 · 3 filesMessage 65 · AdequateInformational 15Details
Commit message · Marko Bencun

bitbox-core-utils: make salt::hash_data return 32 bytes

For better clarity and to remove needless try_into().unwrap().

65/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
Why it was queued
boot or update path
AI analysis · Informational 15/100

This is a small internal code cleanup in the BitBox02 firmware. It changes a helper function that computes SHA-256 hashes so that it returns a fixed 32-byte array instead of a variable-length vector. The only effects are removing an unnecessary type conversion and making the code clearer. There is no security bug being fixed here.

Lower-priorityhal/securechip: make kdf output 32 bytesby Marko Bencun · 6ea21ad5 · Apr 16, 2026 · 8 filesMessage 45 · ThinInformational 18Details
Commit message · Marko Bencun

hal/securechip: make kdf output 32 bytes

For better clarity.

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI analysis · Informational 18/100

This commit is a small code cleanup in the BitBox hardware wallet firmware. It changes the way a 32-byte secret produced by the secure chip's key-derivation function (KDF) is represented in code, switching from a variable-length vector to a fixed 32-byte array. The commit message says this is 'for better clarity.' There is no direct evidence in the commit or supplied references that this fixes a security vulnerability.

Lower-priorityhal/securechip: make kdf input 32 bytesby Marko Bencun · d509583f · Apr 16, 2026 · 9 filesMessage 60 · AdequateInformational 15Details
Commit message · Marko Bencun

hal/securechip: make kdf input 32 bytes

It is only used with that size, and simplifies the async port of that
function later.

60/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
AI analysis · Informational 15/100

This commit is a routine code cleanup, not a security fix. It changes a key-derivation function so it only accepts exactly 32-byte inputs instead of any length up to 127 bytes. The function was already only ever called with 32-byte inputs, so behavior does not change. The stated reason is to make a later code rewrite easier.

Lower-priorityoptiga: add async bridge and counter readby Marko Bencun · 503ee06f · Apr 16, 2026 · 16 filesMessage 68 · AdequateInformational 11Details
Commit message · Marko Bencun

optiga: add async bridge and counter read

Expose the shared OPTIGA util instance to Rust and route\nmonotonic_increments_remaining() through the async command\nbridge. This keeps the first async step small while exercising\nthe bridge with one real read operation.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
AI analysis · Informational 11/100

This commit is a routine firmware refactoring: it moves a single secure-chip counter read from a synchronous C function into a new asynchronous Rust wrapper. There is no indication of a security bug being fixed or introduced. The change is architectural groundwork for future async secure-chip operations.

Security candidaterust: rename bitbox02-noise -> bitbox-noiseby Marko Bencun · 6a206d68 · Apr 15, 2026 · 15 filesMessage 45 · ThinInformational 15Details
Commit message · Marko Bencun

rust: rename bitbox02-noise -> bitbox-noise

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
seed or entropy path
AI analysis · Informational 15/100

This commit is a simple rename of a Rust crate from 'bitbox02-noise' to 'bitbox-noise'. The code itself is unchanged; only file paths, package names, and import references are updated. There is no security fix or vulnerability introduced.

Security candidateUse HAL random for noise key generationby Marko Bencun · 4e982183 · Apr 15, 2026 · 11 filesMessage 85 · StrongLow 27Details
Commit message · Marko Bencun

Use HAL random for noise key generation

bitbox02-rust should not depend on bitbox02-specific random types just
to initialize the Noise responder state. Move Noise key generation
onto bitbox_hal::Random and let bitbox02-noise initialize the
responder handshake from HAL-provided randomness.

This removes the old Random32/BB02Random32 plumbing. That trait
existed only because the handshake state was generic over a DH type
whose genkey() path generated the responder ephemeral internally. Once
the responder ephemeral is treated as explicit init input instead, the
state no longer needs a device-specific RNG type parameter. In the
final API, init() takes a HAL random source and derives that ephemeral
key there, which keeps the dependency boundary at bitbox-hal while
preserving the same handshake flow.

85/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Names security-relevant behavior explicitly
Why it was queued
entropy or randomnessseed or entropy path
AI analysis · Low 27/100

This commit is a code cleanup in the BitBox02 firmware's Rust code. It changes how random numbers are supplied when creating cryptographic keys for the Noise protocol, moving from a device-specific random type to a more generic hardware abstraction layer (HAL) random source. The commit message and diff do not describe this as fixing a security bug; it reads as an architectural refactor to simplify dependencies. There is no direct evidence in the commit that the old code was exploitable or that any vulnerability was fixed.

Lower-priorityremove cmake run-rust-unit-tests custom targetby Marko Bencun · 32779ab1 · Apr 15, 2026 · 3 filesMessage 55 · ThinInformational 15Details
Commit message · Marko Bencun

remove cmake run-rust-unit-tests custom target

55/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
AI analysis · Informational 15/100

This change is purely about how the project runs its internal Rust unit tests and regenerates protobuf files. It removes a CMake custom target called 'rust-test' and instead makes the Makefile's 'run-rust-unit-tests' target run cargo directly, while adding a separate 'generate-protobufs' target. There is no change to the firmware code that runs on the device, no bug fix, and no security patch.

Lower-priorityhal: put noise key functions into Memory HALby Marko Bencun · 567efc40 · Apr 15, 2026 · 5 filesMessage 45 · ThinInformational 12Details
Commit message · Marko Bencun

hal: put noise key functions into Memory HAL

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI analysis · Informational 12/100

This commit is a routine code reorganization. It moves functions that manage Noise protocol cryptographic keys (used for secure communication between the BitBox device and apps) into a common hardware abstraction layer called the Memory HAL. The actual behavior of these functions is not changed; they are simply routed through a new trait interface so the same code can be reused across different BitBox hardware models and test environments. There is no indication this fixes a security bug.

Lower-priorityAGENTS.md: remove run-rust-unit-testsby Marko Bencun · e3e2d3f7 · Apr 15, 2026 · 1 fileMessage 55 · ThinInformational 15Details
Commit message · Marko Bencun

AGENTS.md: remove run-rust-unit-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
documentation-only discount
AI analysis · Informational 15/100

This commit is a documentation-only change in the project's AGENTS.md file. It removes a shorthand make target ('make run-rust-unit-tests') and replaces it with the longer underlying cargo command that developers should run directly. There is no code change, no firmware change, and no security fix or vulnerability introduced.

Lower-priorityAGENTS.md: no dev-exec.sh for `cargo` commandsby Marko Bencun · 50b264a2 · Apr 15, 2026 · 1 fileMessage 60 · AdequateInformational 15Details
Commit message · Marko Bencun

AGENTS.md: no dev-exec.sh for `cargo` commands

They run on the host without ARM toolchain.

60/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
Why it was queued
documentation-only discount
AI analysis · Informational 15/100

This commit only updates developer-facing documentation (AGENTS.md). It tells contributors they can run Rust's cargo commands directly on their computer instead of inside the project's Docker/development wrapper script. No firmware code, build scripts, or security behavior changed.

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.

Lower-priorityethereum/amount: fix typo in docstringby Marko Bencun · e9f51e00 · Apr 13, 2026 · 1 fileMessage 45 · ThinInformational 15Details
Commit message · Marko Bencun

ethereum/amount: fix typo in docstring

And switch to a more realistic unit :)

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI analysis · Informational 15/100

This commit only changes placeholder text in documentation and unit tests. It replaces the fake token name 'LOL' with 'ETH' in code comments and test expectations. No real program behavior is altered, and there is no security relevance.

Lower-priorityhal/securechip: mark monotonic_increments_remaining asyncby Marko Bencun · 40b3c548 · Apr 13, 2026 · 6 filesMessage 50 · ThinInformational 15Details
Commit message · Marko Bencun

hal/securechip: mark monotonic_increments_remaining async

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI analysis · Informational 15/100

This commit is a routine internal refactoring: it changes one function in the secure-chip hardware abstraction layer from synchronous to asynchronous. It does not fix a bug, change any security behavior, or alter how data is validated. It only adjusts how the firmware waits for the secure chip's answer when reporting how many times a one-way counter can still be incremented.

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.

Lower-prioritypayment_request: truncate long swap-to amountsby Marko Bencun · 8d362ffc · Apr 13, 2026 · 1 fileMessage 68 · AdequateLow 25Details
Commit message · Marko Bencun

payment_request: truncate long swap-to amounts

Same as amount.rs in Ethereum.

We apply it regardless of the coin target, as we can't enumerate
them (any ERC20 token etc. is possible).

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
AI analysis · Low 25/100

This commit changes how the BitBox02 hardware wallet displays very long swap-to amounts on its screen. Previously, an extremely long amount string could be shown in full, potentially overflowing the display or making the user interface unusable. Now, long decimal portions are truncated with '...' so the integer part and a fixed number of decimal digits remain visible. This is a UI hardening change rather than a fix for a remote exploit.

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.

Lower-prioritysecurechip: port model to Rustby Marko Bencun · 9559e931 · Apr 11, 2026 · 4 filesMessage 45 · ThinInformational 15Details
Commit message · Marko Bencun

securechip: port model to Rust

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI analysis · Informational 15/100

This commit is a straightforward code cleanup: it moves a tiny function that reports the hardware security chip model from C to Rust. The function always returned the same fixed value (OPTIGA_TRUST_M_V3), and after the change it still returns that same fixed value. There is no security-relevant change in behavior.

Security candidateadd new bitbox-core-utils workspace crateby Marko Bencun · e12dae77 · Apr 10, 2026 · 13 filesMessage 83 · StrongInformational 15Details
Commit message · Marko Bencun

add new bitbox-core-utils workspace crate

Move the salt and random helpers out of bitbox02-rust into a
new workspace crate that depends on bitbox-hal.
Add bitbox-platform-host as a dev-dependency there so the same
unit tests can run against the host fakes, and update the
bitbox02-rust and bitbox02-rust-c consumers to use the new
crate.

83/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Names security-relevant behavior explicitly
Why it was queued
seed or entropy pathboot or update path
AI analysis · Informational 15/100

This commit is a routine code reorganization: it moves two small helper modules (one for generating random bytes, one for salting/hashing data) from an existing Rust crate into a new shared workspace crate named bitbox-core-utils. The actual logic, algorithms, and behavior are copied unchanged; only the file paths and import names are updated. There is no indication this fixes or introduces a security vulnerability.

Lower-priorityeth: validate payment request coin purchase coin type and keypathby Marko Bencun · 7e443b27 · Apr 9, 2026 · 2 filesMessage 50 · ThinModerate 61Details
Commit message · Marko Bencun

eth: validate payment request coin purchase coin type and keypath

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
defensive validation
AI analysis · Moderate 61/100

This commit adds missing safety checks for Ethereum payment requests on the BitBox02 hardware wallet. Previously, when a user paid a merchant via a Bitcoin payment request that included an Ethereum coin-purchase memo, the device did not verify that the requested Ethereum coin type and the keypath matched a supported mainnet network. A malicious or buggy payment request could therefore ask the device to prove ownership of an address on an unexpected or test Ethereum network, potentially misleading the user or weakening the security guarantee of the payment request. The patch now rejects unsupported coin types (notably testnet coin type 1) and ensures the keypath's second component matches the declared coin type.

Lower-prioritybitbox03: activate app-u2f in bitbox-halby Marko Bencun · 5028149d · Apr 9, 2026 · 1 fileMessage 45 · ThinInformational 15Details
Commit message · Marko Bencun

bitbox03: activate app-u2f in bitbox-hal

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI analysis · Informational 15/100

This commit changes a single line in a Rust package configuration file. It makes the 'app-u2f' feature of the bitbox03 package also enable the 'app-u2f' feature in the underlying 'bitbox-hal' hardware abstraction library. There is no visible bug fix or security patch in the diff itself; it appears to be a build/feature wiring change.

Lower-priorityscripts/format: only format git-tracked filesby Marko Bencun · 03f69906 · Apr 8, 2026 · 1 fileMessage 60 · AdequateInformational 15Details
Commit message · Marko Bencun

scripts/format: only format git-tracked files

It also formatted all headers in src/rust/target etc., slowing it down.

60/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
AI analysis · Informational 15/100

This commit changes a code-formatting helper script so it only processes files tracked by Git, instead of scanning every file in the source directories. The old behavior accidentally formatted files inside build/cache folders such as src/rust/target, which only made the script slower. There is no security issue here.

Security candidatehal: move TestingRandom to platform hostby Marko Bencun · 57d7c80d · Apr 8, 2026 · 4 filesMessage 45 · ThinInformational 15Details
Commit message · Marko Bencun

hal: move TestingRandom to platform host

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
seed or entropy path
AI analysis · Informational 15/100

This commit simply moves a test-only fake random number generator from one internal Rust module to another. The code is identical and is only used in automated tests running on a developer's computer, not in the real BitBox02 hardware wallet firmware. There is no security issue.

Lower-prioritysalt: use TestingMemory in testsby Marko Bencun · 225097e6 · Apr 8, 2026 · 1 fileMessage 55 · ThinInformational 15Details
Commit message · Marko Bencun

salt: use TestingMemory in tests

55/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
AI analysis · Informational 15/100

This commit only updates internal unit tests to use a more specific mock object (TestingMemory instead of TestingHal). It does not change any production code, security behavior, or user-facing functionality. There is no security issue here.

Security candidatehal: add random, factory_randomness, drop random_32_bytesby Marko Bencun · 47454d61 · Apr 8, 2026 · 27 filesMessage 55 · ThinLow 45Details
Commit message · Marko Bencun

hal: add random, factory_randomness, drop random_32_bytes

55/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Names security-relevant behavior explicitly! No meaningful explanatory body
Why it was queued
seed or entropy pathsigning or wallet path
AI analysis · Low 45/100

This commit changes how the BitBox02 hardware wallet generates random numbers used to create secret keys and encrypt stored data. Previously, the firmware used a single 32-byte random value from the microcontroller. After this change, it mixes three sources: the microcontroller's random generator, the secure chip's random generator, and a fixed 32-byte 'factory randomness' value stored in a special flash memory location. The commit also adds a factory script to write that fixed value into devices during production. The change is a defensive hardening measure, not a fix for an active bug, but it introduces a new dependency: if the factory randomness is not actually random or is reused across devices, it could weaken security instead of strengthening it.