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

Lower-prioritybuild: add distclean for environment switchesby NickeZ Agent · 6d5a7c4e · Nov 16, 2026 · 2 filesMessage 80 · StrongTriage 0Details
Commit message · NickeZ Agent

build: add distclean for environment switches

Switching between host and container builds requires clearing
Python packages and build artifacts from the previous environment.
The existing clean target leaves the repository virtualenv in place.

Add a phony distclean target that depends on clean and removes .venv.
Document running it before switching environments and bootstrapping
again in the new environment.

80/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Lower-prioritysimulator-graphical: add --port optionby Tomas Vrba · a540c993 · Nov 12, 2026 · 1 fileMessage 68 · AdequateTriage 0Details
Commit message · Tomas Vrba

simulator-graphical: add --port option

The headless simulator already takes --port; the graphical one always
bound 15423, so two instances could only run side by side in separate
network namespaces. Those are unavailable in most CI containers.

The default stays 15423.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
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.

Lower-priorityMerge branch 'nickez-agent/fix-language-status-clippy'by Niklas Dusenlund · b38873c0 · Nov 12, 2026 · 1 fileMessage 50 · ThinTriage 0Details
Commit message · Niklas Dusenlund

Merge branch 'nickez-agent/fix-language-status-clippy'

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
merge-commit duplicate discount
Lower-priorityi18n: check language change success messageby NickeZ Agent · ce46ae5c · Nov 12, 2026 · 1 fileMessage 68 · AdequateTriage 8Details
Commit message · NickeZ Agent

i18n: check language change success message

The direct translation call for the language change success message is
rejected by the i18n Clippy rules, causing CI to fail.

Use the checked translation macro to validate the message against the
catalog at compile time. The displayed text and language selection remain
unchanged.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
defensive validation
Security candidatebuild: use IPv4 for container downloadsby NickeZ Agent · bc434dcf · Nov 12, 2026 · 1 fileMessage 80 · StrongInformational 15Details
Commit message · NickeZ Agent

build: use IPv4 for container downloads

GitHub Actions' hosted Ubuntu runners do not support IPv6 connectivity.
When the LLVM signing-key download resolves to IPv6, it fails with
"Network is unreachable" and prevents the development image from building.

Force IPv4 for APT and the Dockerfile's wget and curl downloads so they
use the network available on the CI runners.

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
signing boundary
AI analysis · Informational 15/100

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 security fix.

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.

Lower-priorityMerge remote-tracking branch 'agent/benma-agent/noise-contributory-check'by Marko Bencun · 325d681a · Nov 12, 2026 · 3 filesMessage 50 · ThinTriage 0Details
Commit message · Marko Bencun

Merge remote-tracking branch 'agent/benma-agent/noise-contributory-check'

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
merge-commit duplicate discount
Security candidateMerge branch 'translate-passphrase-on-host'by Marko Bencun · 4dfa26b4 · Nov 12, 2026 · 3 filesMessage 45 · ThinInformational 15Details
Commit message · Marko Bencun

Merge branch 'translate-passphrase-on-host'

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
access controlboot or update pathmerge-commit duplicate discount
AI analysis · Informational 15/100

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 can be shown in German or other supported languages. There is no security vulnerability here; it is a routine code-quality and user-interface improvement.

Lower-priorityMerge commit 'refs/pull/2194/head' of https://github.com/BitBoxSwiss/bitbox02-firmwareby Marko Bencun · 9b7ed1ac · Nov 12, 2026 · 2 filesMessage 58 · ThinTriage 0Details
Commit message · Marko Bencun

Merge commit 'refs/pull/2194/head' of https://github.com/BitBoxSwiss/bitbox02-firmware

58/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
merge-commit duplicate discount
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.

Lower-prioritybuild: unify Python setup with bootstrapby NickeZ Agent · 4619bff7 · Nov 11, 2026 · 9 filesMessage 90 · StrongTriage 0Details
Commit message · NickeZ Agent

build: unify Python setup with bootstrap

