DIY air-gapped Bitcoin hardware-wallet firmware.
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.
Aug 5 → Feb 618 seen6 candidatesCompleteFeb 6 → Jun 65 seen1 candidatesCompleteJun 6 → Jul 60 seen0 candidatesCompleteJul 6 → Aug 50 seen0 candidatesCompleteMessage quality measures whether a commit identifies its scope, purpose, rationale, testing, and supporting references. It does not change the security-severity score.
Public Git author strings; identities are not independently verified.
Last scanned 0 minutes ago
This commit only updates a Git submodule pointer for the bootloader to a newer commit. No actual source code changes are shown, and no verified security references were provided. There is no direct evidence in the materials that this updat…
95353b64by k9ert+1−11 fileThis commit adds more information to the transaction signing screen of the Specter DIY hardware wallet. It now shows the transaction version, locktime, and each input's sequence number, helping users spot unusual transaction settings (such…
3d1bb8edby Oren+207−108 filesThis commit changes a build script so that the upgrade package now includes the bootloader alongside the main application firmware, and adds a safety flag that stops the script on first error. There is no direct evidence in the commit that…
ed9ad9a6by k9ert+4−21 fileThis change simply updates the project's firmware build script and documentation to also produce a 'no bootloader' firmware image by default. It is a developer convenience for testing on development boards and does not alter any runtime co…
6f66962aby 3rd Iteration+21−03 filesThis commit undoes a previous change that added the bootloader to the device's upgrade binary. It removes the bootloader from the generated upgrade file and also removes a 'set -e' safety flag from the build script. On its own, this revert…
b6778187by k9ert+2−51 fileThis is a build-script change for a hardware-wallet project. It adds a command-line flag so that the upgrade package generator includes the bootloader file alongside the main firmware. It also adds `set -e` so the build script stops on err…
54a38094by k9ert+5−21 fileThis commit is a routine build and continuous-integration (CI) maintenance change for the Specter DIY hardware wallet project. It adds Nix package-manager files to pin build dependencies, a GitHub Actions workflow to compile the firmware, …
ce35419bby k9ert+45671−0243 filesExpand any commit for its author, full message, clarity score, changed files, triage signals, analysis, and source link.
95353b64 · Apr 9, 2026 · 1 fileInformational 0Update bootloader submodule to latest (#350)
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit only updates a Git submodule pointer for the bootloader to a newer commit. No actual source code changes are shown, and no verified security references were provided. There is no direct evidence in the materials that this update fixes or introduces a security issue.
30ebb834 · Jan 29, 2026 · 2 filesTriage 12release: prepare release (#340)
Co-authored-by: k9ert <kim@swanbitcoin.com>
7bfd5196 · Jan 22, 2026 · 1 fileTriage 12feat: Removed ben and added k9ert keys for releasing (#306)
Why it was queued3d1bb8ed · Jan 20, 2026 · 8 filesInformational 19Show Transaction Version, Locktime and inputs' sequences when signing transactions! (#321)
Co-authored-by: k9ert <117085+k9ert@users.noreply.github.com>
Co-authored-by: k9ert <kim@swanbitcoin.com>
This commit adds more information to the transaction signing screen of the Specter DIY hardware wallet. It now shows the transaction version, locktime, and each input's sequence number, helping users spot unusual transaction settings (such as delayed spending or disabled locktime) before they approve a signature. There is no direct evidence this fixes an active exploit; it is primarily a user-interface hardening change.
1f98790b · Dec 11, 2025 · 5 filesTriage 12Add support for selecting and combining build actions (#333)
Why it was queueded9ad9a6 · Dec 4, 2025 · 1 fileInformational 11Add bootloader to upgrade binary (#323)
Why it was queuedThis commit changes a build script so that the upgrade package now includes the bootloader alongside the main application firmware, and adds a safety flag that stops the script on first error. There is no direct evidence in the commit that this fixes a security vulnerability; it appears to be a build/packaging improvement.
6f66962a · Nov 27, 2025 · 3 filesInformational 15Update build firmware.sh to add no bootloader build by default (#315)
Why it was queuedThis change simply updates the project's firmware build script and documentation to also produce a 'no bootloader' firmware image by default. It is a developer convenience for testing on development boards and does not alter any runtime code, cryptographic checks, or security behavior of the actual device firmware.
7447f04a · Nov 27, 2025 · 2 filesTriage 18Change button text from 'Enter BIP-39 password' to 'Enter passphrase' (#327)
Why it was queuedb6778187 · Nov 17, 2025 · 1 fileInformational 11Revert "chore: adding the bootloader to upgrade binary for next release"
This reverts commit 54a38094e822c42b6acaabf30a5cbbca418388ef.
This commit undoes a previous change that added the bootloader to the device's upgrade binary. It removes the bootloader from the generated upgrade file and also removes a 'set -e' safety flag from the build script. On its own, this revert does not introduce a clear security vulnerability; it is a build-script change whose security implications depend heavily on whether the bootloader is supposed to be included in upgrades.
54a38094 · Nov 17, 2025 · 1 fileInformational 11chore: adding the bootloader to upgrade binary for next release
Why it was queuedThis is a build-script change for a hardware-wallet project. It adds a command-line flag so that the upgrade package generator includes the bootloader file alongside the main firmware. It also adds `set -e` so the build script stops on errors. There is no direct evidence in the commit that this fixes or introduces a security vulnerability; it appears to be a release-engineering change.
ce35419b · Oct 7, 2025 · 243 filesInformational 15chore: Get build back to work and some CI (#307)
* fix: pin dependencies via on nix and create flake
* ci: try build
* Update flake.nix
Co-authored-by: Ruben <36157890+ubbabeck@users.noreply.github.com>
* Update shell.nix
Co-authored-by: Ruben <36157890+ubbabeck@users.noreply.github.com>
* fix: as suggested by mike
* a bit more concrete prerequisites
* nix prefixes
---------
Co-authored-by: Ruben <36157890+ubbabeck@users.noreply.github.com>
This commit is a routine build and continuous-integration (CI) maintenance change for the Specter DIY hardware wallet project. It adds Nix package-manager files to pin build dependencies, a GitHub Actions workflow to compile the firmware, and a large amount of documentation, hardware files, and project scaffolding. There is no indication in the diff that any cryptographic, wallet, or firmware runtime code was changed in a way that introduces a security vulnerability.