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 48 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 candidatereload Trick Pins before deleting unlock pinsby scgbckbone · f3aaf3d5 · Sep 25, 2025 · 1 fileMessage 45 · ThinModerate 57Details
Commit message · scgbckbone

reload Trick Pins before deleting unlock pins

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

This change fixes a potential bug in how COLDCARD's 'trick PIN' feature removes special unlock PINs. Before deleting those PINs, the code now reloads the trick PIN data from storage. Without the reload, the function might operate on stale in-memory data and fail to delete some trick PINs that should have been removed. That could leave behind an unintended bypass PIN after a feature is turned off, which is a security-relevant state.

Lower-prioritydisallow Type Passwords if not okeys in ssspby scgbckbone · 06fa4f33 · Sep 25, 2025 · 1 fileMessage 45 · ThinLow 46Details
Commit message · scgbckbone

disallow Type Passwords if not okeys in sssp

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

This commit tightens access to the 'Type Passwords' feature on COLDCARD devices when operating in a restricted 'semi-seedless' mode (SSSP). Previously, the feature was available whenever the device was in emulator mode; now it also requires that SSSP-related keys are present. Without this change, a user in this restricted mode might have been able to type out stored passwords even when other seed-dependent features were intentionally disabled. The fix is a one-line guard that aligns the password-typing feature with the same key-presence check used for related features.

Lower-priorityproper label for Web 2FA warningby scgbckbone · 2d81b725 · Sep 25, 2025 · 1 fileMessage 45 · ThinInformational 15Details
Commit message · scgbckbone

proper label for Web 2FA warning

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

This is a tiny user-interface label fix. It changes the warning label shown when a spending policy requires web-based two-factor authentication from the generic text 'CCC' to the specific policy key name. There is no security vulnerability here.

Security candidatedo not allow empty BIP-39 passphrase over USBby scgbckbone · 91f10c2f · Sep 25, 2025 · 1 fileMessage 45 · ThinModerate 64Details
Commit message · scgbckbone

do not allow empty BIP-39 passphrase over USB

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
access control
AI analysis · Moderate 64/100

This update prevents a COLDCARD hardware wallet from accepting an empty BIP-39 passphrase when the command comes over the USB connection. A BIP-39 passphrase is an extra word or phrase users can add to their seed to create a separate wallet. Previously, an empty passphrase could be sent through USB, which might let software on the connected computer silently access the user's default/no-passphrase wallet without the user typing anything on the device. Now the device rejects empty passphrases over USB, so the user must intentionally enter a passphrase on the device itself.

Lower-priorityfix SSSP test drive to actually enforce policyby scgbckbone · a1e7e4c8 · Sep 25, 2025 · 1 fileMessage 55 · ThinModerate 57Details
Commit message · scgbckbone

fix SSSP test drive to actually enforce policy

55/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
AI analysis · Moderate 57/100

This commit fixes a bug in the COLDCARD firmware's 'SSSP test drive' feature. Previously, the code that checks whether the feature is enabled did not properly recognize the special 'test drive' mode, and it called the wrong method when approving transactions. The fix makes the test drive mode correctly activate the feature and uses the intended transaction-approval routine. In practical terms, a user in test-drive mode might have been unable to use the feature as designed, or the wrong internal path could have led to an approval that did not enforce the intended spending policy.

AI review queuedbump ccc_min_block (block height)by scgbckbone · fce9503d · Sep 25, 2025 · 1 fileMessage 35 · OpaqueInformational 12Details
Commit message · scgbckbone

bump ccc_min_block (block height)

35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 12/100

This commit updates a single configuration number in the COLDCARD firmware that tells the device the earliest Bitcoin block height at which a certain feature (likely related to 'ccc' or CoinJoin-style coordination) should be considered active. It is a routine date/height bump, not a code change that fixes a vulnerability. By itself it does not appear to introduce or patch a security flaw.

Lower-priorityfix multisig test ms_sign_simpleby scgbckbone · b88590f8 · Sep 24, 2025 · 1 fileMessage 45 · ThinInformational 15Details
Commit message · scgbckbone

fix multisig test ms_sign_simple

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Mentions testing or verification! No meaningful explanatory body
AI analysis · Informational 15/100

This commit only changes a test file (testing/test_multisig.py). It fixes a test helper called ms_sign_simple by adding proper derivation path handling and adjusting how xpubs are included in test multisig wallets. There is no change to the actual COLDCARD firmware code that users run, so it cannot directly affect real device security.

AI review queuedrewordby Peter D. Gray · 1a591a70 · Sep 23, 2025 · 1 fileMessage 0 · OpaqueInformational 15Details
Commit message · Peter D. Gray

reword