Fresh firmware builds can regenerate protobuf bindings with whichever
protoc and mypy-protobuf happen to be on PATH. This can change generated
code or require a newer runtime, while separate local and CI setup makes
the tool versions easy to diverge.

Have make bootstrap create or reuse the repository .venv and install
Python dependencies, including protoc 21.2 and mypy-protobuf 3.6.0, from
py/requirements.txt. Install the checkout's bitbox02 package in editable
mode so scripts use its current APIs and pick up local changes without
reinstallation. Top-level Make commands prefer that environment so
builds use the installed tools without shell activation.

Run bootstrap in the shared CI build, test and lint jobs, letting it
initialize submodules and configure Cargo. Use the same requirements in
the development image, track them as an image input, and bump the
container version to 60. Document the common setup for host and container
development.

90/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Mentions testing or verification
Security candidateMerge remote-tracking branch 'agent/benma-agent/rust-audit-upgrades'by Marko Bencun · daa2ff28 · Nov 11, 2026 · 300 filesMessage 50 · ThinLow 25Details
Commit message · Marko Bencun

Merge remote-tracking branch 'agent/benma-agent/rust-audit-upgrades'

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
cryptography-sensitive pathseed or entropy pathparser or protocol pathmerge-commit duplicate discount
AI analysis · Low 25/100

This is a large dependency upgrade commit for the BitBox02 firmware, primarily updating vendored Rust cryptography and utility crates (such as aead, anyhow, chacha20poly1305, sha2, etc.) and adding build flags to use smaller 32-bit and compact software-only backends. The commit itself is a routine maintenance/audit upgrade merge; it does not introduce an obvious vulnerability in the diff shown, but any large dependency bump carries a risk of subtle breaking changes or supply-chain issues. There is no vendor statement or external advisory supplied that identifies this commit as a security fix or as addressing a known 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.

Security candidaterust: upgrade crypto dependencies togetherby benma's agent · 25bc564c · Nov 10, 2026 · 300 filesMessage 68 · AdequateLow 38Details
Commit message · benma's agent

rust: upgrade crypto dependencies together

RustSec advisories require newer crypto dependencies. Upgrade P-256 and all consumers of
the shared RustCrypto traits together so the migration does not introduce parallel
crypto versions.

Use the upstream bip32-ed25519 v0.2.2 tag and share DER 0.8 with bitbox-securechip.
Adapt the remaining digest, HMAC, AEAD and P-256 APIs while preserving key derivation,
signatures and Noise wire behavior. Retain key and keystream zeroization and inline
Noise storage.

sha2 0.11 replaces the force-soft-compact Cargo feature with quoted compiler cfg values.
Select the compact software backend in Cargo, CMake and CI to preserve the firmware size
optimization. CMake must pass the inner quotes through to rustc, so enable VERBATIM on
the Rust build commands. Split CARGOFLAGS into separate arguments and expand optional
argument lists so quoting does not combine multiple options or pass empty arguments.

Refresh the lockfile and vendored sources. Remove the direct Keccak dependency now that
sha3 uses compact loops by default.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
secret or key materialsigning boundarycryptography-sensitive pathseed or entropy pathsigning or wallet pathparser or protocol path
AI analysis · Low 38/100

This is a large maintenance update for the BitBox02 hardware wallet's Rust cryptography libraries. The developers upgraded many crypto-related dependencies (such as those handling SHA-2 hashing, AEAD encryption, BLAKE2, and Ed25519 key derivation) to newer versions required by RustSec security advisories. They also adjusted build settings to keep the firmware small and preserve existing security behavior, such as clearing sensitive key material from memory. The commit itself is a routine, security-motivated dependency refresh rather than a fix for an active, exploitable bug in the device.

Lower-priorityrust: use 32-bit crypto arithmeticby benma's agent · 31b00726 · Nov 10, 2026 · 3 filesMessage 78 · AdequateTriage 0Details
Commit message · benma's agent

rust: use 32-bit crypto arithmetic

