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 36 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-priorityci: disable ble ota delta testing, add v2 and local testing supportby Jon Griffiths · a67e5f17 · Feb 2, 2026 · 2 filesMessage 72 · AdequateInformational 15Details
Commit message · Jon Griffiths

ci: disable ble ota delta testing, add v2 and local testing support

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

This commit only changes internal continuous-integration (CI) scripts that run automated hardware-in-the-loop tests for Blockstream Jade firmware updates. It disables Bluetooth OTA delta testing when the required Bluetooth tool is missing, adds support for the newer Jade v2 hardware, and lets developers run the same scripts locally. There is no change to the firmware, wallet logic, cryptography, or any code that end users run, so this commit does not create or fix a security vulnerability.

Lower-priorityci: disable bluetooth testing (consistently flaky)by Jon Griffiths · c51e0298 · Feb 2, 2026 · 3 filesMessage 72 · AdequateInformational 15Details
Commit message · Jon Griffiths

ci: disable bluetooth testing (consistently flaky)

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

This commit only changes internal continuous-integration (CI) scripts. It disables flaky Bluetooth tests by passing a --skipble flag and makes minor shell-script cleanups. There is no change to the actual Jade firmware, wallet application, or any code that end users run.

Lower-priorityci: disable file locking for ci flashingby Jon Griffiths · 0ca176a0 · Feb 2, 2026 · 1 fileMessage 57 · ThinInformational 15Details
Commit message · Jon Griffiths

ci: disable file locking for ci flashing

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 changes internal CI (Continuous Integration) scripts used to flash firmware onto test devices during automated builds. It temporarily removes a file-locking wrapper around flashing commands because GitLab was not reliably killing background processes. There is no change to the actual Jade firmware, wallet code, or anything end users install. It is purely a build/test infrastructure adjustment.

Lower-priorityci: increase the time allowance for selfcheckby Jon Griffiths · cc7907b2 · Feb 2, 2026 · 1 fileMessage 57 · ThinInformational 15Details
Commit message · Jon Griffiths

ci: increase the time allowance for selfcheck

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 raises the time limit allowed for a hardware self-test in a test script. It is a routine CI/testing adjustment with no security relevance.

Security candidatetests: add green 2of3 recovery signing by recovery key (full path from master key)by Mihailo Milenkovic · 6779fc7a · Feb 2, 2026 · 2 filesMessage 75 · AdequateInformational 5Details
Commit message · Mihailo Milenkovic

tests: add green 2of3 recovery signing by recovery key (full path from master key)

Test case for the situation described in the previous commit, showing
that the transaction is correctly signed.

75/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Mentions testing or verification
Why it was queued
signing boundarysigning or wallet path
AI analysis · Informational 5/100

This commit only adds a new test case and updates a description of an existing test. It does not change any production code. The new test documents that when a recovery key is provided with a full derivation path (from the master key), a Blockstream Jade device will still sign the transaction, but a helper function called is_green_multisig_signers() will return false, meaning some extra Green 2of3 validation is skipped. Because no actual signing logic is changed, this commit by itself is not a security fix or vulnerability.

Security candidatesign_psbt: add 2of3 recovery path comment for is_green_multisig_signersby Mihailo Milenkovic · 34f3d162 · Feb 2, 2026 · 1 fileMessage 50 · ThinInformational 15Details
Commit message · Mihailo Milenkovic

sign_psbt: add 2of3 recovery path comment for is_green_multisig_signers

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing boundarysigning or wallet path
AI analysis · Informational 15/100

This commit only adds a code comment explaining an existing limitation in how Blockstream Jade detects Green multisignature transactions. No code behavior changes. The comment documents that for a specific 2-of-3 recovery wallet setup, the device may skip extra Green-specific validation and fall back to treating the transaction as a standard 2-of-3 multisig, but signing still works correctly.

Lower-priorityci: update flashing ci runnersby Jon Griffiths · 34a069cb · Feb 2, 2026 · 1 fileMessage 57 · ThinInformational 15Details
Commit message · Jon Griffiths

ci: update flashing ci runners

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 only renames the labels used to pick which GitLab CI runner executes firmware flashing jobs. It does not change any code that runs on the Jade device, nor any build logic, secrets, or network behavior. There is no security relevance visible in the change.

