COLDCARD firmware

This commit only changes version numbers in the changelog and two build makefiles. It does not modify any code, fix any bug, or alter any behavior. The actual security-relevant fix for the 'limited entropy bug' is not present in this diff.

This commit only updates two automatically generated files that store a fixed build date and firmware version number used for timestamps on files written to SD cards. The actual code logic did not change; only the hardcoded date and version constants were bumped from June 30, 2026 to July 30, 2026, and from 5.5.1/1.4.1Q to 5.5.2/1.4.2Q. There is no security-relevant change visible in the diff.

This commit simply updates a hardcoded Bitcoin block height number in a firmware file, moving it forward by two blocks. There is no code change that affects security, user funds, or device behavior beyond reflecting a slightly later point in time.

This commit simply updates a stored Bitcoin blockchain height number and its timestamp in a generated data file. It is a routine data refresh with no code changes and no apparent security relevance.

This commit updates Coldcard's release notes to announce an urgent security fix for a 'limited entropy' bug in how the device generates wallet seeds. On older Mk3 hardware, seeds created after firmware 4.0.1 may have only about 40 bits of randomness—far weaker than the intended 256 bits—making them far easier for an attacker to guess. Newer Mk4, Mk5, and Q devices may also have seeds with only about 72 bits. The company is telling users to regenerate their seeds with the new firmware and to stop generating seeds on Mk3 devices. This specific commit only changes documentation; the actual code fix is in a different commit.

This commit fixes a critical random-number bug in COLDCARD hardware wallets. The device was accidentally using a weak, software-based fallback random generator instead of its secure hardware one when creating Bitcoin seed phrases. Because the fallback generator had very little real randomness, attackers who captured a public transaction or signature could potentially figure out the wallet's private keys and steal funds. The patch forces the build to use the hardware random source and adds a build-time check to make sure the weak fallback is never linked in again. Coinkite issued an emergency hotfix and warned users to move funds from wallets created with affected firmware.

This update fixes a bug in the COLDCARD hardware wallet where short PSBT (Partially Signed Bitcoin Transaction) files could be mistaken for partial firmware uploads when their size landed near a specific firmware-probe boundary. The fix adds a length check so the device only treats a chunk as a firmware header probe when the incoming data block is exactly 256 bytes long. If the bug were triggered, a legitimate PSBT upload might be misclassified, potentially causing the upload to fail or behave unexpectedly. There is no evidence in the commit of malicious exploitation or a security bypass.

This commit only updates the COLDCARD firmware's internal test suite to remain compatible with Bitcoin Core version 32. It adds helper methods to read and set locktime in a way that works for both old PSBT version 0/1 and new PSBT version 2, and changes test calls to Bitcoin Core so they request PSBT version 0 when the newer Core would otherwise default to version 2. There is no change to the actual firmware code that runs on the device, and no security vulnerability is fixed or introduced.

This commit tightens the rules for messages that COLDCARD will sign using the BIP-322 proof-of-reserves feature. Previously, non-ASCII characters were allowed with only a warning; now the message must be plain printable ASCII (with limited exceptions), must be 2-330 characters long, and cannot have tricky spacing. This reduces the chance that a crafted message could mislead the user into signing something they did not intend.

This is a routine automated update by Dependabot that bumps the Python Pillow image-processing library from version 12.1.1 to 12.3.0 inside a small helper tool used only for font generation. The commit itself does not describe any security problem, and the changed file is not part of the COLDCARD firmware that runs on the device. It is best treated as normal maintenance, though any dependency update can in principle include undisclosed fixes.

This is a small bug-fix in the COLDCARD hardware wallet's battery monitoring code. It prevents a crash that could occur if a background battery check runs before the QR-code scanner module has finished starting up. The change makes the code safely skip the check when the scanner isn't ready yet, rather than trying to read a value that doesn't exist and crashing.

This commit only corrects two placeholder release dates in the changelog from the year 2065 to 2026. There are no code changes, no functional changes, and no security relevance.

This commit only updates the release signature file. It adds two new file checksums for a COLDCARD firmware release (version 5.5.1 for the 'mk' model) and refreshes the PGP signature that covers the file. There is no code change, no bug fix, and no security patch in the diff itself.

This commit simply updates a hardcoded Bitcoin block height number in a single file by one block. There is no security issue visible in the change itself.

This commit only updates the release signature file (signatures.txt). It refreshes SHA-256 hashes for changelog/history files and adds hashes for two new Q1 firmware release files, plus updates the PGP signature that covers the file. There is no source code change and nothing that directly affects device security.

This commit simply updates a hardcoded Bitcoin blockchain height number and its timestamp in a firmware file. It is a routine data refresh with no code changes and no apparent security implications.

This commit only updates two release dates in a changelog file from June 30 to July 1, 2065. There are no code changes, no security fixes, and no functional changes of any kind.

This commit only updates build instructions and a Makefile for compiling the COLDCARD simulator on macOS. It removes a hardcoded PKG_CONFIG_PATH workaround and updates the README to tell users to install pkgconf and libffi themselves. There is no change to firmware code, wallet logic, cryptography, or anything that handles secrets or transactions.

This commit only edits the release changelog text. It reorders and rewords bugfix entries, adds one new NFC-related note, and removes some duplicate lines. No source code, firmware logic, or security behavior was changed.

This commit simply updates a stored Bitcoin blockchain height number from 932,301 to 956,098, along with its timestamp. There is no code logic change, no bug fix, and no security-related content.

This commit appears to be a one-line version correction in a submodule reference (external/ckcc-protocol). No code changes are visible, and no security relevance is stated or inferable from the available information.

This commit simplifies a build-time check that verifies the correct versions of submodules are being used. It does not change what is being checked, only how the result is reported. There is no indication this is a security fix.

This commit only updates two automatically-generated timestamp files used to set dates on files created by the COLDCARD hardware wallet. It changes the recorded build date from March 5, 2026 to June 30, 2026, and bumps the firmware version numbers from 5.5.0 to 5.5.1 (MK4) and 1.4.0Q to 1.4.1Q (Q1). There is no security-relevant code change.

This is a tiny build-script change for the COLDCARD hardware wallet firmware. It makes two Makefile adjustments: the release-candidate build target now depends on a submodule-check step, and a cleanup command is silenced so it doesn't print to the screen. There is nothing here that affects device security, user funds, or runtime behavior.