BS
← All projectsBlockstream

Blockstream Jade

Firmware for Jade and Jade Plus Bitcoin hardware wallets.

BitcoinHardware walletsElevated watch
Repository coverage

557 commits in the local evidence base

Every captured commit receives deterministic security triage and a separate communication-quality score. Security candidates and broader second-pass signals receive full-patch Ollama analysis.

120security candidates80second-pass queue462AI analyses
0commits · 30 days
47commits · 60 days
209commits · 180 days
423commits · 365 days
Backfill bands
Aug 5 → Feb 6216 seen38 candidatesComplete
Feb 6 → Jun 6131 seen9 candidatesComplete
Jun 6 → Jul 657 seen10 candidatesComplete
Jul 6 → Aug 510 seen0 candidatesComplete
Commit communication

Does the history explain itself?

Message quality measures whether a commit identifies its scope, purpose, rationale, testing, and supporting references. It does not change the security-severity score.

57/100 average clarity
37Strong · 80–100
204Adequate · 60–79
275Thin · 40–59
41Opaque · 0–39
5security candidates with opaque commit messaging
Read the scoring rubric →
Developer activity

Who is changing the project?

Public Git author strings; identities are not independently verified.

DeveloperCommitsCandidatesAnalyzedHigh riskMessage avg.
Jon Griffiths32663289157
Mike Tolkachev541744153
Daniel Newton902078055
Mihailo Milenkovic878057
roderico633074
Valerio Vaccaro2226056
Jamie C. Driver525053
Gustavo Cateim917078
Austin-Fulbright414060
kkdao211068
quantpoet111072
cmiguelrn111045
Analysis record

Published AI watches

Last scanned 43 minutes ago

Moderate 57 AI analysisMessage 45 · Thin
BS BlockstreamBlockstream Jade BitcoinHardware wallets

process: whitelist reply message function calls

This commit adds a whitelist of approved functions that can be used when sending reply messages from the Jade hardware wallet to a connected computer or phone. Previously, any function could be passed in, which could allow a bug or malicio…

Function-pointer whitelist added to reply pathMultiple static reply helpers made global to enable whitelist comparisonAssertion tightened to validate callback before use
a59d14c2by Jon Griffiths+53−1513 files
No security note in commit
Low 42 AI analysisMessage 30 · Opaque
BS BlockstreamBlockstream Jade BitcoinHardware wallets

temporary_stack: whitelist temporary task function calls

This commit adds a whitelist to a special helper that lets certain functions run with extra memory stack space. Previously, any function could be passed to this helper. Now only a small list of approved functions is allowed, except during …

Addition of function-pointer whitelistRemoval of static linkage on internal functions to enable whitelist comparisonConditional bypass of whitelist only for debug/selfcheck builds
6a0fea51by Jon Griffiths+26−54 files
No security note in commit
Informational 15 AI analysisMessage 43 · Thin
BS BlockstreamBlockstream Jade BitcoinHardware wallets

consistency: fix typos

This commit is a large typo-fixing cleanup across 40 files. Almost every change corrects spelling mistakes in code comments, variable names, or user-facing text strings. There is no change to program logic, security behavior, or cryptograp…

251f7713by Jon Griffiths+96−9640 files
No security note in commit
Informational 15 AI analysisMessage 47 · Thin
BS BlockstreamBlockstream Jade BitcoinHardware wallets

docs: document get_bip85_bip39_entropy

This commit only updates documentation and removes a single comment line. It documents an existing feature that lets a user request encrypted BIP85-based BIP39 entropy from the Jade hardware wallet after on-device confirmation. There is no…

05a578adby Jon Griffiths+52−12 files
No security note in commit
Low 28 AI analysisMessage 50 · Thin
BS BlockstreamBlockstream Jade BitcoinHardware wallets

bip85: expose get_bip85_bip39_entropy over rpc in addition to qr

This commit moves a feature that derives BIP85 BIP39 entropy from being available only in debug builds to being available over the normal RPC interface. BIP85 lets a hardware wallet derive child seed phrases from a master seed. Making this…

