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

AI review queuedDrop ValueError message string to save flash spaceby copilot-swe-agent[bot] · dc89513c · Sep 3, 2026 · 1 fileMessage 65 · AdequateInformational 15Details
Commit message · copilot-swe-agent[bot]

Drop ValueError message string to save flash space

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

65/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit removes a human-readable error message from a ValueError exception to reduce the amount of flash storage used by the firmware. It is a minor code cleanup and does not change the security behavior of the code. The function still raises an exception when invalid JSON input is provided; only the descriptive text is dropped.

AI review queuedAdd changelog entry for msgsign JSON crash fixby copilot-swe-agent[bot] · 07afee0d · Sep 3, 2026 · 1 fileMessage 60 · AdequateLow 49Details
Commit message · copilot-swe-agent[bot]

Add changelog entry for msgsign JSON crash fix

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

60/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
Why it was queued
documentation-only discountsecond-pass: broader security terminology
AI analysis · Low 49/100

This commit only adds a changelog note saying a previous fix stopped the COLDCARD hardware wallet from crashing when a message-signing request was valid JSON but not a JSON object (for example, a number or string instead of a dictionary). The actual code fix is not shown here, so we can only judge the issue from the changelog description. It appears to be a denial-of-service-style crash affecting message signing over NFC, QR, or SD card JSON files.

AI review queuedFix uncaught AttributeError on non-object JSON in parse_msg_sign_requestby copilot-swe-agent[bot] · d55ddbce · Sep 3, 2026 · 1 fileMessage 65 · AdequateInformational 23Details
Commit message · copilot-swe-agent[bot]

Fix uncaught AttributeError on non-object JSON in parse_msg_sign_request

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

65/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 23/100

This commit fixes a bug where the COLDCARD firmware's message-signing feature would crash with an uncaught error if a user supplied valid JSON that wasn't a structured object (for example, a plain number, string, list, or null). The fix checks the parsed JSON type and raises a proper, handled error instead of letting an AttributeError propagate. There is no direct evidence in the commit that this is exploitable for security harm, but unhandled exceptions can sometimes cause unexpected device behavior or denial of service.

AI review queuedSigned for mk release.by Peter D. Gray · e6d01c36 · Sep 3, 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 (signatures.txt) for the COLDCARD firmware. It adds two new file hashes for a v5.6.2-mk release and refreshes the PGP signature covering the file. There are no code changes, no bug fixes, and no security-relevant modifications visible in the diff.

AI review queuedSigned for q1 release.by Peter D. Gray · a310e1dd · Sep 3, 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 release signature file. It refreshes SHA-256 hashes for changelog files and adds hashes for two new firmware release files, then re-signs the file with a PGP signature. There are no code changes, no bug fixes, and no security-relevant content in the diff itself.

AI review queuedupdate block heightby Peter D. Gray · 3caf599e · Sep 3, 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 965,337 to 965,338. It is a routine, automatically generated data refresh with no code logic changes and no apparent security relevance.

AI review queuednew policy w blank linesby Peter D. Gray · 3d8f90f1 · Sep 3, 2026 · 1 fileMessage 38 · OpaqueInformational 15Details
Commit message · Peter D. Gray

new policy w blank lines

38/100 · OpaqueMessage clarity
✓ Subject identifies a change✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
documentation-only discountsecond-pass: opaque commit message
AI analysis · Informational 15/100

This commit only edits the project's internal release notes file. It replaces a detailed list of upcoming changes with placeholder 'tbd' entries and adds a note asking contributors to leave blank lines between additions. There are no code changes and no security relevance in the commit itself.

AI review queuedupdate for new releaseby Peter D. Gray · ea2b89bf · Sep 3, 2026 · 4 filesMessage 28 · OpaqueModerate 58Details
Commit message · Peter D. Gray

update for new release

28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
documentation-only discountsecond-pass: opaque commit message
AI analysis · Moderate 58/100

