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 35 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 candidateprocess: whitelist reply message function callsby Jon Griffiths · a59d14c2 · Oct 22, 2026 · 13 filesMessage 45 · ThinModerate 57Details
Commit message · Jon Griffiths

process: whitelist reply message function calls

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
seed or entropy pathsigning or wallet pathboot or update path
AI analysis · Moderate 57/100

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 malicious code path to craft unexpected replies. Now only a specific list of known-safe reply-building functions is accepted. The change is defensive hardening rather than a clear fix for an active attack.

Lower-priorityprocess: whitelist inbound message writer function callsby Jon Griffiths · 626423c8 · Oct 22, 2026 · 1 fileMessage 50 · ThinTriage 0Details
Commit message · Jon Griffiths

process: whitelist inbound message writer function calls

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-priorityprocess: whitelist outbound message writer function callsby Jon Griffiths · 044d56bb · Oct 22, 2026 · 6 filesMessage 50 · ThinTriage 0Details
Commit message · Jon Griffiths

process: whitelist outbound message writer function calls

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI review queuedtemporary_stack: whitelist temporary task function callsby Jon Griffiths · 6a0fea51 · Oct 22, 2026 · 4 filesMessage 30 · OpaqueLow 42Details
Commit message · Jon Griffiths

temporary_stack: whitelist temporary task function calls

30/100 · OpaqueMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body! Contains work-in-progress language
Why it was queued
signing or wallet pathsecond-pass: opaque commit messagesecond-pass: security-sensitive path
AI analysis · Low 42/100

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 internal self-tests. This reduces the chance that an attacker could trick the device into running unexpected code with a larger stack, which could cause crashes or be exploited. It is a hardening change rather than a clear fix for a known active attack.

Lower-prioritygui: whitelist gui updatables function callsby Jon Griffiths · c14652a8 · Oct 22, 2026 · 1 fileMessage 45 · ThinTriage 0Details
Commit message · Jon Griffiths

gui: whitelist gui updatables function calls

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Security candidateconsistency: fix typosby Jon Griffiths · 251f7713 · Oct 22, 2026 · 40 filesMessage 43 · ThinInformational 15Details
Commit message · Jon Griffiths

consistency: fix typos

Almost entirely comments; one user visible RPC error message,
"User abandonded pin entry".

43/100 · ThinMessage clarity
✓ Subject identifies a change✓ Provides an explanatory body
Why it was queued
access controlsigning or wallet pathauthentication path
AI analysis · Informational 15/100

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 cryptographic handling. The only user-visible change is correcting the error message 'User abandonded pin entry' to 'User abandoned pin entry'.

Lower-priorityprocess: whitelist deferred function callsby Jon Griffiths · 74232041 · Oct 22, 2026 · 2 filesMessage 45 · ThinTriage 0Details
Commit message · Jon Griffiths

process: whitelist deferred function calls

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-prioritygui: make test scrolling smoother by changing character to pixel stepby Mike Tolkachev · 335af155 · Oct 14, 2026 · 3 filesMessage 60 · AdequateTriage 0Details
Commit message · Mike Tolkachev

gui: make test scrolling smoother by changing character to pixel step

60/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
Lower-priorityinput: avoid deprecated esp_lcd_touch_get_coordinates() functionby Bota · 6cdc9494 · Oct 14, 2026 · 1 fileMessage 50 · ThinTriage 0Details
Commit message · Bota

input: avoid deprecated esp_lcd_touch_get_coordinates() function

Use esp_lcd_touch_get_data() instead.

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-priorityci: fix btagent callby Valerio Vaccaro · 93366632 · Oct 14, 2026 · 1 fileMessage 40 · ThinTriage 0Details
Commit message · Valerio Vaccaro

ci: fix btagent call

40/100 · ThinMessage clarity
✓ Subject identifies a change✓ Uses a recognizable type or scope! No meaningful explanatory body
Lower-prioritydiy: set INPUT_WHEEL_A/B defaults for M5StickS3by GitHub User · e6a51ab6 · Oct 14, 2026 · 1 fileMessage 68 · AdequateTriage 0Details
Commit message · GitHub User

diy: set INPUT_WHEEL_A/B defaults for M5StickS3

The M5StickS3 custom board config was missing INPUT_WHEEL_A and INPUT_WHEEL_B
defaults, causing CI warnings that these values have no set value. Set both
to -1 (disabled) to match how other custom board configs handle this.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Lower-prioritydescriptor: assert descriptor parsing does not return WALLY_ERRORby Jon Griffiths · 42c2ce93 · Oct 13, 2026 · 1 fileMessage 65 · AdequateTriage 0Details
Commit message · Jon Griffiths

descriptor: assert descriptor parsing does not return WALLY_ERROR

This can only happen when something has gone wrong internally in
wally, so do not continue after this point.

65/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
Lower-prioritybuild: align USB CDC receive FIFO size with endpoint buffer sizeby Mike Tolkachev · 14ea2c04 · Oct 13, 2026 · 13 filesMessage 62 · AdequateTriage 0Details
Commit message · Mike Tolkachev

