Blockstream Jade

This commit increases the time the Jade hardware wallet waits for the rest of a large message sent over its USB/serial connection from 2 seconds to 3 seconds, but only for older v1.x devices. The change is described as a workaround; the commit message says a proper fix would require sending the message length first so the receiver knows exactly how much data to expect. The change itself is a simple timeout bump and does not appear to introduce a security vulnerability, but it highlights a reliability issue that could, in theory, be abused to desynchronize or confuse the device by sending partial messages.

This is a one-line change to a GitLab CI pipeline file. It adds a command to load the ESP-IDF build environment before running an over-the-air (OTA) delta firmware test for version 2 hardware. There is no change to device firmware, user-facing behavior, or security-sensitive code.

This commit only changes a test script. It raises the acceptable memory-fragmentation threshold for a newer Jade hardware version (JADE_V2) during automated continuous integration testing. There is no change to the actual device firmware, no user-facing behavior change, and no security fix or vulnerability present in the diff.

This commit is a small code cleanup in the part of Blockstream Jade that displays wallet backup words on screen. It changes how four word-pointers are passed between internal functions so they live in caller memory rather than being copied as function arguments. The stated goal is to reduce stack memory use during mnemonic verification. There is no direct evidence in the commit of a fix for an exploitable security bug, but reducing stack pressure can help prevent crashes or memory corruption in constrained hardware wallets.

This commit slightly increases the memory stack reserved for the device's on-screen user-interface task. The change is specifically for builds that have 'stack protection' enabled, a compiler hardening feature. The one-line patch suggests that when stack protection is turned on, the GUI task was running out of stack space, which could cause crashes or instability. There is no direct evidence in the commit that this fixes an exploitable security vulnerability; it reads more like a hardening/stability fix.

This commit only adds a code comment explaining an existing limitation in how Blockstream Jade detects Green multisignature transactions. No code behavior changes. The comment documents that for a specific 2-of-3 recovery wallet setup, the device may skip extra Green-specific validation and fall back to treating the transaction as a standard 2-of-3 multisig, but signing still works correctly.

This commit changes internal CI (Continuous Integration) scripts used to flash firmware onto test devices during automated builds. It temporarily removes a file-locking wrapper around flashing commands because GitLab was not reliably killing background processes. There is no change to the actual Jade firmware, wallet code, or anything end users install. It is purely a build/test infrastructure adjustment.

This commit simply deletes old helper scripts and instructions used to flash early 'Jade v1' hardware devices. No code that runs on the Jade wallet itself is changed, and nothing in the commit fixes or introduces a security vulnerability. It is a cleanup of obsolete tooling.

This commit only changes internal continuous-integration (CI) scripts that run automated hardware-in-the-loop tests for Blockstream Jade firmware updates. It disables Bluetooth OTA delta testing when the required Bluetooth tool is missing, adds support for the newer Jade v2 hardware, and lets developers run the same scripts locally. There is no change to the firmware, wallet logic, cryptography, or any code that end users run, so this commit does not create or fix a security vulnerability.

This commit only changes internal continuous-integration (CI) scripts. It disables flaky Bluetooth tests by passing a --skipble flag and makes minor shell-script cleanups. There is no change to the actual Jade firmware, wallet application, or any code that end users run.

This commit only renames the labels used to pick which GitLab CI runner executes firmware flashing jobs. It does not change any code that runs on the Jade device, nor any build logic, secrets, or network behavior. There is no security relevance visible in the change.

This commit only adds a new test case and updates a description of an existing test. It does not change any production code. The new test documents that when a recovery key is provided with a full derivation path (from the master key), a Blockstream Jade device will still sign the transaction, but a helper function called is_green_multisig_signers() will return false, meaning some extra Green 2of3 validation is skipped. Because no actual signing logic is changed, this commit by itself is not a security fix or vulnerability.

This commit simply raises the time limit allowed for a hardware self-test in a test script. It is a routine CI/testing adjustment with no security relevance.

This commit refactors how a wallet's secret recovery phrase (mnemonic) is handled on screen during verification. Instead of keeping an array of direct memory pointers to each word, it now stores offsets into the original phrase buffer. The stated goal is to reduce stack memory usage. The change also makes the code treat the mnemonic as read-only ('const') in more places, which is a defensive improvement. There is no direct evidence in the commit of an exploitable vulnerability being fixed, but reducing stack pressure and avoiding extra pointers to secret data is a sensible hardening measure.

This commit only adds a new test data file containing a sample Bitcoin transaction (PSBT) for a multi-signature wallet scenario. It does not change any actual wallet code, cryptography, or security logic. There is no indication of a vulnerability or security fix.

This is a small bug-fix in the Python library that talks to Blockstream Jade hardware wallets. When the code was asked to read zero bytes, it previously passed that request straight to the underlying transport, which could misbehave or return unexpected results. The fix makes it return an empty response immediately instead. It is a robustness improvement rather than a clear security vulnerability.

This commit is a cleanup of the device attestation code in Blockstream Jade, which is the cryptographic proof that the device is genuine. The changes fix a memory-management bug where sensitive key data could be cleared in the wrong order, correct a logic issue when debug mode is enabled, avoid repeatedly reloading attestation data from storage, ensure cryptographic keys are initialized before being freed, and move a large attestation data structure from the stack to the heap to prevent a possible stack overflow. Most changes are defensive hardening, but the SENSITIVE_POP ordering and the debug-mode logic fix are genuine security-relevant corrections.

This commit simply adds more information to an existing device status report (the 'get_version_info' RPC). It now reports whether tamper-evident attestation is active, the battery voltage, and whether the battery is charging. There is no change to security logic, access control, or cryptography. It is a routine telemetry/informational enhancement.

This commit changes how debug logging is handled in a library version of Blockstream Jade (libjade). When a build option that disables logging is set, the code now completely removes the internal log-level variable and the function that adjusts it, rather than just setting them to 'no logging.' This is a hardening/cleanup change that reduces the chance that sensitive debug information could accidentally leak in builds meant to be silent, but it does not by itself fix any active vulnerability.

This commit adds a new feature to Blockstream Jade hardware wallets that lets the user export an extended public key (xpub) as a file to a connected USB storage device. The feature only works when the device is unlocked and explicitly disallows multisig exports. It is a normal product feature, not a fix for a known security bug. There is no evidence in the commit or supplied references that this is a security patch or that it addresses any disclosed vulnerability.

This change only affects how test firmware is built in the project's continuous integration (CI) pipeline. It removes a debug logging flag so that test builds more closely match the firmware actually shipped to users. There is no user-facing code change and no security fix or vulnerability patch.

This commit changes a helper function that turns numeric Bitcoin key paths (like 0/1/2) into human-readable text. It adds an option to leave off the leading 'm/' so callers that only want the raw path can get it. All existing callers are updated to keep the old behavior (with the 'm/'), so there is no immediate change in behavior. It appears to be a code cleanup or preparation for a future feature rather than a fix for an active security problem.

This commit adds support for a new hardware variant called Jade Core (jade_v2c), which is a Jade Plus device without a camera or battery. The changes are purely build, configuration, release-script, and documentation updates to recognize the new board type. There is no indication of any security vulnerability being fixed or introduced.

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 moves when a special device private key (used for PIN server authentication) is created. Previously it was generated at every boot if missing; now it is created only when actually needed during a PIN operation. This is a code-quality and reliability change that reduces unnecessary key creation at startup, but it does not appear to fix an active security vulnerability.