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 50 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 README.md to cover recent build/config changesby Jon Griffiths · 6ff10c6a · Dec 5, 2025 · 1 fileMessage 62 · AdequateInformational 15Details
Commit message · Jon Griffiths

docs: update README.md to cover recent build/config changes

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
documentation-only discount
AI analysis · Informational 15/100

This commit only updates the README.md documentation file. It rewrites build and configuration instructions for developers, adds details about new device targets, and reorganizes sections. No source code, firmware logic, or security-sensitive behavior was changed.

Lower-priorityFix release date for version 1.0.38 in CHANGELOGby Jacob Heider · bc072653 · Dec 3, 2025 · 1 fileMessage 60 · AdequateInformational 15Details
Commit message · Jacob Heider

Fix release date for version 1.0.38 in CHANGELOG

Correct the release date for version 1.0.38. We don't want people waiting till Decembruary for the update.

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

This commit only fixes a typo in the release date for version 1.0.38 in the project's CHANGELOG file, changing '2025-13-26' (an invalid month) to '2025-11-26'. It does not change any software code, functionality, or security behavior.

Lower-prioritycamera: skip every second screen refresh during continuous scanningby Jon Griffiths · 369b182e · Dec 3, 2025 · 1 fileMessage 65 · AdequateInformational 13Details
Commit message · Jon Griffiths

camera: skip every second screen refresh during continuous scanning

Allows us to scan more frames per second overall.

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

This commit is a performance tweak for the camera preview screen on Blockstream Jade hardware wallets. It skips updating the on-screen preview every second camera frame so the device can analyze more frames per second when scanning QR codes. There is no security-relevant change visible in the code.

Lower-prioritybuild: use switch_to.sh for config generationby Jon Griffiths · e04adeb2 · Dec 3, 2025 · 4 filesMessage 57 · ThinInformational 15Details
Commit message · Jon Griffiths

build: use switch_to.sh for config generation

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 is a routine build-system cleanup. It changes how GitLab CI jobs select firmware configuration files, replacing inline shell commands with calls to a helper script called switch_to.sh. There is no indication this fixes or introduces a security vulnerability.

Lower-prioritychore: fix a large number of spelling issuesby fengyuchuanshen · d8528f03 · Dec 3, 2025 · 9 filesMessage 72 · AdequateInformational 15Details
Commit message · fengyuchuanshen

chore: fix a large number of spelling issues

Signed-off-by: fengyuchuanshen <fengyuchuanshen@outlook.com>

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

This commit only fixes spelling mistakes in comments, documentation, debug log messages, and a usage string. There are no code behavior changes, no security fixes, and no functional patches.

Lower-priorityconfig: enable maximum stack protections for dev devicesby Jon Griffiths · 8e9636a9 · Dec 3, 2025 · 4 filesMessage 65 · AdequateInformational 15Details
Commit message · Jon Griffiths

config: enable maximum stack protections for dev devices

A preparatory step for increasing production stack checking.

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

This commit changes a compiler setting in four development configuration files for the Blockstream Jade hardware wallet. It switches the stack overflow protection level from 'STRONG' to 'ALL' for developer devices only. This is a defensive hardening step, not a fix for an active security flaw. There is no evidence in the commit of any vulnerability being patched.

Lower-priorityci: increase the time allowance for v2 selfcheckby Jon Griffiths · 590823af · Dec 3, 2025 · 1 fileMessage 80 · StrongInformational 15Details
Commit message · Jon Griffiths

ci: increase the time allowance for v2 selfcheck

This is likely caused by increased stack checks; increasing the speed of
individual RPC calls will be made in the future on a case by case basis.

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

This commit simply loosens a test timeout in the project's automated test suite. It changes how long a self-check test is allowed to take, likely because the test was failing due to slower internal safety checks. There is no change to the actual device firmware or wallet security logic, and no security issue is introduced.

