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 52 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 branch 'benma-agent/prost-size-update'by Marko Bencun · 2b082e10 · Oct 15, 2026 · 89 filesMessage 45 · ThinInformational 24Details
Commit message · Marko Bencun

Merge branch 'benma-agent/prost-size-update'

45/100 · ThinMessage clarity
✓ 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 24/100

This commit is a large dependency update for the BitBox02 firmware, primarily updating the vendored Rust 'prost' protobuf library and related crates. It removes old vendored copies of 'concurrent-queue' and 'crossbeam-utils' and updates generated protobuf code. The commit itself does not describe any security fix, and the visible diff does not show a clear, exploitable vulnerability. It appears to be routine maintenance to keep dependencies current and reduce vendored code size.

Security candidateMerge remote-tracking branch 'agent/benma-agent/factory-context-size-comment'by Marko Bencun · e34efd26 · Oct 13, 2026 · 1 fileMessage 50 · ThinInformational 15Details
Commit message · Marko Bencun

Merge remote-tracking branch 'agent/benma-agent/factory-context-size-comment'

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 only updates a code comment to correct the stated memory savings from using a static secp256k1 verification context. No actual code behavior, logic, or security properties changed. It is a documentation-only fix.

Security candidateMerge remote-tracking branch 'agent/benma-agent/secp256k1-randomize'by Marko Bencun · 04f37f80 · Oct 13, 2026 · 8 filesMessage 50 · ThinLow 45Details
Commit message · Marko Bencun

Merge remote-tracking branch 'agent/benma-agent/secp256k1-randomize'

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

This commit changes how the BitBox02 hardware wallet initializes the secp256k1 cryptographic library. Previously, the library's global context was created automatically on first use. Now, it must be explicitly initialized with a random 32-byte seed before use. The seed is used to randomize internal computations, which is a standard side-channel defense. If the context is used before initialization, the firmware will panic (crash). The change also adds test-only fallbacks so existing tests still work without providing a seed.

Security candidatefactorysetup: update context savings commentby benma's agent · c7b395df · Oct 13, 2026 · 1 fileMessage 68 · AdequateInformational 15Details
Commit message · benma's agent

factorysetup: update context savings comment

The 35 kB estimate predates the secp256k1 upgrade and switch to the
2 KiB signing table. Update it to roughly 6.5 kB; this changes only
the comment.

With the current library and table settings, restoring the Rust
context used before 2756aca4 produces a 165,644-byte factory-setup.bin,
compared with 159,164 bytes using the static context: a saving of
6,480 bytes (6.33 KiB).

The static context avoids the 2,048-byte signing table plus 4,432
bytes of context initialization/support code and other linked data.

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

This commit only updates a code comment to correct the estimated memory savings from using a static cryptographic context. No actual code behavior, logic, or security properties were changed.

Security candidateMerge remote-tracking branch 'agent/benma-agent/secp256k1-22k'by Marko Bencun · 03c8d127 · Oct 13, 2026 · 3 filesMessage 50 · ThinInformational 22Details
Commit message · Marko Bencun

Merge remote-tracking branch 'agent/benma-agent/secp256k1-22k'

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 22/100

This commit updates the secp256k1-zkp cryptographic library inside the BitBox02 firmware and changes how a key signing-speed optimization table is configured. The change replaces one table-size setting with two newer upstream settings and adds a Rust compiler flag needed for the new library version. There is no direct evidence in the commit that this fixes a security vulnerability; it appears to be a routine dependency update to keep the code aligned with upstream secp256k1-zkp.

Security candidatesecp256k1: randomize the context once per bootby benma's agent · 32762289 · Oct 12, 2026 · 8 filesMessage 83 · StrongLow 37Details
Commit message · benma's agent

secp256k1: randomize the context once per boot

The global secp256k1 context starts with deterministic blinding values.
Randomize it once per boot to add protection against power and
electromagnetic side channels during secret-key operations.

After secure-chip setup and before entering the main loop, obtain a
32-byte seed through the existing HAL randomness helper. It combines
MCU and secure-chip randomness with factory randomness. Randomize the
context before publishing it in the OnceCell, then drop the zeroizing
seed buffer. Failure to obtain randomness stops startup.

Require initialization before production access to the shared context.
Repeated initialization keeps the existing context, without changing
blinding state while callers may hold references. Keep lazy initialization
for test configurations that do not run firmware startup, and initialize
both graphical simulators explicitly. Forward testing and c-unit-testing
independently to preserve the separation of Rust and C test builds.