The crypto-bigint backend defaults to 64-bit limbs on ARMv7, increasing the size of the
firmware's P-256 arithmetic.

Select 32-bit limbs in Cargo, CMake and CI to reduce firmware size while preserving
cryptographic outputs. Use the same backend for host tests so they exercise the firmware
arithmetic.

78/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Security candidaterust: prepare crypto callers for upgradesby benma's agent · df4284d6 · Nov 10, 2026 · 7 filesMessage 73 · AdequateInformational 15Details
Commit message · benma's agent

rust: prepare crypto callers for upgrades

The crypto dependency upgrade changes digest and hash APIs. Use caller forms supported
by both dependency generations so these behavior-preserving adaptations can be reviewed
separately.

Express the fixed Cardano hash sizes in the types and consume the single-use backup MAC.
Keep random and salt outputs in their existing zeroizing allocations. Add the expected
P-256 public key alongside the existing signature vector.

73/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Names security-relevant behavior explicitly
Why it was queued
signing boundaryseed or entropy pathsigning or wallet path
AI analysis · Informational 15/100

This commit is a routine code cleanup in the BitBox02 firmware's Rust code. It changes how cryptographic hashing functions are called so the project can upgrade a dependency later without breaking anything. There is no indication of a security bug being fixed or introduced.

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.

Security candidaterust: replace Noise crypto adaptersby benma's agent · 89f51cf9 · Nov 10, 2026 · 16 filesMessage 68 · AdequateLow 32Details
Commit message · benma's agent

rust: replace Noise crypto adapters

The noise-rust-crypto dependency ties the Noise adapters to an older
RustCrypto dependency set, blocking the planned dependency upgrades.

Own the SHA-256, ChaCha20-Poly1305 and sensitive-buffer adapters in
bitbox-noise so their dependencies can be updated with the workspace.
Keep the existing sha2 and chacha20poly1305 versions, Noise wire behavior,
and inline zeroizing storage.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
cryptography-sensitive path
AI analysis · Low 32/100

This commit replaces an external cryptography adapter library with the project's own in-house version for the secure communication layer (Noise protocol) used in the BitBox02 hardware wallet. The stated reason is to unblock future dependency upgrades, not to fix a known bug or vulnerability. The new code closely mirrors the old implementation and adds test vectors to verify correct behavior, but any change to cryptographic code carries a risk of subtle mistakes that could weaken secure connections.

Security candidatei18n: add missing passphrase on host translationsby Sebastian · 3ba5f42d · Nov 9, 2026 · 3 filesMessage 68 · AdequateInformational 18Details
Commit message · Sebastian

i18n: add missing passphrase on host translations

Passphrase on host related translations were missing.

Existing translation for "Please try again" was bypassed in unlock.rs,
fixed as well.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
access controlboot or update path
AI analysis · Informational 18/100

This commit is a localization (translation) fix. It adds missing translated text strings for the 'passphrase on host' feature and makes the unlock code use those translated strings instead of hard-coded English text. There is no evidence of a security vulnerability being fixed; it is a user-interface completeness and internationalization improvement.

Lower-priorityMerge remote-tracking branch 'agent/benma-agent/describe-stage0'by Marko Bencun · b27f5f68 · Nov 4, 2026 · 1 fileMessage 50 · ThinTriage 0Details
Commit message · Marko Bencun

Merge remote-tracking branch 'agent/benma-agent/describe-stage0'

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
merge-commit duplicate discount
Lower-priorityscripts: add stage0 inspection toolby benma's agent · 3be0c5f1 · Nov 4, 2026 · 1 fileMessage 76 · AdequateTriage 8Details
Commit message · benma's agent

scripts: add stage0 inspection tool

Stage0 binaries need to be identified from their embedded descriptor,
without relying on their filenames.

Add scripts/describe_stage0.py to validate the image size, descriptor
magic, product ID, and flags, and print the product, version, build mode,
and SHA-256 hash.

Split out from #2101.

76/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
defensive validation