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 35 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 candidateTest P2A signing and future SegWit address renderingby scgbckbone · 467d53dc · Nov 11, 2026 · 5 filesMessage 83 · StrongInformational 19Details
Commit message · scgbckbone

Test P2A signing and future SegWit address rendering

Add BIP-350 address vectors, malformed witness-script checks, P2A signing coverage, and HSM whitelist tests. Clarify rendering comments with P2A and BIP-350 references.

83/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
signing boundarysigning or wallet path
AI analysis · Informational 19/100

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' outputs). The only production code change is a comment update in shared/chains.py that clarifies how future SegWit addresses are rendered. There is no patch to a vulnerability and no change to wallet behavior; it improves test coverage and documentation.

Security candidatebugfix: rng_selftest fails with __fatal_error instead of mp_raise before VM initby Kyle Santiago · b902f91d · Nov 9, 2026 · 1 fileMessage 50 · ThinModerate 52Details
Commit message · Kyle Santiago

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

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

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 the Python virtual machine had not started yet. That would cause an uncontrolled crash. Now it calls a controlled fatal-error shutdown instead. The change improves reliability and predictability during early boot, but does not by itself create a security vulnerability.

Security candidatebugfix: show segwit v1+ outputs of any program length as addressesby habakan · 09766a14 · Nov 3, 2026 · 3 filesMessage 65 · AdequateLow 49Details
Commit message · habakan

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

BIP-141 allows 2 to 40 byte programs, and the wallet that built the PSBT shows them as bech32m.

65/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
Why it was queued
signing boundary
AI analysis · Low 49/100

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 length, the wallet displayed the raw script data instead of a normal address. The fix makes the wallet correctly display all allowed lengths as addresses, which helps users verify where their coins are going.

AI review queuedbuild(deps): bump pillow from 12.3.0 to 13.0.0 in /misc/q1fontby dependabot[bot] · a772156d · Oct 23, 2026 · 1 fileMessage 93 · StrongInformational 13Details
Commit message · dependabot[bot]

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

