Blockstream Jade

This commit only adds three new test data files for the Blockstream Jade hardware wallet. The files are deliberately invalid Liquid Bitcoin swap transactions used to verify that the device correctly rejects bad asset summaries. No production code was changed, so this commit does not introduce or fix a security vulnerability by itself.

This commit fixes a bug in the Blockstream Jade hardware wallet where a function that tracks assets during transaction signing could fail silently. Previously, if an unexpected or wrong asset was encountered while building a summary of transaction inputs and outputs, the wallet ignored the failure and continued signing. The patch now checks the function's return value and aborts signing with an error. This could have allowed a malicious or malformed transaction to bypass the wallet's balance checks, potentially misleading the user about what assets were actually being moved.

This commit updates a list of Python helper libraries used by the project, mainly to keep them in line with another related project called 'pinserver'. The changes bump versions of common networking and code-style packages (pycodestyle, idna, certifi, urllib3, charset-normalizer, requests). There is no direct evidence in the commit that this fixes a specific security vulnerability, but updating dependencies—especially urllib3 and requests—often includes routine security patches. The commit message does not describe a security issue.

This commit updates a submodule or external dependency called 'pinserver' to the latest master version in the Blockstream Jade hardware wallet project. The actual code changes are not visible because the diff is unavailable. Without seeing what changed in pinserver, we cannot determine whether this update fixes a security issue, adds a feature, or is routine maintenance. The title suggests it is a routine dependency update.

This commit only changes internal CI (continuous integration) configuration. It comments out automated test jobs that flash firmware onto older Jade v1.0 hardware because those devices do not reliably reboot during testing. There is no change to the product firmware, no user-facing change, and no security fix or vulnerability patch.

This commit reworks how a Blockstream Jade hardware wallet labels transaction outputs. The key change is that the 'change' flag is now only set when the output is also confirmed as belonging to the wallet ('is ours'). Previously, downstream code had to check both 'validated' and 'change' bits to safely hide a change output; now it can rely on the 'change' bit alone. The commit also renames the flag from VALIDATED to IS_OURS and adds comments. The stated intent is to prevent a change output from being marked as change unless it is also confirmed as a wallet output, which could reduce the risk of an attacker tricking the device into hiding a payment to an external address.

This is a large update that pulls in Espressif's ESP-IDF v5.5.4 bootloader code, plus Blockstream's own multi-signature secure-boot patches. Most of the visible changes are routine: support for newer ESP32 chips, larger flash sizes, and a new Trusted Execution Environment (TEE) mode. There are also several security-hardening touches, such as preventing the TEE from writing or erasing its own active flash partition and adding anti-fault-injection checks. However, the commit is a broad vendor SDK refresh rather than a single focused security fix, and the diff provided is only a partial sample of the whole change.

This commit simply updates the version of the Espressif build tools used by automated GitHub test builds from v5.4 to v5.5.4. It is a routine CI/CD maintenance change with no visible security relevance.

This commit explicitly sets the physical pins used for the device's main serial (UART0) communication on ESP32 chips. In newer ESP-IDF versions (from v5.5), the default pins are no longer assigned automatically, so without this change the serial port might not work at all or might map to unexpected pins. It is a hardware-configuration fix rather than a patch for an active security vulnerability, but misconfigured serial pins could in theory cause communication failures or expose debug traffic on unintended pins.

This commit is a routine build-system update that renames several ESP-IDF configuration options to match the names used in ESP-IDF version 5.5. It does not change any actual behavior or security settings of the firmware. The old and new configuration names control the same features, so this is purely a compatibility change.

This is a routine build-system update. It changes the Dockerfile to use a newer internal base image and a newer version of Espressif's ESP-IDF toolchain. There is no indication of a security bug, vulnerability fix, or malicious change in the commit itself.

This commit changes a build configuration script for the ESP32 version of Blockstream Jade. When Wi-Fi logging is enabled, the script now places some FreeRTOS operating system functions into flash memory instead of fast internal RAM (IRAM). The stated reason is to free up IRAM space so the firmware can compile. This is a build tooling change to avoid a linker memory overflow, not a fix for an exploitable security vulnerability.

This commit simply updates the version of Espressif's ESP-IDF development framework used to build Jade's Docker builder image, from v5.4.3 to v5.5.4. There is no indication in the commit of any security issue, vulnerability, or functional code change.

This commit simply updates the version (SHA hash) of a Docker build image used by the project in four configuration/documentation files. There is no code change, no vulnerability fix, and no security-relevant behavior change visible in the diff.

This commit updates two Python library version requirements in the Jade Python package's setup file. It raises the minimum required version of cbor2 (a data-serialization library) from 5.4.6 to 5.9.0, and updates the bleak Bluetooth library from 0.13.0 to 2.1.1 for the optional Bluetooth feature. The commit message gives no security reason for the change, and the diff alone does not show any vulnerability being fixed. It is most likely routine dependency maintenance, but pinning older, possibly insecure library versions can indirectly affect users if those older versions have known security flaws.

This update fixes a security gap in how Blockstream Jade signs Bitcoin transactions for a specific wallet type called Green 2of3. Previously, the device trusted the connected app to supply a recovery public key and might silently treat an output as 'change' going back to the user's own wallet. A malicious or compromised companion app could have supplied a fake recovery key, tricking the device into marking a payment to an attacker's address as safe internal change. The fix forces the user to manually verify such outputs on the device screen instead of trusting the app, matching the behavior already used for PSBT signing.

This commit simply bumps the version of a Python client library (jade-client) used by the project from version 1.0.37 to 1.0.40, and updates the corresponding cryptographic signature file. There is no indication in the commit itself that this is a security fix, vulnerability, or malicious change. It is a routine dependency update.

This commit updates the command-line tool for Blockstream Jade hardware wallets so that its 'sign transaction' command now requires additional pieces of information (the transaction inputs and any change output details) and formats its output as JSON. The change appears to be a normal feature/API update rather than a fix for a security vulnerability. There is no evidence in the commit that this was done to address a security issue.

This commit is a straightforward code cleanup. It replaces a verbose way of showing on-screen messages and errors with simpler helper functions, and fixes a spelling mistake ('re-encypt' to 're-encrypt'). There is no change to security logic, no bug fix, and no vulnerability addressed.

This commit simply moves existing production build configuration files from one folder (production/) into a subfolder (configs/production/). The contents of the files are unchanged, and only two helper scripts are updated to point to the new location. There is no change to the actual software behavior, security settings, or user-facing functionality.

This commit only adds automated security scanning steps to the project's continuous-integration (CI) pipeline. It does not change any firmware, application, or wallet code, and it does not fix a known vulnerability. It enables GitLab's built-in SAST, dependency-scanning, and secret-detection tools to run on future commits.

This commit is a small internal cleanup of how fonts are selected on the device's screen. It removes an unused second argument from the font-setting function and adds a minor caching shortcut so the same font isn't re-initialized repeatedly. There is no visible security change.

This commit simply deletes two unused font files and removes their references from a combined source file. It is a cleanup change with no security relevance.

This commit simply deletes a helper Python script used to capture image data from a Blockstream Jade hardware wallet. The commit message says the same task can now be done with jade_cli, so the old standalone script is no longer needed. There is no code change to the wallet firmware, no bug fix, and no security-related content in the diff or message.

This commit is a straightforward internal cleanup of how a hardware wallet's screen font lookup works. It rewrites a helper function to be faster and simpler, but does not change what the function does or fix any security problem. There is no indication this is a security patch.