CK
← All projectsCoinkite

COLDCARD firmware

Open-source firmware for COLDCARD Bitcoin signing devices.

BitcoinHardware walletsActive incident
Repository coverage

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

145security candidates221second-pass queue433AI analyses
7commits · 30 days
45commits · 60 days
282commits · 180 days
383commits · 365 days
Backfill bands
Aug 5 → Feb 6148 seen2 candidatesComplete
Feb 6 → Jun 684 seen8 candidatesComplete
Jun 6 → Jul 649 seen4 candidatesComplete
Jul 6 → Aug 525 seen4 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.

36/100 average clarity
12Strong · 80–100
49Adequate · 60–79
223Thin · 40–59
230Opaque · 0–39
43security 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.
scgbckbone2811172361843
Peter D. Gray18220170818
Dmitry Monakhov212173
@Bibo-dochex1023043
doc-hex311073
habakan111065
Piotr Duszynski111073
Kyle Santiago111050
kdmukai111050
tadeubas606051
Danilo500079
copilot-swe-agent[bot]504072
Analysis record

Published AI watches

Last scanned 11 minutes ago

Informational 19 AI analysisMessage 83 · Strong
CK CoinkiteCOLDCARD firmware BitcoinHardware wallets

Test P2A signing and future SegWit address rendering

