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 1 minute ago

Informational 12 AI analysisMessage 50 · Thin
BB BitBoxBitBox02 firmware BitcoinHardware wallets

Merge remote-tracking branch 'agent/benma-agent/remove-aes-hmac-c-exports'

This commit removes unused C-language export functions for AES encryption/HMAC from the BitBox02 firmware's Rust code. It is a cleanup change: the functions are deleted, the crate is no longer included in firmware builds, and simulators st…

Reduction of C FFI attack surface by removing no_mangle AES/HMAC exportsDependency cleanup: bitbox-aes no longer linked into firmware or simulatorsNo patch of an identified vulnerability in cryptographic logic
0b6365c6by Marko Bencun+2−5913 files
No security note in commit
Low 43 AI analysisMessage 50 · Thin
BB BitBoxBitBox02 firmware BitcoinHardware wallets

Merge remote-tracking branch 'agent/benma-agent/btc-root-xpub-m49'

This firmware update makes two changes to how the BitBox02 hardware wallet handles Bitcoin-related requests. First, it blocks apps from exporting the wallet's master public key (the 'root xpub') at the top-level path 'm/'. Second, it allow…

Root xpub export blocked at empty keypath (m/)Changelog describes root-xpub restriction as a security-relevant changeExternal service message signing expanded to m/49 unhardened purpose
5294645cby Marko Bencun+79−195 files
Vendor flagged security relevance
Informational 17 AI analysisMessage 78 · Adequate
BB BitBoxBitBox02 firmware BitcoinHardware wallets

cipher: remove unused AES-HMAC C exports

This commit removes two unused C-language bridge functions that wrapped an AES-HMAC encryption/decryption module. The functions themselves were not called from C code; the firmware now calls the same encryption logic directly from Rust. Re…

Removal of C FFI wrappers that could panic on malformed inputsCommit message acknowledges potential panic conditions (invalid IV length, undersized output buffer)No functional change to the underlying AES-HMAC implementation
090a263fby benma's agent+2−5913 files
Vendor flagged security relevance
Low 34 AI analysisMessage 85 · Strong
BB BitBoxBitBox02 firmware BitcoinHardware wallets

u2f: bound DER signature component reads

This commit fixes a small but real bug in how U2F signature components are converted to DER format. The old code could strip too many leading zeros and then read past the end of a 32-byte signature piece, potentially producing an invalid o…

Out-of-bounds read at component boundary during DER encodingPotential malformed DER output for all-zero signature componentDefensive hardening in U2F signature handling
dd17bed7by benma's agent+21−43 files
Vendor flagged security relevance
Low 30 AI analysisMessage 78 · Adequate
BB BitBoxBitBox02 firmware BitcoinHardware wallets

btc: allow message signing under m/49

This commit expands the BitBox02 hardware wallet's Bitcoin message-signing feature to also accept key paths starting with the unhardened purpose 'm/49'. Previously only hardened m/45' and m/48' were treated as valid 'external service' keyp…

Relaxation of keypath allowlist for message signingUnhardened purpose m/49 added to external-service signing namespaceUser confirmation prompt still required ('External service key')
1f377f72by benma's agent+63−194 files
No security note in commit
High 72 AI analysisMessage 73 · Adequate
BB BitBoxBitBox02 firmware BitcoinHardware wallets

btc: reject master xpub exports

This commit closes a security gap in the BitBox02 hardware wallet's Bitcoin API. Previously, a host app could ask the device to export the 'master xpub' (the public key at the very top of the wallet, keypath m/). Combined with any leaked p…

Master xpub export preventedPrivate-key derivation risk described in commit messageUnhardened path key compromise scenario
c4524b15by benma's agent+16−02 files
Vendor flagged security relevance
Informational 15 AI analysisMessage 50 · Thin
BB BitBoxBitBox02 firmware BitcoinHardware wallets

Merge branch 'nickez-agent/configure-stage1-embedding'

This commit is a build-system refactor for the BitBox02 hardware wallet firmware. It replaces a set of separate 'bootloader upgrade' firmware images with a configurable option to embed the same bootloader update data into the normal firmwa…

70a32f5bby Niklas Dusenlund+152−33111 files
No security note in commit
High 70 AI analysisMessage 50 · Thin
BB BitBoxBitBox02 firmware BitcoinHardware wallets

