What changed, and why it matters
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.
Users should treat this as a critical advisory: upgrade to firmware 5.5.2/1.4.2Q or later, regenerate wallet seeds using the fixed firmware, and move funds from any seed generated on affected firmware. Mk3 users should stop generating seeds on that hardware and either migrate to newer hardware or protect existing seeds with a strong BIP-39 passphrase. Security reviewers should locate the companion source-code commit that actually changes the entropy source/seed generation logic to verify the fix.
Security signals we found
Vendor-disclosed urgent hotfix for limited entropy in seed generation
Mk3 seeds after v4.0.1 reported to have ~40 bits of entropy
Mk4/Mk5/Q seeds reported to have as low as ~72 bits of entropy
Advisory to regenerate seeds and stop generating seeds on Mk3 hardware
Recommendation to move funds or use BIP-39 passphrase for affected devices
Documentation-only commit; actual entropy fix is not shown here
Evidence from the diff
The commit is a documentation-only update to release notes (ChangeLog.md, History-Mk.md, History-Mk3.md, History-Q.md). It adds a prominent warning that firmware 5.5.2 (Mk) and 1.4.2Q (Q) fix a ‘limited entropy bug’ in seed generation. It states Mk3 seeds created after v4.0.1 have critically low entropy (~40 bits), while Mk4/Mk5/Q seeds may have entropy as low as ~72 bits, below the 256-bit target. The notes direct users to a Coinkite blog post and advise regenerating seeds, moving funds, or adding a BIP-39 passphrase. The prior 5.5.1/1.4.1Q changelog entries are moved into the per-platform history files. No source code changes are present in this commit.
Changed components
COLDCARD Mk3 seed generation (firmware 4.0.1 and later)COLDCARD Mk4/Mk5 seed generationCOLDCARD Q seed generationRelease documentation (ChangeLog.md, History-Mk.md, History-Mk3.md, History-Q.md)Inspect captured patch +148 / −84
diff --git a/releases/ChangeLog.md b/releases/ChangeLog.md
index f65039d..eaff034 100644
--- a/releases/ChangeLog.md
+++ b/releases/ChangeLog.md
@@ -2,95 +2,24 @@
This lists the changes in the most recent firmware, for each hardware platform.
-# Shared Improvements - Both Mk and Q
+## 5.5.2 - 2026-07-30 & 1.4.2Q - 2026-07-30
-- Enhancement: Can export WIF Store watch-only descriptor.
-- Enhancement: WIF Store address detection without the need
- for `PSBT_IN_BIP32_DERIVATION` (improves Electrum support)
-- Enhancement: BIP-322 Proof of Reserves and Message Signing PSBT
- requires `PSBT_GLOBAL_GENERIC_SIGNED_MESSAGE` field
- (read more [BIP-322 Proof of Reserves documentation](../docs/proof-of-reserves-bip-322.md) )
-- Bugfix: Fixes legacy input amount spoofing by rejecting witness-utxo-only
- PSBT inputs when Coldcard is expected to sign a non-segwit input. When both
- UTXO fields are present the full `non_witness_utxo` is now preferred for
- amount/script lookup. Thanks, @Damir!
-- Bugfix: Keep NFC export tag alive for repeated probes. Helps NFC tap reliability on iOS.
-- Bugfix: Emit warning and do not calculate fee for legacy UTXOs with only witness utxo.
-- Bugfix: Disable Virtual Disk and NFC before activating HSM.
-- Bugfix: P2PK signing was broken. Now supports both compressed and uncompressed P2PK spend.
-- Bugfix: Custom address default menu position was wrong.
-- Bugfix: Delta Mode Trick PIN was never restored from backup.
-- Bugfix: Proper error message for incorrect 7z headers.
-- Bugfix: Exiting nickname entry with nickname already saved deleted previous nickname.
-- Bugfix: Incorrect error message caused by error in Verify/Decrypt Backup.
-- Bugfix: NFC Verify Address raised incorrect error message.
-- Bugfix: CCC key C challenge handled bad BIP-39 checksum by crashing the UX. Now treated
- as a wrong attempt (counts toward 3-strike lockout).
-- Bugfix: CCC magnitude reset from CANCEL on empty input.
-- Bugfix: `OP_RETURN` in CCC with whitelist enabled caused Yikes.
-- Bugfix: TX Explorer crashed on foreign input with non-standard sighash.
-- Bugfix: Malformed JSON message-sign request crashed signing UX.
-- Bugfix: Reject UI-control bytes in JSON / QR text message-signing.
-- Bugfix: Non-standard `OP_RETURN` outputs shown as "null-data", hiding part of the script.
-- Bugfix: Over-limit CCC address-whitelist import was rejected but still modified the policy.
-- Bugfix: Deleting a file right after renaming it (List Files) blanked the old name,
- leaving the renamed file.
-- Bugfix: Reordered `multi(...)` multisig with same keys was misreported as name-only
- change. Now blocked as duplicate.
-- Bugfix: Max WIF store capacity limit was ignored if saving via QR WIF visualization.
-- Bugfix: Force Seed XOR restore from Temporary Seed menu to remain temporary even when
- master seed is blank.
-- Bugfix: Binary signed-transaction (.txn) failed in NFC/QR file share.
-- Bugfix: Yikes in transaction explorer for goto index for tx with only one output.
-- Bugfix: Sending `signmessage` payload encoded as BBQr caused Yikes.
-- Bugfix: CCC/SSSP NFC whitelist import caused Yikes.
-- Bugfix: Stricter address ownership validation rejects unrecognized payment
- addresses before wallet search.
-- Bugfix: Handle malformed NDEF records robustly. Thanks, @Damir!
-- Bugfix: Ignore `bkpw` if added to backup. Thanks, [@dmonakhov](https://github.com/dmonakhov)!
-- Bugfix: Fix 1-of-1 multisig signing failure.
+**Urgent hotfix to correct a limited entropy bug.**
-# Mk Specific Changes
+Please regenerate seeds only with this version of the firmware and any
+later updates from today.
-## 5.5.1 - 2026-07-01
-
-- All bug fixes and enhancements listed above.
-
-
-# Q Specific Changes
-
-## 1.4.1Q - 2026-07-01
-
-- New Feature: Secure Notes & Passwords UX groups. Thanks, [@Gen6G](https://x.com/Gen6G)!
-- New Feature: Apply Secure Note text, or Secure Note password as BIP-39 passphrase.
-- New Feature: Standalone encrypted backups for Secure Notes & Passwords.
-- Bugfix: Major scanner robustness improvements!
- - Recover scanner setup failures by retrying configuration and reinitializing on
- the next scan when needed.
- - Prevent delayed scanner sleep commands from racing with a newly started scan.
- - Improve scanner shutdown/recovery after scan cancel or command timeout.
- - Bottom line: should be less "stuck" QR scanners, with the light left on.
-- Bugfix: Teleporting a multisig PSBT file (without signing it first) sent stale data
- instead of the selected file.
-- Bugfix: Fix export message shown after teleport PSBT import & sign.
-- Bugfix: BIP-21 QR `amount` rendered with wrong decimal scaling on the Payment Address
- screen (e.g. `amount=1.1` was shown as `1.00000001 BTC`).
-- Bugfix: Q1 seed word entry cursor alignment for 12-word seeds and preserve visible words
- after failed QR scans.
-- Bugfix: QR scan import (Scan Any QR Code, master/temp seed via QR) now shows a clear
- error message on any parser or seed-loading failure (e.g. wordlist-valid but bad-checksum
- SeedQR) instead of Yikes.
-- Bugfix: Yikes when showing "QR too big" for a transaction output alone on
- an output-explorer page.
-- Bugfix: Yikes receiving a malformed full-backup via Key Teleport.
-- Bugfix: Keyboard debounce could leave a key stuck as "pressed" after release, when another
- key was held (sometimes).
-- Bugfix: "Send Password" menu item inside Notes & Passwords visibility reversed.
-- Bugfix: Yikes when using "Send Password" on entry with password None field.
-- Bugfix: Do not show "Saving..." UX after failed Notes & Passwords import.
-- Bugfix: Notes & Passwords bulk import JSON with BBQr encoded as text.
+**Mk3 users must regenerate any seeds** made on Mk3 hardware after
+version 4.0.1 as their entropy is critically low at just ~40 bits.
+We are not planning to update Mk3 firmware at this time, so please
+use newer hardware or add a BIP-39 passphrase.
+On Mk4, Mk5 and Q entropy may be as low as ~72 bits. This is well below
+our target of 256 bits.
+Follow the steps listed in
+[our blog announcement](https://blog.coinkite.com/coldcard-mk3-seed-generation-warning/)
+to be safe, and please be careful not to cut corners or rush this process.
# Release History
diff --git a/releases/History-Mk.md b/releases/History-Mk.md
index 09bc8bd..4d5f5bc 100644
--- a/releases/History-Mk.md
+++ b/releases/History-Mk.md
@@ -1,5 +1,55 @@
*See ChangeLog.md for more recent changes, these are historic versions*
+
+## 5.5.1 - 2026-07-01
+
+- Enhancement: Can export WIF Store watch-only descriptor.
+- Enhancement: WIF Store address detection without the need
+ for `PSBT_IN_BIP32_DERIVATION` (improves Electrum support)
+- Enhancement: BIP-322 Proof of Reserves and Message Signing PSBT
+ requires `PSBT_GLOBAL_GENERIC_SIGNED_MESSAGE` field
+ (read more [BIP-322 Proof of Reserves documentation](../docs/proof-of-reserves-bip-322.md) )
+- Bugfix: Fixes legacy input amount spoofing by rejecting witness-utxo-only
+ PSBT inputs when Coldcard is expected to sign a non-segwit input. When both
+ UTXO fields are present the full `non_witness_utxo` is now preferred for
+ amount/script lookup. Thanks, @Damir!
+- Bugfix: Keep NFC export tag alive for repeated probes. Helps NFC tap reliability on iOS.
+- Bugfix: Emit warning and do not calculate fee for legacy UTXOs with only witness utxo.
+- Bugfix: Disable Virtual Disk and NFC before activating HSM.
+- Bugfix: P2PK signing was broken. Now supports both compressed and uncompressed P2PK spend.
+- Bugfix: Custom address default menu position was wrong.
+- Bugfix: Delta Mode Trick PIN was never restored from backup.
+- Bugfix: Proper error message for incorrect 7z headers.
+- Bugfix: Exiting nickname entry with nickname already saved deleted previous nickname.
+- Bugfix: Incorrect error message caused by error in Verify/Decrypt Backup.
+- Bugfix: NFC Verify Address raised incorrect error message.
+- Bugfix: CCC key C challenge handled bad BIP-39 checksum by crashing the UX. Now treated
+ as a wrong attempt (counts toward 3-strike lockout).
+- Bugfix: CCC magnitude reset from CANCEL on empty input.
+- Bugfix: `OP_RETURN` in CCC with whitelist enabled caused Yikes.
+- Bugfix: TX Explorer crashed on foreign input with non-standard sighash.
+- Bugfix: Malformed JSON message-sign request crashed signing UX.
+- Bugfix: Reject UI-control bytes in JSON / QR text message-signing.
+- Bugfix: Non-standard `OP_RETURN` outputs shown as "null-data", hiding part of the script.
+- Bugfix: Over-limit CCC address-whitelist import was rejected but still modified the policy.
+- Bugfix: Deleting a file right after renaming it (List Files) blanked the old name,
+ leaving the renamed file.
+- Bugfix: Reordered `multi(...)` multisig with same keys was misreported as name-only
+ change. Now blocked as duplicate.
+- Bugfix: Max WIF store capacity limit was ignored if saving via QR WIF visualization.
+- Bugfix: Force Seed XOR restore from Temporary Seed menu to remain temporary even when
+ master seed is blank.
+- Bugfix: Binary signed-transaction (.txn) failed in NFC/QR file share.
+- Bugfix: Yikes in transaction explorer for goto index for tx with only one output.
+- Bugfix: Sending `signmessage` payload encoded as BBQr caused Yikes.
+- Bugfix: CCC/SSSP NFC whitelist import caused Yikes.
+- Bugfix: Stricter address ownership validation rejects unrecognized payment
+ addresses before wallet search.
+- Bugfix: Handle malformed NDEF records robustly. Thanks, @Damir!
+- Bugfix: Ignore `bkpw` if added to backup. Thanks, [@dmonakhov](https://github.com/dmonakhov)!
+- Bugfix: Fix 1-of-1 multisig signing failure.
+
+
## 5.5.0 - 2065-03-05
- This release supports both the newer Mk5 hardware and existing Mk4.
diff --git a/releases/History-Mk3.md b/releases/History-Mk3.md
index f8d0c10..d4f0c0c 100644
--- a/releases/History-Mk3.md
+++ b/releases/History-Mk3.md
@@ -1,5 +1,11 @@
*See ChangeLog.md for more recent changes, these are historic versions*
+**July 30/2026: Do not generate seeds on Mk3 hardware. Move funds to new seeds or a BIP-39
+derived secret.**
+
+Follow the steps listed in
+[our blog announcement](https://blog.coinkite.com/coldcard-mk3-seed-generation-warning/)
+
## 4.1.9 - Jun 26, 2023
- Bugfix: QR codes could not be rendered in 4.1.8 release due to a regression.
diff --git a/releases/History-Q.md b/releases/History-Q.md
index 90b3386..c71987d 100644
--- a/releases/History-Q.md
+++ b/releases/History-Q.md
@@ -1,5 +1,84 @@
*See ChangeLog.md for more recent changes, these are historic versions*
+
+## 1.4.1Q - 2026-07-01
+
+- Enhancement: Can export WIF Store watch-only descriptor.
+- Enhancement: WIF Store address detection without the need
+ for `PSBT_IN_BIP32_DERIVATION` (improves Electrum support)
+- Enhancement: BIP-322 Proof of Reserves and Message Signing PSBT
+ requires `PSBT_GLOBAL_GENERIC_SIGNED_MESSAGE` field
+ (read more [BIP-322 Proof of Reserves documentation](../docs/proof-of-reserves-bip-322.md) )
+- Bugfix: Fixes legacy input amount spoofing by rejecting witness-utxo-only
+ PSBT inputs when Coldcard is expected to sign a non-segwit input. When both
+ UTXO fields are present the full `non_witness_utxo` is now preferred for
+ amount/script lookup. Thanks, @Damir!
+- Bugfix: Keep NFC export tag alive for repeated probes. Helps NFC tap reliability on iOS.
+- Bugfix: Emit warning and do not calculate fee for legacy UTXOs with only witness utxo.
+- Bugfix: Disable Virtual Disk and NFC before activating HSM.
+- Bugfix: P2PK signing was broken. Now supports both compressed and uncompressed P2PK spend.
+- Bugfix: Custom address default menu position was wrong.
+- Bugfix: Delta Mode Trick PIN was never restored from backup.
+- Bugfix: Proper error message for incorrect 7z headers.
+- Bugfix: Exiting nickname entry with nickname already saved deleted previous nickname.
+- Bugfix: Incorrect error message caused by error in Verify/Decrypt Backup.
+- Bugfix: NFC Verify Address raised incorrect error message.
+- Bugfix: CCC key C challenge handled bad BIP-39 checksum by crashing the UX. Now treated
+ as a wrong attempt (counts toward 3-strike lockout).
+- Bugfix: CCC magnitude reset from CANCEL on empty input.
+- Bugfix: `OP_RETURN` in CCC with whitelist enabled caused Yikes.
+- Bugfix: TX Explorer crashed on foreign input with non-standard sighash.
+- Bugfix: Malformed JSON message-sign request crashed signing UX.
+- Bugfix: Reject UI-control bytes in JSON / QR text message-signing.
+- Bugfix: Non-standard `OP_RETURN` outputs shown as "null-data", hiding part of the script.
+- Bugfix: Over-limit CCC address-whitelist import was rejected but still modified the policy.
+- Bugfix: Deleting a file right after renaming it (List Files) blanked the old name,
+ leaving the renamed file.
+- Bugfix: Reordered `multi(...)` multisig with same keys was misreported as name-only
+ change. Now blocked as duplicate.
+- Bugfix: Max WIF store capacity limit was ignored if saving via QR WIF visualization.
+- Bugfix: Force Seed XOR restore from Temporary Seed menu to remain temporary even when
+ master seed is blank.
+- Bugfix: Binary signed-transaction (.txn) failed in NFC/QR file share.
+- Bugfix: Yikes in transaction explorer for goto index for tx with only one output.
+- Bugfix: Sending `signmessage` payload encoded as BBQr caused Yikes.
+- Bugfix: CCC/SSSP NFC whitelist import caused Yikes.
+- Bugfix: Stricter address ownership validation rejects unrecognized payment
+ addresses before wallet search.
+- Bugfix: Handle malformed NDEF records robustly. Thanks, @Damir!
+- Bugfix: Ignore `bkpw` if added to backup. Thanks, [@dmonakhov](https://github.com/dmonakhov)!
+- Bugfix: Fix 1-of-1 multisig signing failure.
+
+- New Feature: Secure Notes & Passwords UX groups. Thanks, [@Gen6G](https://x.com/Gen6G)!
+- New Feature: Apply Secure Note text, or Secure Note password as BIP-39 passphrase.
+- New Feature: Standalone encrypted backups for Secure Notes & Passwords.
+- Bugfix: Major scanner robustness improvements!
+ - Recover scanner setup failures by retrying configuration and reinitializing on
+ the next scan when needed.
+ - Prevent delayed scanner sleep commands from racing with a newly started scan.
+ - Improve scanner shutdown/recovery after scan cancel or command timeout.
+ - Bottom line: should be less "stuck" QR scanners, with the light left on.
+- Bugfix: Teleporting a multisig PSBT file (without signing it first) sent stale data
+ instead of the selected file.
+- Bugfix: Fix export message shown after teleport PSBT import & sign.
+- Bugfix: BIP-21 QR `amount` rendered with wrong decimal scaling on the Payment Address
+ screen (e.g. `amount=1.1` was shown as `1.00000001 BTC`).
+- Bugfix: Q1 seed word entry cursor alignment for 12-word seeds and preserve visible words
+ after failed QR scans.
+- Bugfix: QR scan import (Scan Any QR Code, master/temp seed via QR) now shows a clear
+ error message on any parser or seed-loading failure (e.g. wordlist-valid but bad-checksum
+ SeedQR) instead of Yikes.
+- Bugfix: Yikes when showing "QR too big" for a transaction output alone on
+ an output-explorer page.
+- Bugfix: Yikes receiving a malformed full-backup via Key Teleport.
+- Bugfix: Keyboard debounce could leave a key stuck as "pressed" after release, when another
+ key was held (sometimes).
+- Bugfix: "Send Password" menu item inside Notes & Passwords visibility reversed.
+- Bugfix: Yikes when using "Send Password" on entry with password None field.
+- Bugfix: Do not show "Saving..." UX after failed Notes & Passwords import.
+- Bugfix: Notes & Passwords bulk import JSON with BBQr encoded as text.
+
+
## 1.4.0Q - 2065-03-05
- New Feature: Sign [BIP-322](https://github.com/bitcoin/bips/blob/master/bip-0322.mediawiki) Proof of Reserve PSBT files.
Why this scored 90/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.