1
00:00:00,000 --> 00:00:07,360
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.

2
00:00:07,480 --> 00:00:15,540
Because there's a firmware bug that came out a couple of hours that affects some cold card devices generated recording phrases.

3
00:00:15,800 --> 00:00:22,260
And the short version of all of this is that updating your firmware does not automatically fix this.

4
00:00:22,340 --> 00:00:27,740
If your seed was already generated, it might still be sitting on a weak kiss right now.

5
00:00:27,740 --> 00:00:34,260
today while you listen to this now so here's everything i know in plain language and exactly

6
00:00:34,260 --> 00:00:35,920
what to do about it

7
00:00:35,920 --> 00:00:51,320
hello guys welcome once again to bitconner podcast i'm sorry that i'm doing this episode

8
00:00:51,320 --> 00:00:58,180
under the circumstances basically the episode it's basically i wrote a blog about you know the

9
00:00:58,180 --> 00:01:04,900
cold car rng bug and basically the article is about what happened and what to do but a bunch

10
00:01:04,900 --> 00:01:12,560
of you asked for an audio version of the article of the blog so that's why i'm here so i spent the

11
00:01:12,560 --> 00:01:18,440
last few hours going through everything that happened and i put together a full breakdown

12
00:01:18,440 --> 00:01:26,820
on the blog so basically what we're calling are three things that is what actually broke how a

13
00:01:26,820 --> 00:01:32,360
bug like this hides in upper cells code for years without anyone catching it and most importantly

14
00:01:32,360 --> 00:01:39,520
exactly what to do if this affects you so if you own a cold card i need you to listen to this one

15
00:01:39,520 --> 00:01:45,220
and not having it in the background while you do something else because there's a film firmware bug

16
00:01:45,220 --> 00:01:47,420
that came out a couple of hours

17
00:01:47,420 --> 00:01:49,840
that affects some cold card devices

18
00:01:49,840 --> 00:01:51,200
generate recorded phrases.

19
00:01:51,460 --> 00:01:53,560
And the short version of all of this

20
00:01:53,560 --> 00:01:55,700
is that updating your firmware

21
00:01:55,700 --> 00:01:57,940
does not automatically fix this.

22
00:01:58,020 --> 00:02:00,160
If your seed was already generated,

23
00:02:00,400 --> 00:02:03,420
it might still be sitting on a weak keys right now.

24
00:02:03,800 --> 00:02:06,400
Today, while you listen to this now.

25
00:02:06,400 --> 00:02:09,140
So here's everything I know in plain language

26
00:02:09,140 --> 00:02:11,460
and exactly what to do about it.

27
00:02:11,600 --> 00:02:13,460
So actually I was doubting

28
00:02:13,460 --> 00:02:17,060
about if to do this episode on English or in Spanish,

29
00:02:17,060 --> 00:02:20,640
because I'm aware that half of my audience is,

30
00:02:20,980 --> 00:02:22,440
they speak Spanish,

31
00:02:22,640 --> 00:02:25,140
but I think this affects us worldwide.

32
00:02:25,640 --> 00:02:27,940
And I think the Spanish community can also,

33
00:02:28,120 --> 00:02:29,720
Bitcoiners can also speak English.

34
00:02:29,720 --> 00:02:33,360
So I think that it will spread faster

35
00:02:33,360 --> 00:02:35,840
and it will help more people

36
00:02:35,840 --> 00:02:38,180
if I do this episode in English.

37
00:02:38,420 --> 00:02:39,600
So that's why I'm doing it.

38
00:02:39,700 --> 00:02:41,880
So I'm going to literally read

39
00:02:41,880 --> 00:02:43,840
exactly what I wrote in the blog.

40
00:02:43,940 --> 00:02:44,960
So you can go deeper.

41
00:02:45,140 --> 00:02:46,260
If you don't want to listen to me,

42
00:02:46,320 --> 00:02:46,920
go to the blog.

43
00:02:47,020 --> 00:02:47,1000
I hope it helps.

44
00:02:48,200 --> 00:02:49,600
The only reason that I'm doing this

45
00:02:49,600 --> 00:02:51,540
is that I'm just a member of the community

46
00:02:51,540 --> 00:02:52,900
that wants to help you.

47
00:02:53,180 --> 00:02:54,720
And the reason is that,

48
00:02:54,920 --> 00:02:55,320
as you know,

49
00:02:55,480 --> 00:02:55,1000
CoinKid,

50
00:02:56,180 --> 00:02:57,160
ColdCard,

51
00:02:57,360 --> 00:03:00,140
they don't have any user information.

52
00:03:00,280 --> 00:03:01,360
They don't collect information.

