Blockstream Jade

This commit changes how Blockstream Jade handles a private key used for PIN server authentication. Previously, the device kept the same private key even when the user changed or removed their PIN server settings. Now it deletes that key whenever the PIN server settings change, so a fresh key is generated the next time it is needed. This reduces the risk that an old or compromised key could be reused across different PIN server configurations.

This commit updates the code that signs Bitcoin transactions for Blockstream Jade's Green multisig wallets. It specifically adds support for '2-of-3 recovery signing,' where the Jade device acts as the recovery key rather than the regular user key. The change lets Jade recognize and sign recovery transactions it previously would have rejected. There is no clear security bug being fixed; it appears to be a feature addition to support a missing signing scenario.

This commit changes how Blockstream Jade hardware wallets sign Bitcoin transactions in a specific multi-signature setup called Green 2of3. It lets Jade act as the 'recovery signer' by deriving a special recovery key from the user's key when the first key in the transaction looks like a Blockstream Green server key. The change is a feature addition to support a previously unsupported signing scenario, not a fix for a known exploit. There is no evidence in the commit or supplied references that this is a security patch or that it addresses a disclosed vulnerability.

This commit is a pure variable rename inside a single function. The local variable `key_index` is renamed to `found_index` to make the code easier to read. No logic, behavior, or security properties change.

This commit is a small internal code cleanup in a Bitcoin hardware wallet library. It replaces an if/else branch that chose between two similar key-lookup functions with a single function pointer. There is no change to what data is read, what keys are used, or what is returned to the caller. It is a stylistic refactor, not a security fix.

This commit only corrects a spelling mistake in a code comment ('conenction' to 'connection'). It does not change any program instructions, behavior, or security logic.

This commit updates a bundled cryptographic library (libwally-core) to its latest master version. No actual code diff was provided—only a one-line submodule pointer change is described—so there is no visible evidence of any security bug, fix, or behavior change. It appears to be a routine dependency refresh.

This commit only updates the user documentation file FWUPDATE.md. It adds instructions for manually fetching firmware hashes, fixes grammar and style issues, and clarifies where to find published firmware metadata. No code, firmware, cryptographic, or security logic was changed.

This commit only removes a redundant note in the do-it-yourself hardware documentation. It deletes two parenthetical references to an older commit ID from lines describing the battery indicator on TTGO T-Display devices. There is no code change and no security relevance.

This commit only updates documentation in a README file. It corrects the battery description for two do-it-yourself hardware boards, noting that a battery connector is present and that the battery indicator works when a battery is attached. There are no code changes and no security relevance.

This commit is a build-script cleanup for Blockstream Jade firmware release tooling. It rewrites three shell scripts so they loop over a list of hardware directories (currently just 'jade2.0') instead of hard-coding that path, and adds 'set -e' to one script so it exits immediately on any error. The commit message explicitly says 'No functional changes.' There is no change to firmware code, cryptography, device behavior, or user-facing functionality, and no security issue is evident.

This commit only adds one-line human-readable comments to the top of 24 configuration files. It does not change any settings, code, or behavior. There is no security relevance.

This commit is purely a formatting cleanup in the project's internal GitLab CI configuration. It adds missing spaces between '&&' and './tools/switch_to.sh' in several build job scripts. There is no functional change, no security fix, and no change to the firmware or user-facing behavior.

This is a one-line change that adds a missing C header file include (#include "button_events.h") to a source file in the Blockstream Jade hardware wallet firmware. It is a routine build/fix commit with no apparent security relevance.

This commit only updates a documentation file (REPRODUCIBLE.md) that explains how to build Blockstream Jade firmware. It replaces manual copy-and-delete instructions with a helper script and fixes a typo. There are no code changes and no security implications.

This commit is a straightforward internal cleanup of how the firmware identifies different Jade hardware versions. It introduces broader 'any Jade v1/v2' configuration flags and replaces many scattered checks with simpler ones. There is no user-facing change, no bug fix, and no security alteration visible in the code.

This commit fixes missing battery icons on several hardware variants of the Blockstream Jade crypto wallet and tidies up power/battery code. The main functional change is that boards without a direct charging-status pin now report 'charging' whenever USB power is detected. That is a UI approximation, not a real charging measurement. There is no direct evidence in the commit of a security vulnerability, but the change could make a device falsely display a charging icon when it is merely plugged into USB without actually charging.

This commit is a configuration cleanup for the Blockstream Jade hardware wallet firmware. It generalizes the meaning of the 'HAS_BATTERY' setting so that battery-related and camera-related menu options are automatically hidden on device variants that lack those hardware parts. There is no direct security fix here; it is a maintainability and user-interface change that prevents unsupported features from being shown or compiled on devices that do not have the required hardware.

This commit fixes how two hardware variants of the Blockstream Jade crypto wallet (T-Display and T-Display S3) read battery levels and detect whether they are plugged into USB. It replaces an unreliable voltage-guess method with proper ADC hardware reading and, for the S3, uses the actual USB state. It also stops falsely showing a 'charging' icon. There is no obvious security vulnerability here; it is a hardware-support and user-experience fix.

This commit simply deletes four build configuration files used for QEMU emulator builds. It is a cleanup change with no code modifications and no apparent security relevance.

This commit simply deletes six build configuration files used for a special 'no-radio' variant of the Jade hardware wallet. The project says these files can be regenerated with a script, so this is a cleanup of duplicated build settings, not a security fix or vulnerability.

This is a developer-only build helper script update. It adds support for QEMU emulator builds, a few new build options, and a flag to skip reconfiguring the build. There is no change to the actual Jade firmware or wallet security logic, and nothing in the commit suggests a security fix or vulnerability.

This commit is a routine cleanup of the project's automated build configuration. It replaces a custom QEMU build setup with a shared helper script already used elsewhere. There is no change to the actual Jade firmware code, user-facing behavior, or security-sensitive logic.

This commit is a simple code cleanup: it renames an internal type and its values to make naming more consistent, and removes a few unnecessary local variables. There is no change to how the camera or QR scanning works, and no security impact.

This commit is a minor visual tweak for older Jade hardware wallets. It moves the corner guide lines shown around QR codes slightly farther inward on Jade v1 and v1.1 screens so they don't overlap the edges of the actual QR code. There is no security-relevant change.