Skip to content
PodSubs
ShowsPeopleGuestsJobsNewsEvents
More
BlogPodCred
Menu
ShowsPeopleGuestsJobsNewsEventsBlogPodCredNetworksSign in
Join nowSign in
  • Shows
  • People
  • Jobs
  • News
  • More
    • Guests
    • Events
    • Blog
    • PodCred
    • Networks
    Join nowSign in

BitCorner

BitCorner artwork

The Coldcard Bug: What Broke, Why It Was Missed, and What To Do Right Now

Aug 1, 202614 minAudio

🎧 WATCH ON FOUNTAIN.FM & EARN SATS! ⚑ This episode PREMIERES FIRST on Fountain - earn sats while you listen. 🧠 Support independent podcasts. Escape the algorithm. πŸ‘‰ Listen & subscribe here: https://tinyurl.com/yck8u6sa ━━━━━━━━━━━━━━━━━━━━━━━━━━ 🎯 EPISODE THESIS ━━━━━━━━━━━━━━━━━━━━━━━━━━ "Not your keys, not your coins" only protects you if the keys were actually random in the first place. This week, Coinkite disclosed that certain Coldcard devices generated recovery phrases with weakened randomness - and updating the firmware doesn't fix a seed that's already out there. Coinkite's founder NVK called it "heartbroken" territory in a public apology, and committed to full transparency on how it happened. In this episode, I break down exactly what went wrong in the code, why it slipped past review for years, and - most importantly - the exact steps to check if you're affected and migrate your funds safely. This is the episode you send to anyone you know holding a Coldcard, especially if they're not glued to crypto Twitter. Every hour matters. ━━━━━━━━━━━━━━━━━━━━━━━━━━ ⏱️ TIMESTAMPS ━━━━━━━━━━━━━━━━━━━━━━━━━━ 0:00 Cold open: what happened and why it matters right now 0:45 Intro 1:30 The short version: what actually broke 3:15 How bad is "weaker randomness," really 5:00 Coinkite's response: NVK's statement and accountability 6:45 How the bug hid in open-source code for years 8:15 Exactly what to do if you're affected 9:45 Two habits to keep permanently 10:45 Close: help spread the word ━━━━━━━━━━━━━━━━━━━━━━━━━━ πŸ“– SOURCES & FURTHER READING ━━━━━━━━━━━━━━━━━━━━━━━━━━ Coinkite's official advisory: https://blog.coinkite.com/ NVK's full statement: https://x.com/nvk Full written breakdown (this episode's source article): [link] ━━━━━━━━━━━━━━━━━━━━━━━━━━ 🟧 SUPPORT THE SHOW ━━━━━━━━━━━━━━━━━━━━━━━━━━ 🟦 Blockstream Jade - The BEST Bitcoin hardware wallet. Not affected by this week's Coldcard vulnerability. πŸ” Use promo code BITCORNERPODCAST for 10% off: πŸ‘‰πŸΌ https://rewards.blockstream.com/bitcornerpodcast 🟠 Bitcoin Conference 2027 - The world's biggest Bitcoin event is coming back to Nashville, TN. July 15-17. This is the one you don't miss. 🎫 Use code BITCORNER: πŸ‘‰ https://track.flexlinkspro.com/g.ashx?foid=24.245444.6669831&trid=1537115.245444&foc=16&fot=9999&fos=6 πŸ‚ Bull Bitcoin - Buy Bitcoin directly into self-custody. No banks. No middlemen. πŸ‘‰ https://app.bullbitcoin.com/registration/bitcornerpodcast ━━━━━━━━━━━━━━━━━━━━━━━━━━ πŸ“² SUBSCRIBE TO THE PODCAST ━━━━━━━━━━━━━━━━━━━━━━━━━━ 🎧 Fountain: https://tinyurl.com/yck8u6sa 🎡 Spotify: https://tinyurl.com/bdcsyy4u 🍎 Apple Podcasts: https://tinyurl.com/cj5wkhxv 🎬 Rumble: https://tinyurl.com/3bc6bvtn πŸ“Ί YouTube: /@bitcornerpodcast ━━━━━━━━━━━━━━━━━━━━━━━━━━ πŸ‘€ CONNECT ━━━━━━━━━━━━━━━━━━━━━━━━━━ 🌐 Juan / BitCorner Website: https://bitcornershow.framer.ai/ πŸ“Έ Instagram: @bitcorner_official 🐦 Twitter/X: https://x.com/TheJuanSC πŸ“§ Email: bitcornerpodcast@proton.me ━━━━━━━━━━━━━━━━━━━━━━━━━━ Bitcoin #Coldcard #BitcoinSecurity #SelfCustody #HardwareWallet #BitCorner #NotYourKeysNotYourCoins #BitcoinEducation #SeedPhrase #BitcoinNews #KeepYourKeysSafe #BitcoinPodcast