Security candidatepsbt: fix a (harmless) off-by-one assert checkby Jon Griffiths · 42f6948c · Dec 3, 2025 · 1 fileMessage 45 · ThinInformational 18Details
Commit message · Jon Griffiths

psbt: fix a (harmless) off-by-one assert check

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

This commit fixes a boundary check in code that walks through parts of a Bitcoin transaction (PSBT). The old check allowed an index equal to the number of items, which is one too high. The commit message calls it 'harmless,' meaning it should not cause a real security problem in practice. It is a defensive correction to an assert that guards internal iteration.

Lower-priorityci: allow ci_flash to run on local development envsby Jon Griffiths · 522dffda · Dec 3, 2025 · 1 fileMessage 62 · AdequateInformational 15Details
Commit message · Jon Griffiths

ci: allow ci_flash to run on local development envs

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

This change is a developer tooling update. It makes the project's continuous-integration flash script work on local developer machines, not just the CI server. It adds fallback serial ports, creates a local Python virtual environment if one isn't present, skips Bluetooth testing if a Bluetooth tool is missing, and deactivates the virtual environment at the end. There is no indication this affects end-user security or the firmware itself.

AI review queuedquirc: fix compiler warningby Jon Griffiths · ea03ce7d · Dec 3, 2025 · 1 fileMessage 35 · OpaqueInformational 15Details
Commit message · Jon Griffiths

quirc: fix compiler warning

35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
parser or protocol pathsecond-pass: opaque commit messagesecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit only swaps the order of two C keywords ('const static' becomes 'static const') and adds a missing newline at the end of a file. It is a cosmetic/compiler-warning fix with no functional or security change.

Lower-priorityconfig: remove the debug jade configsby Jon Griffiths · 3fe8cf31 · Dec 3, 2025 · 6 filesMessage 60 · AdequateInformational 18Details
Commit message · Jon Griffiths

config: remove the debug jade configs

These can be created with:
./tools/switch_to.sh [jade|jade_v1_1|jade_v2] --dev --debug [--log|--log-cbor] [--jtag]

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

This commit removes six pre-made debug configuration files for the Blockstream Jade hardware wallet. The project message says these debug settings can now be created on demand using a build script instead of being stored in the repository. The change itself is a cleanup and does not fix a vulnerability, but shipping debug configs that enable verbose logging and JTAG debugging could make it easier for an attacker to analyze or tamper with a device if those configs were accidentally used in a production build. There is no direct evidence in the commit of a security incident or exploit.

Lower-priorityquirc: use float constants and convert division to multiplicationby Jon Griffiths · daf8ce63 · Dec 3, 2025 · 1 fileMessage 73 · AdequateInformational 15Details
Commit message · Jon Griffiths

quirc: use float constants and convert division to multiplication

Based on upstream commit:
https://github.com/dlbeer/quirc/commit/75ab5aa321facc28eabe56c4370dbdfb720cd82d

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
AI analysis · Informational 15/100

This commit is a routine performance and portability cleanup in the QR-code recognition library used by Blockstream Jade. It replaces floating-point division operations with equivalent multiplication-by-reciprocal operations and adds explicit 'float' type casts to numeric constants. There is no security-relevant change: the mathematical results are intended to be identical, and no bounds checks, memory handling, or cryptographic logic is modified.

Lower-prioritylog: socket server logger that communicates over wifiby Daniel Newton · 68751302 · Dec 3, 2025 · 7 filesMessage 65 · AdequateLow 44Details
Commit message · Daniel Newton

log: socket server logger that communicates over wifi

Set CONFIG_LOG_WIFI (default off) to enable

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

This commit adds an optional Wi-Fi logging feature to the Blockstream Jade hardware wallet. When enabled at compile time, the device can connect to a Wi-Fi network and stream its internal log messages over a TCP socket to a configured IP address and port. The feature is off by default and is intended only for development/debugging. It also includes extra profiling commands (like 'reset', 'stats', 'tasks') that can be sent over the same socket if another compile-time option is enabled. Because this feature can expose sensitive internal log data over a wireless network and includes remote commands, it could weaken security if accidentally enabled in a production build or used on an untrusted network.

