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
149commits · 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 32 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 candidaterust: async unit tests instead of block_onby Marko Bencun · 2560d5d1 · Apr 6, 2026 · 41 filesMessage 55 · ThinInformational 15Details
Commit message · Marko Bencun

rust: async unit tests instead of block_on

Easier to read/write the 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
cryptography-sensitive pathsigning or wallet pathauthentication path
AI analysis · Informational 15/100

This commit is a code-quality refactor for unit tests only. It introduces a small Rust helper macro called async_test::test that lets developers write async test functions directly, instead of manually wrapping async code in a block_on() call. The change touches many test files but does not alter any production firmware behavior, user-facing functionality, or security logic.

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

eth: drop needless RefCell in sign typed msg unit tests

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

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

Lower-prioritysystem test use should_panicby Marko Bencun · 74e433e7 · Apr 6, 2026 · 1 fileMessage 45 · ThinInformational 15Details
Commit message · Marko Bencun

system test use should_panic

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Mentions testing or verification! No meaningful explanatory body
AI analysis · Informational 15/100

This commit is a minor cleanup of an internal Rust unit test. It replaces a manual panic-catching block with Rust's built-in #[should_panic] test attribute. The test still verifies the same behavior: that calling reboot_to_bootloader in a test environment triggers a panic with the message 'reboot_to_bootloader called'. There is no change to production firmware code, no security fix, and no user-facing behavior change.

Lower-priorityswap: make long destination amounts scrollableby Cedric Wiese · c116b0a8 · Apr 6, 2026 · 1 fileMessage 45 · ThinInformational 15Details
Commit message · Cedric Wiese

swap: make long destination amounts scrollable

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

This commit makes a single on-screen message scrollable. When swapping cryptocurrency, the destination amount can be very long and previously may have been cut off or unreadable. The change lets the user scroll through the full text before confirming. There is no security issue visible in the code change itself.

Lower-priorityrust/cbindgen: remove APP_ETH definesby Marko Bencun · f5fcb2f7 · Apr 4, 2026 · 1 fileMessage 45 · ThinInformational 15Details
Commit message · Marko Bencun

rust/cbindgen: remove APP_ETH defines

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

This commit removes leftover build configuration lines related to Ethereum support from a code-generation config file. It does not change any firmware behavior, fix a bug, or alter how user funds or secrets are handled. It appears to be a cleanup change with no security relevance.

Lower-prioritybuild: remove unused APP_ C defsby Marko Bencun · 04261bbc · Apr 3, 2026 · 2 filesMessage 57 · ThinInformational 15Details
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
AI analysis · Informational 15/100

This commit is a routine build cleanup. It removes several unused C preprocessor definitions (APP_BTC, APP_LTC, APP_ETH) from the build files, leaving only APP_U2F. There is no indication this changes runtime behavior or fixes a security issue.

Lower-prioritybuild: remove used nanopb defsby Marko Bencun · 70fcc373 · Apr 3, 2026 · 1 fileMessage 72 · AdequateInformational 15Details
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
AI analysis · Informational 15/100

This commit simply removes two leftover compiler definitions that were used by an old library (nanopb) the project no longer uses. It is a cleanup change with no security relevance.

Lower-priorityoptiga: simplify PAL I2C retriesby Marko Bencun · 035bfddf · Apr 2, 2026 · 1 fileMessage 68 · AdequateInformational 18Details
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 analysis · Informational 18/100

This commit removes an internal retry loop from the low-level I2C driver that talks to the Optiga secure chip in the BitBox02 hardware wallet. Previously, every I2C write/read would automatically retry up to 25 times with 2 ms delays. Now it tries once and lets the upper-layer Optiga library decide whether to retry. The change is described by the vendor as a simplification that reduces redundant blocking; it is not presented as a security fix and the diff alone does not show an exploitable vulnerability.

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

rust: route delays through HAL timer

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

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

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

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

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