0/100 · OpaqueMessage clarity
! Very short subject! Too few words to establish purpose! No meaningful explanatory body
Why it was queued
documentation-only discountsecond-pass: opaque commit message
AI analysis · Informational 15/100

This commit only changes one word in a documentation file. It rephrases a sentence about how COLDCARD handles PSBT warnings under a policy rule. There is no code change, no behavior change, and no security fix or vulnerability introduced.

AI review queuedtest fixesby scgbckbone · 26680a00 · Sep 23, 2025 · 4 filesMessage 0 · OpaqueInformational 15Details
Commit message · scgbckbone

test fixes

0/100 · OpaqueMessage clarity
✓ Mentions testing or verification! Very short subject! Too few words to establish purpose! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100

This commit only updates test files in the COLDCARD firmware repository. It adjusts test cases to use new internal constants, skips some secure-notes/password checks on non-Q1 hardware, replaces a slow wallet-creation helper with a faster import helper, updates menu navigation labels in a test, and adds a missing assertion for a classic P2PKH address format. There are no changes to firmware source code, no security fixes, and no disclosed vulnerability.

AI review queuedckcc bumpby scgbckbone · 429b8e64 · Sep 23, 2025 · 1 fileMessage 0 · OpaqueInformational 0Details
Commit message · scgbckbone

ckcc bump

0/100 · OpaqueMessage clarity
! Very short subject! Too few words to establish purpose! No meaningful explanatory body
Why it was queued
parser or protocol pathsecond-pass: opaque commit messagesecond-pass: security-sensitive path
AI analysis · Informational 0/100

This commit is titled 'ckcc bump' and changes one line in one file: external/ckcc-protocol. No diff content is available, and no verified references were supplied. There is no visible information about what was changed, why it was changed, or whether it has any security relevance.

AI review queuededitsby Peter D. Gray · 74fd862c · Sep 23, 2025 · 1 fileMessage 0 · OpaqueInformational 15Details
Commit message · Peter D. Gray

edits

0/100 · OpaqueMessage clarity
! Very short subject! Too few words to establish purpose! No meaningful explanatory body
Why it was queued
documentation-only discountsecond-pass: opaque commit message
AI analysis · Informational 15/100

This commit only edits a documentation file (docs/limitations.md). It updates descriptions of product limitations, such as noting that a previously reserved PIN code is now available, explaining backup file timestamps, adding a note about unsupported pay-to-pubkey transactions, and renaming a feature section. There are no code changes, no bug fixes, and no security-relevant behavior changes in the firmware itself.

AI review queuedcommentsby Peter D. Gray · 0625aa46 · Sep 23, 2025 · 3 filesMessage 0 · OpaqueInformational 15Details
Commit message · Peter D. Gray

comments

0/100 · OpaqueMessage clarity
! Very short subject! Too few words to establish purpose! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100

This commit only adds explanatory comments to two source files and makes a tiny, non-functional cleanup in a USB error handler (removing an unused exception variable). It also adds one line to the changelog noting a separate multisig address-format bugfix. The code changes themselves do not alter program behavior or fix any security issue.

AI review queuedmultisig input/output address formatby scgbckbone · d0c5998e · Sep 23, 2025 · 8 filesMessage 45 · ThinHigh 72Details
Commit message · scgbckbone

multisig input/output address format

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 · High 72/100

This commit fixes how COLDCARD handles different Bitcoin address formats in multisig transactions. Previously, the wallet could be tricked into treating inputs or change outputs as belonging to the wrong address type (for example, treating a classic P2SH multisig input as if it were a wrapped SegWit P2SH-P2WSH input, or vice versa). The patch makes the device strictly check that the script type matches the wallet's configured address format and verifies that the script in the transaction actually produces the expected on-chain scriptPubKey. This prevents attackers from deceiving the device about which coins are being spent or where change is going.

AI review queuedtest hobbled Teleportby scgbckbone · faa5ebf1 · Sep 23, 2025 · 2 filesMessage 38 · OpaqueInformational 15Details
Commit message · scgbckbone

test hobbled Teleport

38/100 · OpaqueMessage clarity
✓ Subject identifies a change✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100

This commit only changes test code for the COLDCARD firmware. It adjusts how a test sets up a 'hobbled' Teleport signing scenario by importing wallet data before hobbled mode is enabled, and removes an unused test parameter. There is no change to the actual firmware or wallet behavior, and no security issue is present in the diff.

AI review queuedhide empty menuby Peter D. Gray · 50d20713 · Sep 23, 2025 · 1 fileMessage 28 · OpaqueInformational 20Details
Commit message · Peter D. Gray

hide empty menu

28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 20/100

This commit hides the 'Spending Policy' menu item when the COLDCARD wallet does not actually have a real secret key loaded. Previously, the menu item was always shown, even though it would be empty or non-functional without a real secret. This is a minor UI cleanup rather than a serious security fix.

