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

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

process: whitelist reply message function calls

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

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

temporary_stack: whitelist temporary task function calls

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

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

consistency: fix typos

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

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

docs: document get_bip85_bip39_entropy

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

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

bip85: expose get_bip85_bip39_entropy over rpc in addition to qr

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

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

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

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

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

sign_tx/sign_psbt: extra check for BTC inputs

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

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

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

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

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

tests: migrate pin action tests from test_jade to rpc tests

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

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

tests: add tests for pin actions via debug_set_pin

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

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

process: require user to permit get_identity_shared_key RPC

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

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

auth: add unattended pin selection for rpc tests

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

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

pin: disallow pin update on initialized units in debug mode

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

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

tests: fix mnemonic handling following seed changes

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

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

malloc_ext: fix JADE_CALLOC_DRAM

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

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

sign_psbt: fix reply count for exact chunk sizes

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

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

ui: allow tapping directly on touchscreen elements

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

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

urldecode: use plain strlen in self-tests of libjade

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

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

assets: support tickers up to 24 characters

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

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

assets: improve empty ticker support

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

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

Explore captured commits

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

Security candidatepsbt: always confirm green outputs when recovery signingby Jon Griffiths · a963f628 · Apr 16, 2026 · 1 fileMessage 50 · ThinModerate 57Details
Commit message · Jon Griffiths

psbt: always confirm green outputs when recovery signing

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing boundarysigning or wallet path
AI analysis · Moderate 57/100

This commit changes the logic in Blockstream Jade's PSBT signing flow so that, when the hardware wallet is acting as a 'recovery' key for a Green 2-of-3 wallet, it always asks the user to confirm outputs that belong to Green, rather than silently trusting them. Previously, the code skipped confirmation if Jade detected it was the recovery key and the output matched a Green script. The change flips the condition: now, if Jade is the recovery key OR the script does not match Green's expected pattern, the output must be confirmed. This is a defensive fix to prevent a compromised companion app or host from sneaking an unverified output past the user during recovery signing.

Security candidateui: fix backspace icon not shown in pin entry page (and checkmark icon in index entry page)by Daniel Newton · 749eaf51 · Apr 14, 2026 · 1 fileMessage 50 · ThinInformational 15Details
Commit message · Daniel Newton

ui: fix backspace icon not shown in pin entry page (and checkmark icon in index entry page)

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

This commit fixes a user-interface bug where the backspace icon was missing on the PIN entry screen and the checkmark/enter icon was missing on the index entry screen. It changes the number of allowed on-screen characters so the correct icons are displayed. There is no security issue here.

Security candidatemnemonic: gracefully handle invalid bcur-bip39 mnemonics, improve testsby Jon Griffiths · 898b9fb2 · Apr 14, 2026 · 5 filesMessage 91 · StrongModerate 59Details
Commit message · Jon Griffiths

mnemonic: gracefully handle invalid bcur-bip39 mnemonics, improve tests

- Show an error rather than asserting when importing an invalid mnemonic
- Reduce stack usage when parsing
- Reject clearly malformed mnemonics early
- Simplify code and share related constants

Suggested-by: Jordan Mecom (@jmecom) via https://github.com/jmecom/odo

91/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
secret or key material
AI analysis · Moderate 59/100

This update fixes how Blockstream Jade handles QR-code-based recovery phrases imported in a specific format (bcur-bip39). Previously, a malformed or invalid recovery phrase could crash the device because the code used internal 'assert' checks that halt the device when they fail. The patch replaces those hard crashes with proper error handling, rejects obviously wrong inputs earlier (wrong number of words, words that are too long, empty words), and reduces memory used on the stack. It also adds tests for bad inputs. In practical terms, scanning a bad wallet QR code is now more likely to show a user-friendly error instead of freezing or rebooting the device.

Security candidateattestation: ensure attestation provision signature is correctly sizedby Jon Griffiths · b6ca54db · Apr 14, 2026 · 1 fileMessage 78 · AdequateModerate 58Details
Commit message · Jon Griffiths

attestation: ensure attestation provision signature is correctly sized

Suggested-by: Jordan Mecom (@jmecom) via https://github.com/jmecom/odo

78/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference✓ Names security-relevant behavior explicitly
Why it was queued
signing boundaryupdate trustboot or update path
AI analysis · Moderate 58/100

This update fixes a check in the Blockstream Jade hardware wallet's attestation setup. Before the fix, the code did not verify that an externally-provided signature was small enough to fit into its storage buffer. A too-large signature could overflow that buffer during verification, potentially corrupting memory or crashing the device. The patch adds a size check before calling the signature verification routine.

Security candidateotp: be more strict parsing counter/period.by Jon Griffiths · 2a9b5fb0 · Apr 13, 2026 · 4 filesMessage 76 · AdequateModerate 59Details
Commit message · Jon Griffiths

