Blockstream Jade

This commit only adds a new test file that exercises an existing URL-decoding function. It does not change any production code, so by itself it cannot introduce a security vulnerability or fix one. It is a defensive-quality improvement that adds self-tests.

This commit only deletes test files and test code for multisignature wallet features from the Blockstream Jade test suite. It does not change the actual firmware, runtime code, or how the device handles multisig wallets. There is no security fix or vulnerability introduced here—only a cleanup of automated tests.

This commit adds a new automated test file that checks whether sending a simple 'ping' message to a Jade hardware wallet interrupts an ongoing signing process. It is purely a test addition with no changes to production code, and it does not fix or introduce any security vulnerability.

This commit removes a leftover Git submodule reference (a 'gitlink') that had no matching configuration entry. It fixes a Git checkout error but does not change any compiled code, cryptographic logic, or device behavior. There is no security issue here.

This is a small build-fix change. The project has mock versions of ESP logging macros used when building on a regular computer (host build). Previously these macros treated the log tag as a string literal, which broke compilation when a module passed a variable tag. The patch changes the macros to print the tag via %s instead. There is no security issue here.

This commit adds a new command-line command called 'selfcheck' to the Jade CLI tool. It simply calls an existing device function and prints the result. There is no indication of a security fix or vulnerability being patched.

This commit adds a screen brightness control feature for the TTGO T-Display development board used with Blockstream Jade. It is a hardware-support change, not a security fix or vulnerability. There are no security signals in the code or commit message.

This commit only changes CI (Continuous Integration) pipeline configuration. It tells certain automated test jobs not to download build artifacts from previous stages because those tests do not need them. There is no change to the actual Jade firmware, wallet logic, cryptography, or any code that users run.

This commit adds input validation to make sure the text shown in the OTP (one-time password) setup screen is properly URL-encoded and printable. It is likely a hardening fix to prevent malformed or sneaky label/issuer strings from confusing the user or causing unexpected behavior on the hardware wallet's screen, but the commit message does not call it a security fix.

This commit only updates documentation. It adds a description of an optional 'genesis_hash' parameter for Liquid transaction signing and removes trailing whitespace. There are no code changes, so it cannot directly introduce or fix a security vulnerability.

This commit changes how Blockstream Jade handles the 'genesis blockhash' when signing Liquid transactions. Previously, the device only accepted the network's built-in genesis hash. Now it lets users provide a custom genesis hash for test networks (like regtest), but blocks attempts to use the real Liquid mainnet genesis hash on test networks to prevent spoofing. The change also applies the same validation to both PSBT/PSET signing and raw transaction signing. It appears to be a hardening/feature addition rather than a fix for an active exploit, but it does close a spoofing path on test networks.

This commit changes a CI/CD configuration file so that QEMU-based test jobs run on a dedicated GitLab runner tag (ga-qemu) instead of a shared one (ga). The stated purpose is to limit QEMU jobs to one per physical CI box, likely to avoid resource contention or hardware conflicts during automated testing. There is no change to the Blockstream Jade firmware, wallet logic, cryptography, or any code that end users run.

This commit adds compiler annotations (WARN_UNUSED_RESULT) to functions that return success/failure codes, so the compiler will warn if a caller ignores the result. It also fixes a few places where return values were being ignored, replacing them with safer default-value helpers. The changes reduce the chance that a malformed or missing RPC parameter silently causes wrong behavior, such as using an empty wallet path or a false success flag. This is a defensive hardening patch rather than a confirmed exploit fix.

This commit simply renames an internal helper function from `rpc_get_uint64_t` to `rpc_get_uint64` and updates every place that calls it. There are no changes to what the function does, how it checks data, or how secure it is. It is a routine code cleanup with no security relevance.

This commit is a simple rename of two internal helper functions from `rpc_get_boolean`/`rpc_get_boolean_or` to `rpc_get_bool`/`rpc_get_bool_or`, updating all call sites accordingly. There is no change to what the code does, no bug fix, and no security relevance.

This commit is a straightforward code cleanup that replaces verbose 'read this optional value, or leave the default' patterns with shorter helper functions that do the same thing. There is no change in behavior and no security issue visible in the diff.

This commit tightens how Blockstream Jade handles the 'precision' value in asset contracts for Liquid assets. Previously, a very large precision value could be accepted and later used to read past the end of an internal lookup table (POW_10), which could cause a crash or undefined behavior when displaying or signing a transaction. The patch caps precision at 8 and adds a compile-time check that the lookup table is sized correctly for that cap.

This commit adds convenience functions that read settings from CBOR messages and return a default value if the setting is missing or invalid. It is a straightforward feature addition with no visible security bug.

This commit strengthens a security guardrail on Blockstream Jade hardware wallets by turning on the most thorough stack-smashing protection for production builds. Stack smashing is a common way attackers try to take control of a device by overflowing a memory region; enabling 'ALL' mode tells the compiler to insert checks on every function, rather than only risky-looking ones, making exploitation harder. It is a defensive hardening change, not a fix for a known active bug.

This commit simply updates the SHA256 digest of the 'blockstream/jade_builder' Docker image used for building and testing Jade in four configuration files. There is no code change, no disclosed security fix, and no evidence in the commit or supplied references that this update addresses a vulnerability.

This commit is a large feature/refactor patch for Blockstream Jade's libjade (a desktop emulator of the Jade hardware wallet). It adds RPC endpoints that let a host application read the emulated device's screen, push fake button presses, read/write all emulated flash storage (NVS), and feed camera frames. The README explicitly warns that these RPCs mean 'a libjade instance is NOT SECURE FROM EXTERNAL APPLICATIONS, and that SECRET DATA CAN BE READ FROM THE RUNNING FIRMWARE.' The change is intended for development/testing only, but it removes the option to build without GUI support and makes the GUI code always compiled in. The security relevance is therefore primarily about increased attack surface and accidental misuse of a testing tool, rather than a vulnerability in production hardware wallets.

This commit fixes a race condition in the Blockstream Jade hardware wallet's camera and screen rendering code. When the camera task finished, its stack memory could be freed while the GUI task was still trying to draw the last camera image, potentially causing a crash or corrupted display. The fix adds a new function that safely clears the picture reference under a lock before the camera task's memory is released.

This commit simply updates the version of a Python library called cbor2 from 5.9.0 to 6.1.2 in the project's dependency list. There is no information in the commit itself saying this fixes a security problem. It is a routine dependency bump with no visible security relevance based on the provided materials.

This commit fixes a user-interface navigation quirk on the M5StickC Plus 2 hardware for Blockstream Jade. When entering a PIN, the up/down button directions were not inverted to match the rest of the device's menus, making number entry confusing or inconsistent. There is no security vulnerability here—just a UI consistency bug.

This commit adds three simple file-like method declarations (readable, writable, seekable) to a Python class that communicates with a Blockstream Jade hardware wallet. The change appears to be a compatibility fix so the Jade interface object works correctly with newer versions of the cbor2 library, which may now expect these methods to exist. There is no obvious security vulnerability in the diff itself; it is a small API compatibility patch.