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 41 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 candidateMerge remote-tracking branch 'agent/benma-agent/stage0-device-info'by Marko Bencun · 8a65822e · Nov 2, 2026 · 19 filesMessage 50 · ThinInformational 15Details
Commit message · Marko Bencun

Merge remote-tracking branch 'agent/benma-agent/stage0-device-info'

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

This commit adds a new read-only piece of information to the BitBox02 device-info API: the version of the installed 'stage0' bootloader component. It does not change any security-critical behavior, access controls, or cryptographic operations. It is purely an informational/reporting change, with corresponding tests and fake-memory support for development.

Security candidateMerge branch 'cedwies/i18n-firmware'by Cedric Wiese · 57c7be66 · Nov 2, 2026 · 4 filesMessage 45 · ThinInformational 15Details
Commit message · Cedric Wiese

Merge branch 'cedwies/i18n-firmware'

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

This commit only changes on-screen text strings and their translations. It rewords a German firmware-upgrade prompt and splits two English/German message strings across more lines so they fit better on the device display. There is no security-relevant code change.

Security candidateMerge branch 'nickez-agent/delete-wallet-copy'by Niklas Dusenlund · 90584502 · Nov 2, 2026 · 5 filesMessage 45 · ThinInformational 15Details
Commit message · Niklas Dusenlund

Merge branch 'nickez-agent/delete-wallet-copy'

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

This commit only changes the on-screen wording shown when resetting a BitBox02 device. Phrases like 'factory reset' are replaced with 'delete wallet from this device'. The actual reset behavior, code flow, and security checks are unchanged. There is no security fix or vulnerability here.

Security candidatei18n: clarify wallet deletion promptby NickeZ Agent · ff94ecb4 · Nov 2, 2026 · 5 filesMessage 68 · AdequateInformational 15Details
Commit message · NickeZ Agent

i18n: clarify wallet deletion prompt

Make the reset flow explicit about deleting the wallet from this device.
Replace factory reset wording with wallet deletion text in English and
German, including the confirmation title and completion message.

Use short titles and two-line prompts and completion messages for the
device display. Reset behavior is unchanged.

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

This commit only changes the wording shown on the BitBox02 device screen during the wallet reset process. It replaces phrases like 'factory reset' with 'delete wallet from this device' to make the action clearer to users. The actual reset behavior is unchanged, and no security vulnerability is present.

Security candidateapi: expose stage0 version in device infoby benma's agent · 5d6e0ecc · Nov 2, 2026 · 19 filesMessage 68 · AdequateInformational 19Details
Commit message · benma's agent

api: expose stage0 version in device info

Clients cannot determine the installed stage0 version from device info.

Expose the descriptor's numeric image version as an optional
stage0_version field. Leave it absent when no valid stage0 descriptor
is present, and return the integer or None in the Python client.

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 · Informational 19/100

This commit adds a new read-only piece of information to the BitBox02's device-info API response: the version of the installed 'stage0' bootloader component. It does not change any security behavior, access controls, or data handling. It simply lets host software see which stage0 version is present, or omit the field if none is installed. There is no indication this fixes or introduces a vulnerability.

Security candidateblupgrade: refresh development stage1 binariesby benma's agent · a34ffbda · Nov 2, 2026 · 10 filesMessage 73 · AdequateInformational 15Details
Commit message · benma's agent

blupgrade: refresh development stage1 binaries

The development blupgrade targets still embed stage1 images from before
the 1 ms HWW OUT polling change, so installing them does not enable the
faster upload path.

Rebuild the BitBox02 and Nova multi and Bitcoin-only development images
from 56503be44b and update the v1.2.3 assets, CMake paths, and checksums.
Keep their signature slots empty for development stage0.

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 boundarysigning or wallet pathboot or update path
AI analysis · Informational 15/100

This commit updates the development-only bootloader upgrade files for the BitBox02 and Nova hardware wallets. It replaces older test-stage1 bootloader images with newer ones that include a previously made USB communication speed improvement. The change does not affect production devices or introduce a security vulnerability; it is a build/development maintenance update.

