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

Security candidateprocess: whitelist reply message function callsby Jon Griffiths · a59d14c2 · Oct 22, 2026 · 13 filesMessage 45 · ThinModerate 57Details
Commit message · Jon Griffiths

process: whitelist reply message function calls

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 path
AI analysis · Moderate 57/100

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 malicious code path to craft unexpected replies. Now only a specific list of known-safe reply-building functions is accepted. The change is defensive hardening rather than a clear fix for an active attack.

Security candidateconsistency: fix typosby Jon Griffiths · 251f7713 · Oct 22, 2026 · 40 filesMessage 43 · ThinInformational 15Details
Commit message · Jon Griffiths

consistency: fix typos

Almost entirely comments; one user visible RPC error message,
"User abandonded pin entry".

43/100 · ThinMessage clarity
✓ Subject identifies a change✓ Provides an explanatory body
Why it was queued
access controlsigning or wallet pathauthentication path
AI analysis · Informational 15/100

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 cryptographic handling. The only user-visible change is correcting the error message 'User abandonded pin entry' to 'User abandoned pin entry'.

Security candidatedocs: document get_bip85_bip39_entropyby Jon Griffiths · 05a578ad · Oct 12, 2026 · 2 filesMessage 47 · ThinInformational 15Details
Commit message · Jon Griffiths

docs: document get_bip85_bip39_entropy

47/100 · ThinMessage clarity
✓ Descriptive subject✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
entropy or randomnesssecret or key material
AI analysis · Informational 15/100

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 code behavior change, no bug fix, and no security patch in the diff.

Security candidatebip85: expose get_bip85_bip39_entropy over rpc in addition to qrby Jon Griffiths · c6c5e860 · Oct 12, 2026 · 1 fileMessage 50 · ThinLow 28Details
Commit message · Jon Griffiths

bip85: expose get_bip85_bip39_entropy over rpc in addition to qr

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
entropy or randomnesssecret or key material
AI analysis · Low 28/100

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 available over RPC means wallet software can request derived seed entropy through the standard communication channel, not only via QR codes. There is no direct evidence in the commit that this fixes a security vulnerability; it appears to be a functionality or API-consistency change.

Security candidateversioninfo: add JADE_INTERFACE field to show which connection source holds the unlocked walletby Daniel Newton · 2fe9df0b · Oct 6, 2026 · 6 filesMessage 50 · ThinInformational 19Details
Commit message · Daniel Newton

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

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

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. There is no change to security rules, authentication, or how wallets are unlocked; it only exposes existing internal state for better visibility.

Security candidatesign_tx/sign_psbt: extra check for BTC inputsby Daniel Newton · 41d7e8b4 · Sep 30, 2026 · 2 filesMessage 60 · AdequateLow 44Details
Commit message · Daniel Newton

sign_tx/sign_psbt: extra check for BTC inputs

should be redundant as each amount is bounded by WALLY_SATOSHI_MAX and
inputs at MAX_TX_INPUTS

60/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
Why it was queued
signing boundarysigning or wallet path
AI analysis · Low 44/100

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 transaction pushed the running total above the maximum 64-bit integer value. The patch now uses a checked addition and rejects the transaction if the total would overflow. The commit message says the check 'should be redundant' because each individual input amount and the number of inputs are already bounded, so this is a defensive hardening change rather than a confirmed exploitable bug.

Security candidatebuild: move NVS cache objects that can pin the DRAM heap to SPIRAM if availableby Daniel Newton · 329f73c5 · Sep 30, 2026 · 7 filesMessage 62 · AdequateInformational 19Details
Commit message · Daniel Newton

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

62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
access control
AI analysis · Informational 19/100

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 direct security fix. It may help prevent out-of-memory situations, which can indirectly improve stability, but it does not patch a known vulnerability.

Security candidatetests: migrate pin action tests from test_jade to rpc testsby Mike Tolkachev · be0e6b3d · Sep 30, 2026 · 2 filesMessage 60 · AdequateInformational 15Details
Commit message · Mike Tolkachev