Security candidateotp: clearer message when device does not have current time for TOTP functionby Daniel Newton · e9f544ff · Dec 3, 2025 · 4 filesMessage 50 · ThinInformational 20Details
Commit message · Daniel Newton

otp: clearer message when device does not have current time for TOTP function

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 20/100

This commit improves the on-screen error messages shown when a Blockstream Jade hardware wallet cannot generate a TOTP (time-based one-time password) code because the device does not know the current time. It does not change the security rules or fix a vulnerability; it only makes the failure message clearer to the user, suggesting they unlock the device with the Blockstream app to set the time.

Lower-prioritybc_ur: update to include native build supportby Jon Griffiths · e68c832a · Dec 3, 2025 · 1 fileMessage 45 · ThinInformational 3Details
Commit message · Jon Griffiths

bc_ur: update to include native build support

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

This commit updates a build configuration for a sub-component called bc_ur to support native (non-embedded) builds. The title and stats suggest a one-line change to a submodule or build file. There is no code diff available, no security-related language in the commit message, and no references linking this change to any security issue.

Lower-prioritybuild: add 'tools/switch_to.sh' to switch between different configsby Daniel Newton · 84578147 · Dec 3, 2025 · 1 fileMessage 77 · AdequateInformational 15Details
Commit message · Daniel Newton

build: add 'tools/switch_to.sh' to switch between different configs

Preferred to adding more sdkconfig.default files.

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

This commit adds a new developer helper script that lets engineers switch between different Jade hardware build configurations. It does not change any firmware code, cryptography, or user-facing behavior. It only automates build setup steps that developers could already do manually.

Security candidatelibjade: enable building the Jade firmware as a native libraryby Jon Griffiths · 30aef5c7 · Dec 3, 2025 · 63 filesMessage 83 · StrongInformational 15Details
Commit message · Jon Griffiths

libjade: enable building the Jade firmware as a native library

Implements an in-process instance of the Jade firmware. This can be
thought of as an emulated or virtual Jade device that runs in the address
space of the application that links to it.

Also expose a daemon process which allows using libjade from another
process using the existing jadepy API.

This initial implementation is highly experimental and incomplete, and
should under no circumstances be used beyond development and testing.

Co-authored-by: Lawrence Nahum <lawrence@greenaddress.it>

83/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
cryptography-sensitive pathauthentication path
AI analysis · Informational 15/100

This commit adds a new experimental developer/testing feature called libjade that lets the Jade hardware-wallet firmware be compiled and run as a normal Linux software library or daemon. It is explicitly marked as incomplete, not for real funds, and for development/testing only. There is no indication this is a security fix or that it addresses any vulnerability.

Lower-priorityquirc: always inline perspective_map functionby Jon Griffiths · d84629ce · Dec 3, 2025 · 1 fileMessage 45 · ThinInformational 15Details
Commit message · Jon Griffiths

quirc: always inline perspective_map function

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

This commit is a minor compiler-level optimization. It tells the compiler to always inline a small helper function used when mapping QR code corners to image coordinates. There is no visible security relevance: no input validation, memory access, or logic changes are made.

Lower-priorityota: shorten error code text for 1.x displaysby Jon Griffiths · 62fa83d6 · Dec 3, 2025 · 1 fileMessage 45 · ThinInformational 15Details
Commit message · Jon Griffiths

ota: shorten error code text for 1.x displays

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

This commit simply shortens the text shown on screen when an over-the-air (OTA) firmware update fails on older 1.x displays. It changes strings like 'OTA_ERR_SETUP' to 'ERR_SETUP' so they fit better on small screens. There is no security change.

