assertions: Add nickez assertions for v9.23.2
What changed, and why it matters
This commit adds two digital signature files for firmware version 9.23.2. These signatures are part of the project's reproducible-build attestation process, where an independent party (nickez) confirms that the published firmware matches the publicly available source code. No code, no bug fix, and no security vulnerability is present in the change itself.
No action required. This is a routine release-attestation artifact addition. Reviewers may optionally verify the signature against the published public key and reproducible build hash, but the commit itself does not alter firmware behavior.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The commit introduces two new binary files: releases/firmware-btc-v9.23.2/assertion-nickez.sig and releases/firmware-v9.23.2/assertion-nickez.sig. They are GPG-style assertion signatures for the reproducible build of firmware v9.23.2 (both the standard and BTC-only variants). The diff shows only binary file additions; no source code, logic, or configuration was modified.
Changed components
releases/firmware-v9.23.2/assertion-nickez.sigreleases/firmware-btc-v9.23.2/assertion-nickez.sigInspect captured patch +0 / −0
diff --git a/releases/firmware-btc-v9.23.2/assertion-nickez.sig b/releases/firmware-btc-v9.23.2/assertion-nickez.sig
new file mode 100644
index 0000000..fdda264
Binary files /dev/null and b/releases/firmware-btc-v9.23.2/assertion-nickez.sig differ
diff --git a/releases/firmware-v9.23.2/assertion-nickez.sig b/releases/firmware-v9.23.2/assertion-nickez.sig
new file mode 100644
index 0000000..f6f0a79
Binary files /dev/null and b/releases/firmware-v9.23.2/assertion-nickez.sig differ
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.