tests: migrate pin action tests from test_jade to rpc tests

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
access controlauthentication path
AI analysis · Informational 15/100

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 PIN-related actions, but those checks already existed before this change.

Security candidatetests: add tests for pin actions via debug_set_pinby Mike Tolkachev · dd3d5b22 · Sep 29, 2026 · 1 fileMessage 60 · AdequateInformational 15Details
Commit message · Mike Tolkachev

tests: add tests for pin actions via debug_set_pin

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
access controlauthentication path
AI analysis · Informational 15/100

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 tests verify existing PIN setup, unlock, retry-limit, and pinserver-configuration logic.

Security candidateauth: add unattended pin selection for rpc testsby Mike Tolkachev · 309ee8bb · Sep 29, 2026 · 5 filesMessage 60 · AdequateInformational 20Details
Commit message · Mike Tolkachev

auth: add unattended pin selection for rpc tests

60/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification✓ Names security-relevant behavior explicitly! No meaningful explanatory body
Why it was queued
access controlauthentication path
AI analysis · Informational 20/100

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 itself is a test helper, but it touches the sensitive PIN-entry path, so it deserves careful review to ensure it cannot accidentally end up in a shipping build.

Security candidatepin: disallow pin update on initialized units in debug modeby Jon Griffiths · a5667efd · Sep 28, 2026 · 1 fileMessage 65 · AdequateModerate 59Details
Commit message · Jon Griffiths

pin: disallow pin update on initialized units in debug mode

The caller can debug_reset to work around this at any point.

65/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
Why it was queued
access controlboot or update pathauthentication path
AI analysis · Moderate 59/100

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 initialized device is blocked to prevent an attacker from redirecting the device to a malicious PIN server and potentially unlocking or controlling the wallet. The debug exception created a security gap: if a debug-mode device (or an attacker able to trigger debug mode) was initialized, they could swap the PIN server key. The fix closes that gap by applying the same restriction regardless of debug mode. A legitimate developer who needs to change the key can still use debug_reset first.

Security candidatetests: fix mnemonic handling following seed changesby Jon Griffiths · 85e87d4e · Sep 28, 2026 · 7 filesMessage 95 · StrongInformational 15Details
Commit message · Jon Griffiths

tests: fix mnemonic handling following seed changes

- Fix calling set_mnemonic directly instead of through the caching
config wrapper
- Rename invalidatecache to reset since these tests require device reset
- Handle reset explicitly and don't use a valid mnemonic for it, to
prevent any test becoming dependent on it and avoid the overhead of
setting the unused mnemonic
- Add the missing mnemonic argument to the tests, to make the reset mnemonic
actually reset the device (as the fixture is not executed otherwise)

95/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Mentions testing or verification
Why it was queued
defensive validationauthentication path
AI analysis · Informational 15/100

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 firmware or any user-facing security behavior.

Security candidatesign_psbt: fix reply count for exact chunk sizesby kkdao · 4f1a1565 · Sep 24, 2026 · 2 filesMessage 68 · AdequateLow 43Details
Commit message · kkdao

sign_psbt: fix reply count for exact chunk sizes

When the signed PSBT length is an exact multiple of the output chunk
size, the reply advertised one message too many. The host then asked
for the extra chunk and the device aborted on an assertion. Count the
messages by rounding up instead.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
signing boundarysigning or wallet path
AI analysis · Low 43/100

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 was one extra chunk. When the host asked for that non-existent chunk, the device hit an internal assertion and aborted. The fix rounds the chunk count up correctly. A new test exercises sizes right at the chunk-size boundary.

Security candidatefmt: fix and prevent future use of unsupported format spec "zu"by Jon Griffiths · 26042182 · Sep 21, 2026 · 5 filesMessage 65 · AdequateInformational 20Details
Commit message · Jon Griffiths

fmt: fix and prevent future use of unsupported format spec "zu"

Reported-by: oroderico <oroderico@users.noreply.github.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 pathauthentication path
AI analysis · Informational 20/100

