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 9 minutes ago

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

process: whitelist reply message function calls

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

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

temporary_stack: whitelist temporary task function calls

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

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

consistency: fix typos

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

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

docs: document get_bip85_bip39_entropy

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

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

bip85: expose get_bip85_bip39_entropy over rpc in addition to qr

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

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

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

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

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

sign_tx/sign_psbt: extra check for BTC inputs

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

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

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

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

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

tests: migrate pin action tests from test_jade to rpc tests

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

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

tests: add tests for pin actions via debug_set_pin

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

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

process: require user to permit get_identity_shared_key RPC

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

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

auth: add unattended pin selection for rpc tests

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

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

pin: disallow pin update on initialized units in debug mode

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

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

tests: fix mnemonic handling following seed changes

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

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

malloc_ext: fix JADE_CALLOC_DRAM

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

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

sign_psbt: fix reply count for exact chunk sizes

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

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

ui: allow tapping directly on touchscreen elements

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

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

urldecode: use plain strlen in self-tests of libjade

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

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

assets: support tickers up to 24 characters

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

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

assets: improve empty ticker support

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

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

Explore captured commits

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

Lower-priorityci: security: execute all security test in same stageby Valerio Vaccaro · acdd5d40 · Jul 21, 2026 · 1 fileMessage 77 · AdequateTriage 0Details
Commit message · Valerio Vaccaro

ci: security: execute all security test in same stage

77/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Mentions testing or verification✓ Names security-relevant behavior explicitly! No meaningful explanatory body
Lower-priorityci: security: skip tests directoryby Valerio Vaccaro · 252fb8a3 · Jul 21, 2026 · 1 fileMessage 72 · AdequateTriage 0Details
Commit message · Valerio Vaccaro

ci: security: skip tests directory

72/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Mentions testing or verification✓ Names security-relevant behavior explicitly! No meaningful explanatory body
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.

Lower-prioritytests: remove blinding tests from test_jade.pyby Valerio Vaccaro · 4285f95f · Jul 17, 2026 · 2 filesMessage 55 · ThinTriage 0Details
Commit message · Valerio Vaccaro

tests: remove blinding tests from test_jade.py

55/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
Lower-prioritytests: migrate blindings testsby Valerio Vaccaro · 2a7560cb · Jul 17, 2026 · 2 filesMessage 45 · ThinTriage 0Details
Commit message · Valerio Vaccaro

tests: migrate blindings tests

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Mentions testing or verification! No meaningful explanatory body
Lower-prioritytests: remove address tests from test_jade.pyby Valerio Vaccaro · b1c8ed9d · Jul 17, 2026 · 1 fileMessage 55 · ThinTriage 0Details
Commit message · Valerio Vaccaro

tests: remove address tests from test_jade.py

55/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
Lower-prioritywally: update wally to release 1.5.6by Jon Griffiths · cfce08ce · Jul 11, 2026 · 1 fileMessage 45 · ThinInformational 0Details
Commit message · Jon Griffiths

wally: update wally to release 1.5.6

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

This commit updates a bundled dependency (libwally-core) to a newer release, but no actual diff content or release notes were provided. We cannot see what changed or whether any security issue is involved.

Lower-prioritypower: release PMU devices before deleting the i2c bus on M5CoreS3by Gustavo Cateim · fb3a009a · Jul 11, 2026 · 1 fileMessage 100 · StrongLow 26Details
Commit message · Gustavo Cateim

power: release PMU devices before deleting the i2c bus on M5CoreS3

