Blockstream Jade

This commit adds a new intermediate menu screen for one-time password (OTP) entries in the Blockstream Jade hardware wallet. When a user views an OTP, they now see a menu with 'View' and 'Export' options. The 'Export' button currently just shows a placeholder message saying the feature is not implemented yet. There is no security-relevant change in this commit.

This commit is a small code cleanup in the QR-code display module of the Blockstream Jade hardware wallet firmware. It extracts a repeated size-calculation into a helper function and replaces a variable with the hard-coded value 32 (the number of bits in a uint32_t). There is no change in behavior and no security fix.

This commit fixes a mismatch between what a function called register_otp_string() actually returns and what callers expect. The function used to claim it returned a simple true/false value, but it was really returning numeric error codes. The fix changes the declared return type from bool to int so the code matches reality. This is a cleanup that prevents callers from misinterpreting error codes as plain failure, but the diff does not show an active exploit path on its own.

This commit simply updates the version of a Docker container image used for building and testing the Jade firmware. It changes three configuration files to point from one published image hash to another. There is no code change, no disclosed security fix, and no evidence of a vulnerability in the commit itself.

This commit simply moves a helper function that breaks a long text string into smaller chunks from one source file to a shared utility file. The code itself is unchanged, and there is no indication of a security fix or vulnerability.

This change updates a developer build script so that, when enabling Wi-Fi logging on a Blockstream Jade device, it tries to auto-fill the user's current Wi-Fi network name and password from their Linux computer. The credentials are shown on screen as defaults and written into the device's build configuration. This is a convenience feature, but it increases the chance that real Wi-Fi credentials are copied into a firmware build configuration file and displayed in the terminal.

This commit is a harmless code-size optimization. It replaces the mathematical pow() function (used to calculate 10 raised to a small power) with a simple lookup table of powers of 10, allowing the compiler to remove the floating-point pow() library code and save about 3.9 KB of firmware space. The displayed asset amounts are computed the same way as before.

This commit updates the Python Bluetooth library used to talk to Blockstream Jade hardware wallets from an older version (bleak 0.13.0 with dbus-next) to newer versions (bleak 2.1.1 with dbus-fast). The code changes are mechanical API adjustments: how the app scans for devices, how it reads descriptors, and how it stores the receive characteristic. There is no direct evidence in the commit that this fixes a specific security vulnerability, but updating dependencies can remove known bugs or weaknesses in the Bluetooth stack. The commit message does not describe any security issue.

This commit changes how a one-time passcode (OTP) is shortened to the requested number of digits. Previously the code used the floating-point math function pow() to compute 10^digits, which can introduce tiny rounding errors. Now it uses fixed integer constants (1,000,000 for 6 digits and 100,000,000 for 8 digits). The change removes a potential source of incorrect OTP values and also drops an unnecessary math-library dependency, but the commit message does not frame it as a security fix.

This commit changes how a hardware wallet (Blockstream Jade) turns on-screen digit entries into a numeric value. It replaces a floating-point math function (pow()) with simple integer arithmetic and switches the number type from size_t to uint32_t. The change is defensive: using pow() with floating-point numbers for integer digit values can introduce tiny rounding errors, and size_t is unnecessarily large/wide for this purpose. The commit does not by itself fix a known exploitable bug, but it removes a risky pattern in security-sensitive code that handles BIP85 child mnemonic indexes.

This commit is a user-interface refactor for the Blockstream Jade hardware wallet. It replaces a PIN-only digit-entry screen with a shared 'digit entry' widget that can also accept shorter numeric indices (for things like BIP85 child mnemonic indexes or account indexes). The PIN entry behavior itself is preserved: PINs still require all six digits. The main functional change is that index entry can now be shorter than six digits, which is a usability improvement rather than a security fix. There is no vendor statement that this change addresses a security vulnerability.

This commit only edits the project's CHANGELOG.md file. It updates a release date and adds a few bullet points describing new features and fixes, but it does not change any source code, firmware, build scripts, or configuration. There is no security-relevant change in the diff itself.