53
00:03:01,740 --> 00:03:04,220
So even MBK asked all of us

54
00:03:04,220 --> 00:03:06,780
to help each other through the community

55
00:03:06,780 --> 00:03:09,140
because there could be some users

56
00:03:09,140 --> 00:03:11,600
that they probably are not even aware

57
00:03:11,600 --> 00:03:17,240
if they are not actively on x about these attacks right now and its logic is summer most people are

58
00:03:17,240 --> 00:03:33,362
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

59
00:03:33,662 --> 00:03:35,822
If that helps, just share it, guys.

60
00:03:35,822 --> 00:03:40,222
And again, this is the only purpose I'm doing is just like you, I'm trying to help.

61
00:03:40,482 --> 00:03:42,222
So let's get into it.

62
00:03:42,422 --> 00:03:44,442
So let's talk since the beginning.

63
00:03:44,762 --> 00:03:46,002
So here's the shared version.

64
00:03:46,002 --> 00:03:50,422
So every hardware wallet needs to generate a recovery phrase.

65
00:03:50,662 --> 00:03:54,522
That's a set of words that mathematically becomes your private key.

66
00:03:54,762 --> 00:04:00,242
For that to be secure, the process generating those words needs to be truly unpredictably random.

67
00:04:00,442 --> 00:04:04,682
Because if an attacker can narrow down the possible outcomes, they can start guessing.

68
00:04:04,982 --> 00:04:08,102
And computers are very good at guessing quickly.

69
00:04:08,102 --> 00:04:15,962
So what Conkite found is that on certain framework versions, the randomness behind that process was weaker than it was supposed to be.

70
00:04:16,002 --> 00:04:18,382
Not broken in an obvious way.

71
00:04:18,582 --> 00:04:19,922
The device still worked fine.

72
00:04:20,142 --> 00:04:22,582
It still gave you a seed phrase that looked completely normal.

73
00:04:22,802 --> 00:04:28,102
But under the hood, the pool of possible outcomes was much smaller than it should have been.

74
00:04:28,102 --> 00:04:31,602
And here's the part that trips people up.

75
00:04:31,762 --> 00:04:35,602
Updating your firmware fixes this going forward.

76
00:04:35,822 --> 00:04:38,762
And it does not fix a seed phrase you already generated.

77
00:04:39,042 --> 00:04:41,002
That seed is what it is.

78
00:04:41,182 --> 00:04:45,362
Permanently until you actually move your funds to a brand new one.

79
00:04:45,362 --> 00:05:02,362
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.

80
00:05:02,362 --> 00:05:04,262
So also who is not affected?

81
00:05:04,602 --> 00:05:07,802
The tab signers, the open dime, and the SATX card.

82
00:05:08,022 --> 00:05:10,402
Those runes completely a different code.

83
00:05:10,682 --> 00:05:14,722
And the fixed framework is already out for every affected model.

84
00:05:14,862 --> 00:05:15,622
So that's important.

85
00:05:15,982 --> 00:05:19,102
So step one, no matter what, what you need to do is update.

86
00:05:19,382 --> 00:05:25,082
But, and I want to say this twice because it's the single most important thing in this whole episode.

87
00:05:25,342 --> 00:05:29,862
Updating alone is not enough if your existing seed was generated on the broken framework.

88
00:05:30,042 --> 00:05:31,222
So that's important, guys.

89
00:05:31,222 --> 00:05:36,802
And by the way, I'm sorry, my English, if sometimes I'm pronounced badly, you know, that is not my main language.

90
00:05:36,982 --> 00:05:39,962
And literally, as I told you, I'm reading exactly what I wrote.

91
00:05:40,242 --> 00:05:40,722
So, so yeah.

92
00:05:40,802 --> 00:05:46,042
So anyways, now I want to give you real numbers here because how bad is this?

93
00:05:46,242 --> 00:05:46,742
But for real.

94
00:05:46,942 --> 00:05:53,142
So because weaker randomness can sound either scarier or more harmless than it actually is, depending on how it's phrased.

95
00:05:53,142 --> 00:06:04,782
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.

96
00:06:04,962 --> 00:06:11,702
Those models had a little extra randomness mixing from other components almost by accident, which helped somewhat.

97
00:06:11,702 --> 00:06:20,702
So for comparison, a properly generated seed is supposed to sit around 128 or 256 bits of randomness.

98
00:06:20,862 --> 00:06:25,402
Going from 128 down to 40 isn't somewhat weaker.

99
00:06:25,502 --> 00:06:26,522
Think of it like this.

100
00:06:26,842 --> 00:06:33,502
128 bits is a log with more possible combinations that are atoms in the visible universe.

101
00:06:33,762 --> 00:06:40,422
So 40 bits is a log that world-resourced attackers could realistically start working through.