Since ESP-IDF v5.5 i2c_del_master_bus() refuses to delete a bus that
still has devices attached and returns ESP_ERR_INVALID_STATE. On the
M5CoreS3, power_init() attaches the axp2101 and aw9523 devices and
then deletes the bus without releasing them, so under IDF 5.5.4 the
deinit fails, power_init() propagates the error and the JADE_ASSERT
in main.c aborts the boot. Same root cause as the touchscreen fix in
the previous commit (#306).

Remove both devices from the bus before deleting it.

Not tested on hardware (none available); the change mirrors the
touchscreen fix validated on the Waveshare S3 Touch LCD 2.

100/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✓ Links an issue, advisory, or supporting reference
Why it was queued
defensive validation
AI analysis · Low 26/100

This commit fixes a boot failure on the M5CoreS3 hardware. A recent update to the underlying Espressif SDK (ESP-IDF v5.5) changed the rules for deleting an I2C bus: it now refuses to delete a bus that still has devices attached. The power initialization code was attaching two power-management chips to the bus and then trying to delete the bus without detaching them first, causing the device to abort boot. The fix simply detaches those two devices before deleting the bus. There is no security vulnerability here—it's a compatibility/bug fix for a crash-on-boot scenario.

Security candidateinput: release touch handles before deleting the i2c busby Gustavo Cateim · 36776fec · Jul 11, 2026 · 1 fileMessage 86 · StrongLow 27Details
Commit message · Gustavo Cateim

input: release touch handles before deleting the i2c bus

Since ESP-IDF v5.5 (espressif/esp-idf@e73d78ba) i2c_del_master_bus()
refuses to delete a bus that still has devices attached and returns
ESP_ERR_INVALID_STATE. The touchscreen task registers a panel IO
device on the bus but never releases it, so under IDF 5.5.4 the first
touchscreen_deinit() fails and aborts via ESP_ERROR_CHECK.

On boards that panic with PRINT_HALT, such as the Waveshare S3 Touch
LCD 2, this freezes the device on the boot splash screen while
gathering camera entropy, and also hangs the QR scanner and the
camera exit path, since the touchscreen is restarted around every
camera start/stop (see #306).

Releasing the touch handle and the panel IO device (which removes it
from the bus) before deleting the bus restores the deinit/init cycle,
and also fixes a heap leak present under IDF 5.4 where both handles
leaked on every cycle.

Co-authored-by: oroderico <oroderico@users.noreply.github.com>

86/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference✓ Names security-relevant behavior explicitly
Why it was queued
entropy or randomness
AI analysis · Low 27/100

This commit fixes a bug where the touchscreen driver failed to clean up internal handles when shutting down. On newer ESP-IDF firmware, this cleanup failure caused the device to panic and freeze during boot and when using the camera or QR scanner. The fix releases the touch and panel IO handles before deleting the I2C bus, preventing freezes and a memory leak. There is no evidence this is a security vulnerability or exploitable by an attacker.

Lower-priorityinput: mirror touch navbar band on display orientation flipby Gustavo Cateim · 9819ed29 · Jul 11, 2026 · 1 fileMessage 73 · AdequateTriage 0Details
Commit message · Gustavo Cateim

input: mirror touch navbar band on display orientation flip

The touch controllers keep reporting physical panel coordinates after the display orientation is flipped, so the virtual navbar band stops lining up with the rendered buttons: taps still land on the stale Y band.

Mirror only the touch Y coordinate from the touchscreen task whenever the GUI orientation changes. This keeps the navbar hit area in the same coordinate space as the display while preserving the physical left/right button actions. Mirroring X would make the right-side button trigger prev after a flip.

The M5 Core2 is excluded: its buttons are silk-screened on a fixed capacitive strip below the display and must not follow the flip.

For the software mirror to be correct, y_max must span the full touch panel, including the navbar area below the main display, so it gains TOUCH_BUTTON_AREA. The navbar band check also replaces the hardcoded touch_y > 200 with the board display height: on displays taller than 200 pixels, such as the Waveshare S3 Touch LCD 2 (280 pixels), the old value made taps on the bottom of the GUI area trigger navigation.

Neither expression includes CONFIG_DISPLAY_OFFSET_Y. That value is not panel geometry: it is the ST7789 GRAM gap fed to esp_lcd_panel_set_gap(), a display-side API. The touch controller reports panel coordinates and never sees it, so adding it here would mix two coordinate spaces. It is 0 on three of the four touchscreen boards, but 80 on the TTGO TWatchS3, where it would push the navbar threshold to 280 on a panel that only reports 0..239 and make the navbar unreachable in the default orientation.

Co-authored-by: oroderico <oroderico@users.noreply.github.com>

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Lower-prioritydisplay: redraw touch navbar on orientation flipby oroderico · b15df8e5 · Jul 11, 2026 · 4 filesMessage 68 · AdequateTriage 0Details
Commit message · oroderico

display: redraw touch navbar on orientation flip

On boards with a virtual touch navbar (TTGO TWatchS3, M5 CoreS3,
Waveshare S3 Touch LCD 2) the prev/OK/next buttons are drawn only once
at startup, inside display_init(). Flipping the display orientation
remaps the panel scan direction, so the navbar was left stale and
upside down at the wrong edge of the panel.

Extract the drawing code into display_touch_navbar_redraw() and call
it from gui_set_flipped_orientation() whenever the orientation
actually changes. Boards without a navbar get an inline no-op stub.
The TOUCH_BUTTON_AREA constant moves to display.h so the touch input
code can share it. The two 50 ms settle delays stay in display_init(),
as flipping does not need them.

Co-authored-by: Gustavo Cateim <cateim@gmail.com>

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Lower-prioritydiy: Add M5StickC Plus2 backlight brightness controlby oroderico · 5c22b7d3 · Jul 10, 2026 · 4 filesMessage 50 · ThinInformational 15Details
Commit message · oroderico

diy: Add M5StickC Plus2 backlight brightness control

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 a screen brightness control feature for the M5StickC Plus2 hardware variant of the Blockstream Jade device. It is a hardware-support and user-interface change, not a security fix or vulnerability. There is no indication of a security issue in the code changes.

AI review queuedurldecode: add self-tests for validation and decodeby Mike Tolkachev · c9873a11 · Jul 9, 2026 · 1 fileMessage 60 · AdequateInformational 12Details
Commit message · Mike Tolkachev

urldecode: add self-tests for validation and decode

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
parser or protocol pathsecond-pass: security-sensitive path
AI analysis · Informational 12/100

This commit only adds a new test file that exercises an existing URL-decoding function. It does not change any production code, so by itself it cannot introduce a security vulnerability or fix one. It is a defensive-quality improvement that adds self-tests.

Lower-prioritytests: remove ping test from test_jade.pyby Valerio Vaccaro · 2a4379f4 · Jul 9, 2026 · 1 fileMessage 55 · ThinTriage 0Details
Commit message · Valerio Vaccaro

tests: remove ping test from test_jade.py

55/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
AI review queuedtests: remove multisig tests from test_jade.pyby Valerio Vaccaro · 74e3af87 · Jul 9, 2026 · 62 filesMessage 55 · ThinInformational 15Details
Commit message · Valerio Vaccaro

tests: remove multisig tests from test_jade.py

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

This commit only deletes test files and test code for multisignature wallet features from the Blockstream Jade test suite. It does not change the actual firmware, runtime code, or how the device handles multisig wallets. There is no security fix or vulnerability introduced here—only a cleanup of automated tests.

Security candidatetests: migrate ping testby Valerio Vaccaro · 486acb06 · Jul 9, 2026 · 1 fileMessage 38 · OpaqueInformational 15Details
Commit message · Valerio Vaccaro

tests: migrate ping test

38/100 · OpaqueMessage clarity
✓ Subject identifies a change✓ Mentions testing or verification! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
authentication path
AI analysis · Informational 15/100

This commit adds a new automated test file that checks whether sending a simple 'ping' message to a Jade hardware wallet interrupts an ongoing signing process. It is purely a test addition with no changes to production code, and it does not fix or introduce any security vulnerability.

Lower-priorityrepo: remove stray cUR submodule gitlinkby odudex · 88d69aa6 · Jul 8, 2026 · 1 fileMessage 68 · AdequateInformational 15Details
Commit message · odudex

repo: remove stray cUR submodule gitlink

Commit 121adaad was cherry-picked from a branch where components/cUR is a proper submodule, and accidentally carried the cUR gitlink along without a matching .gitmodules entry. This breaks 'git submodule update --init' with "no submodule mapping found in .gitmodules for path 'components/cUR'".

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

This commit removes a leftover Git submodule reference (a 'gitlink') that had no matching configuration entry. It fixes a Git checkout error but does not change any compiled code, cryptographic logic, or device behavior. There is no security issue here.

Lower-prioritylibjade: accept non-literal tags in mocked ESP_LOG macrosby odudex · 121adaad · Jul 8, 2026 · 2 filesMessage 73 · AdequateInformational 15Details
Commit message · odudex

libjade: accept non-literal tags in mocked ESP_LOG macros

k_quirc logs with a 'static const char* TAG' tag, which the mocked
macros could not handle as they pasted the tag as a string literal.
Print it via %s instead, fixing the libjade host build.

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
AI analysis · Informational 15/100

This is a small build-fix change. The project has mock versions of ESP logging macros used when building on a regular computer (host build). Previously these macros treated the log tag as a string literal, which broke compilation when a module passed a variable tag. The patch changes the macros to print the tag via %s instead. There is no security issue here.

AI review queuedjade_cli: add selfcheck commandby Jon Griffiths · 32d3c9a7 · Jul 8, 2026 · 1 fileMessage 35 · OpaqueInformational 15Details
Commit message · Jon Griffiths

jade_cli: add selfcheck command

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 adds a new command-line command called 'selfcheck' to the Jade CLI tool. It simply calls an existing device function and prints the result. There is no indication of a security fix or vulnerability being patched.

Lower-priorityci: avoid downloading artifacts for non-flash testingby Jon Griffiths · d786cefa · Jul 8, 2026 · 2 filesMessage 72 · AdequateInformational 15Details
Commit message · Jon Griffiths

ci: avoid downloading artifacts for non-flash testing

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

This commit only changes CI (Continuous Integration) pipeline configuration. It tells certain automated test jobs not to download build artifacts from previous stages because those tests do not need them. There is no change to the actual Jade firmware, wallet logic, cryptography, or any code that users run.

Lower-priorityAdd TTGO T-Display backlight brightness controlby oroderico · b28e145c · Jul 8, 2026 · 4 filesMessage 45 · ThinInformational 15Details
Commit message · oroderico

Add TTGO T-Display backlight brightness control

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

This commit adds a screen brightness control feature for the TTGO T-Display development board used with Blockstream Jade. It is a hardware-support change, not a security fix or vulnerability. There are no security signals in the code or commit message.

Security candidateotp: add validation of URL-encoded strings in OTP contextby Mike Tolkachev · b0552c8e · Jul 3, 2026 · 3 filesMessage 50 · ThinLow 46Details
Commit message · Mike Tolkachev

otp: add validation of URL-encoded strings in OTP context

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

This commit adds input validation to make sure the text shown in the OTP (one-time password) setup screen is properly URL-encoded and printable. It is likely a hardening fix to prevent malformed or sneaky label/issuer strings from confusing the user or causing unexpected behavior on the hardware wallet's screen, but the commit message does not call it a security fix.

Lower-prioritylog: move cbor message and read bytes logging to debug levelby Daniel Newton · 545fb1e7 · Jul 2, 2026 · 2 filesMessage 50 · ThinTriage 0Details
Commit message · Daniel Newton

log: move cbor message and read bytes logging to debug level

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