Keep the OnceCell inside GlobalContext so initialization and access
operate on the state it owns. Preserve the shared-reference API and
the existing single-threaded, non-interrupt usage requirement.

Public keys and deterministic signatures stay unchanged. This uses the
existing seeded_randomize API without new dependencies or changes to the
secp256k1 library.

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

83/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Names security-relevant behavior explicitly
Why it was queued
signing boundarysecure hardware boundarycryptography-sensitive pathboot or update path
AI analysis · Low 37/100

This commit hardens the BitBox02 hardware wallet against advanced physical attacks. It randomizes the internal math context used for Bitcoin private-key operations once each time the device boots, using a mix of randomness from the microcontroller, secure chip, and factory-stored randomness. Public keys and signatures remain unchanged; the change only makes it harder for an attacker with physical access to extract secrets through power or electromagnetic side-channel analysis.

Security candidatesecp256k1: update C library to bitbox02-2026-10-12by benma's agent · 1ccd7820 · Oct 12, 2026 · 2 filesMessage 88 · StrongInformational 17Details
Commit message · benma's agent

secp256k1: update C library to bitbox02-2026-10-12

Upgrade the C library and select its 2 KiB signing table to reduce
firmware.bin from 694,548 to 665,176 bytes, saving 29,372 bytes (28.68 KiB)
without the temporary boot benchmark. The new implementation also takes
36-38% less signing time than the old 32 KiB implementation in host
measurements.

Pin the submodule to e54d68ea on the BitBoxSwiss fork's
bitbox02-20261012 branch. It is based on upstream 10366dbb (2026-08-19),
the last master revision before the deprecated context pointer and
Schnorr signing alias were removed. This preserves compatibility with
the existing bitcoin, miniscript, and Rust secp256k1 dependencies.

Keep the existing anti-exfil recovery-ID and DLEQ patches. Their public
interfaces stay unchanged; the DLEQ wrapper adapts to the internal
argument order and hash-context API.

Replace ECMULT_GEN_PREC_BITS=2 with COMB_BLOCKS=2 and COMB_TEETH=5 to
select the smallest upstream-supported signing table. Keep
ECMULT_WINDOW_SIZE=2 for verification. Signature formats stay unchanged.

With the new 2 KiB table, device measurements show 30.4% fewer cycles for
ECDSA signing and 33.4% fewer cycles for Schnorr signing than with the old
32 KiB implementation. This speedup comes from the updated library's
generator multiplication, which replaces fixed two-bit windows with a
signed-digit multi-comb algorithm. It reuses precomputed point combinations
across bit positions:
this configuration needs 52 point additions and 25 doublings instead of
128 additions. The reduction in expensive additions lets the new library
use a much smaller table while still outperforming the old implementation.

Host median times with the old 32 KiB table and the new 2 KiB table:
- ECDSA signing: 68.230 -> 43.776 us (35.8% less time).
- Schnorr signing: 60.566 -> 37.779 us (37.6% less time).
- Anti-exfil commitment plus signing: 192.709 -> 123.176 us (36.1% less time).

These compare edc3c3e0 with d9d4ccd4 using GCC -Os on x86_64 with the
32-bit limb backend. Revision e54d68ea differs from d9d4ccd4 only in the
CI symbol checker. The timings exclude context and keypair setup; they
are not device or whole-transaction timings.

Live device runs of the boot benchmark before and after this upgrade
compare the old 32 KiB implementation with the new 2 KiB implementation.
The following values are mean CPU cycles per operation over 16 measured
calls after one warm-up call. Negative changes mean fewer cycles.

Operation Before After Change
Context initialization 14,337 112,573 +685.2%
Public-key creation 1,775,431 1,167,625 -34.2%
Public-key encoding 2,555 2,451 -4.1%
Public-key parsing 182,577 184,605 +1.1%
Secret-key add tweak 3,324 4,288 +29.0%
Secret-key mul tweak 4,769 5,775 +21.1%
Public-key add tweak 1,738,066 1,759,125 +1.2%
Public-key mul tweak 1,489,530 1,482,017 -0.5%
Public-key combine 96,269 94,781 -1.5%
X-only public tweak 1,740,247 1,761,258 +1.2%
Keypair creation 1,776,999 1,169,171 -34.2%
Keypair tweak 1,741,094 1,763,131 +1.3%
ECDSA signing 1,996,136 1,389,395 -30.4%
ECDSA verification 2,417,780 2,447,168 +1.2%
Anti-exfil commitment 1,935,342 1,323,431 -31.6%
Anti-exfil signing 3,796,601 2,581,140 -32.0%
Schnorr signing 1,810,803 1,206,321 -33.4%
Schnorr verification 2,491,463 2,522,637 +1.3%
DLEQ proof creation 3,712,662 3,072,532 -17.2%
DLEQ verification 5,349,679 5,316,498 -0.6%

