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 17 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-prioritydocs: update sign_tx docs to include genesis_hashby Jon Griffiths · b937de6f · Jun 29, 2026 · 1 fileMessage 72 · AdequateInformational 15Details
Commit message · Jon Griffiths

docs: update sign_tx docs to include genesis_hash

Also remove trailing spaces for consistency.

72/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body
Why it was queued
documentation-only discount
AI analysis · Informational 15/100

This commit only updates documentation. It adds a description of an optional 'genesis_hash' parameter for Liquid transaction signing and removes trailing whitespace. There are no code changes, so it cannot directly introduce or fix a security vulnerability.

Security candidateLiquid (taproot): add sign_liquid_tx genesis blockhash supportby Jon Griffiths · 888eff30 · Jun 29, 2026 · 4 filesMessage 95 · StrongLow 42Details
Commit message · Jon Griffiths

Liquid (taproot): add sign_liquid_tx genesis blockhash support

Allow providing the genesis blockhash for sign_liquid_tx in
addition to the already existing sign_psbt support for PSET.

For test networks, do not require that the provided genesis blockhash
matches the network genesis blockhash. This allows signing for e.g.
custom regtest environments. Ensure that test network signing cannot
use the mainnet genesis blockhash in order to prevent spoofing.

Suggested-by: topologoanatom <survisysy@gmail.com>

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
signing boundarysigning or wallet path
AI analysis · Low 42/100

This commit changes how Blockstream Jade handles the 'genesis blockhash' when signing Liquid transactions. Previously, the device only accepted the network's built-in genesis hash. Now it lets users provide a custom genesis hash for test networks (like regtest), but blocks attempts to use the real Liquid mainnet genesis hash on test networks to prevent spoofing. The change also applies the same validation to both PSBT/PSET signing and raw transaction signing. It appears to be a hardening/feature addition rather than a fix for an active exploit, but it does close a spoofing path on test networks.

Lower-priorityqemu: increase interrupt watchdog timeout on qemu to account for non realtime behavior due to CPU emulationby Daniel Newton · 65eb36c5 · Jun 25, 2026 · 2 filesMessage 62 · AdequateTriage 0Details
Commit message · Daniel Newton

qemu: increase interrupt watchdog timeout on qemu to account for non realtime behavior due to CPU emulation

62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Explains rationale or failure mode! No meaningful explanatory body
Lower-priorityci: run only one qemu job per physical boxby Jon Griffiths · 18fdfd07 · Jun 25, 2026 · 1 fileMessage 57 · ThinInformational 15Details
Commit message · Jon Griffiths

ci: run only one qemu job per physical box

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 a CI/CD configuration file so that QEMU-based test jobs run on a dedicated GitLab runner tag (ga-qemu) instead of a shared one (ga). The stated purpose is to limit QEMU jobs to one per physical CI box, likely to avoid resource contention or hardware conflicts during automated testing. There is no change to the Blockstream Jade firmware, wallet logic, cryptography, or any code that end users run.

Security candidaterpc: rename get_boolean to get_boolby Jon Griffiths · f6e946ac · Jun 25, 2026 · 18 filesMessage 45 · ThinInformational 15Details
Commit message · Jon Griffiths

rpc: rename get_boolean to get_bool

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

This commit is a simple rename of two internal helper functions from `rpc_get_boolean`/`rpc_get_boolean_or` to `rpc_get_bool`/`rpc_get_bool_or`, updating all call sites accordingly. There is no change to what the code does, no bug fix, and no security relevance.

AI review queuedrpc: rename get_uint64_t to get_uint64by Jon Griffiths · 8e0de45e · Jun 25, 2026 · 7 filesMessage 45 · ThinInformational 15Details
Commit message · Jon Griffiths

rpc: rename get_uint64_t to get_uint64

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit simply renames an internal helper function from `rpc_get_uint64_t` to `rpc_get_uint64` and updates every place that calls it. There are no changes to what the function does, how it checks data, or how secure it is. It is a routine code cleanup with no security relevance.