This commit is a release-notes-only update for the COLDCARD hardware wallet firmware. It moves many security-relevant bug fixes and hardening items from the current changelog into the historical release notes for versions 5.6.1 and 1.5.1Q, and adds a new set of notes for versions 5.6.2 and 1.5.2Q. The actual code changes are not present in the diff, only descriptions of them. The described issues include USB data leaks, PSBT tampering, firmware-update bypasses, virtual-disk file parsing flaws, and duress-wallet exposure in Delta Mode. Because we cannot see the patches themselves, we can only assess the claimed severity, not verify the fixes.

AI review queuedupdate block heightby Peter D. Gray · 15deb2f6 · Sep 3, 2026 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · Peter D. Gray

update block height

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

This commit simply updates a stored Bitcoin blockchain height number from 963,314 to 965,337, along with its timestamp. It is an automatic, routine data refresh with no code logic changes and no apparent security relevance.

Security candidatebugfix: report staged firmware modification at upgrade approvalby scgbckbone · ef73cf58 · Sep 3, 2026 · 4 filesMessage 73 · AdequateModerate 59Details
Commit message · scgbckbone

bugfix: report staged firmware modification at upgrade approval

- FirmwareUpgradeRequest: fail with "Firmware modified" story instead of
bare assert when PSRAM write counter moved after staging
- main_pin_changer: assert no temporary wallet is active (menu already
hides the item; defense in depth)
- test_upgrades: assert tamper abort shows the failure message
- test_ccc: drop stale CCCFeature.last_fail_reason resets

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
authentication path
AI analysis · Moderate 59/100

This commit fixes a bug in the COLDCARD firmware upgrade process. Previously, if someone tampered with the staged firmware after the user saw the approval prompt but before they confirmed, the device would crash with a bare internal error (assert). Now it cleanly aborts and tells the user 'Firmware modified'. The commit also adds a small extra safety check in the main PIN change flow to ensure no temporary wallet is active, and updates tests accordingly.

AI review queuedbump ckcc to latest masterby scgbckbone · ec1c9417 · Sep 2, 2026 · 1 fileMessage 45 · ThinInformational 2Details
Commit message · scgbckbone

bump 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 2/100

This commit only updates a linked external code library (a Git submodule called ckcc-protocol) to a newer version. The actual code changes inside that library are not shown in the commit diff, and no security-related information was provided by the project or any verified source. On its own, this single-line submodule bump tells us nothing about whether a security issue was fixed or introduced.

AI review queuedtweaksby Peter D. Gray · e166ffdd · Sep 2, 2026 · 1 fileMessage 0 · OpaqueInformational 15Details
Commit message · Peter D. Gray

tweaks

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 the draft release changelog file. It rewords two upcoming feature descriptions and fixes line wrapping for another entry. No source code, firmware logic, or security behavior was changed.

Security candidatebugfix: reject non-ASCII BIP-39 passphrasesby scgbckbone · c1a67660 · Sep 2, 2026 · 7 filesMessage 45 · ThinModerate 62Details
Commit message · scgbckbone

bugfix: reject non-ASCII BIP-39 passphrases

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
access controlcryptography-sensitive pathseed or entropy path
AI analysis · Moderate 62/100

This update fixes a bug where COLDCARD wallets would accept BIP-39 passphrases containing non-ASCII characters (like accented letters or emojis) or non-printable characters. Because different wallet software normalizes such characters differently, the same passphrase could silently produce a different wallet address on COLDCARD than on another app. The fix now rejects those passphrases outright, preventing users from accidentally creating funds they later cannot access or reconcile with other wallets.

Security candidatebugfix: capture single-sig segwit changeby scgbckbone · 8979a8a5 · Sep 2, 2026 · 6 filesMessage 60 · AdequateHigh 74Details
Commit message · scgbckbone