Signing uses 30-33% fewer cycles on-device, slightly less of a gain than
on the host. Signing and key creation benefit from the new generator
multiplication; verification and public-key tweaks use a different
multiplication path and remain close to their previous performance.

Context initialization adds 98,236 cycles, about 0.819 ms at the configured
120 MHz. The new initialization includes a loop to compute the comb
algorithm's scalar offset. Firmware initializes and caches its global
context once, so this cost is small compared with the roughly 600,000
cycles saved by one ECDSA or Schnorr signature.

Secret-key addition and multiplication tweaks add 964 and 1,006 cycles,
respectively, or about 8 us each. Upstream's explicit wiping of temporary
scalars is a plausible contributor, but these runs do not isolate its
cost. Public-key addition, x-only and keypair tweaks, and ECDSA/Schnorr
verification take 1.2-1.3% more cycles. Interrupts remain enabled during
the benchmark; repeated runs would help establish how much of these small
differences is systematic. Time equivalents use cycles / 120,000 for ms;
the device screen reports cycles.

Summing the relevant measured components gives these estimates:

Components Before After Change
Anti-exfil commitment + signing 5,731,943 3,904,571 -31.9%
Schnorr keypair + tweak + signing 5,328,896 4,138,623 -22.3%
DLEQ creation + verification 9,062,341 8,389,030 -7.4%

These sums exclude key derivation, randomness generation, communication,
UI, and other surrounding work, so they are not whole-transaction timings.
DLEQ verification dominates its pair, limiting the combined improvement.

88/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Names security-relevant behavior explicitly
Why it was queued
secret or key materialsigning boundarydefensive validationcryptography-sensitive path
AI analysis · Informational 17/100

This commit updates the secp256k1 cryptographic library inside the BitBox02 firmware and switches to a smaller, faster signing table. The change reduces firmware size by about 29 KB and makes ECDSA and Schnorr signing roughly 30-37% faster. There is no indication in the commit that this fixes a known security vulnerability; it appears to be a routine performance and size optimization while preserving existing behavior and patches.

Security candidateMerge branch 'cedwies/bb03-zeroize'by Cedric Wiese · e5afd223 · Oct 12, 2026 · 7 filesMessage 45 · ThinLow 49Details
Commit message · Cedric Wiese

Merge branch 'cedwies/bb03-zeroize'

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

This commit hardens how the BitBox02/BitBox03 firmware handles sensitive text, such as recovery seed words and confirmation dialog bodies. It replaces ordinary Rust strings with versions that automatically wipe their memory when no longer needed, and it pre-allocates buffers to avoid creating leftover copies during growth. The change reduces the risk that secret words or passphrases remain in device memory after use, but it is a defensive hardening patch rather than a fix for a known active attack.

Security candidateMerge branch 'nickez/bb02-lvgl-font'by Niklas Dusenlund · d19a195e · Oct 8, 2026 · 99 filesMessage 45 · ThinLow 35Details
Commit message · Niklas Dusenlund

Merge branch 'nickez/bb02-lvgl-font'

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

This is a large firmware update that replaces the device's font system and, as a consequence, loosens text validation from 'printable ASCII only' to 'valid UTF-8 that the new font can render'. The change is primarily a feature/UX improvement (support for accented European characters and the Euro sign), but it also adds new input-validation checks to make sure unsupported characters cannot be shown on screen. There is no direct evidence in the commit that this fixes an active security bug, but the new validation is defensive: it prevents a user from being shown misleading or truncated text on the small OLED screen.

Security candidateui: add LVGL font assetsby NickeZ Agent · afdcd8d6 · Oct 8, 2026 · 19 filesMessage 61 · AdequateInformational 15Details
Commit message · NickeZ Agent

ui: add LVGL font assets

BitBox02 needs compact font data for English, German, Spanish,
Italian, and French while preserving the existing ASCII appearance.
Add regular fonts covering 162 characters, password fonts with a
visible space marker, and the ASCII monogram font.

