CommitWatch RSS
BB
← All projectsBitBox

BitBox02 firmware

Firmware and bootloader for BitBox02 signing devices.

BitcoinHardware walletsNormal
Source repository ↗
Repository coverage

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

193security candidates127second-pass queue200AI analyses
28commits · 30 days
47commits · 60 days
312commits · 180 days
647commits · 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
65Strong · 80–100
281Adequate · 60–79
230Thin · 40–59
71Opaque · 0–39
23security 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 Bencun390117119258
benma's agent892831162
Niklas Dusenlund1112929059
cedwies1256063
Tomas Vrba944074
Cedric Wiese1234049
Jad811062
thisconnect211072
benma211074
Niklas111035
Yasser Aziza111070
Patrick Steiger111045
Analysis record

Published AI watches

Last scanned 52 minutes ago

Moderate 60 AI analysisMessage 90 · Strong
BB BitBoxBitBox02 firmware BitcoinHardware wallets

backup: validate decoded seed length

This update fixes a bug in how the BitBox02 hardware wallet reads backup files from an SD card. A tampered backup file could claim to contain a seed longer than the 32-byte limit, which previously caused the device to panic (crash) when li…

Out-of-bounds/panic condition in backup parsingMissing input validation on decoded protobuf fieldSD-card backup file could be attacker-controlled
80baf1eeby benma's agent+34−01 file
Vendor flagged security relevance
Open full analysis →Source commit ↗
Low 39 AI analysisMessage 73 · Adequate
BB BitBoxBitBox02 firmware BitcoinHardware wallets

rust: initialize C output buffers

This commit fixes a class of low-level memory-safety bugs where Rust code was given buffers containing uninitialized bytes. Rust's rules require every byte of a slice to be initialized, even if the function will overwrite them. Passing uni…

Undefined behavior at C/Rust FFI due to uninitialized buffers being treated as Rust slicesPotential optimizer-dependent behavior from violating Rust slice initialization rulesHardening of cryptographic output paths (SHA-256, HMAC-SHA256, HMAC-SHA512)
511018eaby benma's agent+52−2713 files
Vendor flagged security relevance
Open full analysis →Source commit ↗
High 74 AI analysisMessage 78 · Adequate
BB BitBoxBitBox02 firmware BitcoinHardware wallets

eth: limit EIP-712 recursion depth

This commit adds a hard limit on how deeply nested Ethereum typed-message (EIP-712) structures can be when the BitBox02 hardware wallet signs them. Without the limit, an attacker could craft a message type that refers to itself over and ov…

Adds explicit recursion-depth cap to attacker-controlled input parsingPre-validates schema roots before host callbacks or user confirmationProtects against stack exhaustion / denial-of-service from deeply nested EIP-712 types
4ccadcc0by benma's agent+196−451 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 50 · Thin
BB BitBoxBitBox02 firmware BitcoinHardware wallets

py: extract bootloader connection