otp: be more strict parsing counter/period.

Suggested-by: Jordan Mecom (@jmecom) via https://github.com/jmecom/odo

Adds a parse_uint64 to parse decimal unsigned integers.

76/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
authentication path
AI analysis · Moderate 59/100

This commit tightens how Blockstream Jade handles the numbers inside OTP setup URLs (the 'counter' for HOTP codes and the 'period' for TOTP codes). Before the change, the code copied the number into a small temporary buffer and converted it with standard C library functions, which could silently accept non-digit characters, ignore overflow, or be fed an oversized input. The patch adds a strict decimal parser that only accepts digits, rejects values too large for the variable, and enforces length limits. The commit message credits the change to an external suggestion, but does not call it a security fix.

Security candidateui: fix stack overflow in gui task when verifiing a bip85 mnemonicby Daniel Newton · 114c180e · Mar 23, 2026 · 1 fileMessage 55 · ThinModerate 58Details
Commit message · Daniel Newton

ui: fix stack overflow in gui task when verifiing a bip85 mnemonic

55/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Names security-relevant behavior explicitly! No meaningful explanatory body
Why it was queued
memory safety
AI analysis · Moderate 58/100

This commit increases the stack memory given to the device's on-screen user-interface task. The change is described as fixing a 'stack overflow' that could happen while verifying a special backup phrase called a 'BIP85 mnemonic.' A stack overflow in the screen task could crash the user interface or, in the worst case, be abused to disrupt the device during a sensitive wallet operation.

Security candidateotp: parse google authenticator export qr codesby Daniel Newton · e3933c80 · Mar 13, 2026 · 4 filesMessage 60 · AdequateLow 36Details
Commit message · Daniel Newton

otp: parse google authenticator export qr codes

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

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

This commit adds the ability for the Blockstream Jade hardware wallet to read Google Authenticator's bulk-export QR codes (the 'otpauth-migration://' format). It converts those exported codes back into normal OTP URIs and registers them. The change is a feature addition, not a documented security fix. Because it parses an external, attacker-controllable protobuf payload and builds URIs from it, there is some potential for parsing bugs or malformed data to cause crashes or unexpected behavior, but the commit itself does not obviously introduce a known vulnerability.

Security candidatedeps: add google-otpauth-migrateby Daniel Newton · 9ab9f070 · Mar 13, 2026 · 11 filesMessage 45 · ThinInformational 17Details
Commit message · Daniel Newton

deps: add google-otpauth-migrate

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

This commit adds a new software component to the Blockstream Jade hardware wallet project. The component is a copy of the nanopb library plus generated code for parsing Google's OTP (one-time password) migration format. It is a dependency addition only: there is no actual user-facing feature or change to how secrets are handled in this commit. On its own, it does not fix or introduce a security vulnerability.

Security candidateutils: add bin_to_base32, move base32_to_bin and add support for paddingby Daniel Newton · 701542b0 · Mar 13, 2026 · 3 filesMessage 65 · AdequateInformational 21Details
Commit message · Daniel Newton

utils: add bin_to_base32, move base32_to_bin and add support for padding

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
Why it was queued
authentication path
AI analysis · Informational 21/100

This commit refactors how Blockstream Jade handles Base32-encoded one-time-password (OTP) secrets. It moves the Base32 decoder into a shared utility, adds a new encoder, and makes padding characters ('=') stop decoding instead of being rejected. The change is a routine code cleanup; there is no direct evidence in the commit that it fixes an active security vulnerability.

Security candidateotp: wipe and don't log the otp secretby Jon Griffiths · 9f652e85 · Mar 13, 2026 · 1 fileMessage 60 · AdequateModerate 59Details
Commit message · Jon Griffiths

otp: wipe and don't log the otp secret

Remove the sanity check which is already handled by base32_to_bin().

60/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
Why it was queued
authentication path
AI analysis · Moderate 59/100

This commit fixes two security hygiene issues in the handling of one-time password (OTP) secrets in Blockstream Jade. First, it stops writing the raw OTP secret into device logs when decoding fails. Second, it marks the temporary memory buffer holding the decoded secret as sensitive so it is wiped after use rather than left behind. The change also removes a redundant size check because another function already performs it. There is no evidence in the commit of an active exploit or a reported incident.

Security candidateotp: added intermediate options screen for otp detailsby Austin-Fulbright · 8af72c79 · Mar 13, 2026 · 3 filesMessage 65 · AdequateInformational 15Details
Commit message · Austin-Fulbright

otp: added intermediate options screen for otp details

Co-authored-by: Daniel Newton <dnewton@blockstream.com>

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

This commit adds a new intermediate menu screen for one-time password (OTP) entries in the Blockstream Jade hardware wallet. When a user views an OTP, they now see a menu with 'View' and 'Export' options. The 'Export' button currently just shows a placeholder message saying the feature is not implemented yet. There is no security-relevant change in this commit.