bugfix: capture single-sig segwit change
bugfix: defer OVC persistence until signing
enhancement: improve OVC implementation and size 30 -> 128

60/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
Why it was queued
signing boundarycryptography-sensitive pathsigning or wallet pathauthentication path
AI analysis · High 74/100

This commit fixes two related security bugs in the COLDCARD hardware wallet's protection against a known 'BIP-143 amount swap' attack. First, the wallet was recording the claimed amount of a segwit input to its secure cache as soon as a transaction was previewed, even if the user later cancelled without signing. A malicious co-signer could therefore 'poison' the cache with a wrong amount and later prevent the owner from spending that coin. Second, single-signature segwit change outputs created by transactions the user signed were not being added to the cache, so an attacker could later trick the wallet into signing a spend that understated the change amount. The patch defers cache writes until after a signature is actually produced, and captures single-sig segwit change amounts at finalize time. It also expands the cache size from 30 to 128 entries.

Security candidatebugfix: Reject duplicate singleton PSBT keysby scgbckbone · cb6df8da · Sep 2, 2026 · 3 filesMessage 45 · ThinModerate 66Details
Commit message · scgbckbone

bugfix: Reject duplicate singleton PSBT keys

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 · Moderate 66/100

This update fixes a bug in how the COLDCARD wallet reads PSBT files (the standard format for passing Bitcoin transactions between devices). Previously, if a PSBT contained the same special 'singleton' key twice in the same section, the device might silently use the second value. Now it immediately rejects the file. Duplicate singleton keys could let a malicious transaction tool trick the wallet into using one value while a human reviewer sees another, potentially causing the wrong amount or destination to be signed.

AI review queuedadd commentby Peter D. Gray · b2a47fc9 · Sep 1, 2026 · 1 fileMessage 0 · OpaqueInformational 15Details
Commit message · Peter D. Gray

add comment

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

This commit only adds a plain-language comment ('# 10 years') next to an existing constant that sets how far in the future a transaction's locktime can be. No code behavior changed.

Security candidateWipe on duress-secret view/activate in Delta Modeby scgbckbone · 3ad73025 · Sep 1, 2026 · 3 filesMessage 68 · AdequateHigh 76Details
Commit message · scgbckbone

Wipe on duress-secret view/activate in Delta Mode

In Delta Mode, the Trick PINs menu allowed a coercer to (a) press (6) to read
a duress wallet's full seed words / XPRV off screen, and (b) Activate Wallet to
load the duress secret as the active temporary seed -- all without a wipe. Every
other secret-revealing flow calls wipe_if_deltamode(); these two paths were
missed. The master seed itself is safe (hardened derivation), but the duress
wallet's funds and the user's deniability were exposed.

Keep menu browsing working (Delta Mode should look like normal operation), but
call wipe_if_deltamode() before the (6) viewer reads the slot and before
Activate Wallet applies the secret.

Add test_deltamode_duress_secret_view_wipes: browsing the menu works in delta
mode, but viewing the duress secret and activating the wallet each trigger a
wipe. Verified to fail pre-patch (no wipe) and pass with the fix.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
access controldefensive validationauthentication path
AI analysis · High 76/100

This commit fixes a security bug in the COLDCARD hardware wallet's 'Delta Mode' duress feature. Delta Mode is designed to make the device look normal while silently protecting secrets. Previously, a coercer could force someone to open the Trick PINs menu and either view the full seed words of a duress wallet, or activate that wallet, without triggering a wipe. This exposed the duress wallet's funds and weakened the user's deniability. The fix makes both actions trigger a secure wipe when in Delta Mode, matching how other secret-revealing flows already behaved. Browsing the menu still works so Delta Mode remains plausible.

Security candidateReject out-of-range txn version on PSBTv2 pathby scgbckbone · e81b64bb · Sep 1, 2026 · 3 filesMessage 68 · AdequateModerate 64Details
Commit message · scgbckbone