Security candidatemk4 fix word entry after restore via USBby scgbckbone · 2445b4d4 · Sep 22, 2025 · 5 filesMessage 45 · ThinInformational 21Details
Commit message · scgbckbone

mk4 fix word entry after restore via USB

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

This commit fixes a user-interface bug on the COLDCARD MK4 that occurred when restoring a wallet backup over USB. After a USB restore, the device was supposed to let the user enter the backup password as a series of seed words, but the on-screen word-entry menu did not work correctly because the device was not coming from the normal menu flow. The fix detects the USB case and uses a simpler, direct word-entry path instead. There is no direct evidence this is a security vulnerability; it appears to be a usability/functional bug fix.

AI review queuednitsby Peter D. Gray · a8366f55 · Sep 22, 2025 · 1 fileMessage 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
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100

This is a tiny test-only change. It removes an unused function argument (`only_q1`) from a test and adds a short delay (`time.sleep(0.1)`) during a test that simulates user button presses. There is no change to the actual COLDCARD firmware code that users run, and nothing here affects security.

Security candidateseedxor allowed when hobbledby Peter D. Gray · 41b81678 · Sep 22, 2025 · 2 filesMessage 35 · OpaqueLow 44Details
Commit message · Peter D. Gray

seedxor allowed when hobbled

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

This commit fixes a security policy bug in the COLDCARD hardware wallet. In 'hobbled mode'—a restricted operating mode meant to limit what secrets can leave or be combined—the device was incorrectly allowing users to include the wallet's master seed as one of the parts when restoring a seed via XOR. The patch removes that option when hobbled, so a locked-down COLDCARD can no longer be tricked or misused into mixing its master seed into an externally reconstructed secret.

AI review queuednitby Peter D. Gray · 3461ce33 · Sep 22, 2025 · 2 filesMessage 0 · OpaqueInformational 15Details
Commit message · Peter D. Gray

nit

0/100 · OpaqueMessage clarity
! Very short subject! Too few words to establish purpose! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100

This is a tiny cleanup commit. It fixes a wording error in the changelog ('after 13 PIN failures, when device is bricked' becomes 'after 13 PIN failures or when device is bricked') and removes an unused local import inside a calculator feature. There is no security-relevant code change.

Security candidateQ becomes calculator rather than e-wasteby Peter D. Gray · 4457576a · Sep 22, 2025 · 9 filesMessage 45 · ThinLow 27Details
Commit message · Peter D. Gray

Q becomes calculator rather than e-waste

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

This update changes what happens on the COLDCARD Q hardware wallet after someone enters the wrong PIN 13 times and the device becomes permanently locked ("bricked"). Instead of showing only a useless "I Am Brick!" screen, the Q model now turns into a simple calculator. The change also lets the calculator's login prompt check whether PIN attempts remain before trying to log in, and adds simulator options so developers can test bricked devices. There is no direct evidence in the commit that this fixes an active security vulnerability; it reads as a usability enhancement for a device that is already considered lost.

Security candidatereviewby scgbckbone · 038199a3 · Sep 22, 2025 · 4 filesMessage 0 · OpaqueLow 42Details
Commit message · scgbckbone

review

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

This commit reorganizes how a COLDCARD device decides it is 'bricked' and what it does next. It moves the brick check from the main boot code into the PIN-handling code, and slightly cleans up a calculator/login helper. The change appears intended to make bricked devices stop earlier in boot and still offer a calculator-only recovery screen on QWERTY models. There is no clear vulnerability being fixed; it reads more like a defensive hardening or refactor.

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.

AI review queuedSSSP settings shared across temporary seedsby scgbckbone · 88110bc5 · Sep 22, 2025 · 6 filesMessage 25 · OpaqueModerate 59Details
Commit message · scgbckbone

SSSP settings shared across temporary seeds

25/100 · OpaqueMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body! Contains work-in-progress language
Why it was queued
second-pass: opaque commit message
AI analysis · Moderate 59/100

This commit fixes a security bug in the COLDCARD firmware where the 'SSSP' (a spending-limit / hobbled mode feature) settings were being saved under the current temporary seed instead of the master seed. That meant switching to a different temporary seed could bypass or corrupt the spending policy. The patch forces SSSP settings to be read from and written to the master seed only, and hides the 'Destroy Seed' menu item when only a temporary seed is loaded.

AI review queuedupdate ckcc to latest masterby scgbckbone · 0a2c0cba · Sep 19, 2025 · 1 fileMessage 45 · ThinInformational 0Details
Commit message · scgbckbone

update ckcc to latest master

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

This commit updates a linked external component (ckcc-protocol) to its latest master version. No actual code changes are shown, and no security-related description is provided. There is not enough information to assess whether this update fixes or introduces any security issue.