AI review queuedrpc: annotate functions returning error codes to ensure they are checkedby Mike Tolkachev · 517075ba · Jun 25, 2026 · 5 filesMessage 62 · AdequateLow 48Details
Commit message · Mike Tolkachev

rpc: annotate functions returning error codes to ensure they are checked

62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Explains rationale or failure mode! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 48/100

This commit adds compiler annotations (WARN_UNUSED_RESULT) to functions that return success/failure codes, so the compiler will warn if a caller ignores the result. It also fixes a few places where return values were being ignored, replacing them with safer default-value helpers. The changes reduce the chance that a malformed or missing RPC parameter silently causes wrong behavior, such as using an empty wallet path or a false success flag. This is a defensive hardening patch rather than a confirmed exploit fix.

Lower-priorityrpc: add alternative typed getters with default valuesby Mike Tolkachev · 23993a22 · Jun 25, 2026 · 2 filesMessage 50 · ThinInformational 15Details
Commit message · Mike Tolkachev

rpc: add alternative typed getters with default values

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

This commit adds convenience functions that read settings from CBOR messages and return a default value if the setting is missing or invalid. It is a straightforward feature addition with no visible security bug.

AI review queuedassets: improve precision checkingby Mike Tolkachev · fd0f625d · Jun 25, 2026 · 3 filesMessage 35 · OpaqueModerate 59Details
Commit message · Mike Tolkachev

assets: improve precision checking

35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: opaque commit messagesecond-pass: security-sensitive path
AI analysis · Moderate 59/100

This commit tightens how Blockstream Jade handles the 'precision' value in asset contracts for Liquid assets. Previously, a very large precision value could be accepted and later used to read past the end of an internal lookup table (POW_10), which could cause a crash or undefined behavior when displaying or signing a transaction. The patch caps precision at 8 and adds a compile-time check that the lookup table is sized correctly for that cap.

Security candidaterpc: refactor app code to use getters with default valuesby Mike Tolkachev · b6a07147 · Jun 25, 2026 · 8 filesMessage 50 · ThinInformational 15Details
Commit message · Mike Tolkachev

rpc: refactor app code to use getters with default values

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

This commit is a straightforward code cleanup that replaces verbose 'read this optional value, or leave the default' patterns with shorter helper functions that do the same thing. There is no change in behavior and no security issue visible in the diff.

Lower-priorityconfigs: enable overall stack smashing protection for production devicesby Mike Tolkachev · 0d8422da · Jun 25, 2026 · 3 filesMessage 50 · ThinLow 46Details
Commit message · Mike Tolkachev

configs: enable overall stack smashing protection for production devices

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

This commit strengthens a security guardrail on Blockstream Jade hardware wallets by turning on the most thorough stack-smashing protection for production builds. Stack smashing is a common way attackers try to take control of a device by overflowing a memory region; enabling 'ALL' mode tells the compiler to insert checks on every function, rather than only risky-looking ones, making exploitation harder. It is a defensive hardening change, not a fix for a known active bug.

Lower-prioritygui/camera: stop the gui task from possibly trying to render an image from a camera task stack that no longer existsby Daniel Newton · c51f7fb9 · Jun 23, 2026 · 3 filesMessage 65 · AdequateModerate 59Details
Commit message · Daniel Newton

gui/camera: stop the gui task from possibly trying to render an image from
a camera task stack that no longer exists

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

This commit fixes a race condition in the Blockstream Jade hardware wallet's camera and screen rendering code. When the camera task finished, its stack memory could be freed while the GUI task was still trying to draw the last camera image, potentially causing a crash or corrupted display. The fix adds a new function that safely clears the picture reference under a lock before the camera task's memory is released.

AI review queueddocker: update jade_builderby Jon Griffiths · 00e7a397 · Jun 23, 2026 · 4 filesMessage 35 · OpaqueInformational 15Details
Commit message · Jon Griffiths

docker: update jade_builder

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 updates the SHA256 digest of the 'blockstream/jade_builder' Docker image used for building and testing Jade in four configuration files. There is no code change, no disclosed security fix, and no evidence in the commit or supplied references that this update addresses a vulnerability.