Security candidateMerge branch 'nickez-agent/disable-nvm-cache-latest'by Niklas Dusenlund · d43b8ebd · Nov 2, 2026 · 4 filesMessage 50 · ThinModerate 59Details
Commit message · Niklas Dusenlund

Merge branch 'nickez-agent/disable-nvm-cache-latest'

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
boot or update pathmerge-commit duplicate discount
AI analysis · Moderate 59/100

This commit changes how the BitBox02 hardware wallet writes data to its internal flash memory. It disables the microcontroller's flash cache during programming operations, following a manufacturer errata note (Microchip SAM D5x/E5x errata 2.14.1). Without this fix, cached flash reads could interfere with the data being programmed, potentially leading to corrupted writes in firmware updates, bootloader fuses, or the secure EEPROM area that stores device secrets. The change is defensive and addresses a known silicon errata, but the commit itself does not describe a specific exploited vulnerability or security incident.

Security candidatebootloader: scan flash to check for empty appby benma's agent · 5e4e77aa · Nov 2, 2026 · 2 filesMessage 68 · AdequateInformational 18Details
Commit message · benma's agent

bootloader: scan flash to check for empty app

Entering bootloader mode hashes the whole firmware area just to choose
which device setup text to show, even when firmware is present.

Reuse the existing flash scan across the application region.
It stops at the first programmed byte and still checks every byte
when flash is empty. Remove the reference digest and its fixed-size
guard. The condition for showing the setup text remains unchanged.

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

This commit replaces a slow cryptographic hash check with a faster flash scan to decide whether the bootloader should display a first-time setup screen. It is a performance optimization that removes a hard-coded reference digest and its guard. There is no direct evidence in the commit that this fixes a security vulnerability.

Security candidatebootloader: version stage1 and firmware sighashesby benma's agent · a56fc866 · Nov 2, 2026 · 11 filesMessage 95 · StrongLow 47Details
Commit message · benma's agent

bootloader: version stage1 and firmware sighashes

Subsequent firmware must require the intermediate bootloader upgrade
so that stage1 is installed by stage0 that preserves the signed
firmware area.

Prefix both the stage1 and firmware prehashes with 0x01. Old stage0
skips the new stage1 payload and can boot the old-scheme upgrade
firmware; new stage0 installs it after reboot. The new device verifiers
accept only the new schemes.

Set stage1's monotonic version to 2 for v1.2.3. Build-time embedding
verification uses the legacy stage1 prehash below version 2 and the
prefixed prehash from version 2 onward, preserving support for the
bundled v1.2.2 images.

Keep firmware 56 on the existing scheme and select the new scheme
from version 57 in release tooling. Match the client's empty flash
hash to bootloader v1.2.3 and retain historical firmware hashes.
The image format and signing keys are unchanged.

Bundled binaries still need to be rebuilt and stage1 re-signed before
shipping. This sequence applies to production devices, since
development stage0 skips signature checks.

95/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Mentions testing or verification✓ Names security-relevant behavior explicitly
Why it was queued
signing boundaryupdate trustdefensive validationsigning or wallet pathboot or update path
AI analysis · Low 47/100

This commit changes how the BitBox02 bootloader and firmware compute the cryptographic hash used to verify signed updates. It adds a version byte (0x01) to the data that gets hashed before signatures are checked, starting with bootloader v1.2.3 and firmware version 57. The goal is to make old and new verification schemes distinguishable, so an older, less secure bootloader cannot be tricked into accepting a newer firmware image using the old hash format, and vice versa. The change is defensive: it does not fix a known remote exploit, but it hardens the upgrade chain against potential downgrade or cross-version signature-confusion attacks. Existing signing keys and the overall image format stay the same.

Security candidateMerge commit 'refs/pull/2002/head' of https://github.com/BitBoxSwiss/bitbox02-firmwareby Marko Bencun · 69706e52 · Nov 2, 2026 · 1 fileMessage 58 · ThinModerate 57Details
Commit message · Marko Bencun

Merge commit 'refs/pull/2002/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
boot or update pathmerge-commit duplicate discount
AI analysis · Moderate 57/100