Audio and video play straight from the show's own hosting. PodSubs stores and serves no media.

Transcript

From the show. Tap a time to play from there.

If you own a cold card, I need you to listen to this one and not having it in the background while you do something else. Because there's a firmware bug that came out a couple of hours that affects some cold card devices generated recording phrases. And the short version of all of this is that updating your firmware does not automatically fix this. If your seed was already generated, it might still be sitting on a weak kiss right now. today while you listen to this now so here's everything i know in plain language and exactly

what to do about it hello guys welcome once again to bitconner podcast i'm sorry that i'm doing this episode under the circumstances basically the episode it's basically i wrote a blog about you know the cold car rng bug and basically the article is about what happened and what to do but a bunch

of you asked for an audio version of the article of the blog so that's why i'm here so i spent the last few hours going through everything that happened and i put together a full breakdown on the blog so basically what we're calling are three things that is what actually broke how a bug like this hides in upper cells code for years without anyone catching it and most importantly exactly what to do if this affects you so if you own a cold card i need you to listen to this one

and not having it in the background while you do something else because there's a film firmware bug that came out a couple of hours that affects some cold card devices generate recorded phrases. And the short version of all of this is that updating your firmware does not automatically fix this. If your seed was already generated, it might still be sitting on a weak keys right now. Today, while you listen to this now. So here's everything I know in plain language and exactly what to do about it.

So actually I was doubting about if to do this episode on English or in Spanish, because I'm aware that half of my audience is, they speak Spanish, but I think this affects us worldwide. And I think the Spanish community can also, Bitcoiners can also speak English. So I think that it will spread faster and it will help more people if I do this episode in English. So that's why I'm doing it. So I'm going to literally read

exactly what I wrote in the blog. So you can go deeper. If you don't want to listen to me, go to the blog. I hope it helps. The only reason that I'm doing this is that I'm just a member of the community that wants to help you. And the reason is that, as you know, CoinKid, ColdCard, they don't have any user information. They don't collect information. So even MBK asked all of us to help each other through the community because there could be some users that they probably are not even aware if they are not actively on x about these attacks right now and its logic is summer most people are

in holidays are traveling are disconnected so yeah if the if we can spread this word mouth it will be awesome so if somehow this episode helps you or the blog you can go to check it out on my profile on X on Nostra on LinkedIn If that helps, just share it, guys. And again, this is the only purpose I'm doing is just like you, I'm trying to help. So let's get into it. So let's talk since the beginning. So here's the shared version. So every hardware wallet needs to generate a recovery phrase.

That's a set of words that mathematically becomes your private key. For that to be secure, the process generating those words needs to be truly unpredictably random. Because if an attacker can narrow down the possible outcomes, they can start guessing. And computers are very good at guessing quickly. So what Conkite found is that on certain framework versions, the randomness behind that process was weaker than it was supposed to be. Not broken in an obvious way. The device still worked fine. It still gave you a seed phrase that looked completely normal.

But under the hood, the pool of possible outcomes was much smaller than it should have been. And here's the part that trips people up. Updating your firmware fixes this going forward. And it does not fix a seed phrase you already generated. That seed is what it is. Permanently until you actually move your funds to a brand new one. So who is actually affected? So it's call card MK3 owners on firmware 4.0.1 through 4.1.9 and MK4, MK5 and Q owners on certain firmware releases before the fix.

