BS
← All projectsBlockstream

Blockstream Jade

Firmware for Jade and Jade Plus Bitcoin hardware wallets.

BitcoinHardware walletsElevated watch
Repository coverage

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

106security candidates69second-pass queue437AI analyses
25commits · 30 days
67commits · 60 days
220commits · 180 days
417commits · 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
32Strong · 80–100
182Adequate · 60–79
250Thin · 40–59
38Opaque · 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 Griffiths31357282157
Mike Tolkachev431438152
Daniel Newton771668055
Mihailo Milenkovic878057
roderico333060
Valerio Vaccaro1526054
Jamie C. Driver525053
Gustavo Cateim917078
Austin-Fulbright414060
quantpoet111072
cmiguelrn111045
tokyovyse111063
Analysis record

Published AI watches

Last scanned 15 minutes ago

Informational 20 AI analysisMessage 65 · Adequate
BS BlockstreamBlockstream Jade BitcoinHardware wallets

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

This commit fixes the use of the "%zu" printf format specifier, which is not supported by the ESP32 toolchain used in this project. The unsupported format could cause log messages and user-facing strings to display incorrect or garbage val…

Use of unsupported printf format specifier %zu on embedded targetPotential for malformed log/UI output due to undefined format behaviorAddition of CI guard to prevent recurrence
26042182by Jon Griffiths+21−145 files
No security note in commit
Low 33 AI analysisMessage 30 · Opaque
BS BlockstreamBlockstream Jade BitcoinHardware wallets

otp: release md context on failure and clean temporary buffers

This commit fixes cleanup in the one-time-password (OTP) code. Previously, if setting up the cryptographic hash context failed, the code could return without freeing that context, and temporary buffers holding sensitive counter/HMAC data w…

Resource leak fix: mbedtls_md_free() now called on prepare_md_ctx failure pathSensitive buffer zeroization: wally_bzero() added for rcnt_buf and hmacControl-flow change from macro-based early return to explicit success checks
6e2cb6b6by Mike Tolkachev+26−141 file
No security note in commit
Low 47 AI analysisMessage 25 · Opaque
BS BlockstreamBlockstream Jade BitcoinHardware wallets

identity: clean temporary hash buffer

This commit fixes a small but real security hygiene issue in Blockstream Jade, a hardware wallet. A temporary buffer that holds a sensitive cryptographic hash (HMAC-SHA512 output used to derive child private keys) was not marked as sensiti…

Sensitive memory not marked for clearing (missing SENSITIVE_PUSH/POP)Buffer holds HMAC-SHA512 output used in BIP32 hardened child key derivationPatch adds explicit sensitive-memory lifecycle management
b5c35779by Mike Tolkachev+2−01 file
No security note in commit
Low 36 AI analysisMessage 15 · Opaque
BS BlockstreamBlockstream Jade BitcoinHardware wallets

qrmode: clean temporary buffer

This commit adds cleanup of a temporary memory buffer used when turning data into QR codes on the Blockstream Jade hardware wallet. The buffer could previously remain in memory after use, potentially leaving sensitive QR data behind for la…

Sensitive temporary buffer not cleared before fixUse of SENSITIVE_PUSH/SENSITIVE_POP memory-clearing macrosQR payload data may include private or confidential material
34f68c20by Mike Tolkachev+2−01 file
No security note in commit
Low 43 AI analysisMessage 50 · Thin
BS BlockstreamBlockstream Jade BitcoinHardware wallets

pinserver: retain unit private key on url change

This commit changes how Blockstream Jade handles its PIN server settings. Previously, changing the PIN server web address (URL) also wiped the device's private PIN encryption key, forcing the device to create a fresh one. The patch keeps t…

PIN private key lifecycle change: key retained on URL-only pinserver updatePublic-key change still triggers private-key erasure/regenerationDebug-clean and full reset still erase private key
ddcd93a3by Mike Tolkachev+38−324 files
No security note in commit
Informational 15 AI analysisMessage 45 · Thin
BS BlockstreamBlockstream Jade BitcoinHardware wallets

add more boards and descriptions

This commit is a documentation update for the do-it-yourself (DIY) hardware section of the Blockstream Jade project. It adds descriptions and photos for additional supported circuit boards and updates image file references. There are no co…

f4fb150dby Valerio Vaccaro+65−1625 files
No security note in commit
Moderate 63 AI analysisMessage 50 · Thin
BS BlockstreamBlockstream Jade BitcoinHardware wallets