This commit fixes the use of the "%zu" printf format specifier, which is not supported by the ESP32 toolchain used in this project. The unsupported format could cause log messages and user-facing strings to display incorrect or garbage values. The commit also adds a CI check to prevent future use of "%zu". There is no direct evidence in the commit that this caused a security vulnerability such as information disclosure or memory corruption, but it is a code-quality fix that removes undefined/unsupported formatting behavior.

Security candidateotp: release md context on failure and clean temporary buffersby Mike Tolkachev · 6e2cb6b6 · Sep 18, 2026 · 1 fileMessage 30 · OpaqueLow 33Details
Commit message · Mike Tolkachev

otp: release md context on failure and clean temporary buffers

30/100 · OpaqueMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body! Contains work-in-progress language! Opaque security-relevant change
Why it was queued
authentication path
AI analysis · Low 33/100

This commit fixes cleanup in the one-time-password (OTP) code. Previously, if setting up the cryptographic hash context failed, the code could return without freeing that context, and temporary buffers holding sensitive counter/HMAC data were not always wiped. The change ensures the context is released on failure and wipes temporary buffers before returning. It is a defensive hardening fix rather than a clear exploitable vulnerability.

Security candidatesign_tx/sign_psbt: give a more useful error message for invalid output amountsby Daniel Newton · 3a31aaa4 · Sep 17, 2026 · 2 filesMessage 50 · ThinLow 32Details
Commit message · Daniel Newton

sign_tx/sign_psbt: give a more useful error message for invalid output amounts

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 improves error handling in Blockstream Jade's transaction signing code. Previously, if the total output amount of a Bitcoin transaction was too large to be valid, the device would trigger an internal assertion failure (JADE_WALLY_VERIFY). Now it returns a clear 'bad parameters' error to the user instead. This is primarily a robustness and user-experience improvement; it may also prevent a potential denial-of-service or confusing error state when signing malformed transactions.

Security candidatepinserver: retain unit private key on url changeby Mike Tolkachev · ddcd93a3 · Aug 27, 2026 · 4 filesMessage 50 · ThinLow 43Details
Commit message · Mike Tolkachev

pinserver: retain unit private key on url change

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 materialboot or update pathauthentication path
AI analysis · Low 43/100

This commit changes how Blockstream Jade handles its PIN server settings. Previously, changing the PIN server web address (URL) also wiped the device's private PIN encryption key, forcing the device to create a fresh one. The patch keeps the existing private key when only the URL changes, while still erasing it when the PIN server's public key changes. This avoids unnecessary key rotation and reduces the risk that a legitimate URL-only update silently breaks PIN security by generating a new key.

Security candidateconsistency: fix docs/comment/script typosby Jon Griffiths · 9ea7eed3 · Aug 19, 2026 · 5 filesMessage 45 · ThinInformational 15Details
Commit message · Jon Griffiths

consistency: fix docs/comment/script typos

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

This commit fixes five spelling mistakes in documentation, code comments, and a script comment. None of the changes alter program behavior or affect security.

Security candidatebuild: "fakeprod" prod-like development modeby Daniel Newton · cecedc76 · Aug 13, 2026 · 9 filesMessage 57 · ThinInformational 21Details
Commit message · Daniel Newton

build: "fakeprod" prod-like development mode

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
boot or update path
AI analysis · Informational 21/100

This commit adds an official developer-only 'fakeprod' build mode for Blockstream Jade hardware wallets. It deliberately weakens several security settings (single signature, committed private keys, readable flash-encryption key, enabled JTAG and ROM download mode) so developers can easily flash and debug a production-like firmware. The commit and its documentation explicitly warn that this mode is NOT secure and must never be used on a real wallet. It is a development/testing feature, not a vulnerability in production firmware.

Security candidatepsbt: check output amount presence before readingby Jon Griffiths · 9f2b916d · Aug 9, 2026 · 1 fileMessage 45 · ThinLow 46Details
Commit message · Jon Griffiths

psbt: check output amount presence before reading

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing boundarysigning or wallet path
AI analysis · Low 46/100