Lower-prioritytools: remove obsolete jade v1 flashing codeby Daniel Newton · 755c1b44 · Feb 2, 2026 · 6 filesMessage 45 · ThinInformational 15Details
Commit message · Daniel Newton

tools: remove obsolete jade v1 flashing code

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

This commit simply deletes old helper scripts and instructions used to flash early 'Jade v1' hardware devices. No code that runs on the Jade wallet itself is changed, and nothing in the commit fixes or introduces a security vulnerability. It is a cleanup of obsolete tooling.

Lower-priorityci: disable cbor logging for ci firmware buildsby Jon Griffiths · 94e22c19 · Feb 2, 2026 · 1 fileMessage 100 · StrongInformational 15Details
Commit message · Jon Griffiths

ci: disable cbor logging for ci firmware builds

CBOR logging seems to cause (many) more problems than it solves. Given
we don't enable it on any device that we ship to users, avoid enabling
it in order to make the tested images closer to the actually deployed
ones.

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

This change only affects how test firmware is built in the project's continuous integration (CI) pipeline. It removes a debug logging flag so that test builds more closely match the firmware actually shipped to users. There is no user-facing code change and no security fix or vulnerability patch.

Lower-prioritylibjade: compile out debug logging under CONFIG_LOG_DEFAULT_LEVEL_NONEby Jon Griffiths · a374888d · Feb 2, 2026 · 2 filesMessage 50 · ThinInformational 19Details
Commit message · Jon Griffiths

libjade: compile out debug logging under CONFIG_LOG_DEFAULT_LEVEL_NONE

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

This commit changes how debug logging is handled in a library version of Blockstream Jade (libjade). When a build option that disables logging is set, the code now completely removes the internal log-level variable and the function that adjusts it, rather than just setting them to 'no logging.' This is a hardening/cleanup change that reduces the chance that sensitive debug information could accidentally leak in builds meant to be silent, but it does not by itself fix any active vulnerability.

Lower-priorityjadepy: return empty bytes if asked to read 0 bytesby Jon Griffiths · 318db989 · Feb 2, 2026 · 1 fileMessage 65 · AdequateInformational 15Details
Commit message · Jon Griffiths

jadepy: return empty bytes if asked to read 0 bytes

The CBOR parser appears to ask for 0 bytes when parsing on occasion.

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

This is a small bug-fix in the Python library that talks to Blockstream Jade hardware wallets. When the code was asked to read zero bytes, it previously passed that request straight to the underlying transport, which could misbehave or return unexpected results. The fix makes it return an empty response immediately instead. It is a robustness improvement rather than a clear security vulnerability.

Security candidateattestation: misc cleanupsby Jon Griffiths · 4d782bf8 · Feb 2, 2026 · 1 fileMessage 75 · AdequateLow 42Details
Commit message · Jon Griffiths

attestation: misc cleanups

- fix SENSITIVE_POP in attestation_initialise()
- fix attestation_can_be_initialised() with CONFIG_DEBUG_MODE
- avoid uneeded reloads of attestation data
- ensure keys are always initialized before being freed
- allocate attestation data on the heap to avoid stack overflow

Co-authored-by: Daniel Newton <dnewton@blockstream.com>

75/100 · AdequateMessage clarity
✓ Descriptive subject✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Names security-relevant behavior explicitly
Why it was queued
update trustmemory safetyboot or update path
AI analysis · Low 42/100

This commit is a cleanup of the device attestation code in Blockstream Jade, which is the cryptographic proof that the device is genuine. The changes fix a memory-management bug where sensitive key data could be cleared in the wrong order, correct a logic issue when debug mode is enabled, avoid repeatedly reloading attestation data from storage, ensure cryptographic keys are initialized before being freed, and move a large attestation data structure from the stack to the heap to prevent a possible stack overflow. Most changes are defensive hardening, but the SENSITIVE_POP ordering and the debug-mode logic fix are genuine security-relevant corrections.

Security candidatetests: add test for a green 2of3 psbt with jade as the recovery key signerby Mihailo Milenkovic · 2d9c0a4c · Feb 2, 2026 · 1 fileMessage 60 · AdequateInformational 15Details
Commit message · Mihailo Milenkovic