This commit rewrites how the BitBox02 bootloader accepts and writes firmware updates. It adds stricter ordering (chunks must now arrive in ascending order), replaces a combined write-and-erase operation with explicit erase-before-write, and verifies that flash is blank before writing. These changes look like hardening against a bug where an attacker or glitch could cause the bootloader to accept out-of-order or repeated firmware chunks, potentially leaving old code in flash or allowing a downgrade/partial overwrite. The commit itself does not say it fixes a security issue, and no independent report is supplied, so the security relevance is inferred from the defensive nature of the changes.

Security candidateu2f: prevent clipping of initialization promptby Cedric Wiese · 3d5da732 · Nov 2, 2026 · 2 filesMessage 45 · ThinInformational 15Details
Commit message · Cedric Wiese

u2f: prevent clipping of initialization prompt

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

This commit fixes a visual text layout issue on the BitBox02 device screen. The message telling users to initialize the device with the BitBoxApp before using U2F was being cut off or clipped because it was too long for one line. The fix splits the text across three shorter lines so it displays correctly. There is no security vulnerability here.

Security candidatei18n: clarify German firmware update promptby Cedric Wiese · 2fb81c05 · Nov 2, 2026 · 2 filesMessage 45 · ThinInformational 15Details
Commit message · Cedric Wiese

i18n: clarify German firmware update prompt

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

This commit simply changes the German wording shown on the device screen during a firmware update, from 'Upgrade fortsetzen?' to 'Firmware aktualisieren?'. It also updates the matching automated test. There is no code behavior change and no security fix.

Security candidatebuild: upload graphical simulator branch buildsby NickeZ Agent · 39d5e33d · Oct 29, 2026 · 1 fileMessage 80 · StrongInformational 15Details
Commit message · NickeZ Agent

build: upload graphical simulator branch builds

Graphical simulator artifacts are only uploaded for push events,
leaving pull request and manually triggered branch builds without
downloadable binaries.

Package and upload Linux x86_64 and macOS ARM64 simulators for every
successful CI build. Preserve executable permissions in tar archives,
check process startup before packaging, and fail uploads when an
archive is missing.

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
credential or privilege statedocumentation-only discount
AI analysis · Informational 15/100

This commit changes the project's automated build workflow so that graphical simulator programs are packaged and uploaded for every successful build, not just for direct pushes to the main branch. It is a build/CI convenience improvement with no apparent security relevance.

Security candidateusb: reduce HWW OUT polling interval to 1 msby benma's agent · 933cbd5b · Oct 28, 2026 · 3 filesMessage 68 · AdequateInformational 15Details
Commit message · benma's agent

usb: reduce HWW OUT polling interval to 1 ms

The 4 ms HWW OUT polling interval limits firmware upload throughput in
stage1. Reduce OUT to 1 ms in firmware and bootloader descriptors to speed
up upgrades, while keeping IN at 4 ms.

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

This commit simply makes the BitBox02 device respond more quickly to firmware upgrade data sent over USB by changing a timing value from 4 milliseconds to 1 millisecond. It is a performance improvement, not a security fix, and does not introduce any obvious security problem.

Security candidateMerge branch 'nickez-agent/locked-devdevice'by Niklas Dusenlund · 8ec7034c · Oct 28, 2026 · 16 filesMessage 45 · ThinLow 37Details
Commit message · Niklas Dusenlund

Merge branch 'nickez-agent/locked-devdevice'

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

This commit reworks how BitBox02/Nova bootloader images are built, adding two new build flags: LOCKED (which enables hardware debug protection and boot protection) and DEVELOPMENT (which controls whether unsigned firmware images are accepted). It also renames the old 'devdevice' terminology to 'development' across scripts and tests. The change is primarily a build-system and naming refactor that introduces a new 'locked development' variant. It is not a patch for an active security vulnerability, but it touches security-relevant bootloader behavior, so care is needed that the wrong combination of flags cannot be accidentally produced or flashed.

