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.

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.

AI review queuedchangelog: note temporary-only wallet import fixesby scgbckbone · 6d5788b0 · Aug 31, 2026 · 1 fileMessage 30 · OpaqueLow 40Details
Commit message · scgbckbone

changelog: note temporary-only wallet import fixes

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
documentation-only discountsecond-pass: opaque commit message
AI analysis · Low 40/100

This is a one-line changelog note, not the actual code fix. It describes a bug where, if the main wallet was empty and a temporary seed was active, importing wallets or restoring backups would incorrectly become permanent changes to the master wallet instead of staying temporary. The note suggests the real fix happened elsewhere, so this commit alone does not show what code changed or how severe the underlying bug is.

Security candidatetest: cover seedless temporary backup restoresby scgbckbone · f062289b · Aug 31, 2026 · 1 fileMessage 47 · ThinInformational 12Details
Commit message · scgbckbone

test: cover seedless temporary backup restores

47/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Mentions testing or verification! No meaningful explanatory body! Contains work-in-progress language
Why it was queued
seed or entropy path
AI analysis · Informational 12/100

This commit only adds a new automated test for the COLDCARD hardware wallet. It checks that a backup file can be restored as a temporary seed while the device is in a 'seedless' state. There is no change to the actual wallet firmware code, only to the test suite, so it does not introduce or fix a security vulnerability by itself.

Security candidatebugfix: guard low-level master secret writesby scgbckbone · 30a05819 · Aug 31, 2026 · 2 filesMessage 45 · ThinModerate 63Details
Commit message · scgbckbone

bugfix: guard low-level master secret writes

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

This commit adds safety checks to prevent the COLDCARD wallet from overwriting or restoring the main master secret while a temporary seed is active. Without these guards, a low-level restore or seed-setting operation could potentially replace the real wallet seed while the device is operating under a temporary seed, leading to confusion or loss of funds. The fix adds explicit assertions that block these operations when a temporary seed is in use.

Security candidatebugfix: recognize temporary secrets in teleport and Seed XORby scgbckbone · 8594d6be · Aug 31, 2026 · 2 filesMessage 30 · OpaqueModerate 59Details
Commit message · scgbckbone

bugfix: recognize temporary secrets in teleport and Seed XOR

30/100 · OpaqueMessage clarity
✓ Specific, 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 · Moderate 59/100

This commit fixes a bug in the COLDCARD hardware wallet where two seed-management features (teleport and Seed XOR) did not properly recognize temporary/ephemeral wallets. Previously, the code only checked whether the secure element (SE) held a permanent seed. If a user was operating from a temporary seed while the SE was blank, the device treated the wallet as empty. In teleport, this could cause an incoming seed to overwrite the current temporary seed as the master seed. In Seed XOR, it could cause the reconstructed seed to be saved as the master seed or fail to warn that the result would be temporary. The fix makes both features check whether any secret—stored or temporary—is active.

Security candidatebugfix: keep CKCC backup restores temporaryby scgbckbone · 10456538 · Aug 31, 2026 · 1 fileMessage 25 · OpaqueLow 44Details
Commit message · scgbckbone

bugfix: keep CKCC backup restores temporary

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
authentication path
AI analysis · Low 44/100

This commit fixes a logic bug in how COLDCARD decides whether to restore a backup as a temporary wallet or as the device's main wallet. Previously, the code checked whether the master secret was blank using an older method. The fix changes that check to use a more accurate function that detects whether any secrets are active. The risk is that a backup could be restored to the wrong place—permanently overwriting the main wallet when the user expected a temporary restore, or failing to create a temporary wallet when one was intended. The commit message calls this a bugfix but does not describe it as a security issue.

AI review queuedbugfix: keep developer backup restores temporaryby scgbckbone · 6340a5f8 · Aug 31, 2026 · 1 fileMessage 25 · OpaqueModerate 58Details
Commit message · scgbckbone

bugfix: keep developer backup restores temporary

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

This fix corrects a developer-only backup restore feature so that it always creates a temporary wallet when any real wallet secret is already stored on the device. Before the fix, the restore could report success while silently failing to overwrite the active wallet because the operation was treated as a no-op. The change prevents misleading success reports and accidental or malicious overwrites of the real wallet.

AI review queuedbugfix: guard permanent key imports with temporary walletsby scgbckbone · 2504cde0 · Aug 31, 2026 · 2 filesMessage 30 · OpaqueModerate 58Details
Commit message · scgbckbone

