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/remove-aes-hmac-c-exports'by Marko Bencun · 0b6365c6 · Nov 20, 2026 · 13 filesMessage 50 · ThinInformational 12Details
Commit message · Marko Bencun

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

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

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 stop depending on it. There is no indication this fixes an active security bug; it reduces attack surface by narrowing what code is exposed to C callers.

Lower-priorityMerge remote-tracking branch 'agent/benma-agent/u2f-der-bounds'by Marko Bencun · 84bda67b · Nov 20, 2026 · 3 filesMessage 50 · ThinTriage 0Details
Commit message · Marko Bencun

Merge remote-tracking branch 'agent/benma-agent/u2f-der-bounds'

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
AI review queuedMerge remote-tracking branch 'agent/benma-agent/btc-root-xpub-m49'by Marko Bencun · 5294645c · Nov 20, 2026 · 5 filesMessage 50 · ThinLow 43Details
Commit message · Marko Bencun

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

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

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 allows signing Bitcoin messages using keypaths that start with 'm/49' (unhardened) for external services, in addition to the already allowed 'm/45'' and 'm/48'' paths. The changelog explicitly frames the root-xpub restriction as a security improvement, while the m/49 change is described as a feature expansion.

Lower-priorityMerge remote-tracking branch 'agent/benma-agent/multisig-lookup-hash-size'by Marko Bencun · a5ff45ee · Nov 20, 2026 · 1 fileMessage 50 · ThinTriage 0Details
Commit message · Marko Bencun

Merge remote-tracking branch 'agent/benma-agent/multisig-lookup-hash-size'

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-prioritymemory: require a 32-byte multisig lookup hashby benma's agent · 837b01ae · Nov 19, 2026 · 1 fileMessage 68 · AdequateTriage 0Details
Commit message · benma's agent

memory: require a 32-byte multisig lookup hash

The C lookup compares all 32 bytes of a stored multisig hash. Its safe
Rust wrapper accepted a slice of any length, so it could pass a shorter
buffer to C.

Take a reference to a 32-byte array to enforce the required length at
compile time, matching the memory HAL and its callers.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Security candidatecipher: remove unused AES-HMAC C exportsby benma's agent · 090a263f · Nov 19, 2026 · 13 filesMessage 78 · AdequateInformational 17Details
Commit message · benma's agent

cipher: remove unused AES-HMAC C exports

The keystore calls the AES-HMAC implementation directly from Rust. No
C caller needs the wrappers, which can panic if given an invalid IV
length or an undersized output buffer.

Remove both C exports and their binding and link configuration. Drop
the redundant test import and direct AES dependencies in the device
tests and graphical simulators. The keystore continues to use the same
Rust encryption and decryption functions.

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

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. Removing them eliminates the risk that someone might later misuse these wrappers with a wrong input size, but the change does not fix any currently exploitable vulnerability.

Security candidateu2f: bound DER signature component readsby benma's agent · dd17bed7 · Nov 19, 2026 · 3 filesMessage 85 · StrongLow 34Details
Commit message · benma's agent

u2f: bound DER signature component reads

Trimming every leading zero from a P-256 component can move the DER
encoder past the component boundary before it checks the sign bit.

Keep the final octet of each component when trimming so that zero has
its required one-octet DER INTEGER representation.

This is defensive hardening. The production U2F signer generates
nonzero R and S. Valid signatures, including ones with leading zeros,
produce exactly the same DER bytes as before.

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
signing boundarydefensive validation
AI analysis · Low 34/100

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 or malformed DER-encoded signature. The fix ensures at least one byte of each component is always kept. The vendor describes this as defensive hardening, because the device's own signer is not expected to produce the all-zero inputs that trigger the bug.

Security candidatebtc: allow message signing under m/49by benma's agent · 1f377f72 · Nov 19, 2026 · 4 filesMessage 78 · AdequateLow 30Details
Commit message · benma's agent

btc: allow message signing under m/49

Casa (casa.io) needs Bitcoin message signatures to verify control of
keys in the unhardened m/49 branch. The firmware currently rejects
these keypaths before prompting.

Accept m/49 and its descendants up to the existing limit of ten path
components. Use the same external service key confirmation as for m/45'
and m/48'.

