1 00:00:00,169 --> 00:00:03,373 One manufacturer's product had a bug, and 2 00:00:03,574 --> 00:00:06,738 some bad actor exploited that bug to 3 00:00:06,798 --> 00:00:10,042 drain some people's wallets. Events like this, at some 4 00:00:10,102 --> 00:00:13,386 level, are required to push people to 5 00:00:13,446 --> 00:00:17,151 go the distance with their due diligence. Bitcoin is ongoing tech. It's 6 00:00:17,191 --> 00:00:20,434 not a set it and forget it. You can't have like a bulletproof setup today and 7 00:00:20,474 --> 00:00:23,696 expect it to remain bulletproof for the next 15 years. It's not going to 8 00:00:23,736 --> 00:00:26,958 work. You will become your own risk if that's the approach that 9 00:00:27,599 --> 00:00:31,001 Should people who currently hold significant amounts on 10 00:00:34,164 --> 00:00:37,566 We can create a setup that's ultra complicated, but it's of no use 11 00:00:37,786 --> 00:00:41,389 if there's a risk of the user screwing it up, right? And you essentially 12 00:00:41,449 --> 00:00:44,651 lock yourself out of your funds. And that's even worse. than running into 13 00:00:44,691 --> 00:00:48,193 a bug because you know it's your fault. This casts a spotlight on 14 00:00:48,253 --> 00:00:51,816 self-custody in general. Is self-custody a risky thing? Is 15 00:00:51,896 --> 00:00:55,077 it in danger? Has it died? Is it time to, you 16 00:00:56,658 --> 00:00:59,900 Tony from the Bitcoin Way. Hey, welcome to the Crypto Collective. Hey, great 17 00:00:59,920 --> 00:01:03,202 to see you, mate. How you been? Fantastic, Matthew. Thank you for having me 18 00:01:03,242 --> 00:01:06,454 back on, man. It's good to be here. Yeah, look, thank you so much for taking 19 00:01:06,474 --> 00:01:09,616 the time to come and join our community because there's so much has been 20 00:01:09,656 --> 00:01:13,018 happening in the Bitcoin space, particularly with the 21 00:01:13,098 --> 00:01:16,760 cold card issue and people getting their Bitcoin hacked and 22 00:01:16,820 --> 00:01:20,142 stolen. And so I just really want to dive deep on that because there's still 23 00:01:20,162 --> 00:01:23,264 a lot of questions that people have about protecting their wealth. And I just want to say from the 24 00:01:23,304 --> 00:01:26,586 outset, too, that I'm a client of the Bitcoin way. I've been using 25 00:01:26,606 --> 00:01:30,308 your service for many, many years now. I've been absolutely over the moon with 26 00:01:30,568 --> 00:01:33,709 the delivery and the service. And I was one of those 27 00:01:33,769 --> 00:01:37,211 people who had the cold card Q, which we all thought 28 00:01:37,571 --> 00:01:41,232 was the Rolls Royce of protecting our wealth. So 29 00:01:44,193 --> 00:01:48,614 Let me just start from the very beginning to explain what took place. a 30 00:01:48,674 --> 00:01:51,775 bug was discovered, right? It's not necessarily a hack. It 31 00:01:51,816 --> 00:01:55,217 was a bug that was uncovered because of the new landscape that 32 00:01:55,257 --> 00:01:58,478 we find ourselves in. Like this thing went unnoticed for five years and 33 00:01:58,638 --> 00:02:02,240 what flipped it was an AI agent, you 34 00:02:02,260 --> 00:02:05,421 know, scoured it and within minutes detected, you know, the few 35 00:02:05,461 --> 00:02:08,782 lines that caused all this. And of course, some bad actors out there, 36 00:02:08,822 --> 00:02:13,044 you know, use that for, you know, doing bad things. And unfortunately, some 37 00:02:13,084 --> 00:02:16,486 people woke up to a drained wallet. Innocent people done everything 38 00:02:16,526 --> 00:02:19,792 by the book, Um, thought they were safe and then woke up to like 39 00:02:19,972 --> 00:02:23,441 one of the most brutal reality. So our hearts go out to these folks, 40 00:02:23,481 --> 00:02:26,725 you know, It's horrible what happened, there's 41 00:02:26,745 --> 00:02:30,988 no other way to put it. However, when you 42 00:02:31,028 --> 00:02:34,311 zoom out a little bit, this also casts a 43 00:02:34,371 --> 00:02:37,614 spotlight on self-custody in general. Why did 44 00:02:37,654 --> 00:02:40,936 this happen? Is self-custody a 45 00:02:40,996 --> 00:02:44,499 risky thing? Is it in danger? Has it died? Is 46 00:02:44,559 --> 00:02:47,802 it time to leave the idea behind? Absolutely not. 47 00:02:48,542 --> 00:02:52,606 Self-custody did not fail. 48 00:02:52,767 --> 00:02:56,310 Bitcoin has not changed, nothing has been modified, 49 00:02:56,450 --> 00:02:59,654 altered, weakened by any stretch. What 50 00:02:59,734 --> 00:03:02,817 happened was that one manufacturer's product had a 51 00:03:02,857 --> 00:03:06,641 bug. and some bad actor exploited 52 00:03:06,701 --> 00:03:10,003 that bug to drain some people's wallets. But 53 00:03:10,204 --> 00:03:14,287 the silver lining to all of this is that it brought attention to, 54 00:03:14,507 --> 00:03:18,030 one, the changing landscape with AI, but to attention to 55 00:03:18,070 --> 00:03:22,154 a weakness and a lot of other weaknesses that the 56 00:03:22,194 --> 00:03:25,617 community in general perhaps have been too complacent about. 57 00:03:26,257 --> 00:03:30,060 So it doubled down the efforts on solidifying 58 00:03:30,120 --> 00:03:33,743 self-custody. For me, If enough time passes, we're 59 00:03:33,783 --> 00:03:37,326 probably going to look back at this and it's going to be one of these points 60 00:03:37,867 --> 00:03:41,490 that's really upgraded everything about Bitcoin self-custody. 61 00:03:41,590 --> 00:03:44,992 Because now the community rallied together in a way that 62 00:03:45,012 --> 00:03:48,315 I haven't seen for a very long time. We've 63 00:03:48,355 --> 00:03:51,738 got OG developers now that are leveraging the 64 00:03:51,818 --> 00:03:54,900 same tools that uncovered that bug in order to 65 00:03:54,960 --> 00:03:58,884 find vulnerabilities and glitches and flaws in almost every 66 00:03:58,964 --> 00:04:02,286 popular hardware and software that is used in the Bitcoin space. 67 00:04:02,967 --> 00:04:06,490 And, you know, very quickly it did find thousands of 68 00:04:06,550 --> 00:04:10,474 vulnerabilities and critical flaws. Does 69 00:04:10,494 --> 00:04:13,797 that mean, you know, it's bad news? Absolutely not. Because the 70 00:04:13,837 --> 00:04:17,161 fact that we found them, good actors are able to fix them 71 00:04:17,601 --> 00:04:21,104 very quickly. And at some point that makes any 72 00:04:21,204 --> 00:04:24,327 future attacks that much harder. Because, you know, 73 00:04:24,347 --> 00:04:27,690 and again, if they come, We see the weaknesses, we 74 00:04:27,710 --> 00:04:31,152 level up, we upgrade, we fix. And at some point, you know, they 75 00:04:31,172 --> 00:04:34,295 just become, you know, like just noise that's out 76 00:04:34,335 --> 00:04:37,537 there. But this is part of the journey. You know, we've never had anything like 77 00:04:37,597 --> 00:04:40,779 Bitcoin before. There's a lot we don't know. I mean, there's a 78 00:04:40,819 --> 00:04:43,921 lot we do know, but there's still, you know, like nobody has a crystal ball to 79 00:04:43,961 --> 00:04:47,544 predict what's going to happen in six months or 60 years or whatever. But 80 00:04:47,564 --> 00:04:51,126 as long as Bitcoin remains decentralized and secure, nothing 81 00:04:51,186 --> 00:04:54,607 is going to change that trajectory. As they say, nothing 82 00:04:54,627 --> 00:04:57,848 is going to stop that train. Bitcoin, in my view, will become the 83 00:04:57,888 --> 00:05:01,649 future of money. The tools to use it will become simplified. We 84 00:05:01,689 --> 00:05:05,570 just have to hold the line until we get to that point. But 85 00:05:10,951 --> 00:05:14,373 I've got a lot of people, like thousands of people in my community, and 86 00:05:14,473 --> 00:05:18,136 hundreds and hundreds of them have moved their superannuation, their 87 00:05:18,176 --> 00:05:22,499 retirement fund, into essentially Bitcoin. You 88 00:05:22,519 --> 00:05:25,781 just mentioned the word before that some people were complacent. I don't feel 89 00:05:25,821 --> 00:05:28,983 like even myself or many members in my community were 90 00:05:29,023 --> 00:05:32,545 complacent. We went with what was considered the best device. 91 00:05:33,246 --> 00:05:36,508 So how can people now have trust in the next 92 00:05:36,568 --> 00:05:40,231 device or the next setup with their entire life savings? 93 00:05:41,231 --> 00:05:44,992 That's a very good question. I'll reframe what I said when I meant complacent. 94 00:05:45,032 --> 00:05:49,293 I wasn't referring to individuals. I was referring to perhaps companies 95 00:05:49,354 --> 00:05:53,175 and developers, people putting out products in the space. Coldcard was 96 00:05:53,235 --> 00:05:57,416 supposedly independently verified by many people. It was supposedly independently 97 00:05:57,576 --> 00:06:01,157 audited by many people. They even claimed that they passed AI 98 00:06:02,457 --> 00:06:05,838 on their own code and it still found nothing. So why 99 00:06:05,918 --> 00:06:09,639 this bug still existed despite all of these efforts for so long is 100 00:06:09,919 --> 00:06:13,540 honestly, it's a mystery. It's a mystery to me. But 101 00:06:13,620 --> 00:06:17,001 again, you know, like, I mean, this is an unfortunate event that 102 00:06:17,041 --> 00:06:20,262 took place that is going to force everybody to pay even 103 00:06:20,322 --> 00:06:23,623 more attention, right? It's not to make light of the losses, but 104 00:06:23,703 --> 00:06:26,924 in light of these losses, what this did is that it's going to 105 00:06:27,324 --> 00:06:31,425 probably kill trust in every hardware manufacturer's firmware. 106 00:06:32,125 --> 00:06:35,286 So for example, the word entropy now has become a thing. A lot 107 00:06:35,306 --> 00:06:38,808 of people are aware of what that word means, randomness, right? A 108 00:06:38,848 --> 00:06:42,089 lot of people are talking about- You better dive deep into that entropy for those who 109 00:06:42,129 --> 00:06:45,730 don't know what entropy actually means. Entropy in simple English 110 00:06:45,790 --> 00:06:49,032 basically means like randomness, right? Like the higher your 111 00:06:49,092 --> 00:06:52,133 entropy, the higher the randomness, the more impossible it 112 00:06:52,173 --> 00:06:55,254 is for anyone to guess your private keys, which is 113 00:06:55,294 --> 00:06:59,075 essentially those 12 or 24 words. The bug from 114 00:06:59,155 --> 00:07:02,697 cold card failed to give the level of entropy 115 00:07:02,717 --> 00:07:06,418 that it was supposed to. It was supposed to be around 128 bit on 116 00:07:06,738 --> 00:07:10,159 one specific device, the MK3, which none of our clients 117 00:07:10,319 --> 00:07:13,401 use was at close to zero. And so if 118 00:07:13,441 --> 00:07:16,722 that's all that you were using, you know, a 119 00:07:16,782 --> 00:07:20,543 human brain may not have figured out, you know, the 24 words, but 120 00:07:20,643 --> 00:07:24,005 an AI supercomputer you know, broke it within 121 00:07:24,345 --> 00:07:28,087 hours. That is the unfortunate reality. However, 122 00:07:28,327 --> 00:07:32,009 those that have been generating their independent, you know, entropy 123 00:07:32,069 --> 00:07:35,611 using, like, if they knew about dice rolls back then, even on that vulnerable 124 00:07:35,651 --> 00:07:39,534 device, the MK3, those folks were not touched. People 125 00:07:39,574 --> 00:07:42,795 that used advanced passphrases, something, you know, we default to 126 00:07:42,836 --> 00:07:46,478 with all our advanced single-sig clients. It's that 25th word, 127 00:07:46,738 --> 00:07:50,500 which adds independent extra entropy to 128 00:07:50,520 --> 00:07:53,782 the wallet itself. So if you had that, your 129 00:07:53,802 --> 00:07:56,943 wallet would have likely been okay for right now, 130 00:07:57,043 --> 00:08:00,185 unless your passphrase was a really simple English word like 131 00:08:00,385 --> 00:08:03,607 cats and dogs to use, which is not something we recommend at 132 00:08:03,787 --> 00:08:07,089 Let me touch on that, Tony, because I want to say that no one 133 00:08:07,129 --> 00:08:10,371 in my community who has used your service, who had 134 00:08:10,411 --> 00:08:13,772 the cold card, has lost any Bitcoin whatsoever. So what 135 00:08:13,952 --> 00:08:17,654 was it that you implemented from a security point 136 00:08:17,694 --> 00:08:21,037 of view, compared to where other people perhaps didn't 137 00:08:21,097 --> 00:08:24,819 implement something with the same device, but they lost Bitcoin and 138 00:08:25,640 --> 00:08:29,502 Well, that's where experience comes from. I mean, I come from the world of cybersecurity and 139 00:08:29,562 --> 00:08:33,124 my brain is always on, you know, OCD paranoid mode, 140 00:08:33,225 --> 00:08:36,667 right? So, I mean, our mission here, building these guidances and 141 00:08:36,707 --> 00:08:40,069 processes, we're never about finding the best product because I 142 00:08:40,109 --> 00:08:43,371 know for a fact that just simply doesn't exist. We're building an 143 00:08:43,491 --> 00:08:46,673 architecture where if any one of these moving parts were 144 00:08:46,713 --> 00:08:50,155 to fail, it doesn't risk blowing up your Bitcoin 145 00:08:50,215 --> 00:08:53,978 and you losing your wallet, right? So we knew about secure 146 00:08:53,998 --> 00:08:58,380 passphrases a long time ago and we made it like a mandatory thing 147 00:08:58,420 --> 00:09:02,102 to have when we're setting folks up, irrespective of 148 00:09:02,682 --> 00:09:06,024 And just to be clear, Tony, it's not essential, correct? So if you're setting 149 00:09:06,084 --> 00:09:09,486 up these devices, the 25th word, 150 00:09:12,968 --> 00:09:16,412 Correct yes basically it's a it's a it's a word that 151 00:09:16,593 --> 00:09:19,857 you create or you randomly generate that sits on 152 00:09:19,957 --> 00:09:23,581 top of your wallet so if you're using the wallet itself to 153 00:09:23,661 --> 00:09:27,225 create your twenty four words that's going to give you wallet a. When 154 00:09:27,245 --> 00:09:30,949 you generate a twenty fifth word, it creates wallet B, 155 00:09:31,150 --> 00:09:34,853 it's a completely different wallet, right? So if you don't have that word, then 156 00:09:34,893 --> 00:09:38,597 you don't have access to the wallet that's created using that passphrase. So 157 00:09:38,617 --> 00:09:42,200 you can't simply like upgrade wallet A into 158 00:09:42,220 --> 00:09:45,443 like a, just add a passphrase to it because when you 159 00:09:45,523 --> 00:09:48,646 add that 25th word, it's a brand new wallet. So that's why you 160 00:09:48,666 --> 00:09:51,889 really have to make sure that you don't lose these moving parts. And of course, you 161 00:09:51,909 --> 00:09:55,131 know, we go through the methodology to show you how to back 162 00:09:55,151 --> 00:09:58,574 it up, how to create redundancy, how to get used to using a passphrase 163 00:09:58,614 --> 00:10:02,178 and things of that sort. And in light of this event, this 164 00:10:02,458 --> 00:10:05,820 is what, you know, practically I think saved pretty much every 165 00:10:05,920 --> 00:10:09,401 one of our clients that was using a cold card but despite 166 00:10:09,441 --> 00:10:13,122 of all of this, it just leveled up our baseline. 167 00:10:13,623 --> 00:10:17,564 So not only were we completely paranoid to begin with, now 168 00:10:17,664 --> 00:10:21,565 we are taking that to a much higher standard where 169 00:10:21,605 --> 00:10:25,206 we are no longer trusting the firmware of any hardware product, be 170 00:10:25,666 --> 00:10:29,368 it cold card which we don't recommend anymore, But any hardware product, 171 00:10:29,448 --> 00:10:32,671 whether it's, you name it, seed signer, anything, I 172 00:10:33,272 --> 00:10:36,975 don't really care. The entropy will be generated independently, so 173 00:10:37,015 --> 00:10:40,358 that if something were to show up at some point with any 174 00:10:40,398 --> 00:10:43,921 piece of hardware, your private keys should no longer be affected. 175 00:10:44,741 --> 00:10:48,284 And we are implementing the same methodology to that passphrase for 176 00:10:48,344 --> 00:10:51,667 those who want to remain on an advanced single SIG. And 177 00:10:51,687 --> 00:10:55,650 of course, in light of this, everybody now is buzzing around multi-SIG. And 178 00:10:55,750 --> 00:10:59,013 so there's been a lot of misinformation about that as well, which we 179 00:10:59,073 --> 00:11:02,755 are trying to counter with real facts, right? Because 180 00:11:02,855 --> 00:11:06,117 most people out there when they hear multisig, they automatically default to 181 00:11:06,137 --> 00:11:09,620 thinking about collaborative multisig, which involves a 182 00:11:09,660 --> 00:11:13,362 third party custodian in the mix, which is absolutely 183 00:11:14,003 --> 00:11:17,465 not required and unnecessary and against the whole ethos of 184 00:11:17,505 --> 00:11:20,707 the Bitcoin white paper, where not a single character in 185 00:11:20,747 --> 00:11:23,949 there mentions a third party. So Now 186 00:11:23,969 --> 00:11:27,472 we're offering services to train people who are qualified to 187 00:11:27,572 --> 00:11:30,994 learn multisig, where they and they alone can either be 188 00:11:31,074 --> 00:11:34,316 the signer of all their devices, or they can come 189 00:11:34,416 --> 00:11:37,798 to us with some members of their own trusted inner 190 00:11:37,838 --> 00:11:41,681 circle, and we will individually train everyone to 191 00:11:41,721 --> 00:11:44,923 show them how to be responsible over the key that they 192 00:11:44,963 --> 00:11:48,085 hold. But essentially, the Bitcoin way has nothing to do 193 00:11:48,125 --> 00:11:51,868 with these keys. We don't hold anything. We don't back up anything. We don't sign anything. We 194 00:11:51,908 --> 00:11:55,210 put you, the user, Info control but 195 00:11:55,850 --> 00:11:59,152 the hardest part about our job is to find 196 00:11:59,192 --> 00:12:02,955 that balance right like it's really hard sometimes to find the balance between maintaining 197 00:12:03,095 --> 00:12:06,697 super security but also usability. Knowing 198 00:12:06,817 --> 00:12:10,600 that most users are not tech folks. They 199 00:12:10,640 --> 00:12:14,084 come to us from the regular world that doesn't involve tech 200 00:12:14,204 --> 00:12:17,348 or computers and now all of a sudden they have to 201 00:12:17,388 --> 00:12:20,771 learn this because their life savings, generational wealth is 202 00:12:20,912 --> 00:12:24,275 on the line. And I'm very proud to say that every 203 00:12:24,295 --> 00:12:27,479 single person that we've worked with that has come from 204 00:12:27,499 --> 00:12:31,163 a zero tech background is fully sovereign today. Like I'm extremely 205 00:12:31,243 --> 00:12:34,525 proud to really announce that because in light of this cold 206 00:12:34,565 --> 00:12:37,667 card event, I'd say maybe 40 to 50% of 207 00:12:37,727 --> 00:12:41,089 our clients were transacting on their own. They 208 00:12:41,129 --> 00:12:44,791 didn't even contact us for guidance because the training was 209 00:12:44,931 --> 00:12:48,353 so good, they learned it, they repeated the steps enough, 210 00:12:48,754 --> 00:12:51,976 boom, became autopilot, part of their everyday lives, they 211 00:12:52,016 --> 00:12:55,157 were good to go. And that's really the ultimate objective, the 212 00:12:55,298 --> 00:12:58,599 end game, that we have here at the Bitcoin way into building these 213 00:12:58,679 --> 00:13:01,861 sovereign individuals that can do whatever they want whenever they want 214 00:13:05,862 --> 00:13:09,864 Tony, some people are saying now that we can't really trust self-custody 215 00:13:10,825 --> 00:13:14,126 and we should just leave it on the exchange now. Is there a case for leaving 216 00:13:14,226 --> 00:13:17,527 on the exchange or do you still think that people should still 217 00:13:21,209 --> 00:13:24,471 Absolutely, self-custody is the final destination for 218 00:13:24,511 --> 00:13:28,433 Bitcoin, it's the only way to win. Don't 219 00:13:29,033 --> 00:13:32,555 replace a technical risk or vulnerability that you can monitor 220 00:13:32,615 --> 00:13:35,856 and control by a counterparty risk that you have 221 00:13:36,076 --> 00:13:39,739 no say over. The exchanges may be an interim solution. 222 00:13:40,240 --> 00:13:44,023 You can buy your Bitcoin there while you still can, you can leave it there temporarily 223 00:13:44,524 --> 00:13:47,687 and withdraw it before somehow they change the rules on 224 00:13:47,707 --> 00:13:51,170 you. Because that world is not in your control. You 225 00:13:51,190 --> 00:13:54,373 can fix or work around or mitigate a 226 00:13:54,453 --> 00:13:57,996 technical vulnerability like we did with the cold card. But 227 00:13:58,056 --> 00:14:01,780 if you leave your funds with a company, an institution, or an exchange, and 228 00:14:01,980 --> 00:14:05,343 one day they change the rules and they tell you, sorry, we're not allowed 229 00:14:05,423 --> 00:14:08,566 to give you your Bitcoin back because of X, Y, or Z, or 230 00:14:08,606 --> 00:14:12,569 they demand all sorts of KYC and 231 00:14:12,629 --> 00:14:16,052 compliance requirements that you cannot provide, well then you're 232 00:14:16,092 --> 00:14:20,114 done. Your money is locked into their system. It 233 00:14:20,515 --> 00:14:24,640 Tony, we've got a big issue right here in Australia. We've got a tyrannical leftist 234 00:14:25,521 --> 00:14:29,126 communist government right now, aka the 235 00:14:29,166 --> 00:14:32,610 Labour Party. But look, governments 236 00:14:32,650 --> 00:14:36,756 around the world are doing this, right? They're implementing all these draconian rules to 237 00:14:36,796 --> 00:14:40,279 seize things. I always think back to the Canadian 238 00:14:40,339 --> 00:14:43,741 truckers protest during COVID, where the government stepped in 239 00:14:44,361 --> 00:14:47,723 and locked up people's bank accounts. Now, that's my 240 00:14:47,883 --> 00:14:51,345 ultimate fear, is that if people actually do leave their Bitcoin 241 00:14:51,485 --> 00:14:55,208 on an exchange, and it's normal in Australia now, most of these exchanges have 242 00:14:55,668 --> 00:14:59,170 what's called an AFSL, an Australian Financial Services License. They've 243 00:14:59,190 --> 00:15:02,472 got to do all the KYC, and they've got to ask you where you're sending 244 00:15:02,512 --> 00:15:07,174 it to, where you're not sending it to, and what you had for breakfast. And 245 00:15:07,355 --> 00:15:10,476 ultimately, I think the government could just step in and say, hey, look, we're going to close up 246 00:15:10,516 --> 00:15:13,778 these accounts because we don't want to even have people with Bitcoin. We don't have people 247 00:15:13,798 --> 00:15:18,020 with sovereignty and they want you to stay on the debasing fiat 248 00:15:18,801 --> 00:15:22,002 Absolutely, man. I mean, if you understand what Bitcoin represents, it's 249 00:15:22,122 --> 00:15:25,244 only logical to conclude that very few governments are 250 00:15:25,284 --> 00:15:28,946 going to embrace Bitcoin in the way it was created. There's 251 00:15:28,986 --> 00:15:32,148 no sugarcoating what Bitcoin is. It's the separation of money and 252 00:15:32,188 --> 00:15:35,730 state. Simple as that. And so they don't want people 253 00:15:35,830 --> 00:15:39,092 to know that owning their own money is easy 254 00:15:39,132 --> 00:15:43,155 now. You know, I've always said it many times, as of 2009, the entire 255 00:15:43,295 --> 00:15:46,797 fiat world, all of it has become optional. But 256 00:15:46,837 --> 00:15:50,200 in order to get to that level of conviction, you have to understand, first 257 00:15:50,220 --> 00:15:53,282 of all, what money is, that it's not that, you know, worthless piece of 258 00:15:53,322 --> 00:15:56,624 paper that they print whenever they feel like it. And it's not about leaving it 259 00:15:56,684 --> 00:16:00,106 in a bank where the bank owns it. Most people to this day, despite the 260 00:16:00,146 --> 00:16:04,290 bad headlines, still think they own their money in a bank. Yeah, you 261 00:16:04,310 --> 00:16:07,673 understand until their day comes where you know, they're putting 262 00:16:07,713 --> 00:16:11,653 their ATM card or they're going to the teller and there's no more money I 263 00:16:12,634 --> 00:16:16,596 don't know if that's the prerequisite for people to finally believe what 264 00:16:16,676 --> 00:16:19,919 Bitcoin Maxis have been saying for the last 17 years. 265 00:16:20,299 --> 00:16:23,421 I pray that it's not. But in the same way that the 266 00:16:23,501 --> 00:16:27,203 cold card shook up a lot of people around self-custody, a 267 00:16:27,243 --> 00:16:30,426 lot of people say, I saw the bullet whiz right by me. And I'm 268 00:16:30,446 --> 00:16:33,728 like, yeah, I understand. And I'm genuinely sorry for 269 00:16:33,788 --> 00:16:37,451 so many people that have gone through that anxiety. Like 270 00:16:37,471 --> 00:16:40,957 nobody really signs up to almost give themselves a heart attack. But 271 00:16:40,997 --> 00:16:45,285 at the same time, if you don't experience something like this, you 272 00:16:45,305 --> 00:16:48,486 don't pay attention as well, right? Like you 273 00:16:48,526 --> 00:16:51,687 fall back, you think everything's cool, and this forces you 274 00:16:51,767 --> 00:16:55,508 to become alert again. So I absolutely 275 00:16:55,568 --> 00:16:58,629 do not think self-custody has taken a 276 00:16:58,669 --> 00:17:02,191 hit to the downside. I think it has taken a hit to 277 00:17:02,231 --> 00:17:05,832 like a massive upside. It's leveled up. All eyes, all 278 00:17:05,872 --> 00:17:09,313 the intelligent people are now, you know, gung-ho, leveraging again 279 00:17:09,353 --> 00:17:12,654 the AI tools to improve everything that's out there. And 280 00:17:12,694 --> 00:17:17,236 I genuinely believe it's going to become incredibly harder for 281 00:17:17,296 --> 00:17:21,938 attacks to break this. That's good news. 282 00:17:21,998 --> 00:17:25,839 Yeah, we're not firmware experts. 283 00:17:26,319 --> 00:17:30,241 This is the problem. We actually have to rely on others to 284 00:17:30,381 --> 00:17:33,742 check the firmware. And so you sort of touched on something before that 285 00:17:33,822 --> 00:17:37,123 people or companies are actually doing that. And is that something 286 00:17:37,163 --> 00:17:40,344 that other people can go and double check their work? Or how 287 00:17:40,364 --> 00:17:43,690 do you now know in the advice that you're giving 288 00:17:43,710 --> 00:17:47,001 to your clients, what is now a good device with good 289 00:17:48,892 --> 00:17:52,715 The thing is, if you're not a software developer or a coder yourself, you're 290 00:17:52,816 --> 00:17:57,099 going to have to take a trust-minimized approach 291 00:17:57,199 --> 00:18:01,142 where you're going to have to take the word of someone that you find has 292 00:18:01,323 --> 00:18:04,545 a credible experience to be able to tell you 293 00:18:04,745 --> 00:18:08,208 if they've done the work, right? And there's a lot in the space now that 294 00:18:08,549 --> 00:18:11,671 are doing just that. And I believe at some point, when people are 295 00:18:11,711 --> 00:18:15,374 selling Bitcoin-related products, you're going to see a new tag on 296 00:18:15,394 --> 00:18:19,736 their products, which is like AI audited or AI reviewed, investigated, things 297 00:18:19,776 --> 00:18:22,977 of that sort. Because human intelligence, as 298 00:18:23,057 --> 00:18:26,458 good as it may be for some people, has a limit. It's no 299 00:18:26,498 --> 00:18:29,599 match for a supercomputer. And so if 300 00:18:29,659 --> 00:18:33,641 you're someone who's putting out a product of that nature into the 301 00:18:33,661 --> 00:18:37,264 market, you have got to do this it's no longer you know maybe 302 00:18:37,304 --> 00:18:40,667 we do this it has to be part of your business plan to 303 00:18:40,747 --> 00:18:43,950 ensure that you know no one runs into a problem that you could have 304 00:18:43,990 --> 00:18:47,453 avoided because at the end of the day if it's your product it's your responsibility right 305 00:18:48,033 --> 00:18:52,377 and so. That's why i'm saying like events like this. at 306 00:18:52,477 --> 00:18:56,038 some level are required to push people to 307 00:18:56,078 --> 00:18:59,820 go the distance with their due diligence, especially 308 00:18:59,860 --> 00:19:03,781 around their products. So as far as we're concerned, our criteria for 309 00:19:03,881 --> 00:19:07,002 good hardware walls hasn't changed. It's still open source or 310 00:19:07,042 --> 00:19:10,584 verifiable source, Bitcoin only fully air-gapped devices. The 311 00:19:10,644 --> 00:19:14,025 difference is, like I said earlier, we don't care about the brand. So 312 00:19:14,085 --> 00:19:17,646 whether it's a seat signer, a jade, a passport, whatever it is, the 313 00:19:17,726 --> 00:19:20,989 entropy will be generated independent of that 314 00:19:21,089 --> 00:19:24,792 device. So the device will only serve the signing part 315 00:19:25,133 --> 00:19:28,356 of the wallet, because the hardware wallet has two parts, the 316 00:19:28,416 --> 00:19:31,979 seed phrase generation and the signing. We're no longer using 317 00:19:32,039 --> 00:19:35,462 the seed phrase generation, we're only using it to sign. And I suspect 318 00:19:35,542 --> 00:19:39,325 at some point, future hardware wallets will no longer generate 319 00:19:39,746 --> 00:19:43,088 anything, because the default will be no longer to trust that people will 320 00:19:43,108 --> 00:19:46,590 be, going to do dice rolls or whatever the case may be in 321 00:19:46,710 --> 00:19:50,231 order to make sure that that entropy remains at the highest possible level 322 00:19:50,592 --> 00:19:54,093 with no software or code that may impact 323 00:19:54,753 --> 00:19:57,894 Yeah tiny just explain to me because we're talking like high tech stuff and 324 00:19:57,914 --> 00:20:01,536 then you dropped in this is dice roll which seems very primitive so. 325 00:20:02,516 --> 00:20:05,917 People listening what exactly mean like i'd like literally getting dyson rolling 326 00:20:07,745 --> 00:20:10,906 Yeah, so it's ironic you mentioned that because, you know, 327 00:20:10,946 --> 00:20:14,247 Bitcoin, the world's most advanced technology, you know, seems to need 328 00:20:14,287 --> 00:20:17,448 the most Fred Flintstone analog ways to protect it. 329 00:20:18,048 --> 00:20:21,329 And so basically a dice roll is exactly what it sounds like. You have 330 00:20:21,349 --> 00:20:24,590 a little box, you throw in five or ten dice in it, you shake 331 00:20:24,610 --> 00:20:27,911 it for three seconds, and you place it on a table, and you 332 00:20:28,011 --> 00:20:31,212 read, like you list down the numbers from left to right. And 333 00:20:31,252 --> 00:20:34,635 you do this 10 times in order to get a hundred rolls. And 334 00:20:34,675 --> 00:20:37,998 then once you get these numbers written down a hundred times, you enter 335 00:20:38,038 --> 00:20:41,141 them into the hardware device that supports dice rolls, and 336 00:20:41,261 --> 00:20:44,424 it will generate your private keys based on the 337 00:20:44,484 --> 00:20:48,267 randomness of these rolls. It sounds like fun, for 338 00:20:48,368 --> 00:20:52,211 example. Is that right? The full 24 words, is that what we're talking about? Yes. 339 00:20:52,812 --> 00:20:56,134 That's the job that the firmware should be doing. 340 00:20:56,815 --> 00:21:00,598 Like that's the job of the device should have done automatically, but 341 00:21:00,638 --> 00:21:04,282 it didn't. The cold card firmware failed at 342 00:21:04,342 --> 00:21:07,825 doing that. There was a bug in there that did not generate 343 00:21:07,985 --> 00:21:11,108 enough randomness. So other devices right now are 344 00:21:11,148 --> 00:21:14,731 not impacted by this. So if you use something else, chances are 345 00:21:14,811 --> 00:21:18,194 this whole headline would have, you know, just been something you ignored. 346 00:21:18,734 --> 00:21:22,857 But for cold card users, specifically on the MK3, that 347 00:21:22,897 --> 00:21:26,160 was not something they could ignore because their funds were actually drained, right? 348 00:21:26,740 --> 00:21:29,923 So in light of this, it's going to cause, in 349 00:21:29,983 --> 00:21:33,305 my view, a cascading domino effect where it doesn't matter 350 00:21:33,746 --> 00:21:36,928 if your product has not been breached or hacked or 351 00:21:37,288 --> 00:21:40,811 a bug was discovered. Logical people, especially those 352 00:21:40,871 --> 00:21:44,273 holding a high level of savings, will not trust 353 00:21:44,314 --> 00:21:47,535 it. So at our team at 354 00:21:47,555 --> 00:21:50,676 the Bitcoin, we are defaulting everything that we're doing now to 355 00:21:50,797 --> 00:21:54,138 independent entropy. So whether it's advanced single SIG, whether 356 00:21:54,158 --> 00:21:58,100 it's multi SIG, all the entropy will be created outside 357 00:21:58,600 --> 00:22:01,921 whatever hardware the user is using to 358 00:22:02,021 --> 00:22:05,803 sign these transactions. So that this particular issue becomes 359 00:22:07,924 --> 00:22:11,067 So just a couple of things, Tony. So you're still recommending then, even 360 00:22:11,087 --> 00:22:14,330 though you've done the dice roll, you've got the 24 words, you would 361 00:22:18,234 --> 00:22:21,777 Yes, absolutely. The passphrase is non-negotiable, you know, like whether 362 00:22:21,797 --> 00:22:25,260 it was before or now, that's non-negotiable. What's 363 00:22:25,300 --> 00:22:28,623 going to be different about the passphrase now is that it's 364 00:22:28,643 --> 00:22:32,926 not going to be human generated. it's going to be generated 365 00:22:33,006 --> 00:22:36,928 randomly by, again, something with true randomness associated 366 00:22:36,968 --> 00:22:40,169 to it. So you will not be able to memorize it. You will have 367 00:22:40,209 --> 00:22:43,931 to save it properly, ensure you have proper redundancy, and 368 00:22:44,091 --> 00:22:48,573 perhaps it's gonna take you like an extra minute or so to enter it because it's 369 00:22:49,673 --> 00:22:52,935 But just to be clear though, from what it sounds like, Tony, is that 370 00:22:53,235 --> 00:22:56,896 this 25th word that can be skit was 371 00:22:56,936 --> 00:23:00,074 the clear, I guess, catalyst for 372 00:23:00,134 --> 00:23:03,419 those people who lost Bitcoin. They just chose not to do this 373 00:23:06,149 --> 00:23:09,492 Either they chose not to use it or they simply didn't know that 374 00:23:09,552 --> 00:23:14,276 that was an option available to them. Because they didn't have the right technical cybersecurity 375 00:23:14,316 --> 00:23:17,539 advice to protect their wealth. Correct. And in their 376 00:23:17,599 --> 00:23:20,901 defense, they didn't have to use it, right? I 377 00:23:20,921 --> 00:23:24,484 mean, if that cold card firmware was not buggy, it 378 00:23:24,524 --> 00:23:27,627 would have generated enough entropy that the chances of 379 00:23:27,707 --> 00:23:31,270 a supercomputer figuring it out, at least like now, would 380 00:23:31,290 --> 00:23:34,533 have been very, very unlikely. That's what's 381 00:23:34,553 --> 00:23:38,238 so upsetting at this. It was a bug in that firmware that 382 00:23:38,278 --> 00:23:42,104 was unnoticed for five years or so, and 383 00:23:42,544 --> 00:23:45,949 people woke up to the nightmare results of 384 00:23:46,795 --> 00:23:50,137 And I just want to touch on this because I've been recommending your 385 00:23:50,177 --> 00:23:53,479 service for years and years now since I was someone who has 386 00:23:53,519 --> 00:23:57,582 been using your service. And I say to people, look, I understand there's 387 00:23:57,682 --> 00:24:01,905 an investment that needs to be made into your education and learning. But 388 00:24:02,245 --> 00:24:05,948 if you're someone who's now lost your Bitcoin because you didn't know about this 25th 389 00:24:06,008 --> 00:24:09,170 word and the extra level protocols to implement, aren't you going to think, 390 00:24:09,730 --> 00:24:13,172 I should have, I should have spent that little bit of extra money to get the right training, 391 00:24:13,212 --> 00:24:16,655 to get the right security in place so I didn't lose my entire wealth. 392 00:24:20,357 --> 00:24:23,499 I completely agree, man. I mean, if there's some people that are 393 00:24:23,599 --> 00:24:27,001 good at doing things themselves, you know, there's plenty of free resources online that 394 00:24:27,061 --> 00:24:30,644 you can videos you can watch, you know, articles you can read. If 395 00:24:30,704 --> 00:24:34,106 that's you and you're comfortable doing this and by all means do 396 00:24:34,186 --> 00:24:37,548 it otherwise. Seek the advice of someone 397 00:24:37,568 --> 00:24:41,191 who does this on a daily basis. I mean, there's a lot of details 398 00:24:41,371 --> 00:24:44,574 involved in self-custody. It's not about just, you know, following the 399 00:24:44,614 --> 00:24:47,777 manual and setting up, you know, a hardware A, B, or 400 00:24:47,817 --> 00:24:50,999 C. Our process is insanely thorough. Like 401 00:24:51,039 --> 00:24:54,442 there's, I mean, you know, there's a lot of moving parts involved and 402 00:24:54,482 --> 00:24:58,365 we train you on every single one of them so that in 403 00:24:58,405 --> 00:25:01,785 the event something fails, Nothing 404 00:25:01,826 --> 00:25:05,150 blows up. And we follow up with all our users. We make 405 00:25:05,190 --> 00:25:08,434 sure you stay up to date. We make sure you're practicing. We make sure, 406 00:25:08,654 --> 00:25:11,898 like we babysit all of our users that are in touch 407 00:25:11,918 --> 00:25:15,323 with us 24-7 as long as they want via these 408 00:25:15,423 --> 00:25:18,827 private signal groups that we create specifically for that purpose. 409 00:25:19,488 --> 00:25:22,752 Bitcoin is ongoing tech. It's not a set it and forget it. You can't 410 00:25:22,792 --> 00:25:26,616 have like a bulletproof setup today and expect it to remain bulletproof 411 00:25:26,636 --> 00:25:29,819 for the next 15 years. It's not going to work. You will become your 412 00:25:29,919 --> 00:25:33,523 own risk if that's the approach that you take. And so we don't allow 413 00:25:33,583 --> 00:25:37,588 it, you know, as part of our ethos at the company, we don't allow our clients to 414 00:25:39,542 --> 00:25:42,864 Right. Tony, I just want to say one thing too, in light 415 00:25:42,884 --> 00:25:46,066 of all that's happened through this cold card hack, I want to just give a big shout out 416 00:25:46,106 --> 00:25:49,688 and thank you to everyone at the Bitcoin Way because you guys have been working 24-7 417 00:25:49,748 --> 00:25:53,230 for so many days now 418 00:25:53,691 --> 00:25:56,932 just to make sure that all the existing clients are well protected, that they've 419 00:25:56,952 --> 00:26:00,415 got any queries, you're answering them if they need to move any funds, you're 420 00:26:00,455 --> 00:26:04,217 helping them do it at no cost and just been delivering updates 421 00:26:04,737 --> 00:26:08,199 uh, all the time with what's, what's going on and now even helping people 422 00:26:08,299 --> 00:26:11,560 rebuild, um, their setups, which is incredible. So just 423 00:26:11,600 --> 00:26:15,302 thank you so much for, for everyone at the team for doing that. I 424 00:26:15,462 --> 00:26:18,684 do want to jump into something else because, um, I'm going to, I 425 00:26:18,724 --> 00:26:22,485 actually put to my community some, uh, if they wanted to ask you some questions, okay, 426 00:26:22,525 --> 00:26:26,448 about this, I'm just going to put some questions to you, Tony. And, and Before 427 00:26:26,468 --> 00:26:29,792 I do that, also, I know that you're also doing a 428 00:26:29,852 --> 00:26:33,536 webinar livestream called The Future of Self-Custody on 429 00:26:33,616 --> 00:26:36,981 September the 30th. So I'm going to leave a link in the show notes 430 00:26:37,041 --> 00:26:40,565 of how people can register for that, especially if they want to get more 431 00:26:40,625 --> 00:26:43,784 details from you. So Tony, here we go. This is a 432 00:26:43,804 --> 00:26:47,526 question from the audience. Are you ready? So what should people who generated their 433 00:26:47,666 --> 00:26:51,209 seed on a cold card between 2021 and 434 00:26:51,249 --> 00:26:54,971 mid-2026 do right now if they haven't already 435 00:26:55,932 --> 00:26:59,114 First of all, you're going to have to generate a brand new seed phrase. Updating the 436 00:26:59,154 --> 00:27:02,416 firmware on the cold card if you decide to continue using it is not going to fix 437 00:27:02,436 --> 00:27:05,959 the issue. If you're really panicked 438 00:27:06,019 --> 00:27:09,801 about this, move your funds to either another 439 00:27:09,861 --> 00:27:13,584 hardware wallet that you may have if you have one, or generate yourself a 440 00:27:13,644 --> 00:27:17,286 secure hot wallet on a clean computer temporarily that 441 00:27:17,366 --> 00:27:20,788 you can move the funds to while you rebuild whatever setup that 442 00:27:20,848 --> 00:27:23,930 you currently have. If none of these options are available to you, 443 00:27:23,950 --> 00:27:27,233 and I cringe when I say this, but it may be better to send 444 00:27:27,293 --> 00:27:30,715 it to the exchange temporarily until you 445 00:27:31,456 --> 00:27:34,899 you rebuild your setup and then you withdraw it again into 446 00:27:38,564 --> 00:27:42,588 So just to be clear, if you've got a cold card queue for example, you 447 00:27:42,688 --> 00:27:46,473 cannot update the firmware, is that right? There's no new firmware update 448 00:27:47,754 --> 00:27:51,098 No you can, coinkite released firmware updates 449 00:27:51,158 --> 00:27:54,502 for all of their products, the mk3, 4, 5 and 450 00:27:54,522 --> 00:27:57,745 the q. Now just to be clear, there are no 451 00:27:57,805 --> 00:28:01,089 reports of any loss of funds on any 452 00:28:01,169 --> 00:28:04,800 hardware other than the mk3. Right. 453 00:28:04,820 --> 00:28:08,182 Interesting. The firmware technically affects all 454 00:28:08,242 --> 00:28:11,665 the line, but the level of entropy on the MK4, 455 00:28:12,405 --> 00:28:15,527 5, and Q seems to be higher than the one 456 00:28:15,607 --> 00:28:18,729 on the MK3. I think it's around 72 bits. It's supposed to be 457 00:28:18,769 --> 00:28:22,232 around 128. It's at 72. And so that 458 00:28:22,972 --> 00:28:26,354 added a bit more substance to the entropy of 459 00:28:26,434 --> 00:28:29,937 the seed words created on the 4, 5, and Q. That being said, 460 00:28:30,797 --> 00:28:34,139 As a precautionary measure, just because we don't know what we don't know, 461 00:28:34,739 --> 00:28:38,481 we moved all our cold card clients to 462 00:28:38,641 --> 00:28:42,103 either another hardware device that they had temporarily or 463 00:28:42,163 --> 00:28:45,665 some other secure setup temporarily. Some people decided 464 00:28:45,685 --> 00:28:48,886 they wanted to move to the exchange, you know, again, temporarily until we 465 00:28:48,946 --> 00:28:52,468 rebuild everything. And we offered free rebuilds to absolutely 466 00:28:52,588 --> 00:28:56,210 every cold card user. Um, out there and, uh, 467 00:28:56,290 --> 00:28:59,630 we grew the team, you know, we added like seven people to the team in 468 00:28:59,790 --> 00:29:03,111 order to keep up, you know, with doing this as, as efficiently and quickly 469 00:29:03,171 --> 00:29:06,432 as possible. But. If you don't have any 470 00:29:06,472 --> 00:29:09,653 guidance, if you're all, if you're all by yourself and you're using a cold 471 00:29:09,693 --> 00:29:12,994 card and you're worried that you might be affected, get your funds off 472 00:29:13,034 --> 00:29:16,315 of it again. And any hardware wallet that you have right now, 473 00:29:16,795 --> 00:29:20,156 that is not a cold card shouldn't have this bug. Otherwise, if 474 00:29:20,176 --> 00:29:23,759 you, if. You can move it to a secure hot wallet that you can, you 475 00:29:23,799 --> 00:29:26,942 pick, just make sure it's on a secure device, no viruses, no 476 00:29:26,982 --> 00:29:30,405 malware. And if none of these options are available to you, it may be better 477 00:29:30,786 --> 00:29:34,790 to move it to, you know, your exchange of choice temporarily until 478 00:29:37,412 --> 00:29:41,173 Yeah, and Tony, just on that note too, I think people really have to practice 479 00:29:41,713 --> 00:29:45,174 moving their Bitcoin. I move Bitcoin around, so when 480 00:29:45,194 --> 00:29:48,815 an issue like this arises and you're in a state of panic, oh, 481 00:29:49,015 --> 00:29:52,336 I need to move my Bitcoin immediately, you're not freaking out because 482 00:29:52,376 --> 00:29:55,616 you've never moved the Bitcoin before, right? You can just jump in, do it 483 00:29:56,477 --> 00:29:59,557 in a calm way, maybe do a test, then move the 484 00:29:59,617 --> 00:30:03,298 rest and everything will be fine. So practice is key. Because 485 00:30:03,318 --> 00:30:06,400 then it's just like what you keep saying, it just becomes second nature. What do 486 00:30:08,240 --> 00:30:11,422 Yeah, it becomes as instinctive as making a cup of coffee. You don't think 487 00:30:11,462 --> 00:30:15,023 twice about it. And the amount of money really doesn't matter. Whether 488 00:30:15,043 --> 00:30:18,465 you're transacting with a dollar equivalent of Bitcoin or a billion, 489 00:30:21,646 --> 00:30:25,228 Next question for you, Tony. What are the most important steps everyday 490 00:30:25,288 --> 00:30:28,530 Bitcoiners should take today to reduce the chance of 491 00:30:28,630 --> 00:30:31,811 being hit by a similar hardware wallet flaw in the future? I 492 00:30:34,213 --> 00:30:37,554 When it comes to the private key, which is essentially the most important part 493 00:30:37,694 --> 00:30:40,976 of your wallet security, generating it independent of 494 00:30:41,116 --> 00:30:44,278 any code or firmware is going to become the default in my view. 495 00:30:44,858 --> 00:30:48,139 That's what we're defaulting to anyhow at the Bitcoin way. There's 496 00:30:48,199 --> 00:30:51,520 no more, like I don't care what hardware you're using, we're not using 497 00:30:51,580 --> 00:30:54,781 it to generate your keys. So you're going to be rolling dice, it's going to be fun, 498 00:30:54,801 --> 00:30:58,002 you're going to get used to that way 499 00:30:58,042 --> 00:31:01,483 of doing things, and we're going to apply that to essentially every 500 00:31:01,543 --> 00:31:05,164 moving part that is attached to your wallet. So 501 00:31:05,324 --> 00:31:10,188 pay attention to the news. I mean, if you're in Bitcoin for the right reasons, follow 502 00:31:10,228 --> 00:31:13,371 people that you trust, keep up to date with the information. This 503 00:31:13,431 --> 00:31:16,753 is going to be forever evolving news 504 00:31:16,813 --> 00:31:20,076 and technology. It's a very exciting time in 505 00:31:20,136 --> 00:31:23,398 history, but we cannot be complacent about this. 506 00:31:23,939 --> 00:31:27,822 I read and watch things on a daily basis nonstop. Even 507 00:31:27,862 --> 00:31:31,144 for someone that has my background, I am learning every 508 00:31:31,184 --> 00:31:35,091 single day. And I'm not shy to publicly 509 00:31:35,131 --> 00:31:38,636 say this because AI has never 510 00:31:38,716 --> 00:31:42,017 existed in my life growing up. Like there's a lot of things this thing can 511 00:31:42,058 --> 00:31:45,499 do that I'm not aware of. I'm learning 512 00:31:45,599 --> 00:31:48,841 about this and I'm using that information to 513 00:31:48,901 --> 00:31:52,103 strengthen my position as a sovereign individual and 514 00:31:52,143 --> 00:31:55,525 to pass on that education to folks that I know also 515 00:31:55,585 --> 00:32:00,347 don't know anything about it, right? And so together, collectively, education 516 00:32:00,528 --> 00:32:03,829 is what's going to keep everything, you know, unified. And 517 00:32:03,929 --> 00:32:07,251 so again, personal responsibility, discipline, are 518 00:32:07,332 --> 00:32:10,777 not optional. It's just, that's it. It's part of your DNA now, if 519 00:32:14,844 --> 00:32:18,269 Yeah, people probably, I'm sure they'll be shocked to know, Tony, that you 520 00:32:18,309 --> 00:32:23,480 and I were actually around before a mobile phone existed. This 521 00:32:23,560 --> 00:32:27,823 is amazing technology for us old people. Tony, 522 00:32:27,863 --> 00:32:31,766 this is a really interesting question. Should people who currently hold 523 00:32:31,826 --> 00:32:35,328 significant amounts on a single SIG wallet 524 00:32:35,348 --> 00:32:39,051 of some description or device consider moving to a multi-SIG? And 525 00:32:39,231 --> 00:32:42,674 if so, how can it be done properly to ensure 526 00:32:42,694 --> 00:32:46,276 that they're protected? And perhaps even touch on why even have a multi-SIG 527 00:32:48,223 --> 00:32:52,024 Look, there's two ways to do this. We have high net worth individuals that 528 00:32:52,084 --> 00:32:56,526 are very comfortable on advanced single stake 529 00:32:56,606 --> 00:32:59,867 because it reduces the complexity. We can create a 530 00:32:59,887 --> 00:33:03,108 setup that's ultra complicated, but it's of no use if there's 531 00:33:03,188 --> 00:33:06,709 a risk of the user screwing it up, right? And you essentially lock 532 00:33:06,769 --> 00:33:09,950 yourself out of your funds. And that's even worse than 533 00:33:09,990 --> 00:33:13,652 running into a bug because you know it's your fault. Multisig is 534 00:33:13,712 --> 00:33:17,255 definitely a very good option. Multivendor multisig reduces the 535 00:33:17,315 --> 00:33:20,618 risk of any one device. If it has a flaw, there's 536 00:33:21,138 --> 00:33:25,162 two or three other ones involved, it mitigates the risk. But multisig 537 00:33:25,182 --> 00:33:28,905 done properly is going to require a commitment from 538 00:33:28,945 --> 00:33:32,248 the user. There's more moving parts, there's more stuff to 539 00:33:32,288 --> 00:33:35,631 learn, it's a little bit more involved. You have a lot more parts 540 00:33:35,651 --> 00:33:38,933 that you need to back up and create redundancy for. there's 541 00:33:38,974 --> 00:33:42,296 a lot more discipline required from the user. We 542 00:33:42,356 --> 00:33:46,100 have massive interest in it right now in light of this event, but 543 00:33:46,180 --> 00:33:50,263 people are coming to Multisig with the right mindset. They 544 00:33:50,343 --> 00:33:53,766 are committed to learning this properly, which makes the process a 545 00:33:53,826 --> 00:33:57,189 lot easier. It's not rocket science, but just understand that 546 00:33:57,589 --> 00:34:01,213 initially it's going to seem perhaps unfamiliar, very unfamiliar, 547 00:34:01,573 --> 00:34:05,957 if you've never ventured into this world before. Unfamiliar 548 00:34:06,017 --> 00:34:09,400 becomes second nature the more you repeat 549 00:34:09,420 --> 00:34:12,683 it. And this is where, like, this is the gap that we 550 00:34:12,723 --> 00:34:15,886 fill. We bring in the education, we help you, like, we help you 551 00:34:15,926 --> 00:34:19,369 get this right the first time, and then we make sure you keep repeating it 552 00:34:19,609 --> 00:34:23,252 so that it does become something part of your everyday existence. So 553 00:34:23,272 --> 00:34:26,897 whether you want to keep using advanced single SIG for the reduced 554 00:34:26,937 --> 00:34:30,501 complexity, or you want to level up to multi-vendor multi-SIG, we 555 00:34:30,521 --> 00:34:33,825 will guide you, educate you, support you on either way. But we 556 00:34:33,945 --> 00:34:37,429 will also make you aware of the pros and cons, the trade-offs, and 557 00:34:37,509 --> 00:34:40,573 you at the end of the day, will pick whatever you're comfortable with. And 558 00:34:40,613 --> 00:34:43,916 it's not to say like if you start with an advanced single state, you can't at some point 559 00:34:43,936 --> 00:34:47,459 say, okay, well, you know what? I'm ready for multi-state. We can definitely move 560 00:34:47,539 --> 00:34:50,823 up at any point in time. It's not a race. Like you said earlier, you 561 00:34:50,843 --> 00:34:54,146 don't want to panic and make any rash decisions, especially when 562 00:34:56,752 --> 00:34:59,994 Yeah, one of the things I now suggest is even with your different 563 00:35:00,034 --> 00:35:03,216 buckets. So for example, if you've got a retirement bucket, you 564 00:35:03,256 --> 00:35:06,558 might have a multi-sig. It's something that you sort of set and forget for 565 00:35:06,578 --> 00:35:10,021 a bit more, right? It's more moving parts, so it's more time, 566 00:35:10,061 --> 00:35:13,383 but you can sort of just worry about that later. You might have another bucket, which is either a 567 00:35:13,463 --> 00:35:16,685 company or in your personal name, and on those two, you 568 00:35:16,725 --> 00:35:20,027 might have a single sig. So not everything has to be bundled into the same 569 00:35:20,127 --> 00:35:23,289 type of security setup, and that may be something that people might want 570 00:35:23,309 --> 00:35:26,711 to consider as well. Absolutely correct. Yeah, 571 00:35:26,751 --> 00:35:30,134 Tony, thank you so much, mate. I think we've touched on so many topics today. 572 00:35:30,154 --> 00:35:33,716 I think what's probably the most important thing, if people have more questions, 573 00:35:33,756 --> 00:35:37,279 they can reach out to you guys at The Bitcoin Way, and I really would encourage people 574 00:35:37,299 --> 00:35:40,841 to jump onto the Future of Self-Custody webinar 575 00:35:40,861 --> 00:35:44,424 that's coming up on September the 30th. They can register for that by 576 00:35:47,580 --> 00:35:51,182 Absolutely. I mean, guys, this is a new space. Bitcoin, the 577 00:35:51,222 --> 00:35:54,763 world has never seen. And the fact that it's so valuable 578 00:35:55,343 --> 00:35:58,685 is why we have all these horror stories, all of these attacks. If 579 00:35:58,745 --> 00:36:01,886 it was really worthless, no 580 00:36:01,966 --> 00:36:05,868 one would be spending time and energy in trying to keep 8.3 billion 581 00:36:05,908 --> 00:36:09,210 people away from it. The 582 00:36:09,250 --> 00:36:12,651 narratives that I see going on here, they can't kill the 583 00:36:12,691 --> 00:36:15,993 tech. They can't kill Bitcoin. But what they can do 584 00:36:16,113 --> 00:36:19,317 is scare the living daylights of folks from even considering it. 585 00:36:20,058 --> 00:36:23,963 And you don't want to let yourself get shaken out because the alternative to 586 00:36:24,003 --> 00:36:27,367 Bitcoin in self-custody is a nightmare. You 587 00:36:27,387 --> 00:36:31,271 know, that digital panopticon, central bank, digital currencies, restrictions, 588 00:36:31,412 --> 00:36:34,495 asking for permissions. If you thought it was bad now, I 589 00:36:34,535 --> 00:36:37,798 can assure you it's a million times worse if you find 590 00:36:37,818 --> 00:36:41,181 yourself stuck in a system where you and you alone are 591 00:36:41,221 --> 00:36:44,544 not in control of your funds, especially funds that 592 00:36:44,645 --> 00:36:48,168 cannot be printed to oblivion, that cannot be turned 593 00:36:48,268 --> 00:36:51,511 off because somebody's in a bad mood or doesn't like what you said or how you 594 00:36:51,531 --> 00:36:56,435 look or whatever lousy excuse they come up with. Again, 595 00:36:57,356 --> 00:37:00,778 Bitcoin is the future, just understand that it's money. 596 00:37:01,378 --> 00:37:04,900 You earn, you spend, you save in it. There's nothing 597 00:37:04,980 --> 00:37:08,282 complicated about this. Ignore the counterparty risk. You don't trade 598 00:37:08,342 --> 00:37:11,644 it, you don't leverage it, you don't borrow against it. Unless you 599 00:37:11,684 --> 00:37:14,706 really know what you're doing and you're able to navigate this as a 600 00:37:14,766 --> 00:37:18,348 sophisticated investor, which most people do not fall 601 00:37:18,368 --> 00:37:21,609 into that category, stay away from it. Find ways to earn 602 00:37:21,649 --> 00:37:24,870 it. That is the key. Once the on-ramps disappear, which I believe at 603 00:37:24,910 --> 00:37:28,312 some point they will, because they're going to have to stop the bleeding somehow, 604 00:37:28,392 --> 00:37:32,153 right? Apparently this is another episode. We could go deep into the 605 00:37:32,173 --> 00:37:35,394 politics. Exactly. So understand that all of this is 606 00:37:35,474 --> 00:37:38,915 coming because of how valuable this thing 607 00:37:39,055 --> 00:37:42,296 is and what real threat it poses to a system that's 608 00:37:42,316 --> 00:37:45,578 been around for forever. Separation of money and 609 00:37:45,598 --> 00:37:49,361 states never been possible before 2009. So you 610 00:37:49,401 --> 00:37:52,824 either get on board or you learn the lesson, 611 00:37:56,787 --> 00:37:59,869 Yeah, fantastic. Always wise words from Tony from the 612 00:37:59,909 --> 00:38:03,132 Bitcoin Way. It's so great to have you on. And a big thank you once 613 00:38:03,192 --> 00:38:06,414 again for helping Bitcoiners protect their wealth into 614 00:38:06,434 --> 00:38:09,557 the future. All right, Tony, thank you so much. I'll see you next time. Thank you, 615 00:38:09,597 --> 00:38:13,029 Matthew. If you're ready to dive deeper into crypto and Bitcoin and 616 00:38:13,109 --> 00:38:16,851 build real wealth, join my free crypto collective 617 00:38:16,931 --> 00:38:20,272 community. It's where I share exclusive insights and strategies and 618 00:38:20,373 --> 00:38:24,034 live discussions to help you succeed, whether you're a beginner or 619 00:38:24,154 --> 00:38:27,556 scaling your portfolio. Click on the link in the description and join