COLDCARD firmware

This commit updates the COLDCARD Bitcoin hardware wallet firmware to accept and sign transactions that use version 3 of the Bitcoin transaction format. Previously, the wallet only allowed versions 1 and 2. The change is framed as a new feature, not a security fix. It adds parsing and test support for v3 transactions, including a special case for 'ephemeral anchor' outputs that have a zero value and are expected to trigger a warning.

This commit only updates the release signature file. It adds hashes for two new firmware files (v6.4.1X for MK4 and Q1 models), updates the hash for the Next-ChangeLog.md file, and refreshes the PGP signature that covers the file. There are no code changes and no security vulnerability is present in the diff.

This commit only updates the signed release checksum file (signatures.txt). It adds hashes for two new firmware files and updates hashes for four changelog files, then re-signs the file with a PGP signature. There are no code changes, no bug fixes, and no security-relevant modifications visible in the diff.

This commit only updates test code for the COLDCARD hardware wallet simulator. It adds missing device.close() calls after simulator shutdowns and adjusts one expected on-screen message for the Q1 model when a device is bricked. There are no changes to the actual firmware or wallet code that users rely on, so this does not create or fix a security vulnerability in the product itself.

This commit adds a new wallet-export feature to COLDCARD firmware: it lets users export a BIP-380 "key expression" (a compact text string containing the master fingerprint, derivation path, and extended public key). The change is a user-facing feature addition, not a bug fix. There is no indication in the commit or supplied references that this resolves a security vulnerability. The export is marked as privacy-sensitive but not secret, consistent with normal public-key export behavior.

This commit only reorganizes and updates the project's release notes (changelogs). It moves the description of features and bug fixes from the current release section into the historical release notes, and updates version numbers and dates. No actual firmware code was changed, so this commit cannot by itself introduce or fix any security vulnerability.

This commit only updates the release signatures file for the COLDCARD Mk4 hardware wallet. It adds cryptographic hashes (SHA-256) and a PGP signature for two new firmware files (version 5.4.5). There are no code changes, bug fixes, or feature modifications in this commit.

This commit only updates the file releases/signatures.txt. It refreshes SHA-256 hashes for two changelog files and adds hashes for two new Q1 firmware release files, then re-signs the file with a PGP signature. No source code, executable logic, or security-sensitive behavior changed.

This commit simply updates a minimum block height number in the Bitcoin mainnet configuration from 916,210 to 922,061. This is a routine date/height adjustment, not a security fix. It affects when a COLDCARD feature (likely related to a protocol or service activation) becomes available, but does not patch any vulnerability.

This commit only updates a generated timestamp and version number in a firmware build file. It changes the date from 2025-09-18 to 2025-10-30, the version from 5.4.4 to 5.4.5, and adjusts a corresponding FAT filesystem timestamp constant. There is no security-relevant code change.

This commit is a routine version bump and changelog cleanup. It changes two Makefile version strings from 5.4.4 to 5.4.5 and from 1.3.4Q to 1.3.5Q, and edits the release notes for grammar and formatting. No code behavior changes are present, and there is no security relevance in the diff itself.

This commit only adjusts automated test scripts for the COLDCARD hardware wallet firmware. It skips one display test on non-Q1 devices, adds small timing delays and a confirmation step in ephemeral seed tests, and updates an expected menu item label. There are no changes to the actual firmware code that runs on the device, so this cannot affect real user security.

This is a one-line bug fix in the COLDCARD firmware's backup restore code. The developer accidentally checked the wrong variable (`pwd` instead of `ipw`) when deciding whether the user cancelled the custom backup password entry screen. Because `pwd` is a list that is always truthy, the code never returned early when the user exited the password form, which the commit message describes as causing a 'yikes' error. The fix makes the code check the actual user input variable instead.

This change adds a confirmation screen when loading a backup file onto a COLDCARD hardware wallet. Before the wallet actually restores the seed from the backup, it now shows the backup's master fingerprint and asks the user to confirm or cancel. This helps prevent users from accidentally or maliciously loading the wrong backup. The change also refactors how the raw secret is extracted so the confirmation screen can compute the fingerprint before the restore happens. Clone operations skip this extra prompt because the user already sees what is being loaded on the source device.

This commit is a user-interface improvement, not a security fix. When restoring a COLDCARD backup on the Q-series device, the screen now shows the backup filename above the password-entry prompt so the user knows which file they are unlocking. No code behavior that protects secrets was changed.

This commit fixes a bug in the COLDCARD hardware wallet where cancelling out of the 'Custom Backup Password' text-entry screen during a backup restore would cause a crash (internally called a 'yikes'). The fix adds a simple check so that if the user exits without entering a password, the restore process stops gracefully instead of continuing with an empty value and crashing.

This commit only updates two release dates in the project's changelog file. It does not change any source code, configuration, or documentation that affects how the product works. There is no security relevance.

This commit only updates the release signature file. It adds two new cryptographic signatures for COLDCARD Mk4 firmware version 5.4.4 and refreshes the PGP signature that covers the entire 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 (signatures.txt) for the COLDCARD firmware. It adds two new file hashes for a Q1 hardware model firmware release (version 1.3.4Q) and refreshes the PGP signature that covers the entire file. There are no code changes, no bug fixes, and no security-related content in the commit message or diff.

This commit simply removes the digital signatures and file hashes for a previously listed firmware release (version 5.4.4 for Mk4 and 1.3.4Q for Q1) from the project's release signatures file, and updates the PGP signature covering that file. It is a release-management rollback of a 'gold' release candidate, not a code change. There is no firmware source code modification, no bug fix, and no security patch in this commit.

This commit only fixes two spelling mistakes in the project's release changelog document. It changes 'trival' to 'trivial' and 'Wife' to 'Wipe' in user-facing text. No source code, firmware logic, or security behavior is modified.

This commit only adds tiny 0.1-second delays inside a test file. It does not change any production firmware code, user-facing behavior, or security logic. It is purely a test stability tweak to avoid race conditions during automated testing.

This commit only updates the release signature file for COLDCARD Mk4 firmware. It adds two new signed hashes for version 5.4.4 and refreshes the PGP signature that covers the file. There are no code changes, no bug fixes, and no security-related content in the diff itself.

This commit updates a signed release manifest file (signatures.txt) for the COLDCARD hardware wallet firmware. It adds cryptographic hashes for two new Q1 firmware files and updates the hash and PGP signature for the ChangeLog. There are no code changes, no bug fixes, and no security-related content in the diff itself.

This commit only updates two release dates in the ChangeLog file (from 2025-09-25 to 2025-09-26). It makes no code changes and has no security relevance.