Bump the firmware version to v9.30.0 for the two Bitcoin keypath changes.

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 boundarydefensive validationsigning or wallet path
AI analysis · Low 30/100

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' keypaths. The change is presented as a feature for Casa (casa.io) to verify control of keys. It is not a vulnerability fix; it is a deliberate relaxation of an access check, accompanied by tests and a version bump.

Security candidatebtc: reject master xpub exportsby benma's agent · c4524b15 · Nov 19, 2026 · 2 filesMessage 73 · AdequateHigh 72Details
Commit message · benma's agent

btc: reject master xpub exports

The master xpub combined with a leaked private key on an entirely
unhardened path exposes the master private key. The single-xpub API
would release the master xpub after an unusual-keypath confirmation.

Reject the empty keypath before prompting. Hosts that need to identify
the wallet can use the dedicated root fingerprint request.

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
secret or key materialdefensive validation
AI analysis · High 72/100

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 private key from an unhardened derivation path, that master xpub could let an attacker compute the wallet's master private key and steal all funds. The fix rejects empty keypath requests before showing any confirmation screen. The commit message itself describes the security relevance.

Security candidateMerge branch 'nickez-agent/configure-stage1-embedding'by Niklas Dusenlund · 70a32f5b · Nov 19, 2026 · 11 filesMessage 50 · ThinInformational 15Details
Commit message · Niklas Dusenlund

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

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

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 firmware image. There is no indication in the commit of a security vulnerability being fixed; it appears to be a change to how firmware variants are produced.

Security candidateMerge remote-tracking branch 'agent/benma-agent/merge-firmware-v9.29.0'by Marko Bencun · 9b16af63 · Nov 19, 2026 · 11 filesMessage 50 · ThinHigh 70Details
Commit message · Marko Bencun

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

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 pathmerge-commit duplicate discount
AI analysis · High 70/100

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 wallet account being spent from, preventing a malicious or compromised swap provider from redirecting refunds to an attacker's address. It also tightens Bitcoin multisig address keypath checks so only normal receive/change branches (0 or 1) are allowed when displaying a receiving address, while still permitting broader paths for spending/recovery. The changelog explicitly calls these 'Bitcoin security fixes' and 'Require wallet-owned refund addresses for SwapKit'.

Security candidateMerge remote-tracking branch 'agent/benma-agent/merge-bootloader-v1.2.3'by Marko Bencun · a4ddb764 · Nov 19, 2026 · 23 filesMessage 50 · ThinModerate 60Details
Commit message · Marko Bencun

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

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

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 corruption of those floors. It also improves flash read/write error handling (including ECC memory errors) and makes the bootloader refuse to use invalid boot data on production devices. Development devices can reset corrupt boot data for testing. The change is defensive: it closes a path where an attacker or glitch could potentially downgrade firmware or signing-key versions by corrupting stored data.

Lower-priorityMerge remote-tracking branch 'agent/benma-agent/firmware-upgrade-note'by Marko Bencun · 5289a8a9 · Nov 19, 2026 · 1 fileMessage 50 · ThinTriage 0Details
Commit message · Marko Bencun

Merge remote-tracking branch 'agent/benma-agent/firmware-upgrade-note'

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 branch 'nickez-agent/lvgl-9.6'by Niklas Dusenlund · c0ba0a98 · Nov 19, 2026 · 5 filesMessage 45 · ThinTriage 0Details
Commit message · Niklas Dusenlund

Merge branch 'nickez-agent/lvgl-9.6'

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 remote-tracking branch 'release-v9.27.2'by Marko Bencun · f96bc1f5 · Nov 19, 2026 · 2 filesMessage 45 · ThinTriage 0Details
Commit message · Marko Bencun

Merge remote-tracking branch 'release-v9.27.2'

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-priorityscripts: include the v9.27.2 firmware upgrade stepby benma's agent · dff84ddc · Nov 19, 2026 · 1 fileMessage 73 · AdequateTriage 0Details
Commit message · benma's agent

scripts: include the v9.27.2 firmware upgrade step

Devices running v9.27.1 or earlier must install and run v9.27.2 before upgrading
to newer firmware. Include the link to v9.27.2 from the v9.29.0 release notes in
the template so future firmware releases document this step.

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
AI review queuedMerge remote-tracking branch 'agent/benma-agent/high-fee-wording-v9.27.2'by Marko Bencun · 00f9eb22 · Nov 19, 2026 · 3 filesMessage 50 · ThinInformational 15Details
Commit message · Marko Bencun

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

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

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 logic, or user-facing behavior. There is no security issue here.