Feature moved from debug-only to production RPC surfaceNo accompanying access-control or input-sanitization changes visible in diffBIP85 entropy derivation is a sensitive cryptographic operation
c6c5e860by Jon Griffiths+3−41 file
No security note in commit
Informational 19 AI analysisMessage 50 · Thin
BS BlockstreamBlockstream Jade BitcoinHardware wallets

versioninfo: add JADE_INTERFACE field to show which connection source holds the unlocked wallet

This commit adds a new read-only field, JADE_INTERFACE, to the device's version information reply. It simply tells a connected computer which communication path (USB, Bluetooth, QR mode, etc.) currently has control of the unlocked wallet. …

No authentication or authorization logic changedNo cryptographic or key-management code changedNo input parsing or memory-unsafe code added
2fe9df0bby Daniel Newton+66−56 files
No security note in commit
Low 44 AI analysisMessage 60 · Adequate
BS BlockstreamBlockstream Jade BitcoinHardware wallets

sign_tx/sign_psbt: extra check for BTC inputs

This commit adds overflow protection when adding up the total value of Bitcoin transaction inputs in Blockstream Jade's signing code. Previously, the firmware used a plain addition that could silently wrap around if a specially crafted tra…

Integer overflow hardening in financial-amount accumulationDefensive checked_add_uint64() introduced where plain addition existedTransaction signing path now rejects overflowed input totals
41d7e8b4by Daniel Newton+15−32 files
No security note in commit
Informational 19 AI analysisMessage 62 · Adequate
BS BlockstreamBlockstream Jade BitcoinHardware wallets

build: move NVS cache objects that can pin the DRAM heap to SPIRAM if available

This commit changes how the Jade hardware wallet's firmware uses memory. It moves some internal storage cache objects from the main RAM (DRAM) to external RAM (PSRAM/SPIRAM) when available. This is a memory-optimization change, not a direc…

Memory layout change: moves NVS cache from DRAM to SPIRAMNo direct security fix or vulnerability patch present in diffNo mention of CVE, security researcher, or security advisory in commit
329f73c5by Daniel Newton+7−17 files
No security note in commit
Informational 15 AI analysisMessage 60 · Adequate
BS BlockstreamBlockstream Jade BitcoinHardware wallets

tests: migrate pin action tests from test_jade to rpc tests

This commit simply moves existing test cases from one test file to another. It does not change any production code, security behavior, or fix any vulnerability. The tests check that the Jade device correctly rejects invalid parameters for …

be0e6b3dby Mike Tolkachev+42−402 files
No security note in commit
Informational 15 AI analysisMessage 60 · Adequate
BS BlockstreamBlockstream Jade BitcoinHardware wallets

tests: add tests for pin actions via debug_set_pin

This commit only adds a new test file that exercises PIN-related features of the Jade hardware wallet using a debug-only RPC command. It does not change any production code, introduce new functionality, or alter security behavior. The test…

dd3d5b22by Mike Tolkachev+334−01 file
No security note in commit
Moderate 62 AI analysisMessage 50 · Thin
BS BlockstreamBlockstream Jade BitcoinHardware wallets

process: require user to permit get_identity_shared_key RPC

This commit adds a user confirmation step before a hardware wallet will share an identity-derived shared secret. Previously, the get_identity_shared_key RPC could compute and return the shared key without the user pressing approve on the d…

RPC that derives/releases a cryptographic shared secret now requires explicit on-device user approvalInput validation added: identity string must be printable before being shown in a security promptNew dedicated accept/reject button event IDs separate this flow from sign_identity
7ca0d26cby Daniel Newton+70−116 files
No security note in commit
Informational 20 AI analysisMessage 60 · Adequate
BS BlockstreamBlockstream Jade BitcoinHardware wallets

auth: add unattended pin selection for rpc tests

This commit adds a debug-only feature that lets automated tests set or change the device's PIN over an internal RPC message. It only compiles when special debug flags are enabled and is not present in normal production firmware. The change…

New RPC endpoint debug_set_pin can set/change the unlock PINPIN-handling code path modified to read from a mutable debug context instead of a fixed constantCode is wrapped in CONFIG_DEBUG_UNATTENDED_CI and CONFIG_DEBUG_MODE preprocessor guards
309ee8bbby Mike Tolkachev+100−205 files
No security note in commit
Moderate 59 AI analysisMessage 65 · Adequate
BS BlockstreamBlockstream Jade BitcoinHardware wallets