tests: add test for a green 2of3 psbt with jade as the recovery key signer

60/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
signing boundarysigning or wallet path
AI analysis · Informational 15/100

This commit only adds a new test data file containing a sample Bitcoin transaction (PSBT) for a multi-signature wallet scenario. It does not change any actual wallet code, cryptography, or security logic. There is no indication of a vulnerability or security fix.

Lower-priorityusb: add descriptor export for unlocked devicesby Austin-Fulbright · 22fe675a · Feb 2, 2026 · 6 filesMessage 60 · AdequateInformational 24Details
Commit message · Austin-Fulbright

usb: add descriptor export for unlocked devices

Does not currently support Liquid or Green multisig.

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

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

This commit adds a new feature to Blockstream Jade hardware wallets that lets the user export an extended public key (xpub) as a file to a connected USB storage device. The feature only works when the device is unlocked and explicitly disallows multisig exports. It is a normal product feature, not a fix for a known security bug. There is no evidence in the commit or supplied references that this is a security patch or that it addresses any disclosed vulnerability.

Security candidateattestation: add status, battery charging/volts to 'get_version_info' RPCby Daniel Newton · cc3fb705 · Feb 2, 2026 · 5 filesMessage 50 · ThinInformational 13Details
Commit message · Daniel Newton

attestation: add status, battery charging/volts to 'get_version_info' RPC

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
update trustboot or update path
AI analysis · Informational 13/100

This commit simply adds more information to an existing device status report (the 'get_version_info' RPC). It now reports whether tamper-evident attestation is active, the battery voltage, and whether the battery is charging. There is no change to security logic, access control, or cryptography. It is a routine telemetry/informational enhancement.

Security candidatewallet: allow skipping leading 'm' when converting bip32 pathsby Jon Griffiths · d64ade24 · Feb 2, 2026 · 9 filesMessage 50 · ThinInformational 18Details
Commit message · Jon Griffiths

wallet: allow skipping leading 'm' when converting bip32 paths

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
secret or key materialsigning or wallet path
AI analysis · Informational 18/100

This commit changes a helper function that turns numeric Bitcoin key paths (like 0/1/2) into human-readable text. It adds an option to leave off the leading 'm/' so callers that only want the raw path can get it. All existing callers are updated to keep the old behavior (with the 'm/'), so there is no immediate change in behavior. It appears to be a code cleanup or preparation for a future feature rather than a fix for an active security problem.

Security candidatepin: erase the pin privatekey when changing/erasing pin settingsby Jon Griffiths · ee6ea9a5 · Feb 2, 2026 · 2 filesMessage 70 · AdequateLow 42Details
Commit message · Jon Griffiths

pin: erase the pin privatekey when changing/erasing pin settings

Ensures we use a new private key whenever the pinserver is changed,
created on demand at first-use.

70/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Names security-relevant behavior explicitly
Why it was queued
secret or key materialaccess control
AI analysis · Low 42/100

This commit changes how Blockstream Jade handles a private key used for PIN server authentication. Previously, the device kept the same private key even when the user changed or removed their PIN server settings. Now it deletes that key whenever the PIN server settings change, so a fresh key is generated the next time it is needed. This reduces the risk that an old or compromised key could be reused across different PIN server configurations.

Security candidatepsbt: rename key_index to found_index in key_iter_next for better code readingby Mihailo Milenkovic · 6e3ac474 · Feb 2, 2026 · 1 fileMessage 50 · ThinInformational 15Details
Commit message · Mihailo Milenkovic

psbt: rename key_index to found_index in key_iter_next for better code reading

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing boundarysigning or wallet path
AI analysis · Informational 15/100

This commit is a pure variable rename inside a single function. The local variable `key_index` is renamed to `found_index` to make the code easier to read. No logic, behavior, or security properties change.

AI review queuedutils: add util.c and functions is_potential_green_*_path()by Mihailo Milenkovic · e42b5c26 · Feb 2, 2026 · 4 filesMessage 65 · AdequateInformational 12Details
Commit message · Mihailo Milenkovic

utils: add util.c and functions is_potential_green_*_path()

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

65/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 12/100