AI review queuedbtc: fix high-fee wording cutoff in vectorsby benma's agent · dc5702d0 · Nov 19, 2026 · 3 filesMessage 68 · AdequateInformational 15Details
Commit message · benma's agent

btc: fix high-fee wording cutoff in vectors

Firmware v9.27.2 already displays the revised high-fee warning. The Bitcoin transaction
vectors use v9.28.0 as the cutoff, so they expect the old wording when run against v9.27.2.

Move the cutoff to v9.27.2 for both the send-amount and total-input warnings. Earlier firmware
versions keep their existing screen expectations.

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

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 new wording in version 9.27.2, not 9.28.0. There is no change to the actual device firmware or to user-facing security behavior.

Security candidateMerge remote-tracking branch 'agent/benma-agent/stage0-reject-zero-signatures'by Marko Bencun · aec4595d · Nov 18, 2026 · 2 filesMessage 50 · ThinHigh 77Details
Commit message · Marko Bencun

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

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

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 under some conditions, which might let a malicious or malformed firmware image pass the signature check. The fix explicitly scans every byte of each signature to ensure it is not all zeros, and it re-reads the signature bytes fresh during each verification pass to guard against subtle compiler or hardware-level tampering.

Security candidateMerge remote-tracking branch 'agent/benma-agent/stage1-pairing-lifecycle'by Marko Bencun · 1047430d · Nov 18, 2026 · 5 filesMessage 50 · ThinLow 35Details
Commit message · Marko Bencun

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

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

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 does not act on an outdated or unintended pairing code.

Lower-priorityMerge remote-tracking branch 'nickez-agent/nickez-agent/exclude-st-runtime-stubs'by Niklas Dusenlund · 34c74437 · Nov 18, 2026 · 1 fileMessage 50 · ThinTriage 0Details
Commit message · Niklas Dusenlund

Merge remote-tracking branch 'nickez-agent/nickez-agent/exclude-st-runtime-stubs'

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
Security candidateMerge remote-tracking branch 'agent/benma-agent/silent-payment-constant-time-ecdh'by Marko Bencun · c1590222 · Nov 18, 2026 · 2 filesMessage 50 · ThinLow 47Details
Commit message · Marko Bencun

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

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

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 took. The new code uses a constant-time elliptic-curve Diffie-Hellman operation and passes the intermediate public point into the proof creation so the secret is no longer multiplied in a variable-time way. This is a defensive side-channel fix, not an active exploit.

Security candidatebtc: use constant-time ECDH for silent paymentsby benma's agent · 7e741cfd · Nov 18, 2026 · 2 filesMessage 68 · AdequateModerate 59Details
Commit message · benma's agent

btc: use constant-time ECDH for silent payments

Use libsecp256k1's constant-time ECDH to multiply the scan public key
by the sum of the input private keys. Reuse this DLEQ point to derive
the same BIP352 shared point by multiplying it by the input hash. The
host receives the DLEQ point with the proof and can compute the hash,
so both operands of the remaining variable-time tweak are public to it.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
secret or key materialconstant-time or timing behaviorcryptography-sensitive path
AI analysis · Moderate 59/100

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 the secret. The change uses libsecp256k1's constant-time ECDH for the secret multiplication, and only performs a variable-time multiplication on a value that is already public to the connected computer. This reduces the risk that a local attacker or malware could recover private key material by timing how long the device takes.

Lower-priorityMerge branch 'e2e-sim-graphical-port'by Tomas Vrba · 76e721b2 · Nov 17, 2026 · 2 filesMessage 45 · ThinTriage 0Details
Commit message · Tomas Vrba

Merge branch 'e2e-sim-graphical-port'

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-prioritysimulator-graphical-bb03: add --port optionby NickeZ Agent · ee03f51a · Nov 17, 2026 · 1 fileMessage 68 · AdequateTriage 0Details
Commit message · NickeZ Agent

simulator-graphical-bb03: add --port option

The BB03 graphical simulator always binds TCP port 15423, preventing
multiple instances from running side by side without separate network
namespaces.

Add the same --port option as the BB02 graphical simulator and use it
for the host connection listener. Keep 15423 as the default.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context