Merge remote-tracking branch 'agent/benma-agent/merge-firmware-v9.29.0'

This firmware update hardens how the BitBox02 handles SwapKit-style cryptocurrency swaps and Bitcoin multisig addresses. It adds a new 'refund memo' to payment requests so the device can verify that any refund address belongs to the same w…

CHANGELOG labels prior changes as 'Bitcoin security fixes (multisig keypath and previous-transaction hash length validation)'CHANGELOG labels v9.29.0 as 'Require wallet-owned refund addresses for SwapKit'New RefundMemo protobuf message with address and optional derivation info
9b16af63by Marko Bencun+867−12411 files
Vendor flagged security relevance
Moderate 60 AI analysisMessage 50 · Thin
BB BitBoxBitBox02 firmware BitcoinHardware wallets

Merge remote-tracking branch 'agent/benma-agent/merge-bootloader-v1.2.3'

This commit hardens the BitBox02 bootloader's stored version-rollback protection data. It adds a SHA-256 checksum over the firmware and signing-key version 'floors' and a one-time migration marker, so the device can detect tampering or cor…

Adds integrity checksum (SHA-256) for anti-rollback version floors in bootloader flash dataIntroduces one-time migration marker to prevent repeated downgrade/migration windowsProduction bootloader now aborts on invalid bootdata instead of silently reinitializing it
a4ddb764by Marko Bencun+2124−3123 files
Vendor flagged security relevance
Informational 15 AI analysisMessage 50 · Thin
BB BitBoxBitBox02 firmware BitcoinHardware wallets

Merge remote-tracking branch 'agent/benma-agent/high-fee-wording-v9.27.2'

This commit only updates test data and test expectations to reflect that a wording change for high Bitcoin transaction fees was released in firmware version 9.27.2 instead of 9.28.0. It does not change any device firmware code, security lo…

00f9eb22by Marko Bencun+65−1123 files
No security note in commit
Informational 15 AI analysisMessage 68 · Adequate
BB BitBoxBitBox02 firmware BitcoinHardware wallets

btc: fix high-fee wording cutoff in vectors

This commit only updates test data and test expectations for the BitBox02 firmware. It changes which firmware versions are expected to show an old versus new high-fee warning message, because the real firmware already started showing the n…

dc5702d0by benma's agent+65−1123 files
No security note in commit
High 77 AI analysisMessage 50 · Thin
BB BitBoxBitBox02 firmware BitcoinHardware wallets

Merge remote-tracking branch 'agent/benma-agent/stage0-reject-zero-signatures'

This update hardens the BitBox02 hardware wallet's bootloader so it refuses to accept a firmware update signed with an all-zero signature. Previously, the cryptographic verification routine could treat a zero-filled signature as valid unde…

Rejects all-zero ECDSA signatures that may verify as validAdds volatile signature read to mitigate LTO-based read eliminationORs all signature bytes without early exit to ensure full-byte inspection
aec4595dby Marko Bencun+81−22 files
No security note in commit
Low 35 AI analysisMessage 50 · Thin
BB BitBoxBitBox02 firmware BitcoinHardware wallets

Merge remote-tracking branch 'agent/benma-agent/stage1-pairing-lifecycle'

This update fixes a Bluetooth pairing bug in the BitBox02 Nova hardware wallet. When the device switched from Bluetooth back to USB mode, it could keep an old pairing request active. The fix clears that stale pairing state so the device do…

Clearing of stale Bluetooth pairing state on mode switchPairing code/request flag left set across BLE->USB transition before fixBluetooth pairing lifecycle change in bootloader startup path
1047430dby Marko Bencun+7−65 files
Vendor flagged security relevance
Low 47 AI analysisMessage 50 · Thin
BB BitBoxBitBox02 firmware BitcoinHardware wallets

Merge remote-tracking branch 'agent/benma-agent/silent-payment-constant-time-ecdh'

This commit changes how the BitBox02 hardware wallet computes a secret value used in Bitcoin silent payments. Previously, the device used a function that could leak timing information about the secret key through how long the calculation t…

Constant-time cryptographic operation addedVariable-time secret-key multiplication removedSide-channel hardening for silent payments
c1590222by Marko Bencun+21−122 files
No security note in commit
Moderate 59 AI analysisMessage 68 · Adequate
BB BitBoxBitBox02 firmware BitcoinHardware wallets