Bumps [pillow](https://github.com/python-pillow/Pillow) from 12.3.0 to 13.0.0.
- [Release notes](https://github.com/python-pillow/Pillow/releases)
- [Changelog](https://github.com/python-pillow/Pillow/blob/main/CHANGES.rst)
- [Commits](https://github.com/python-pillow/Pillow/compare/12.3.0...13.0.0)

---
updated-dependencies:
- dependency-name: pillow
dependency-version: 13.0.0
dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>

93/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
documentation-only discountautomated dependency-update discountsecond-pass: broader security terminology
AI analysis · Informational 13/100

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 line in a requirements file. There is no direct evidence in the commit that this fixes a specific security problem, but Pillow 13.0.0 is a major release that removes several old, insecure image decoders and fixes known bugs. The helper tool is not part of the firmware that runs on the device, so any risk is limited to the build/development environment.

Security candidateFix PSBT input classification and finalizationby scgbckbone · 7e26ade3 · Oct 23, 2026 · 4 filesMessage 45 · ThinHigh 74Details
Commit message · scgbckbone

Fix PSBT input classification and finalization

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

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 invalid ready-to-broadcast transaction instead of returning a still-partial PSBT. The patch separates input analysis from key selection, validates scripts against known wallets before finalizing, and refuses to finalize inputs whose signatures or scripts cannot be verified. The changelog explicitly calls these security-relevant bugfixes and credits an external reporter.

AI review queuedSigned for mk release.by Peter D. Gray · 5dbb374b · Sep 30, 2026 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · Peter D. Gray

Signed for mk release.

28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
signing or wallet pathdocumentation-only discountsecond-pass: opaque commit messagesecond-pass: security-sensitive path
AI analysis · Informational 15/100

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 security-relevant behavior changes in the firmware itself.

AI review queuedupdate block heightby Peter D. Gray · d3db2a30 · Sep 30, 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 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.

AI review queuedSigned for q1 release.by Peter D. Gray · 8b1d005b · Sep 30, 2026 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · Peter D. Gray

Signed for q1 release.

28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
signing or wallet pathdocumentation-only discountsecond-pass: opaque commit messagesecond-pass: security-sensitive path
AI analysis · Informational 15/100

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. No source code, executable logic, or configuration behavior changed. There is no indication of a security fix or vulnerability.

AI review queuedupdate block heightby Peter D. Gray · 5fa4e6a6 · Sep 30, 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 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.

AI review queuededitsby Peter D. Gray · 08ae1a54 · Sep 30, 2026 · 4 filesMessage 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 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, build scripts, or firmware logic were changed.

AI review queuedupdate block heightby Peter D. Gray · 54a7fafa · Sep 30, 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 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 apparent security relevance.

AI review queuedupdate block heightby Peter D. Gray · df07ca73 · Sep 30, 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 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.

AI review queuedTemporary Seed Names does not fit as menu item on Mk4 & Mk5by scgbckbone · 7243a6dd · Sep 30, 2026 · 2 filesMessage 30 · OpaqueInformational 15Details
Commit message · scgbckbone

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

30/100 · OpaqueMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body! Contains work-in-progress language
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100

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.

AI review queuedtest fixesby scgbckbone · 33525668 · Sep 29, 2026 · 5 filesMessage 0 · OpaqueInformational 12Details
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 12/100

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 simulator-only SE2 data in a separate pretend storage key. There is no change to real firmware security behavior.

Security candidateAllow activation of calculated Codex32 secretsby scgbckbone · 16b33e85 · Sep 29, 2026 · 4 filesMessage 45 · ThinLow 33Details
Commit message · scgbckbone

Allow activation of calculated Codex32 secrets

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

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 for legitimate seed setup, not a fix for an attack. The change only affects how a user chooses to turn a valid secret into their wallet, and it still requires the user to confirm the action. There is no direct evidence in the commit that this resolves a security vulnerability.

AI review queuedversion bumpby Peter D. Gray · 97719c6b · Sep 28, 2026 · 3 filesMessage 18 · OpaqueInformational 15Details
Commit message · Peter D. Gray

version bump

18/100 · OpaqueMessage clarity
✓ Subject identifies a change! 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 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 entries. There are no code changes, no bug fixes, and no security-relevant modifications in the diff itself.

Security candidateRestrict signing and Teleport retry QR scans to expected typesby scgbckbone · fcc0dc96 · Sep 28, 2026 · 7 filesMessage 50 · ThinHigh 78Details
Commit message · scgbckbone

Restrict signing and Teleport retry QR scans to expected types

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing boundaryseed or entropy path
AI analysis · High 78/100

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 shown in the QR code. The fix restricts those screens so they only accept the specific QR types they expect (a PSBT file for signing, or a Key Teleport code), and rejects seed/private-key QR codes. A related assertion that protects the master seed was also tightened.

Security candidateWarn before risky firmware upgradesby scgbckbone · 5c13be46 · Sep 28, 2026 · 3 filesMessage 45 · ThinLow 37Details
Commit message · scgbckbone

Warn before risky firmware upgrades

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

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 downgrade). It does not block these installs; it only makes the user confirm they understand the extra risk. The change is defensive and improves security by reducing the chance a user accidentally installs risky firmware.

AI review queuedShow Seed Vault names for temporary seedsby scgbckbone · 5a18e566 · Sep 25, 2026 · 5 filesMessage 25 · OpaqueInformational 15Details
Commit message · scgbckbone

Show Seed Vault names for 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 · Informational 15/100

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 security-relevant behavior change.

Security candidateCodex32 & Shamir Secret Sharingby scgbckbone · 571f0338 · Sep 24, 2026 · 40 filesMessage 35 · OpaqueInformational 15Details
Commit message · scgbckbone

Codex32 & Shamir Secret Sharing

35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
cryptography-sensitive pathseed or entropy pathsigning or wallet pathparser or protocol path
AI analysis · Informational 15/100

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 extensions (CW1 for BIP-39 entropy and CX1 for extended private keys). The commit also adds documentation, conformance vectors, and many tests. There is no indication of a security bug or vulnerability fix; it is a new feature implementation.

Security candidateHarden PSBTv2 parsingby scgbckbone · 5e0dbd0e · Sep 11, 2026 · 3 filesMessage 28 · OpaqueModerate 59Details
Commit message · scgbckbone

Harden PSBTv2 parsing

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

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 have none, badly encoded input/output counts, and PSBTv2 files that are missing the required global version field. These are defensive hardening fixes rather than a single obvious exploit, but they close paths where a malicious or malformed PSBT could confuse the wallet's transaction parser.

Security candidatePSBTv2 per input required lock time calculationby scgbckbone · 2ea2e791 · Sep 6, 2026 · 6 filesMessage 45 · ThinLow 34Details
Commit message · scgbckbone

PSBTv2 per input required lock time calculation

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

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 transaction lock time from these per-input requirements, which could cause it to sign transactions with the wrong lock time or reject valid ones. The patch implements the BIP-370 rule: if any input requires a lock time, the transaction's final lock time must be the most restrictive (maximum) of those requirements, overriding any fallback. This is a correctness/feature fix rather than a remote exploit, but incorrect lock-time handling could in theory let a malicious co-signer or wallet software trick a user into signing a transaction that becomes spendable earlier or later than expected.

AI review queuedAdd regression test for non-object JSON message-sign inputby copilot-swe-agent[bot] · adb7baa8 · Sep 5, 2026 · 1 fileMessage 91 · StrongLow 46Details
Commit message · copilot-swe-agent[bot]

Add regression test for non-object JSON message-sign input

Test requested in review on Coldcard/firmware#808: valid JSON that is not
an object (or lacks the "msg" key) must produce a clean failure story,
never a device crash.

Co-authored-by: Amiga500 <16525337+Amiga500@users.noreply.github.com>

91/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
fuzzing or regression evidencesecond-pass: broader security terminology
AI analysis · Low 46/100

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), or a JSON object missing the required 'msg' key, the device shows a clean error message instead of crashing. The commit itself does not change any firmware code, so it does not fix or introduce a vulnerability directly. It is a regression test requested during review of an earlier change, likely to make sure a previous fix stays effective.

Security candidatehygiene: duress wallet activate - wipe before getting slot databy scgbckbone · aa645247 · Sep 4, 2026 · 1 fileMessage 50 · ThinModerate 56Details
Commit message · scgbckbone

hygiene: duress wallet activate - wipe before getting slot data

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

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 which sensitive wallet data could remain in memory if the device is in Delta Mode (a limited, coerced-access mode). There is no direct evidence in the commit that an actual leak was exploited; it reads as a precautionary hardening change.

AI review queuedOVC clear stale outputs from new_outputsby scgbckbone · 62163ccd · Sep 4, 2026 · 1 fileMessage 45 · ThinLow 41Details
Commit message · scgbckbone

OVC clear stale outputs from new_outputs

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

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 previous signing attempt that failed or was aborted. If stale records remained, they could potentially confuse the wallet's checks about where money is going, which in rare cases might affect user-facing warnings or transaction validation.