Preserve the original glyph pixels, placement, advances, and line
heights, including manual bitmap adjustments. Include smaller ASCII
and hexadecimal subsets for the bootloader and document the exact
character set and regeneration constraints.

61/100 · AdequateMessage clarity
✓ Subject identifies a change✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
update trustboot or update path
AI analysis · Informational 15/100

This commit adds new font files and documentation for the BitBox02 hardware wallet's user interface. It is a routine asset update that changes how text looks on screen, not a security fix or vulnerability. There are no code changes that handle secrets, network data, or user input.

Security candidateui: render BB02 text with LVGL fontsby NickeZ Agent · dfa02f24 · Oct 8, 2026 · 68 filesMessage 78 · AdequateLow 34Details
Commit message · NickeZ Agent

ui: render BB02 text with LVGL fonts

BitBox02 must measure and render supported UTF-8 text consistently
without changing the appearance of existing ASCII screens. Switch
uGUI to LVGL font descriptors and compact 1bpp glyph callbacks, and
update firmware and bootloader consumers together.

Validate text against the font selected by each component. Preserve
UTF-8 boundaries when shortening device names, and reject malformed
input before rendering. Use font coverage for name validation and
legacy-backup sanitization.

Update C/Rust font bindings and native-build header tracking. Remove
the superseded font data and cover ASCII pixel/metric compatibility,
font fallbacks, malformed UTF-8, and lockscreen truncation in tests.

78/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
update trustdefensive validationsigning or wallet pathboot or update path
AI analysis · Low 34/100

This commit replaces the BitBox02's old ASCII-only font system with a new UTF-8-capable font engine based on LVGL. It adds checks to reject or sanitize characters that the device cannot display, preserves UTF-8 boundaries when shortening names, and updates tests. The change is primarily a defensive hardening and internationalization improvement rather than a fix for an active attack.

Security candidateMerge remote-tracking branch 'agent/benma-agent/passphrase-show-last-after-delete'by Marko Bencun · f33930d6 · Oct 7, 2026 · 2 filesMessage 50 · ThinInformational 20Details
Commit message · Marko Bencun

Merge remote-tracking branch 'agent/benma-agent/passphrase-show-last-after-delete'

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

This commit changes how the BitBox02 hardware wallet shows the last character of a passphrase or PIN while the user is typing. Previously, deleting a character would immediately re-hide (mask) every character. After this change, deleting a character instead reveals the new last character in plain text until the next keystroke. This is a deliberate user-experience change, not a fix for a vulnerability. It slightly increases the chance that someone watching the device screen could see a character of the user's secret, but only while the user is actively editing it and only the final character.

Security candidateMerge remote-tracking branch 'agent/benma-agent/backup-buffer-zeroization'by Marko Bencun · e5755430 · Oct 3, 2026 · 4 filesMessage 50 · ThinLow 48Details
Commit message · Marko Bencun

Merge remote-tracking branch 'agent/benma-agent/backup-buffer-zeroization'

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

This commit changes how the BitBox02 hardware wallet stores backup data so that the seed (the secret that protects cryptocurrency) is automatically wiped from temporary memory buffers after use. It also keeps the backup file format compatible with older firmware versions. The change is a defensive hardening improvement rather than a fix for an active attack, because the commit itself does not describe a specific vulnerability or incident.

Security candidateMerge branch 'fix/bb02-empty-passphrase-scroll'by beerosagos · a1319588 · Oct 1, 2026 · 2 filesMessage 45 · ThinInformational 18Details
Commit message · beerosagos

Merge branch 'fix/bb02-empty-passphrase-scroll'

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

This commit changes the on-screen confirmation text from "Use empty passphrase?" to "Use empty\npassphrase?" — adding a line break so the message fits properly on the device's small display. It appears to be a UI layout fix, not a security fix. There is no indication in the commit that this resolves a security vulnerability.

Security candidateMerge branch 'cedwies/zeroize'by Cedric Wiese · dfbb0e66 · Sep 30, 2026 · 2 filesMessage 35 · OpaqueLow 46Details
Commit message · Cedric Wiese

Merge branch 'cedwies/zeroize'

35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
memory safetycryptography-sensitive pathmerge-commit duplicate discount
AI analysis · Low 46/100