bugfix: guard permanent key imports with temporary wallets

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
signing or wallet pathsecond-pass: opaque commit messagesecond-pass: security-sensitive path
AI analysis · Moderate 58/100

This commit fixes a bug in the COLDCARD hardware wallet where importing a permanent private key could incorrectly be allowed while a temporary wallet was still active. The old check only verified that the main secure-element secret was blank, but that condition can be true even when a temporary wallet is loaded. The new check ensures no secret of any kind is active before a permanent key import proceeds. If the bug were triggered, a permanent import might overwrite or coexist unexpectedly with an active temporary wallet, potentially confusing the user about which wallet is in control or causing loss of funds if the wrong wallet is used.

Security candidateKeep TRNG words together on Qby scgbckbone · 23e7e70c · Aug 31, 2026 · 2 filesMessage 45 · ThinInformational 19Details
Commit message · scgbckbone

Keep TRNG words together on Q

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

This commit fixes a display layout problem on the COLDCARD Q hardware wallet. When showing 24 special 'TRNG words' on the Q's screen, the list was being split across two screens in a confusing way, so a user might not see all words together. The change adds a hint telling the user to scroll, and adjusts the text so the 24-word grid starts cleanly on a new screen. It is a usability fix for viewing sensitive seed material, not a fix for a code-execution or theft vulnerability.

Security candidateAdd seed mix verifierby scgbckbone · 27535c89 · Aug 31, 2026 · 2 filesMessage 28 · OpaqueInformational 15Details
Commit message · scgbckbone

Add seed mix verifier

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

This commit adds a new standalone Python helper script and its tests. The script lets a user independently verify how COLDCARD mixes its built-in random words with dice rolls or coin flips to create a seed. It does not change any firmware code, wallet behavior, or cryptographic logic in the device itself. There is no indication this is a security fix or that it addresses any vulnerability.

Lower-prioritytesting: write multisig config to card before the picker scans itby Kyle 🐆 · 948dc108 · Aug 29, 2026 · 1 fileMessage 60 · AdequateTriage 0Details
Commit message · Kyle 🐆

testing: write multisig config to card before the picker scans it

60/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
Security candidatebugfix: hide main PIN change for temporary walletsby scgbckbone · efe407a9 · Aug 28, 2026 · 3 filesMessage 30 · OpaqueLow 38Details
Commit message · scgbckbone

bugfix: hide main PIN change for temporary wallets

30/100 · OpaqueMessage clarity
✓ Specific, 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
access controlauthentication path
AI analysis · Low 38/100

This update fixes a user-interface bug where the 'Change Main PIN' option remained visible while using a temporary wallet or a BIP-39 passphrase wallet. Changing the main PIN from a temporary wallet could confuse users or lead to unexpected wallet state, so the option is now hidden in those modes. It is a straightforward menu fix rather than a cryptographic flaw.

Security candidateReject foreign BIP322 reserve inputsby scgbckbone · 803bd04d · Aug 27, 2026 · 3 filesMessage 45 · ThinModerate 62Details
Commit message · scgbckbone

Reject foreign BIP322 reserve inputs

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
secret or key materialcryptography-sensitive pathsigning or wallet path
AI analysis · Moderate 62/100

This update fixes a bug in the COLDCARD hardware wallet's handling of BIP-322 Proof of Reserves (PoR) transactions. Previously, the wallet could be presented with a PoR PSBT containing extra 'foreign' inputs that it did not control, and it would not clearly reject the transaction. This could allow a malicious or malformed PoR request to include unrelated inputs, potentially misleading the user or weakening the proof. The fix now rejects any BIP-322 PoR PSBT that contains inputs not belonging to the wallet.

Lower-prioritydocs: credit VirtDisk tamper reportby scgbckbone · 34659cee · Aug 27, 2026 · 1 fileMessage 57 · ThinTriage 0Details
Commit message · scgbckbone

docs: credit VirtDisk tamper report

57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
documentation-only discount
Security candidatebugfix: use write counter for firmware approvalby scgbckbone · 11fcadc6 · Aug 27, 2026 · 5 filesMessage 45 · ThinHigh 74Details
Commit message · scgbckbone

bugfix: use write counter for firmware approval

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

This update fixes a security bug in the COLDCARD hardware wallet's firmware upgrade process. Previously, an attacker could potentially swap the staged firmware image while the user was still reviewing the upgrade approval screen. The device now uses a write counter to detect if the staged firmware image was overwritten after it was shown to the user, and aborts the upgrade if so. The change log credits Huzaifa Jawaid for the finding.