This commit changes the on-screen confirmation message shown to users when a specific BIP85 entropy export is requested. Normally the device warns that it is exporting an encrypted seed phrase for a specific BIP85 index. For the exact combination of a 12-word seed phrase at index 26589, the device instead shows a friendly 'Scan successful! Continue to pair with wallet app.' message under the title 'Enable Swaps'. The underlying cryptographic operation is unchanged; only the user-facing text is different. This could mislead users about what is actually being exported, but it does not by itself bypass the user's approval button press.

This commit simply swaps the SHA256 digest of the Docker base image used for building Jade firmware in three configuration files. There is no code change, no disclosed vulnerability, and no security signal in the commit itself or the supplied references.

This commit rolls back the software framework (Espressif IDF) used to build Blockstream Jade hardware wallets from version 5.4.3 to 5.4.0. The stated reason is that 5.4.1 through 5.4.3 introduce Bluetooth bugs that break Bluetooth on older 'v2' Jade devices. The team considers the newer bug-fix releases too risky to ship because the upstream framework's own version history is broken, making it hard to isolate which changes cause the Bluetooth problems. This is a defensive, risk-reduction change rather than a fix for an active exploit.

This commit changes how Blockstream Jade's Bluetooth Low Energy (BLE) code retries sending data. Previously, if the system ran out of temporary memory buffers, the code would crash with an assertion failure. Now it treats that situation like any other send failure and retries. It also retries more often and faster to stay within typical BLE timeouts, and reduces how often warning messages are logged. The change is a robustness improvement rather than a clear security fix, but the removed assertion crash could have been triggered by an attacker exhausting buffers.

This commit changes how three internal Bluetooth-related data structures are initialized in the Blockstream Jade hardware wallet firmware. Previously, two structures were declared without initialization and later zeroed with memset(), while one was declared without initialization and never zeroed. Now all three are initialized to zero at the point of declaration, and the redundant memset() calls are removed. The change is defensive and reduces the risk that future edits could accidentally use uninitialized memory. There is no direct evidence in the commit that this fixes an exploitable security vulnerability.

This is a tiny build-script fix. After compiling a library, the script now moves up one directory so the printed instructions about where to find the compiled files point to the correct folder. It does not change any security-sensitive code or behavior.

This commit only changes a GitLab CI configuration file. It comments out one automated test job (flash_qemu_psram) because the same scenario is already tested by another job (flash_qemu_psram_unamalgamated). There is no change to the actual Jade firmware, wallet code, cryptography, or anything users interact with. It is purely a pipeline optimization to avoid redundant testing.

This commit simply updates three configuration files to use a newer version of a Docker container image used for building and testing the Jade firmware. There is no code change, no user-facing behavior change, and no security issue visible in the diff itself.

This commit changes the project's Docker build file to use a custom-built base image instead of the upstream Espressif one, and adds the g++ compiler package. The change is described by the project as a workaround for a bug where the upstream Docker image produces bad firmware images for older 1.x Jade devices. There is no security-relevant change visible in the diff itself.

This commit adds a new manual CI job that builds a custom Docker base image for compiling Jade firmware. It is a build-infrastructure change, not a code change that affects the device firmware itself. There is no security vulnerability in the diff.

This commit is a routine developer tooling cleanup. It removes a separate debug script and instead lets the same launch script start the emulator in debugger mode when a --gdb flag is passed. There is no change to the actual Jade firmware or to how end-user devices behave.

This commit is a routine build-system fix for the QEMU emulator Dockerfile used in development and testing. It switches the Docker base image and simplifies the build steps so the documented README commands work correctly. There is no indication this change affects the security of the actual Jade hardware wallet firmware or introduces any vulnerability.

This commit only updates the README.md documentation to reflect new Docker build instructions for running a Jade emulator. No source code, build scripts, or configuration files were changed. There is no security-relevant content.