Security candidateotp: avoid pow() when computing the otp moduloby Jon Griffiths · 4bee2b18 · Mar 13, 2026 · 1 fileMessage 45 · ThinLow 35Details
Commit message · Jon Griffiths

otp: avoid pow() when computing the otp modulo

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

This commit changes how a one-time passcode (OTP) is shortened to the requested number of digits. Previously the code used the floating-point math function pow() to compute 10^digits, which can introduce tiny rounding errors. Now it uses fixed integer constants (1,000,000 for 6 digits and 100,000,000 for 8 digits). The change removes a potential source of incorrect OTP values and also drops an unnecessary math-library dependency, but the commit message does not frame it as a security fix.

Security candidateui: add a better UI for index selection vs PIN entryby Daniel Newton · c78995b6 · Mar 13, 2026 · 9 filesMessage 73 · AdequateInformational 20Details
Commit message · Daniel Newton

ui: add a better UI for index selection vs PIN entry

Allow entering just the number required when entering indices rather
than having to populate all digits including leading zeros.

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
access controlauthentication path
AI analysis · Informational 20/100

This commit is a user-interface refactor for the Blockstream Jade hardware wallet. It replaces a PIN-only digit-entry screen with a shared 'digit entry' widget that can also accept shorter numeric indices (for things like BIP85 child mnemonic indexes or account indexes). The PIN entry behavior itself is preserved: PINs still require all six digits. The main functional change is that index entry can now be shorter than six digits, which is a usability improvement rather than a security fix. There is no vendor statement that this change addresses a security vulnerability.

Security candidategui: special case for swap recovey in bip85 UIby Daniel Newton · e108d7bb · Mar 4, 2026 · 1 fileMessage 45 · ThinLow 30Details
Commit message · Daniel Newton

gui: special case for swap recovey in bip85 UI

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

This commit changes the on-screen confirmation message shown to users when a specific BIP85 entropy export is requested. Normally the device warns that it is exporting an encrypted seed phrase for a specific BIP85 index. For the exact combination of a 12-word seed phrase at index 26589, the device instead shows a friendly 'Scan successful! Continue to pair with wallet app.' message under the title 'Enable Swaps'. The underlying cryptographic operation is unchanged; only the user-facing text is different. This could mislead users about what is actually being exported, but it does not by itself bypass the user's approval button press.

Security candidatepinserver: update to latest masterby Jon Griffiths · 3aae124f · Feb 20, 2026 · 1 fileMessage 45 · ThinInformational 0Details
Commit message · Jon Griffiths

pinserver: update to latest master

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

This commit is described as updating a submodule or external dependency called 'pinserver' to the latest master version. No actual code diff was provided, and there are no verified references explaining what changed in the pinserver update. Based only on the supplied materials, we cannot determine whether this update fixes a security issue, adds a feature, or is routine maintenance.

Security candidateci: remove pin files on test completionby Jon Griffiths · 0ad5e6f7 · Feb 20, 2026 · 1 fileMessage 67 · AdequateInformational 17Details
Commit message · Jon Griffiths

ci: remove pin files on test completion

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
access control
AI analysis · Informational 17/100

This change cleans up temporary '.pin' test files after automated tests finish. It is a minor hygiene improvement in test code, not a fix for an exploitable product vulnerability. There is no indication these leftover files create meaningful security risk in normal use.

Security candidatesign_psbt: add 2of3 recovery path comment for is_green_multisig_signersby Mihailo Milenkovic · 34f3d162 · Feb 2, 2026 · 1 fileMessage 50 · ThinInformational 15Details
Commit message · Mihailo Milenkovic

sign_psbt: add 2of3 recovery path comment for is_green_multisig_signers

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

This commit only adds a code comment explaining an existing limitation in how Blockstream Jade detects Green multisignature transactions. No code behavior changes. The comment documents that for a specific 2-of-3 recovery wallet setup, the device may skip extra Green-specific validation and fall back to treating the transaction as a standard 2-of-3 multisig, but signing still works correctly.

Security candidatetests: add green 2of3 recovery signing by recovery key (full path from master key)by Mihailo Milenkovic · 6779fc7a · Feb 2, 2026 · 2 filesMessage 75 · AdequateInformational 5Details
Commit message · Mihailo Milenkovic

tests: add green 2of3 recovery signing by recovery key (full path from master key)

Test case for the situation described in the previous commit, showing
that the transaction is correctly signed.

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 boundarysigning or wallet path
AI analysis · Informational 5/100

This commit only adds a new test case and updates a description of an existing test. It does not change any production code. The new test documents that when a recovery key is provided with a full derivation path (from the master key), a Blockstream Jade device will still sign the transaction, but a helper function called is_green_multisig_signers() will return false, meaning some extra Green 2of3 validation is skipped. Because no actual signing logic is changed, this commit by itself is not a security fix or vulnerability.