build: align USB CDC receive FIFO size with endpoint buffer size

62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Security candidatedocs: document get_bip85_bip39_entropyby Jon Griffiths · 05a578ad · Oct 12, 2026 · 2 filesMessage 47 · ThinInformational 15Details
Commit message · Jon Griffiths

docs: document get_bip85_bip39_entropy

47/100 · ThinMessage clarity
✓ Descriptive subject✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
entropy or randomnesssecret or key material
AI analysis · Informational 15/100

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 code behavior change, no bug fix, and no security patch in the diff.

Security candidatebip85: expose get_bip85_bip39_entropy over rpc in addition to qrby Jon Griffiths · c6c5e860 · Oct 12, 2026 · 1 fileMessage 50 · ThinLow 28Details
Commit message · Jon Griffiths

bip85: expose get_bip85_bip39_entropy over rpc in addition to qr

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
entropy or randomnesssecret or key material
AI analysis · Low 28/100

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 available over RPC means wallet software can request derived seed entropy through the standard communication channel, not only via QR codes. There is no direct evidence in the commit that this fixes a security vulnerability; it appears to be a functionality or API-consistency change.

Lower-priorityci: remove constant and testvector not usedby Valerio Vaccaro · 1dbcb48a · Oct 8, 2026 · 1 fileMessage 57 · ThinTriage 0Details
Commit message · Valerio Vaccaro

ci: remove constant and testvector not used

57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Lower-priorityci: remove test covered by mnemonic testsby Valerio Vaccaro · 1ebf4cc5 · Oct 8, 2026 · 1 fileMessage 67 · AdequateTriage 0Details
Commit message · Valerio Vaccaro

ci: remove test covered by mnemonic tests

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
Lower-priorityci: remove unused helper functionsby Valerio Vaccaro · 7f9da73c · Oct 8, 2026 · 1 fileMessage 57 · ThinTriage 0Details
Commit message · Valerio Vaccaro

ci: remove unused helper functions

57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Lower-priorityci: remove test covered by low level testsby Valerio Vaccaro · ca5bad64 · Oct 8, 2026 · 1 fileMessage 67 · AdequateTriage 0Details
Commit message · Valerio Vaccaro

ci: remove test covered by low level tests

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
Security candidateversioninfo: add JADE_INTERFACE field to show which connection source holds the unlocked walletby Daniel Newton · 2fe9df0b · Oct 6, 2026 · 6 filesMessage 50 · ThinInformational 19Details
Commit message · Daniel Newton

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

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

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. There is no change to security rules, authentication, or how wallets are unlocked; it only exposes existing internal state for better visibility.

Lower-priorityui: update icons for bluetoothby Valerio Vaccaro · ce7302bc · Oct 2, 2026 · 3 filesMessage 68 · AdequateTriage 0Details
Commit message · Valerio Vaccaro

ui: update icons for bluetooth

Follow the convention commonly used elsewhere:
- No icon shown at all if BLE is not supported (radio only FW)
- Dark BLE 'B' icon if enabled but not connected
- Light BLE 'B' icon with dots if enabled and connected

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Security candidatesign_tx/sign_psbt: extra check for BTC inputsby Daniel Newton · 41d7e8b4 · Sep 30, 2026 · 2 filesMessage 60 · AdequateLow 44Details
Commit message · Daniel Newton

sign_tx/sign_psbt: extra check for BTC inputs

should be redundant as each amount is bounded by WALLY_SATOSHI_MAX and
inputs at MAX_TX_INPUTS

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

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 transaction pushed the running total above the maximum 64-bit integer value. The patch now uses a checked addition and rejects the transaction if the total would overflow. The commit message says the check 'should be redundant' because each individual input amount and the number of inputs are already bounded, so this is a defensive hardening change rather than a confirmed exploitable bug.

Security candidatebuild: move NVS cache objects that can pin the DRAM heap to SPIRAM if availableby Daniel Newton · 329f73c5 · Sep 30, 2026 · 7 filesMessage 62 · AdequateInformational 19Details
Commit message · Daniel Newton

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

62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
access control
AI analysis · Informational 19/100

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 direct security fix. It may help prevent out-of-memory situations, which can indirectly improve stability, but it does not patch a known vulnerability.

Security candidatetests: migrate pin action tests from test_jade to rpc testsby Mike Tolkachev · be0e6b3d · Sep 30, 2026 · 2 filesMessage 60 · AdequateInformational 15Details
Commit message · Mike Tolkachev

tests: migrate pin action tests from test_jade to rpc tests

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
access controlauthentication path
AI analysis · Informational 15/100

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 PIN-related actions, but those checks already existed before this change.

Lower-prioritydisplay: fix artifacts of partially clipped charactersby Mike Tolkachev · 1a785645 · Sep 30, 2026 · 1 fileMessage 50 · ThinTriage 0Details
Commit message · Mike Tolkachev

display: fix artifacts of partially clipped characters

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