Blockstream Jade

This commit fixes a bug in the Blockstream Jade hardware wallet's attestation signing process. Previously, if signing the attestation challenge failed, the device would send an error message but then continue running the rest of the function anyway, potentially sending an invalid or uninitialized reply back to the caller. The fix ensures the function stops immediately after reporting the error.

This commit fixes a bug in the Blockstream Jade hardware wallet where a function that tracks assets during transaction signing could fail silently. Previously, if an unexpected or wrong asset was encountered while building a summary of transaction inputs and outputs, the wallet ignored the failure and continued signing. The patch now checks the function's return value and aborts signing with an error. This could have allowed a malicious or malformed transaction to bypass the wallet's balance checks, potentially misleading the user about what assets were actually being moved.

This commit updates a submodule or external dependency called 'pinserver' to the latest master version in the Blockstream Jade hardware wallet project. The actual code changes are not visible because the diff is unavailable. Without seeing what changed in pinserver, we cannot determine whether this update fixes a security issue, adds a feature, or is routine maintenance. The title suggests it is a routine dependency update.

This commit reworks how a Blockstream Jade hardware wallet labels transaction outputs. The key change is that the 'change' flag is now only set when the output is also confirmed as belonging to the wallet ('is ours'). Previously, downstream code had to check both 'validated' and 'change' bits to safely hide a change output; now it can rely on the 'change' bit alone. The commit also renames the flag from VALIDATED to IS_OURS and adds comments. The stated intent is to prevent a change output from being marked as change unless it is also confirmed as a wallet output, which could reduce the risk of an attacker tricking the device into hiding a payment to an external address.

This is a large update that pulls in Espressif's ESP-IDF v5.5.4 bootloader code, plus Blockstream's own multi-signature secure-boot patches. Most of the visible changes are routine: support for newer ESP32 chips, larger flash sizes, and a new Trusted Execution Environment (TEE) mode. There are also several security-hardening touches, such as preventing the TEE from writing or erasing its own active flash partition and adding anti-fault-injection checks. However, the commit is a broad vendor SDK refresh rather than a single focused security fix, and the diff provided is only a partial sample of the whole change.

This update fixes a security gap in how Blockstream Jade signs Bitcoin transactions for a specific wallet type called Green 2of3. Previously, the device trusted the connected app to supply a recovery public key and might silently treat an output as 'change' going back to the user's own wallet. A malicious or compromised companion app could have supplied a fake recovery key, tricking the device into marking a payment to an attacker's address as safe internal change. The fix forces the user to manually verify such outputs on the device screen instead of trusting the app, matching the behavior already used for PSBT signing.

This commit is a straightforward code cleanup. It replaces a verbose way of showing on-screen messages and errors with simpler helper functions, and fixes a spelling mistake ('re-encypt' to 're-encrypt'). There is no change to security logic, no bug fix, and no vulnerability addressed.

This commit changes how message context is passed between functions in the Blockstream Jade hardware wallet firmware. Instead of copying the entire message context structure on the stack, functions now receive a pointer to it. The stated goal is to reduce stack memory usage. There is no direct evidence in the commit that this fixes an exploitable vulnerability, but reducing stack pressure can help prevent stack overflow crashes or corruption in a security-critical embedded device.

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 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 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 fixes a user-interface bug where the backspace icon was missing on the PIN entry screen and the checkmark/enter icon was missing on the index entry screen. It changes the number of allowed on-screen characters so the correct icons are displayed. There is no security issue here.

This update fixes a check in the Blockstream Jade hardware wallet's attestation setup. Before the fix, the code did not verify that an externally-provided signature was small enough to fit into its storage buffer. A too-large signature could overflow that buffer during verification, potentially corrupting memory or crashing the device. The patch adds a size check before calling the signature verification routine.

This update fixes how Blockstream Jade handles QR-code-based recovery phrases imported in a specific format (bcur-bip39). Previously, a malformed or invalid recovery phrase could crash the device because the code used internal 'assert' checks that halt the device when they fail. The patch replaces those hard crashes with proper error handling, rejects obviously wrong inputs earlier (wrong number of words, words that are too long, empty words), and reduces memory used on the stack. It also adds tests for bad inputs. In practical terms, scanning a bad wallet QR code is now more likely to show a user-friendly error instead of freezing or rebooting the device.

This commit tightens how Blockstream Jade handles the numbers inside OTP setup URLs (the 'counter' for HOTP codes and the 'period' for TOTP codes). Before the change, the code copied the number into a small temporary buffer and converted it with standard C library functions, which could silently accept non-digit characters, ignore overflow, or be fed an oversized input. The patch adds a strict decimal parser that only accepts digits, rejects values too large for the variable, and enforces length limits. The commit message credits the change to an external suggestion, but does not call it a security fix.

This commit increases the stack memory given to the device's on-screen user-interface task. The change is described as fixing a 'stack overflow' that could happen while verifying a special backup phrase called a 'BIP85 mnemonic.' A stack overflow in the screen task could crash the user interface or, in the worst case, be abused to disrupt the device during a sensitive wallet operation.

This commit adds the ability for the Blockstream Jade hardware wallet to read Google Authenticator's bulk-export QR codes (the 'otpauth-migration://' format). It converts those exported codes back into normal OTP URIs and registers them. The change is a feature addition, not a documented security fix. Because it parses an external, attacker-controllable protobuf payload and builds URIs from it, there is some potential for parsing bugs or malformed data to cause crashes or unexpected behavior, but the commit itself does not obviously introduce a known vulnerability.

This commit refactors how Blockstream Jade handles Base32-encoded one-time-password (OTP) secrets. It moves the Base32 decoder into a shared utility, adds a new encoder, and makes padding characters ('=') stop decoding instead of being rejected. The change is a routine code cleanup; there is no direct evidence in the commit that it fixes an active security vulnerability.

This commit fixes two security hygiene issues in the handling of one-time password (OTP) secrets in Blockstream Jade. First, it stops writing the raw OTP secret into device logs when decoding fails. Second, it marks the temporary memory buffer holding the decoded secret as sensitive so it is wiped after use rather than left behind. The change also removes a redundant size check because another function already performs it. There is no evidence in the commit of an active exploit or a reported incident.

This commit adds a new software component to the Blockstream Jade hardware wallet project. The component is a copy of the nanopb library plus generated code for parsing Google's OTP (one-time password) migration format. It is a dependency addition only: there is no actual user-facing feature or change to how secrets are handled in this commit. On its own, it does not fix or introduce a security vulnerability.

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 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 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 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.