BS
← All projectsBlockstream

Blockstream Jade

Firmware for Jade and Jade Plus Bitcoin hardware wallets.

BitcoinHardware walletsElevated watch
Repository coverage

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

93security candidates58second-pass queue75AI analyses
10commits · 30 days
67commits · 60 days
198commits · 180 days
414commits · 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
147Adequate · 60–79
203Thin · 40–59
32Opaque · 0–39
3security 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 Griffiths2755242157
Mike Tolkachev311110155
Daniel Newton651510055
Mihailo Milenkovic877057
Jamie C. Driver522053
Gustavo Cateim711079
Austin-Fulbright410060
roderico111045
quantpoet111072
tokyovyse110063
cmiguelrn111045
odudex200071
Analysis record

Published AI watches

Last scanned 21 minutes ago

Low 27 AI analysisMessage 86 · Strong
BS BlockstreamBlockstream Jade BitcoinHardware wallets

input: release touch handles before deleting the i2c bus

This commit fixes a bug where the touchscreen driver failed to clean up internal handles when shutting down. On newer ESP-IDF firmware, this cleanup failure caused the device to panic and freeze during boot and when using the camera or QR …

Device freeze/DoS-like symptom on affected hardwareMemory leak fixedNo input validation, authentication, or cryptographic weakness visible
36776fecby Gustavo Cateim+3−01 file
No security note in commit
Low 42 AI analysisMessage 95 · Strong
BS BlockstreamBlockstream Jade BitcoinHardware wallets

Liquid (taproot): add sign_liquid_tx genesis blockhash support

This commit changes how Blockstream Jade handles the 'genesis blockhash' when signing Liquid transactions. Previously, the device only accepted the network's built-in genesis hash. Now it lets users provide a custom genesis hash for test n…

Adds input validation for caller-supplied genesis blockhashPrevents mainnet genesis hash from being used on Liquid test networksRestricts genesis_hash parameter to Liquid networks only
888eff30by Jon Griffiths+82−264 files
No security note in commit
Informational 15 AI analysisMessage 45 · Thin
BS BlockstreamBlockstream Jade BitcoinHardware wallets

rpc: rename get_boolean to get_bool

This commit is a simple rename of two internal helper functions from `rpc_get_boolean`/`rpc_get_boolean_or` to `rpc_get_bool`/`rpc_get_bool_or`, updating all call sites accordingly. There is no change to what the code does, no bug fix, and…

f6e946acby Jon Griffiths+24−2518 files
No security note in commit
Informational 15 AI analysisMessage 50 · Thin
BS BlockstreamBlockstream Jade BitcoinHardware wallets

rpc: refactor app code to use getters with default values

This commit is a straightforward code cleanup that replaces verbose 'read this optional value, or leave the default' patterns with shorter helper functions that do the same thing. There is no change in behavior and no security issue visibl…

b6a07147by Mike Tolkachev+22−348 files
No security note in commit
Informational 15 AI analysisMessage 45 · Thin
BS BlockstreamBlockstream Jade BitcoinHardware wallets

Fix M5StickC Plus 2 PIN navigation

This commit fixes a user-interface navigation quirk on the M5StickC Plus 2 hardware for Blockstream Jade. When entering a PIN, the up/down button directions were not inverted to match the rest of the device's menus, making number entry con…

9de1409eby roderico+3−21 file
No security note in commit
Low 36 AI analysisMessage 74 · Adequate
BS BlockstreamBlockstream Jade BitcoinHardware wallets

build: annotate functions returning error codes to ensure they are checked

This commit is a preventive build-hardening change. It adds compiler annotations (WARN_UNUSED_RESULT) to many functions that return success/failure codes, so the compiler will warn if a caller ignores the result. The goal is to catch futur…

Compiler annotation added to enforce checking of error-returning functionsNo specific vulnerability fixed in the diffNo functional code changes or call-site fixes included
909a89aaby Mike Tolkachev+215−15225 files
No security note in commit
Low 42 AI analysisMessage 28 · Opaque
BS BlockstreamBlockstream Jade BitcoinHardware wallets

psbt: fix path size

This commit fixes a small but meaningful bug in how Jade, a hardware wallet, reads key paths from Bitcoin PSBT data. The code was passing the byte size of a buffer when it should have passed the number of 32-bit entries. Depending on how t…