This commit hardens how the BitBox02 firmware builds BIP39 recovery phrases so the memory buffer is pre-sized and never grows. The goal is to prevent leftover copies of sensitive mnemonic words from lingering in memory after a reallocation. The change is defensive: it does not fix an observed exploit, but reduces the attack surface for information leaks of wallet recovery words.

Security candidatebip39: avoid unwiped mnemonic copiesby Cedric Wiese · f68abb80 · Sep 30, 2026 · 2 filesMessage 78 · AdequateModerate 59Details
Commit message · Cedric Wiese

bip39: avoid unwiped mnemonic copies

to_string() can leave unwiped copies behind when its buffer grows.

Write the mnemonic into a preallocated zeroizing String, reusing
the capacity limit from last-word calculation. Add a maximum-length
test to check that the buffer does not grow.

78/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
secret or key materialcryptography-sensitive path
AI analysis · Moderate 59/100

This commit fixes a security hygiene issue in the BitBox02 hardware wallet's handling of BIP39 recovery phrases (mnemonics). When converting a mnemonic to text, the previous code could create temporary copies of the secret phrase in memory due to how Rust's string buffer grows. The new code pre-allocates a fixed-size, self-erasing buffer and writes the mnemonic directly into it, reducing the chance that leftover copies of the recovery words remain in device memory.

Security candidateMerge branch 'nickez/make-config-attempt2'by Niklas Dusenlund · 2008ca11 · Sep 28, 2026 · 28 filesMessage 45 · ThinInformational 15Details
Commit message · Niklas Dusenlund

Merge branch 'nickez/make-config-attempt2'

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 is a large build-system refactor for the BitBox02/BitBox03 firmware repository. It replaces hard-coded Make targets and CMake-generated J-Link scripts with a new Python-based configuration system that lets developers choose product, edition, debug mode, and probe software. There is no change to the actual firmware code that runs on the device, and nothing in the commit suggests a security vulnerability or fix.

Security candidateMerge remote-tracking branch 'agent/benma-agent/host-passphrase-polling'by Marko Bencun · 4474a3e9 · Sep 25, 2026 · 39 filesMessage 50 · ThinLow 47Details
Commit message · Marko Bencun

Merge remote-tracking branch 'agent/benma-agent/host-passphrase-polling'

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

This commit adds a new feature that lets users type their optional BIP39 passphrase on the computer (host) instead of only on the BitBox02 device. The device still asks the user for approval before accepting host input, and the actual passphrase is shown on the device for confirmation. The change also moves the unlock handshake inside the already-encrypted Noise channel, adds protocol messages for polling, and includes many tests. It is a feature addition with security-relevant design, not a fix for a known vulnerability.

Security candidatebtc: reject raw key hashes in policiesby benma's agent · 980d937d · Sep 25, 2026 · 1 fileMessage 78 · AdequateModerate 59Details
Commit message · benma's agent

btc: reject raw key hashes in policies

Taproot parsing and sanity_check accept raw public-key-hash leaves,
which are not included in key enumeration. Reject RawPkH in the shared
policy validator before registration or use, including nested fragments.

Correct the stale Taproot parsing comment and cover standalone leaves,
nested expressions, and multi-leaf trees with regression tests.

This also rejects previously registered policies containing this
unsupported fragment when they are used for address derivation or signing.

78/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
signing boundaryfuzzing or regression evidence
AI analysis · Moderate 59/100

This commit fixes a bug in the BitBox02 hardware wallet's Bitcoin policy handling. Previously, the wallet accepted a specific type of unsupported script fragment called a 'raw public-key hash' (RawPkH) inside Taproot wallet policies. Because these fragments were not tracked as keys, they could silently alter how addresses were derived or how transactions were signed, potentially allowing a malicious or malformed policy to behave in unexpected ways. The fix rejects any policy containing RawPkH, including when it is nested inside other expressions, and also rejects already-registered policies that contain it when they are later used.

Security candidateMerge commit 'refs/pull/2123/head' of https://github.com/BitBoxSwiss/bitbox02-firmwareby Marko Bencun · b8bbbb64 · Sep 24, 2026 · 2 filesMessage 58 · ThinInformational 15Details
Commit message · Marko Bencun

Merge commit 'refs/pull/2123/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 · Informational 15/100

This commit only adds two digital signature files for an already-released firmware version (v9.25.0). These are third-party reproducible-build assertions by a user named 'yaziza', not changes to the firmware source code. There is no code change and no apparent security issue.

