Specter DIY

This commit fixes the firmware build process so that two people building from the same source code get the exact same binary file. Previously, the build script embedded local git details (like the repository URL, branch name, or commit hash) into the firmware, which changed the final binary depending on how the source was downloaded. The change strips those local details from release builds and adds tests to prove the output is now identical regardless of the source's git history. It is a reproducible-build hardening patch, not a fix for an exploitable vulnerability.

This commit fixes a security bug in how Specter DIY generates random numbers for creating cryptocurrency wallet secrets. Previously, if the hardware random-number generator (TRNG) stalled or failed, the device would silently use all-zero or mostly-repeated bytes, which could lead to predictable private keys and seed phrases. The patch adds a sanity check that rejects such 'dead' random output and raises an error instead of using it. The bug is serious because weak randomness can let an attacker guess a user's wallet keys, but the patch only detects obvious failures (all-zero or heavily repeated output), not every possible TRNG weakness.

This commit fixes a security bug in Specter DIY, a hardware wallet, where the device could wrongly hide a transaction output as 'change' (your own money coming back) when it actually went to an attacker or to another of your own wallet addresses. The old code trusted the host computer's claim that an output was change based only on which wallet owned the inputs. The new code independently re-derives the output address from the wallet's descriptor and only hides it as change when the math matches exactly, the descriptor has the standard two branches, and the output is on the change branch. It also warns the user when the host's metadata does not match.

This commit updates the embedded embit cryptography library to version 0.8.2 and adds a small compatibility shim so Specter DIY can accept a new style of Bitcoin wallet descriptor that mixes fixed and multi-path keys. Most of the changes are build/test plumbing (submodules, paths, smoke tests) rather than a security fix. There is no direct evidence in the commit that this resolves an exploitable vulnerability.

This commit restores a security warning on the Specter DIY hardware wallet. When a user is about to sign a Bitcoin transaction that spends coins from more than one wallet, or from several unknown sources, the device now shows a clear 'mixed inputs' warning at the top of the confirmation screen. This helps protect against a known class of attack where a malicious co-signer or software wallet can trick the device into sending change to the wrong address, potentially stealing funds. The warning had existed before but was accidentally dropped during an earlier code refactor.

This commit changes a single version number string in the bootloader from v1.10.1 to v1.10.3. There is no functional code change, no bug fix, and no security-relevant behavior modification. It is purely a release version bump.

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.

This commit simply updates a hardcoded firmware version string from v1.10.0 to v1.10.1 and removes a trailing space in a comment. There is no functional code change and no security relevance visible in the diff.

This commit only fixes three comments in the source code: two replace the word 'he' with 'they' for inclusive language, and one corrects 'dont' to 'don't'. No executable code, logic, or security behavior was changed.

This commit only updates two lines in documentation files: it renames the GUI library from 'LittlevGL' to 'LVGL' and fixes a grammar typo ('splitted' to 'split'). There are no code changes and no security implications.

This commit is a routine release preparation for the Specter DIY hardware wallet. The only meaningful change is updating an embedded version string from '0100900099' to '0101000099'. There are no security fixes, new features, or behavior changes visible in the diff.

This commit fixes a UI bug in the recovery phrase import menu. Previously, the menu showed buttons for import methods (like a QR scanner) even when those methods were disabled. Now it only shows methods that are actually enabled. This is a user experience fix rather than a security vulnerability.

This commit updates the list of trusted public keys used to sign firmware releases for the Specter DIY hardware wallet. One maintainer's key (ben) was removed and another maintainer's key (k9ert) was added. There is no code change that introduces a vulnerability or fixes one; it is purely a release-process key rotation.

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.

This commit adds support for a new QR scanner model (M3Y) and fixes several QR scanning bugs for existing GM65 scanners. The changes are primarily about hardware compatibility and reliability: making sure different scanner models are detected correctly, that large QR codes fit in the device's buffer, and that animated QR codes don't stop mid-scan. There is also a minor UI fix for colored progress icons. The commit does not appear to be a security patch; it is a feature and bug-fix update for hardware support.

This commit is a build-system and documentation refactor. It splits a single long firmware build script into smaller selectable actions (like 'build main firmware', 'build bootloader', 'assemble', 'sign', 'hash', etc.), fixes a Dockerfile environment-variable syntax, updates developer instructions, and adds a way to fix file ownership when running builds inside Docker. There is no indication it fixes a security vulnerability or introduces a security-relevant bug.

This 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.

This commit fixes how the project's test scripts set up Python's module search path and how they detect a missing optional dependency. It only changes files inside the 'test/' directory, which are used for running automated tests on a regular computer, not the actual hardware wallet firmware. There is no indication this fixes a security vulnerability.

This commit is primarily a hardware-compatibility fix for newer GM65 QR scanners used with the Specter DIY Bitcoin hardware wallet. It adds logic to detect a specific scanner firmware version and enable a special 'RAW' mode so binary QR codes (CompactSeedQR) scan correctly. It also adds an 'About this device' screen showing firmware and security metadata, and embeds git build info into firmware images. There is no obvious security vulnerability being patched; the changes are defensive and improve device transparency.

This 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.