Buffer-size semantic mismatch in security-critical PSBT parsingUse of sizeof() on uint32_t array where element count is expectedCode path involved in 2of3 multisig recovery key identification
9e0c3747by Mike Tolkachev+2−21 file
No security note in commit
Moderate 59 AI analysisMessage 50 · Thin
BS BlockstreamBlockstream Jade BitcoinHardware wallets

sign_psbt: add early reject on wrong genesis blockhash

This commit fixes a bug in the Blockstream Jade hardware wallet's PSBT (Partially Signed Bitcoin Transaction) signing code. Previously, when the transaction's genesis block hash did not match the expected network, the code set an error mes…

Missing return in error path allows execution to continue after validation failureCross-network genesis hash mismatch not enforced as a hard failurePSBT signing logic accepts mismatched network parameters
56e130b0by Mike Tolkachev+1−01 file
No security note in commit
Low 42 AI analysisMessage 45 · Thin
BS BlockstreamBlockstream Jade BitcoinHardware wallets

main: fix error handling during PIN change

This commit fixes a bug in the PIN-change flow on Blockstream Jade hardware wallets. Previously, if re-encrypting the wallet keys with a new PIN failed, or if the user abandoned the PIN change, the code did not jump to cleanup as intended.…

Missing error-path control flow in cryptographic key handlingPotential use of stale or partially initialized key material after PIN-change failureCleanup bypass in sensitive authentication code path
64c30823by Mike Tolkachev+2−01 file
No security note in commit
Moderate 59 AI analysisMessage 50 · Thin
BS BlockstreamBlockstream Jade BitcoinHardware wallets

attestation: harden error handling of challenge signing

This commit fixes a bug in the Blockstream Jade hardware wallet's attestation signing process. Previously, if signing the attestation challenge failed, the device would send an error message but then continue running the rest of the functi…

Missing return after error path allows fall-through to success-path replyUninitialized output.ext_signature_len could leak stack data or cause undefined behaviorAttestation signing failure could result in sending an invalid attestation reply
ecc5871bby Mike Tolkachev+2−01 file
No security note in commit
Low 39 AI analysisMessage 50 · Thin
BS BlockstreamBlockstream Jade BitcoinHardware wallets

attestation: fix missing cleanup on failed efuse write

This commit fixes a small but real bug in the device attestation setup code for Blockstream Jade, a hardware crypto wallet. When a one-time programmable security fuse failed to burn, the code used to exit immediately without releasing memo…

Missing cleanup on error path in security-critical initializationResource leak on failed efuse writePotential inconsistent attestation state after partial initialization
d37d88b7by Mike Tolkachev+1−11 file
No security note in commit
Moderate 59 AI analysisMessage 77 · Adequate
BS BlockstreamBlockstream Jade BitcoinHardware wallets

wallet: fix unhandled wrong asset in wallet summaries

This commit fixes a bug in the Blockstream Jade hardware wallet where a function that tracks assets during transaction signing could fail silently. Previously, if an unexpected or wrong asset was encountered while building a summary of tra…

Unchecked return value from asset_summary_update() in signing pathPotential bypass of asset/balance validation during transaction signingWrong or unknown asset could be silently dropped from wallet summaries
b33cf02bby Mike Tolkachev+18−53 files
No security note in commit
Moderate 59 AI analysisMessage 85 · Strong
BS BlockstreamBlockstream Jade BitcoinHardware wallets

sign: update output logic, rename and document output flags for clarity

This commit reworks how a Blockstream Jade hardware wallet labels transaction outputs. The key change is that the 'change' flag is now only set when the output is also confirmed as belonging to the wallet ('is ours'). Previously, downstrea…

Change output flag now gated by wallet-ownership flagUI hides change outputs based on single bit with runtime assertionGreen 2of3 outputs no longer marked as change because not marked as wallet-owned
cf79a3aaby Mike Tolkachev+32−245 files
Vendor flagged security relevance
Moderate 57 AI analysisMessage 58 · Thin
BS BlockstreamBlockstream Jade BitcoinHardware wallets

esp-idf: update to v5.5.4, take multisig bootloader component from https://github.com/Blockstream/esp-idf/tree/securebootv2_multisig_v5.5.4

This is a large update that pulls in Espressif's ESP-IDF v5.5.4 bootloader code, plus Blockstream's own multi-signature secure-boot patches. Most of the visible changes are routine: support for newer ESP32 chips, larger flash sizes, and a …

Anti-fault-injection assertion (ESP_FAULT_ASSERT) added around TEE flash address validationTEE flash write/erase now rejects operations targeting the active TEE partition rangeSecure Boot V2 extended to support ECDSA-P384 / SHA-384 digests
d931d543by Daniel Newton+3879−1437104 files
No security note in commit
High 72 AI analysisMessage 85 · Strong
BS BlockstreamBlockstream Jade BitcoinHardware wallets

