What changed, and why it matters
This commit adds release artifacts for firmware version 9.23.3 of the BitBox02 hardware wallet. It contains two signed text files (assertions) confirming the expected SHA-256 hash of the compiled firmware binary for both the standard and Bitcoin-only editions. There is no code change and no security issue visible in the diff.
No security action required; this is a routine release attestation. Users verifying reproducible builds can compare their compiled firmware hash against the asserted SHA-256 values and validate the signature.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The commit creates four files under releases/firmware-v9.23.3/ and releases/firmware-btc-v9.23.3/: assertion.txt documents the git tag, source commit hash (a085e26da2065c8474bbe0bf4bb56968848af825), and expected SHA-256 of the built firmware; assertion-benma.sig is the detached signature over that assertion. This is a normal reproducible-build attestation step and does not modify firmware source code.
Changed components
releases/firmware-v9.23.3/assertion.txtreleases/firmware-v9.23.3/assertion-benma.sigreleases/firmware-btc-v9.23.3/assertion.txtreleases/firmware-btc-v9.23.3/assertion-benma.sigInspect captured patch +16 / −0
diff --git a/releases/firmware-btc-v9.23.3/assertion-benma.sig b/releases/firmware-btc-v9.23.3/assertion-benma.sig
new file mode 100644
index 0000000..b23767a
Binary files /dev/null and b/releases/firmware-btc-v9.23.3/assertion-benma.sig differ
diff --git a/releases/firmware-btc-v9.23.3/assertion.txt b/releases/firmware-btc-v9.23.3/assertion.txt
new file mode 100644
index 0000000..eedcc77
--- /dev/null
+++ b/releases/firmware-btc-v9.23.3/assertion.txt
@@ -0,0 +1,8 @@
+By signing this file, the signer confirms that the firmware binary built from:
+
+git tag firmware-btc-only/v9.23.3
+git commit hash a085e26da2065c8474bbe0bf4bb56968848af825
+
+resulted, at the time of signing, in a firmware binary file with the following sha256sum:
+
+b191da5acc39507808323f42275db67cbeb9b3357318b0922744dd8af0a108e8
diff --git a/releases/firmware-v9.23.3/assertion-benma.sig b/releases/firmware-v9.23.3/assertion-benma.sig
new file mode 100644
index 0000000..c905b82
Binary files /dev/null and b/releases/firmware-v9.23.3/assertion-benma.sig differ
diff --git a/releases/firmware-v9.23.3/assertion.txt b/releases/firmware-v9.23.3/assertion.txt
new file mode 100644
index 0000000..6007046
--- /dev/null
+++ b/releases/firmware-v9.23.3/assertion.txt
@@ -0,0 +1,8 @@
+By signing this file, the signer confirms that the firmware binary built from:
+
+git tag firmware/v9.23.3
+git commit hash a085e26da2065c8474bbe0bf4bb56968848af825
+
+resulted, at the time of signing, in a firmware binary file with the following sha256sum:
+
+9eea36ded28bd83890cb4d39e0905e0bbdd9384165651a28d7d5231acb4347a8
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.