Reject out-of-range txn version on PSBTv2 path

The `bad txn version` check (`txn_version in {0,1,2,3}`) lives in
parse_txn(), which only runs for PSBTv0. On the PSBTv2 path read_psbt()
skips parse_txn(), so PSBT_GLOBAL_TX_VERSION was used unvalidated: a v2
PSBT with nVersion 4 (or a negative value) could be approved and signed,
producing a transaction the network will not relay.

validate() already enforces PoR-specific versions (0 only for BIP-322,
{0,2} for PoR txns) but had no upper bound for ordinary transactions. Add
the matching non-PoR bound (txn_version in {1,2,3}) so both v0 and v2
reject out-of-range versions while the BIP-322 PoR path is unchanged.

Add test_psbt_v2_bad_txn_version (versions 4, -1, 100 rejected on v2).
Verified to fail pre-patch (v2 reaches 'OK TO SEND?') and pass with the
fix; full test_bip322.py suite still passes.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
secret or key materialsigning boundarydefensive validationsigning or wallet path
AI analysis · Moderate 64/100

This fix closes a gap where COLDCARD would approve and sign a Bitcoin transaction with an invalid version number if the transaction was packaged in the newer PSBTv2 format. For PSBTv0, such bad versions were already rejected, but the PSBTv2 code path skipped that check. The result could be a signed transaction that the Bitcoin network refuses to relay, potentially trapping funds or breaking wallet workflows. The patch adds the same version-number sanity check to the shared validation routine so both PSBT versions are protected.

AI review queuedWarn for far-future block-height locktimeby scgbckbone · 4b07fb56 · Sep 1, 2026 · 3 filesMessage 45 · ThinLow 29Details
Commit message · scgbckbone

Warn for far-future block-height locktime

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

This change adds a warning when a Bitcoin transaction's locktime is set to a block height more than 10 years in the future. It does not block the transaction but alerts the user, helping catch potential tricks where a transaction is made unspendable for a very long time without the user noticing.

Security candidateUse one PSRAM write counterby scgbckbone · 2469c0f1 · Sep 1, 2026 · 6 filesMessage 45 · ThinModerate 58Details
Commit message · scgbckbone

Use one PSRAM write counter

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 · Moderate 58/100

This commit simplifies how the COLDCARD firmware tracks writes to its external PSRAM memory chip. Previously, the firmware kept two separate counters: one for transaction (TXN) data and one for firmware upgrade images. The change merges them into a single counter that increments on any PSRAM write. The goal is to make it harder for an attacker to silently modify data after the user has reviewed it, by detecting any later write to PSRAM. It is a defensive hardening change rather than a fix for a known active attack, and the commit message does not describe a specific vulnerability.

Security candidateMerge pull request #773 from scgbckbone/bugfix/bip322-por-foreign-inputs-publicby doc-hex · 84d185de · Sep 1, 2026 · 3 filesMessage 73 · AdequateModerate 64Details
Commit message · doc-hex

Merge pull request #773 from scgbckbone/bugfix/bip322-por-foreign-inputs-public

bugfix: reject foreign inputs from BIP322 proofs of reserves

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
secret or key materialcryptography-sensitive pathsigning or wallet pathmerge-commit duplicate discount
AI analysis · Moderate 64/100

This update fixes a bug in COLDCARD's handling of BIP-322 Proof of Reserves (POR). A maliciously crafted proof could include a foreign (not owned by the device) Bitcoin input disguised to look like the device's own input using a fake key path and a partial signature. Before the fix, the device might have accepted such a foreign input in a POR, potentially allowing someone to falsely inflate or manipulate a proof of reserves. After the fix, the device rejects any POR that contains inputs it is not actually going to sign, beyond the required first input.

AI review queuedValidate wrapped-segwit redeem script contentsby scgbckbone · b03fccb9 · Sep 1, 2026 · 3 filesMessage 78 · AdequateHigh 73Details
Commit message · scgbckbone