Security candidatebuild: support locked development bootloadersby NickeZ Agent · f7009522 · Oct 28, 2026 · 16 filesMessage 85 · StrongLow 34Details
Commit message · NickeZ Agent

build: support locked development bootloaders

Hardware locking was tied to production mode, so development bootloaders
could not enable debug and boot protection while accepting unsigned
images.

Add saved LOCKED and DEVELOPMENT options for BitBox02 and Nova. LOCKED
controls hardware protection; DEVELOPMENT controls signature enforcement
and development markers. Keep unlocked development as the default,
support locked development, and require LOCKED=yes when DEVELOPMENT=no.
BitBox03 continues to accept only the default modes.

Select stage0/stage1 build and probe images from configuration, replacing
the top-level production/development stage aggregates. Preserve existing
artifact names and add development-locked variants. Refresh CMake target
definitions on each build and extend CI to build locked development
bootloaders for both products and stages.

Use BOOTLOADER_DEVELOPMENT in both stages and expose is_development() in
the Python client, retaining is_devdevice() as a deprecated alias. Keep
on-device flags and bundled bootloader images unchanged.

85/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Names security-relevant behavior explicitly
Why it was queued
signing boundaryupdate trustboot or update path
AI analysis · Low 34/100

This commit rewrites how BitBox02/Nova bootloaders are built so that 'hardware locking' and 'development mode' become two independent settings. Previously, locking was only available in production builds. Now developers can build a bootloader that has hardware debug protection enabled while still allowing unsigned (development) firmware. The change also renames internal flags from 'devdevice/production' to 'development/locked', updates build scripts, CI, and the Python flashing tool, and adds tests. It is a build-system and naming refactor rather than a runtime vulnerability fix.

Security candidateMerge remote-tracking branch 'agent/benma-agent/stage0-install-auth'by Marko Bencun · c13776fb · Oct 27, 2026 · 13 filesMessage 55 · ThinHigh 72Details
Commit message · Marko Bencun

Merge remote-tracking branch 'agent/benma-agent/stage0-install-auth'

55/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Names security-relevant behavior explicitly! No meaningful explanatory body
Why it was queued
boot or update pathmerge-commit duplicate discount
AI analysis · High 72/100

This commit hardens the BitBox02 bootloader's stage0 code against fault-injection attacks during firmware updates. It adds a new authorization check that re-verifies the installed firmware image and ensures a glitch cannot trick the device into installing an older, invalid, or attacker-chosen update. The change also prevents the compiler from optimizing away safety checks. Pre-built stage0 bootloader binaries were regenerated, and unit tests were added for the new logic.

Security candidateMerge remote-tracking branch 'agent/benma-agent/translations'by Marko Bencun · e4356238 · Oct 26, 2026 · 90 filesMessage 50 · ThinInformational 24Details
Commit message · Marko Bencun

Merge remote-tracking branch 'agent/benma-agent/translations'

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
cryptography-sensitive pathsigning or wallet pathboot or update pathauthentication pathmerge-commit duplicate discount
AI analysis · Informational 24/100

This commit adds German-language translations to the BitBox02 hardware wallet firmware. It introduces a new internationalization (i18n) system, stores the chosen UI language in device memory, exposes it via the device-info API, and lets the host change it. The change is large but mostly mechanical: replacing hard-coded English strings with translated equivalents. There is no direct evidence in the diff of a security vulnerability, but any broad UI-text change carries a small risk that a safety-critical warning could be rendered incorrectly or bypassed due to a translation/lookup bug.

Security candidatememory: disable NVM caches during programmingby benma's agent · 5b902dae · Oct 26, 2026 · 4 filesMessage 76 · AdequateModerate 57Details
Commit message · benma's agent

memory: disable NVM caches during programming

On SAMD51 revisions A and D, reading flash while loading the NVM page
buffer can return corrupt data. Our programming routines execute from
flash, so instruction fetches expose them to this erratum even when the
source buffer is in RAM.