btc: use constant-time ECDH for silent payments

This commit hardens the BitBox02 hardware wallet's silent-payments feature against a side-channel attack. Previously, the device multiplied a secret key with a public key using a routine whose execution time could leak information about th…

Constant-time cryptographic operation introduced to replace variable-time secret-key multiplicationVariable-time scalar multiplication retained only on public operandsSilent payments private input key material (a_sum) no longer used in variable-time path
7e741cfdby benma's agent+21−122 files
Vendor flagged security relevance
Informational 15 AI analysisMessage 50 · Thin
BB BitBoxBitBox02 firmware BitcoinHardware wallets

Merge branch 'nickez-agent/pin-protobuf-generators'

This commit is a build-system and developer-environment change. It pins the protobuf compiler and related Python tools to specific versions via a project-managed Python virtual environment, instead of relying on whatever version a develope…

Pinning build tools to exact versions reduces non-determinism in generated codeMoves protobuf compiler from system/Docker-installed binary to a version-locked Python wheelNo changes to firmware, cryptography, authentication, or device protocol logic
d072b0f9by Niklas Dusenlund+107−6411 files
No security note in commit
Informational 15 AI analysisMessage 92 · Strong
BB BitBoxBitBox02 firmware BitcoinHardware wallets

build: prefer local protoc for Rust bindings

This commit changes the build script that generates Rust code from protobuf definitions. It makes the build prefer a specific local copy of the protobuf compiler (protoc) installed in the repository's virtual environment, rather than relyi…

de8be632by NickeZ Agent+4−01 file
No security note in commit
Informational 15 AI analysisMessage 80 · Strong
BB BitBoxBitBox02 firmware BitcoinHardware wallets

build: use IPv4 for container downloads

This change forces the build system to use IPv4 instead of IPv6 when downloading tools and software packages during Docker image creation. It is a build reliability fix for GitHub Actions CI runners that lack IPv6 connectivity, not a secur…

bc434dcfby NickeZ Agent+6−41 file
No security note in commit
Informational 15 AI analysisMessage 80 · Strong
BB BitBoxBitBox02 firmware BitcoinHardware wallets

build: check regenerated protobuf bindings

This change improves a build/CI script that checks whether automatically generated protobuf binding files are up to date. It now also checks Python bindings and deletes old generated files before regenerating them, so stale files cannot hi…

No security-relevant code changeBuild/CI hardening onlyNo vulnerability fix or exploit mitigation present in diff
ff3f7474by NickeZ Agent+13−22 files
No security note in commit
Informational 15 AI analysisMessage 45 · Thin
BB BitBoxBitBox02 firmware BitcoinHardware wallets

Merge branch 'translate-passphrase-on-host'

This commit is a localization (translation) update for the BitBox02 hardware wallet. It replaces hard-coded English text strings in the passphrase unlock feature with calls to the device's internationalization system, so the same messages …

4dfa26b4by Marko Bencun+33−103 files
No security note in commit
Repository ledger

Explore captured commits

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

AI review queuedMerge remote-tracking branch 'agent/benma-agent/fee-percentage-rounding'by Marko Bencun · d15c46b3 · Oct 19, 2026 · 2 filesMessage 50 · ThinInformational 21Details
Commit message · Marko Bencun

Merge remote-tracking branch 'agent/benma-agent/fee-percentage-rounding'

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Informational 21/100

This commit fixes how the BitBox02 hardware wallet rounds a fee percentage shown on screen. The old code used a standard floating-point rounding function that could produce wrong results for values very close to a rounding boundary, and it also added unwanted floating-point code to the firmware binary. The new code does the rounding with integer arithmetic and clamps out-of-range or invalid inputs. The visible effect is a slightly different displayed fee percentage in edge cases; there is no direct evidence this could be used to steal funds or run unauthorized code.

AI review queuedMerge remote-tracking branch 'agent/benma-agent/compact-erc20-storage'by Marko Bencun · 69660056 · Oct 19, 2026 · 5 filesMessage 50 · ThinInformational 17Details
Commit message · Marko Bencun

Merge remote-tracking branch 'agent/benma-agent/compact-erc20-storage'

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Informational 17/100