This commit is a minor code cleanup in a Python helper script. It moves existing bootloader connection logic into a small nested helper function to satisfy a style checker (pylint's limit on the number of return statements). No behavior ch…

886113d0by benma's agent+10−61 file
No security note in commit
Open full analysis →Source commit ↗
Low 42 AI analysisMessage 78 · Adequate
BB BitBoxBitBox02 firmware BitcoinHardware wallets

Warn before truncated value displays

This commit adds a warning screen to the BitBox02 hardware wallet whenever a long message or value is about to be shown in a truncated form. Previously, the device could silently cut off the end of very long transaction details, message da…

UI truncation warning added before oversized confirmation bodiesCentralized body-size limit to keep Rust and C UI limits in syncReplaced duplicated warning logic with shared confirm_value helper
5b3aee6fby benma's agent+266−4710 files
No security note in commit
Open full analysis →Source commit ↗
Informational 12 AI analysisMessage 45 · Thin
BB BitBoxBitBox02 firmware BitcoinHardware wallets

releases: add v9.26.2, v9.26.3 and v9.26.4

This commit is a routine release-management update. It adds signed build assertions for three new BitBox02 firmware versions (9.26.2, 9.26.3, 9.26.4) and updates the release documentation and build helper script. The build script now delet…

No firmware source code is modifiedNo cryptographic primitives or protocols are changedNo bug fixes or vulnerability mitigations are present in the diff
eed2e68eby Marko Bencun+79−116 files
No security note in commit
Open full analysis →Source commit ↗
Informational 21 AI analysisMessage 68 · Adequate
BB BitBoxBitBox02 firmware BitcoinHardware wallets

eth: loosen EIP-712 identifier validation

This firmware update relaxes the rules for valid Ethereum typed-data (EIP-712) names so they can contain a colon (:), which some decentralized apps use as a namespace separator. Member names still cannot contain colons. The change is prese…

Input validation relaxation for externally supplied EIP-712 type namesExplicit claim that ':' cannot forge encodeType boundariesMember-name validation remains strict
9703d8d9by Marko Bencun+50−43 files
No security note in commit
Open full analysis →Source commit ↗
Moderate 59 AI analysisMessage 69 · Adequate
BB BitBoxBitBox02 firmware BitcoinHardware wallets

Limit SD erase file size

This commit fixes a bug in how the BitBox02 hardware wallet wipes files from its SD card. Before erasing a file, the device now checks the file's reported size against a safe maximum. Without this check, a tampered SD card could claim a fi…

CVE-2026-6682 referenced in commit messageMalformed FAT directory entry could cause excessive overwrite loopDenial-of-service via SD card tampering
2453f528by Marko Bencun+4−01 file
Vendor flagged security relevance
Open full analysis →Source commit ↗
High 70 AI analysisMessage 66 · Adequate
BB BitBoxBitBox02 firmware BitcoinHardware wallets

Validate mounted FAT geometry

This update adds a safety check when the BitBox02 hardware wallet mounts a microSD card. A malicious or deliberately malformed FAT filesystem could trick the device's file-system library into placing user data inside attacker-controlled bo…

Fixes integer-wrap / geometry confusion in FAT mount logicAdds explicit post-mount validation of filesystem metadataPrevents data area from landing inside attacker-controlled FAT sectors
01c017d6by Marko Bencun+21−01 file
Vendor flagged security relevance
Open full analysis →Source commit ↗
Low 27 AI analysisMessage 69 · Adequate
BB BitBoxBitBox02 firmware BitcoinHardware wallets

Update FatFs to R0.16

This commit updates the third-party FatFs file-system library inside the BitBox02 firmware from version R0.14b to R0.16 plus an upstream patch. The change is a routine dependency refresh: it replaces the vendored source files with the newe…

Third-party dependency update (FatFs R0.14b -> R0.16+p1)No explicit security claim in commit messageNo CVE or advisory referenced in commit or supplied references
9f2b493dby Marko Bencun+3842−256979 files
No security note in commit
Open full analysis →Source commit ↗
Low 34 AI analysisMessage 59 · Thin
BB BitBoxBitBox02 firmware BitcoinHardware wallets

api: add BitBoxSync

This commit adds a brand-new firmware feature called BitBoxSync, which lets the BitBox02 hardware wallet participate in a sync service by proving its identity, signing login/admin intents, and decrypting namespace encryption keys. The code…

New cryptographic API surface added to the hardware wallet (Ed25519, X25519, HKDF, AEAD)Vendored third-party crate `hkdf` introduced into the firmware supply chainNew user-confirmation flow for signing sync intents; one operation (UnwrapNamespaceDek) deliberately skips confirmation
54cdb54dby Marko Bencun+2883−2230 files
No security note in commit
Open full analysis →Source commit ↗
Informational 0 AI analysisMessage 45 · Thin
BB BitBoxBitBox02 firmware BitcoinHardware wallets

blupgrade: update stage1 binaries to v1.2.2

This commit simply swaps in newer pre-built bootloader stage1 binary files (version 1.2.2 replacing 1.2.1) for four BitBox02 hardware variants and updates the corresponding checksum list. The actual code inside the new binary files is not …

5940a800by Marko Bencun+8−86 files
No security note in commit
Open full analysis →Source commit ↗
Moderate 59 AI analysisMessage 50 · Thin
BB BitBoxBitBox02 firmware BitcoinHardware wallets

bootloader/stage1: fix erase handling for partially erased blocks

This update fixes the BitBox02 bootloader's firmware-erase routine. Previously, when erasing leftover padding after a firmware update, the bootloader started erasing at the exact page where the firmware ended. Because flash memory can only…

Bootloader firmware erase routine could erase a flash block containing both firmware and paddingFix aligns erase start to erase-block boundary and re-checks erased state before erasingChangelog describes the change as a fix for 'partially erased flash blocks'
b31206a8by Marko Bencun+23−83 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 45 · Thin
BB BitBoxBitBox02 firmware BitcoinHardware wallets

blupgrade: add stage0/stage1 production binaries

This commit adds production bootloader upgrade files for the BitBox02 hardware wallet and updates build scripts to use them. It is a routine asset-management change: replacing placeholder development hashes with real signed production bina…

8db4b0dcby Marko Bencun+26−1720 files
No security note in commit
Open full analysis →Source commit ↗
Informational 20 AI analysisMessage 83 · Strong
BB BitBoxBitBox02 firmware BitcoinHardware wallets

blupgrade: keep dev stage1 unsigned

This commit fixes a build script used only for development/testing versions of the BitBox02 bootloader upgrade. It makes the development-stage1 bootloader images unsigned again, while keeping production images fully signature-verified. The…

Signature verification relaxed only for development buildsProduction payload validation still requires signaturesDevelopment stage0 already skipped stage1 signature verification per commit message
476b90e3by Marko Bencun+9−69 files
No security note in commit
Open full analysis →Source commit ↗
High 76 AI analysisMessage 23 · Opaque
BB BitBoxBitBox02 firmware BitcoinHardware wallets

security improvements

This BitBox02 firmware update is a broad security patch that fixes several independent bugs: it prevents a maliciously oversized USB report from overflowing memory, stops a corrupted Bluetooth pairing database from being read or written wi…

Bounds check added to USB HID Set Report input lengthBLE bond DB length validation hardened against negative and oversized valuesBootloader firmware image size limit relaxed to intended maximum
cbb40634by Marko Bencun+1117−25021 files
Vendor flagged security relevance
Open full analysis →Source commit ↗
Low 46 AI analysisMessage 60 · Adequate
BB BitBoxBitBox02 firmware BitcoinHardware wallets

bootloader: allow full sized images

This commit fixes a bootloader bug where the device rejected firmware updates that used the maximum allowed size. The off-by-one check meant legitimate full-sized firmware images could not be installed, potentially blocking updates. The fi…

Off-by-one input validation in firmware-update pathBootloader change affecting firmware chunk count acceptanceCHANGELOG labels the change as a bugfix for full-sized firmware upgrades
f60b93ccby Marko Bencun+5−33 files
No security note in commit
Open full analysis →Source commit ↗
Moderate 59 AI analysisMessage 28 · Opaque
BB BitBoxBitBox02 firmware BitcoinHardware wallets

Add bootloader update

This is a large firmware commit that adds a new two-stage bootloader update mechanism for the BitBox02 hardware wallet. It replaces the old single bootloader with a small, fixed 'stage0' plus a separately signed 'stage1', and ships a speci…

Bootloader architecture changed from monolithic to two-stage (stage0 + signed stage1).Firmware signature hash now includes a 16-bit product_id, binding firmware to product variant.Root public keys were rotated/replaced with a single set across all products.
3f1f3172by Marko Bencun+5003−52379 files
Vendor flagged security relevance
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 73 · Adequate
BB BitBoxBitBox02 firmware BitcoinHardware wallets

Add flash data backup scripts

This commit adds two helper scripts for developers to back up and restore BitBox02 flash memory areas using a Segger J-Link debugger. The scripts require physical hardware access and a debugging probe, and they are not part of the firmware…

285fa768by Niklas Dusenlund+383−03 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 40 · Thin
BB BitBoxBitBox02 firmware BitcoinHardware wallets

bb03 UI: placeholder BTC signing workflows

This commit replaces unfinished placeholder code (which would crash with 'todo!()') with simple working user-interface placeholders for Bitcoin signing demonstrations. It adds basic on-screen prompts to confirm a recipient/amount and a tot…

f7b0b082by Jad+24−121 file
No security note in commit
Open full analysis →Source commit ↗
Repository ledger

Explore captured commits

Expand any commit for its author, full message, clarity score, changed files, triage signals, analysis, and source link.

Lower-prioritybuild: remove unused APP_ C defsby Marko Bencun · 04261bbc · Apr 3, 2026 · 2 filesMessage 57 · ThinTriage 0Details
Commit message · Marko Bencun

build: remove unused APP_ C defs

57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Lower-prioritybuild: remove used nanopb defsby Marko Bencun · 70fcc373 · Apr 3, 2026 · 1 fileMessage 72 · AdequateTriage 0Details
Commit message · Marko Bencun

build: remove used nanopb defs

PB_ defs were from when we used nanopb, which we dropped a long time ago.

72/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body
Lower-priorityoptiga: simplify PAL I2C retriesby Marko Bencun · 035bfddf · Apr 2, 2026 · 1 fileMessage 68 · AdequateTriage 0Details
Commit message · Marko Bencun

optiga: simplify PAL I2C retries

The Optiga PAL contract is single-attempt: write/read should try once
and then report PAL_I2C_EVENT_SUCCESS, PAL_I2C_EVENT_ERROR, or
PAL_I2C_EVENT_BUSY to the upper layer callback. Upstream PAL examples
do not spin inside pal_i2c_write() and pal_i2c_read(); they leave
retry handling to the Optiga IFX I2C stack above PAL, using a 1 ms
retry interval and up to 200 attempts from
external/optiga-trust-m/include/ifx_i2c/ifx_i2c_config.h:37.

Our local PAL implementation added an extra 25x2ms retry loop around
i2c_m_sync_transfer() in both pal_i2c_write() and pal_i2c_read(). That
made each PAL call block for up to about 50ms before the stack even
saw an error or busy event.

The host library already retries these conditions asynchronously in
the physical layer. Normal register and frame operations set
retry_counter and reschedule ifx_i2c_pal_poll_callback() after
PAL_I2C_EVENT_ERROR or PAL_I2C_EVENT_BUSY. The special slave-address
path also retries around pal_i2c_write() on its own. Keeping the retry
loop in PAL therefore duplicates the library's retry logic and turns
PAL into a blocking poller.

Remove the local retry and sleep loops and perform a single
synchronous i2c_m_sync_transfer() per PAL call instead. This keeps the
PAL aligned with the upstream contract and lets the Optiga stack
decide when and how often to poll.

This change removes redundant blocking from PAL. It does not change
the higher-level optiga_ops synchronous wrappers, which still
busy-wait on the Optiga callbacks.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
AI review queuedrust: route delays through HAL timerby Niklas Dusenlund · f99cf2f4 · Apr 2, 2026 · 22 filesMessage 68 · AdequateTriage 0Details
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 review queuedbitbo03/ui: unlock_animation stubby Marko Bencun · 291bc936 · Apr 2, 2026 · 1 fileMessage 35 · OpaqueTriage 0Details
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 review queuedbitbox03/ui: status stubby Marko Bencun · fb8bd4c3 · Apr 2, 2026 · 8 filesMessage 28 · OpaqueTriage 0Details
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 review queuedbitbox03/ui: password stubby Marko Bencun · 478fac57 · Apr 2, 2026 · 2 filesMessage 35 · OpaqueTriage 0Details
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
Security candidatesecurechip: port securechip.c to Rustby Marko Bencun · 9706ea2c · Apr 2, 2026 · 20 filesMessage 45 · ThinLow 34Details
Commit message · Marko Bencun

securechip: port securechip.c to Rust

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

This commit rewrites the secure-chip abstraction layer from C to Rust. It is a refactoring/porting change: the same underlying ATECC and Optiga hardware drivers are still used, but the dispatch logic that picks between them and the test fake is now implemented in Rust. No new security vulnerability is visible in the diff, but any rewrite of security-critical code carries a risk of subtle behavior changes.

Lower-priorityutil/futures: drop UI completion namesby Marko Bencun · 5bd29ad3 · Apr 2, 2026 · 3 filesMessage 45 · ThinTriage 0Details
Commit message · Marko Bencun

util/futures: drop UI completion names

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-priorityatecc: don't call securechip_kdfby Marko Bencun · 77764c72 · Apr 1, 2026 · 1 fileMessage 60 · AdequateTriage 0Details
Commit message · Marko Bencun

atecc: don't call securechip_kdf

The securechip interface function dispatches to atecc_kdf, no need to
go through the dispatcher.

60/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
Lower-prioritysimulator-graphical-bb03: make communication_timeout_reset a no-opby Marko Bencun · 209e9bc1 · Apr 1, 2026 · 1 fileMessage 50 · ThinTriage 0Details
Commit message · Marko Bencun

simulator-graphical-bb03: make communication_timeout_reset a no-op

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-prioritybitbox02_rust: enable app/firmware features in simulatorby Marko Bencun · b2bee384 · Apr 1, 2026 · 2 filesMessage 73 · AdequateTriage 0Details
Commit message · Marko Bencun

bitbox02_rust: enable app/firmware features in simulator

In bitbox02 graphical simulator, the `simulator-grahical` feature
bitbox02_rust_c enables `firmware` and all the `app-` features.

In bitbox02 graphical simulator, bitbox02_rust_c is not a dep, so
these were all disabled.

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Security candidatesimulator-graphical-bb03: implement Randomby Marko Bencun · f5fae7e6 · Apr 1, 2026 · 3 filesMessage 50 · ThinInformational 15Details
Commit message · Marko Bencun

simulator-graphical-bb03: implement Random

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

This commit implements a placeholder random-number generator inside a graphical simulator for the BitBox03 hardware wallet. It replaces 'todo!' stubs with code that fills 32-byte buffers using the standard Rust 'rand' crate. The change only affects test/simulator code, not the real firmware or any production device, so it does not create a security vulnerability in shipped products. The only concern is that simulator developers must remember this is a non-cryptographic/test RNG and must not copy it into real hardware code.

Lower-prioritysimulator-graphical-bb03: remove test screen popby Marko Bencun · 58d55079 · Apr 1, 2026 · 1 fileMessage 55 · ThinTriage 0Details
Commit message · Marko Bencun

simulator-graphical-bb03: remove test screen pop

55/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
Lower-prioritybitbox03/ui: split UI from async machineby Marko Bencun · 894dc727 · Apr 1, 2026 · 8 filesMessage 45 · ThinTriage 0Details
Commit message · Marko Bencun

bitbox03/ui: split UI from async machine

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-priorityAGENTS: do not use bitbox_lvgl::ffi directlyby Marko Bencun · 9a12e594 · Apr 1, 2026 · 1 fileMessage 45 · ThinTriage 0Details
Commit message · Marko Bencun

AGENTS: do not use bitbox_lvgl::ffi directly

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
documentation-only discount
Lower-prioritybitbox03/ui: add confirm screen demo implby Marko Bencun · 40a0fb53 · Apr 1, 2026 · 5 filesMessage 80 · StrongTriage 0Details
Commit message · Marko Bencun

bitbox03/ui: add confirm screen demo impl

- ScreenGuard is so that the screen is popped when the future is
dropped, e.g. when the client disconnects
- Rc is used for safety just in case the parent object is deleted from
within the callback. We don't expect this to ever be a pattern, but it
would avoid deleting the shared state during callback execution.

80/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode
AI review queuedbitbox03/ui: implement reset()by Marko Bencun · 38e728ad · Mar 31, 2026 · 1 fileMessage 35 · OpaqueTriage 0Details
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 review queuedpy/bitbox02: add BitBox03 to platform enum and info parsingby Marko Bencun · bcd3c558 · Mar 31, 2026 · 1 fileMessage 50 · ThinTriage 7Details
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
Security candidatebitbox03: add local simulator HALby Marko Bencun · f0845590 · Mar 31, 2026 · 7 filesMessage 60 · AdequateInformational 15Details
Commit message · Marko Bencun

bitbox03: add local simulator HAL

- Reuse bitbox-platform-host
- Reuse bitbox03 UI
- For now, keep other subsytems with todo!() stubs

60/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
Why it was queued
seed or entropy path
AI analysis · Informational 15/100

This commit adds a new local simulator for the BitBox03 hardware wallet. It is purely test/development tooling: it wires up fake hardware components (fake memory, fake secure chip, fake SD card, etc.) and leaves many simulator functions as unimplemented 'todo!()' stubs. There is no indication this change affects real device firmware or introduces a security vulnerability.

Lower-priorityhal: move Testing subsystems to new bitbox-platform-host crateby Marko Bencun · c0445ce5 · Mar 31, 2026 · 10 filesMessage 60 · AdequateTriage 0Details
Commit message · Marko Bencun

hal: move Testing subsystems to new bitbox-platform-host crate

To be reused by simulators.

60/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
Lower-prioritysimulator-graphical-bb03: remove bitbox02_rust_c depby Marko Bencun · 7d1ae7d8 · Mar 31, 2026 · 3 filesMessage 50 · ThinTriage 0Details
Commit message · Marko Bencun

simulator-graphical-bb03: remove bitbox02_rust_c dep

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI review queuedAdd Rust U2FHID HWW transportby Niklas Dusenlund · 635c9609 · Mar 31, 2026 · 24 filesMessage 68 · AdequateTriage 0Details
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 review queuedethereum: support payment requests for eip1559by Cedric Wiese · 38d26b42 · Mar 30, 2026 · 5 filesMessage 45 · ThinTriage 12Details
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 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.