pin: disallow pin update on initialized units in debug mode

This commit removes a special debug-only exception that previously allowed the PIN server's public key to be changed on a Jade hardware wallet that already had a wallet set up. In normal operation, changing this public key on an initialize…

Removal of debug-mode bypass for a security-critical authorization checkProtection against pinserver public key substitution on initialized devicesDefense-in-depth for wallet PIN/server trust binding
a5667efdby Jon Griffiths+1−31 file
Vendor flagged security relevance
Informational 15 AI analysisMessage 95 · Strong
BS BlockstreamBlockstream Jade BitcoinHardware wallets

tests: fix mnemonic handling following seed changes

This commit only changes test code for the Blockstream Jade hardware wallet. It fixes how tests set and reset the device mnemonic/seed so tests run correctly after earlier seed-handling changes. There is no change to the actual wallet firm…

85e87d4eby Jon Griffiths+32−377 files
No security note in commit
Low 32 AI analysisMessage 35 · Opaque
BS BlockstreamBlockstream Jade BitcoinHardware wallets

malloc_ext: fix JADE_CALLOC_DRAM

This commit fixes a macro definition for a memory-allocation helper. The macro was accidentally written to take only one argument ('size') even though the underlying function it calls needs two arguments ('number of items' and 'size of eac…

Memory-allocation wrapper macro arity mismatch fixedPotential for undefined behavior if mismatched macro were usedNo explicit security claim or CVE referenced in commit
828835ccby Daniel Newton+1−11 file
No security note in commit
Low 43 AI analysisMessage 68 · Adequate
BS BlockstreamBlockstream Jade BitcoinHardware wallets

sign_psbt: fix reply count for exact chunk sizes

This commit fixes a bug in how Blockstream Jade counts the number of message chunks needed to send back a signed Bitcoin transaction (PSBT). When the transaction size was an exact multiple of the chunk size, the device told the host there …

Integer division off-by-one in chunk/message countDevice abort on assertion when host requests non-existent chunkDenial-of-service-like symptom: valid signing flow can crash the device
4f1a1565by kkdao+38−22 files
No security note in commit
Low 37 AI analysisMessage 73 · Adequate
BS BlockstreamBlockstream Jade BitcoinHardware wallets

ui: allow tapping directly on touchscreen elements

This commit adds a new touchscreen mode for some Jade hardware wallets where users can tap on-screen buttons directly instead of only using the three virtual buttons below the screen. To reduce the risk of accidental or malicious confirmat…

New direct-touch input path added to GUI event handlingCritical-action buttons require long-press to mitigate stray or coerced tap confirmationsDestructive operations (reset, delete wallet, delete OTP) converted to critical yes/no prompts
a46aa30aby Bota+206−1111 files
Vendor flagged security relevance
Informational 13 AI analysisMessage 60 · Adequate
BS BlockstreamBlockstream Jade BitcoinHardware wallets

urldecode: use plain strlen in self-tests of libjade

This commit only changes the internal test file for a URL-decoding helper. It swaps a custom string-length macro for the standard C strlen() function inside test data. The actual product code that users rely on is not changed, and there is…

b39a7a20by Mike Tolkachev+27−291 file
No security note in commit
Moderate 50 AI analysisMessage 45 · Thin
BS BlockstreamBlockstream Jade BitcoinHardware wallets

assets: support tickers up to 24 characters

This commit updates the Blockstream Jade hardware wallet to support longer asset tickers (up to 24 characters) and adds validation to reject malformed tickers. It also fixes a potential display bug where a ticker longer than 8 characters c…

Buffer size increased from 8 to 25 bytes to match new ticker maximumNew input validation added for asset ticker length and character setsnprintf precision argument cast from size_t to int to avoid undefined behavior on some platforms
cc5859a6by Mike Tolkachev+36−53 files
No security note in commit
Low 29 AI analysisMessage 45 · Thin
BS BlockstreamBlockstream Jade BitcoinHardware wallets

assets: improve empty ticker support

This commit hardens how the Blockstream Jade hardware wallet handles assets that have no ticker symbol. Previously, if an asset's ticker was missing (NULL), the code could pass a NULL pointer to string-length functions, which can cause cra…

NULL-pointer dereference risk in asset ticker handlingDefensive null-check added before strlen()New test fixture for NULL ticker asset path
9d0d74d0by Mike Tolkachev+30−23 files
No security note in commit
Repository ledger

Explore captured commits

Expand any commit for its author, full message, clarity score, changed files, triage signals, analysis, and source link.

Lower-prioritytests: add liquid descriptor to debug_selfcheck()by Daniel Newton · f1da3eba · Jun 18, 2026 · 1 fileMessage 55 · ThinInformational 15Details
Commit message · Daniel Newton

tests: add liquid descriptor to debug_selfcheck()

55/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
AI analysis · Informational 15/100

This commit only adds a new test case to the device's self-check suite. It exercises Liquid Bitcoin descriptor parsing and checks that blinding keys and script outputs are produced correctly. There is no change to production code, no bug fix, and no security-relevant behavior change.

AI review queueddescriptor: add support for liquid confidential descriptorsby Daniel Newton · 0e009e4f · Jun 18, 2026 · 9 filesMessage 73 · AdequateLow 29Details
Commit message · Daniel Newton

descriptor: add support for liquid confidential descriptors

Show any blinding key details in the descriptor details UX.

Currently supported for debug builds only unless LIQUID_DESCRIPTORS is
defined at build time.

Co-authored-by: Jon Griffiths <jon_p_griffiths@yahoo.com>

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 29/100

This commit adds support for Liquid confidential descriptors to the Blockstream Jade hardware wallet. It is a feature addition, not a fix for a known vulnerability. The code introduces new validation rules that reject non-SLIP77 blinding keys on Liquid and reject confidential descriptors on Bitcoin. It also shows the blinding key on the device screen during wallet registration and management. The feature is gated so it is only active in debug builds unless explicitly enabled at compile time.

Lower-prioritywally: update to latest master to pick up liquid descriptor supportby Daniel Newton · baeedee5 · Jun 18, 2026 · 1 fileMessage 50 · ThinInformational 5Details
Commit message · Daniel Newton

wally: update to latest master to pick up liquid descriptor support

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI analysis · Informational 5/100

This commit updates an internal dependency (libwally-core) to a newer version so that Blockstream Jade can support Liquid descriptors. No actual code changes are shown, and the commit message describes only a feature addition, not a security fix.

Lower-prioritytest: fix test_generic_multisig_matches_ga_addressesby Mike Tolkachev · bab82e2c · Jun 12, 2026 · 1 fileMessage 85 · StrongInformational 15Details
Commit message · Mike Tolkachev

test: fix test_generic_multisig_matches_ga_addresses

Restores original intent to run blinding key and commitments tests as
inner loops. Also add local wallet registration to fix the issue with
Liquid wallets overwritten by Bitcoin ones and to remove from reliance
on wallet registration tests.

85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Mentions testing or verification
AI analysis · Informational 15/100

This commit only changes a test file. It fixes how a multi-signature wallet test is structured so that wallet registration happens inside the test loop and so that blinding-key and commitment checks run for each wallet separately. There is no change to the actual Jade firmware or wallet code that users rely on.

Lower-prioritytest: add test case filtering by glob patternby Mike Tolkachev · 9c35e4b6 · Jun 12, 2026 · 1 fileMessage 90 · StrongInformational 15Details
Commit message · Mike Tolkachev

test: add test case filtering by glob pattern

A new CLI option is added allowing selective execution of test cases
filtered by glob pattern applied to JSON test fixtures in test_data/
directory.

90/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Mentions testing or verification
AI analysis · Informational 15/100

This commit only changes the project's internal test script. It adds a command-line option that lets developers run a subset of test cases by matching JSON fixture filenames with a glob pattern. There is no change to the actual Jade firmware, wallet logic, cryptography, or any code that end users run on the device.

Lower-prioritytests: add test cases for invalid asset summariesby Mike Tolkachev · 942101fb · Jun 9, 2026 · 3 filesMessage 55 · ThinInformational 12Details
Commit message · Mike Tolkachev

tests: add test cases for invalid asset summaries

55/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
AI analysis · Informational 12/100

This commit only adds three new test data files for the Blockstream Jade hardware wallet. The files are deliberately invalid Liquid Bitcoin swap transactions used to verify that the device correctly rejects bad asset summaries. No production code was changed, so this commit does not introduce or fix a security vulnerability by itself.

Security candidatewallet: fix unhandled wrong asset in wallet summariesby Mike Tolkachev · b33cf02b · Jun 9, 2026 · 3 filesMessage 77 · AdequateModerate 59Details
Commit message · Mike Tolkachev

wallet: fix unhandled wrong asset in wallet summaries

Verifies that asset_summary_update returns true, otherwise aborts
transaction or PSBT processing with error.

77/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Explains rationale or failure mode
Why it was queued
signing boundarysigning or wallet path
AI analysis · Moderate 59/100

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.

Security candidatepinserver: update to latest masterby Jon Griffiths · f51613c9 · Jun 8, 2026 · 1 fileMessage 45 · ThinInformational 24Details
Commit message · Jon Griffiths

pinserver: update to latest master

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
authentication path
AI analysis · Informational 24/100

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.

Lower-prioritypython: sync deps to pinserverby Jon Griffiths · 6f43f541 · Jun 8, 2026 · 1 fileMessage 45 · ThinLow 28Details
Commit message · Jon Griffiths

python: sync deps to pinserver

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
documentation-only discount
AI analysis · Low 28/100

This commit updates a list of Python helper libraries used by the project, mainly to keep them in line with another related project called 'pinserver'. The changes bump versions of common networking and code-style packages (pycodestyle, idna, certifi, urllib3, charset-normalizer, requests). There is no direct evidence in the commit that this fixes a specific security vulnerability, but updating dependencies—especially urllib3 and requests—often includes routine security patches. The commit message does not describe a security issue.

Lower-priorityci: disable 1.0 flashing jobsby Jon Griffiths · 1873c5a5 · May 21, 2026 · 1 fileMessage 72 · AdequateInformational 15Details
Commit message · Jon Griffiths

ci: disable 1.0 flashing jobs

These devices do not always cleanly reboot and thus the CI is
not suitable for automatation.

72/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body
AI analysis · Informational 15/100

This commit only changes internal CI (continuous integration) configuration. It comments out automated test jobs that flash firmware onto older Jade v1.0 hardware because those devices do not reliably reboot during testing. There is no change to the product firmware, no user-facing change, and no security fix or vulnerability patch.

Security candidatesign: update output logic, rename and document output flags for clarityby Mike Tolkachev · cf79a3aa · May 16, 2026 · 5 filesMessage 85 · StrongModerate 59Details
Commit message · Mike Tolkachev

sign: update output logic, rename and document output flags for clarity

Re-fixes change output marking so that it is only ever set if the
output is also marked as a wallet output. Downstream code can thus
check the change bit alone to determine wallet change.

85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode
Why it was queued
signing boundarysigning or wallet path
AI analysis · Moderate 59/100

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.

Security candidateesp-idf: update to v5.5.4, take multisig bootloader component from https://github.com/Blockstream/esp-idf/tree/securebootv2_multisig_v5.5.4by Daniel Newton · d931d543 · May 15, 2026 · 104 filesMessage 58 · ThinModerate 57Details
Commit message · Daniel Newton

esp-idf: update to v5.5.4, take multisig bootloader component from https://github.com/Blockstream/esp-idf/tree/securebootv2_multisig_v5.5.4

58/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
update trustcryptography-sensitive pathseed or entropy pathsigning or wallet pathboot or update path
AI analysis · Moderate 57/100

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.

AI review queuedbuild: update sdkconfig definitionsby Daniel Newton · 032ddce0 · May 15, 2026 · 29 filesMessage 70 · AdequateInformational 15Details
Commit message · Daniel Newton

build: update sdkconfig definitions

match esp-idf v5.5 changes:
- CONFIG_PERIPH_CTRL_FUNC_IN_IRAM is now default enabled
- CONFIG_NEWLIB_NANO_FORMAT renamed to CONFIG_LIBC_NEWLIB_NANO_FORMAT
- CONFIG_NEWLIB_STDIN_LINE_ENDING_LF renamed to
CONFIG_LIBC_STDIN_LINE_ENDING_LF
- CONFIG_NEWLIB_STDOUT_LINE_ENDING_LF renamed to
CONFIG_LIBC_STDOUT_LINE_ENDING_LF

Co-authored-by: Jon Griffiths <jon_p_griffiths@yahoo.com>

70/100 · AdequateMessage clarity
✓ Descriptive subject✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Why it was queued
second-pass: unusually broad change
AI analysis · Informational 15/100

This commit is a routine build-system update that renames several ESP-IDF configuration options to match the names used in ESP-IDF version 5.5. It does not change any actual behavior or security settings of the firmware. The old and new configuration names control the same features, so this is purely a compatibility change.

Lower-priorityserial: set UART0 pins on esp32by Daniel Newton · f2cb1e11 · May 15, 2026 · 1 fileMessage 60 · AdequateInformational 24Details
Commit message · Daniel Newton

serial: set UART0 pins on esp32

before ESP-IDF v5.5 these were set by default

60/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
AI analysis · Informational 24/100

This commit explicitly sets the physical pins used for the device's main serial (UART0) communication on ESP32 chips. In newer ESP-IDF versions (from v5.5), the default pins are no longer assigned automatically, so without this change the serial port might not work at all or might map to unexpected pins. It is a hardware-configuration fix rather than a patch for an active security vulnerability, but misconfigured serial pins could in theory cause communication failures or expose debug traffic on unintended pins.

Lower-prioritybuild: update github action to 5.5.4by Jon Griffiths · 5a4dfcac · May 15, 2026 · 1 fileMessage 57 · ThinInformational 15Details
Commit message · Jon Griffiths

build: update github action to 5.5.4

57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
documentation-only discount
AI analysis · Informational 15/100

This commit simply updates the version of the Espressif build tools used by automated GitHub test builds from v5.4 to v5.5.4. It is a routine CI/CD maintenance change with no visible security relevance.

Lower-prioritybuild: update jade_builder docker image script to latest jade_builder_baseby Daniel Newton · 543e3d64 · May 15, 2026 · 1 fileMessage 77 · AdequateInformational 15Details
Commit message · Daniel Newton

build: update jade_builder docker image script to latest jade_builder_base

Co-authored-by: Jon Griffiths <jon_p_griffiths@yahoo.com>

77/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body
AI analysis · Informational 15/100

This is a routine build-system update. It changes the Dockerfile to use a newer internal base image and a newer version of Espressif's ESP-IDF toolchain. There is no indication of a security bug, vulnerability fix, or malicious change in the commit itself.

Lower-prioritytools: esp32 move OS functions to flash from IRAM when wifi logging onby Daniel Newton · 8330ce0e · May 15, 2026 · 1 fileMessage 50 · ThinInformational 18Details
Commit message · Daniel Newton

tools: esp32 move OS functions to flash from IRAM when wifi logging on

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI analysis · Informational 18/100

This commit changes a build configuration script for the ESP32 version of Blockstream Jade. When Wi-Fi logging is enabled, the script now places some FreeRTOS operating system functions into flash memory instead of fast internal RAM (IRAM). The stated reason is to free up IRAM space so the firmware can compile. This is a build tooling change to avoid a linker memory overflow, not a fix for an exploitable security vulnerability.

Lower-prioritybuild: update jade_builder_base docker image to esp-idf v5.5.4by Daniel Newton · d4adb65d · May 15, 2026 · 1 fileMessage 62 · AdequateInformational 15Details
Commit message · Daniel Newton

build: update jade_builder_base docker image to esp-idf v5.5.4

62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
AI analysis · Informational 15/100

This commit simply updates the version of Espressif's ESP-IDF development framework used to build Jade's Docker builder image, from v5.4.3 to v5.5.4. There is no indication in the commit of any security issue, vulnerability, or functional code change.

Lower-prioritybuild: update jade_builder image referencesby Daniel Newton · 4ee1ffa2 · May 15, 2026 · 4 filesMessage 57 · ThinInformational 15Details
Commit message · Daniel Newton

build: update jade_builder image references

57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
AI analysis · Informational 15/100

This commit simply updates the version (SHA hash) of a Docker build image used by the project in four configuration/documentation files. There is no code change, no vulnerability fix, and no security-relevant behavior change visible in the diff.

Lower-priorityjadepy: update setup.py install depsby Jon Griffiths · 52ab757c · May 15, 2026 · 1 fileMessage 45 · ThinInformational 16Details
Commit message · Jon Griffiths

jadepy: update setup.py install deps

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI analysis · Informational 16/100

This commit updates two Python library version requirements in the Jade Python package's setup file. It raises the minimum required version of cbor2 (a data-serialization library) from 5.4.6 to 5.9.0, and updates the bleak Bluetooth library from 0.13.0 to 2.1.1 for the optional Bluetooth feature. The commit message gives no security reason for the change, and the diff alone does not show any vulnerability being fixed. It is most likely routine dependency maintenance, but pinning older, possibly insecure library versions can indirectly affect users if those older versions have known security flaws.

Security candidatesign_tx: suppress validation/change attribution for green 2of3 outputsby Mike Tolkachev · 0243f239 · May 15, 2026 · 1 fileMessage 85 · StrongHigh 72Details
Commit message · Mike Tolkachev

sign_tx: suppress validation/change attribution for green 2of3 outputs

Since the recovery xpub is not currently registered on-device, we should
not trust the caller provided value, and users must validate the address
on-device. A malicious companion app could otherwise swap out the
recovery xpub to grief the user.

This brings sign_tx behaviour in line with sign_psbt for Green 2of3.

A future update will allow user-confirmed registration for Green 2of3
which will allow skipping the confirmation for these outputs.

85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode
Why it was queued
signing boundarydefensive validationsigning or wallet path
AI analysis · High 72/100

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.

AI review queuedjadepy: update jadepy releaseby Jon Griffiths · cdcebe8f · May 15, 2026 · 2 filesMessage 35 · OpaqueInformational 15Details
Commit message · Jon Griffiths

jadepy: update jadepy release

35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100

This commit simply bumps the version of a Python client library (jade-client) used by the project from version 1.0.37 to 1.0.40, and updates the corresponding cryptographic signature file. There is no indication in the commit itself that this is a security fix, vulnerability, or malicious change. It is a routine dependency update.

Lower-priorityjade_cli: add required arguments to sign_txby Valerio Vaccaro · dd481eec · May 14, 2026 · 1 fileMessage 45 · ThinInformational 19Details
Commit message · Valerio Vaccaro

jade_cli: add required arguments to sign_tx

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI analysis · Informational 19/100

This commit updates the command-line tool for Blockstream Jade hardware wallets so that its 'sign transaction' command now requires additional pieces of information (the transaction inputs and any change output details) and formats its output as JSON. The change appears to be a normal feature/API update rather than a fix for a security vulnerability. There is no evidence in the commit that this was done to address a security issue.

Security candidateui: tidy up message/error activitiesby Daniel Newton · 1914ace0 · May 4, 2026 · 25 filesMessage 45 · ThinInformational 15Details
Commit message · Daniel Newton

ui: tidy up message/error activities

Fix spelling of "re-encrypt".

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
seed or entropy pathsigning or wallet pathboot or update pathauthentication path
AI analysis · Informational 15/100

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.

Lower-prioritybuild: move production config directory into the configs directoryby Daniel Newton · be7f66d2 · May 1, 2026 · 9 filesMessage 62 · AdequateInformational 15Details
Commit message · Daniel Newton

build: move production config directory into the configs directory

62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
AI analysis · Informational 15/100

This commit simply moves existing production build configuration files from one folder (production/) into a subfolder (configs/production/). The contents of the files are unchanged, and only two helper scripts are updated to point to the new location. There is no change to the actual software behavior, security settings, or user-facing functionality.