This commit is a code-size optimization for how the BitBox02 hardware wallet stores ERC-20 token metadata (token symbols, decimals, and contract addresses). It replaces a simpler but larger table with a compact, bit-packed lookup table generated at build time. There is no direct evidence in the commit that this fixes a security bug; it appears to be a firmware-size reduction refactor. The only user-visible code change is switching from a static string reference to an owned String for the token unit, which is a consequence of the new packed storage format.

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.

AI review queuedeth: reduce big-integer code sizeby benma's agent · 05e80656 · Oct 15, 2026 · 3 filesMessage 68 · AdequateInformational 12Details
Commit message · benma's agent

eth: reduce big-integer code size

Generic num-bigint formatting and multiplication retain routines for much
larger integers than Ethereum needs. Avoiding those routines saves 6,420
bytes in BitBox02 multi firmware, reducing it from 661,912 to 655,492 bytes
without changing dependencies.

Convert decimal digits with division and remainder by 10u32. Use this for
amount formatting and EIP-712 integer text, preserving the sign of signed
values. Calculate transaction fees by consuming the gas-limit bytes from
most to least significant, using shifts, scalar products, and additions.
Both changes are needed to remove the general multiplication routines,
which generic decimal conversion also uses.

Keep arbitrary-precision arithmetic, input validation, decimal placement,
trimming, and EIP-712 sign extension unchanged. The scalar loops favor
code size and can perform more iterations and temporary allocations.

Add the eliminated formatting, multiplication, and division symbols to the
firmware CI check so future call sites cannot silently bring them back.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 12/100

This commit is a code-size optimization for the BitBox02 hardware wallet firmware. It replaces generic big-integer formatting and multiplication with smaller, hand-written scalar loops specifically sized for Ethereum's needs. There is no security fix or vulnerability being patched; the goal is to reduce firmware size by about 6,420 bytes while keeping the same arithmetic results.

AI review queuedeth: cover large-number formatting and feesby benma's agent · c1375689 · Oct 15, 2026 · 2 filesMessage 78 · AdequateInformational 12Details
Commit message · benma's agent

eth: cover large-number formatting and fees

Add focused regression cases before changing large-number formatting and
fee calculations to reduce firmware size.

Compare the signed and unsigned decimal helpers directly with
num-bigint's formatting. Cover zero, digit boundaries, embedded and
trailing zeroes, large unsigned values, a 257-bit transaction total, and
negative values through the minimum signed 256-bit value.

Compare both fee formulas with direct BigUint multiplication using zero,
one, mixed bytes, and maximum inputs. Keep these cases separate from the
implementation change so they apply to both versions.

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 or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 12/100

This commit only adds new automated tests for Ethereum fee calculation and large-number decimal formatting. It does not change any production code, so it cannot by itself introduce or fix a security bug. The tests are described by the author as regression tests to prepare for a future formatting and fee-calculation change that aims to reduce firmware size.

AI review queuedutil: extract big-integer decimal formattingby benma's agent · 9e999101 · Oct 15, 2026 · 2 filesMessage 78 · AdequateInformational 19Details
Commit message · benma's agent

util: extract big-integer decimal formatting

Give signed and unsigned integer-to-text conversion dedicated entry
points so it can be tested directly, separately from amount formatting
and EIP-712 message encoding.

Route existing callers through bigint_to_string() and
biguint_to_string(). Both helpers still delegate to num-bigint's
to_string(), preserving the existing behavior.

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 or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 19/100