sign_tx: suppress validation/change attribution for green 2of3 outputs

This update fixes a security gap in how Blockstream Jade signs Bitcoin transactions for a specific wallet type called Green 2of3. Previously, the device trusted the connected app to supply a recovery public key and might silently treat an …

Host-supplied recovery_xpub was trusted for change attributionChange output could be misattributed without user confirmationFix suppresses automatic validation for Green 2of3 outputs
0243f239by Mike Tolkachev+17−11 file
Vendor flagged security relevance
Informational 15 AI analysisMessage 45 · Thin
BS BlockstreamBlockstream Jade BitcoinHardware wallets

ui: tidy up message/error activities

This commit is a straightforward code cleanup. It replaces a verbose way of showing on-screen messages and errors with simpler helper functions, and fixes a spelling mistake ('re-encypt' to 're-encrypt'). There is no change to security log…

No security-relevant logic changesRefactoring only: API simplification for UI message displaySpelling correction in user-facing error string
1914ace0by Daniel Newton+162−24625 files
No security note in commit
Low 25 AI analysisMessage 60 · Adequate
BS BlockstreamBlockstream Jade BitcoinHardware wallets

wire: reduce stack usage sending replies

This commit changes how message context is passed between functions in the Blockstream Jade hardware wallet firmware. Instead of copying the entire message context structure on the stack, functions now receive a pointer to it. The stated g…

Stack usage reduction in embedded firmwarePointer passing instead of structure copyingNo direct vulnerability described in commit message
c41f5fddby Jon Griffiths+65−6429 files
No security note in commit
Informational 24 AI analysisMessage 45 · Thin
BS BlockstreamBlockstream Jade BitcoinHardware wallets

rpc: add show_bip85_bip39_entropy RPC command

This commit adds a new device command that lets a connected computer or phone ask a Blockstream Jade hardware wallet to display an encrypted BIP85 seed-entropy backup as a QR code. The change also tightens validation of the BIP32 index in …

New RPC exposes encrypted BIP85 entropy via on-device QR displayBIP32 index bounds checks added in multiple RPC parameter parsersSensitive stack buffers now marked with SENSITIVE_PUSH/POP in QR reply path
3392661cby Daniel Newton+115−277 files
No security note in commit
Informational 15 AI analysisMessage 62 · Adequate
BS BlockstreamBlockstream Jade BitcoinHardware wallets

docs: add show_bip85_bip39_entropy RPC documentation

This commit only adds documentation for an existing RPC command called show_bip85_bip39_entropy. It does not change any code, so it cannot introduce or fix a security vulnerability by itself.

2e829638by Daniel Newton+37−01 file
No security note in commit
Moderate 57 AI analysisMessage 50 · Thin
BS BlockstreamBlockstream Jade BitcoinHardware wallets

psbt: always confirm green outputs when recovery signing

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

Logic inversion in authorization/confirmation pathRecovery-key signing path previously trusted Green-classified outputs without user confirmationComment explicitly frames change around inability to verify output ownership in recovery path
a963f628by Jon Griffiths+2−21 file
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-prioritybuild: update jade_builder image referencesby Daniel Newton · 4ee1ffa2 · May 15, 2026 · 4 filesMessage 57 · ThinTriage 0Details
Commit message · Daniel Newton

build: update jade_builder image references

57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Lower-prioritytools: esp32 move OS functions to flash from IRAM when wifi logging onby Daniel Newton · 8330ce0e · May 15, 2026 · 1 fileMessage 50 · ThinTriage 0Details
Commit message · Daniel Newton

tools: esp32 move OS functions to flash from IRAM when wifi logging on

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-priorityjadepy: update setup.py install depsby Jon Griffiths · 52ab757c · May 15, 2026 · 1 fileMessage 45 · ThinTriage 0Details
Commit message · Jon Griffiths

jadepy: update setup.py install deps

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Security candidatesign_tx: suppress validation/change attribution for green 2of3 outputsby Mike Tolkachev · 0243f239 · May 15, 2026 · 1 fileMessage 85 · StrongHigh 72Details
Commit message · Mike Tolkachev

sign_tx: suppress validation/change attribution for green 2of3 outputs

Since the recovery xpub is not currently registered on-device, we should
not trust the caller provided value, and users must validate the address
on-device. A malicious companion app could otherwise swap out the
recovery xpub to grief the user.