So also who is not affected? The tab signers, the open dime, and the SATX card. Those runes completely a different code. And the fixed framework is already out for every affected model. So that's important. So step one, no matter what, what you need to do is update. But, and I want to say this twice because it's the single most important thing in this whole episode. Updating alone is not enough if your existing seed was generated on the broken framework. So that's important, guys. And by the way, I'm sorry, my English, if sometimes I'm pronounced badly, you know, that is not my main language.

And literally, as I told you, I'm reading exactly what I wrote. So, so yeah. So anyways, now I want to give you real numbers here because how bad is this? But for real. So because weaker randomness can sound either scarier or more harmless than it actually is, depending on how it's phrased. So, CoinKite estimates the effect in randomness fell to around 40 bits on the MK3, around 72 bits on the MK4, the Q, and the MK5. Those models had a little extra randomness mixing from other components almost by accident, which helped somewhat.

So for comparison, a properly generated seed is supposed to sit around 128 or 256 bits of randomness. Going from 128 down to 40 isn't somewhat weaker. Think of it like this. 128 bits is a log with more possible combinations that are atoms in the visible universe. So 40 bits is a log that world-resourced attackers could realistically start working through. It's still not hard, not universalized, hard anymore.

So now two things pull you back out of danger And if either applies to you these matter a lot So pay attention So number one if you generated your seed using at least 50 independent private dice rolls so you added your own physical randomness on top of what the device did, CoinKite says they don't consider that seed at risk from this specific bug. And second, you have a strong unique passphrase on your wallet, not short, not reused, not something quoted from somewhere.

that passphrase created a functionally different wallet layer on the top and that meaningful reduce the immediate risk so if neither of those applies to you the threat is real it's not theoretical and conkite themselves aren't hanging on that point so how this happened okay quick technical detour because i think it's actually fascinating and it explains something important about why just read the code it's open source isn't the safety net people assume so back in 2021 cold Card moved some of their cryptographic code over to a library called libsecp256k1, which for what's worth is the same library Bitcoin Core itself uses.

Good decision on its own. But that migration pulled it in a supporting piece of software. And somewhere in that process, the actual code patch responsible for generating your wallet seed code quickly rewired. So instead of pulling randomness from cold cards, portal built hardware random number generator, it started to solve into a generic software fallback that was never designed to be cryptographically secure. So here's the part that made this invisible for years, both the correct hardware generator and incorrect software fallback used the

exact same function name. So if you were out in this code, you could see the well-built secure hardware generator sitting right there, confirm it looked correct, and never realized that the seed generation process was actually calling it. And underneath that, there was a second smaller bug, a safety check that was supposed to stop the software from billing at all if the hardware generator wasn't properly connected. But that check only verified whether a setting existed, not whether it was set to something meaningful.

And in Colcar's case, it existed. it was just set to zero so technical present functionality useless so quite individually reasonable looking mistakes let's take on the top of each other and in code that's been seen in public view the entire time guys so all right so this is beautiful now we know what happened but what to actually do and this is the part that matters most so let me out this clearly and I'll go slow. So first, don't panic. Don't do something stupid.

Yes, the clock is ticking, but play smart. So first, step zero, I will say breathe. All right, breathe. There's nothing wrong. You're going to be safe. So step one, update to the fixed framework. Don't generate anything new until you have done this. Second, step two, generate a completely new seed. This is the step people mess up under stress. Do not restore your all-recovered phrase into the new wallet. That just carries the same potential weak key forward. You want the device generating something brand new from scratch.

All right. This is step two. Step three, verify everything directly on the device screen, not your phone, not your laptop the actual hardware screen Confirm your wallet fingerprint and receive an address match what you are seeing elsewhere if they don match stop immediately step four send a small test transaction first wait for it to confirm say that it show up in a completely fresh session uh not the same type you were already looking at all of them move the rest of all your funds all right this is really important step five

don't destroy your whole backup yet hold on to it until the new wallet is fully verified and the one is confirmed completely empty including any small default amounts of transactions you might have forgotten about if you destroyed that backup too early if you destroyed that backup too early and there's still a balance sitting there it becomes permanently unrecognizable so be aware of that and step six once everything is confirmed migrated retire the old phrase for good thread or bond a paper backup do whatever you want physically destroy it even the metal never use it forget