This commit adds a new utility file with helper functions that validate whether a Bitcoin key derivation path looks like one used by Blockstream Green wallets. There is no evidence in the commit that this fixes a security bug; it appears to be a new helper for recognizing Green wallet paths.

Security candidatepsbt: remove branching for getting public/private key function callby Mihailo Milenkovic · 3be9c485 · Feb 2, 2026 · 1 fileMessage 55 · ThinInformational 12Details
Commit message · Mihailo Milenkovic

psbt: remove branching for getting public/private key function call

55/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Names security-relevant behavior explicitly! No meaningful explanatory body
Why it was queued
secret or key materialsigning boundarysigning or wallet path
AI analysis · Informational 12/100

This commit is a small internal code cleanup in a Bitcoin hardware wallet library. It replaces an if/else branch that chose between two similar key-lookup functions with a single function pointer. There is no change to what data is read, what keys are used, or what is returned to the caller. It is a stylistic refactor, not a security fix.

Security candidatesign_psbt: update is_green_multisig_signers to handle green 2of3 recovery signingby Mihailo Milenkovic · 39f02f88 · Feb 2, 2026 · 1 fileMessage 50 · ThinLow 42Details
Commit message · Mihailo Milenkovic

sign_psbt: update is_green_multisig_signers to handle green 2of3 recovery signing

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing boundarysigning or wallet path
AI analysis · Low 42/100

This commit updates the code that signs Bitcoin transactions for Blockstream Jade's Green multisig wallets. It specifically adds support for '2-of-3 recovery signing,' where the Jade device acts as the recovery key rather than the regular user key. The change lets Jade recognize and sign recovery transactions it previously would have rejected. There is no clear security bug being fixed; it appears to be a feature addition to support a missing signing scenario.

Security candidatepsbt: allow signing green 2of3 txs with Jade as the recovery signerby Mihailo Milenkovic · 6cf2694a · Feb 2, 2026 · 2 filesMessage 50 · ThinLow 32Details
Commit message · Mihailo Milenkovic

psbt: allow signing green 2of3 txs with Jade as the recovery signer

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing boundarysigning or wallet path
AI analysis · Low 32/100

This commit changes how Blockstream Jade hardware wallets sign Bitcoin transactions in a specific multi-signature setup called Green 2of3. It lets Jade act as the 'recovery signer' by deriving a special recovery key from the user's key when the first key in the transaction looks like a Blockstream Green server key. The change is a feature addition to support a previously unsupported signing scenario, not a fix for a known exploit. There is no evidence in the commit or supplied references that this is a security patch or that it addresses a disclosed vulnerability.

Security candidatebuild: add support for jade core/v2.0cby Daniel Newton · 6e788ed0 · Feb 2, 2026 · 30 filesMessage 57 · ThinInformational 15Details
Commit message · Daniel Newton

build: add support for jade core/v2.0c

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
signing or wallet pathboot or update path
AI analysis · Informational 15/100

This commit adds support for a new hardware variant called Jade Core (jade_v2c), which is a Jade Plus device without a camera or battery. The changes are purely build, configuration, release-script, and documentation updates to recognize the new board type. There is no indication of any security vulnerability being fixed or introduced.

Security candidatepin: create the pin private key on demandby Jon Griffiths · 46e09b14 · Feb 2, 2026 · 4 filesMessage 50 · ThinLow 35Details
Commit message · Jon Griffiths

pin: create the pin private key on demand

50/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Names security-relevant behavior explicitly! No meaningful explanatory body
Why it was queued
secret or key materialaccess controlauthentication path
AI analysis · Low 35/100

This commit moves when a special device private key (used for PIN server authentication) is created. Previously it was generated at every boot if missing; now it is created only when actually needed during a PIN operation. This is a code-quality and reliability change that reduces unnecessary key creation at startup, but it does not appear to fix an active security vulnerability.

Lower-prioritywally: update to latest wally masterby Jon Griffiths · 8e1e2a07 · Feb 2, 2026 · 1 fileMessage 45 · ThinInformational 0Details
Commit message · Jon Griffiths

wally: update to latest wally master

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

This commit updates a bundled cryptographic library (libwally-core) to its latest master version. No actual code diff was provided—only a one-line submodule pointer change is described—so there is no visible evidence of any security bug, fix, or behavior change. It appears to be a routine dependency refresh.