Security candidatebugfix: restrict HSM BIP322 WIF signingby scgbckbone · fb2f6da7 · Aug 27, 2026 · 3 filesMessage 45 · ThinModerate 62Details
Commit message · scgbckbone

bugfix: restrict HSM BIP322 WIF signing

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
secret or key materialsigning boundary
AI analysis · Moderate 62/100

This commit fixes a bug in the COLDCARD HSM (High-Security Mode) where signing BIP-322 messages using private keys stored in the device's WIF Store could bypass the message-signing policy. Previously, such signatures may have been allowed even when the policy only permitted specific derivation paths. The fix now requires the HSM policy to explicitly allow 'any' path before WIF Store keys can be used for BIP-322 signing. This is a security-hardening bugfix for a niche but sensitive code path.

Security candidatebugfix: bind firmware upgrade approval to staged imageby scgbckbone · 1d01d533 · Aug 26, 2026 · 2 filesMessage 83 · StrongHigh 76Details
Commit message · scgbckbone

bugfix: bind firmware upgrade approval to staged image

FirmwareUpgradeRequest renders the consent screen from a header
snapshot captured at upload time, but hands the flash operation a
live PSRAM window. A second upload is permitted while the approval
is displayed (check_busy allow-lists FirmwareUpgradeRequest), and a
raw image upload without the legacy trailer never re-enters
authorize_upgrade — so the staged bytes can be replaced after review
without any error.

Record a digest of the staged image at approval time and re-verify
immediately before pa.firmware_upgrade(), failing closed on mismatch.
Mirrors the staged-bytes guard ApproveTransaction already has.

Add a regression test that uploads image A, gets the approval screen,
uploads image B as a raw image (no trailer), approves, and asserts
the upgrade aborts.

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
fuzzing or regression evidenceauthentication path
AI analysis · High 76/100

This commit fixes a security bug in the COLDCARD hardware wallet's firmware update process. Previously, while the user was looking at the approval screen for one firmware file, a second file could be silently uploaded and replace the first one. If the user approved, the second (unreviewed) firmware would be installed instead of the one they saw on screen. The fix records a fingerprint of the staged firmware at approval time and checks it again right before flashing, aborting if anything changed.

Security candidatebugfix: vdisk import bumps txn write countby scgbckbone · 39fa3547 · Aug 26, 2026 · 3 filesMessage 78 · AdequateModerate 67Details
Commit message · scgbckbone

bugfix: vdisk import bumps txn write count

The C VirtDisk importer memcpy's into the PSRAM TXN staging regions without going through PSRAMWrapper.write_at(), so txn_write_count is not bumped and the pre-signing re-hash takes its fast path over possibly-clobbered bytes.

Bump the counter and revoke any PSRAM lease before copy_file, so post-review tampering through the virtual disk is caught and stale staged bytes cannot be downloaded.

Make the simulator model copy_file as a direct PSRAM write, then exercise the real VirtDisk event path during a pending PSBT approval and verify signing aborts.

78/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
signing boundary
AI analysis · Moderate 67/100

This commit fixes a bug in the COLDCARD hardware wallet's virtual disk (VirtDisk) feature. When a user imported a file via the virtual disk, the firmware's fast C importer copied data directly into a sensitive memory area used to stage pending Bitcoin transactions. Because it bypassed the normal tracking mechanism, the wallet did not realize the transaction data had been touched. An attacker or malicious program with virtual disk access could therefore overwrite a transaction you were about to approve, and the wallet might sign the altered version instead of the one you reviewed on screen. The fix records the write, revokes any pending download lease, and adds a test proving the wallet now aborts signing when this happens.

AI review queuedbugfix: reject incomplete wrapped segwit inputsby scgbckbone · 28182e29 · Aug 26, 2026 · 3 filesMessage 45 · ThinHigh 72Details
Commit message · scgbckbone

bugfix: reject incomplete wrapped segwit inputs

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 update fixes a bug in the COLDCARD hardware wallet where a malformed Bitcoin transaction file (PSBT) could slip through if it described a wrapped SegWit input but left out a required piece of data called the redeem script. Without that script, the wallet could not correctly calculate the transaction's fee, which might let an attacker trick the user into approving a transaction that sends far more in fees than intended. The fix makes the wallet reject such malformed files outright.