This commit is almost entirely new test code for the COLDCARD hardware wallet. It adds checks that the wallet correctly shows and signs transactions involving newer Bitcoin address types (SegWit v1 through v16, including P2A 'anchor' outpu…

Adds test coverage for BIP-350 Bech32m address encoding/decodingAdds malformed witness script rejection tests for render_addressAdds HSM whitelist tests for future SegWit (v1/v2) outputs
467d53dcby scgbckbone+206−25 files
No security note in commit
Moderate 52 AI analysisMessage 50 · Thin
CK CoinkiteCOLDCARD firmware BitcoinHardware wallets

bugfix: rng_selftest fails with __fatal_error instead of mp_raise before VM init

This commit fixes a bug in the COLDCARD MK4 hardware wallet's random number generator (RNG) self-test. Before the fix, if the RNG hardware failed during the self-test, the code would try to raise a Python exception (mp_raise) even though t…

Controlled fatal error replaces uncontrolled exception in pre-VM contextRNG hardware-failure handling during early bootAvoids potential undefined behavior / crash before nlr handler exists
b902f91dby Kyle Santiago+9−61 file
No security note in commit
Low 49 AI analysisMessage 65 · Adequate
CK CoinkiteCOLDCARD firmware BitcoinHardware wallets

bugfix: show segwit v1+ outputs of any program length as addresses

This commit fixes a display bug in the COLDCARD hardware wallet. Previously, newer-style Bitcoin addresses (SegWit version 1 and above) were only shown as readable bech32m addresses if they were exactly 32 bytes long. For any other allowed…

UI display bug in address renderingIncorrect handling of valid BIP-141 witness program lengthsPotential user confusion when verifying transaction outputs
09766a14by habakan+24−13 files
No security note in commit
Informational 13 AI analysisMessage 93 · Strong
CK CoinkiteCOLDCARD firmware BitcoinHardware wallets

build(deps): bump pillow from 12.3.0 to 13.0.0 in /misc/q1font

This is a routine automated update by Dependabot that bumps the Python Pillow image-processing library from version 12.3.0 to 13.0.0 in a small helper tool used to build fonts for the COLDCARD hardware wallet. The change itself is a single…

Dependency version bump from 12.3.0 to 13.0.0Pillow 13.0.0 removes deprecated/insecure image decoders (XBM, MSP) and fixes historical parsing bugsNo CVE, advisory, or security rationale is mentioned in the commit or supplied references
a772156dby dependabot[bot]+1−11 file
No security note in commit
High 74 AI analysisMessage 45 · Thin
CK CoinkiteCOLDCARD firmware BitcoinHardware wallets

Fix PSBT input classification and finalization

This commit fixes bugs in how the COLDCARD hardware wallet classifies and finalizes Bitcoin transaction inputs from PSBT files. Before the fix, the device could incorrectly treat foreign or already-signed inputs as complete, producing an i…

Changelog labels the changes as 'Bugfix' and credits 'Nabeel-javed' for one of themSeparation of input classification from signing-key selection reduces risk of misclassifying foreign/presigned inputsNew script_validated flag prevents finalization of inputs whose scripts/signatures were not verified
7e26ade3by scgbckbone+851−1534 files
Vendor flagged security relevance
Informational 15 AI analysisMessage 28 · Opaque
CK CoinkiteCOLDCARD firmware BitcoinHardware wallets

Signed for mk release.

This commit only updates the release signature file. It adds two new cryptographic hashes for recently built firmware files and refreshes the PGP signature that covers the whole file. There are no code changes, no bug fixes, and no securit…

5dbb374bby Peter D. Gray+10−81 file
No security note in commit
Informational 15 AI analysisMessage 28 · Opaque
CK CoinkiteCOLDCARD firmware BitcoinHardware wallets

update block height

This commit simply updates an automatically-generated Bitcoin blockchain checkpoint number in a single file. It changes one digit in the stored block height and the timestamp by less than two minutes. There is no security relevance.

d3db2a30by Peter D. Gray+2−21 file
No security note in commit
Informational 15 AI analysisMessage 28 · Opaque
CK CoinkiteCOLDCARD firmware BitcoinHardware wallets

Signed for q1 release.

This commit only updates a signed release manifest file (releases/signatures.txt). It refreshes SHA-256 checksums for several changelog/history files and adds two new Q1 firmware release files, then re-signs the file with a PGP signature. …

8b1d005bby Peter D. Gray+16−141 file
No security note in commit
Informational 15 AI analysisMessage 28 · Opaque
CK CoinkiteCOLDCARD firmware BitcoinHardware wallets

update block height

This commit simply updates a stored Bitcoin blockchain height number from 969,312 to 969,345, reflecting about five hours of new blocks. There is no code logic change, no user-facing behavior change, and no security relevance.

5fa4e6a6by Peter D. Gray+2−21 file
No security note in commit
Informational 15 AI analysisMessage 0 · Opaque
CK CoinkiteCOLDCARD firmware BitcoinHardware wallets

edits

This commit only reorganizes release notes. It moves the changelog entries for firmware versions 5.6.2/1.5.2Q and 5.6.3/1.5.3Q into the historic changelog files and resets the 'next' changelog to placeholder 'tbd' entries. No source code, …

08ae1a54by Peter D. Gray+142−824 files
No security note in commit
Informational 15 AI analysisMessage 28 · Opaque
CK CoinkiteCOLDCARD firmware BitcoinHardware wallets

update block height

This commit simply increments a stored Bitcoin blockchain height value by one block (from 969,311 to 969,312) and updates the corresponding timestamp by 97 seconds. It is an auto-generated data update with no code logic changes and no appa…

54a7fafaby Peter D. Gray+2−21 file
No security note in commit
Informational 15 AI analysisMessage 28 · Opaque
CK CoinkiteCOLDCARD firmware BitcoinHardware wallets

update block height

This is a routine data update that bumps an internal Bitcoin block height number used by the COLDCARD firmware. There are no code logic changes, no bug fixes, and no security-relevant behavior changes visible in the diff.

df07ca73by Peter D. Gray+2−21 file
No security note in commit
Informational 15 AI analysisMessage 30 · Opaque
CK CoinkiteCOLDCARD firmware BitcoinHardware wallets

Temporary Seed Names does not fit as menu item on Mk4 & Mk5

This commit shortens a menu label on older COLDCARD devices (Mk4 and Mk5) because the original text 'Temporary Seed Names' was too long to display on their smaller screens. It is a user-interface fix with no security relevance.

7243a6ddby scgbckbone+14−42 files
No security note in commit
Informational 12 AI analysisMessage 0 · Opaque
CK CoinkiteCOLDCARD firmware BitcoinHardware wallets

test fixes

This commit only adjusts test scripts and the simulator's fake secure-element storage. It makes tests more reliable by waiting for screens longer, refreshing menus after settings changes, ignoring a harmless internal counter, and keeping s…

33525668by scgbckbone+37−115 files
No security note in commit
Low 33 AI analysisMessage 45 · Thin
CK CoinkiteCOLDCARD firmware BitcoinHardware wallets

Allow activation of calculated Codex32 secrets

This commit adds a new feature to COLDCARD firmware that lets users activate a Bitcoin wallet directly from a Codex32 checksum calculation screen, instead of having to export and re-import the secret. It is a user-experience improvement fo…

Feature addition enabling direct activation of calculated secretsUser confirmation still required before setting master seedActivation restricted to secret shares (index 'S') only
16b33e85by scgbckbone+78−114 files
No security note in commit
Informational 15 AI analysisMessage 18 · Opaque
CK CoinkiteCOLDCARD firmware BitcoinHardware wallets

version bump

This commit is a routine version bump for the COLDCARD firmware release process. It updates version strings in two build makefiles (from 5.6.2 to 5.6.3 for Mk, and from 1.5.2Q to 1.5.3Q for Q) and finalizes the release date and changelog e…

97719c6bby Peter D. Gray+11−113 files
No security note in commit
High 78 AI analysisMessage 50 · Thin
CK CoinkiteCOLDCARD firmware BitcoinHardware wallets

Restrict signing and Teleport retry QR scans to expected types

This update fixes a bug in the COLDCARD Q1 hardware wallet where scanning a QR code from the 'Ready To Sign' or 'Key Teleport retry' screens could accidentally replace the device's master seed with seed words or an extended private key sho…

Unintended master seed replacement via QR scan in signing/Teleport flowsMissing input-type validation on context-sensitive QR scannerTightened secure-element secret-overwrite guard in set_seed_value()
fcc0dc96by scgbckbone+70−87 files
Vendor flagged security relevance
Low 37 AI analysisMessage 45 · Thin
CK CoinkiteCOLDCARD firmware BitcoinHardware wallets

Warn before risky firmware upgrades

This commit adds user-facing warnings to the COLDCARD hardware wallet before it installs firmware that is either signed by someone other than Coinkite (an 'external contributor') or older than the firmware already on the device (a downgrad…

Adds explicit user warning for externally signed firmware imagesAdds explicit user warning for firmware downgradesDoes not enforce a hard block; relies on user consent
5c13be46by scgbckbone+77−43 files
Vendor flagged security relevance
Informational 15 AI analysisMessage 25 · Opaque
CK CoinkiteCOLDCARD firmware BitcoinHardware wallets

Show Seed Vault names for temporary seeds

This commit adds a user-facing preference that lets a COLDCARD owner optionally replace the temporary seed's fingerprint (XFP) on the home screen with the friendly name stored in the Seed Vault. It is a cosmetic UI enhancement with no secu…

5a18e566by scgbckbone+56−55 files
No security note in commit
Informational 15 AI analysisMessage 35 · Opaque
CK CoinkiteCOLDCARD firmware BitcoinHardware wallets

Codex32 & Shamir Secret Sharing

This is a large feature commit adding Codex32 (BIP-93) secret encoding and Shamir secret sharing to COLDCARD firmware. It introduces new menu flows to generate, import, split, recover, and derive Codex32 shares, plus two COLDCARD-specific …

New feature: Codex32 / BIP-93 secret encoding and Shamir secret sharingNew COLDCARD extensions CW1 and CX1 with documented wire format and conformance vectorsInput validation for case, HRP, length, checksum, threshold, and scalar bounds
571f0338by scgbckbone+4993−8940 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 candidateQ: brick into forever calculatorby scgbckbone · 1929067a · Sep 22, 2025 · 3 filesMessage 45 · ThinLow 42Details
Commit message · scgbckbone

Q: brick into forever calculator

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 42/100

This commit changes what a COLDCARD Q device does when its secure element (SE) is 'bricked'—a state where the hardware security chip is no longer usable. Previously, the device immediately entered DFU (device firmware update) mode and stopped. After this change, the device first opens a calculator-like text interface that can run forever, and only then enters DFU mode. The commit title 'Q: brick into forever calculator' suggests this is intentional behavior for bricked devices, not a vulnerability. The change also removes the ability to enter a PIN from within that calculator when reached through this bricked path, so it does not appear to provide a way to bypass authentication.

Security candidateadd "Restore from XOR" to Temporary Seed menuby scgbckbone · 2b115059 · Sep 22, 2025 · 1 fileMessage 25 · OpaqueInformational 17Details
Commit message · scgbckbone

add "Restore from XOR" to Temporary Seed menu

25/100 · OpaqueMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body! Contains work-in-progress language! Opaque security-relevant change
Why it was queued
seed or entropy path
AI analysis · Informational 17/100

This commit adds a new menu option called 'Restore Seed XOR' to the Temporary Seed menu on a COLDCARD device. It simply exposes an existing feature (restoring a seed from XOR-encoded parts) in a new place where users can reach it more easily. There is no code change to how seeds are stored, processed, or protected.

Security candidatetxout explorer do not yikes on big QRsby scgbckbone · 0237fd29 · Sep 18, 2025 · 8 filesMessage 45 · ThinLow 36Details
Commit message · scgbckbone

txout explorer do not yikes on big QRs

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

This update fixes a user-interface crash in the COLDCARD hardware wallet when it tries to display very large QR codes. Before the change, certain long transaction outputs (for example, OP_RETURN data or unusual scripts) could make the on-device QR generator fail and throw an error, interrupting transaction review. The patch catches that failure, shows a 'QR too big' placeholder instead, and lets the user keep reviewing the transaction. It is a denial-of-service-style reliability fix rather than a theft-of-funds vulnerability.

Security candidaterestore backup via USBby scgbckbone · de043f22 · Sep 18, 2025 · 8 filesMessage 28 · OpaqueModerate 59Details
Commit message · scgbckbone

restore backup via USB

28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
authentication path
AI analysis · Moderate 59/100

This commit adds a new USB command that lets a connected computer restore a COLDCARD wallet backup onto the device. The user must confirm on the device screen, and the backup file's checksum is verified. However, because restoring a backup replaces the wallet seed, the feature is security-sensitive. The commit also blocks this command in HSM (unattended signing) mode, which is a good protective measure. There is no direct evidence of a vulnerability in the patch, but the feature increases the attack surface available over USB.

Security candidateforgotten pinby Peter D. Gray · 8d84979d · Sep 16, 2025 · 1 fileMessage 18 · OpaqueInformational 15Details
Commit message · Peter D. Gray

forgotten pin

18/100 · OpaqueMessage clarity
✓ Subject identifies a change! Too few words to establish purpose! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
access controldocumentation-only discount
AI analysis · Informational 15/100

This commit only updates user documentation. It fixes a typo in a menu path and adds a new section explaining what to do if a user forgets their 'Bypass PIN' for the Spending Policy feature: perform a factory reset via 'Destroy Seed' and restore from backup. There is no code change and no security vulnerability is being fixed.

Security candidatenitsby Peter D. Gray · 1a1daf32 · Sep 16, 2025 · 3 filesMessage 0 · OpaqueInformational 15Details
Commit message · Peter D. Gray

nits

0/100 · OpaqueMessage clarity
! Very short subject! Too few words to establish purpose! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
authentication path
AI analysis · Informational 15/100

This commit contains only trivial non-code changes: a comment rewording, a stylistic Python list change with identical behavior, a typo fix in a user-facing message, and a hyphenation fix in a test file docstring. There is no security-relevant change.

Security candidatenitsby Peter D. Gray · 3f24307d · Sep 16, 2025 · 2 filesMessage 0 · OpaqueInformational 15Details
Commit message · Peter D. Gray

nits

0/100 · OpaqueMessage clarity
! Very short subject! Too few words to establish purpose! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
seed or entropy path
AI analysis · Informational 15/100

This commit is a minor code cleanup ('nits'). It moves a helper function, adds a comment, and removes an unused local import. There is no change to user-facing behavior or security logic.

Security candidatebug noteby Peter D. Gray · 6b1c38fe · Sep 16, 2025 · 1 fileMessage 0 · OpaqueLow 41Details
Commit message · Peter D. Gray

bug note

0/100 · OpaqueMessage clarity
! Very short subject! Too few words to establish purpose! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
boot or update path
AI analysis · Low 41/100

A developer added a comment in the COLDCARD MK4 bootloader code flagging that a function reads a configuration byte from a secure chip but does not check whether the read operation failed. If the read fails, the function could return an uninitialized or garbage value. This is a code-quality and potential security issue, but the patch only adds a comment—it does not fix the bug.

Security candidatecleanupsby Peter D. Gray · 609af3a2 · Sep 16, 2025 · 2 filesMessage 0 · OpaqueInformational 15Details
Commit message · Peter D. Gray

cleanups

0/100 · OpaqueMessage clarity
! Very short subject! Too few words to establish purpose! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
authentication path
AI analysis · Informational 15/100

This commit is a minor cleanup. It removes an obsolete unused method from the PIN handling code and fixes a punctuation error in a user-facing message shown when a spending policy blocks an action. There is no security-relevant change.

Security candidateSSSP update menu tree & related adjustmentsby scgbckbone · 372954e4 · Sep 16, 2025 · 5 filesMessage 45 · ThinInformational 11Details
Commit message · scgbckbone

SSSP update menu tree & related adjustments

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 · Informational 11/100

This commit is a routine update to the on-device menu layout and the developer tool that prints that layout. It reorganizes where options appear for a special 'SSSP' limited mode, renames some menu labels, and fixes a few internal code patterns (like replacing inline checks with named helper functions). There is no direct evidence in the commit of a security vulnerability being fixed.

Security candidatemore testsby scgbckbone · 8ceb6a46 · Sep 16, 2025 · 2 filesMessage 0 · OpaqueInformational 15Details
Commit message · scgbckbone

more tests

0/100 · OpaqueMessage clarity
✓ Mentions testing or verification! Very short subject! Too few words to establish purpose! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
cryptography-sensitive path
AI analysis · Informational 15/100

This commit only adds and updates test files for the COLDCARD firmware. It expands automated tests for temporary seed handling under a restricted 'hobble' mode, including a new test case for BIP-39 passphrases and a more complete XPRV import test. There are no changes to the actual firmware code that runs on the device, so this commit does not introduce or fix any security vulnerability by itself.

Security candidatetestingby Peter D. Gray · 76cc136a · Sep 16, 2025 · 6 filesMessage 0 · OpaqueLow 35Details
Commit message · Peter D. Gray

testing

0/100 · OpaqueMessage clarity
✓ Mentions testing or verification! Very short subject! Too few words to establish purpose! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
seed or entropy path
AI analysis · Low 35/100

This commit adjusts how COLDCARD's 'hobbled mode' handles temporary seeds and the Seed Vault. Hobbled mode is a restricted operating mode (often tied to a special PIN or duress-like setup). The change makes temporary seeds read-only: users can import and use an existing temporary seed for signing, but cannot generate new words or save the temporary seed into the Seed Vault. It also exposes a 'Temporary Seed' menu under Advanced/Tools when a spending-policy flag called 'okeys' is enabled. The commit is titled 'testing' and appears to be a work-in-progress feature patch with added tests, not a published security fix.

Security candidateword entryby Peter D. Gray · 43544f4f · Sep 16, 2025 · 3 filesMessage 0 · OpaqueLow 26Details
Commit message · Peter D. Gray

word entry

0/100 · OpaqueMessage clarity
! Very short subject! Too few words to establish purpose! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
seed or entropy path
AI analysis · Low 26/100

This commit fixes a small bug in the COLDCARD wallet's login security check. When the device asks the user to confirm the first and last seed words (to prove they know the backup), the old code could accidentally keep leftover words from a previous attempt. The change makes the word collection more reliable and adds a 'Startup...' message so the screen doesn't look frozen. It is a cleanup/hardening fix rather than a clear-cut exploitable vulnerability.

Security candidateMk4 SSSP Word Checkby scgbckbone · d15de032 · Sep 16, 2025 · 2 filesMessage 28 · OpaqueLow 44Details
Commit message · scgbckbone

Mk4 SSSP Word Check

28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
seed or entropy path
AI analysis · Low 44/100

This commit fixes the 'first and last seed word' login challenge on older COLDCARD Mk4 devices. Previously, the on-screen word picker for this security check was broken (the code even had a 'TODO: fix bugs here on Mk4' comment), which could have allowed someone with physical access to bypass or fail the word-check screen. The patch replaces the buggy callback-based picker with a working one, so the device can now properly verify the user's seed words during login.

Security candidatenitsby scgbckbone · 0420d4b6 · Sep 16, 2025 · 4 filesMessage 0 · OpaqueLow 43Details
Commit message · scgbckbone

nits

0/100 · OpaqueMessage clarity
! Very short subject! Too few words to establish purpose! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
authentication path
AI analysis · Low 43/100

This commit fixes a PIN-uniqueness check in the COLDCARD's 'Seed Vault / Secure Spending Policy' setup. Previously, when a user picked an unlock PIN, the code only compared it against the main PIN and visible 'trick' PINs, but missed hidden trick PINs. That could let the same PIN be used for two different security features, which can cause confusion or allow a hidden trick PIN to silently override the intended unlock behavior. The patch now asks the secure element (SE2) whether the PIN is already in use anywhere before accepting it.

Security candidatespending policy implementedby Peter D. Gray · f12457cb · Sep 16, 2025 · 12 filesMessage 35 · OpaqueLow 35Details
Commit message · Peter D. Gray

spending policy implemented

35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
authentication path
AI analysis · Low 35/100

This commit adds and reorganizes a 'Spending Policy' feature for the COLDCARD hardware wallet. It lets owners set rules (daily limits, allowed addresses, time delays, web 2FA) that block or allow transaction signing. The change is a feature implementation, not a reported security bug fix. There is no vendor statement that this commit fixes a vulnerability, and no independent researcher is credited.

Security candidatehobbled mode support for spending policyby Peter D. Gray · c3a454ab · Sep 16, 2025 · 13 filesMessage 45 · ThinLow 37Details
Commit message · Peter D. Gray

hobbled mode support for spending policy

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

This commit adds a new 'hobbled mode' feature to the COLDCARD hardware wallet firmware. It lets a user set a 'Spending Policy' that restricts what the device can do even when the main PIN is entered. The policy can limit access to seed words, backups, secure notes, and certain signing operations. A special bypass PIN is required to disable or change the policy. The change is a feature addition, not a fix for a known vulnerability, and the commit message and code comments describe it as a user-controlled self-protection mechanism.

Security candidatetest deltamode worksby Peter D. Gray · 7daa67cc · Sep 16, 2025 · 4 filesMessage 38 · OpaqueInformational 15Details
Commit message · Peter D. Gray

test deltamode works

38/100 · OpaqueMessage clarity
✓ Subject identifies a change✓ Mentions testing or verification! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
access control
AI analysis · Informational 15/100

This commit only adds automated tests for an existing firmware feature called 'deltamode' trick PINs. It does not change the actual COLDCARD firmware code that users run. The tests confirm that when a deltamode trick PIN is active, the device produces an intentionally invalid Bitcoin signature and does not wipe the seed. No security bug is introduced or fixed here.

Security candidatebugfix: enter vfs after creating itby scgbckbone · 9a4d3986 · Sep 16, 2025 · 4 filesMessage 45 · ThinLow 41Details
Commit message · scgbckbone

bugfix: enter vfs after creating it

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 41/100

This commit fixes a bug where the COLDCARD device's internal flash filesystem was created but not properly entered before trying to create a settings folder. As a result, the folder could be created in the wrong place or the filesystem setup could fail. The fix changes the code to enter the new filesystem first, then create the folder. A related change removes an extra argument when wiping the filesystem during seed operations, and adds a confirmation-key requirement to the filesystem wipe command to reduce accidental use.

Security candidateClarify allowed usage of Seed XOR standard and nameby kdmukai · 3eb99272 · Aug 29, 2025 · 1 fileMessage 50 · ThinInformational 15Details
Commit message · kdmukai

Clarify allowed usage of Seed XOR standard and name

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
seed or entropy pathdocumentation-only discount
AI analysis · Informational 15/100

This commit only adds a short paragraph to documentation stating that Seed XOR is an open standard and that others may use the name and implement it freely. There is no code change, no security fix, and no vulnerability.