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

Lower-prioritySECURITY.md: add responsible-disclosure link and security contactby @Bibo-dochex · a27b5abb · Aug 11, 2026 · 1 fileMessage 55 · ThinTriage 0Details
Commit message · @Bibo-dochex

SECURITY.md: add responsible-disclosure link and security contact

55/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Names security-relevant behavior explicitly! No meaningful explanatory body
Why it was queued
documentation-only discount
AI review queuedreviewby scgbckbone · 8c07dbe3 · Aug 10, 2026 · 1 fileMessage 0 · OpaqueInformational 15Details
Commit message · scgbckbone

review

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 updates documentation. It clarifies that a BIP39 passphrase wallet backup stores an extended private key (XPRV) rather than the seed words or passphrase, and adds version numbers for older firmware behavior. There is no code change and no security fix or vulnerability introduced.

Lower-prioritytest: wait for multiproc simulator readinessby scgbckbone · 39409e23 · Aug 10, 2026 · 1 fileMessage 67 · AdequateTriage 0Details
Commit message · scgbckbone

test: wait for multiproc simulator readiness

67/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Mentions testing or verification! No meaningful explanatory body
Security candidatedocument nested passphrase wallet handlingby scgbckbone · 8eafbb2a · Aug 10, 2026 · 1 fileMessage 45 · ThinLow 35Details
Commit message · scgbckbone

document nested passphrase wallet handling

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
access controldocumentation-only discount
AI analysis · Low 35/100

This commit only adds a single line to the changelog, describing a bugfix that was apparently already made elsewhere. The bug concerned how COLDCARD's 'View Seed Words' and backup features handled BIP-39 passphrase wallets when a passphrase was applied on top of a temporary seed. In that case, the device reportedly treated the master seed as the parent instead of the immediate temporary seed, potentially showing or backing up the wrong secret. Because the actual code change is not in this commit, we cannot directly verify the fix or assess its full security implications from this diff alone.

Security candidatecapture effective seed in backup workflowsby scgbckbone · 160bbb88 · Aug 8, 2026 · 12 filesMessage 45 · ThinLow 47Details
Commit message · scgbckbone

capture effective seed in backup workflows

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

This commit changes how COLDCARD backup, clone, and Key Teleport features handle temporary seeds and BIP-39 passphrases. Previously, users could sometimes back up the main wallet even when a passphrase or temporary seed was active. Now the device always backs up the wallet currently in effect and warns the user first. This is a security-hardening change that reduces the risk of accidentally exposing or archiving the wrong secret, but it is not a fix for an active remote exploit.

Security candidateshow effective seed in View Seed Wordsby scgbckbone · 36e6b5e3 · Aug 8, 2026 · 4 filesMessage 45 · ThinInformational 22Details
Commit message · scgbckbone

show effective seed in View Seed Words

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

This commit changes what the COLDCARD wallet displays on its 'View Seed Words' screen when a BIP-39 passphrase is active. Previously it showed the original 24 seed words plus a masked passphrase and the derived extended private key. Now it shows only the effective extended private key (and a note that a passphrase is in effect), hiding the underlying seed words. This is a deliberate UX/security hardening change, not a fix for an exploitable vulnerability.

Security candidatebugfix: wipe in deltamode before listing saved passphrasesby scgbckbone · 0e78b8e1 · Aug 8, 2026 · 2 filesMessage 50 · ThinHigh 71Details
Commit message · scgbckbone

bugfix: wipe in deltamode before listing saved passphrases

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

This commit fixes a bug in the COLDCARD hardware wallet where, when the device is in 'Delta Mode' (a special temporary operating mode), opening the list of saved BIP-39 passphrases would reveal the passphrases and wallet fingerprints instead of securely wiping the seed first. The fix adds a call to wipe the seed if Delta Mode is active before displaying the saved passphrase menu. This prevents sensitive secret material from being exposed on screen in a mode meant to limit what an attacker can see.

Security candidatecleanup: drop unused fetch() paramsby scgbckbone · 81685458 · Aug 8, 2026 · 1 fileMessage 45 · ThinInformational 15Details
Commit message · scgbckbone

cleanup: drop unused fetch() params

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

This commit removes unused parameters from an internal function called fetch() in the COLDCARD firmware. There is no evidence this change fixes or introduces a security issue; it is purely a code cleanup that simplifies the function signature and removes dead code paths.

