r/coldcard: report of a Mk4 bricked by the emergency firmware hotfix
reddit-mk4-bricked-hotfix
https://www.reddit.com/r/coldcard/comments/1vct6m2/psa_coldcard_mk4_bricked_by_the_new_emergency/
Latest reviewed change
source content difference between and
Two new comments were added: one argues the hotfix bricking is triggered by the hardware RNG randomizing keyboard scan order on each press, and the poster confirms this is unintended and links the pull requests containing the fix.
edited: false
body:
That message was before the edit. After carching the why, the problem is not the passphrase, it’s the keyboard press. Coldcard uses HW RNG to randomize the scan order. So every press could potentially send it in a soft bricked state.
+
+comment: p2migmm
+parent: t1_p2mcn5g
+author: bje332013
+created_utc: 1786273333
First lines only. The complete diff is in the timeline below.
- Organisation
- Evidence role
- Community discussion
- Published
- not established
- Source changes
- 13
- Detected differences
- 13
- Unreviewed
- 0
- Copies held
- 14
Every check is recorded, including checks that found no text change. A detected edit is therefore bounded between two checks. The publisher's exact save time is not observable from this record. Last checked .
Also held inside a captured conversation
This post is held twice: here, with this project's own note on why it matters, and again as part of the conversation captured at , which is polled for changes. Both copies are the same post; neither is a separate event.
Public privacy boundary
Snapshot and diff bodies for this chain monitor are held in the local evidence archive but withheld from the public site because they can contain the addresses of people who published nothing themselves. Capture times and reviewed change summaries remain available below.
Held captures
-
Two new comments were added: one argues the hotfix bricking is triggered by the hardware RNG randomizing keyboard scan order on each press, and the poster confirms this is unintended and links the pull requests containing the fix.
Recovered from the Internet Archive rather than captured by this project. The row records that third-party provenance separately from captures made by this project.
What changed from the previous capture 18 lines
edited: false body: That message was before the edit. After carching the why, the problem is not the passphrase, it’s the keyboard press. Coldcard uses HW RNG to randomize the scan order. So every press could potentially send it in a soft bricked state. + +comment: p2migmm +parent: t1_p2mcn5g +author: bje332013 +created_utc: 1786273333 +edited: false +body: +"the problem is not the passphrase, it’s the keyboard press. Coldcard uses HW RNG to randomize the scan order. So every press could potentially send it in a soft bricked state." + +Sorry, I don't understand your explanation. If the Coldcard device is working correctly (which it reportedly is not once the new firmware gets flashed), no sequence of valid keyboard/button presses should 'brick' the device. + +comment: p2mn4fd +parent: t1_p2migmm +author: lucapocchio +created_utc: 1786275400 +edited: false +body: +U are 100% right, and this is not intended. In the edits i’ve added the urls of the PR’s to verify the fix. But still until when a new firmware doesn’t include it this can happen.Extracted text as captured
post: 1vct6m2 author: lucapocchio created_utc: 1785605030 title: PSA: Coldcard Mk4 BRICKED by the new emergency firmware hotfix (seed.py crash). Irony at its finest. body: Just wanted to put out a serious warning for anyone updating their Coldcard Mk4 to fix the recent RNG/seed generation vulnerability. I followed Coinkite's urgent advisory to the letter: updated to the new hotfix firmware 5.6.0, wiped my old seed, and generated a brand-new one. I even tested it, created two BIP-39 passphrases, and everything seemed fine at first. But then, the premium "Don't Trust, Verify" experience kicked in. While I was testing the passphrases—literally just entering the words and clicking apply—the device threw a critical MicroPython software crash error pointing directly to \`seed.py\` and another method. To be precise, I had done this exact same process successfully several times just before it happened, so it doesn't look completely deterministic, but the bug is definitely present and lurking in the code. I had to power cycle it, and guess what? The screen now permanently reads "BRICKED". No recovery mode, no factory reset, just a hundreds-of-dollars paperweight. I bought a bundle of 2 units directly from their site, and one is already dead due to their rushed code. If you are running the new firmware and messing with passphrases, PLEASE BE CAREFUL. This hotfix seems to have a catastrophic bug that permanently hard-locks the secure element or the firmware during passphrase application. Hey Coinkite, I thought Coldcard was the ultimate, unbreakable fortress for paranoid Bitcoiners? Fixing a critical seed generation vulnerability with a firmware bug that literally kills the hardware is quite a strategic move to sell more devices! This is completely unacceptable for a premium security device, also given what is happening. Anyone else experiencing crashes or weird behavior on the new firmware? Lmk. ———-EDIT 2 DAYS LATER, BUG CONFIRMED ———- [https://github.com/Coldcard/firmware/pull/692](https://github.com/Coldcard/firmware/pull/692) ———-EDIT 3 DAYS LATER, COLD CARD REPORT ———- [https://x.com/COLDCARDwallet/status/2084632863756955661](https://x.com/COLDCARDwallet/status/2084632863756955661) I will try to test in the described way and update here about results for everyone. ——— EDIT 3 DAYS LATER, DEVICE RECOVERED / WHAT ACTUALLY HAPPENED ——— The device was not permanently bricked.Excerpt only. The complete copy is held offline and backs quotations on this site. The original publication remains the canonical public source.
-
The thread gained two comments: one arguing third-party developers might not notice the TRNG failure, and another by the original poster explaining that keyboard-press randomization using the hardware RNG can soft-brick the device.
Recovered from the Internet Archive rather than captured by this project. The row records that third-party provenance separately from captures made by this project.
What changed from the previous capture 24 lines
Damien George, the lead MicroPython developer, released an analysis of the problem: [Coldcard postmortem from MicroPython's perspective](https://github.com/orgs/micropython/discussions/19588). The problem was in LibNgU (not part of MicroPython) which checked if the `MICROPY_HW_ENABLE_RNG` macro was defined, rather than if it was enabled. Oops. + +comment: p2ltylc +parent: t1_p1xen2l +author: Charming-Designer944 +created_utc: 1786260881 +edited: false +body: +Me too. + +I don't see it very likely a third party dev would notice the TRNG error. Not even one who adds another entropy source to the seed mixing. + +I agree they will notice the stupid crippled mixing of the safe elements entropy into the main entropy. But not necessarily the failure to use the main TRNG of the main CPU. + +If the third party dev had used another line of CPUs then they will not even look at the Coldcard "improved" STM32 TRNG integration attempt + +If the third party developer had used the same CPU family as Coldcard then there is a high risk that they had accepted the coldcard TRNG integration as verified working, not thinking that Couldcard cold fail the integration at such fundamental level. + +comment: p2mcn5g +parent: t1_p2hekmj +author: lucapocchio +created_utc: 1786270523 +edited: false +body: +That message was before the edit. After carching the why, the problem is not the passphrase, it’s the keyboard press. Coldcard uses HW RNG to randomize the scan order. So every press could potentially send it in a soft bricked state.Extracted text as captured
post: 1vct6m2 author: lucapocchio created_utc: 1785605030 title: PSA: Coldcard Mk4 BRICKED by the new emergency firmware hotfix (seed.py crash). Irony at its finest. body: Just wanted to put out a serious warning for anyone updating their Coldcard Mk4 to fix the recent RNG/seed generation vulnerability. I followed Coinkite's urgent advisory to the letter: updated to the new hotfix firmware 5.6.0, wiped my old seed, and generated a brand-new one. I even tested it, created two BIP-39 passphrases, and everything seemed fine at first. But then, the premium "Don't Trust, Verify" experience kicked in. While I was testing the passphrases—literally just entering the words and clicking apply—the device threw a critical MicroPython software crash error pointing directly to \`seed.py\` and another method. To be precise, I had done this exact same process successfully several times just before it happened, so it doesn't look completely deterministic, but the bug is definitely present and lurking in the code. I had to power cycle it, and guess what? The screen now permanently reads "BRICKED". No recovery mode, no factory reset, just a hundreds-of-dollars paperweight. I bought a bundle of 2 units directly from their site, and one is already dead due to their rushed code. If you are running the new firmware and messing with passphrases, PLEASE BE CAREFUL. This hotfix seems to have a catastrophic bug that permanently hard-locks the secure element or the firmware during passphrase application. Hey Coinkite, I thought Coldcard was the ultimate, unbreakable fortress for paranoid Bitcoiners? Fixing a critical seed generation vulnerability with a firmware bug that literally kills the hardware is quite a strategic move to sell more devices! This is completely unacceptable for a premium security device, also given what is happening. Anyone else experiencing crashes or weird behavior on the new firmware? Lmk. ———-EDIT 2 DAYS LATER, BUG CONFIRMED ———- [https://github.com/Coldcard/firmware/pull/692](https://github.com/Coldcard/firmware/pull/692) ———-EDIT 3 DAYS LATER, COLD CARD REPORT ———- [https://x.com/COLDCARDwallet/status/2084632863756955661](https://x.com/COLDCARDwallet/status/2084632863756955661) I will try to test in the described way and update here about results for everyone. ——— EDIT 3 DAYS LATER, DEVICE RECOVERED / WHAT ACTUALLY HAPPENED ——— The device was not permanently bricked.Excerpt only. The complete copy is held offline and backs quotations on this site. The original publication remains the canonical public source.
-
A new comment links to Damien George's MicroPython postmortem and attributes the bricking to a LibNgU macro check error.
Recovered from the Internet Archive rather than captured by this project. The row records that third-party provenance separately from captures made by this project.
What changed from the previous capture 10 lines
"If you are running the new firmware and messing with passphrases, PLEASE BE CAREFUL." What exactly do you mean by "be careful"? It sounds like you did everything right, so I don't get what action(s) you're advising others against taking other than maybe avoiding the new firmware. + +comment: p2k01mt +parent: t1_p1xdvg6 +author: scruss +created_utc: 1786233653 +edited: false +body: +Damien George, the lead MicroPython developer, released an analysis of the problem: [Coldcard postmortem from MicroPython's perspective](https://github.com/orgs/micropython/discussions/19588). + +The problem was in LibNgU (not part of MicroPython) which checked if the `MICROPY_HW_ENABLE_RNG` macro was defined, rather than if it was enabled. Oops.Extracted text as captured
post: 1vct6m2 author: lucapocchio created_utc: 1785605030 title: PSA: Coldcard Mk4 BRICKED by the new emergency firmware hotfix (seed.py crash). Irony at its finest. body: Just wanted to put out a serious warning for anyone updating their Coldcard Mk4 to fix the recent RNG/seed generation vulnerability. I followed Coinkite's urgent advisory to the letter: updated to the new hotfix firmware 5.6.0, wiped my old seed, and generated a brand-new one. I even tested it, created two BIP-39 passphrases, and everything seemed fine at first. But then, the premium "Don't Trust, Verify" experience kicked in. While I was testing the passphrases—literally just entering the words and clicking apply—the device threw a critical MicroPython software crash error pointing directly to \`seed.py\` and another method. To be precise, I had done this exact same process successfully several times just before it happened, so it doesn't look completely deterministic, but the bug is definitely present and lurking in the code. I had to power cycle it, and guess what? The screen now permanently reads "BRICKED". No recovery mode, no factory reset, just a hundreds-of-dollars paperweight. I bought a bundle of 2 units directly from their site, and one is already dead due to their rushed code. If you are running the new firmware and messing with passphrases, PLEASE BE CAREFUL. This hotfix seems to have a catastrophic bug that permanently hard-locks the secure element or the firmware during passphrase application. Hey Coinkite, I thought Coldcard was the ultimate, unbreakable fortress for paranoid Bitcoiners? Fixing a critical seed generation vulnerability with a firmware bug that literally kills the hardware is quite a strategic move to sell more devices! This is completely unacceptable for a premium security device, also given what is happening. Anyone else experiencing crashes or weird behavior on the new firmware? Lmk. ———-EDIT 2 DAYS LATER, BUG CONFIRMED ———- [https://github.com/Coldcard/firmware/pull/692](https://github.com/Coldcard/firmware/pull/692) ———-EDIT 3 DAYS LATER, COLD CARD REPORT ———- [https://x.com/COLDCARDwallet/status/2084632863756955661](https://x.com/COLDCARDwallet/status/2084632863756955661) I will try to test in the described way and update here about results for everyone. ——— EDIT 3 DAYS LATER, DEVICE RECOVERED / WHAT ACTUALLY HAPPENED ——— The device was not permanently bricked.Excerpt only. The complete copy is held offline and backs quotations on this site. The original publication remains the canonical public source.
-
The thread gained a new comment reporting an auto-blocked post about firmware bricking and asking what actions passphrase users should avoid.
Recovered from the Internet Archive rather than captured by this project. The row records that third-party provenance separately from captures made by this project.
What changed from the previous capture 12 lines
edited: false body: still using coldcard or thinking about moving your funds? + +comment: p2hekmj +parent: t3_1vct6m2 +author: bje332013 +created_utc: 1786205567 +edited: false +body: +I tried to start a new thread in this subreddit asking about the firmware and whether people are getting 'BRICKED' messages as often as is suggested on X / Twitter. However, my thread was automatically blocked by Reddit's filters. + +"If you are running the new firmware and messing with passphrases, PLEASE BE CAREFUL." + +What exactly do you mean by "be careful"? It sounds like you did everything right, so I don't get what action(s) you're advising others against taking other than maybe avoiding the new firmware.Extracted text as captured
post: 1vct6m2 author: lucapocchio created_utc: 1785605030 title: PSA: Coldcard Mk4 BRICKED by the new emergency firmware hotfix (seed.py crash). Irony at its finest. body: Just wanted to put out a serious warning for anyone updating their Coldcard Mk4 to fix the recent RNG/seed generation vulnerability. I followed Coinkite's urgent advisory to the letter: updated to the new hotfix firmware 5.6.0, wiped my old seed, and generated a brand-new one. I even tested it, created two BIP-39 passphrases, and everything seemed fine at first. But then, the premium "Don't Trust, Verify" experience kicked in. While I was testing the passphrases—literally just entering the words and clicking apply—the device threw a critical MicroPython software crash error pointing directly to \`seed.py\` and another method. To be precise, I had done this exact same process successfully several times just before it happened, so it doesn't look completely deterministic, but the bug is definitely present and lurking in the code. I had to power cycle it, and guess what? The screen now permanently reads "BRICKED". No recovery mode, no factory reset, just a hundreds-of-dollars paperweight. I bought a bundle of 2 units directly from their site, and one is already dead due to their rushed code. If you are running the new firmware and messing with passphrases, PLEASE BE CAREFUL. This hotfix seems to have a catastrophic bug that permanently hard-locks the secure element or the firmware during passphrase application. Hey Coinkite, I thought Coldcard was the ultimate, unbreakable fortress for paranoid Bitcoiners? Fixing a critical seed generation vulnerability with a firmware bug that literally kills the hardware is quite a strategic move to sell more devices! This is completely unacceptable for a premium security device, also given what is happening. Anyone else experiencing crashes or weird behavior on the new firmware? Lmk. ———-EDIT 2 DAYS LATER, BUG CONFIRMED ———- [https://github.com/Coldcard/firmware/pull/692](https://github.com/Coldcard/firmware/pull/692) ———-EDIT 3 DAYS LATER, COLD CARD REPORT ———- [https://x.com/COLDCARDwallet/status/2084632863756955661](https://x.com/COLDCARDwallet/status/2084632863756955661) I will try to test in the described way and update here about results for everyone. ——— EDIT 3 DAYS LATER, DEVICE RECOVERED / WHAT ACTUALLY HAPPENED ——— The device was not permanently bricked.Excerpt only. The complete copy is held offline and backs quotations on this site. The original publication remains the canonical public source.
-
Three new comments: lucapocchio confirming the bricking bug can still occur until a fix ships in a version like 5.6.1, zatsnotmyname saying the workaround works, and nicolbolas10 asking whether others are staying on Coldcard or moving funds.
Recovered from the Internet Archive rather than captured by this project. The row records that third-party provenance separately from captures made by this project.
What changed from the previous capture 24 lines
edited: false body: did this problem happen again? I updated my CC with the new firmware 5.6.0 last week, used it without any problems for 2 days. Opened it after 6 days and the device bricked(MK4). After trying to open it for 30 min, the device turned on and now it's working. However I think this bug can still happen again with the current firmware so not sure what to do. + +comment: p27w6vj +parent: t1_p27i4b1 +author: lucapocchio +created_utc: 1786086324 +edited: false +body: +Yes it can happen. I wrote that also on the edit. Until the fix is not in a new version like 5.6.1. + +comment: p28mha5 +parent: t3_1vct6m2 +author: zatsnotmyname +created_utc: 1786098868 +edited: false +body: +Works. 'x' + +comment: p28rrb0 +parent: t1_p27w6vj +author: nicolbolas10 +created_utc: 1786101040 +edited: false +body: +still using coldcard or thinking about moving your funds?Extracted text as captured
post: 1vct6m2 author: lucapocchio created_utc: 1785605030 title: PSA: Coldcard Mk4 BRICKED by the new emergency firmware hotfix (seed.py crash). Irony at its finest. body: Just wanted to put out a serious warning for anyone updating their Coldcard Mk4 to fix the recent RNG/seed generation vulnerability. I followed Coinkite's urgent advisory to the letter: updated to the new hotfix firmware 5.6.0, wiped my old seed, and generated a brand-new one. I even tested it, created two BIP-39 passphrases, and everything seemed fine at first. But then, the premium "Don't Trust, Verify" experience kicked in. While I was testing the passphrases—literally just entering the words and clicking apply—the device threw a critical MicroPython software crash error pointing directly to \`seed.py\` and another method. To be precise, I had done this exact same process successfully several times just before it happened, so it doesn't look completely deterministic, but the bug is definitely present and lurking in the code. I had to power cycle it, and guess what? The screen now permanently reads "BRICKED". No recovery mode, no factory reset, just a hundreds-of-dollars paperweight. I bought a bundle of 2 units directly from their site, and one is already dead due to their rushed code. If you are running the new firmware and messing with passphrases, PLEASE BE CAREFUL. This hotfix seems to have a catastrophic bug that permanently hard-locks the secure element or the firmware during passphrase application. Hey Coinkite, I thought Coldcard was the ultimate, unbreakable fortress for paranoid Bitcoiners? Fixing a critical seed generation vulnerability with a firmware bug that literally kills the hardware is quite a strategic move to sell more devices! This is completely unacceptable for a premium security device, also given what is happening. Anyone else experiencing crashes or weird behavior on the new firmware? Lmk. ———-EDIT 2 DAYS LATER, BUG CONFIRMED ———- [https://github.com/Coldcard/firmware/pull/692](https://github.com/Coldcard/firmware/pull/692) ———-EDIT 3 DAYS LATER, COLD CARD REPORT ———- [https://x.com/COLDCARDwallet/status/2084632863756955661](https://x.com/COLDCARDwallet/status/2084632863756955661) I will try to test in the described way and update here about results for everyone. ——— EDIT 3 DAYS LATER, DEVICE RECOVERED / WHAT ACTUALLY HAPPENED ——— The device was not permanently bricked.Excerpt only. The complete copy is held offline and backs quotations on this site. The original publication remains the canonical public source.
-
New comment by nicolbolas10 reporting a first-hand recurrence: an Mk4 on firmware 5.6.0 bricked after six days, then recovered after 30 minutes, asking whether the bug can still happen.
Recovered from the Internet Archive rather than captured by this project. The row records that third-party provenance separately from captures made by this project.
What changed from the previous capture 8 lines
edited: false body: Oops forgot to do regression testing + +comment: p27i4b1 +parent: t1_p1q1psp +author: nicolbolas10 +created_utc: 1786079926 +edited: false +body: +did this problem happen again? I updated my CC with the new firmware 5.6.0 last week, used it without any problems for 2 days. Opened it after 6 days and the device bricked(MK4). After trying to open it for 30 min, the device turned on and now it's working. However I think this bug can still happen again with the current firmware so not sure what to do.Extracted text as captured
post: 1vct6m2 author: lucapocchio created_utc: 1785605030 title: PSA: Coldcard Mk4 BRICKED by the new emergency firmware hotfix (seed.py crash). Irony at its finest. body: Just wanted to put out a serious warning for anyone updating their Coldcard Mk4 to fix the recent RNG/seed generation vulnerability. I followed Coinkite's urgent advisory to the letter: updated to the new hotfix firmware 5.6.0, wiped my old seed, and generated a brand-new one. I even tested it, created two BIP-39 passphrases, and everything seemed fine at first. But then, the premium "Don't Trust, Verify" experience kicked in. While I was testing the passphrases—literally just entering the words and clicking apply—the device threw a critical MicroPython software crash error pointing directly to \`seed.py\` and another method. To be precise, I had done this exact same process successfully several times just before it happened, so it doesn't look completely deterministic, but the bug is definitely present and lurking in the code. I had to power cycle it, and guess what? The screen now permanently reads "BRICKED". No recovery mode, no factory reset, just a hundreds-of-dollars paperweight. I bought a bundle of 2 units directly from their site, and one is already dead due to their rushed code. If you are running the new firmware and messing with passphrases, PLEASE BE CAREFUL. This hotfix seems to have a catastrophic bug that permanently hard-locks the secure element or the firmware during passphrase application. Hey Coinkite, I thought Coldcard was the ultimate, unbreakable fortress for paranoid Bitcoiners? Fixing a critical seed generation vulnerability with a firmware bug that literally kills the hardware is quite a strategic move to sell more devices! This is completely unacceptable for a premium security device, also given what is happening. Anyone else experiencing crashes or weird behavior on the new firmware? Lmk. ———-EDIT 2 DAYS LATER, BUG CONFIRMED ———- [https://github.com/Coldcard/firmware/pull/692](https://github.com/Coldcard/firmware/pull/692) ———-EDIT 3 DAYS LATER, COLD CARD REPORT ———- [https://x.com/COLDCARDwallet/status/2084632863756955661](https://x.com/COLDCARDwallet/status/2084632863756955661) I will try to test in the described way and update here about results for everyone. ——— EDIT 3 DAYS LATER, DEVICE RECOVERED / WHAT ACTUALLY HAPPENED ——— The device was not permanently bricked.Excerpt only. The complete copy is held offline and backs quotations on this site. The original publication remains the canonical public source.
-
Three comments by DonTheHolder disappeared: one body replaced with [removed] and the account shown as [deleted], two others dropped from the listing entirely. The removed text had argued for leaving hardware wallets for CEX or ETF custody.
Recovered from the Internet Archive rather than captured by this project. The row records that third-party provenance separately from captures made by this project.
What changed from the previous capture 28 lines
comment: p13yo6g parent: t3_1vct6m2 -author: DonTheHolder +author: [deleted] created_utc: 1785607309 edited: false body: -Bricked and hacked. Lovely. Investors putting trust in companies who program their crypto as its worh 63k a coin right now for a $100 wallet. So silly. - -No migration. Get off the hardware wallets and mitigate the issue by going to the CEX such as Coinbase, ETF stock, etc. - -You're going to pay taxes regardless, unless you're in another country that has none or low taxes. - -Safer for you, your family, and being wrenched 🔧 - -Not to mention there is a beneficiary path versus some posted note that your wife finds before she divorces you and has a boating accident. +[removed] comment: p13yrfv parent: t1_p13xt0j body: Nice try 😄 -comment: p158e0x -parent: t1_p1560p6 -author: DonTheHolder -created_utc: 1785620944 -edited: false -body: -Thats what the leftover Cold Card holders said. The bag holders are eliminated. - comment: p15ai96 parent: t1_p13tui2 author: SpareEconomy1849 body: Its like a dog that got beat. Still gotta eat lol -comment: p1cv0qw -parent: t1_p15pe4v -author: DonTheHolder -created_utc: 1785717135 -edited: false -body: -All garbage 🗑 CEX. Coinbase or bust. Stop shopping at Walmart and shop at Whole Foods. - comment: p1fx8i6 parent: t1_p16gdco author: buzzkillbExtracted text as captured
post: 1vct6m2 author: lucapocchio created_utc: 1785605030 title: PSA: Coldcard Mk4 BRICKED by the new emergency firmware hotfix (seed.py crash). Irony at its finest. body: Just wanted to put out a serious warning for anyone updating their Coldcard Mk4 to fix the recent RNG/seed generation vulnerability. I followed Coinkite's urgent advisory to the letter: updated to the new hotfix firmware 5.6.0, wiped my old seed, and generated a brand-new one. I even tested it, created two BIP-39 passphrases, and everything seemed fine at first. But then, the premium "Don't Trust, Verify" experience kicked in. While I was testing the passphrases—literally just entering the words and clicking apply—the device threw a critical MicroPython software crash error pointing directly to \`seed.py\` and another method. To be precise, I had done this exact same process successfully several times just before it happened, so it doesn't look completely deterministic, but the bug is definitely present and lurking in the code. I had to power cycle it, and guess what? The screen now permanently reads "BRICKED". No recovery mode, no factory reset, just a hundreds-of-dollars paperweight. I bought a bundle of 2 units directly from their site, and one is already dead due to their rushed code. If you are running the new firmware and messing with passphrases, PLEASE BE CAREFUL. This hotfix seems to have a catastrophic bug that permanently hard-locks the secure element or the firmware during passphrase application. Hey Coinkite, I thought Coldcard was the ultimate, unbreakable fortress for paranoid Bitcoiners? Fixing a critical seed generation vulnerability with a firmware bug that literally kills the hardware is quite a strategic move to sell more devices! This is completely unacceptable for a premium security device, also given what is happening. Anyone else experiencing crashes or weird behavior on the new firmware? Lmk. ———-EDIT 2 DAYS LATER, BUG CONFIRMED ———- [https://github.com/Coldcard/firmware/pull/692](https://github.com/Coldcard/firmware/pull/692) ———-EDIT 3 DAYS LATER, COLD CARD REPORT ———- [https://x.com/COLDCARDwallet/status/2084632863756955661](https://x.com/COLDCARDwallet/status/2084632863756955661) I will try to test in the described way and update here about results for everyone. ——— EDIT 3 DAYS LATER, DEVICE RECOVERED / WHAT ACTUALLY HAPPENED ——— The device was not permanently bricked.Excerpt only. The complete copy is held offline and backs quotations on this site. The original publication remains the canonical public source.
-
Reddit added a comment attributing the reported hotfix failure to absent regression testing.
Recovered from the Internet Archive rather than captured by this project. The row records that third-party provenance separately from captures made by this project.
What changed from the previous capture 8 lines
I'll let an expert take a shot at explaining it: https://youtu.be/GQOoONFuDE0?si=5-ApnzdNYWery00F&t=272 + +comment: p1xq90j +parent: t3_1vct6m2 +author: OldRefrigerator8821 +created_utc: 1785964514 +edited: false +body: +Oops forgot to do regression testingExtracted text as captured
post: 1vct6m2 author: lucapocchio created_utc: 1785605030 title: PSA: Coldcard Mk4 BRICKED by the new emergency firmware hotfix (seed.py crash). Irony at its finest. body: Just wanted to put out a serious warning for anyone updating their Coldcard Mk4 to fix the recent RNG/seed generation vulnerability. I followed Coinkite's urgent advisory to the letter: updated to the new hotfix firmware 5.6.0, wiped my old seed, and generated a brand-new one. I even tested it, created two BIP-39 passphrases, and everything seemed fine at first. But then, the premium "Don't Trust, Verify" experience kicked in. While I was testing the passphrases—literally just entering the words and clicking apply—the device threw a critical MicroPython software crash error pointing directly to \`seed.py\` and another method. To be precise, I had done this exact same process successfully several times just before it happened, so it doesn't look completely deterministic, but the bug is definitely present and lurking in the code. I had to power cycle it, and guess what? The screen now permanently reads "BRICKED". No recovery mode, no factory reset, just a hundreds-of-dollars paperweight. I bought a bundle of 2 units directly from their site, and one is already dead due to their rushed code. If you are running the new firmware and messing with passphrases, PLEASE BE CAREFUL. This hotfix seems to have a catastrophic bug that permanently hard-locks the secure element or the firmware during passphrase application. Hey Coinkite, I thought Coldcard was the ultimate, unbreakable fortress for paranoid Bitcoiners? Fixing a critical seed generation vulnerability with a firmware bug that literally kills the hardware is quite a strategic move to sell more devices! This is completely unacceptable for a premium security device, also given what is happening. Anyone else experiencing crashes or weird behavior on the new firmware? Lmk. ———-EDIT 2 DAYS LATER, BUG CONFIRMED ———- [https://github.com/Coldcard/firmware/pull/692](https://github.com/Coldcard/firmware/pull/692) ———-EDIT 3 DAYS LATER, COLD CARD REPORT ———- [https://x.com/COLDCARDwallet/status/2084632863756955661](https://x.com/COLDCARDwallet/status/2084632863756955661) I will try to test in the described way and update here about results for everyone. ——— EDIT 3 DAYS LATER, DEVICE RECOVERED / WHAT ACTUALLY HAPPENED ——— The device was not permanently bricked.Excerpt only. The complete copy is held offline and backs quotations on this site. The original publication remains the canonical public source.
-
Reddit added comments debating COLDCARD's source-verifiable licence, how the RNG defect might have been found, and moving funds generated with dice entropy.
Recovered from the Internet Archive rather than captured by this project. The row records that third-party provenance separately from captures made by this project.
What changed from the previous capture 88 lines
edited: false body: Can you elaborate on the not open source claim? Because I dont quite follow the chain of thought there. + +comment: p1w7wm1 +parent: t1_p1uuiuf +author: Yodel_And_Hodl_Mode +created_utc: 1785950559 +edited: false +body: +Open source means anyone can read the code, and anyone can use the code in their own work. It's literally open to view, copy, use, work with, build on, etc. + +Bitcoin is open source. + +ColdCard was open source until March 2021, when the license for the code was changed from Open Source to "Source Verifiable." + +Source Verifiable meant anyone could read ColdCard's code, but other devs weren't legally allowed to use it in their own work. + +Since they weren't allowed to use it anymore, they didn't use it. And since they weren't using it in their own work, they weren't battle testing it through real world use. They weren't finding bugs, which left bugs unfound and thus not reported. That's why this devastating bug lasted in ColdCard's code for almost five and a half years. + +Other devs didn't have a reason to read ColdCard's code anymore, because as of March 2021, they weren't allowed to use it in their own work. + +Part of the reason there's so much confusion is because Coinkite, makers of ColdCard, falsely promoted their products as if they were open source. They didn't say there were open source, but they used other ways of saying it. That's why people think ColdCards are open source. They're not. + +comment: p1wgnsl +parent: t1_p1w7wm1 +author: Charming-Designer944 +created_utc: 1785952701 +edited: false +body: +Thanks. Valid arguments, but I doubt there would had been a different outcome if the license did not have the non-competition clause. + +comment: p1wivih +parent: t1_p140izw +author: jdells59 +created_utc: 1785953249 +edited: false +body: +Other cases of catastrophic crashes. Don’t forget crowd strike two years ago. Impacted virtually the whole world. Microsoft involved too. Or Boeing software that killed people. Trust is earned back. Let’s hope coinkite can earn it back + +comment: p1wt25k +parent: t1_p1wgnsl +author: Yodel_And_Hodl_Mode +created_utc: 1785955776 +edited: false +body: +I strongly disagree. + +The first time a dev used that code with a wallet containing any different options for entropy (such as camera pixels), they'd have to edit that line of code, and they'd immediately have seen the bug. They'd surely have had a laugh and gotten in touch with Coinkite to let them know. + +The bug wasn't hidden. It's just that nobody but Coinkite had a reason to work with the code, so nobody found it. + +comment: p1xcuug +parent: t1_p16hrku +author: EyesFor1 +created_utc: 1785960902 +edited: false +body: +This is what I did out of an abundance of caution even thou I had used dice roll entropy. Sent to a new dice roll entropy wallet. Now I'm actively researching new hardware wallets, not rushing into anything but learning. Rushing is another proven way to loose funds. + +comment: p1xdvg6 +parent: t1_p1wt25k +author: Charming-Designer944 +created_utc: 1785961169 +edited: false +body: +Why would they need to edit which rng.c source file is used in the build? + +https://github.com/Coldcard/firmware/commit/ca72463709f4e3f8964952039d5caf955f566a87 + +Mixing of RNG sources was done at a higher level by reseeding the micropython prng. Not by modifying the trng source. And yes they likely would had laughted at that part of the code, + +Its quite likely someone who rebuilds the coldcard firmware for another device first of all uses the same CPU. Second, if they dont then they address the TRNG integration strength directly in micropython instead of trying to override it with a separate copy of the source file. + +And if Coldcard had gone the open source path and sent their improvements to the micropython stm32 TRNG integration upstream directly instead of trying to work around the micropython build then this problem would never have arised. + +On the positive side this debacle triggered a more in depth review of the Coldcard entropy collection and more improvements seem to be coming than just enabling the stm32 TRNG. Like actually using the TRNG sources in the secure elements. But that part have not finalized yet. + +comment: p1xen2l +parent: t1_p1xdvg6 +author: Yodel_And_Hodl_Mode +created_utc: 1785961371 +edited: false +body: +> Why would they need to edit which rng.c source file is used in the build? + +I'm talking about devs using the code for their own work, not using it to just run ColdCard. + +I'll let an expert take a shot at explaining it: + +https://youtu.be/GQOoONFuDE0?si=5-ApnzdNYWery00F&t=272Extracted text as captured
post: 1vct6m2 author: lucapocchio created_utc: 1785605030 title: PSA: Coldcard Mk4 BRICKED by the new emergency firmware hotfix (seed.py crash). Irony at its finest. body: Just wanted to put out a serious warning for anyone updating their Coldcard Mk4 to fix the recent RNG/seed generation vulnerability. I followed Coinkite's urgent advisory to the letter: updated to the new hotfix firmware 5.6.0, wiped my old seed, and generated a brand-new one. I even tested it, created two BIP-39 passphrases, and everything seemed fine at first. But then, the premium "Don't Trust, Verify" experience kicked in. While I was testing the passphrases—literally just entering the words and clicking apply—the device threw a critical MicroPython software crash error pointing directly to \`seed.py\` and another method. To be precise, I had done this exact same process successfully several times just before it happened, so it doesn't look completely deterministic, but the bug is definitely present and lurking in the code. I had to power cycle it, and guess what? The screen now permanently reads "BRICKED". No recovery mode, no factory reset, just a hundreds-of-dollars paperweight. I bought a bundle of 2 units directly from their site, and one is already dead due to their rushed code. If you are running the new firmware and messing with passphrases, PLEASE BE CAREFUL. This hotfix seems to have a catastrophic bug that permanently hard-locks the secure element or the firmware during passphrase application. Hey Coinkite, I thought Coldcard was the ultimate, unbreakable fortress for paranoid Bitcoiners? Fixing a critical seed generation vulnerability with a firmware bug that literally kills the hardware is quite a strategic move to sell more devices! This is completely unacceptable for a premium security device, also given what is happening. Anyone else experiencing crashes or weird behavior on the new firmware? Lmk. ———-EDIT 2 DAYS LATER, BUG CONFIRMED ———- [https://github.com/Coldcard/firmware/pull/692](https://github.com/Coldcard/firmware/pull/692) ———-EDIT 3 DAYS LATER, COLD CARD REPORT ———- [https://x.com/COLDCARDwallet/status/2084632863756955661](https://x.com/COLDCARDwallet/status/2084632863756955661) I will try to test in the described way and update here about results for everyone. ——— EDIT 3 DAYS LATER, DEVICE RECOVERED / WHAT ACTUALLY HAPPENED ——— The device was not permanently bricked.Excerpt only. The complete copy is held offline and backs quotations on this site. The original publication remains the canonical public source.
-
Reddit served an additional comment asking for clarification of the thread's claim that the device is not open source.
Recovered from the Internet Archive rather than captured by this project. The row records that third-party provenance separately from captures made by this project.
What changed from the previous capture 8 lines
edited: false body: POST MORTEM UPDATE ON POST + +comment: p1uuiuf +parent: t1_p140izw +author: Charming-Designer944 +created_utc: 1785938041 +edited: false +body: +Can you elaborate on the not open source claim? Because I dont quite follow the chain of thought there.Extracted text as captured
post: 1vct6m2 author: lucapocchio created_utc: 1785605030 title: PSA: Coldcard Mk4 BRICKED by the new emergency firmware hotfix (seed.py crash). Irony at its finest. body: Just wanted to put out a serious warning for anyone updating their Coldcard Mk4 to fix the recent RNG/seed generation vulnerability. I followed Coinkite's urgent advisory to the letter: updated to the new hotfix firmware 5.6.0, wiped my old seed, and generated a brand-new one. I even tested it, created two BIP-39 passphrases, and everything seemed fine at first. But then, the premium "Don't Trust, Verify" experience kicked in. While I was testing the passphrases—literally just entering the words and clicking apply—the device threw a critical MicroPython software crash error pointing directly to \`seed.py\` and another method. To be precise, I had done this exact same process successfully several times just before it happened, so it doesn't look completely deterministic, but the bug is definitely present and lurking in the code. I had to power cycle it, and guess what? The screen now permanently reads "BRICKED". No recovery mode, no factory reset, just a hundreds-of-dollars paperweight. I bought a bundle of 2 units directly from their site, and one is already dead due to their rushed code. If you are running the new firmware and messing with passphrases, PLEASE BE CAREFUL. This hotfix seems to have a catastrophic bug that permanently hard-locks the secure element or the firmware during passphrase application. Hey Coinkite, I thought Coldcard was the ultimate, unbreakable fortress for paranoid Bitcoiners? Fixing a critical seed generation vulnerability with a firmware bug that literally kills the hardware is quite a strategic move to sell more devices! This is completely unacceptable for a premium security device, also given what is happening. Anyone else experiencing crashes or weird behavior on the new firmware? Lmk. ———-EDIT 2 DAYS LATER, BUG CONFIRMED ———- [https://github.com/Coldcard/firmware/pull/692](https://github.com/Coldcard/firmware/pull/692) ———-EDIT 3 DAYS LATER, COLD CARD REPORT ———- [https://x.com/COLDCARDwallet/status/2084632863756955661](https://x.com/COLDCARDwallet/status/2084632863756955661) I will try to test in the described way and update here about results for everyone. ——— EDIT 3 DAYS LATER, DEVICE RECOVERED / WHAT ACTUALLY HAPPENED ——— The device was not permanently bricked.Excerpt only. The complete copy is held offline and backs quotations on this site. The original publication remains the canonical public source.
-
The Reddit post was updated with the poster’s later device-recovery account and linked official report.
Recovered from the Internet Archive rather than captured by this project. The row records that third-party provenance separately from captures made by this project.
What changed from the previous capture 74 lines
[https://github.com/Coldcard/firmware/pull/692](https://github.com/Coldcard/firmware/pull/692) - - ———-EDIT 3 DAYS LATER, COLD CARD REPORT ———- +[https://x.com/COLDCARDwallet/status/2084632863756955661](https://x.com/COLDCARDwallet/status/2084632863756955661) + +I will try to test in the described way and update here about results for everyone. + -[https://x.com/COLDCARDwallet/status/2084632863756955661](https://x.com/COLDCARDwallet/status/2084632863756955661) - -I will try to test in the described way and update here about results for everyone. +——— EDIT 3 DAYS LATER, DEVICE RECOVERED / WHAT ACTUALLY HAPPENED ——— + +The device was not permanently bricked. + + + +I fully disconnected every power source, left it unpowered for a while, and pressed a few keys for several seconds while it was disconnected, just to help drain any remaining power. After reconnecting it, the normal PIN screen came back. + + + +What seems to have happened is a temporary fault in the STM32 hardware TRNG on firmware 5.6.0. Once the TRNG enters that error state, the current firmware does not recover it properly, so later RNG calls can fail with OSError(EFAULT). + + + +This also explains why it happened while I was applying a passphrase. The BIP-39 passphrase calculation itself is deterministic, but the keypad/UI also uses the hardware RNG to randomize the scan order. The RNG fault likely surfaced through that path, caused the MicroPython crash I saw, and then left the device showing the very misleading BRICKED screen. + + + +The important part is that the fault is temporary and clears after a real power cycle: + + + +disconnect USB, Coldpower, batteries and everything else; + +leave it fully unpowered for a bit; + +while disconnected, press a few keys for several seconds; + +reconnect it using a stable power source. + + + +PR #692 documented the issue, while PR #693 contains the proper fix: + + + +[https://github.com/Coldcard/firmware/pull/693](https://github.com/Coldcard/firmware/pull/693) + + + +The new code detects the TRNG error, tries to recover it properly and retries instead of leaving the device stuck in that state. + + + +Until Coinkite releases an official signed firmware containing the #693 fix, I would avoid unnecessary passphrase/keypad testing on 5.6.0, because the issue could happen again. + + + +Also: do not install random firmware from GitHub and do not trust any “online recovery” link sent through DMs ( I actually received a bunch of those ). Wait for the official release. comment: p13tui2 parent: t3_1vct6m2 [https://github.com/Coldcard/firmware/pull/693](https://github.com/Coldcard/firmware/pull/693) Even if I was not affected (I used dice rolls + strong passphrase) I moved my funds to a new seed (generated with dice rolls, no CC involved) and I would like to update my CC mk3 but firmware hasn't been update to fix this "BRICKED" bug, or? + +comment: p1q1psp +parent: t1_p1natto +author: lucapocchio +created_utc: 1785875582 +edited: false +body: +I updated the post with the "post mortem", and how to recover it. But still can happen until new firmware is not officialy released. + +comment: p1q28tf +parent: t3_1vct6m2 +author: lucapocchio +created_utc: 1785875724 +edited: false +body: +POST MORTEM UPDATE ON POSTExtracted text as captured
post: 1vct6m2 author: lucapocchio created_utc: 1785605030 title: PSA: Coldcard Mk4 BRICKED by the new emergency firmware hotfix (seed.py crash). Irony at its finest. body: Just wanted to put out a serious warning for anyone updating their Coldcard Mk4 to fix the recent RNG/seed generation vulnerability. I followed Coinkite's urgent advisory to the letter: updated to the new hotfix firmware 5.6.0, wiped my old seed, and generated a brand-new one. I even tested it, created two BIP-39 passphrases, and everything seemed fine at first. But then, the premium "Don't Trust, Verify" experience kicked in. While I was testing the passphrases—literally just entering the words and clicking apply—the device threw a critical MicroPython software crash error pointing directly to \`seed.py\` and another method. To be precise, I had done this exact same process successfully several times just before it happened, so it doesn't look completely deterministic, but the bug is definitely present and lurking in the code. I had to power cycle it, and guess what? The screen now permanently reads "BRICKED". No recovery mode, no factory reset, just a hundreds-of-dollars paperweight. I bought a bundle of 2 units directly from their site, and one is already dead due to their rushed code. If you are running the new firmware and messing with passphrases, PLEASE BE CAREFUL. This hotfix seems to have a catastrophic bug that permanently hard-locks the secure element or the firmware during passphrase application. Hey Coinkite, I thought Coldcard was the ultimate, unbreakable fortress for paranoid Bitcoiners? Fixing a critical seed generation vulnerability with a firmware bug that literally kills the hardware is quite a strategic move to sell more devices! This is completely unacceptable for a premium security device, also given what is happening. Anyone else experiencing crashes or weird behavior on the new firmware? Lmk. ———-EDIT 2 DAYS LATER, BUG CONFIRMED ———- [https://github.com/Coldcard/firmware/pull/692](https://github.com/Coldcard/firmware/pull/692) ———-EDIT 3 DAYS LATER, COLD CARD REPORT ———- [https://x.com/COLDCARDwallet/status/2084632863756955661](https://x.com/COLDCARDwallet/status/2084632863756955661) I will try to test in the described way and update here about results for everyone. ——— EDIT 3 DAYS LATER, DEVICE RECOVERED / WHAT ACTUALLY HAPPENED ——— The device was not permanently bricked.Excerpt only. The complete copy is held offline and backs quotations on this site. The original publication remains the canonical public source.
-
The Reddit post was updated with the poster’s later device-recovery account and linked official report.
Recovered from the Internet Archive rather than captured by this project. The row records that third-party provenance separately from captures made by this project.
What changed from the previous capture 11 lines
———-EDIT 2 DAYS LATER, BUG CONFIRMED ———- -https://github.com/Coldcard/firmware/pull/692 +[https://github.com/Coldcard/firmware/pull/692](https://github.com/Coldcard/firmware/pull/692) + + + +———-EDIT 3 DAYS LATER, COLD CARD REPORT ———- + + +[https://x.com/COLDCARDwallet/status/2084632863756955661](https://x.com/COLDCARDwallet/status/2084632863756955661) + +I will try to test in the described way and update here about results for everyone. comment: p13tui2 parent: t3_1vct6m2Extracted text as captured
post: 1vct6m2 author: lucapocchio created_utc: 1785605030 title: PSA: Coldcard Mk4 BRICKED by the new emergency firmware hotfix (seed.py crash). Irony at its finest. body: Just wanted to put out a serious warning for anyone updating their Coldcard Mk4 to fix the recent RNG/seed generation vulnerability. I followed Coinkite's urgent advisory to the letter: updated to the new hotfix firmware 5.6.0, wiped my old seed, and generated a brand-new one. I even tested it, created two BIP-39 passphrases, and everything seemed fine at first. But then, the premium "Don't Trust, Verify" experience kicked in. While I was testing the passphrases—literally just entering the words and clicking apply—the device threw a critical MicroPython software crash error pointing directly to \`seed.py\` and another method. To be precise, I had done this exact same process successfully several times just before it happened, so it doesn't look completely deterministic, but the bug is definitely present and lurking in the code. I had to power cycle it, and guess what? The screen now permanently reads "BRICKED". No recovery mode, no factory reset, just a hundreds-of-dollars paperweight. I bought a bundle of 2 units directly from their site, and one is already dead due to their rushed code. If you are running the new firmware and messing with passphrases, PLEASE BE CAREFUL. This hotfix seems to have a catastrophic bug that permanently hard-locks the secure element or the firmware during passphrase application. Hey Coinkite, I thought Coldcard was the ultimate, unbreakable fortress for paranoid Bitcoiners? Fixing a critical seed generation vulnerability with a firmware bug that literally kills the hardware is quite a strategic move to sell more devices! This is completely unacceptable for a premium security device, also given what is happening. Anyone else experiencing crashes or weird behavior on the new firmware? Lmk. ———-EDIT 2 DAYS LATER, BUG CONFIRMED ———- [https://github.com/Coldcard/firmware/pull/692](https://github.com/Coldcard/firmware/pull/692) ———-EDIT 3 DAYS LATER, COLD CARD REPORT ———- [https://x.com/COLDCARDwallet/status/2084632863756955661](https://x.com/COLDCARDwallet/status/2084632863756955661) I will try to test in the described way and update here about results for everyone. comment: p13tui2 parent: t3_1vct6m2 author: redchannit8 created_utc: 1785605931Excerpt only. The complete copy is held offline and backs quotations on this site. The original publication remains the canonical public source.
-
3 new Reddit comments were posted, including Christianlutz89,lucapocchio,PopCham.
Recovered from the Internet Archive rather than captured by this project. The row records that third-party provenance separately from captures made by this project.
What changed from the previous capture 28 lines
edited: false body: Exactly what i did. Still sucks. + +comment: p1m79nt +parent: t1_p1jlpm2 +author: Christianlutz89 +created_utc: 1785835311 +edited: false +body: +I just tried it and downgraded my MK4 from 5.6.0 to 5.4.5 and it worked without any problems... I still wouldn't recommend it, as every launch on version 5.6.0 carries the risk of bricking the Coldcard. + +comment: p1myc9z +parent: t1_p1m79nt +author: lucapocchio +created_utc: 1785846289 +edited: false +body: +Yes, an hotfix is needed here for sure + +comment: p1natto +parent: t3_1vct6m2 +author: PopCham +created_utc: 1785850100 +edited: false +body: +Is this bug fixed now? + +[https://github.com/Coldcard/firmware/pull/693](https://github.com/Coldcard/firmware/pull/693) + +Even if I was not affected (I used dice rolls + strong passphrase) I moved my funds to a new seed (generated with dice rolls, no CC involved) and I would like to update my CC mk3 but firmware hasn't been update to fix this "BRICKED" bug, or?Extracted text as captured
post: 1vct6m2 author: lucapocchio created_utc: 1785605030 title: PSA: Coldcard Mk4 BRICKED by the new emergency firmware hotfix (seed.py crash). Irony at its finest. body: Just wanted to put out a serious warning for anyone updating their Coldcard Mk4 to fix the recent RNG/seed generation vulnerability. I followed Coinkite's urgent advisory to the letter: updated to the new hotfix firmware 5.6.0, wiped my old seed, and generated a brand-new one. I even tested it, created two BIP-39 passphrases, and everything seemed fine at first. But then, the premium "Don't Trust, Verify" experience kicked in. While I was testing the passphrases—literally just entering the words and clicking apply—the device threw a critical MicroPython software crash error pointing directly to \`seed.py\` and another method. To be precise, I had done this exact same process successfully several times just before it happened, so it doesn't look completely deterministic, but the bug is definitely present and lurking in the code. I had to power cycle it, and guess what? The screen now permanently reads "BRICKED". No recovery mode, no factory reset, just a hundreds-of-dollars paperweight. I bought a bundle of 2 units directly from their site, and one is already dead due to their rushed code. If you are running the new firmware and messing with passphrases, PLEASE BE CAREFUL. This hotfix seems to have a catastrophic bug that permanently hard-locks the secure element or the firmware during passphrase application. Hey Coinkite, I thought Coldcard was the ultimate, unbreakable fortress for paranoid Bitcoiners? Fixing a critical seed generation vulnerability with a firmware bug that literally kills the hardware is quite a strategic move to sell more devices! This is completely unacceptable for a premium security device, also given what is happening. Anyone else experiencing crashes or weird behavior on the new firmware? Lmk. ———-EDIT 2 DAYS LATER, BUG CONFIRMED ———- https://github.com/Coldcard/firmware/pull/692 comment: p13tui2 parent: t3_1vct6m2 author: redchannit8 created_utc: 1785605931 edited: false body: been messing with my q a bunch since updating the firmware, applied passphrases many times, havent had any issues yet. comment: p13v4zy parent: t1_p13tui2 author: lucapocchio created_utc: 1785606299 edited: falseExcerpt only. The complete copy is held offline and backs quotations on this site. The original publication remains the canonical public source.
-
Recovered from the Internet Archive rather than captured by this project. The row records that third-party provenance separately from captures made by this project.
What changed from the previous capture 0 lines
Extracted text as captured
post: 1vct6m2 author: lucapocchio created_utc: 1785605030 title: PSA: Coldcard Mk4 BRICKED by the new emergency firmware hotfix (seed.py crash). Irony at its finest. body: Just wanted to put out a serious warning for anyone updating their Coldcard Mk4 to fix the recent RNG/seed generation vulnerability. I followed Coinkite's urgent advisory to the letter: updated to the new hotfix firmware 5.6.0, wiped my old seed, and generated a brand-new one. I even tested it, created two BIP-39 passphrases, and everything seemed fine at first. But then, the premium "Don't Trust, Verify" experience kicked in. While I was testing the passphrases—literally just entering the words and clicking apply—the device threw a critical MicroPython software crash error pointing directly to \`seed.py\` and another method. To be precise, I had done this exact same process successfully several times just before it happened, so it doesn't look completely deterministic, but the bug is definitely present and lurking in the code. I had to power cycle it, and guess what? The screen now permanently reads "BRICKED". No recovery mode, no factory reset, just a hundreds-of-dollars paperweight. I bought a bundle of 2 units directly from their site, and one is already dead due to their rushed code. If you are running the new firmware and messing with passphrases, PLEASE BE CAREFUL. This hotfix seems to have a catastrophic bug that permanently hard-locks the secure element or the firmware during passphrase application. Hey Coinkite, I thought Coldcard was the ultimate, unbreakable fortress for paranoid Bitcoiners? Fixing a critical seed generation vulnerability with a firmware bug that literally kills the hardware is quite a strategic move to sell more devices! This is completely unacceptable for a premium security device, also given what is happening. Anyone else experiencing crashes or weird behavior on the new firmware? Lmk. ———-EDIT 2 DAYS LATER, BUG CONFIRMED ———- https://github.com/Coldcard/firmware/pull/692 comment: p13tui2 parent: t3_1vct6m2 author: redchannit8 created_utc: 1785605931 edited: false body: been messing with my q a bunch since updating the firmware, applied passphrases many times, havent had any issues yet. comment: p13v4zy parent: t1_p13tui2 author: lucapocchio created_utc: 1785606299 edited: falseExcerpt only. The complete copy is held offline and backs quotations on this site. The original publication remains the canonical public source.
0 presentation-noise differences. Sidebar, ticker and other page chrome churn that our review classified as not being changes to what the source says.
How to check this yourself
The excerpts and plain unified diffs above show the text this project held and how it changed. To verify a quotation, compare it against the page itself or against the Internet Archive's copies, which are independent of this project.
Complete captures are held offline rather than mirrored here, so this page shows diffs and excerpts. If a quotation is ever disputed, the full copy can be produced. Ask.
How to check this yourself
Compare the screenshot or a quotation against the original while it is available.