This commit tightens how Blockstream Jade reads output amounts from a Partially Signed Bitcoin Transaction (PSBT). Before, the code tried to read the amount directly without first confirming it was actually present. Now it checks whether the amount exists before reading it. This is a defensive hardening change that could prevent incorrect handling of missing or malformed PSBT output data during transaction signing.

Security candidatepsbt: require that all psbt bytes are consumed when parsingby Jon Griffiths · 605d86ac · Aug 9, 2026 · 1 fileMessage 50 · ThinModerate 59Details
Commit message · Jon Griffiths

psbt: require that all psbt bytes are consumed when parsing

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 · Moderate 59/100

This commit tightens how Blockstream Jade verifies a Bitcoin transaction file (PSBT) before signing. It now requires that every byte in the file is part of the transaction, with no leftover or trailing data allowed. Previously, extra bytes at the end could have been ignored, which might let a malicious or malformed PSBT hide unexpected content or influence how the device interprets what it is signing.

Security candidatetests: migrate low level testsby Valerio Vaccaro · 767006a0 · Jul 24, 2026 · 4 filesMessage 55 · ThinInformational 15Details
Commit message · Valerio Vaccaro

tests: migrate low level tests

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

This commit only moves and reorganizes existing test code. It adds a new helper to check whether the current transport is a specific type, moves a shared wait() function into a common test package file, and migrates a large set of low-level RPC tests into a new file. There are no changes to the actual Jade firmware, wallet logic, or production code, so this cannot introduce a security vulnerability in the shipped product.

Security candidatemnemonic: restore recovery phrase by word numberby roderico · 99927491 · Jul 18, 2026 · 3 filesMessage 68 · AdequateLow 27Details
Commit message · roderico

mnemonic: restore recovery phrase by word number

Allow advanced 12- and 24-word recovery to use one-based BIP39 word numbers. Resolve and confirm every word, retain the existing final-word calculation flow, and validate the complete recovery phrase before deriving keys. Clear sensitive entry state and displayed words when the flow exits.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
secret or key materialdefensive validation
AI analysis · Low 27/100

This commit adds a new way to restore a Bitcoin wallet on a Blockstream Jade hardware device: instead of typing each recovery word, users can enter each word's one-based BIP39 number (for example, '1' for 'abandon'). The change also refactors the existing word-entry code and adds cleanup of sensitive on-screen state when the user exits. There is no direct evidence in the commit that this fixes an active security vulnerability, but it touches sensitive seed-recovery code and changes how user input is validated and cleared.

Security candidateui: support bounded variable-length digit entryby roderico · 69627745 · Jul 18, 2026 · 2 filesMessage 68 · AdequateInformational 18Details
Commit message · roderico

ui: support bounded variable-length digit entry

Allow digit-entry callers to select a shorter field width and an optional maximum value while preserving the existing six-digit PIN and index defaults. Skip unavailable candidate digits during navigation and keep short-number entry semantics unchanged.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
access control
AI analysis · Informational 18/100

This commit refactors the on-screen digit-entry keypad in Blockstream Jade so callers can ask for shorter number fields (for example 4 digits instead of 6) and optionally cap the entered value. The existing 6-digit PIN and index entry behavior is kept unchanged. There is no direct evidence in the commit that this fixes an active security bug; it reads as a feature/generalization to support new UI flows such as entering BIP39 word numbers.

Security candidatetests: remove pin files for new tests, remove nolegacy from old testsby Jon Griffiths · 92380f9e · Jul 18, 2026 · 7 filesMessage 75 · AdequateInformational 15Details
Commit message · Jon Griffiths

tests: remove pin files for new tests, remove nolegacy from old tests

Note that for non-legacy testing we now only need to run the tx signing
tests that it affects.

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 boundaryaccess controlauthentication path
AI analysis · Informational 15/100

This commit is purely a testing infrastructure cleanup. It removes leftover command-line options and test files related to an older transaction-signing workflow, and makes sure temporary PIN files created during automated tests are cleaned up. There is no change to the actual Jade wallet firmware or its security behavior.