Blockstream Jade

This commit is a performance optimization for drawing small icons on the Blockstream Jade hardware wallet screen. It replaces a helper function call that reads one pixel at a time with faster inline code that reads icon data in 32-bit chunks. There is no indication in the commit or supplied references that this fixes a security bug.

This commit is a straightforward performance optimization for how grayscale images are shown on the screen of a Blockstream Jade hardware wallet. It replaces a runtime color-conversion calculation with a precomputed lookup table. There is no security-relevant change visible in the code.

This is a minor code cleanup in the user-interface drawing code. It changes how one color value is passed between functions, removing an unnecessary pointer indirection. There is no visible security relevance.

This commit changes the on-screen QR scanning frame size on the Jade Plus hardware wallet (which uses an ESP32-S3 processor) from small to large for seed backup, wallet import, and one-time-password (OTP) setup. It is a user-interface adjustment to make QR codes easier to scan on the larger-screen device. There is no security vulnerability here.

This commit reverts a previous change that made the Jade Plus (ESP32-S3) camera use a higher VGA resolution. It returns all hardware variants to the lower QVGA resolution because QVGA was found to scan QR codes faster and more accurately on Jade Plus. It also removes the larger VGA test images and simplifies the output-message buffer size logic. There is no security fix or vulnerability here.

This commit updates a release signing helper script so the operator can optionally specify which serial port a connected Jade hardware device uses. It is a usability/operational change, not a fix for a software vulnerability in the device or wallet itself. There is no indication it addresses a security incident.

This commit fixes a trivial typo in a debug log message: a missing space between two words ('length ...and encoding' becomes 'length ... and encoding'). It has no effect on program logic, security, or behavior.

This commit adds a verification step to Blockstream Jade's internal release script. The script now checks that each firmware file's actual contents match a published hash after decompression. Previously, the script only checked that the hash file existed, not that it matched the firmware. This closes a gap where a corrupted or tampered firmware file could be distributed without being caught by the release-check process.

This change simply adds a console log message that prints the firmware file's hash before saving that same hash to a file. It does not alter security behavior, access controls, or cryptographic operations. It is a transparency/logging improvement for the build process.

This commit changes an internal release script used by Blockstream Jade developers. It switches from downloading firmware files over the public web (using wget) to copying them from a private Google Cloud bucket (using gcloud rsync). It also tightens a consistency check so release scripts now verify that every firmware file has a matching hash file, except for very old versions. There is no direct evidence this fixes a security vulnerability; it appears to be a build/release tooling improvement.

This commit updates an internal release script that checks Blockstream Jade firmware files hosted on a Google Cloud bucket. It adds a check for 'delta' firmware files that exist on the server but are not listed in the index. If any are found, the script now logs commands to delete them and fails the check. The change is a build/release hygiene improvement, not a fix for an active exploit or a vulnerability in the device firmware itself.

This change relaxes a command-line helper script used for firmware updates. Previously, the script would quit with an error if you gave it arguments like release version or hardware target when not actually downloading firmware. Now it simply ignores those extra arguments and prints an informational message. It also now explicitly tells the user when it is assuming default values (stable release, Jade v1.0 hardware). This is a usability improvement, not a security fix, and does not change how firmware is verified on the device itself.

This change simply moves and improves the logging of which Jade hardware device is about to receive a firmware update. Before, the device info was shown after the firmware download had already started; now it is fetched and logged first so the user can confirm the correct device before any download or update begins. There is no security vulnerability here.

This commit is a tiny user-experience improvement in a helper script for updating Jade hardware wallet firmware. It changes an internal assertion message to be more helpful when the user has provided the wrong command-line flag for extended replies. There is no security-relevant change.

This commit simply rearranges existing code in a Python helper script used for firmware updates. It moves the logic that decides where to fetch firmware from into a new function, without changing what the code actually does. There is no security issue visible in this change.

This commit is a straightforward internal refactoring of the firmware update helper script (jade_ota.py). It moves the firmware download step to happen after the device is connected, and passes the device info into functions instead of repeatedly querying it. There is no security bug being fixed here and no new vulnerability introduced.

This commit fixes a bug in the Jade hardware wallet's firmware update helper script. Previously, when a user ran a firmware download without explicitly saying which device model they had, the tool always assumed an old 'Jade 1.0' device. On newer devices this could cause the update to fail with an 'invalid firmware' error. The fix makes the tool look at the connected device and pick the correct firmware variant automatically. It is a reliability/usability fix rather than a remote exploit, but loading the wrong firmware onto a security device is a safety-critical mistake.

This commit simply comments out a broken code-coverage build job in the project's continuous-integration configuration. It is a build-maintenance change with no security relevance.

This commit changes only the Japanese regulatory compliance number displayed on the Jade hardware wallet's legal/about screen. It selects one number for older Jade v1.1 devices and a different number for newer Jade v2.0 devices. There is no security-relevant change.

This commit fixes a bug in how Blockstream Jade signs Liquid Bitcoin transactions. When extra data ('additional_info') was provided for a transaction input, the hardware wallet was not updating its internal running totals of input amounts per asset. This could cause the device to miscalculate whether a transaction is balanced—potentially allowing a malicious or buggy host to trick the wallet into approving a transaction that silently moves more value than the user expects. The fix makes the wallet explicitly require and record the input's asset and amount in this code path.

This commit only adds a new test data file for a single-signature asset swap on the Liquid network. It is a test fixture with no changes to production code, cryptographic logic, or wallet behavior. There is no security issue visible in the commit itself.

This change only affects the project's test script. It deletes leftover test PIN files before running tests so developers don't get confused by stale data from earlier runs. There is no security issue in the product itself.

This commit updates the Python library that talks to the Blockstream Jade hardware wallet. It lets callers pass an optional extra data dictionary called additional_info when signing a Bitcoin PSBT, matching a feature already available for Liquid transactions. The change itself just forwards the new parameter to the device; it does not appear to fix or introduce a vulnerability on its own.

This commit blocks PSET (a privacy-enhanced Bitcoin transaction format) parsing on Blockstream Jade hardware wallets that lack extra RAM (SPIRAM). The change prevents the device from running out of memory while handling complex PSET data. It is a hardening/defensive fix rather than a clear exploit patch, because the commit message and diff do not describe an actual vulnerability—only a known resource limitation.

This commit only adds new test cases for signing Liquid multisig transactions on the Blockstream Jade hardware wallet. It introduces two JSON test fixtures and a one-line change to include them in the test suite. There is no change to production code, no bug fix, and no security-relevant behavior.