This brings sign_tx behaviour in line with sign_psbt for Green 2of3.

A future update will allow user-confirmed registration for Green 2of3
which will allow skipping the confirmation for these outputs.

85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode
Why it was queued
signing boundarydefensive validationsigning or wallet path
AI analysis · High 72/100

This update fixes a security gap in how Blockstream Jade signs Bitcoin transactions for a specific wallet type called Green 2of3. Previously, the device trusted the connected app to supply a recovery public key and might silently treat an output as 'change' going back to the user's own wallet. A malicious or compromised companion app could have supplied a fake recovery key, tricking the device into marking a payment to an attacker's address as safe internal change. The fix forces the user to manually verify such outputs on the device screen instead of trusting the app, matching the behavior already used for PSBT signing.

AI review queuedjadepy: update jadepy releaseby Jon Griffiths · cdcebe8f · May 15, 2026 · 2 filesMessage 35 · OpaqueTriage 0Details
Commit message · Jon Griffiths

jadepy: update jadepy release

35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
Lower-priorityjade_cli: add required arguments to sign_txby Valerio Vaccaro · dd481eec · May 14, 2026 · 1 fileMessage 45 · ThinTriage 0Details
Commit message · Valerio Vaccaro

jade_cli: add required arguments to sign_tx

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Security candidateui: tidy up message/error activitiesby Daniel Newton · 1914ace0 · May 4, 2026 · 25 filesMessage 45 · ThinInformational 15Details
Commit message · Daniel Newton

ui: tidy up message/error activities

Fix spelling of "re-encrypt".

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

This commit is a straightforward code cleanup. It replaces a verbose way of showing on-screen messages and errors with simpler helper functions, and fixes a spelling mistake ('re-encypt' to 're-encrypt'). There is no change to security logic, no bug fix, and no vulnerability addressed.

Lower-prioritybuild: move production config directory into the configs directoryby Daniel Newton · be7f66d2 · May 1, 2026 · 9 filesMessage 62 · AdequateTriage 0Details
Commit message · Daniel Newton

build: move production config directory into the configs directory

62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Lower-priorityci: add security stageby Valerio Vaccaro · 98f87312 · May 1, 2026 · 2 filesMessage 45 · ThinTriage 0Details
Commit message · Valerio Vaccaro

ci: add security stage

45/100 · ThinMessage clarity
✓ Subject identifies a change✓ Uses a recognizable type or scope✓ Names security-relevant behavior explicitly! No meaningful explanatory body
Lower-priorityfonts: speed up/simplify fetching glyph databy Jon Griffiths · f4d99d26 · May 1, 2026 · 1 fileMessage 68 · AdequateTriage 0Details
Commit message · Jon Griffiths

fonts: speed up/simplify fetching glyph data

Note that glyph looking is still O(N), and thus string length
calculation and display is O(N^2). This commit merely makes the existing
linear lookup faster.

The linear lookup is a consequence of the font structure allowing
characters to be out of order. If we were to force the characters to be
ordered in the font definition we could trivially implement an index
to allow even faster lookups.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Lower-prioritytools: remove jade_capture_image_data.py since jade_cli can do this nowby Jon Griffiths · 5a8b6c59 · May 1, 2026 · 1 fileMessage 50 · ThinTriage 0Details
Commit message · Jon Griffiths

tools: remove jade_capture_image_data.py since jade_cli can do this now

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-priorityfonts: simplify font settingby Jon Griffiths · d42f01da · May 1, 2026 · 3 filesMessage 58 · ThinTriage 0Details
Commit message · Jon Griffiths

fonts: simplify font setting

Note that data such as the maximum character width, computed when each font
is set could be computed at compile time, or cached when first set.

58/100 · ThinMessage clarity
✓ Descriptive subject✓ Provides detailed explanatory context
Lower-priorityfonts: remove unused inverted fontsby Jon Griffiths · e5a39e15 · May 1, 2026 · 3 filesMessage 45 · ThinTriage 0Details
Commit message · Jon Griffiths

fonts: remove unused inverted fonts

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-prioritywire: make ble message handling use the same logic as other inputsby Jon Griffiths · 52227215 · May 1, 2026 · 7 filesMessage 73 · AdequateTriage 0Details
Commit message · Jon Griffiths

wire: make ble message handling use the same logic as other inputs

The ble logic was the only user of reject_incomplete, which it used to
process existing buffer data inconsistently.