bitbo03/ui: unlock_animation stub

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

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

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

bitbox03/ui: status stub

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

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

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

bitbox03/ui: password stub

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

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

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 · ThinInformational 15Details
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
AI analysis · Informational 15/100

This commit is a simple internal code cleanup. It renames two Rust types from 'UiResponder' and 'UiResult' to the shorter 'Responder' and 'Result', and updates the files that use those names. There is no change to what the code does, no bug fix, and no security improvement or regression visible in the diff.

Lower-priorityatecc: don't call securechip_kdfby Marko Bencun · 77764c72 · Apr 1, 2026 · 1 fileMessage 60 · AdequateInformational 15Details
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
AI analysis · Informational 15/100

This is a tiny internal code cleanup in the BitBox02 firmware. It replaces one function call with another that does the exact same thing, just without going through a dispatcher. There is no visible security effect.

Lower-prioritysimulator-graphical-bb03: make communication_timeout_reset a no-opby Marko Bencun · 209e9bc1 · Apr 1, 2026 · 1 fileMessage 50 · ThinInformational 15Details
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
AI analysis · Informational 15/100

This commit changes a single placeholder function in the graphical simulator for the BitBox03 hardware wallet. The function, which previously would crash the simulator if called, now does nothing. The change only affects test/simulation code, not real device firmware, and there is no indication it fixes a security issue.

Lower-prioritybitbox02_rust: enable app/firmware features in simulatorby Marko Bencun · b2bee384 · Apr 1, 2026 · 2 filesMessage 73 · AdequateInformational 15Details
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
AI analysis · Informational 15/100

This commit is a build/test configuration fix for the BitBox02 graphical simulator. It enables the same cryptocurrency app features (Bitcoin, Litecoin, Ethereum, Cardano) and firmware feature in the simulator that were already available in the real device build. The change only affects the simulator's compiled feature flags and dependency lock file; it does not change any user-facing behavior or fix a security vulnerability.

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 · ThinInformational 15Details
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
AI analysis · Informational 15/100

This commit removes a leftover test/debug feature from the graphical simulator for the BitBox03 hardware wallet. The simulator used to automatically switch to the logo screen after 5,000 internal 'wake-up' events. That behavior was only for local testing and never affected real devices or user funds.

Lower-prioritybitbox03/ui: split UI from async machineby Marko Bencun · 894dc727 · Apr 1, 2026 · 8 filesMessage 45 · ThinInformational 15Details
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
AI analysis · Informational 15/100

This commit is a routine internal code cleanup for the BitBox02/BitBox03 firmware's user interface. It moves the confirmation dialog code into its own file and introduces a small reusable helper for handling button-press results in async Rust code. There is no indication this fixes a security bug or changes user-visible security behavior.

Lower-priorityAGENTS: do not use bitbox_lvgl::ffi directlyby Marko Bencun · 9a12e594 · Apr 1, 2026 · 1 fileMessage 45 · ThinInformational 15Details
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
AI analysis · Informational 15/100

This commit only updates the project's AGENTS.md file, which is a set of instructions for AI coding assistants. It adds a guideline telling agents not to directly use low-level FFI bindings to the LVGL UI library from feature code, and instead to use safe wrappers. No source code, firmware behavior, or security controls were changed.

Lower-prioritybitbox03/ui: add confirm screen demo implby Marko Bencun · 40a0fb53 · Apr 1, 2026 · 5 filesMessage 80 · StrongInformational 15Details
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 analysis · Informational 15/100

This commit adds a new on-screen confirmation dialog for the BitBox03 hardware wallet and the low-level Rust-to-LVGL event-callback plumbing needed to make it work. It is a feature implementation, not a security patch. The code introduces memory-management patterns (reference-counted callbacks and a screen guard that pops the UI when a future is dropped) that are intended to make the code safer, but the commit itself does not fix any disclosed vulnerability.

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

bitbox03/ui: implement reset()

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

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

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

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

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

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

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.