Lower-priorityexclude schnorr/musig from libngu to save flash space; add adition macro NGU_STM32_EXTERNAL_RNG_GET; disable threads for unix portby scgbckbone · 0af2f5da · Aug 7, 2026 · 5 filesMessage 50 · ThinTriage 0Details
Commit message · scgbckbone

exclude schnorr/musig from libngu to save flash space; add adition macro NGU_STM32_EXTERNAL_RNG_GET; disable threads for unix port

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-prioritymacos: silence benign clang warnings so the build is cleanby Danilo · d9e7fe14 · Aug 6, 2026 · 1 fileMessage 85 · StrongTriage 0Details
Commit message · Danilo

macos: silence benign clang warnings so the build is clean

The unix build emitted 35 warnings under Apple clang 21, all of them
benign-by-design in upstream/third-party code:

25 -Wunused-but-set-variable py/{objfun,vm,objgenerator,
showbc,frozenmod}.c -- the
MP_BC_PRELUDE_*_DECODE macros
declare every prelude field,
callers read only some
4 -Warray-bounds py/vm.c -- deliberate negative
indexing off the VM stack
pointer, eg sp[-N + 1]
3 -Wgnu-folding-constant libngu/hash.c -- uint8_t
d[H_SIZE], const-folded, not a
real VLA
3 -Wunterminated-string-initialization extmod/moductypes.c and
secp256k1 -- fixed-size char
arrays that intentionally omit
the NUL

None indicates a defect, so suppress the classes rather than patch four
third-party trees.

Ordering matters and is the subtle part: -Wextra enables
-Wunterminated-string-initialization, so a -Wno- placed before the
-Wextra line is silently undone (-Wno-error= survived only because it
changes error status, not enablement). The suppressions therefore have
to come after -Wall/-Wextra, hence the reordering and the comment.

Verified: `make setup`, `make`, and mpy-cross all build with 0 compiler
warnings. The lone remaining line is a linker warning about the
CommandLineTools SDK's libSystem.tbd stub, which is not ours to fix.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode
Lower-priorityunix: stop building the unused bundled libffi in `make setup`by Danilo · e26e1eb5 · Aug 6, 2026 · 1 fileMessage 85 · StrongTriage 0Details
Commit message · Danilo

unix: stop building the unused bundled libffi in `make setup`

The `tools` target ran the port's `deplibs`, which builds both axtls and
the bundled lib/libffi. Only axtls is actually used: mpconfigport.mk sets
MICROPY_STANDALONE = 0, so the ffi module links the system libffi found
via pkg-config, and $(BUILD)/lib/libffi is never referenced.

Building it is not merely wasted time -- on macOS it fails outright:

clang: error: unsupported option '-print-multi-os-directory'
src/aarch64/sysv.S: error: invalid CFI advance_loc expression
make[4]: *** [src/aarch64/sysv.lo] Error 1

The failure went unnoticed because that recipe chains its steps with `;`
rather than `&&`, so the errors scroll past and setup still exits 0.

Depend on axtls directly. The resulting vanilla micropython is unchanged
-- both `import ffi` and `import ussl` still work.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode
Lower-prioritysim: keep running when there is no X11 displayby Danilo · aec8d053 · Aug 6, 2026 · 1 fileMessage 68 · AdequateTriage 0Details
Commit message · Danilo

sim: keep running when there is no X11 display

simulator.py spawns xterm purely to host the firmware's REPL console; the
Coldcard screen itself is drawn with SDL and needs no X11. On macOS without
XQuartz, xterm exits immediately ("DISPLAY is not set"), the main loop sees
xterm.poll() != None and breaks, and the simulator dies on startup before
you can use it.

Run the child directly when DISPLAY (or xterm) is missing. The simulated
screen, the /tmp/ckcc-simulator.sock link and `ckcc -x` all keep working;
only the separate console window is lost, and that is already unusable in
that situation. Behaviour with a working X11 display is unchanged.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Lower-prioritymacos: extend mpy patch for Apple clang 21 -Werror failuresby Danilo · 272b3f29 · Aug 6, 2026 · 1 fileMessage 73 · AdequateTriage 0Details
Commit message · Danilo

macos: extend mpy patch for Apple clang 21 -Werror failures

Two warnings that are new (or newly promoted) in Apple clang 21 break the
micropython build on macOS, both in code that is intentional upstream:

extmod/moductypes.c - char type2char[16] = "BbHhIiQq------fd" needs no
NUL terminator, but -Wunterminated-string-initialization flags it
py/emitnative.c - MP_STATIC_ASSERT expands to sizeof(char[1 - 2*!(cond)]),
which -Wgnu-folding-constant rejects as a folded VLA

Demote both to warnings, matching how this patch already handles the
other clang-version drift.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Lower-prioritytesting: bump pyscard to 2.3.1 so requirements install on swig 4.3+by Danilo · 07015188 · Aug 6, 2026 · 1 fileMessage 83 · StrongTriage 0Details
Commit message · Danilo

testing: bump pyscard to 2.3.1 so requirements install on swig 4.3+

pyscard 2.0.2 ships pre-generated SWIG sources that no longer compile
against swig >= 4.3 (clang: "use of undeclared identifier '$function'"
in smartcard/scard/scard_wrap.c), which broke `pip install -r
requirements.txt` entirely. 2.3.1 publishes cp313 wheels, so it installs
without invoking swig at all.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

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
documentation-only discount
Security candidateCredit BIP322 validation issue reporterby scgbckbone · 330bafc1 · Aug 6, 2026 · 1 fileMessage 45 · ThinInformational 15Details
Commit message · scgbckbone

Credit BIP322 validation issue reporter

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
secret or key materialdocumentation-only discount
AI analysis · Informational 15/100

This commit only adds a thank-you credit to an upcoming release changelog. It does not change any code, so it cannot by itself fix or introduce a security issue. The actual BIP-322 validation bugfix must have been made in a different, earlier commit.

Lower-priorityAdd SECURITY.md responsible-disclosure policyby spaceainot · fe77aa24 · Aug 6, 2026 · 1 fileMessage 50 · ThinTriage 0Details
Commit message · spaceainot

Add SECURITY.md responsible-disclosure policy

50/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Names security-relevant behavior explicitly! No meaningful explanatory body
Why it was queued
documentation-only discount
Lower-priorityBump libngu: SHA-256 Hash-DRBG replaces Yasmarangby scgbckbone · 7d53c9be · Aug 5, 2026 · 2 filesMessage 45 · ThinTriage 0Details
Commit message · scgbckbone

Bump libngu: SHA-256 Hash-DRBG replaces Yasmarang

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Security candidatebugfix: detect RNG_SR_SEIS and RNG_SR_SECS, retry safely, and fail closed on persistent faultsby scgbckbone · 82ced47a · Aug 5, 2026 · 5 filesMessage 50 · ThinModerate 66Details
Commit message · scgbckbone

bugfix: detect RNG_SR_SEIS and RNG_SR_SECS, retry safely, and fail closed on persistent faults

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 pathboot or update path
AI analysis · Moderate 66/100

This update fixes how the COLDCARD hardware wallet's random-number generator (RNG) handles rare hardware faults. Previously, the device could silently continue using weak or repeated random numbers if the RNG reported a seed error. Now it detects those error flags, tries a safe recovery a few times, and if the problem persists it stops with an error instead of producing bad randomness. Two keyboard drivers were also updated so a temporary RNG failure does not lock the user out before login.

Security candidatebugfix: harden callgate buffer boundsby scgbckbone · c0d27278 · Aug 5, 2026 · 2 filesMessage 45 · ThinHigh 70Details
Commit message · scgbckbone

bugfix: harden callgate buffer bounds

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

This commit fixes a buffer-validation bug in the COLDCARD Mk4 bootloader's secure callgate. The old code checked memory ranges using simple addition (address + length), which can overflow and trick the device into treating an attacker-controlled buffer as safe. The patch replaces those checks with subtraction-based math that cannot overflow, and also rejects negative input lengths. A security review by Karma-X is credited with the finding.

Security candidatebugfix: invalidate message signatures in Delta Modeby scgbckbone · 0f09d662 · Aug 5, 2026 · 2 filesMessage 50 · ThinModerate 65Details
Commit message · scgbckbone

bugfix: invalidate message signatures in Delta Mode

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing boundaryaccess controldefensive validationsigning or wallet path
AI analysis · Moderate 65/100

This update fixes a bug in the COLDCARD hardware wallet where signing a text message with the special 'Delta Mode' PIN would produce a signature that looked valid to anyone checking it. Delta Mode is a hidden feature that silently corrupts transaction signatures so attackers who force you to unlock your wallet cannot steal funds. The same protection was missing for message signatures, so an attacker could have tricked a victim into producing a seemingly valid signed message under duress. The fix makes message signatures produced in Delta Mode invalid, matching the existing behavior for transactions.