Lower-prioritydocs: add security caveat and @DarkNavyOrg thanks to changelogby Jon Griffiths · 619baa1b · Dec 3, 2025 · 1 fileMessage 67 · AdequateInformational 7Details
Commit message · Jon Griffiths

docs: add security caveat and @DarkNavyOrg thanks to changelog

67/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Names security-relevant behavior explicitly! No meaningful explanatory body
Why it was queued
documentation-only discount
AI analysis · Informational 7/100

This commit only edits the project's changelog. It adds a note saying version 1.0.38 contains important security updates and thanks an outside security research group called DARKNAVY. The actual code fixes are not shown in this commit, so we cannot evaluate what the security problem is or how serious it is from the diff alone.

Lower-prioritybuild: only check hashes that are presentby Jon Griffiths · 895bab82 · Dec 3, 2025 · 1 fileMessage 57 · ThinLow 29Details
Commit message · Jon Griffiths

build: only check hashes that are present

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

This is a small fix to a release verification script. Previously, the script would try to compare a firmware file against its expected hash even when the hash file was missing, which could cause the script to crash or behave unpredictably. Now it only performs the comparison when the hash file actually exists. This is a build/release hygiene improvement rather than a fix for an active security vulnerability in the device itself.

Lower-prioritybuild: only generate deltas that are 1/2 the firmware size or lessby Jon Griffiths · 239b9c14 · Dec 3, 2025 · 3 filesMessage 62 · AdequateLow 26Details
Commit message · Jon Griffiths

build: only generate deltas that are 1/2 the firmware size or less

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 changes the build tooling that creates over-the-air (OTA) firmware update patches for the Blockstream Jade hardware wallet. It now refuses to generate a delta patch if the patch would be larger than half the size of the full new firmware, unless the caller explicitly uses a new '--force' flag. The CI scripts were updated to pass '--force' for their existing self-to-self test patches, so those tests still run. The change is a build/operational hardening measure: it prevents the release pipeline from shipping oversized delta updates that could be inefficient or potentially problematic, but it does not by itself fix a runtime vulnerability in the device.

Lower-prioritylog: added CONFIG_LOG_CBOR (default off) to control logging via jade serial APIby Daniel Newton · 95653c19 · Dec 3, 2025 · 2 filesMessage 50 · ThinLow 29Details
Commit message · Daniel Newton

log: added CONFIG_LOG_CBOR (default off) to control logging via jade serial API

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

This commit adds a new build-time setting (CONFIG_LOG_CBOR) that is off by default. Previously, the Jade hardware wallet could send log messages over its serial interface; now that behavior is gated behind an explicit opt-in flag. The change reduces the risk that diagnostic logs leak sensitive information over the serial port in normal production builds.

AI review queuedUpdate CHANGELOG.mdby Jon Griffiths · fb264239 · Nov 18, 2025 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · Jon Griffiths

Update CHANGELOG.md

28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
documentation-only discountsecond-pass: opaque commit message
AI analysis · Informational 15/100

This commit only updates the project's CHANGELOG.md file, adding release notes for version 1.0.37. It does not change any source code, configuration, or executable files. There is no security-relevant change in the diff itself.

Lower-prioritybuild: increment the firmware secure versionby Jon Griffiths · 3457a52c · Nov 18, 2025 · 6 filesMessage 57 · ThinLow 33Details
Commit message · Jon Griffiths

build: increment the firmware secure version

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

This commit changes the build settings for all production variants of the Blockstream Jade hardware wallet to set a 'secure version' to 1. This is part of the device's anti-rollback protection: once this version is set, the bootloader will refuse to run older firmware that has a lower secure version. On its own, this change does not fix a bug or add a feature users interact with; it is a build-time policy change that affects which firmware versions the device will accept in the future. It could be a routine hardening step, or it could be a response to a known vulnerability that the vendor wants to ensure cannot be exploited by downgrading to an older, vulnerable firmware. The commit message and diff do not say which is the case.