process: limit array sizes in sign_tx, register_multisig and sign_bip85_digests

This commit adds size limits to several message-handling functions in the Blockstream Jade hardware wallet firmware. It caps how many asset records, transaction inputs/outputs, multisig signers, and BIP85 RSA digests a single RPC message c…

Adds explicit upper bounds on attacker-controllable array sizesRejects zero-input/zero-output transactions before further processingMoves BIP85 digest count validation before memory allocation
e87f26bfby Daniel Newton+251−8114 files
No security note in commit
Informational 15 AI analysisMessage 28 · Opaque
BS BlockstreamBlockstream Jade BitcoinHardware wallets

Update CHANGELOG.md

This commit only updates the project's CHANGELOG.md file to add release notes for version 1.0.41. It does not change any source code, build scripts, or configuration. The changelog text itself states that version 1.0.41 contains important …

Changelog describes prior security fixes in release 1.0.41Mentions external security researchers and tools (Loupe, Kvazar)References security-relevant improvements: stack protection, entropy, secure version, memory scrubbing, thread safety
dd45a7dcby Jon Griffiths+49−01 file
Vendor flagged security relevance
Informational 15 AI analysisMessage 35 · Opaque
BS BlockstreamBlockstream Jade BitcoinHardware wallets

jadepy: update jadepy release

This commit simply bumps the version of a Python dependency called jade-client from 1.0.40 to 1.0.41, along with its matching cryptographic hashes and a fresh PGP signature. There is no code change visible here, and nothing in the commit m…

75eeada4by Jon Griffiths+19−192 files
No security note in commit
Informational 15 AI analysisMessage 45 · Thin
BS BlockstreamBlockstream Jade BitcoinHardware wallets

consistency: fix docs/comment/script typos

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

9ea7eed3by Jon Griffiths+5−55 files
No security note in commit
Informational 17 AI analysisMessage 50 · Thin
BS BlockstreamBlockstream Jade BitcoinHardware wallets

esp_lcd: vendor the esp_lcd component (ESP-IDF v5.5.4)

This commit copies the ESP-IDF 'esp_lcd' display-driver component directly into the Blockstream Jade firmware repository (a process called 'vendoring') at version 5.5.4. It adds about 8,700 lines of display-interface code for LCD panels us…

Large vendored third-party driver import (+8,718 lines, 43 files)Driver code runs in interrupt context and uses DMA, which historically carries memory-safety and cache-coherency risksNo explicit security fix or bug-fix narrative in commit title/message
d89207bfby Daniel Newton+8718−043 files
No security note in commit
Informational 21 AI analysisMessage 57 · Thin
BS BlockstreamBlockstream Jade BitcoinHardware wallets

build: "fakeprod" prod-like development mode

