COLDCARD firmware

This commit only edits a README file in the hardware documentation folder. It reformats a list of spreadsheet filenames and updates a sentence from singular to plural. There are no code changes, no firmware changes, and no security-related content.

This commit simply adds public hardware documentation for the COLDCARD Mk5 (a schematic image and a bill-of-materials spreadsheet) and updates the README to list them. There is no code change, no firmware change, and nothing that alters security behavior.

This commit is a routine documentation and asset update announcing that the COLDCARD Mk5 hardware is now publicly supported. It updates the README to reference Mk5 images and wording, adds a changelog note that firmware 5.5.0 supports both Mk4 and Mk5, and replaces/adds simulator background images for the Mk5. There is no code change and no security-relevant behavior is modified.

This commit only adds new automated tests for an existing feature: signing BIP-322 Proof of Reserves messages using private keys stored via WIF (Wallet Import Format) on a COLDCARD. It does not change the firmware's actual signing code, user interface, or security behavior. The changes are confined to test files and test helpers.

This commit only updates a documentation example, changing the displayed currency ticker from 'XTN' (a testnet symbol) to 'BTC' (mainnet Bitcoin) in a proof-of-reserves guide. No firmware code, behavior, or security logic was changed.

This commit only edits release notes and changelogs. It moves completed feature and bugfix descriptions from an unpublished 'Next-ChangeLog' file into the published 'ChangeLog' and historic release notes, and resets the draft file to placeholder 'tbd' entries. No source code, firmware logic, or security behavior is changed.

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 file. There are no code changes, no bug fixes, and no security-relevant behavior changes in the firmware itself.

This commit only updates the release signature file. It adds cryptographic hashes and a PGP signature for a new COLDCARD firmware release (version 1.4.0Q for the Q1 hardware model) and updates the hash for the Next-ChangeLog.md file. There are no code changes, bug fixes, or security patches in this commit.

This commit only updates placeholder release dates in a changelog file (from '2065-03-xx' to '2065-03-05'). It makes no code changes and has no security relevance.

This commit fixes a bug in the COLDCARD hardware wallet's WIF (Wallet Import Format) key import feature. Previously, if a user tried to import a file containing the same private key twice, the code could incorrectly count it as a duplicate of an already-saved key rather than as a duplicate within the import file itself. This could cause the import to fail with a misleading 'duplicate WIF(s)' error even when no keys were actually saved yet. The fix properly distinguishes between duplicates inside the import file and duplicates of already-stored keys. There is no direct evidence this is a security vulnerability—it's primarily a usability/robustness fix.

This commit adds a build-system step that creates an additional release file for factory programming. It does not change any firmware code, cryptographic checks, or user-facing behavior. There is no indication of a security vulnerability.

This commit makes only cosmetic changes to the COLDCARD firmware: it changes a screen title from 'WIF' to 'WIF Key' and adds a few blank lines for readability. There is no functional code change and no security impact.

This commit adds a feature to COLDCARD Q1 hardware wallets that lets users scan a QR code containing a private key (in WIF format), view its details, and optionally save it to the device's WIF Store. The change itself is a user-facing feature addition, not a bug fix. There is no direct evidence in the commit or supplied references that this is a security patch or addresses a vulnerability. However, any feature that imports and stores private keys carries inherent security and usability risks, such as users importing untrusted or leaked keys, or accidentally exposing keys via QR codes.

This commit simply updates a date-based block-height threshold in the COLDCARD firmware from a November 2025 value to a March 2026 value. It appears to be a routine scheduling change for a feature tied to a specific Bitcoin block height, not a security fix in itself. There is no evidence in the commit of a vulnerability being patched.

This commit is purely a test-code reorganization. It moves existing WIF-store-related test cases from several scattered test files into a single dedicated test file (test_wif.py), updates test runner configuration, and removes duplicate imports. There is no change to the actual firmware or security-sensitive code.

This commit updates the COLDCARD firmware's WIF (Wallet Import Format) import feature so it can read paper wallet backup files and is more forgiving of extra text or formatting. It also moves and expands the related tests. The main code change is a usability improvement, not a clear security fix, but it does make the import parser ignore invalid lines instead of stopping with an error. That change could hide a corrupted or malicious file, though it does not obviously create a new vulnerability.

This commit is a routine version and date bump for two auto-generated files. It updates copyright year, build date, firmware version number, and a corresponding timestamp constant used when the device writes files to a microSD card. There is no code logic change and no security relevance visible in the diff.

This commit fixes a bug in the COLDCARD hardware wallet where scanning or verifying a QR code for an address stored in the WIF (Wallet Import Format) store could display or encode the wrong QR address format. Previously, the code assumed all WIF-store addresses used the wallet's default address format, which could cause a mismatch when showing the QR code. The fix correctly tracks the address format for WIF-stored keys and adds a test to verify the QR code matches the expected address.

This commit fixes two typos in a comment inside a build Makefile. It changes no code, commands, or build behavior. There is no security relevance.

This commit adds a new pre-built bootloader release (version 3.3.0) for the COLDCARD Mk4 hardware wallet. It consists of binary firmware files and a hash manifest, plus a disassembly listing. There is no source code change, no vulnerability description, and no indication of a security fix or bug. It appears to be a routine release artifact drop.

This commit only changes version numbers and release dates in build files and a changelog. It does not modify any code that handles secrets, cryptography, user input, or device behavior. There is no security issue here.

This is a small bug fix in the COLDCARD hardware wallet firmware. When importing a BIP-322 message from a file, the file picker was not being told which storage source to use (virtual disk or SD card slot). This could cause the file picker to look in the wrong place or fail to find files, making the feature unreliable rather than directly stealing funds.

This commit is a trivial documentation edit. It expands the abbreviation 'WIF' to 'Wallet Import Format' in an upcoming release changelog. No code, cryptographic logic, or security behavior was changed.

This commit adds support for a new COLDCARD hardware revision, the Mk5. It is a routine product-enablement patch: it teaches the firmware, bootloader, build system, simulator, and signing tools to recognize and run on Mk5 devices. There is no indication of a security vulnerability being fixed or introduced; the changes are about hardware detection, display initialization, graphics, and test coverage.

This commit adds a new 'WIF Store' feature to the COLDCARD firmware. It lets users import external Bitcoin private keys (in WIF format) and use them to sign PSBT transactions and messages, alongside the device's normal seed-derived keys. The change is a deliberate new feature, not a hidden bug, but it touches sensitive code paths: private key storage, PSBT signing, address ownership checks, and message signing. There is no vendor statement in the commit or supplied references calling this a security fix or vulnerability.