Security candidatewallet: allow skipping leading 'm' when converting bip32 pathsby Jon Griffiths · d64ade24 · Feb 2, 2026 · 9 filesMessage 50 · ThinInformational 18Details
Commit message · Jon Griffiths

wallet: allow skipping leading 'm' when converting bip32 paths

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

This commit changes a helper function that turns numeric Bitcoin key paths (like 0/1/2) into human-readable text. It adds an option to leave off the leading 'm/' so callers that only want the raw path can get it. All existing callers are updated to keep the old behavior (with the 'm/'), so there is no immediate change in behavior. It appears to be a code cleanup or preparation for a future feature rather than a fix for an active security problem.

Security candidateattestation: add status, battery charging/volts to 'get_version_info' RPCby Daniel Newton · cc3fb705 · Feb 2, 2026 · 5 filesMessage 50 · ThinInformational 13Details
Commit message · Daniel Newton

attestation: add status, battery charging/volts to 'get_version_info' RPC

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

This commit simply adds more information to an existing device status report (the 'get_version_info' RPC). It now reports whether tamper-evident attestation is active, the battery voltage, and whether the battery is charging. There is no change to security logic, access control, or cryptography. It is a routine telemetry/informational enhancement.

Security candidatetests: add test for a green 2of3 psbt with jade as the recovery key signerby Mihailo Milenkovic · 2d9c0a4c · Feb 2, 2026 · 1 fileMessage 60 · AdequateInformational 15Details
Commit message · Mihailo Milenkovic

tests: add test for a green 2of3 psbt with jade as the recovery key signer

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

This commit only adds a new test data file containing a sample Bitcoin transaction (PSBT) for a multi-signature wallet scenario. It does not change any actual wallet code, cryptography, or security logic. There is no indication of a vulnerability or security fix.

Security candidateattestation: misc cleanupsby Jon Griffiths · 4d782bf8 · Feb 2, 2026 · 1 fileMessage 75 · AdequateLow 42Details
Commit message · Jon Griffiths

attestation: misc cleanups

- fix SENSITIVE_POP in attestation_initialise()
- fix attestation_can_be_initialised() with CONFIG_DEBUG_MODE
- avoid uneeded reloads of attestation data
- ensure keys are always initialized before being freed
- allocate attestation data on the heap to avoid stack overflow

Co-authored-by: Daniel Newton <dnewton@blockstream.com>

75/100 · AdequateMessage clarity
✓ Descriptive subject✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Names security-relevant behavior explicitly
Why it was queued
update trustmemory safetyboot or update path
AI analysis · Low 42/100

This commit is a cleanup of the device attestation code in Blockstream Jade, which is the cryptographic proof that the device is genuine. The changes fix a memory-management bug where sensitive key data could be cleared in the wrong order, correct a logic issue when debug mode is enabled, avoid repeatedly reloading attestation data from storage, ensure cryptographic keys are initialized before being freed, and move a large attestation data structure from the stack to the heap to prevent a possible stack overflow. Most changes are defensive hardening, but the SENSITIVE_POP ordering and the debug-mode logic fix are genuine security-relevant corrections.

Security candidatebuild: add support for jade core/v2.0cby Daniel Newton · 6e788ed0 · Feb 2, 2026 · 30 filesMessage 57 · ThinInformational 15Details
Commit message · Daniel Newton

build: add support for jade core/v2.0c

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

This commit adds support for a new hardware variant called Jade Core (jade_v2c), which is a Jade Plus device without a camera or battery. The changes are purely build, configuration, release-script, and documentation updates to recognize the new board type. There is no indication of any security vulnerability being fixed or introduced.

Security candidatepsbt: rename key_index to found_index in key_iter_next for better code readingby Mihailo Milenkovic · 6e3ac474 · Feb 2, 2026 · 1 fileMessage 50 · ThinInformational 15Details
Commit message · Mihailo Milenkovic

psbt: rename key_index to found_index in key_iter_next for better code reading

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

This commit is a pure variable rename inside a single function. The local variable `key_index` is renamed to `found_index` to make the code easier to read. No logic, behavior, or security properties change.

Security candidatepin: create the pin private key on demandby Jon Griffiths · 46e09b14 · Feb 2, 2026 · 4 filesMessage 50 · ThinLow 35Details
Commit message · Jon Griffiths

pin: create the pin private key on demand

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 materialaccess controlauthentication path
AI analysis · Low 35/100

This commit moves when a special device private key (used for PIN server authentication) is created. Previously it was generated at every boot if missing; now it is created only when actually needed during a PIN operation. This is a code-quality and reliability change that reduces unnecessary key creation at startup, but it does not appear to fix an active security vulnerability.