This commit is a straightforward code cleanup: it pulls out existing big-number-to-text conversion into named helper functions so they can be tested directly. The actual behavior is unchanged because the new helpers still call the same underlying library method (num-bigint's to_string()). There is no security fix or vulnerability here.

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.

Lower-priorityMerge remote-tracking branch 'agent/benma-agent/python-taproot-policy'by Marko Bencun · 448c1630 · Oct 15, 2026 · 2 filesMessage 50 · ThinTriage 0Details
Commit message · Marko Bencun

Merge remote-tracking branch 'agent/benma-agent/python-taproot-policy'

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
merge-commit duplicate discount
Lower-priorityMerge remote-tracking branch 'agent/benma-agent/release-build-docs'by Marko Bencun · ca1164c6 · Oct 14, 2026 · 2 filesMessage 50 · ThinTriage 0Details
Commit message · Marko Bencun

Merge remote-tracking branch 'agent/benma-agent/release-build-docs'

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
merge-commit duplicate discount
Lower-priorityreleases: update reproducible build workflowby benma's agent · 948f4855 · Oct 13, 2026 · 2 filesMessage 68 · AdequateTriage 0Details
Commit message · benma's agent

releases: update reproducible build workflow

The configurable build system replaced the Bitcoin-only make target and moved firmware
outputs. The reproduction guide still showed only the old commands and paths, and build.sh
printed paths that no longer matched the generated binaries.

Document the new commands alongside the historical examples, with a shared introduction to
the script. Print the firmware binaries found in both build layouts so the reported paths
match the release being built.

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

AI review queuedMerge remote-tracking branch 'agent/benma-agent/btc-validate-prevout-hash'by Marko Bencun · 5352b8b9 · Oct 13, 2026 · 1 fileMessage 50 · ThinModerate 60Details
Commit message · Marko Bencun

Merge remote-tracking branch 'agent/benma-agent/btc-validate-prevout-hash'

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
defensive validationsigning or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Moderate 60/100

This commit adds a safety check in the BitBox02 hardware wallet's Bitcoin transaction signing code. It now rejects transaction inputs whose 'previous output hash' (a transaction identifier) is not exactly 32 bytes long. Previously, only a zero-value input was rejected. The change prevents malformed or attacker-crafted inputs with wrong hash lengths from being processed during signing. A new test verifies the device correctly refuses these invalid inputs.

Lower-priorityMerge branch 'fix/dockerdev-podman-image-lookup'by beerosagos · ce7b1e8a · Oct 13, 2026 · 1 fileMessage 45 · ThinTriage 0Details
Commit message · beerosagos

Merge branch 'fix/dockerdev-podman-image-lookup'

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
merge-commit duplicate discount
Lower-priorityMerge pull request #2149 from shonsirsha/chore-agent-commit-pr-guidanceby Niklas · 994d5610 · Oct 13, 2026 · 1 fileMessage 73 · AdequateTriage 0Details
Commit message · Niklas

Merge pull request #2149 from shonsirsha/chore-agent-commit-pr-guidance

chore: clarify commit and PR writing rules

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
documentation-only discountmerge-commit duplicate discount
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.

Lower-prioritychore: clarify commit and PR writing rulesby sl · 4bfa1913 · Oct 13, 2026 · 1 fileMessage 72 · AdequateTriage 0Details
Commit message · sl

chore: clarify commit and PR writing rules

Keep commit messages and PR bodies focused on motivation and behavior.

72/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body
Why it was queued
documentation-only discount
Lower-priorityMerge pull request #2147 from benma-agent/benma-agent/python-u2f-payload-limitby benma · e3ca9b45 · Oct 13, 2026 · 2 filesMessage 58 · ThinTriage 0Details
Commit message · benma

Merge pull request #2147 from benma-agent/benma-agent/python-u2f-payload-limit

py: reject oversized U2F HID payloads

58/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
merge-commit duplicate discount
Lower-prioritypy: reject oversized U2F HID payloadsby benma's agent · f59658fd · Oct 13, 2026 · 2 filesMessage 68 · AdequateTriage 0Details
Commit message · benma's agent

py: reject oversized U2F HID payloads

Checking only the 16-bit length field allows payloads that need more than
128 continuation frames. With 64-byte reports, messages above 7609 bytes
send invalid sequence numbers, and larger ones can fail after partial
transmission.

Enforce the U2F HID payload limit before copying data or writing any
frames, while continuing to accept the maximum-size payload.

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

Lower-prioritytools: replace ttf2ugui converterby NickeZ Agent · 6742a542 · Oct 8, 2026 · 9 filesMessage 68 · AdequateTriage 0Details
Commit message · NickeZ Agent

tools: replace ttf2ugui converter

BitBox02 font generation needs compact LVGL fmt_txt data instead of
the uGUI bitmap format. Replace the ttf2ugui submodule with a local
FreeType converter for explicit Unicode ranges and 1bpp glyphs.

Use ICU to escape invisible characters in generated comments and
pkg-config to locate dependencies. Include the development-container
dependencies, usage documentation, and converter regression checks.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Provides detailed explanatory context✓ Mentions testing or verification