Security candidatelibjade: add camera/input/nvs support, refactorby Daniel Newton · f7184945 · Jun 23, 2026 · 32 filesMessage 78 · AdequateLow 40Details
Commit message · Daniel Newton

libjade: add camera/input/nvs support, refactor

Use libjade-specific rpc calls to handle gui/input/nvs and camera
support. Update the gui example to allow exercising nvs/camera
functionality and optionally running libjade in daemon mode (i.e.
out-of-process).

Add a python console to the gui example to allow programmatic
control of the running jade instance for testing.

Remove config for building without gui support; gui code is now always
built-in regardless of whether a client chooses to fetch the screen
contents for display or not.

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

78/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
authentication path
AI analysis · Low 40/100

This commit is a large feature/refactor patch for Blockstream Jade's libjade (a desktop emulator of the Jade hardware wallet). It adds RPC endpoints that let a host application read the emulated device's screen, push fake button presses, read/write all emulated flash storage (NVS), and feed camera frames. The README explicitly warns that these RPCs mean 'a libjade instance is NOT SECURE FROM EXTERNAL APPLICATIONS, and that SECRET DATA CAN BE READ FROM THE RUNNING FIRMWARE.' The change is intended for development/testing only, but it removes the option to build without GUI support and makes the GUI code always compiled in. The security relevance is therefore primarily about increased attack surface and accidental misuse of a testing tool, rather than a vulnerability in production hardware wallets.

Lower-priorityjadepy: add builtin file method impls for newer cbor2 versionsby Jon Griffiths · 9857bed9 · Jun 23, 2026 · 1 fileMessage 50 · ThinLow 26Details
Commit message · Jon Griffiths

jadepy: add builtin file method impls for newer cbor2 versions

Thanks to @1-21gigasats for reporting.

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

This commit adds three simple file-like method declarations (readable, writable, seekable) to a Python class that communicates with a Blockstream Jade hardware wallet. The change appears to be a compatibility fix so the Jade interface object works correctly with newer versions of the cbor2 library, which may now expect these methods to exist. There is no obvious security vulnerability in the diff itself; it is a small API compatibility patch.

Security candidateFix M5StickC Plus 2 PIN navigationby roderico · 9de1409e · Jun 23, 2026 · 1 fileMessage 45 · ThinInformational 15Details
Commit message · roderico

Fix M5StickC Plus 2 PIN navigation

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

This commit fixes a user-interface navigation quirk on the M5StickC Plus 2 hardware for Blockstream Jade. When entering a PIN, the up/down button directions were not inverted to match the rest of the device's menus, making number entry confusing or inconsistent. There is no security vulnerability here—just a UI consistency bug.

Lower-priorityjadepy: support new/old versions of cbor2by Jon Griffiths · 91cc2edb · Jun 23, 2026 · 1 fileMessage 68 · AdequateInformational 20Details
Commit message · Jon Griffiths

jadepy: support new/old versions of cbor2

Based on a change from @1-21gigasats.

cbor2 b0rkage seems assured while it transitions its underlying
implementation. Supply a workaround for library interface changes,
as distateful as requiring it is.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
AI analysis · Informational 20/100

This is a small compatibility fix for the Python Jade library so it works with both older and newer versions of the cbor2 serialization library. Newer cbor2 changed which exception it raises when data runs out, so the code now detects the available exception type and catches the right one. It is a robustness improvement rather than a fix for an active security vulnerability.

Lower-prioritydeps: update cbor2 to 6.1.2by Jon Griffiths · 2c602b52 · Jun 23, 2026 · 1 fileMessage 45 · ThinInformational 15Details
Commit message · Jon Griffiths

deps: update cbor2 to 6.1.2

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 · Informational 15/100

This commit simply updates the version of a Python library called cbor2 from 5.9.0 to 6.1.2 in the project's dependency list. There is no information in the commit itself saying this fixes a security problem. It is a routine dependency bump with no visible security relevance based on the provided materials.

