Blockstream Jade

This commit simply renames the displayed issuer label for the Liquid Bitcoin token from 'peg-in' to 'federation' in the wallet's built-in asset list. It is a cosmetic string change with no security relevance.

This commit only updates QEMU emulator helper scripts and documentation. It renames a script from make-flash-img.sh to make_flash_img.sh, adds command-line options, updates README instructions, and removes an unused reboot script. There is no change to the actual Jade firmware or wallet security code.

This change only adjusts the project's automated test suite. It adds a one-second wait before sending a 'ping' check so the test hardware has time to finish background tasks before the test asserts it is idle. There is no change to the actual Jade firmware or wallet software that users rely on, and no security fix or vulnerability is present in the diff.

This commit only turns on diagnostic logging for automated QEMU (emulated hardware) test runs in CI. It adds a new logger that writes messages to the emulated serial port, changes CI scripts to capture that output, and adjusts a build helper so the '--log' flag is allowed for QEMU builds. There is no indication it fixes or introduces a security vulnerability.

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 change simply adds a user-configurable timeout to a serial connection script used for firmware updates, and uses a longer timeout during automated testing in a simulated (QEMU) environment. There is no security issue here.

This commit only changes test code to print more helpful error messages when a test assertion fails. It does not modify the actual Jade wallet firmware or any production code. There is no security issue here.

This commit is a routine code cleanup in Blockstream Jade's QR message handling. It removes a helper function that added an extra memory allocation and copy, and instead lets callers reserve a leading byte directly when allocating the buffer. There is no indication this fixes a security bug; it appears to be an efficiency and consistency improvement.

This commit only changes how automated tests are run. It adds an option to run a random 33% sample of test cases when testing in a slow emulator (QEMU), in order to save CI time. It does not change any wallet, firmware, or cryptographic code that end users interact with.

This commit is a straightforward maintenance change: it removes the old firmware-level gcov code-coverage support and switches to a new libjade-based coverage workflow. There is no security bug being fixed here, and no new attack path is introduced. The only user-visible change is that the 'GCOV' field is no longer reported in the get_version_info RPC response.

This commit adds a desktop GUI mode for testing the Jade hardware wallet firmware on a regular computer. It is a development/testing feature, not a change to the production firmware that runs on real Jade devices. The code introduces a new event-dispatching shim and lets a Python/Tkinter window drive the firmware's screen and buttons. There is no indication this fixes a security vulnerability; it is a tooling enhancement.

This commit only changes a release date in the project's CHANGELOG.md file. It does not modify any software code, security settings, or functionality. There is no security relevance.

This commit bumps the firmware 'secure version' number from 1 to 2 across all production builds of the Blockstream Jade hardware wallet. On its own, increasing this number is a defensive measure that prevents the device from accepting older firmware (anti-rollback). It does not by itself fix a bug, but it is typically done after a security fix so that attackers cannot downgrade to a vulnerable version. The change is therefore a security-related build configuration update, not a direct vulnerability patch.

This commit only updates the project's CHANGELOG.md file. It corrects the release date for version 1.0.39 and adds the changelog entry for the new 1.0.40 release. There are no code changes, no security fixes applied, and no security vulnerability introduced.

This commit only wraps three optional hardware-specific functions in conditional compilation guards so the code compiles cleanly on QEMU emulator builds that lack a camera or battery. It is a build-warning cleanup with no security relevance.

This commit only bumps a version string in a Python package from 1.0.39 to 1.0.40. There are no code behavior changes, no bug fixes, and no security-related content in the diff or commit message.

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 a new command-line option that lets users run the Jade CLI with a local software simulator ('libjade') instead of a real hardware device connected over USB/serial. It is a feature addition, not a security fix or vulnerability.

This commit simply updates a dependency called wallycore (a cryptography library used by Blockstream Jade) from version 1.5.1 to 1.5.3 in the Python pinserver requirements. The diff only changes pinned package hashes; there is no code change or explanation of why the update was made. Without a vendor security advisory or changelog, we cannot tell whether this fixes a security issue or is just routine maintenance.

This commit updates a bundled software library (libwally-core) to a newer release, version 1.5.3. No actual code changes are shown, and no security-related information is provided in the commit message or title. It appears to be a routine dependency update.

This commit adds a new device command that lets a connected computer or phone ask a Blockstream Jade hardware wallet to display an encrypted BIP85 seed-entropy backup as a QR code. The change also tightens validation of the BIP32 index in several places, fixing a place where an out-of-range index was accepted. There is no direct evidence in the diff of a vulnerability being exploited, but the new QR-display path and the tightened validation are security-relevant.

This commit only adds documentation for an existing RPC command called show_bip85_bip39_entropy. It does not change any code, so it cannot introduce or fix a security vulnerability by itself.

This commit adds support for a new do-it-yourself hardware build of the Blockstream Jade wallet using an ESP32-S3 development board, a small LCD screen, and a camera module. It only adds configuration files, documentation, and a build job. There is no indication of a security fix or vulnerability.

This commit changes the logic in Blockstream Jade's PSBT signing flow so that, when the hardware wallet is acting as a 'recovery' key for a Green 2-of-3 wallet, it always asks the user to confirm outputs that belong to Green, rather than silently trusting them. Previously, the code skipped confirmation if Jade detected it was the recovery key and the output matched a Green script. The change flips the condition: now, if Jade is the recovery key OR the script does not match Green's expected pattern, the output must be confirmed. This is a defensive fix to prevent a compromised companion app or host from sneaking an unverified output past the user during recovery signing.

This commit updates a Python helper-library dependency called cbor2 from version 5.7.1 to 5.9.0. The old version was pinned because of a known upstream bug (cbor2 issue #272). The change itself only swaps pinned hashes in a requirements file, so it is a routine maintenance patch rather than a direct code fix. It likely removes a known defect or security issue in the dependency, but the commit does not say the issue is exploitable in Jade itself.