102
00:06:40,422 --> 00:06:43,722
It's still not hard, not universalized, hard anymore.

103
00:06:43,942 --> 00:06:57,604
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

104
00:06:57,804 --> 00:07:01,224
so you added your own physical randomness on top of what the device did,

105
00:07:01,484 --> 00:07:06,204
CoinKite says they don't consider that seed at risk from this specific bug.

106
00:07:06,424 --> 00:07:11,164
And second, you have a strong unique passphrase on your wallet,

107
00:07:11,664 --> 00:07:14,644
not short, not reused, not something quoted from somewhere.

108
00:07:14,644 --> 00:07:20,464
that passphrase created a functionally different wallet layer on the top and that meaningful reduce

109
00:07:20,464 --> 00:07:25,204
the immediate risk so if neither of those applies to you the threat is real it's not theoretical

110
00:07:25,204 --> 00:07:31,404
and conkite themselves aren't hanging on that point so how this happened okay quick technical

111
00:07:31,404 --> 00:07:36,304
detour because i think it's actually fascinating and it explains something important about why

112
00:07:36,304 --> 00:07:43,404
just read the code it's open source isn't the safety net people assume so back in 2021 cold

113
00:07:43,404 --> 00:07:56,644
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.

114
00:07:56,764 --> 00:07:57,984
Good decision on its own.

115
00:07:57,984 --> 00:08:01,644
But that migration pulled it in a supporting piece of software.

116
00:08:01,924 --> 00:08:07,984
And somewhere in that process, the actual code patch responsible for generating your wallet seed code quickly rewired.

117
00:08:07,984 --> 00:08:11,224
So instead of pulling randomness from cold cards,

118
00:08:11,224 --> 00:08:13,744
portal built hardware random number generator,

119
00:08:13,744 --> 00:08:18,264
it started to solve into a generic software fallback that was never designed to

120
00:08:18,264 --> 00:08:22,144
be cryptographically secure.

121
00:08:22,144 --> 00:08:25,504
So here's the part that made this invisible for years,

122
00:08:25,504 --> 00:08:29,944
both the correct hardware generator and incorrect software fallback used the

123
00:08:29,944 --> 00:08:31,584
exact same function name.

124
00:08:31,584 --> 00:08:33,904
So if you were out in this code,

125
00:08:33,904 --> 00:08:38,084
you could see the well-built secure hardware generator sitting right there,

126
00:08:38,304 --> 00:08:39,484
confirm it looked correct,

127
00:08:39,664 --> 00:08:43,544
and never realized that the seed generation process was actually calling it.

128
00:08:43,724 --> 00:08:46,124
And underneath that, there was a second smaller bug,

129
00:08:46,324 --> 00:08:51,484
a safety check that was supposed to stop the software from billing at all

130
00:08:51,484 --> 00:08:54,204
if the hardware generator wasn't properly connected.

131
00:08:54,424 --> 00:08:57,824
But that check only verified whether a setting existed,

132
00:08:58,064 --> 00:09:00,884
not whether it was set to something meaningful.

133
00:09:01,064 --> 00:09:02,864
And in Colcar's case, it existed.

134
00:09:02,864 --> 00:09:10,004
it was just set to zero so technical present functionality useless so quite individually

135
00:09:10,004 --> 00:09:14,944
reasonable looking mistakes let's take on the top of each other and in code that's been seen in

136
00:09:14,944 --> 00:09:21,164
public view the entire time guys so all right so this is beautiful now we know what happened

137
00:09:21,164 --> 00:09:27,424
but what to actually do and this is the part that matters most so let me out this clearly

138
00:09:27,424 --> 00:09:28,984
and I'll go slow.

139
00:09:29,204 --> 00:09:30,504
So first, don't panic.

140
00:09:30,624 --> 00:09:31,764
Don't do something stupid.

141
00:09:32,244 --> 00:09:34,984
Yes, the clock is ticking, but play smart.

142
00:09:34,984 --> 00:09:37,784
So first, step zero, I will say breathe.

143
00:09:38,004 --> 00:09:38,684
All right, breathe.

144
00:09:39,284 --> 00:09:39,944
There's nothing wrong.

145
00:09:40,324 --> 00:09:41,024
You're going to be safe.

146
00:09:41,384 --> 00:09:44,084
So step one, update to the fixed framework.

147
00:09:44,424 --> 00:09:46,984
Don't generate anything new until you have done this.

148
00:09:47,224 --> 00:09:50,724
Second, step two, generate a completely new seed.

149
00:09:50,924 --> 00:09:53,504
This is the step people mess up under stress.