Now that all handlers use the same logic we can investigate strategies
for attempting to re-sync message streams when an error occurs.

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Lower-prioritytests: re-enable large qr code tests for 1.1 devicesby Jon Griffiths · fd52cfaf · May 1, 2026 · 1 fileMessage 83 · StrongTriage 0Details
Commit message · Jon Griffiths

tests: re-enable large qr code tests for 1.1 devices

Now that we allow processing of valid data receieved after a timeout, the
occasional write-level split of the input qr data shouldn't cause this
test any issues.

83/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Lower-prioritytests: test splitting the write for concatenated messagesby Jon Griffiths · ab0c6d07 · May 1, 2026 · 1 fileMessage 60 · AdequateTriage 0Details
Commit message · Jon Griffiths

tests: test splitting the write for concatenated messages

60/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
Lower-prioritywire: refactor handle_message, enable all message tests for libjadeby Jon Griffiths · c89a51e3 · May 1, 2026 · 2 filesMessage 83 · StrongTriage 0Details
Commit message · Jon Griffiths

wire: refactor handle_message, enable all message tests for libjade

Require any candidate message be a valid map up-front since this is a
prerequisite for the message to be a valid RPC message.

Ignore reject_incomplete which will be removed in an upcoming commit.

Note we continue to attempt to parse including new data that has arrived
after the timeout before discarding stale data.

83/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Lower-prioritytests: enable "too much input" test for libjadeby Jon Griffiths · 296e4774 · May 1, 2026 · 1 fileMessage 55 · ThinTriage 0Details
Commit message · Jon Griffiths

tests: enable "too much input" test for libjade

55/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
Lower-prioritywire: merge handle_data()/handle_data_impl()by Jon Griffiths · cbda68b4 · May 1, 2026 · 1 fileMessage 50 · ThinTriage 0Details
Commit message · Jon Griffiths

wire: merge handle_data()/handle_data_impl()

No functional changes; removes a couple of now-redundant asserts.

50/100 · ThinMessage clarity
✓ Descriptive subject✓ Provides an explanatory body
Security candidatewire: reduce stack usage sending repliesby Jon Griffiths · c41f5fdd · May 1, 2026 · 29 filesMessage 60 · AdequateLow 25Details
Commit message · Jon Griffiths

wire: reduce stack usage sending replies

This offsets the increased stack usage from the previous commit.

60/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
Why it was queued
seed or entropy pathsigning or wallet pathboot or update pathauthentication path
AI analysis · Low 25/100

This commit changes how message context is passed between functions in the Blockstream Jade hardware wallet firmware. Instead of copying the entire message context structure on the stack, functions now receive a pointer to it. The stated goal is to reduce stack memory usage. There is no direct evidence in the commit that this fixes an exploitable vulnerability, but reducing stack pressure can help prevent stack overflow crashes or corruption in a security-critical embedded device.

Lower-prioritylibjade: handle received bytes in the same way as the serial deviceby Jon Griffiths · df99d865 · May 1, 2026 · 1 fileMessage 83 · StrongTriage 0Details
Commit message · Jon Griffiths

libjade: handle received bytes in the same way as the serial device

Send all bytes through handle_data(), in chunks if required.

This allows testing the real world comms behaviour using libjade,
with the exception that BLE message handling is currently different
to both (and arguably incorrect).

83/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Lower-prioritywire: remove transport specific output buffersby Jon Griffiths · e682ecfc · May 1, 2026 · 6 filesMessage 68 · AdequateTriage 0Details
Commit message · Jon Griffiths

wire: remove transport specific output buffers

These are only ever used to reject messages which can be done with a
temporary ~128 bytes of stack instead of a permanent 3-9kb of RAM.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Lower-prioritywire: fix not processing all received data when wire.c timeout hitby Daniel Newton · fa76e536 · May 1, 2026 · 6 filesMessage 65 · AdequateTriage 0Details
Commit message · Daniel Newton

wire: fix not processing all received data when wire.c timeout hit

Minor code cleanup to make the existing logic clearer.

65/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
Lower-prioritytests: allow qemu tests to run longerby Jon Griffiths · 21aceccc · May 1, 2026 · 1 fileMessage 55 · ThinTriage 0Details
Commit message · Jon Griffiths

tests: allow qemu tests to run longer

55/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
Lower-priorityqemu: fix outdated scripts/documenationby Daniel Newton · 9cfc58fb · May 1, 2026 · 8 filesMessage 45 · ThinTriage 0Details
Commit message · Daniel Newton

qemu: fix outdated scripts/documenation

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