Blockstream Jade

This commit changes how the QEMU emulator build of the Jade hardware wallet behaves when the firmware hits a critical error. Previously it would silently reboot; now it prints diagnostic information and halts. This is a developer/testing convenience change, not a fix for an exploitable security flaw in production devices.

This commit simply updates three build configuration files to use a newer version (different SHA256 hash) of the same 'blockstream/jade_builder' Docker image. There is no code change, no vulnerability fix, and no security-relevant behavior change visible in the diff.

This commit adds an optional logging switch to libjade, a Linux build of the Jade firmware used for in-process debugging. By default logging remains disabled, but developers can now turn it on with a --log flag. There is no security vulnerability here; it is a build/debugging convenience change.

This commit adds a new helper function that converts text into URL-encoded format (for example, turning spaces into '+' and special characters into '%XX'). It also makes a tiny internal helper function non-static-inline. There is no indication this fixes a security bug; it appears to be a routine feature addition.

This commit adds helper functions to convert FreeRTOS tick counts into regular clock time, and uses them to implement delay functions for the Blockstream Jade hardware wallet's simulator build. It is a normal feature/fix for the non-firmware simulator environment and does not appear to address a security vulnerability.

This commit changes how the Jade hardware wallet clears text shown on screen. Previously, ordinary memory freeing could leave sensitive strings (like seed words or passphrases) sitting in RAM. Now it uses a secure wipe function before freeing. The commit itself notes this is not a complete fix, because some UI elements are not yet covered by the secure-memory mechanism.

This commit simply updates the version of a Docker container image used for building and testing the Jade firmware. It changes three configuration files to point from one published image hash to another. There is no code change, no disclosed security fix, and no evidence of a vulnerability in the commit itself.

This change updates a developer build script so that, when enabling Wi-Fi logging on a Blockstream Jade device, it tries to auto-fill the user's current Wi-Fi network name and password from their Linux computer. The credentials are shown on screen as defaults and written into the device's build configuration. This is a convenience feature, but it increases the chance that real Wi-Fi credentials are copied into a firmware build configuration file and displayed in the terminal.

This commit is a harmless code-size optimization. It replaces the mathematical pow() function (used to calculate 10 raised to a small power) with a simple lookup table of powers of 10, allowing the compiler to remove the floating-point pow() library code and save about 3.9 KB of firmware space. The displayed asset amounts are computed the same way as before.

This commit only edits the project's CHANGELOG.md file. It updates a release date and adds a few bullet points describing new features and fixes, but it does not change any source code, firmware, build scripts, or configuration. There is no security-relevant change in the diff itself.

This commit simply swaps the SHA256 digest of the Docker base image used for building Jade firmware in three configuration files. There is no code change, no disclosed vulnerability, and no security signal in the commit itself or the supplied references.

This is a tiny build-script fix. After compiling a library, the script now moves up one directory so the printed instructions about where to find the compiled files point to the correct folder. It does not change any security-sensitive code or behavior.

This commit simply updates three configuration files to use a newer version of a Docker container image used for building and testing the Jade firmware. There is no code change, no user-facing behavior change, and no security issue visible in the diff itself.

This commit only edits the project's CHANGELOG.md file, adding release notes about new features, changes, and fixes. There are no code changes and no security-related content.

This commit is a routine build-system housekeeping change. It swaps the Docker image used for automated builds from 'verde' to 'jade_builder', updates the ESP-IDF framework version from 5.4.0 to 5.4.3, adjusts paths to the ESP-IDF installation, and refactors several CI helper scripts. There is no change to the wallet firmware code that handles private keys, transactions, or user data, and no security vulnerability is introduced or fixed in the diff itself.

This commit only changes one date in the project's CHANGELOG.md file, moving a release date from 2026-02-09 to 2026-02-18. There is no code change, no security fix, and no functional change of any kind.

This commit is a routine build-script maintenance change. It updates three release helper scripts so they use different firmware output directory names for two hardware variants (jade2.0 and jade2.0c). There is no user-facing security change, no vulnerability fix, and no change to cryptographic signing logic.

This commit only updates the project's CHANGELOG.md file, adding release notes for version 1.0.39. It does not change any source code, configuration, or executable behavior. The changelog mentions routine items such as faster QR scanning, a library update, and minor fixes, but nothing is disclosed as a security vulnerability, and no code is patched.

This commit adds a new utility file with helper functions that validate whether a Bitcoin key derivation path looks like one used by Blockstream Green wallets. There is no evidence in the commit that this fixes a security bug; it appears to be a new helper for recognizing Green wallet paths.

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 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 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 fixes spelling mistakes in code comments, changing the misspelled word 'implmentation' to 'implementation' across eight files. It does not change any actual program instructions, so it cannot affect security or functionality.

This commit only swaps the order of two C keywords ('const static' becomes 'static const') and adds a missing newline at the end of a file. It is a cosmetic/compiler-warning fix with no functional or security change.