Security candidateexternal entropy required for CCC key and temporary seedsby scgbckbone · 7100bb66 · Aug 5, 2026 · 5 filesMessage 35 · OpaqueLow 46Details
Commit message · scgbckbone

external entropy required for CCC key and temporary seeds

35/100 · OpaqueMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Names security-relevant behavior explicitly! No meaningful explanatory body! Contains work-in-progress language! Opaque security-relevant change
Why it was queued
entropy or randomnessseed or entropy path
AI analysis · Low 46/100

This commit changes how COLDCARD creates two special types of secrets: temporary seeds and the 'CCC' co-signing key. Previously these were generated purely from the device's own random number generator. Now the user must add their own randomness (for example by mashing buttons, rolling dice, or flipping coins) before the secret is created. This makes it harder for an attacker who has somehow compromised the device's random generator to predict or control those secrets. It is a defensive hardening change, not a fix for a known active attack.

Security candidateWarn before dice-only seed generationby scgbckbone · 71763b2c · Aug 5, 2026 · 3 filesMessage 45 · ThinInformational 22Details
Commit message · scgbckbone

Warn before dice-only seed generation

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

This commit adds a warning screen before users create a Bitcoin wallet seed using only dice rolls. It tells users that no hardware randomness is added, and that the on-screen hash must be kept secret because anyone who sees it could recreate the wallet and steal funds. This is a user-experience and safety improvement, not a fix for a software vulnerability.

Security candidaterng: verify libngu bytes path reaches hardware driverby scgbckbone · 8570af2a · Aug 5, 2026 · 1 fileMessage 60 · AdequateLow 45Details
Commit message · scgbckbone

rng: verify libngu bytes path reaches hardware driver

60/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
entropy or randomness
AI analysis · Low 45/100

This commit adds build-time checks to ensure the firmware's random-number generator actually chains all the way down to the hardware chip. It does not fix a known exploit, but it prevents a future build misconfiguration from silently causing the wallet to use weaker random numbers, which could eventually make private keys guessable. Think of it as adding an assembly-line inspection that verifies a critical safety wire is connected end-to-end.

Security candidateRequire external entropy for all new master seed wallets - with new options dice/coin/mashby scgbckbone · 886582c8 · Aug 4, 2026 · 10 filesMessage 78 · AdequateLow 37Details
Commit message · scgbckbone

Require external entropy for all new master seed wallets - with new options dice/coin/mash

Deduplicate dice and coin collection while retaining separate mash handling. Capture raw mash press edges with the DWT CPU cycle counter (~8.33ns at 120MHz) before debounce. Credit two bits per inter-press gap, requiring 65 presses for 64 credited gaps; key identity is mixed in but receives no entropy credit.

78/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Names security-relevant behavior explicitly
Why it was queued
entropy or randomnessseed or entropy path
AI analysis · Low 37/100

This commit changes how new COLDCARD wallets are created: instead of relying only on the device's internal random-number generators, users must now add their own physical randomness by either mashing keys, rolling dice, or flipping coins. The internal random sources are still used, but the user's extra randomness is mixed in. This is a security improvement meant to reduce the risk that a hidden flaw in the device's random-number hardware could produce a predictable wallet. The change also adds checks to catch obviously biased dice or coin results.

Security candidatereseed with full 32 bytes of digest from SE1/SE2 entropy sourcesby scgbckbone · ac1644cd · Aug 4, 2026 · 2 filesMessage 55 · ThinModerate 59Details
Commit message · scgbckbone

reseed with full 32 bytes of digest from SE1/SE2 entropy sources

55/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Names security-relevant behavior explicitly! No meaningful explanatory body
Why it was queued
entropy or randomness
AI analysis · Moderate 59/100

This commit fixes a security weakness in how the COLDCARD MK4 hardware wallet seeds its random number generator (RNG). Previously, the firmware took a 256-bit hash of entropy from two secure elements, but only used the first 32 bits (4 bytes) of that hash to reseed the RNG. The change now uses the full 256-bit (32-byte) digest. More entropy bits means the RNG's initial state is much harder to predict, which matters when the device is generating cryptographic secrets like Bitcoin seed phrases. The commit also adds length checks to make sure the expected amount of entropy is actually received from each secure element.