Security candidateMerge commit 'refs/pull/2124/head' of https://github.com/BitBoxSwiss/bitbox02-firmwareby Marko Bencun · 392ac2ff · Sep 24, 2026 · 2 filesMessage 58 · ThinInformational 0Details
Commit message · Marko Bencun

Merge commit 'refs/pull/2124/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 · Informational 0/100

This commit only adds two digital signature files for an already-released firmware version (v9.27.1). These are release attestation signatures from a contributor named 'yaziza'. There is no code change, no firmware change, and nothing in the commit message or diff that suggests a security fix or vulnerability.

Security candidateMerge branch 'nickez/bb02-finalize-elf'by Niklas Dusenlund · 810d3e87 · Sep 24, 2026 · 13 filesMessage 45 · ThinInformational 12Details
Commit message · Niklas Dusenlund

Merge branch 'nickez/bb02-finalize-elf'

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 12/100

This commit is a build-system refactor that unifies how firmware image headers are generated for the BitBox02 and BitBox03. It replaces a device-specific Python script and a C header placeholder with a shared Python tool and JSON manifests, and removes an older intermediate 'prepare unsigned stage1' step. There is no direct evidence in the commit of a security vulnerability being fixed or introduced; the changes are structural and add more validation and tests.

Security candidatebootloader: use shared stage1 header toolby Niklas Dusenlund · 5b14742f · Sep 23, 2026 · 5 filesMessage 78 · AdequateInformational 12Details
Commit message · Niklas Dusenlund

bootloader: use shared stage1 header tool

Generate stage1 headers from per-target JSON manifests with the existing
image_header.py commands. Link the generated header object, finalize the
ELF image length, and then create the binary with objcopy.

Remove the C header placeholder and the unused header-generation command
and helpers from bootloader_update.py. Retain its upgrade-asset validation
and leave image_header.py unchanged.

All eight stage1 variants build. Generated headers match the previous C
implementation, and binaries match the previous post-processing output.
The updated Python tests and type checks pass, and both retained embedding
commands successfully process all 16 shipped bootloader assets.

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

This commit is a build-system refactoring for the BitBox02 bootloader. It replaces a C-language placeholder for the bootloader's stage1 header with a Python tool that generates the same header from JSON manifests during the build. The old Python helper that prepared unsigned stage1 images is removed because it is no longer needed. The commit explicitly states that generated headers and final binaries match the previous output, and tests were updated and pass. There is no indication of a security vulnerability being fixed or introduced.

Security candidatescripts: unify the BitBox image formatby Niklas Dusenlund · 9403e6fe · Sep 23, 2026 · 6 filesMessage 83 · StrongLow 27Details
Commit message · Niklas Dusenlund

scripts: unify the BitBox image format

Use one 1024-byte header format with BBS1 stage1 magic, metadata,
signature slots, and a 64-bit total image length. Update the BitBox03
manifests and Rust reader, including checked image-length conversion.

Support rendering and finalizing BitBox02 stage1 headers without
changing its existing build integration. BitBox03 metadata uses
placeholder values until product and version information is wired up.

Validate compatibility with shipped headers and existing post-processing,
malformed headers, ELF flash spans, and Rust loader bounds. Python and
Rust tests pass, as do BitBox03 boot0, boot1, and firmware builds.

83/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Names security-relevant behavior explicitly
Why it was queued
signing boundarydefensive validationboot or update path
AI analysis · Low 27/100

This commit refactors the firmware image header format used by BitBox hardware wallets so that BitBox02 and BitBox03 share a single 1024-byte layout. It adds new metadata fields (product ID, version numbers, signature slots) and switches the stored image length from 32-bit to 64-bit. The Rust bootloader code that reads these headers is updated with explicit length checks to avoid integer problems. There is no direct evidence in the commit of an exploitable vulnerability being fixed; it reads as a structural unification and hardening change.

Security candidatescripts: rename image header toolby Niklas Dusenlund · 29d6720a · Sep 23, 2026 · 5 filesMessage 68 · AdequateInformational 15Details
Commit message · Niklas Dusenlund

scripts: rename image header tool

Rename bitbox03_image_header.py to image_header.py as the first step toward shared image header post-processing. Update Makefile and Rust references while preserving the script contents and behavior.

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 simply renames a build script from bitbox03_image_header.py to image_header.py and updates all references in the Makefile and Rust build files. The script's contents and behavior are unchanged. There is no security issue here.