Disable both NVMCTRL AHB line caches around explicit page-buffer writes,
following [Microchip's workaround](https://www.microchip.com/DS80000748#page=35)
(DS80000748T, section 2.14.1). Restore the saved controller settings after
programming completes. This covers normal flash and user-row writes,
including BOOTPROT and SmartEEPROM configuration. The BOOTPROT path
resets immediately after programming.

Keep the caches enabled for normal execution: disabling them permanently
stalls stage0 while ICM hashes stage1 directly from flash. Scoping the
workaround to programming also limits its execution-time and power impact.

The change applies to rebuilt firmware, bootloader and factory images.
Ordinary SmartEEPROM data writes are outside its scope.

Co-authored-by: NickeZ Agent <niklas+agent@bitbox.swiss>

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
update trustboot or update path
AI analysis · Moderate 57/100

This commit fixes a hardware erratum in the microcontroller used by the BitBox02 hardware wallet. When the device writes to its internal flash memory, a bug in certain chip revisions can corrupt data being read from flash at the same time—including the program instructions being fetched to run the write routine. The patch temporarily disables two flash caches only during programming, then restores them afterward. If left unpatched, this could in theory lead to corrupted firmware writes, fuses, or security-critical configuration bits, but the commit is a preventive fix rather than a confirmed exploited vulnerability.

Security candidateMerge remote-tracking branch 'agent/benma-agent/mpu-scratch-nonexecutable'by Marko Bencun · 3aac81c9 · Oct 26, 2026 · 1 fileMessage 50 · ThinModerate 57Details
Commit message · Marko Bencun

Merge remote-tracking branch 'agent/benma-agent/mpu-scratch-nonexecutable'

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
boot or update pathmerge-commit duplicate discount
AI analysis · Moderate 57/100

This change adjusts how the bootloader configures memory protection for a storage area called 'appdata' on the BitBox02 hardware wallet. The patch appears to extend a protected region so it also covers 'scratch space' and SmartEEPROM, and keeps these areas marked as non-executable. The branch name suggests the intent was to make the scratch area non-executable, which is a hardening measure rather than a fix for an active attack. However, the change is small and the commit message gives no details, so it is difficult to be certain whether this closes a real security gap or is just defensive cleanup.

Security candidateMerge remote-tracking branch 'agent/benma-agent/stage0-randomness-backup'by Marko Bencun · 870bd953 · Oct 21, 2026 · 18 filesMessage 55 · ThinLow 46Details
Commit message · Marko Bencun

Merge remote-tracking branch 'agent/benma-agent/stage0-randomness-backup'

55/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Names security-relevant behavior explicitly! No meaningful explanatory body
Why it was queued
boot or update pathmerge-commit duplicate discount
AI analysis · Low 46/100

This commit updates the BitBox02 hardware wallet's earliest boot code (stage0 bootloader) to version 3. The main change moves a backup copy of the factory-generated randomness out of the main firmware flash area and into a dedicated scratch region. Previously, that backup sat inside the firmware update area, so a firmware update could accidentally overwrite or corrupt it. The change is a defensive hardening fix: it preserves a secret used during bootloader updates and reduces the chance that a firmware update could break the device's ability to update the bootloader or boot securely.

Security candidatestage0: name backup block as shared scratch spaceby benma's agent · e3811c4c · Oct 20, 2026 · 5 filesMessage 85 · StrongInformational 15Details
Commit message · benma's agent

stage0: name backup block as shared scratch space

The backup block can also hold temporary data for stage1 and firmware,
but its factory-randomness name suggests dedicated storage.

Expose the region as shared flash scratch space and keep the backup
record specific to stage0. Document that contents may not survive a
reboot because stage0 overwrites the space during stage1 updates.

Check the stage1 update slot against the appdata boundary so it remains
inside the firmware area. The flash layout and runtime behavior are
unchanged.

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

This commit is a code cleanup and documentation change in the BitBox02 bootloader. It renames a flash memory region from 'factory randomness backup' to 'shared scratch space' because the same area can be used for temporary data by other bootloader stages. The actual memory layout and runtime behavior are explicitly stated to be unchanged. A new compile-time check is added to ensure the stage1 update area stays within the firmware region.

Security candidatestage0: move randomness backup out of firmwareby benma's agent · eff45631 · Oct 20, 2026 · 17 filesMessage 73 · AdequateLow 33Details
Commit message · benma's agent

stage0: move randomness backup out of firmware

Stage0 stores its factory randomness backup in the firmware area. Writing
that backup changes the signed firmware bytes during a stage1 update,
preventing a firmware image from carrying the update and remaining bootable
afterward.

Move the backup to the unused 8 KiB erase block at 0xFA000, between bootdata
and SmartEEPROM. Preserve the existing committed-backup recovery mechanism
and enforce the new memory boundaries. This allows future firmware images
to include a stage1 update without the backup invalidating their signatures.

Bump stage0 to v3 and embed rebuilt production and development images in
blupgrade. Reclaim the former backup reservation and adjacent padding for
blupgrade code/data, and document the flash layout and stage0 releases.

Devices need stage0 v3 before relying on the new backup location.

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 boundaryboot or update path
AI analysis · Low 33/100

This commit fixes a bootloader/firmware layout bug. Previously, a secret factory randomness backup was stored inside the signed firmware area. When stage1 updated that backup, it changed bytes in the firmware image, breaking the cryptographic signature and making the device unbootable. The patch moves the backup to a separate, unused flash region, adds boundary checks, and ships rebuilt bootloader stage0 v3 images. It is a reliability and integrity improvement rather than a direct remote exploit.

Security candidatebtc: use secp256k1 keys in wallet policiesby benma's agent · 662809bd · Oct 19, 2026 · 1 fileMessage 68 · AdequateInformational 19Details
Commit message · benma's agent

btc: use secp256k1 keys in wallet policies

Derived wallet-policy keys always come from compressed BIP32 xpubs. Use
secp256k1::PublicKey for these keys to save 1,280 bytes in the BitBox02
multi firmware, reducing firmware.bin from 638,492 to 637,212 bytes.

bitcoin::PublicKey carries a compression flag and supports both compressed
and uncompressed encodings. Miniscript already supports secp256k1::PublicKey
and treats it as compressed, so the compiler can eliminate unnecessary
compression checks during policy derivation and script construction.

The simpler type also uses a different Display implementation. This removes
the general-purpose hex formatter retained by bitcoin::PublicKey for
Miniscript's error messages, even though the firmware discards that error
text and returns its own error codes.

Key values, serialized scripts, addresses and Taproot spend data remain
unchanged. Update the serialization calls to use the key directly.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
secret or key material
AI analysis · Informational 19/100

This is a code cleanup and memory-optimization change in the BitBox02 Bitcoin wallet firmware. It swaps a more flexible public-key type for a simpler, always-compressed one inside wallet policy handling. The commit explicitly states that serialized scripts, addresses, and Taproot data stay the same, and the main benefit is a 1,280-byte smaller firmware image. There is no direct evidence of a security vulnerability being fixed.

Security candidateapi: use unstable sorting for keysby benma's agent · 377cf9f1 · Oct 15, 2026 · 2 filesMessage 68 · AdequateInformational 19Details
Commit message · benma's agent

api: use unstable sorting for keys

Stable sorting is unnecessary for these keys and adds sorting code to the
firmware. Using sort_unstable() saves 832 bytes in the BitBox02 multi
firmware with Rust 1.96.0, reducing firmware.bin from 661,896 to 661,064
bytes.

Sort serialized multisig xpubs, derived public keys, and Cardano signing
paths with the same lexicographic ordering. Equal values have identical
contents, so changing their relative order cannot affect registration
hashes, output scripts, or witness order. Cardano still removes duplicate
paths after sorting.

The unstable sort also avoids the stable sort's possible temporary
allocation.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
signing boundarysigning or wallet path
AI analysis · Informational 19/100

This commit swaps Rust's stable sort for an unstable sort in three places inside the BitBox02 firmware. The change only affects the order in which equal items are arranged, and the commit message explicitly states that equal items have identical contents, so the result is the same. The main benefit is a smaller firmware file and avoiding a possible memory allocation during sorting. There is no direct evidence this fixes a security vulnerability.