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.
Message quality measures whether a commit identifies its scope, purpose, rationale, testing, and supporting references. It does not change the security-severity score.
36/100 average clarity
10Strong · 80–100
45Adequate · 60–79
195Thin · 40–59
218Opaque · 0–39
42security candidates with opaque commit messaging
This commit tightens how COLDCARD reads PSBTv2 (Partially Signed Bitcoin Transaction version 2) files. It now rejects several malformed or ambiguous encodings that could previously be accepted: extra key data attached to fields that should…
PSBT parser hardeningrejection of non-canonical compact-size encodingsenforcement of singleton key-data emptiness
This commit adds support in the COLDCARD firmware for a newer Bitcoin transaction format feature (PSBTv2) that lets each input specify its own required lock time. Before this change, the device did not correctly compute the final transacti…
PSBTv2 per-input locktime parsing and validation addedBIP-370 required locktime computation implementedIncompatible height/time locktime requirements rejected with assertion
This commit only adds a new automated test to the COLDCARD firmware test suite. The test checks that when a user tries to sign a text file containing valid JSON that is not a JSON object (for example, a plain number, string, null, or list)…
Regression test for input validation of JSON message-signingTest comment explicitly references avoiding a device crash on malformed JSON inputTest requested during review of pull request #808, suggesting prior related code change
This commit is a defensive hygiene fix in the COLDCARD hardware wallet's 'trick PIN' duress-wallet feature. It moves a memory-wipe routine so that it runs before the device looks up the duress wallet slot. The change reduces the window in …
This firmware update fixes a cleanup issue in the COLDCARD wallet's transaction signing code. Before finalizing a new Bitcoin transaction, the device now clears out leftover 'change output' records that may have been captured during a prev…
State not reset between signing attemptsStale change-output metadata reused in transaction finalizationOVC (Output Value Check) validation may be affected by leftover data
This commit removes a human-readable error message from a ValueError exception to reduce the amount of flash storage used by the firmware. It is a minor code cleanup and does not change the security behavior of the code. The function still…
This commit only adds a changelog note saying a previous fix stopped the COLDCARD hardware wallet from crashing when a message-signing request was valid JSON but not a JSON object (for example, a number or string instead of a dictionary). …
Device crash on malformed message-signing inputInput vector includes NFC, QR, and SD card JSON filesValid JSON but wrong type (non-object) bypasses simple format checks
This commit fixes a bug where the COLDCARD firmware's message-signing feature would crash with an uncaught error if a user supplied valid JSON that wasn't a structured object (for example, a plain number, string, list, or null). The fix ch…
uncaught exception in message parsing pathinput validation gap on JSON typepotential denial-of-service via malformed request
This commit only updates the release signature file (signatures.txt) for the COLDCARD firmware. It adds two new file hashes for a v5.6.2-mk release and refreshes the PGP signature covering the file. There are no code changes, no bug fixes,…
This commit only updates a release signature file. It refreshes SHA-256 hashes for changelog files and adds hashes for two new firmware release files, then re-signs the file with a PGP signature. There are no code changes, no bug fixes, an…
This commit simply updates a stored Bitcoin blockchain height number from 965,337 to 965,338. It is a routine, automatically generated data refresh with no code logic changes and no apparent security relevance.
This commit only edits the project's internal release notes file. It replaces a detailed list of upcoming changes with placeholder 'tbd' entries and adds a note asking contributors to leave blank lines between additions. There are no code …
This commit is a release-notes-only update for the COLDCARD hardware wallet firmware. It moves many security-relevant bug fixes and hardening items from the current changelog into the historical release notes for versions 5.6.1 and 1.5.1Q,…
USB protocol encryption upgrade (ncry v3) with direction-separated keys and replay protectionPSBT tampering detection: re-verify staged bytes before signing after Virtual Disk overwriteFirmware update integrity: abort if staged image overwritten, reject images extending past world-checksum region
This commit simply updates a stored Bitcoin blockchain height number from 963,314 to 965,337, along with its timestamp. It is an automatic, routine data refresh with no code logic changes and no apparent security relevance.
This commit fixes a bug in the COLDCARD firmware upgrade process. Previously, if someone tampered with the staged firmware after the user saw the approval prompt but before they confirmed, the device would crash with a bare internal error …
Tamper-detection failure path hardened: assert replaced with user-facing failure storyDefense-in-depth assertion added to PIN-changing flowTest coverage added for tamper-abort message
This commit only updates a linked external code library (a Git submodule called ckcc-protocol) to a newer version. The actual code changes inside that library are not shown in the commit diff, and no security-related information was provid…
This commit only edits the draft release changelog file. It rewords two upcoming feature descriptions and fixes line wrapping for another entry. No source code, firmware logic, or security behavior was changed.
This update fixes a bug where COLDCARD wallets would accept BIP-39 passphrases containing non-ASCII characters (like accented letters or emojis) or non-printable characters. Because different wallet software normalizes such characters diff…
Behavioral fix that prevents silent derivation of incompatible wallet seedsInput validation added for BIP-39 passphrase across USB, UI, saved-passphrase restore, and note/password lanesRejection of non-printable ASCII and non-ASCII Unicode characters
This commit fixes two related security bugs in the COLDCARD hardware wallet's protection against a known 'BIP-143 amount swap' attack. First, the wallet was recording the claimed amount of a segwit input to its secure cache as soon as a tr…
Fixes deferred persistence of UTXO amount cache until after successful signingFixes missing capture of single-sig segwit change outputs (p2wpkh and p2sh-p2wpkh)Prevents cache poisoning by cancelled/malicious PSBT previews
This update fixes a bug in how the COLDCARD wallet reads PSBT files (the standard format for passing Bitcoin transactions between devices). Previously, if a PSBT contained the same special 'singleton' key twice in the same section, the dev…
PSBT parser now rejects duplicate singleton keysNew test cases for duplicate keys in global/input/output mapsChangelog labels the change as a bugfix
Fix integer underflow in PSRAM virtual-disk file import
psram_copy_file() and psram_mmap_file() trusted FAT metadata exposed over USB Mass Storage: a cluster chain covering more bytes than the directory entry's file size made 'len = actual_len - so_far' underflow to ~4GB, causing an out-of-bounds memcpy across PSRAM from a compromised USB host.
- validate cluster-chain coverage against file size before each fragment - check destination bounds with 64-bit arithmetic *before* writing (the old post-memcpy check was too late, and dest+len+3 could wrap)
Q1 shares this file via symlink; both platforms are fixed.
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
defensive validation
AI review queuedupdate block heightby Peter D. Gray · 98b0c906 · Aug 19, 2026 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · Peter D. Gray
update block height
28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100
This commit simply increments an automatically-generated Bitcoin block height constant by one. It is a routine data update with no code changes and no security implications.
AI review queuedupdate block heightby Peter D. Gray · 84d49266 · Aug 19, 2026 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · Peter D. Gray
update block height
28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100
This commit simply updates a stored Bitcoin blockchain height number from 963,074 to 963,190, along with its timestamp. It is a routine data refresh with no code logic changes and no apparent security relevance.
Lower-priorityrestore PSRAM USB download hardening changelogby @Bibo-dochex · 15de4a0c · Aug 19, 2026 · 1 fileMessage 45 · ThinTriage 0Details
Commit message · @Bibo-dochex
restore PSRAM USB download hardening changelog
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
defensive validationdocumentation-only discount
AI review queuedexternal/ckcc-protocol: bump to c39db297by scgbckbone · 9fd64667 · Aug 19, 2026 · 1 fileMessage 45 · ThinInformational 15Details
Commit message · scgbckbone
external/ckcc-protocol: bump to c39db297
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
parser or protocol pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit only updates a linked external code submodule (ckcc-protocol) to a newer version. The actual code changes are not shown in this diff, only the submodule pointer was moved. There is no information in the commit itself about what changed in the submodule or whether it has any security relevance.
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
seed or entropy pathparser or protocol path
AI analysis · Low 35/100
This commit adds a new, more secure USB encryption mode (ncry v3) to the COLDCARD hardware wallet firmware. It does not remove the older v1/v2 mode. The new mode adds message authentication tags and separate keys for each direction, which protects against tampering, replay, and reflection attacks on the USB cable. The commit also fixes a timing side-channel in user authentication by replacing direct HMAC comparisons with a constant-time comparison. The change is defensive and improves security, but the old unauthenticated modes remain available for compatibility, so users must actively choose v3 to get the stronger protection.
AI review queuedenhancement: make multisig rename explicitby scgbckbone · a1857885 · Aug 19, 2026 · 5 filesMessage 45 · ThinLow 34Details
Commit message · scgbckbone
enhancement: make multisig rename explicit
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 34/100
This commit changes how COLDCARD handles multisig wallet names. Previously, re-importing a wallet file or descriptor with a different name would silently rename the existing wallet. Now, renaming must be done through an explicit 'Rename' menu action, and re-importing a duplicate with a different name is rejected. This is a security-hardening UX change that prevents accidental or malicious wallet renaming during import, which could confuse users about which wallet they are signing for.
AI review queuedupdate next changelogby scgbckbone · c7d7ae03 · Aug 19, 2026 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · scgbckbone
update next changelog
28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
This commit only edits the project's 'Next-ChangeLog.md' file. It rewrites upcoming release notes, adds details, fixes wording, and updates release dates. No actual firmware code, build scripts, or security behavior changed in this commit. The changelog text does describe many security fixes, but those fixes are already present in other commits; this commit merely documents them.
Lower-prioritytesting: chunk long simulator storiesby scgbckbone · 7e2e6504 · Aug 19, 2026 · 1 fileMessage 55 · ThinTriage 0Details
Commit message · scgbckbone
testing: chunk long simulator stories
55/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
AI review queuedupdate block heightby Peter D. Gray · 3f640d74 · Aug 18, 2026 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · Peter D. Gray
update block height
28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100
This commit simply updates a stored Bitcoin blockchain height number from 960,398 to 963,074, along with its timestamp. It is a routine data refresh with no code logic changes and no apparent security relevance.
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI review queuedimprove tests stabilityby scgbckbone · 8e0f2bbb · Aug 18, 2026 · 4 filesMessage 38 · OpaqueInformational 15Details
Commit message · scgbckbone
improve tests stability
38/100 · OpaqueMessage clarity
✓ Subject identifies a change✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: opaque commit messagesecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit only changes test code for the COLDCARD firmware. It makes the test suite more stable by letting developers specify a custom Bitcoin daemon path, adding a PSBT2 test flag, fixing a test that checks upload-during-approval behavior, and importing an extra constant for user-interface tests. None of these changes affect the actual firmware that runs on the device, so there is no security risk to users.
Lower-priorityFix release notes formatting and keep current libnguby @Bibo-dochex · 55f93844 · Aug 17, 2026 · 2 filesMessage 50 · ThinTriage 0Details
Commit message · @Bibo-dochex
Fix release notes formatting and keep current libngu
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI review queuededitsby @Bibo-dochex · ca286530 · Aug 17, 2026 · 1 fileMessage 0 · OpaqueInformational 15Details
Commit message · @Bibo-dochex
edits
0/100 · OpaqueMessage clarity
! Very short subject! Too few words to establish purpose! No meaningful explanatory body
This commit only edits the wording of an upcoming release changelog. It does not change any firmware code, cryptographic algorithms, or security behavior. The edits clarify and reorganize descriptions of previously planned entropy-generation improvements, but they do not themselves introduce or fix any vulnerability.
Lower-priorityRelease notes editing, version bumpby @Bibo-dochex · b748d75c · Aug 17, 2026 · 4 filesMessage 45 · ThinTriage 0Details
Commit message · @Bibo-dochex
Release notes editing, version bump
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Security candidatebugfix: separate DFU container limit from firmware boundby scgbckbone · cc63e6fe · Aug 17, 2026 · 3 filesMessage 73 · AdequateLow 34Details
Commit message · scgbckbone
bugfix: separate DFU container limit from firmware bound
FW_MAX_LENGTH_MK4 now bounds only the firmware itself to the world-checksum-covered flash region (4k aligned, no DFU-wrapper slack carved out). New FW_MAX_DFU_SIZE_MK4 adds room for the bootloader element and DFU wrapper so multi-element -factory.dfu images remain selectable in the MicroSD file picker.
73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
update trust
AI analysis · Low 34/100
This commit fixes a bug in the COLDCARD firmware update process. Previously, the maximum file size allowed for a firmware update file (.dfu) was set too small because it was based on the firmware's own size limit, not accounting for extra data that comes with 'factory' update images (which include a bootloader and a DFU wrapper). As a result, legitimate factory firmware files could not be selected from the MicroSD card picker. The fix separates the two limits: one for the actual firmware size, and a larger one for the .dfu container shown in the file picker. There is no direct evidence in the commit that this was a security vulnerability, but overly restrictive size checks can sometimes hide or complicate downgrade or supply-chain issues.
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
defensive validation
Security candidaterequire scrolling to reveal passphraseby scgbckbone · cb6dca78 · Aug 17, 2026 · 3 filesMessage 45 · ThinLow 43Details
Commit message · scgbckbone
require scrolling to reveal passphrase
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
access controlcryptography-sensitive pathseed or entropy path
AI analysis · Low 43/100
This change makes the COLDCARD wallet require the user to scroll down before showing a BIP-39 passphrase on screen. The goal is to reduce the chance that someone nearby (a shoulder-surfer) or a camera can read the secret passphrase when it appears automatically. It is a small user-interface hardening improvement, not a fix for a remote hack.
Security candidateChange: use combined-source RNG for security-sensitive valuesby scgbckbone · 575844f6 · Aug 17, 2026 · 4 filesMessage 55 · ThinLow 46Details
Commit message · scgbckbone
Change: use combined-source RNG for security-sensitive values
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
entropy or randomness
AI analysis · Low 46/100
This commit changes how the COLDCARD hardware wallet generates random numbers used to protect backups, encrypted files, and two-factor authentication secrets. Previously these sensitive values were produced using only the STM32 chip's built-in random number generator (TRNG). Now they are produced through a stronger combined method: a Hash-DRBG (a NIST-style deterministic random-bit generator) that is seeded from both secure elements and the TRNG. The change is defensive hardening rather than a fix for a known exploitable bug, but it reduces the risk that a weakness in the STM32 TRNG alone could weaken user secrets.
Change: enforce entropy checks for temporary dice seeds
35/100 · OpaqueMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Names security-relevant behavior explicitly! No meaningful explanatory body! Contains work-in-progress language! Opaque security-relevant change
Why it was queued
entropy or randomnessseed or entropy path
AI analysis · Low 45/100
This commit tightens security for temporary Bitcoin wallet seeds created by rolling dice on a COLDCARD hardware wallet. Previously, temporary dice-generated seeds skipped the same mandatory entropy checks and warnings used for permanent dice-generated seeds. The change makes temporary dice seeds follow the same rules, so users cannot accidentally create a weak wallet from too few dice rolls. This is a defensive hardening fix, not an active bug that steals funds, but weak entropy could let an attacker guess a wallet's private keys.