about it forever it's done all right never existed bad completely dead that it died so i think we're going to wrap it up this now i hope it helps i told you i'm just reading what i wrote on the blog so i think we're gonna leave this with two apps to keep forever and regardless of what hardware wallet you end up using for long term one always verify on the device screen itself every single time before you approve any transaction not in the app not in the browser not the device that

screen is the one thing an attacker can quickly manipulate from elsewhere second firmware only ever comes from official sources if you get an email from a firmware update no matter how officially it looks that's efficient attempt go to the manufacturer's site directly every time so in this case for the updates i will even tell go to my blog and then link go to the link that i post about the updated framework that cold card coin kite provide no google cold kite go to the framework and do directly everything from their own website so that's the full story guys if you

take one thing away from this episode let me this updating your framework is necessary but it's not sufficient if your seed was generated on effective framework you need to actively generate a new one and migrate today now not this week now you cannot wait on this and if you know someone with a cold card who isn't the type to be following this stuff closely a parent a friend who set up their hardware wallet years ago and it hasn't true about it about it since send them this episode or the full write-up coin count themselves said it plainly they can reach affected users directly

so the community you me everyone is the distribution channel here that's generally one of the most useful things you can do today so i got the complete ready breakdown on the blog with all searching and linked of the coin kite official adversary but again i'll tell you go directly to google and and yeah update from there i'm not even gonna leave the links of coin kite as i normally do in this podcast episode do your own research and i think that's it i think this has covered all i hope it helps i'm sorry that it's under these circumstances actually i was i was working on

the new episode i know that i haven't posted a new episode for so long but trust me guys new episodes are coming we have a bunch now even in the middle of the summer so yeah i took my summer break before but now we're back so see you next week and take care ciao

Open the transcript file

Hosts and Guests

Nobody is credited on this episode yet.

Credit the people on this episode

Be the first to rate this episode

More episodes

All episodes
  1. Ex-Mt. Gox CEO Found a Spy in a Ledger: Mark Karpelès

    Nov 3, 20261 hr 5 minAudio

    Mark Karpelès, the former CEO of Mt. Gox, tells the story in his own words: how he bought the exchange in 2011 with no money down, the June 2011 hack, the 2013 US seizure and blocked wires, a year detained pending...

    Credit the people on this episode

  2. How Bitcoin 2027 Gets Built: Justin Doochin (BTC Inc)

    Oct 27, 202642 minAudio

    Justin Doochin, Head of Events at BTC Inc, explains how the biggest Bitcoin conferences get built: Bitcoin Amsterdam (Nov 5-6, 2026), the new AI event i27 in San Francisco (Apr 22-23, 2027) and Bitcoin 2027 in Nashville...

    Credit the people on this episode

  3. Miss Bitcoin Alejandra Guajardo: de Miss Universo a Bitcoin

    Oct 20, 202640 minAudio

    Alejandra Guajardo, Miss Bitcoin y Miss El Salvador, nos cuenta cΓ³mo pasΓ³ de nueve certΓ‘menes sin ganar a Miss Universo, cΓ³mo llegΓ³ a Bitcoin y por quΓ© hoy enseΓ±a Bitcoin en escuelas pΓΊblicas de El Salvador. Primer...

    Credit the people on this episode

  4. How to Get a Bitcoin Job Without Waiting | Thunder

    Oct 13, 202648 minAudio

    Most people wait a year for the perfect Bitcoin job. Thunder says that's the mistake. Thunder, Head of Talent in the Bitcoin industry, explains what recruiters really look for, why waiting for the "perfect" Bitcoin role...

    Credit the people on this episode

  5. Bitcoin Power Law Explained: Where Are We in the Cycle? | Matthew Mezinskis

    Oct 2, 20261 hr 12 minAudio

    🎧 WATCH ON FOUNTAIN.FM & EARN SATS! ⚑ This episode PREMIERES FIRST on Fountain - earn sats while you listen. 🧠 Support independent podcasts. Escape the algorithm. πŸ‘‰ Listen & subscribe here:...

    Credit the people on this episode