Validate wrapped-segwit redeem script contents

Presence of the redeem script is not enough: the input is signed as
segwit based on the witness script, while witness_utxo_is_provably_segwit
decides amount trust from the redeem script field. A present-but-wrong
redeem script passed the new presence check yet still failed the
provably-segwit test, leaving the fee unverifiable with only a warning
before approval - the same unknown-fee hole as the missing case.

Require the redeem script to be exactly the P2WSH wrapper of the
witness script. Add regression test with a junk redeem script (verified
to reach the approval UX without this fix), and update the changelog.

78/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
defensive validationfuzzing or regression evidencesigning or wallet pathsecond-pass: near security thresholdsecond-pass: security-sensitive path
AI analysis · High 73/100

This update tightens a recently added safety check in the COLDCARD firmware. For a specific type of Bitcoin address (P2SH-P2WSH), the device now verifies that the redeem script provided in the transaction data exactly matches the expected wrapper around the witness script. Previously, a malformed or junk redeem script could slip past the check, causing the device to sign the transaction while being unable to reliably verify the input amount and thus the fee. That could let an attacker trick a user into approving a transaction with a hidden or excessive fee.

Security candidatetesting: stabilize simulator multiprocess runsby scgbckbone · 9091ce62 · Sep 1, 2026 · 10 filesMessage 55 · ThinInformational 15Details
Commit message · scgbckbone

testing: stabilize simulator multiprocess runs

55/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
cryptography-sensitive pathsigning or wallet path
AI analysis · Informational 15/100

This commit only changes test scripts and test infrastructure for the COLDCARD firmware simulator. It adjusts timeouts, adds helper functions for waiting on screen text, fixes test flakiness, and tweaks how tests are split across parallel jobs. There are no changes to the actual firmware code that runs on the device, so this cannot affect real users or introduce a security vulnerability in the product itself.

Security candidateHarden BIP322 POR foreign-input checkby scgbckbone · 8dba7380 · Sep 1, 2026 · 3 filesMessage 83 · StrongHigh 76Details
Commit message · scgbckbone

Harden BIP322 POR foreign-input check

Gate on required_key instead of num_our_keys: keypath metadata is
attacker-controlled, and the zero-xfp placeholder is rewritten to our
fingerprint on the fly, so a foreign input carrying a forged keypath
plus a partial signature looked both 'ours' and already-signed, and
was never rejected nor signed - while the SIGHASH_ALL signature over
input zero still committed to its prevout.

required_key is only set after the input's pubkey/scripts validate
against our seed or WIF store, so gating on it fails closed for all
three variants: no keypaths, forged keypaths, and presigned inputs.

Add regression test with a foreign UTXO (different seed) carrying a
zero-xfp keypath and a garbage partial signature.

83/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Names security-relevant behavior explicitly
Why it was queued
explicit security languagesecret or key materialsigning boundarydefensive validationfuzzing or regression evidencecryptography-sensitive pathsigning or wallet path
AI analysis · High 76/100

This commit fixes a bug in COLDCARD's BIP-322 Proof of Reserves (POR) feature. POR lets a wallet prove it controls certain bitcoins without moving them. The bug allowed an attacker to include someone else's unspent coin in the proof by disguising it with fake key-path metadata and a bogus partial signature. The device would then treat that foreign input as already signed and belonging to the wallet, making the proof falsely claim control of funds the wallet does not actually own. The fix checks that the device can actually derive the required signing key for each input, rather than relying on attacker-controlled key-path data.

AI review queuedSigned for Edge release.by Peter D. Gray · 8ff1a0fa · Aug 31, 2026 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · Peter D. Gray

Signed for Edge 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 cryptographic hashes for two new firmware files and updates a hash for a changelog file, then re-signs the file with a PGP signature. There are no code changes, no bug fixes, and no security-related content in the commit message or diff.