Lower-prioritylibjade: use existing frame buffer rectangle drawingby Jon Griffiths · ff0789f0 · Jun 23, 2026 · 3 filesMessage 50 · ThinInformational 12Details
Commit message · Jon Griffiths

libjade: use existing frame buffer rectangle drawing

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

This commit removes a custom bitmap-drawing function used only in the libjade build and makes that build use the same drawing path as other configurations. It is a code cleanup with no visible security relevance.

Lower-prioritywire: explicitly set nonblocking default to falseby Jon Griffiths · 3d28dccb · Jun 23, 2026 · 1 fileMessage 45 · ThinLow 35Details
Commit message · Jon Griffiths

wire: explicitly set nonblocking default to false

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

This commit fixes a small but real bug in Blockstream Jade's USB/serial message handling. A variable that decides whether a version-info message should get an immediate reply was not given a safe starting value. In C, that means it could accidentally contain leftover garbage data, causing the device to reply immediately when it shouldn't. The fix simply sets that variable to 'false' by default. This is a defensive hardening change; there is no public evidence it has been exploited.

Lower-prioritytools: don't attempt to overwrite kconfig if checking failsby Jon Griffiths · 3dd9c4db · Jun 23, 2026 · 1 fileMessage 50 · ThinInformational 17Details
Commit message · Jon Griffiths

tools: don't attempt to overwrite kconfig if checking fails

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

This is a small fix to a developer helper script (format.sh) used during code formatting. It prevents the script from trying to move a temporary file into place when a configuration-file check fails or never creates that temporary file. The change is about avoiding a build-tool error, not about stopping an attacker or protecting user funds.

Lower-prioritybuild: add build support for enforcing return codes are checkedby Mike Tolkachev · bb2e53d6 · Jun 23, 2026 · 3 filesMessage 62 · AdequateLow 26Details
Commit message · Mike Tolkachev

build: add build support for enforcing return codes are checked

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 · Low 26/100

This commit adds compiler flags and helper macros to make the build fail whenever a function's return value is ignored without explicit intent. It is a hardening change, not a fix for a specific known bug. By enforcing that programmers check or deliberately discard return values, it reduces the chance that silent failures (for example, a failed security check or memory operation) slip into future code. There is no direct evidence in the commit that an existing vulnerability is being patched.

Security candidatebuild: annotate functions returning error codes to ensure they are checkedby Mike Tolkachev · 909a89aa · Jun 23, 2026 · 25 filesMessage 74 · AdequateLow 36Details
Commit message · Mike Tolkachev

build: annotate functions returning error codes to ensure they are checked

74/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Explains rationale or failure mode! No meaningful explanatory body
Why it was queued
cryptography-sensitive pathsigning or wallet pathboot or update pathauthentication pathparser or protocol path
AI analysis · Low 36/100

This commit is a preventive build-hardening change. It adds compiler annotations (WARN_UNUSED_RESULT) to many functions that return success/failure codes, so the compiler will warn if a caller ignores the result. The goal is to catch future bugs where an error return is silently dropped, but the commit itself does not fix any specific known bug or change runtime behavior.

Lower-priorityassets: explicitly allow precision field to be optionalby Mike Tolkachev · 36f997b9 · Jun 23, 2026 · 1 fileMessage 50 · ThinLow 26Details
Commit message · Mike Tolkachev

assets: explicitly allow precision field to be optional

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

This small change makes the 'precision' number in asset metadata optional, defaulting to 0 if missing. Previously, the code may have treated a missing precision field as a failure. The patch uses a wrapper that explicitly ignores any error from reading the field, which could hide unexpected parsing problems. There is no direct evidence this is exploitable, but silently ignoring errors can make future bugs harder to detect.

Lower-priorityusb: remove unused return from usb top level actionsby Jon Griffiths · 2ff2b31d · Jun 23, 2026 · 2 filesMessage 50 · ThinInformational 15Details
Commit message · Jon Griffiths

usb: remove unused return from usb top level actions

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

This commit is a minor code cleanup in the USB storage feature of the Blockstream Jade hardware wallet. It changes two functions so they return nothing (void) instead of a true/false value, because the returned value was never actually used. There is no security-relevant change here.