150
00:09:53,744 --> 00:09:57,184
Do not restore your all-recovered phrase into the new wallet.

151
00:09:57,424 --> 00:10:00,624
That just carries the same potential weak key forward.

152
00:10:00,664 --> 00:10:03,884
You want the device generating something brand new from scratch.

153
00:10:04,024 --> 00:10:04,424
All right.

154
00:10:04,464 --> 00:10:05,324
This is step two.

155
00:10:05,364 --> 00:10:10,284
Step three, verify everything directly on the device screen, not your phone,

156
00:10:10,284 --> 00:10:24,906
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

157
00:10:24,906 --> 00:10:30,846
confirm say that it show up in a completely fresh session uh not the same type you were already

158
00:10:30,846 --> 00:10:36,086
looking at all of them move the rest of all your funds all right this is really important step five

159
00:10:36,086 --> 00:10:41,846
don't destroy your whole backup yet hold on to it until the new wallet is fully verified and the

160
00:10:41,846 --> 00:10:46,246
one is confirmed completely empty including any small default amounts of transactions you might

161
00:10:46,246 --> 00:10:51,886
have forgotten about if you destroyed that backup too early if you destroyed that backup too early

162
00:10:51,886 --> 00:10:58,546
and there's still a balance sitting there it becomes permanently unrecognizable so be aware

163
00:10:58,546 --> 00:11:05,106
of that and step six once everything is confirmed migrated retire the old phrase for good thread or

164
00:11:05,106 --> 00:11:11,026
bond a paper backup do whatever you want physically destroy it even the metal never use it forget

165
00:11:11,026 --> 00:11:17,426
about it forever it's done all right never existed bad completely dead that it died so i think we're

166
00:11:17,426 --> 00:11:23,266
going to wrap it up this now i hope it helps i told you i'm just reading what i wrote on the blog

167
00:11:23,266 --> 00:11:32,546
so i think we're gonna leave this with two apps to keep forever and regardless of what hardware

168
00:11:32,546 --> 00:11:38,446
wallet you end up using for long term one always verify on the device screen itself every single

169
00:11:38,446 --> 00:11:43,786
time before you approve any transaction not in the app not in the browser not the device that

170
00:11:43,786 --> 00:11:49,366
screen is the one thing an attacker can quickly manipulate from elsewhere second firmware only

171
00:11:49,366 --> 00:11:54,126
ever comes from official sources if you get an email from a firmware update no matter how

172
00:11:54,126 --> 00:11:59,026
officially it looks that's efficient attempt go to the manufacturer's site directly every time so

173
00:11:59,026 --> 00:12:05,926
in this case for the updates i will even tell go to my blog and then link go to the link that i post

174
00:12:05,926 --> 00:12:13,626
about the updated framework that cold card coin kite provide no google cold kite go to the

175
00:12:13,626 --> 00:12:19,186
framework and do directly everything from their own website so that's the full story guys if you

176
00:12:19,186 --> 00:12:24,746
take one thing away from this episode let me this updating your framework is necessary but it's not

177
00:12:24,746 --> 00:12:29,726
sufficient if your seed was generated on effective framework you need to actively generate a new one

178
00:12:29,726 --> 00:12:35,986
and migrate today now not this week now you cannot wait on this and if you know someone with

179
00:12:35,986 --> 00:12:41,326
a cold card who isn't the type to be following this stuff closely a parent a friend who set up

180
00:12:41,326 --> 00:12:47,106
their hardware wallet years ago and it hasn't true about it about it since send them this episode

181
00:12:47,106 --> 00:12:52,966
or the full write-up coin count themselves said it plainly they can reach affected users directly

182
00:12:52,966 --> 00:12:58,266
so the community you me everyone is the distribution channel here that's generally one of the most

183
00:12:58,266 --> 00:13:04,046
useful things you can do today so i got the complete ready breakdown on the blog with all

184
00:13:04,046 --> 00:13:08,486
searching and linked of the coin kite official adversary but again i'll tell you go directly to

185
00:13:08,486 --> 00:13:15,706
google and and yeah update from there i'm not even gonna leave the links of coin kite as i normally do

186
00:13:15,706 --> 00:13:22,286
in this podcast episode do your own research and i think that's it i think this has covered all i

187
00:13:22,286 --> 00:13:28,186
hope it helps i'm sorry that it's under these circumstances actually i was i was working on

188
00:13:28,186 --> 00:13:33,086
the new episode i know that i haven't posted a new episode for so long but trust me guys new

189
00:13:33,086 --> 00:13:37,546
episodes are coming we have a bunch now even in the middle of the summer so yeah i took my

190
00:13:37,546 --> 00:13:43,326
summer break before but now we're back so see you next week and take care ciao