This commit adds an official developer-only 'fakeprod' build mode for Blockstream Jade hardware wallets. It deliberately weakens several security settings (single signature, committed private keys, readable flash-encryption key, enabled JT…

In-tree private keys committed to repository (tools/fakeprod_v2.pem, tools/fakeprod_attest.pem)Secure boot minimum signatures reduced from 2 to 1Flash encryption set to DEVELOPMENT mode with key readable
cecedc76by Daniel Newton+350−59 files
Vendor flagged security relevance
Low 45 AI analysisMessage 45 · Thin
BS BlockstreamBlockstream Jade BitcoinHardware wallets

urldecode: add validation for URL encoding

This commit hardens a URL-decoding helper in Blockstream Jade's firmware. It adds validation so malformed percent-encoding, embedded null bytes, control characters, and non-ASCII bytes are rejected instead of being silently decoded. A new …

Input validation added for percent-encoded sequencesRejection of embedded NUL bytes and control characters in decoded outputRejection of non-ASCII decoded bytes (>=0x80 and DEL 0x7f)
dd0d699dby Mike Tolkachev+100−272 files
No security note in commit
Low 26 AI analysisMessage 73 · Adequate
BS BlockstreamBlockstream Jade BitcoinHardware wallets

qr: split datastream data into its own allocation, reorder alloc/free calls

This change rewrites how a small QR-code scanning library allocates memory. Instead of one big 16 KB block, it now uses two separate 8 KB blocks, and it frees them in the reverse order they were allocated. The stated goal is to avoid memor…

Memory allocation pattern changed from single large allocation to two smaller allocationsAllocation/free ordering changed to LIFO-style reverse pairingPointer field added to struct that previously held an inline array
43640f8cby Jon Griffiths+24−153 files
No security note in commit
Low 46 AI analysisMessage 45 · Thin
BS BlockstreamBlockstream Jade BitcoinHardware wallets

psbt: check output amount presence before reading

This commit tightens how Blockstream Jade reads output amounts from a Partially Signed Bitcoin Transaction (PSBT). Before, the code tried to read the amount directly without first confirming it was actually present. Now it checks whether t…

Missing-field check added before sensitive value readPSBT output amount parsing hardenedDefensive validation of libwally presence flags
9f2b916dby Jon Griffiths+2−11 file
No security note in commit
Moderate 59 AI analysisMessage 50 · Thin
BS BlockstreamBlockstream Jade BitcoinHardware wallets

psbt: require that all psbt bytes are consumed when parsing

This commit tightens how Blockstream Jade verifies a Bitcoin transaction file (PSBT) before signing. It now requires that every byte in the file is part of the transaction, with no leftover or trailing data allowed. Previously, extra bytes…

Parsing now rejects trailing/unconsumed bytes in PSBT inputChange is in the signing code path, directly affecting what the hardware wallet will signUse of stricter libwally-core parse flag (COMPLETE) indicates parser hardening
605d86acby Jon Griffiths+1−11 file
No security note in commit
Informational 15 AI analysisMessage 68 · Adequate
BS BlockstreamBlockstream Jade BitcoinHardware wallets

hardware: add Jade Plus design files

This commit reorganizes existing hardware design files for the original Jade device into a new subfolder and adds the open-source hardware design files for a new product, the Jade Plus. It does not change any software, firmware, or device …

5ad85661by bitcoinhelp+2573−122520 files
No security note in commit
Informational 15 AI analysisMessage 55 · Thin
BS BlockstreamBlockstream Jade BitcoinHardware wallets

tests: migrate low level tests

This commit only moves and reorganizes existing test code. It adds a new helper to check whether the current transport is a specific type, moves a shared wait() function into a common test package file, and migrates a large set of low-leve…

767006a0by Valerio Vaccaro+1580−54 files
No security note in commit
Low 27 AI analysisMessage 68 · Adequate
BS BlockstreamBlockstream Jade BitcoinHardware wallets

mnemonic: restore recovery phrase by word number

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 refact…

New user-input path for seed recovery (word numbers instead of words)Refactoring of mnemonic input/validation helpersAddition of SENSITIVE_PUSH/POP for local mnemonic buffers
99927491by roderico+580−3183 files
No security note in commit
Informational 18 AI analysisMessage 68 · Adequate
BS BlockstreamBlockstream Jade BitcoinHardware wallets

ui: support bounded variable-length digit entry

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 beha…

New bounded numeric input path may prevent out-of-range values in future callersRefactoring centralizes input validation rather than relying on callersNo buffer-size changes observed; digit array remains DIGIT_ENTRY_SIZE (6) elements
69627745by roderico+128−332 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-prioritygui: hold the gui mutex while flipping the displayby Bota · 05582cf1 · Sep 23, 2026 · 1 fileMessage 73 · AdequateTriage 0Details
Commit message · Bota

gui: hold the gui mutex while flipping the display

gui_set_flipped_orientation() talks to the panel from the calling task,
while the gui task may be flushing a frame at the same time.

The gui task holds the gui mutex while it flushes, so take it here too.

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Lower-priorityabort: only try to show the error message onceby Bota · 0cc247c7 · Sep 21, 2026 · 1 fileMessage 68 · AdequateTriage 0Details
Commit message · Bota

abort: only try to show the error message once

If showing the "Internal error" message fails an assertion, jade_abort() is
called again and tries to show the same message again, which fails in the
same way, so the device stays on whatever was on screen. Only try once, so
a second failure goes straight on to the real abort.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Lower-priorityui: fix centred messages on displays taller than 240 pixelsby Bota · a3dfebb3 · Sep 21, 2026 · 1 fileMessage 73 · AdequateTriage 0Details
Commit message · Bota

ui: fix centred messages on displays taller than 240 pixels

make_show_message_activity() asserts that the padding used to centre a
multi-line message is below 100, a limit scaled by hand for displays up to
about 240 pixels high. On the 280 pixel Waveshare Touch LCD 2 a two or three
line message with no title bar needs more than that, so it aborts - and the
"Internal error" screen shown by jade_abort() is one of those messages.

The padding is stored as a uint8_t, so check against that instead.

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Lower-prioritypower: add missed source formattingby Jon Griffiths · 5c94c021 · Sep 21, 2026 · 1 fileMessage 45 · ThinTriage 0Details
Commit message · Jon Griffiths

power: add missed source formatting

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-priorityserial: fix tinyusb init with esp_tinyusb 2.xby Bota · 6f46b8a8 · Sep 21, 2026 · 1 fileMessage 68 · AdequateTriage 8Details
Commit message · Bota

serial: fix tinyusb init with esp_tinyusb 2.x

esp_tinyusb 2.x validates the task settings passed to
tinyusb_driver_install(), so the zero-initialised config is now rejected
("Task size can't be 0"): serial_init() fails and every ESP32-S3 build
using TinyUSB aborts at boot. Use TINYUSB_DEFAULT_CONFIG() instead.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
defensive validation
Lower-prioritypower: add support for TTGO T-Display S3 Pro Camera power managementby Darrell · 6f1d22f4 · Sep 21, 2026 · 4 filesMessage 50 · ThinTriage 0Details
Commit message · Darrell

power: add support for TTGO T-Display S3 Pro Camera power management

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Security candidatefmt: fix and prevent future use of unsupported format spec "zu"by Jon Griffiths · 26042182 · Sep 21, 2026 · 5 filesMessage 65 · AdequateInformational 20Details
Commit message · Jon Griffiths

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

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

65/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
Why it was queued
signing or wallet pathauthentication path
AI analysis · Informational 20/100

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

Lower-prioritydiy: add support for Waveshare Touch LCD 3.5by Bota · 52f91228 · Sep 20, 2026 · 15 filesMessage 68 · AdequateTriage 0Details
Commit message · Bota

diy: add support for Waveshare Touch LCD 3.5

ESP32-S3 board with a 3.5inch 480x320 capacitive touch display
(ST7796/FT6336), OV5640 camera and AXP2101 pmu.

The touch controller, the pmu and the camera sccb share the same i2c pins,
so the touchscreen owns the only bus on them and both the pmu and the camera
attach to it, as done for the T-Display S3 Pro camera.

The 3.5B variant uses a different (QSPI) display controller and is not
supported.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Security candidateotp: release md context on failure and clean temporary buffersby Mike Tolkachev · 6e2cb6b6 · Sep 18, 2026 · 1 fileMessage 30 · OpaqueLow 33Details
Commit message · Mike Tolkachev

otp: release md context on failure and clean temporary buffers

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

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

Lower-prioritymnemonic: clean temporary word buffersby Mike Tolkachev · e9f9462c · Sep 17, 2026 · 2 filesMessage 40 · ThinTriage 0Details
Commit message · Mike Tolkachev

mnemonic: clean temporary word buffers

Also add intermediate buffer to sensitive stack earlier.

40/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body! Contains work-in-progress language
Lower-prioritybip85: clean intermediate values of RSA contextby Mike Tolkachev · b462aba4 · Sep 17, 2026 · 1 fileMessage 45 · ThinTriage 0Details
Commit message · Mike Tolkachev

bip85: clean intermediate values of RSA context

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-prioritygui: clean icon buffers having potentially sensitive databy Mike Tolkachev · fe510f56 · Sep 17, 2026 · 4 filesMessage 50 · ThinTriage 0Details
Commit message · Mike Tolkachev

gui: clean icon buffers having potentially sensitive data

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-priorityota: handle unavailable releases and default download targetby ammann · eec5184b · Sep 16, 2026 · 1 fileMessage 50 · ThinTriage 0Details
Commit message · ammann

ota: handle unavailable releases and default download target

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-priorityjadepy: stop reading and retrying closed TCP streamsby ammann · 5177b14c · Sep 16, 2026 · 4 filesMessage 65 · AdequateTriage 0Details
Commit message · ammann

jadepy: stop reading and retrying closed TCP streams

Ignore exceptions while draining; update docs.

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

65/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
Lower-prioritytests: move testvectors in a fileby Valerio Vaccaro · 99bcca42 · Sep 15, 2026 · 3 filesMessage 55 · ThinTriage 0Details
Commit message · Valerio Vaccaro

tests: move testvectors in a file

55/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
Lower-priorityqemu: use device PSRAM malloc thresholds to avoid DRAM fragmentationby Daniel Newton · d0af2522 · Sep 14, 2026 · 1 fileMessage 62 · AdequateTriage 0Details
Commit message · Daniel Newton

qemu: use device PSRAM malloc thresholds to avoid DRAM fragmentation

62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Explains rationale or failure mode! No meaningful explanatory body
AI review queuedidentity: clean temporary hash bufferby Mike Tolkachev · b5c35779 · Sep 11, 2026 · 1 fileMessage 25 · OpaqueLow 47Details
Commit message · Mike Tolkachev

identity: clean temporary hash buffer

25/100 · OpaqueMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body! Contains work-in-progress language
Why it was queued
second-pass: opaque commit message
AI analysis · Low 47/100

This commit fixes a small but real security hygiene issue in Blockstream Jade, a hardware wallet. A temporary buffer that holds a sensitive cryptographic hash (HMAC-SHA512 output used to derive child private keys) was not marked as sensitive memory. That means the buffer could be left uncleared in RAM after use, potentially leaking key material if an attacker could read device memory. The patch marks the buffer with SENSITIVE_PUSH so it is properly wiped with SENSITIVE_POP. It is a cleanup/fix, not a full exploit chain by itself.

Lower-prioritytests: move bcur selfcheck code to libjadeby Daniel Newton · a55811a9 · Sep 10, 2026 · 3 filesMessage 55 · ThinTriage 0Details
Commit message · Daniel Newton

tests: move bcur selfcheck code to libjade

55/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
AI review queuedqrmode: clean temporary bufferby Mike Tolkachev · 34f68c20 · Sep 10, 2026 · 1 fileMessage 15 · OpaqueLow 36Details
Commit message · Mike Tolkachev

qrmode: clean temporary buffer

15/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body! Contains work-in-progress language
Why it was queued
second-pass: opaque commit message
AI analysis · Low 36/100

This commit adds cleanup of a temporary memory buffer used when turning data into QR codes on the Blockstream Jade hardware wallet. The buffer could previously remain in memory after use, potentially leaving sensitive QR data behind for later code to read. The fix marks the buffer as sensitive and securely clears it after use.

Lower-prioritystorage: clean NVS security configuration after useby Mike Tolkachev · 381b3b9f · Sep 4, 2026 · 1 fileMessage 55 · ThinTriage 0Details
Commit message · Mike Tolkachev

storage: clean NVS security configuration after use

55/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Names security-relevant behavior explicitly! No meaningful explanatory body
Lower-prioritygui: widen deep status bar split to avoid truncating device idby Jon Griffiths · a7429479 · Sep 4, 2026 · 1 fileMessage 62 · AdequateTriage 0Details
Commit message · Jon Griffiths

gui: widen deep status bar split to avoid truncating device id

62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Explains rationale or failure mode! No meaningful explanatory body
Lower-prioritydocs: add pytest to firmware test instructionsby Mike Tolkachev · ddbe59f2 · Sep 1, 2026 · 1 fileMessage 67 · AdequateTriage 0Details
Commit message · Mike Tolkachev

docs: add pytest to firmware test instructions

67/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
documentation-only discount
Security candidatepinserver: retain unit private key on url changeby Mike Tolkachev · ddcd93a3 · Aug 27, 2026 · 4 filesMessage 50 · ThinLow 43Details
Commit message · Mike Tolkachev

pinserver: retain unit private key on url change

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

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

AI review queuedadd more boards and descriptionsby Valerio Vaccaro · f4fb150d · Aug 27, 2026 · 25 filesMessage 45 · ThinInformational 15Details
Commit message · Valerio Vaccaro

add more boards and descriptions

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
second-pass: unusually broad change
AI analysis · Informational 15/100

This commit is a documentation update for the do-it-yourself (DIY) hardware section of the Blockstream Jade project. It adds descriptions and photos for additional supported circuit boards and updates image file references. There are no code changes that affect security.

AI review queuedprocess: limit array sizes in sign_tx, register_multisig and sign_bip85_digestsby Daniel Newton · e87f26bf · Aug 25, 2026 · 14 filesMessage 50 · ThinModerate 63Details
Commit message · Daniel Newton

process: limit array sizes in sign_tx, register_multisig and sign_bip85_digests

50/100 · ThinMessage clarity
✓ Specific, 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 · Moderate 63/100

This commit adds size limits to several message-handling functions in the Blockstream Jade hardware wallet firmware. It caps how many asset records, transaction inputs/outputs, multisig signers, and BIP85 RSA digests a single RPC message can contain. The change appears to be a hardening patch: without these limits, an attacker or malformed host application could send an extremely large array and potentially exhaust device memory, cause long processing delays, or trigger memory corruption during signing and multisig registration. The patch also makes the array-length check happen earlier and more consistently across the code.