June 28, 2022
Bitcoin.Review with NVK - A Review of Updates to Popular Bitcoin Projects
NVK is starting a new show focused on covering updates to popular bitcoin projects. I joined him for the first episode, figured some of you may find it helpful. https://bitcoin.review
support the show: https://citadeldispatch.com/contribute
twitch: https://twitch.tv/citadeldispatch
bitcointv: https://bitcointv.com/video-channels/citadeldispatch/videos
podcast: https://www.podpage.com/citadeldispatch
telegram: https://t.me/citadeldispatch
stream sats to the show: https://www.fountain.fm/
join the chat: https://matrix.to/#/#citadel:bitcoin.kyoto
00:08 - Introduction and podcast name
00:32 - Reason for starting the podcast
03:18 - Guests and format of the podcast
45:08 - Discussion about giving a demo and someone wanting the product
45:33 - Bug fixes and improvements in software
47:13 - Discussion about monetizing open-source projects
01:24:41 - Bitcoin crash and lack of interest
01:25:20 - Update on bitcoinbinary.org
01:26:27 - Automated builds and improved security
01:27:22 - Update on BitcoinTreasuries.net
01:27:36 - Introduction of Sats chip
01:29:23 - Physical Bitcoin art and NFTs
01:31:16 - Bitcoin Park in Nashville
01:31:23 - Fully Noted NFC beta on cold card
01:32:33 - Block Clock Micro reservation
01:35:23 - BTC Sessions tutorial and Coin Kite stable coin
WEBVTT
NOTE
Transcription provided by Podhome.fm
Created: 3/17/2024 4:24:58 PM
Duration: 6000.666
Channels: 1
1
00:00:02.000 --> 00:00:02.500
Hello.
2
00:00:02.879 --> 00:00:03.379
Yeah.
3
00:00:04.000 --> 00:00:04.500
So
4
00:00:07.359 --> 00:00:07.859
Hello.
5
00:00:08.565 --> 00:00:09.065
Hello.
6
00:00:10.165 --> 00:00:14.424
It's like a big empty canvas out there, isn't it, Matt? So okay.
7
00:00:14.725 --> 00:00:17.550
So hello, and welcome to the Bitcoin review.
8
00:00:18.170 --> 00:00:28.085
Bitcoin dot review. Fuck. Let's start again. Don't start again. We're good. We're good. Fine. Alright. Hello and welcome to the Bitcoin Dot Review because that's the domain. Get it?
9
00:00:28.465 --> 00:00:28.965
So
10
00:00:29.345 --> 00:00:31.525
I started scratching my own itch with this.
11
00:00:32.490 --> 00:00:37.230
It's a best efforts sort of place to talk about Bitcoin projects and software updates.
12
00:00:39.050 --> 00:00:40.510
And we did so we stopped
13
00:00:41.235 --> 00:00:41.735
covering
14
00:00:42.195 --> 00:00:53.800
software updates and rabbit hole recap. Yeah. Pretty much. I mean, it's kinda how I start everything in my life is, like, there is a a market, normally me and my wants, and somebody is not
15
00:00:55.220 --> 00:00:55.720
covering
16
00:00:56.635 --> 00:00:58.415
or or meeting that need.
17
00:00:59.035 --> 00:01:01.295
So then I have to go and do it myself.
18
00:01:02.875 --> 00:01:12.510
Well, good luck. It's a pain in the ass following all the software updates. It is, I went I went through the list. Way possible. I mean, it's good it's good that there's a lot of software updates.
19
00:01:13.235 --> 00:01:14.855
Yeah. I mean, there is a lot
20
00:01:15.555 --> 00:01:16.035
and,
21
00:01:16.515 --> 00:01:18.055
you know, the rabbit hole,
22
00:01:18.355 --> 00:01:19.335
the rabbit hole
23
00:01:20.710 --> 00:01:23.690
recap does not cover proper software updates anymore.
24
00:01:24.550 --> 00:01:31.455
And you know, and you guys also cover a bunch of other topics, so you couldn't go through the whole boring list and I wanted to go through the whole boring list and I wanted to go through the whole boring list
25
00:01:32.315 --> 00:01:42.640
and sort of mention all the things that we're gonna do. I'm happy to go through the whole boring list with you. You're really Thank you. You're really selling it to the listeners who are Oh, yeah. No idea. Whether or not they should turn it off now or if they should continue.
26
00:01:43.100 --> 00:01:46.560
I I think they should, unlike and unsubscribe right now.
27
00:01:47.005 --> 00:01:47.985
Tap that
28
00:01:48.765 --> 00:01:49.265
button.
29
00:01:50.045 --> 00:01:54.545
Just turn it off. Turn turn it off right now, guys. It's gonna be a long boring list.
30
00:01:54.990 --> 00:01:55.490
Yes.
31
00:01:56.670 --> 00:01:59.570
So okay. So just a couple of things.
32
00:02:00.350 --> 00:02:05.105
So Matt was kind enough to join me on the first episode where I steal his audience,
33
00:02:05.725 --> 00:02:07.185
it was very kind of him.
34
00:02:07.645 --> 00:02:08.145
And
35
00:02:09.005 --> 00:02:10.465
the idea here is
36
00:02:12.210 --> 00:02:13.350
I hope to have
37
00:02:14.930 --> 00:02:17.670
different guests, probably many will repeat
38
00:02:17.970 --> 00:02:19.990
as long as I don't bore them to death,
39
00:02:21.275 --> 00:02:26.975
to help me go through this list. I am not the type of person who enjoys talking to myself
40
00:02:27.515 --> 00:02:29.695
on things, so I like the conversation.
41
00:02:30.709 --> 00:02:32.890
I think you'll add more value to it,
42
00:02:33.829 --> 00:02:34.329
and,
43
00:02:34.790 --> 00:02:38.650
hopefully, you help me see other projects and other updates I've missed.
44
00:02:39.525 --> 00:02:41.865
And the the format will be,
45
00:02:42.965 --> 00:02:43.865
software releases,
46
00:02:44.885 --> 00:02:48.585
and then we'll talk about a few different things like, Taproot adoption,
47
00:02:49.750 --> 00:02:50.570
some initiatives.
48
00:02:51.510 --> 00:02:54.410
I wanna go touch through a few topics
49
00:02:54.950 --> 00:02:57.290
on the Bitcoin OPTAC newsletter.
50
00:02:59.865 --> 00:03:02.605
I will cover some Bitcoin some coin kite updates,
51
00:03:04.265 --> 00:03:06.285
and some of our other websites,
52
00:03:07.220 --> 00:03:15.395
and, you know, whatever other things we wanna talk about at the end. So hopefully, you have about an hour or so of of of stuff to to bore yourself to death.
53
00:03:15.875 --> 00:03:23.415
Let's fucking go. Sounds exciting. Alright. Yeah. So, so not to fully kill the audience from the beginning, we're gonna skip Bitcoin Core
54
00:03:25.150 --> 00:03:30.130
because that one has a wee bit of updates. So we'll start with hwi2.1.1.
55
00:03:34.285 --> 00:03:35.505
Let me get here
56
00:03:36.285 --> 00:03:39.185
the release, and it was surprisingly a small release.
57
00:03:40.100 --> 00:03:41.560
It's, it just adds
58
00:03:41.860 --> 00:03:43.400
Ledger Nano as support.
59
00:03:44.740 --> 00:03:50.255
They changed the yeah. They changed the detection of top root change outputs for Trezor,
60
00:03:51.595 --> 00:03:52.095
and
61
00:03:52.635 --> 00:03:53.295
they fixed
62
00:03:53.595 --> 00:03:54.655
the signing failure
63
00:03:55.129 --> 00:03:56.909
for Ledger Bitcoin app 2.x.
64
00:03:59.370 --> 00:04:00.989
Well, on the plus side,
65
00:04:02.170 --> 00:04:04.705
there is quite a few pull requests that are good there.
66
00:04:05.725 --> 00:04:07.345
I wonder what that means if
67
00:04:08.045 --> 00:04:09.825
they just weren't checking change
68
00:04:10.285 --> 00:04:12.305
for taproot addresses on Trezor.
69
00:04:13.160 --> 00:04:15.340
You know, I don't follow the Trezor part,
70
00:04:17.240 --> 00:04:19.580
on h w I, to be honest.
71
00:04:22.475 --> 00:04:27.055
I think oh, you know what? I think if I remember right, I think Trazer had,
72
00:04:27.595 --> 00:04:28.495
some checks
73
00:04:29.360 --> 00:04:32.260
that they did it, and then it broke HWI.
74
00:04:33.120 --> 00:04:37.215
And then I think they removed it, and now they probably fixed it and added again.
75
00:04:37.615 --> 00:04:38.355
Could be wrong.
76
00:04:38.815 --> 00:04:42.995
Somebody please let me know on the oh, yeah. You can go to bitcoin.review,
77
00:04:44.710 --> 00:04:45.690
that's the domain,
78
00:04:46.230 --> 00:04:49.290
and then on the top right there is a button called
79
00:04:50.470 --> 00:04:55.355
submit story or something like that. If you click there you can send your hate mail
80
00:04:55.735 --> 00:04:56.955
directly to me,
81
00:04:57.495 --> 00:04:58.795
which will be very welcome.
82
00:05:00.055 --> 00:05:01.195
Okay, so
83
00:05:02.090 --> 00:05:04.430
yeah. So there is also a pull request there for
84
00:05:05.050 --> 00:05:05.870
tap signer.
85
00:05:06.650 --> 00:05:07.850
We've, we've,
86
00:05:08.490 --> 00:05:10.750
written the code for Andrew
87
00:05:11.415 --> 00:05:14.555
Ciao, whom What is this big find out review website?
88
00:05:15.175 --> 00:05:19.595
That's gonna be the name of the pod and the name of the and the website for the pod.
89
00:05:20.120 --> 00:05:27.980
But then what are these Do you even know which pods you go on? I'm like, I'm I'm I'm just I'm supportive of this initiative because I'm just gonna
90
00:05:28.575 --> 00:05:42.030
take your show notes, and I'm just gonna read them on rabbit hole recap for our software update section. So I don't have to so I don't have to do all that. So I'm here to support that initiative. It makes it easier for me to track software updates.
91
00:05:42.544 --> 00:05:46.884
But this site isn't just software updates. I see I see the white paper.
92
00:05:47.905 --> 00:05:48.645
I see
93
00:05:49.560 --> 00:05:50.940
something about BIP 85
94
00:05:51.240 --> 00:05:53.980
here. So is this just a new supposed to be a news feed?
95
00:05:54.680 --> 00:05:55.500
Yeah. So
96
00:05:55.800 --> 00:06:00.855
originally, bitcoin dot review was going to be a place for me put articles on that we write.
97
00:06:01.475 --> 00:06:08.050
Like, we wrote the BIP 80 5 sort of, like, article there explaining some stuff about BIP 80 5. Right.
98
00:06:08.430 --> 00:06:12.610
But that initiative sort of like fell off the cracks. We didn't have time to do it.
99
00:06:13.070 --> 00:06:13.570
So,
100
00:06:14.510 --> 00:06:16.690
being lazy and not deleting the 2
101
00:06:17.665 --> 00:06:21.125
original entries there, I just added one more entry which is this podcast.
102
00:06:21.825 --> 00:06:26.485
Gotcha. And I need to fix a few things there, but essentially we're going to start putting in
103
00:06:27.650 --> 00:06:28.629
the pods there.
104
00:06:29.650 --> 00:06:33.430
And once I get the links fixed, you're going to get a show notes by clicking on it.
105
00:06:34.325 --> 00:06:34.825
And,
106
00:06:36.565 --> 00:06:38.665
yeah, so that's the home
107
00:06:38.965 --> 00:06:44.220
of the thing, and you can actually subscribe. Awesome. There is an XML there for RSS feeds, yay.
108
00:06:45.880 --> 00:06:49.100
Not that people use RSS feeds, I'm an RSS maxi.
109
00:06:49.455 --> 00:06:51.555
Yeah. Some some people still do. I do,
110
00:06:52.255 --> 00:06:53.475
and we support that.
111
00:06:54.095 --> 00:06:54.595
Alright.
112
00:06:55.775 --> 00:06:56.275
Next.
113
00:06:56.650 --> 00:06:59.070
Let's toot our own horns. You know
114
00:06:59.610 --> 00:07:00.270
on bitcointv.com
115
00:07:00.970 --> 00:07:01.630
you can
116
00:07:02.490 --> 00:07:08.925
subscribe via RSS feed, so whenever a channel posts something it comes into your RSS feed. Waiting for the way to automatically update,
117
00:07:09.385 --> 00:07:16.180
sub to submit the playlist to, to that awesome website. I mean, dude, figure it out yourself. It's possible.
118
00:07:18.080 --> 00:07:19.860
Alright. Next update, Matt.
119
00:07:21.280 --> 00:07:24.259
Okay. Cold card mark 4 version 504.
120
00:07:25.074 --> 00:07:25.895
That's us.
121
00:07:26.915 --> 00:07:28.854
So we improved the USB
122
00:07:29.315 --> 00:07:33.815
protocol, we added more encryption to it especially for the HSM mode,
123
00:07:37.210 --> 00:07:38.990
We increased the size
124
00:07:40.889 --> 00:07:41.389
of
125
00:07:41.850 --> 00:07:43.310
the HSM mode,
126
00:07:44.965 --> 00:07:45.865
how it handles
127
00:07:46.165 --> 00:07:48.104
the the the messaging back and forth.
128
00:07:48.965 --> 00:07:52.745
So the the people who are using ck bunker will enjoy these updates.
129
00:07:55.150 --> 00:07:57.570
We now have, regtest support,
130
00:07:58.350 --> 00:07:59.729
for testnet coins
131
00:08:00.325 --> 00:08:01.145
as well.
132
00:08:01.845 --> 00:08:04.265
So if you're a developer, you're gonna appreciate that.
133
00:08:06.245 --> 00:08:07.785
We did a major rework
134
00:08:08.730 --> 00:08:11.310
for all the tests and, again, reg test,
135
00:08:11.930 --> 00:08:13.150
for Bitcoin Core,
136
00:08:13.770 --> 00:08:16.110
and also the Linux support got improved.
137
00:08:17.225 --> 00:08:17.725
So,
138
00:08:18.025 --> 00:08:20.605
you know, we did hear the feedback from
139
00:08:20.905 --> 00:08:22.605
Linux devs using codecard,
140
00:08:23.520 --> 00:08:26.340
and they wanted to do that better, so that is better now.
141
00:08:27.520 --> 00:08:30.020
Some of the NFC stuff got improved,
142
00:08:30.965 --> 00:08:33.065
and Fully Noded now has
143
00:08:34.325 --> 00:08:34.905
a beta
144
00:08:35.925 --> 00:08:36.585
of their,
145
00:08:37.205 --> 00:08:41.420
of Fully Noded for iOS that supports codecard NFC, and it works.
146
00:08:42.280 --> 00:08:47.675
I think it's the first hardware wallet ever to do NFC with an iPhone. Yay. That's awesome.
147
00:08:47.975 --> 00:08:49.035
It is pretty cool.
148
00:08:49.495 --> 00:09:01.430
You know, and it's still going to be sort of like you know audio and all that stuff. I don't want to get people sort of like super hyped up but you know, just imagine that with 6 months of customer use and feedback and then you have something awesome.
149
00:09:04.084 --> 00:09:07.704
What else? We fixed it. A year and a half of feedback. But
150
00:09:08.084 --> 00:09:10.185
Yeah. No. You know, you could move fast.
151
00:09:10.620 --> 00:09:14.640
The thing is, like, app devs are sort of, like, a little sort of, like,
152
00:09:15.180 --> 00:09:19.100
more focused on some flashy stuff on lightning and other things. But
153
00:09:19.745 --> 00:09:28.165
Zeus should have NFC soon. Right? That's right. Zeus is working on it. That'll be big. Is working on it. I think there's a couple PRs.
154
00:09:28.630 --> 00:09:29.529
What about BlueWallet?
155
00:09:29.990 --> 00:09:31.529
Yeah, there is a PR there.
156
00:09:31.830 --> 00:09:35.290
I don't know, it hasn't moved much, but it's essentially ready.
157
00:09:36.485 --> 00:09:40.745
I mean, ready for sort of beta dev kind of thing, but it's there.
158
00:09:41.445 --> 00:09:43.690
Hopefully, soon, you'll make it,
159
00:09:44.570 --> 00:09:49.230
and then we'll have it on all of them, and I think it could be very cool. Especially because,
160
00:09:50.170 --> 00:09:51.550
I think it was a square
161
00:09:52.235 --> 00:09:53.535
which is blocks with
162
00:09:55.035 --> 00:09:55.535
Spyro
163
00:09:56.075 --> 00:10:03.820
will launch. Yeah. Once they release with NFC that's just people. That's right. So they're gonna do NFC and, you know, I did have a chat with
164
00:10:05.000 --> 00:10:05.660
with Stick
165
00:10:06.360 --> 00:10:07.580
and with
166
00:10:08.280 --> 00:10:08.780
Charles
167
00:10:09.495 --> 00:10:16.075
at Bitcoin Miami, and both of them are actually pretty interested in NFT as well. So the head of ledger and the head of ledger.
168
00:10:16.390 --> 00:10:40.740
That's right. So they're all excited about NFC as well. So not impossible, we end up seeing, you know, the 2 major competitors we have, also adding NFC, I think, will be fantastic for everybody. Yeah. I mean, if Ledger adds it, that should really push the needle because Ledger's gotta be the most sold, right, by far. Yeah. Oh, yeah. I mean We know they have at least a 1000000 customers because that's all the people that got leaked.
169
00:10:42.515 --> 00:10:45.575
We can count how many emails they have. Yeah.
170
00:10:46.035 --> 00:10:47.095
Right from the source.
171
00:10:48.810 --> 00:10:49.310
Amazing.
172
00:10:49.690 --> 00:10:51.630
Alright. So the other stuff is,
173
00:10:53.130 --> 00:10:53.870
it's small,
174
00:10:55.050 --> 00:10:55.950
mark 4,
175
00:10:57.515 --> 00:10:59.595
mark 4 version 0 3 was,
176
00:11:00.235 --> 00:11:04.495
you know, just more of that. Oh, and there was taproot, pay to taproot support added.
177
00:11:04.850 --> 00:11:06.310
That's important to mention.
178
00:11:07.170 --> 00:11:10.070
It's just that the the version o, 503
179
00:11:11.170 --> 00:11:11.750
and 504
180
00:11:12.130 --> 00:11:15.675
are kind of the same release. They just got split for reasons.
181
00:11:18.454 --> 00:11:23.959
So there there were a bunch of, like, little things. I I recommend if you're a cold card user, go check it out.
182
00:11:24.580 --> 00:11:27.240
Now mark 3, we didn't forget about you.
183
00:11:27.779 --> 00:11:30.200
We also added Pay2 Taproot
184
00:11:30.695 --> 00:11:31.675
on, 415
185
00:11:32.695 --> 00:11:33.435
in May,
186
00:11:35.735 --> 00:11:38.970
and a few sort of, like, little, a few little bug fixes.
187
00:11:39.529 --> 00:11:40.750
There is more
188
00:11:41.370 --> 00:11:48.269
mark 4 features being down ported to mark 3, and the goal is to sort of eventually maybe make
189
00:11:49.545 --> 00:12:03.370
a release that, you know, most of the features that can be back part of the wheel work. So, just wanted to put that out there. Awesome. And are you still selling the MK 3? Yes. We still are. We're still gonna do it for a while.
190
00:12:04.625 --> 00:12:05.525
We're also
191
00:12:06.625 --> 00:12:08.085
using the mark threes
192
00:12:08.705 --> 00:12:13.510
because they're slightly lower cost, and we've already recouped the r and d on it
193
00:12:14.950 --> 00:12:15.450
to
194
00:12:16.070 --> 00:12:16.970
to help
195
00:12:18.630 --> 00:12:19.130
meetups,
196
00:12:19.510 --> 00:12:21.130
especially in developing world
197
00:12:21.695 --> 00:12:22.195
and,
198
00:12:22.794 --> 00:12:27.142
in poor countries to to disseminate hardware wallets
199
00:12:27.741 --> 00:12:29.341
hardware wallet use
200
00:12:29.940 --> 00:12:31.540
signing devices use.
201
00:12:32.950 --> 00:12:40.165
We we figured they can't really afford to buy units to demo and stuff, so we're sort of using the mark 3
202
00:12:40.565 --> 00:12:42.904
as a vehicle to do that. That's awesome.
203
00:12:43.285 --> 00:12:45.625
Yeah. You know props for that. It helps.
204
00:12:48.070 --> 00:12:50.730
Since everybody is now, Bitcoin price poor,
205
00:12:51.270 --> 00:12:52.890
you know, we're gonna send the hardware.
206
00:12:55.885 --> 00:12:59.985
Alright. Yeah. We're all having fun staying poor over here. That that's right.
207
00:13:01.005 --> 00:13:03.185
Okay. So BTC pay server,
208
00:13:04.420 --> 00:13:05.720
version 1.5.
209
00:13:08.500 --> 00:13:10.475
I am not a BTC pay
210
00:13:11.035 --> 00:13:14.255
server user, but it is a project that is widely
211
00:13:16.074 --> 00:13:18.495
installed. And the two main things of this new release
212
00:13:18.810 --> 00:13:20.110
are the new dashboard,
213
00:13:20.410 --> 00:13:21.470
it looks jazzy.
214
00:13:22.890 --> 00:13:25.470
They do a very good job at showing all
215
00:13:26.090 --> 00:13:27.710
the statistics of your store,
216
00:13:28.745 --> 00:13:31.004
recent transactions, recent invoices.
217
00:13:32.425 --> 00:13:35.644
I do have a payment processor for our for CoinKite,
218
00:13:36.024 --> 00:13:40.310
on the credit card side, and it's starting to look like that. This is very nice.
219
00:13:41.010 --> 00:13:42.790
There is a dark mode as well.
220
00:13:43.330 --> 00:13:52.035
Very nice. I mean, they've had dark mode for a while, I think. Okay. And then they have this, payout processor. I think they can batch transactions.
221
00:13:53.855 --> 00:13:56.115
Oh, and it also improves the,
222
00:13:57.170 --> 00:13:58.870
how it handles partial
223
00:13:59.730 --> 00:14:01.829
payments on pool transactions.
224
00:14:02.130 --> 00:14:02.630
So,
225
00:14:03.170 --> 00:14:05.125
when they're using pool for
226
00:14:06.705 --> 00:14:07.205
lightning,
227
00:14:07.985 --> 00:14:12.805
they can handle that better. I'm probably not sure. How does the pool payments work on BTCPay?
228
00:14:13.370 --> 00:14:16.269
Are you aware? I'm not sure. Nope. I don't use it.
229
00:14:16.889 --> 00:14:18.269
I am, I am
230
00:14:18.649 --> 00:14:22.509
a based layer kind of guy so I don't use a lot of lightning.
231
00:14:23.165 --> 00:14:36.350
I mean, at CoinKite, you basically you use the in house solution that you guys made. Right? Yeah. No. I'd love to it's it's it's just BTC pay server came after we already had invested, you know, like, years building our own infrastructure.
232
00:14:38.009 --> 00:14:42.565
And our stores not in source. Right? No. It's, it's like a a monstrosity.
233
00:14:44.305 --> 00:14:45.365
It's a true monstrosity.
234
00:14:46.225 --> 00:14:47.820
You know, it's it's like shipping,
235
00:14:48.520 --> 00:14:49.020
sales,
236
00:14:49.400 --> 00:14:51.020
all the stuff is in there,
237
00:14:51.640 --> 00:14:58.895
and it's like very us way of building it. I don't think many people would like to to take that on.
238
00:15:00.635 --> 00:15:03.055
Yeah. So if BTCPay existed
239
00:15:03.355 --> 00:15:05.490
way back then, maybe you would have gone with it.
240
00:15:07.410 --> 00:15:10.550
It's also dot net, which is not my favorite
241
00:15:11.490 --> 00:15:13.110
flavor of spam,
242
00:15:14.195 --> 00:15:21.334
but, but it is very good. And I mean, you know, in c sharp and, you know, dot net is a real language. It's not like this is JavaScript based.
243
00:15:22.410 --> 00:15:22.890
So,
244
00:15:23.290 --> 00:15:25.390
props to them. This looks awesome.
245
00:15:25.930 --> 00:15:29.150
There there's a lot of this really easy. You can enable and disable users,
246
00:15:31.215 --> 00:15:32.515
lots of UI improvements,
247
00:15:33.535 --> 00:15:37.315
and, yeah. I highly recommend people checking this project out.
248
00:15:39.120 --> 00:15:40.260
Okay. Now BlueWallet.
249
00:15:42.480 --> 00:15:42.980
BlueWallet,
250
00:15:44.855 --> 00:15:45.755
So version
251
00:15:46.135 --> 00:15:46.635
6.2.18
252
00:15:50.855 --> 00:15:51.355
Making
253
00:15:51.980 --> 00:15:54.319
a point at not going to the GitHub
254
00:15:54.779 --> 00:15:57.759
release it release because it's just endless,
255
00:15:58.540 --> 00:15:59.600
amount of commits.
256
00:15:59.944 --> 00:16:02.204
I want just somebody to stop. Do the Marty,
257
00:16:02.665 --> 00:16:08.524
just read the release notes? No. Because, like, there is not like, the problem is, you know,
258
00:16:08.879 --> 00:16:11.540
unless you are a project contributor
259
00:16:12.720 --> 00:16:16.740
or somebody who truly, truly cares about the commits of a specific project,
260
00:16:18.165 --> 00:16:27.430
you want the summary, right, of the release. So like notable Like why does this matter to me? Yeah, like the notable features, right? So I'm going to put this call out to devs out there.
261
00:16:27.910 --> 00:16:31.130
Do me a favor, you know, on your on your,
262
00:16:32.230 --> 00:16:32.730
Apple,
263
00:16:34.310 --> 00:16:37.050
release notes on the app store or Android or whatever,
264
00:16:37.654 --> 00:16:40.634
or on your release notes at the top, put noteworthy
265
00:16:41.095 --> 00:16:41.834
or summary
266
00:16:42.214 --> 00:16:44.954
of the releases and put something there.
267
00:16:45.350 --> 00:16:53.690
Yeah. Every release note should have a TLDR at the top. Yeah. I I think that's that's why we we try to do that on Twitter and a few others do that on Twitter,
268
00:16:54.825 --> 00:16:56.285
because it does help.
269
00:16:57.945 --> 00:16:58.445
Anyways,
270
00:16:59.145 --> 00:17:01.325
so for blue wallet, 6.2.18,
271
00:17:02.825 --> 00:17:03.710
it says fix,
272
00:17:04.510 --> 00:17:05.010
reorder
273
00:17:05.450 --> 00:17:05.950
wallet
274
00:17:06.390 --> 00:17:06.890
screen
275
00:17:07.330 --> 00:17:07.830
crush.
276
00:17:08.270 --> 00:17:10.370
So we'll go back one more, in January
277
00:17:10.750 --> 00:17:11.970
they released 6.2.17
278
00:17:14.195 --> 00:17:14.695
and
279
00:17:15.235 --> 00:17:19.495
now they show the selected coin summary on coin control screen. That's nice.
280
00:17:20.995 --> 00:17:22.775
Navigate to selected wallet.
281
00:17:24.309 --> 00:17:25.930
Rewarded wallet in clunky
282
00:17:26.470 --> 00:17:30.570
is clunky to use. That's a fix, and they deleted AOPP,
283
00:17:31.190 --> 00:17:32.250
which is great.
284
00:17:33.304 --> 00:17:34.205
What was the
285
00:17:34.664 --> 00:17:36.445
yeah. I know. It's bullshit.
286
00:17:37.225 --> 00:17:39.885
It's it's helping the bad people.
287
00:17:41.340 --> 00:17:43.200
I don't care how people spin it.
288
00:17:44.940 --> 00:17:48.320
Yeah. There's just there's no reason for it. That's right.
289
00:17:49.295 --> 00:17:49.775
Alright.
290
00:17:50.415 --> 00:17:51.395
Cold core.
291
00:17:51.695 --> 00:17:53.795
I'm surprised they it took, like,
292
00:17:54.575 --> 00:17:59.450
that they waited this long to remove it and then still removed it. Well, they removed it in January
293
00:17:59.909 --> 00:18:00.409
31st.
294
00:18:01.190 --> 00:18:03.610
So, yeah, now that's actually quite late, isn't it?
295
00:18:04.149 --> 00:18:08.855
Oh, okay. So we're talking about them getting rid of AOPP January 31st. Got it. Yeah.
296
00:18:09.875 --> 00:18:23.085
I went back one more update because the I guess because this is the first one, so you gotta, like, catch up and then Well, no. It's just too thin. Release this. You know, the 6 point the the one in February was just too thin, so I went I went down one more.
297
00:18:23.465 --> 00:18:23.965
Gotcha.
298
00:18:24.745 --> 00:18:25.804
Alright. So,
299
00:18:26.904 --> 00:18:30.360
this is a project I really like. A lot of people don't know about it.
300
00:18:30.840 --> 00:18:32.540
It's called Cold Core.
301
00:18:33.480 --> 00:18:34.700
It's by James O'Byrne,
302
00:18:36.360 --> 00:18:40.220
and it's essentially a command line Bitcoin wallet.
303
00:18:40.825 --> 00:18:41.725
Very featureful,
304
00:18:43.304 --> 00:18:45.885
very pretty for people who like the command line,
305
00:18:47.385 --> 00:18:47.865
and,
306
00:18:48.664 --> 00:18:49.405
it supports
307
00:18:50.630 --> 00:18:52.170
hardware wallets, which is great.
308
00:18:52.630 --> 00:18:54.650
He built it for him to use. It's called,
309
00:18:54.950 --> 00:18:55.450
Coldcard,
310
00:18:56.764 --> 00:18:57.745
hence, Coldcore.
311
00:18:59.325 --> 00:19:02.065
But I think it works with other hardware wallets if I remember right.
312
00:19:03.164 --> 00:19:04.399
Anyways, so
313
00:19:04.779 --> 00:19:05.759
the 0.31
314
00:19:06.380 --> 00:19:06.880
release
315
00:19:08.220 --> 00:19:14.155
It just uses HWI, doesn't it? I believe so. Yeah. So, like, it presumably could work with other wallets,
316
00:19:16.055 --> 00:19:17.115
other signing devices.
317
00:19:17.575 --> 00:19:19.835
Yeah. Well, you'd still have to connect it. Right?
318
00:19:22.019 --> 00:19:24.760
It's not like plug and play per se.
319
00:19:25.940 --> 00:19:31.675
So anyways, I don't know. Somebody should check it out, and let us know. So in April 17th,
320
00:19:34.215 --> 00:19:36.075
where is I lost it.
321
00:19:37.870 --> 00:19:39.809
I lost it. Oh, release. Here.
322
00:19:40.350 --> 00:19:41.730
Bam. There you go.
323
00:19:42.669 --> 00:19:43.169
So,
324
00:19:43.630 --> 00:19:47.174
the release notes here. So, Wayland clipboard support,
325
00:19:48.914 --> 00:19:49.975
that's that's just
326
00:19:50.835 --> 00:19:51.735
never mind.
327
00:19:52.550 --> 00:19:53.370
Allow specification
328
00:19:53.750 --> 00:19:58.650
for fee rate in repair sand. Well, that's nice. So you can, set your fee rate
329
00:19:59.590 --> 00:20:01.210
and some RPC fixes.
330
00:20:02.865 --> 00:20:05.365
So this is a nerdy wallet with a nerdy update.
331
00:20:05.665 --> 00:20:06.725
It's a great wallet.
332
00:20:09.160 --> 00:20:14.220
Moving on to I have a nerdy wallet with a nerdy update. Nailed it. Right?
333
00:20:14.760 --> 00:20:22.695
But shout out to Oberyn. It's it's pretty cool project. Why why don't you you know, maybe the format should include a little nugget about,
334
00:20:23.395 --> 00:20:24.375
about the maintainers
335
00:20:24.760 --> 00:20:26.700
or the main maintainers of the project.
336
00:20:28.040 --> 00:20:32.620
I think when relevant, I mean, ideally, most of these projects have multiple
337
00:20:33.235 --> 00:20:47.559
many contributors. Right? But ColdForce is literally an Elburn project. Right? Like, he just carries it on his back. So It's like Sparrow, which is just like a Craig Raw project. That's right. So so James is both a Bitcoin core contributor,
338
00:20:48.740 --> 00:20:49.240
a,
339
00:20:49.940 --> 00:20:51.240
I believe he writes
340
00:20:52.575 --> 00:20:53.554
economic stuff,
341
00:20:54.414 --> 00:20:56.274
and he's also a great DJ.
342
00:20:58.174 --> 00:21:02.950
So that's a little trivia there for people that did not know much about James O'Byrne.
343
00:21:04.050 --> 00:21:04.550
So,
344
00:21:05.970 --> 00:21:07.735
going to fully note it.
345
00:21:09.255 --> 00:21:09.755
The
346
00:21:10.215 --> 00:21:10.715
0.3.3
347
00:21:11.735 --> 00:21:12.235
version,
348
00:21:12.695 --> 00:21:16.955
fixes some bugs where lnd node via my node would fail.
349
00:21:17.350 --> 00:21:19.130
Well that's a nice bug to fix.
350
00:21:20.630 --> 00:21:20.870
And,
351
00:21:21.830 --> 00:21:23.610
it prevented batching from working.
352
00:21:23.910 --> 00:21:25.610
Okay, so there you go.
353
00:21:26.315 --> 00:21:30.555
And why not, go back a couple more versions here because it's so thin. So,
354
00:21:31.275 --> 00:21:45.025
in April they had, bug fixes. Noted to another project like that. It's a Fontaine project. That's right. I got to meet Fontaine in Miami. Great dude. Yeah. And I believe it's him on the Internet, but it's good to meet him in person. That's right.
355
00:21:46.044 --> 00:21:50.784
I also met him in person the first time in Miami, I think. Or was it in Riga? Can't remember.
356
00:21:52.740 --> 00:21:55.240
It's gotta be Miami because I was in Riga with you.
357
00:21:55.540 --> 00:21:56.840
I didn't meet him in Riga.
358
00:21:57.780 --> 00:22:01.080
Yeah. But I met him in in Miami. I got him on stage too,
359
00:22:01.935 --> 00:22:02.675
which is great.
360
00:22:03.295 --> 00:22:05.315
Oh, nice. It was so funny. Like,
361
00:22:06.735 --> 00:22:09.635
people get excited about, like, these different billionaires and shit,
362
00:22:10.260 --> 00:22:13.600
and, like, getting them on stage. I'm like, yeah. I got Fontaine and Craig Raw.
363
00:22:14.700 --> 00:22:15.440
Super excited.
364
00:22:16.140 --> 00:22:17.600
I mean Who who is that?
365
00:22:18.725 --> 00:22:20.345
You know, the the real Bitcoin
366
00:22:20.725 --> 00:22:22.565
where it happens. Right? It's,
367
00:22:23.045 --> 00:22:26.505
oh, I mean, what is real Bitcoin? Bitcoin is available to everyone.
368
00:22:27.330 --> 00:22:28.710
Billionaires and plebs.
369
00:22:29.090 --> 00:22:38.155
Yeah. I mean, if if you're frustrated with how people use Bitcoin or who's using Bitcoin right now, it's only gonna get worse from here. No. I mean, you really don't understand Bitcoin.
370
00:22:38.615 --> 00:22:39.115
Yeah.
371
00:22:40.054 --> 00:22:41.595
Alright. So 0.3.0.
372
00:22:43.440 --> 00:22:46.899
If you run a joint market server, you can now connect directly,
373
00:22:47.760 --> 00:22:49.299
if you're using core. That's nice.
374
00:22:50.240 --> 00:22:52.155
So joint market support on,
375
00:22:52.715 --> 00:22:56.815
fully in audit is improving. I guess that's my take from the last few updates.
376
00:22:57.755 --> 00:22:59.695
That's nice. And as I mentioned earlier,
377
00:23:00.240 --> 00:23:02.260
they also have now the
378
00:23:02.640 --> 00:23:04.020
the test lite version,
379
00:23:04.480 --> 00:23:06.260
beta version of NFC.
380
00:23:07.045 --> 00:23:10.665
So thanks, Fontaine, for for doing a lot of awesome work.
381
00:23:11.685 --> 00:23:12.825
Next is
382
00:23:13.125 --> 00:23:13.625
Nunchuk,
383
00:23:14.470 --> 00:23:15.130
which is
384
00:23:16.230 --> 00:23:22.145
Hugo. Hugo is doing a fantastic job with this with this wallet. A lot of people don't know about it.
385
00:23:22.705 --> 00:23:23.525
It's essentially,
386
00:23:24.785 --> 00:23:26.485
multi user, multi sig.
387
00:23:28.385 --> 00:23:28.885
It's
388
00:23:29.830 --> 00:23:32.250
it's very focused on on proper security.
389
00:23:33.430 --> 00:23:35.530
His app is fully native,
390
00:23:36.390 --> 00:23:40.825
so they're coding everything native in all the platforms, which is a bit of a feat.
391
00:23:42.565 --> 00:23:44.425
And, they have essentially
392
00:23:44.885 --> 00:23:45.705
a server
393
00:23:46.660 --> 00:23:50.039
that doesn't really know much about you to just coordinate
394
00:23:50.340 --> 00:23:51.960
messaging between the
395
00:23:52.419 --> 00:23:53.080
the clients.
396
00:23:53.895 --> 00:23:56.475
So that means, you know, you can,
397
00:23:57.175 --> 00:23:59.195
you can sort of propose a transaction
398
00:23:59.895 --> 00:24:06.370
to your your quorum of users in that multisig, and they'll get a message saying, you know, please sign this.
399
00:24:07.390 --> 00:24:12.395
You know, I am me, and I really wanna send it to this address, and then the people can choose to sign it or not.
400
00:24:13.975 --> 00:24:16.635
If you're familiar with an old project called
401
00:24:16.935 --> 00:24:17.435
copay,
402
00:24:18.560 --> 00:24:22.260
it's, it's similar, but, much better, implemented.
403
00:24:24.240 --> 00:24:26.580
And these guys are really plowing through here.
404
00:24:27.845 --> 00:24:29.065
So now they do,
405
00:24:29.684 --> 00:24:30.664
proper full,
406
00:24:31.205 --> 00:24:33.145
end to end encryption for the messaging.
407
00:24:35.590 --> 00:24:38.250
You don't need, and this was, it's
408
00:24:38.630 --> 00:24:41.049
so funny, these are all my requests to Hugo.
409
00:24:43.575 --> 00:24:47.115
Primary key accounts, now you don't need an email to sign up.
410
00:24:47.815 --> 00:24:49.035
There was also me.
411
00:24:50.450 --> 00:24:51.910
Large BSPT support.
412
00:24:52.450 --> 00:24:53.430
Yeah. That's great.
413
00:24:54.690 --> 00:24:57.190
Now they support, they improve the seed signer
414
00:24:57.815 --> 00:24:58.315
work.
415
00:24:58.855 --> 00:25:03.195
They support Signet, which is nice. Signet is essentially test net,
416
00:25:03.815 --> 00:25:05.790
but sort of like a new version of it.
417
00:25:07.710 --> 00:25:12.450
And then going back one more update, they added Taproot support in single sig only.
418
00:25:12.830 --> 00:25:20.345
I don't believe there is a multisig spec yet for Taproot use. So MuSig is still sort of like there's no implementation out there.
419
00:25:23.140 --> 00:25:30.920
And they're doing a bunch of other stuff that I don't know if it's public yet, so I'll keep on moving. Thanks, Hugo. This is a good list of updates.
420
00:25:31.225 --> 00:25:34.125
First of all, shout out to Hugo and the rest of the team over there.
421
00:25:35.705 --> 00:25:36.205
Their,
422
00:25:38.345 --> 00:25:42.710
their tool is is extremely slick and it's it's definitely
423
00:25:43.010 --> 00:25:43.830
very well,
424
00:25:44.770 --> 00:25:45.750
sorely needed,
425
00:25:46.770 --> 00:25:50.185
even amongst, you know, I'm a keyholder in multiple
426
00:25:50.645 --> 00:25:51.145
multisigs,
427
00:25:52.485 --> 00:25:57.809
that are that are collaborative multisigs with other other people for different organizations and whatnot,
428
00:25:59.790 --> 00:26:02.049
and even among the die hard Bitcoiners,
429
00:26:02.510 --> 00:26:06.345
there is a it is massive pain point, you know, transferring,
430
00:26:06.965 --> 00:26:13.700
PSVTs, partially signed Bitcoin transactions between each other to, like, sign multisig transactions. It's a complete pain in the ass,
431
00:26:14.740 --> 00:26:18.600
and a lot of lost time and mental energy, and it really simplifies it.
432
00:26:19.380 --> 00:26:21.720
My biggest issue right now is I'm pretty sure,
433
00:26:22.475 --> 00:26:31.455
you know, everything's run through these mobile apps, and I'm pretty sure the mobile apps are still closed source. Am I correct on that? Yeah. But, you know, it's pretty hopeless on that sense.
434
00:26:32.620 --> 00:26:41.360
On iOS you don't have a choice, right, for you to install the app, it's still gonna come from the store, so be your trusting. And in all honesty, the majority of the people using Android,
435
00:26:42.065 --> 00:26:48.485
you know, aside from, you know, the hardcore folks, like, they are also local They're not gonna verify it inside Lo No. But they could, and
436
00:26:48.970 --> 00:26:50.590
the the point remains that
437
00:26:51.130 --> 00:26:53.070
it's not a case where it's viewable. Right? That.
438
00:26:53.450 --> 00:26:55.470
Most most of the,
439
00:26:56.090 --> 00:26:57.230
Android wallets
440
00:26:57.595 --> 00:26:58.335
don't deterministically
441
00:26:58.715 --> 00:27:01.215
build, so that is kind of pointless too.
442
00:27:01.674 --> 00:27:05.455
I mean, but you still we still would like to see at least it being source viewable.
443
00:27:05.990 --> 00:27:09.270
I I think there's, like, some standards here. But if people if it's not
444
00:27:10.070 --> 00:27:18.305
see, the issue is when you have these wallets that the stack is huge, right? Millions of lines of code because of all the libraries they need to make it run on the phones,
445
00:27:19.885 --> 00:27:21.505
and then it's not deterministically
446
00:27:21.965 --> 00:27:22.465
built.
447
00:27:23.140 --> 00:27:25.800
You know, good luck trying to audit that code.
448
00:27:26.820 --> 00:27:30.600
It's nice to have, but realistically speaking it's pretty brutal.
449
00:27:30.980 --> 00:27:32.075
So I think
450
00:27:32.554 --> 00:27:38.014
more than solid loading at this point, it would be nice to to see deterministically built,
451
00:27:39.034 --> 00:27:39.774
phone wallets
452
00:27:40.260 --> 00:27:41.000
in my view.
453
00:27:41.380 --> 00:27:42.600
Okay. Including Nunchuck?
454
00:27:43.380 --> 00:27:46.440
Yeah. Yeah. All of them. I mean, you know, yeah. Like
455
00:27:46.900 --> 00:27:50.275
I'm just saying, like, I that that's, to me, that's, like, the biggest
456
00:27:50.895 --> 00:27:55.155
one of the biggest holdups in terms of But not all with a stable amount of money.
457
00:27:55.455 --> 00:27:57.290
No. No. All it's not all wallets are equal to.
458
00:28:05.825 --> 00:28:11.125
Yeah. But but really right. Wallet. Right? So the standards are higher, I would say, than, like, a spending wallet.
459
00:28:11.585 --> 00:28:13.045
Yeah. But, you know, like,
460
00:28:14.010 --> 00:28:19.230
when you look at the marketing of pretty much all the phone wallets, they all say just put all your funds in it.
461
00:28:21.045 --> 00:28:30.185
So so, you know, me, you, you know But I mean yeah. But still, nunchucks specifically is like the the its bread and butter is could be the ultimate
462
00:28:30.790 --> 00:28:37.210
organization savings wallet. But here's the thing. Right? Yes. I wanna see deterministic built on that wallet is a big deal.
463
00:28:39.774 --> 00:28:44.595
But one thing that is nice about it is because they're building things native and they're using
464
00:28:45.215 --> 00:28:47.554
like Bitcoin core methods of doing things,
465
00:28:48.190 --> 00:28:49.490
there is a lot less
466
00:28:49.790 --> 00:28:51.650
sort of, like, bullshit to dig through.
467
00:28:52.030 --> 00:28:56.130
So if they do add deterministic build to it, it should be very easy to
468
00:28:57.775 --> 00:28:58.434
to audit
469
00:28:58.735 --> 00:29:16.845
it. I mean, I know Hugo says he wants to, so Yeah. I mean, you know, it's like a nice to have thing. And he admits it's in beta still. He's he's in beta. Now, you know, now when you have, like, wallets that have, like, Java stacks and sort of, like, you know, major JavaScript stacks and they're serializing, serializing, serializing, serializing, like,
470
00:29:17.385 --> 00:29:17.885
secrets.
471
00:29:18.664 --> 00:29:20.284
That's really when
472
00:29:20.904 --> 00:29:21.404
things
473
00:29:21.705 --> 00:29:23.404
kind of shit hits the fan.
474
00:29:25.370 --> 00:29:28.430
It's hard to audit those projects. And and then
475
00:29:29.130 --> 00:29:40.775
if they are not deterministically built, it's even worse. Right? Because now it's already hard to audit it, and you cannot prove without reauditing every time, so it's it's tricky. Yeah. We wanna see that in all wallets,
476
00:29:41.790 --> 00:29:43.170
especially the ones out of beta.
477
00:29:48.085 --> 00:29:48.585
Alright.
478
00:29:49.925 --> 00:29:50.985
Next is,
479
00:29:52.485 --> 00:29:52.985
green.
480
00:29:54.085 --> 00:29:55.385
Blockstream green.
481
00:29:56.510 --> 00:29:58.370
That's another interesting wallet,
482
00:30:00.110 --> 00:30:02.290
and it's been in the market for a long time,
483
00:30:03.125 --> 00:30:08.905
And, and under, Green Address used to be the name of it, if you don't know the story of the project.
484
00:30:09.820 --> 00:30:12.000
And That was actually a really cool concept,
485
00:30:12.300 --> 00:30:13.840
the original green address.
486
00:30:14.620 --> 00:30:18.800
Yeah. I don't know. So the problem is green address is also the name of something else
487
00:30:19.154 --> 00:30:21.255
that was meant to be sort of like,
488
00:30:22.434 --> 00:30:22.934
unflagged
489
00:30:23.235 --> 00:30:28.135
or flagged as green addresses so that you know that's not like a drug dealer or something.
490
00:30:28.920 --> 00:30:31.900
Really? Who's, yeah. It was it was an unfortunate name.
491
00:30:32.760 --> 00:30:36.920
For else? Well, the anyway, the idea for the original green address was, like, you'd hold,
492
00:30:37.995 --> 00:30:39.695
it would be a collaborative multisig
493
00:30:40.555 --> 00:30:41.775
with green address
494
00:30:42.235 --> 00:30:49.170
or green wallet, whatever the previous name for green wallet was. I think it was green address. And so if you paid from there, a merchant could trust
495
00:30:49.550 --> 00:30:53.650
a zero confirmation transaction based on Green Address' reputation.
496
00:30:54.350 --> 00:30:59.695
Yep. That was exactly it. And that was, like, what, like, 2013 or 2014 or something like that?
497
00:31:00.154 --> 00:31:02.174
Yeah. Around that time. Maybe a little bit later.
498
00:31:02.554 --> 00:31:05.360
Yeah. I think I think it was post 2014,
499
00:31:05.740 --> 00:31:13.600
around that time. Concept never got any uptick. I mean, merchant adoption never really happened. So I think the name really sent back the concept too,
500
00:31:14.184 --> 00:31:18.605
because, it was kind of like around the time where there was a lot of talk around
501
00:31:19.304 --> 00:31:22.044
the people blocking transactions that were coming from,
502
00:31:22.424 --> 00:31:28.460
you know, things that they don't agree with. And they wanted to maybe include that at part of the Bitcoin consensus
503
00:31:29.080 --> 00:31:29.820
core code.
504
00:31:31.095 --> 00:31:33.835
So it was kind of bad name choice.
505
00:31:34.215 --> 00:31:37.835
But now it's called Blockstream green, which is great. It looks very pretty.
506
00:31:38.799 --> 00:31:40.100
And in the last update,
507
00:31:41.039 --> 00:31:45.700
they added support, support ID on settings about multisig wallet,
508
00:31:47.254 --> 00:31:47.995
they changed
509
00:31:48.695 --> 00:31:50.794
drop address in transaction list,
510
00:31:51.575 --> 00:31:52.554
updated GDK
511
00:31:54.029 --> 00:31:55.250
to, 0.0.54,
512
00:31:59.470 --> 00:32:04.505
and updated translations. It's kinda cool, they do support quite a few languages if I remember right,
513
00:32:05.765 --> 00:32:07.785
and they have been improving. I
514
00:32:08.245 --> 00:32:10.560
have one green wallet that I use
515
00:32:11.180 --> 00:32:13.280
for a specific purpose, and,
516
00:32:15.100 --> 00:32:18.140
they have been improving. Now they support also a
517
00:32:18.885 --> 00:32:25.065
see, one thing that always drove me insane with that project was the fact that you had to use their nonstandard
518
00:32:25.445 --> 00:32:28.630
way of doing Bitcoin multisig or you couldn't use the wallet.
519
00:32:29.590 --> 00:32:30.330
Now they
520
00:32:31.750 --> 00:32:32.250
support,
521
00:32:33.910 --> 00:32:36.090
like just standard single sig,
522
00:32:37.065 --> 00:32:40.205
as well as a few other forms of of script,
523
00:32:40.825 --> 00:32:41.885
which is nice.
524
00:32:42.745 --> 00:32:48.010
So, good for them for any I mean, Green Wallet was, like, way ahead of its time for a while, and
525
00:32:48.790 --> 00:32:54.250
then Blockchain acquired it. It was still kind of ahead of its time, and then they, like, let development
526
00:32:56.385 --> 00:32:58.804
stop. They didn't really have it as a priority,
527
00:32:59.105 --> 00:33:10.025
and then now it's just like they're doing it again, which is awesome. So Blockstream acquired them so that, as far as I understand, to to add to have a wallet that supports liquid. Right?
528
00:33:12.645 --> 00:33:13.145
And
529
00:33:13.605 --> 00:33:18.105
Then they came out with a different wallet called Okta. It was the same no. But it was the same code.
530
00:33:18.520 --> 00:33:22.700
Right. So then That was like a single sig. Exactly. So then they disambiguated
531
00:33:23.080 --> 00:33:27.420
the whole 50 different wallets into a single one that now supports everything. Right?
532
00:33:28.835 --> 00:33:32.055
I know they're working on PSPT support as well which is nice,
533
00:33:33.395 --> 00:33:35.735
and I believe they're also working on
534
00:33:36.340 --> 00:33:39.720
that HWI support because this wallet does support
535
00:33:40.180 --> 00:33:42.360
many different systems with a good UI.
536
00:33:43.434 --> 00:33:49.054
So I am looking forward to having this wallet work with gold cards so I can recommend to people
537
00:33:49.355 --> 00:33:50.894
who want a different wallet
538
00:33:51.490 --> 00:33:53.110
on their desktop or phone.
539
00:33:54.930 --> 00:33:55.430
Alright.
540
00:33:56.450 --> 00:33:57.670
Now the old
541
00:33:58.130 --> 00:34:00.310
good beast, one of my favorite wallets,
542
00:34:00.875 --> 00:34:01.375
Electrum,
543
00:34:03.195 --> 00:34:12.180
also one of the oldest wallets. I believe it's the first wallet after Bitcoin Core with, like, a a reasonable install base. It's that old.
544
00:34:12.640 --> 00:34:14.100
I think they launched in 2011.
545
00:34:17.414 --> 00:34:17.914
So
546
00:34:18.375 --> 00:34:20.474
they did add lightning to Electrum,
547
00:34:21.174 --> 00:34:21.674
which
548
00:34:22.135 --> 00:34:25.515
sort of made things more complicated in a very complicated code base.
549
00:34:27.020 --> 00:34:28.480
So in this last update,
550
00:34:28.780 --> 00:34:29.280
4.2.2
551
00:34:30.780 --> 00:34:31.840
in May 27th,
552
00:34:33.580 --> 00:34:34.780
the lightning
553
00:34:35.835 --> 00:34:37.855
on the lightning part, they added
554
00:34:38.315 --> 00:34:39.855
watching on chain outputs,
555
00:34:41.914 --> 00:34:45.520
enforce relative order of some of the messages
556
00:34:46.220 --> 00:34:46.720
during,
557
00:34:48.780 --> 00:34:49.840
rest reestablishment.
558
00:34:50.780 --> 00:34:55.605
I you know, that that goes into the lightning stuff that I don't really pay too much attention.
559
00:34:58.065 --> 00:35:02.359
I love lightning. It's just it's just too much for me to pay attention to.
560
00:35:04.900 --> 00:35:08.339
Especially especially Electrum's Python implementation, like
561
00:35:09.255 --> 00:35:10.955
Yeah. Well No one cares.
562
00:35:11.815 --> 00:35:19.789
I don't know. Like, the the thing about Electrum that I like is that it works. It just works, and it does everything you need to do, and in my
563
00:35:20.089 --> 00:35:21.710
lifetime, it never broke.
564
00:35:23.130 --> 00:35:23.630
So,
565
00:35:24.205 --> 00:35:27.265
like, respect for that is like and also, you know,
566
00:35:28.525 --> 00:35:30.225
maintaining a wallet this size
567
00:35:31.005 --> 00:35:36.190
is is not easy, and maintaining a wallet this size for, you know, these many years also not easy.
568
00:35:37.530 --> 00:35:44.405
I just I just wish they had not added lightning to that wallet. I wish they had made it maybe a side thing or, you know,
569
00:35:44.785 --> 00:35:58.050
maybe electrum lightning or something so you wouldn't be able to like, it was an easy task, like, there was a lot of man hours that went into that. Oh my god. It was monumental effort, and they you know, props to them. They they even started before a lot of the standards were in place.
570
00:36:00.415 --> 00:36:03.555
Similar with BIP 39, which they still don't support by default.
571
00:36:05.349 --> 00:36:12.170
And, but in my opinion, the biggest mistake that we made was putting starting development of Lightning on master branch
572
00:36:12.710 --> 00:36:13.609
that made
573
00:36:14.015 --> 00:36:16.035
Electrum essentially now released for a year.
574
00:36:17.775 --> 00:36:19.475
But they did, and it works,
575
00:36:20.015 --> 00:36:22.994
and they keep on pushing updates out, which is really cool.
576
00:36:23.560 --> 00:36:27.420
So, yeah, on the hardware wallets, smarter pairing during signed transactions,
577
00:36:28.440 --> 00:36:30.940
they fix a few things with keep key.
578
00:36:31.464 --> 00:36:33.724
It's amazing to me that keep key is still around.
579
00:36:34.425 --> 00:36:37.005
The Trezor clone? The Trezor clone,
580
00:36:38.184 --> 00:36:39.645
that went closed source
581
00:36:42.180 --> 00:36:46.040
because it was a different license at that time. It was a pre g p I when they cloned, I think.
582
00:36:46.420 --> 00:36:55.315
Oh, is this still is GPS closed source right now? I I think it is. I could be wrong, but I think it is. Well, anyway, if you're listening to this, don't use the keep key.
583
00:36:55.694 --> 00:37:00.849
Yeah. I mean, it's like they they no. They have I don't know if they even updated that project since
584
00:37:02.750 --> 00:37:03.470
Yeah. Let's just
585
00:37:04.085 --> 00:37:08.345
don't do it. It's not worth it. Makes no sense. So fix app image,
586
00:37:09.205 --> 00:37:11.625
fix fix bypass central proxy. Nothing
587
00:37:11.925 --> 00:37:12.425
really
588
00:37:13.070 --> 00:37:17.010
of note here. Fix a security fix, remove support for file
589
00:37:17.310 --> 00:37:19.570
in your eyes on BIP 70.
590
00:37:20.270 --> 00:37:21.170
BIP 70.
591
00:37:22.775 --> 00:37:23.275
Alright.
592
00:37:24.375 --> 00:37:25.515
So next.
593
00:37:27.975 --> 00:37:28.955
Oh, Spectre
594
00:37:29.255 --> 00:37:30.795
d Spectre Desktop.
595
00:37:31.510 --> 00:37:33.030
They have a nice tweet with,
596
00:37:33.910 --> 00:37:36.730
with the noteworthy updates. Thank you, Spectre.
597
00:37:38.550 --> 00:37:41.015
So Spectre Spectre is pretty good about it.
598
00:37:41.494 --> 00:37:43.115
Yes. So is BTCPay.
599
00:37:44.295 --> 00:37:57.050
Yes. I Thanks, Tara. I was pretty good about it. Yeah. Just just have a tweet, you know. Tweets are great. They force you to have a search. Like a nice little blog post too usually when you're updates, which is really nice. We are kind of all over the place.
600
00:37:58.175 --> 00:38:15.520
Essentially, what we do is we have a slightly shorter version of the release notes on Twitter and then a picture of the release notes and then the true fully released notes on GitHub. Yeah. You're a little bit of a hypocrite about it. Like, you could do a little bit better with it. Yeah. I mean, that's that's that's the basis of of being a company, is being a hypocrite.
601
00:38:16.595 --> 00:38:19.575
Fair enough. Well, at least you meant it. Do better every k.
602
00:38:20.914 --> 00:38:23.494
Alright. So Spectre 1 point
603
00:38:24.210 --> 00:38:24.710
10.3
604
00:38:25.410 --> 00:38:26.150
is out.
605
00:38:26.450 --> 00:38:28.069
Spook, spook, spook emoji.
606
00:38:29.650 --> 00:38:31.910
June 23rd. So it's recent.
607
00:38:32.714 --> 00:38:36.575
Okay so feature drag and drop for PSVT import. Well that's nice.
608
00:38:37.035 --> 00:38:38.015
So now we can,
609
00:38:38.315 --> 00:38:39.295
I can drag
610
00:38:40.280 --> 00:38:43.340
from my cold cards virtual disk into
611
00:38:43.800 --> 00:38:44.859
Spector desktop
612
00:38:45.400 --> 00:38:45.900
UI?
613
00:38:46.200 --> 00:38:47.260
That's pretty cool.
614
00:38:48.634 --> 00:38:50.654
It should make it a lot easier, and then they have
615
00:38:51.035 --> 00:38:53.775
6 bug fixes. See that's a summary,
616
00:38:54.315 --> 00:38:57.375
2 chores and one docs and one UI.
617
00:38:58.970 --> 00:39:04.430
So yeah, check out the Spectre desktop, it's a good project, and what I love about it it talks directly to core.
618
00:39:06.545 --> 00:39:11.285
It it's a it really is sort of like very little stack that you need to run it.
619
00:39:11.720 --> 00:39:14.940
And their UI does keep on updating and and improving.
620
00:39:15.960 --> 00:39:18.460
I mean, I think one benefit of Electrum
621
00:39:18.760 --> 00:39:20.460
stalling on updates to
622
00:39:21.345 --> 00:39:23.605
integrate their own lightning implementation was
623
00:39:23.985 --> 00:39:27.125
we might not have seen Spectre and Spyro get birthed otherwise.
624
00:39:27.825 --> 00:39:28.865
Yeah. No. It it's
625
00:39:29.265 --> 00:39:33.910
birthed out of this void that was left from Electrum not updating.
626
00:39:35.089 --> 00:39:36.710
Yeah. I mean, Bitcoin core
627
00:39:37.010 --> 00:39:37.510
web,
628
00:39:37.865 --> 00:39:40.425
like the the the UI wallet is,
629
00:39:40.905 --> 00:39:41.385
it's,
630
00:39:41.705 --> 00:39:43.645
you either love it or you hate it.
631
00:39:45.145 --> 00:39:51.370
Most of the devs who work on it love it, therefore, it doesn't change. It is also a monumental amount of change. It's
632
00:39:52.550 --> 00:39:54.810
changing UI in complex,
633
00:39:58.055 --> 00:39:58.555
desktop
634
00:39:58.855 --> 00:39:59.835
native software
635
00:40:00.214 --> 00:40:01.035
is complicated,
636
00:40:01.575 --> 00:40:02.714
especially when it's
637
00:40:03.015 --> 00:40:03.755
open source
638
00:40:04.295 --> 00:40:04.795
because
639
00:40:05.820 --> 00:40:06.320
designers
640
00:40:07.340 --> 00:40:07.840
and,
641
00:40:08.620 --> 00:40:10.240
UX people don't code.
642
00:40:11.100 --> 00:40:15.335
And in open source projects like Bitcoin Core is very sort of meritocratic
643
00:40:16.355 --> 00:40:24.840
and sort of self initiated, right? So if you wanna do something, go and do it, but in especially in Bitcoin Core, you're gonna get 10 noes before you get a yes.
644
00:40:27.460 --> 00:40:27.960
So
645
00:40:28.580 --> 00:40:32.760
if if you are the unicorn who can code and do UI,
646
00:40:33.815 --> 00:40:37.435
you're really gonna get 10 nos, but most guys can't code
647
00:40:37.815 --> 00:40:46.890
who can do UI, so they make these pretty UI's and then they sort of like here, somebody called this, which is the other 90% of the work and everybody's just like nope,
648
00:40:47.750 --> 00:40:48.250
right?
649
00:40:48.630 --> 00:40:50.475
So it's a tricky thing.
650
00:40:51.275 --> 00:40:53.535
We appreciate everybody for working on it.
651
00:40:55.595 --> 00:40:56.095
Alright.
652
00:40:56.555 --> 00:40:58.015
So moving on to
653
00:40:58.475 --> 00:40:58.975
Matt's
654
00:40:59.539 --> 00:41:06.119
favorite project, and because he literally dropped the open dimes hat for Sparrow's hat.
655
00:41:06.819 --> 00:41:07.799
It was noticed.
656
00:41:08.180 --> 00:41:09.079
I wear both.
657
00:41:09.445 --> 00:41:10.745
Yeah. No. You don't.
658
00:41:11.685 --> 00:41:13.945
I I I know. We're an old girlfriend.
659
00:41:14.405 --> 00:41:25.040
I just go through my phases where I just choose one hat and just wear it into the ground. So Sparrow is a relatively I see the the OpenDigm hat is it's really hard to wear it into the ground, the the,
660
00:41:25.420 --> 00:41:30.674
like, ripstop material or whatever that material is. It's Oh, you have the old trucker hat. Right?
661
00:41:31.055 --> 00:41:44.980
No. No. No. I have the good one. I have the one that's, like, made out of the mil spec material. Oh, those I like those. I have those Those like you can't destroy at all, and they're great for traveling. You literally can't destroy it. I used one of those ones to drink water off the lake.
662
00:41:47.105 --> 00:41:48.885
Yeah. So okay. So Sparrow,
663
00:41:50.224 --> 00:41:50.724
Sparrow
664
00:41:52.145 --> 00:41:54.885
is a very cool project, relatively new.
665
00:41:55.309 --> 00:41:56.930
Oh, is it 2 years old now?
666
00:41:58.670 --> 00:41:59.710
It's run by
667
00:42:00.109 --> 00:42:02.675
Maybe Les. Craig Craig Wright.
668
00:42:03.635 --> 00:42:05.735
Craig Rall. Craig Rall. Sorry.
669
00:42:06.035 --> 00:42:06.775
I know.
670
00:42:07.235 --> 00:42:07.735
Oops.
671
00:42:08.035 --> 00:42:09.735
Craig Craig Wright.
672
00:42:10.950 --> 00:42:12.810
Fuck my mouth. Fuck out. Jesus.
673
00:42:13.430 --> 00:42:16.410
Okay. For the audience, I'm dyslexic. Okay? Give me a break.
674
00:42:17.625 --> 00:42:24.444
So so, anyways, I met I met Craig in Miami. It was, it was fun. It was fun. It was fun. It was a nice time chatting. Yes.
675
00:42:24.744 --> 00:42:25.724
Very nice lady.
676
00:42:27.970 --> 00:42:30.230
So, so they are pumping features.
677
00:42:30.849 --> 00:42:31.349
Wow.
678
00:42:32.049 --> 00:42:35.430
He he he reminds me of doc hacks. They just pump
679
00:42:36.290 --> 00:42:36.950
and get
680
00:42:37.325 --> 00:42:38.144
shit done.
681
00:42:39.085 --> 00:42:40.144
I lost
682
00:42:41.724 --> 00:42:42.545
the release.
683
00:42:42.924 --> 00:42:49.510
I need to go see that here, Release notes. So Craig is, Craig does not have a good summary of notes.
684
00:42:49.970 --> 00:42:51.670
So we'll go through a few.
685
00:42:52.635 --> 00:42:55.135
So on May 26th they released 1.6.5,
686
00:42:56.795 --> 00:43:00.415
they added a Ledger Nano as support really because it's HWI.
687
00:43:01.180 --> 00:43:05.200
So you notice a pattern that all the wallets that use hwi
688
00:43:06.220 --> 00:43:13.015
will add, you know, it's not just plug and play, but they will go in and add the implementation of the new wallet that's been supported by HWI,
689
00:43:13.714 --> 00:43:16.454
which is a great way of handling all this stuff.
690
00:43:18.230 --> 00:43:22.810
They now allow watch only key stores to enable signing from matching
691
00:43:23.110 --> 00:43:24.650
connected hardware wallets.
692
00:43:25.265 --> 00:43:28.645
Oh, that's cool. So now you can sign connected too.
693
00:43:30.465 --> 00:43:33.205
They can also import gap limits from Electrum.
694
00:43:34.720 --> 00:43:36.740
I think they had different gap limits.
695
00:43:37.040 --> 00:43:41.300
For people that don't know, the gap limits are essentially how many derivation addresses
696
00:43:41.600 --> 00:43:43.540
and the space in between those
697
00:43:44.755 --> 00:43:47.335
you have or generate and start watching.
698
00:43:47.955 --> 00:43:50.855
So now they can match electrons when they import.
699
00:43:51.555 --> 00:43:52.055
So,
700
00:43:53.180 --> 00:43:55.680
Sparrow is a very was very clever
701
00:43:56.140 --> 00:43:57.040
on the beginning
702
00:43:58.140 --> 00:43:59.280
by essentially
703
00:43:59.660 --> 00:44:00.160
importing
704
00:44:01.734 --> 00:44:04.474
the Electrum, which is one of the most used wallets
705
00:44:05.174 --> 00:44:06.635
in the market before,
706
00:44:08.849 --> 00:44:14.390
importing their JSON file, which is their wallet file into Sparrow and just simply working,
707
00:44:15.410 --> 00:44:18.150
which is fantastic. I I love that kind of thinking.
708
00:44:20.355 --> 00:44:23.175
And then they have a bunch of bug fixes on the release,
709
00:44:23.555 --> 00:44:25.735
including one from Andrew Chow.
710
00:44:26.140 --> 00:44:27.359
Andrew Chow is now
711
00:44:27.819 --> 00:44:32.400
a a a signal isn't his he has a key now for Bitcoin Core. Right?
712
00:44:34.205 --> 00:44:34.705
He's,
713
00:44:35.085 --> 00:44:44.810
he's doing a lot of core work, and he's not in great hands if he does. Yep. He's a very bright kid. Love that, dude. We're lucky to have him. Yep.
714
00:44:45.290 --> 00:44:49.070
And if, Andrew is listening, make sure to merge TapSigner
715
00:44:49.450 --> 00:44:49.950
into
716
00:44:51.325 --> 00:44:51.825
hWI.
717
00:44:52.525 --> 00:44:53.345
We're waiting.
718
00:44:53.805 --> 00:44:54.625
Love you.
719
00:44:56.365 --> 00:45:01.240
Did I tell you that I gave a Sats card and a TapSigner to a, Titans football player?
720
00:45:02.180 --> 00:45:02.680
Nice.
721
00:45:03.220 --> 00:45:03.540
That's
722
00:45:04.580 --> 00:45:14.105
I I I hope that there is a wallet that supports it in the wilds. I I mean, I told him it, like, wasn't really ready yet. I was just using it as a demo, and he's like, can I have this? I was like, I was
723
00:45:14.405 --> 00:45:16.720
like, I'm not gonna say no to you. You can take it.
724
00:45:17.200 --> 00:45:25.055
Just know that you're, like, one of the few in the world who has it right now. That's right. He was super excited about it. It was like this young kid. That's awesome.
725
00:45:26.315 --> 00:45:29.535
Hopefully, soon, everybody's gonna have it. It's gonna be cheap. So,
726
00:45:30.315 --> 00:45:31.440
looking forward to that.
727
00:45:32.960 --> 00:45:34.099
Right. Bug fixes,
728
00:45:34.480 --> 00:45:37.940
restore hardware wallet from communication in older IO, macOS.
729
00:45:40.675 --> 00:45:43.095
When hiding empty used addresses,
730
00:45:43.635 --> 00:45:47.015
add and remove addresses if address balance changes.
731
00:45:48.700 --> 00:45:52.319
This is a classic programmer wrote the release notes.
732
00:45:53.819 --> 00:45:55.519
Explicitly commit spinner
733
00:45:55.965 --> 00:45:58.145
editor value when closing dialogues.
734
00:45:59.325 --> 00:46:01.505
So essentially they fix the spinning,
735
00:46:03.645 --> 00:46:04.865
of the mouse spinning.
736
00:46:06.020 --> 00:46:09.400
Fixed date sorting in the UTXO table, that's nice,
737
00:46:10.420 --> 00:46:11.720
and a few other ones.
738
00:46:13.175 --> 00:46:15.675
Oh, fix PSPT tap root internal key duplication.
739
00:46:16.295 --> 00:46:18.635
Okay. So they might have had a bug with that.
740
00:46:19.950 --> 00:46:25.089
And set lock all wallet menu control command status on every wallet lock,
741
00:46:25.630 --> 00:46:28.405
and that's just more closing little holes there.
742
00:46:28.885 --> 00:46:33.385
Well, I guess it's too bad we missed because the previous release was a massive release.
743
00:46:35.445 --> 00:46:38.345
They added native support for epom 1,
744
00:46:39.990 --> 00:46:42.569
They added a block stream jade support.
745
00:46:43.750 --> 00:46:45.609
They upgraded to to the newest,
746
00:46:46.695 --> 00:46:49.915
HWI, probably why the subsequent release had the nano,
747
00:46:50.375 --> 00:46:51.595
ledger, s,
748
00:46:53.415 --> 00:46:53.915
support.
749
00:46:55.790 --> 00:46:58.450
There's also taproot signing support now.
750
00:47:00.990 --> 00:47:02.369
Support scanning seeds,
751
00:47:04.785 --> 00:47:06.405
and a bunch of other things.
752
00:47:06.945 --> 00:47:09.445
Very, very good work. That's a lot of work.
753
00:47:11.000 --> 00:47:12.619
So props to Craig.
754
00:47:13.560 --> 00:47:18.700
Craig is an absolute legend. We're lucky to have him. I think the Sparrow is by far my favorite.
755
00:47:20.395 --> 00:47:25.215
Yeah. I mean, if it's software wallet to use with signers now. The UI is nice.
756
00:47:25.515 --> 00:47:35.100
Very nice. So nice. The way you visualize transaction. You know, like, what what he has done with with Sparrow reminds me of what you and Peter have done with Coldcard,
757
00:47:35.720 --> 00:47:39.305
which is you can very much tell that it's it's a person who
758
00:47:40.085 --> 00:47:41.705
or a group of people who,
759
00:47:42.244 --> 00:47:44.005
like, need they needed a solution on
760
00:47:44.645 --> 00:47:49.309
for for using Bitcoin. They needed a tool for using Bitcoin, so they built it around their own need.
761
00:47:49.930 --> 00:47:53.869
Yeah. I mean, it's not Shitcoin or Banker sort of like, hey. I need a wallet.
762
00:47:54.265 --> 00:47:59.805
Yeah. It's it's it's a 100%. Like, I I I need something to use, so I'm gonna build it myself.
763
00:48:00.265 --> 00:48:08.660
And then and then, you know, ideally, be able to make make some profit, some lean profit on the side of it with it. And,
764
00:48:09.515 --> 00:48:23.390
yeah, so shout out to him, and he is it is a monetized project now because he does have have the coin join built in, so he is making revenue off of it. But if you wanna support him, he has a donation page on spiral wallet dot com. That's great. Like, I I want sort of contributing.
765
00:48:23.849 --> 00:48:25.965
I want every sort of, like,
766
00:48:26.365 --> 00:48:27.345
good developer,
767
00:48:27.645 --> 00:48:28.145
good
768
00:48:28.525 --> 00:48:29.025
contributor
769
00:48:29.805 --> 00:48:30.305
to
770
00:48:30.685 --> 00:48:36.770
projects to make a killing, not just a little bit. I hope they all become extremely wealthy from their work.
771
00:48:38.750 --> 00:48:49.664
I mean, that's the ideal situation because the donation model is not sustainable. No. I mean, you know, it's it's what I, you know, like, I I I sort of, like, joke sometimes is bag wear. Right? Like, you can't
772
00:48:50.125 --> 00:48:51.184
you can't maintain
773
00:48:51.724 --> 00:48:56.630
money handling software on on, like, you know, on donations only. Right?
774
00:48:58.530 --> 00:49:07.165
And, you know, Bitcoin Core does have enough money because, you know, a lot of people got in early. A lot of people get grants. It's the base layer.
775
00:49:07.985 --> 00:49:13.150
You know, the side projects, all the the all the the the ecosystem projects. Right?
776
00:49:14.330 --> 00:49:18.030
It's a lot harder and a lot more complicated because, you know, traditionally,
777
00:49:18.970 --> 00:49:23.454
you know, if you wanna make sure, you know, you don't make money, you know,
778
00:49:23.994 --> 00:49:25.694
go work on open source projects.
779
00:49:27.340 --> 00:49:30.720
And then in Bitcoin, like, all those projects have also competition.
780
00:49:31.580 --> 00:49:34.640
So it diminishes even their sort of like their
781
00:49:36.175 --> 00:49:37.875
their their, their market base,
782
00:49:38.175 --> 00:49:44.275
and, it's just it's nice to see people come up with ways of making good money, and I hope they make all the money.
783
00:49:45.830 --> 00:49:46.650
So yeah.
784
00:49:46.950 --> 00:49:49.930
Yeah. No. You definitely you wanna see sustainable models.
785
00:49:50.310 --> 00:49:56.455
Yeah. Exactly. It needs to be sustainable. Right? I I don't want people having to email a bunch of people saying, hey, I need help
786
00:49:56.755 --> 00:50:01.735
financially to maintain this project. Like, you know, you want people to feel like they have enough value.
787
00:50:02.099 --> 00:50:07.640
But I I I think also at the same time, like, if you are finding if you find software useful
788
00:50:09.195 --> 00:50:13.295
and they accept donations, even if they are even if they are monetizing,
789
00:50:14.715 --> 00:50:17.530
still consider donating. It's it shouldn't be it shouldn't
790
00:50:27.914 --> 00:50:35.855
like, right now, like, basically, like, Sparrow is is ramping up his monetization, and it's becoming sustainable. Right? But in the early days,
791
00:50:36.180 --> 00:50:40.839
the donations still help even though he's doing that. And, like, a good example right now is Robosats,
792
00:50:41.619 --> 00:50:43.480
which is this new p to p KYC
793
00:50:44.385 --> 00:50:44.885
free,
794
00:50:45.665 --> 00:50:46.484
no KYC
795
00:50:47.185 --> 00:50:48.244
Bitcoin exchange
796
00:50:48.545 --> 00:50:54.600
that's Tor only. And, like, they're built from the ground up to be sustainable. Like, they take a fee of every transaction.
797
00:50:55.220 --> 00:51:02.985
I love it. But but those fees don't cover development right now still. Right. Right? Like, they're in this bootstrap phase, so I'm donating to RoboSats
798
00:51:03.685 --> 00:51:06.905
even though they have a sustainable model. So I'm just saying that people shouldn't
799
00:51:07.460 --> 00:51:16.120
just look at these things and be like, oh, well, you know, they're monetizing, so I'm not gonna donate. Right. I think another thing too is that, like, it it helps developers
800
00:51:17.865 --> 00:51:20.525
or like project manager. It helps the the project people
801
00:51:21.625 --> 00:51:22.125
to
802
00:51:23.065 --> 00:51:24.685
to see market signals.
803
00:51:24.985 --> 00:51:25.485
Right?
804
00:51:25.865 --> 00:51:26.365
So
805
00:51:27.300 --> 00:51:40.765
if they see that there is enough donations going to their project, they will put more effort in and build more features and and maybe or maybe they will maybe that's the the thing that makes it they make the decision if they're gonna go full time on it or not.
806
00:51:41.305 --> 00:51:41.805
Right?
807
00:51:42.585 --> 00:51:49.790
Because a lot of times, people just don't know how much market there is out there for what they make. People cheering on Twitter
808
00:51:50.330 --> 00:51:51.310
for the project
809
00:51:51.610 --> 00:51:53.870
doesn't really sort of mean much.
810
00:51:54.714 --> 00:51:59.935
It's very helpful is, like, in terms of, like, spreading the word about the project, but, like, people,
811
00:52:00.555 --> 00:52:01.295
you know,
812
00:52:02.180 --> 00:52:03.720
partying away with their SATs,
813
00:52:04.340 --> 00:52:06.920
to support a project really sort of reinforces
814
00:52:07.700 --> 00:52:14.195
for the maker that there is a market and they should continue. Right? Even if it may not be a lot now, like,
815
00:52:14.495 --> 00:52:20.809
it just signals to them that there is a market that that is willing to pay for it as opposed to just thank them for it. Right?
816
00:52:21.510 --> 00:52:24.410
I I think that's why it's so important to monetize things.
817
00:52:25.805 --> 00:52:26.305
100%.
818
00:52:26.765 --> 00:52:30.705
We're on the same page on this. Yep. Alright. So fountain
819
00:52:31.325 --> 00:52:33.025
the fountain app podcast.
820
00:52:33.565 --> 00:52:35.569
I'm gonna go you're gonna love this
821
00:52:35.869 --> 00:52:40.049
one. I'm gonna go through the to the app store, release notes,
822
00:52:40.589 --> 00:52:41.809
which is 0.4,
823
00:52:42.109 --> 00:52:43.410
bug fixes and improvements.
824
00:52:43.835 --> 00:52:44.335
0.3,
825
00:52:44.795 --> 00:52:46.095
bug fixes and improvements.
826
00:52:46.635 --> 00:52:47.135
0.319,
827
00:52:48.234 --> 00:52:53.060
bug fixes and improvements. I should tell Oscar that he should do better with that. Shout out to Oscar.
828
00:52:53.840 --> 00:53:00.500
I don't I don't have release notes for it. Well, the big one for so so the big one for 0,
829
00:53:01.714 --> 00:53:04.454
the the previous release, what is that, 0.3.0?
830
00:53:06.835 --> 00:53:16.830
Whatever. The the one before 4. The the one before the most recent release, the big improvement was offline listening, which I think is a must for podcasts. Oh, that has to it has to.
831
00:53:17.415 --> 00:53:21.994
So that was a big one. Fountain Podcast is a podcasting 2.0 app,
832
00:53:22.695 --> 00:53:26.395
where you can stream sats to content creators that you enjoy.
833
00:53:28.990 --> 00:53:29.490
So
834
00:53:29.950 --> 00:53:30.450
so,
835
00:53:30.910 --> 00:53:33.250
it's one of the leading ones along with Breezewallet.
836
00:53:34.745 --> 00:53:45.970
Yeah. So offline listening was a big ad for the previous release, and then this release, the big ad is listeners now can earn SaaS. If you listen to a podcast through Fountain Podcasts, you automatically, without
837
00:53:46.510 --> 00:53:48.849
doing anything, just start receiving SATs.
838
00:53:49.309 --> 00:53:53.345
Yeah. That's pretty cool. Getting paid. Nice little incentive structure. Exactly.
839
00:53:54.444 --> 00:53:56.944
Money goes from the advertiser to
840
00:53:58.350 --> 00:54:01.410
to the Exactly. Media. You actually get paid more if you listen to ads too.
841
00:54:02.190 --> 00:54:03.010
That's great.
842
00:54:03.790 --> 00:54:08.775
It's like a cool concept. They're playing they're, like, tweaking the incentives over there, but it's a pretty cool concept.
843
00:54:09.075 --> 00:54:11.974
The one major negative of Fountain right now
844
00:54:12.355 --> 00:54:15.335
is that the the Lightning Wallet is custodial. So
845
00:54:16.529 --> 00:54:25.755
you have custodial risk there. You shouldn't keep them I I don't have a problem with that. But they are they are actively trying to get away from that, and they'll probably end up using Greenlight,
846
00:54:26.375 --> 00:54:30.475
through Blockstream, which is a trust minimized cloud solution.
847
00:54:30.855 --> 00:54:31.355
Nice.
848
00:54:31.655 --> 00:54:34.790
Yeah. I mean, realistically speaking, you know, like, lightning
849
00:54:35.570 --> 00:54:41.015
lightning amounts are economically more irrelevant. Right? So it's like it's not, like, the incentive to
850
00:54:41.494 --> 00:54:43.434
rob your own user base is a lot lower.
851
00:54:43.734 --> 00:54:44.615
It's it's like,
852
00:54:45.255 --> 00:54:56.500
the way I look at it is like, okay. So, like, how much cash do you have in your back pocket if you go out? Exactly. Like, if you get robbed in that situation and you lose a $100, it's not And realistically speaking, running your own lightning node is a bit of pain in the ass.
853
00:54:57.405 --> 00:55:00.145
You know? So I I think it's a it's a reasonable compromise.
854
00:55:00.605 --> 00:55:04.545
The bigger issue is with custody is, like, if you get big enough
855
00:55:05.420 --> 00:55:09.119
the regulators are gonna come after you and make you add KYC, and no one wants KYC.
856
00:55:09.500 --> 00:55:15.994
That's yeah. So Greenlight is actually a really compelling solution here. The major negative of Greenlight is,
857
00:55:17.255 --> 00:55:20.395
the node is offline if the user's app isn't open,
858
00:55:21.255 --> 00:55:26.410
because the user's app is holding the keys. That's what makes a trust minimized. The keys aren't on the server.
859
00:55:26.790 --> 00:55:30.250
Right. But in this particular instance, if it's a listener paying
860
00:55:30.795 --> 00:55:51.025
while they're listening to a podcast, they already have the app open, so green light could be perfect for that. It doesn't solve the problem for the content creator. The content creator basically needs a 247 node always on. Right. Well but Fountain app could also just just handle that for the content creator too. Right? They can they can host the bitcoin dot review. Or, like, Voltage. They could do, like, Voltage
861
00:55:52.285 --> 00:55:56.225
for the 247 node, something like that where you have a hosted node.
862
00:55:57.059 --> 00:55:58.839
It's fun to see new stuff.
863
00:55:59.619 --> 00:56:10.705
You know, that that's another nice thing too. It's like that's like like new and novel. Like, it's nice that people are trying different stuff. They're not just sort of, like, trying to compete on the same sort of spec at some other app.
864
00:56:12.180 --> 00:56:12.839
I agree.
865
00:56:13.220 --> 00:56:20.975
Cool. But shout out to Oscar and the rest of the fountain team. Yes. Please add release notes. Like they're building over there. Yep. But also, yeah, add release notes,
866
00:56:23.135 --> 00:56:30.115
dude. He usually releases a blog put he releases, like, blog post that's pretty good about with the updates, but you should have it in the App Store too.
867
00:56:32.280 --> 00:56:34.840
No. I I bet there was. I mean, you know so just,
868
00:56:35.560 --> 00:56:49.280
Matt sent me Fountain app to add to the list, but he, of course, did not give me the proper URL for it with the release notes. I mean, NVK, like, messaged me 2 hours ago, and he was like, I wanna do the show. You wanna be the first guest? And I was like, yeah. I'd found it.
869
00:56:49.819 --> 00:56:56.375
Because he sent me a whole list of all the updates. It was the first thing I knew. This wasn't there. So I'm gonna move on now to the Bitcoin
870
00:56:56.755 --> 00:56:57.735
to the Bitcoin
871
00:56:58.115 --> 00:56:58.615
uptech.
872
00:57:00.435 --> 00:57:03.255
Do you have any other apps that we may have missed?
873
00:57:07.130 --> 00:57:10.670
Well, Wasabi 2.0 came out. That way we should use it.
874
00:57:11.605 --> 00:57:12.505
Yeah. Well,
875
00:57:13.045 --> 00:57:14.105
I think it's complicated.
876
00:57:14.405 --> 00:57:14.645
The
877
00:57:15.365 --> 00:57:22.099
They're using chain analysis. They're paying chain surveillance firms to fucking But every every yeah, I mean, it sucks.
878
00:57:22.400 --> 00:57:23.220
It does suck.
879
00:57:23.839 --> 00:57:30.579
But I think we're gonna more and more see that happening. And I think a lot of projects that deal with stuff like this,
880
00:57:31.185 --> 00:57:34.885
they have a server that have a server side. Let's just straight cope.
881
00:57:35.745 --> 00:57:44.450
No. I I don't use Wasabi personally because I I don't really, I use JM. Well, on top of that, if for whatever reason, if you're using a privacy wallet that is
882
00:57:44.830 --> 00:57:47.650
literally over complying, you're paying change surveillance,
883
00:57:47.950 --> 00:57:50.715
it's fine for you. I would add that,
884
00:57:52.215 --> 00:57:56.155
so Wasabi 2.0, the reason I'm bringing it up is because there was a massive change,
885
00:57:56.455 --> 00:57:57.755
in how they do CoinJoin.
886
00:57:59.990 --> 00:58:10.105
You know, it was a fundamental change, and they implemented this new protocol, Wabi Sabi, which, like, on the surface, seems like a pretty cool improvement. You don't have a minimum amount anymore.
887
00:58:11.045 --> 00:58:13.385
The UX is cleaned up a lot,
888
00:58:15.380 --> 00:58:21.640
but it's complicated. Like, the the the method they're using is kind of obscure and complicated.
889
00:58:23.220 --> 00:58:33.914
But isn't it viewed? I I The lead the lead creator of Wacker. I have not, like, looked into it at all. Well, that's one of the issues they have is, like, a lot because they
890
00:58:34.520 --> 00:58:42.860
because they added this change surveillance element, they've lost a lot of their die hard contributors because they're all privacy focused people. Mhmm. So review is minimal.
891
00:58:43.240 --> 00:58:47.875
And then the creator of this Wabi Sabi protocol, which is what is the basis
892
00:58:48.335 --> 00:58:55.170
of Wasabi 2 point o's name, nothing much. He actually has me blocked on Twitter, but I have a lot of respect for that dude. And,
893
00:58:55.890 --> 00:58:59.589
he has a whole thread where he's like, this is unsafe to use.
894
00:59:00.185 --> 00:59:17.520
So Oh. If the creator of the fucking protocol is saying that they implemented it poorly and that he doesn't want anyone to use it, like, that's enough for me. Here's a question. Do they use the chain analysis stuff on the normal wallet use? No, right? Yeah. My understanding is all
895
00:59:17.835 --> 00:59:24.494
oh, no. No. It's only inputs for only, but it's it's for inputs of CoinJoin rounds. So if you're going into a CoinJoin round,
896
00:59:25.170 --> 00:59:32.550
it presumably gets sent to a chain surveillance firm, and then that chain surveillance firm basically gives them the nod yes or no.
897
00:59:32.895 --> 00:59:36.595
But on top of that, the way they've implemented Wabi Sabi, supposedly,
898
00:59:38.815 --> 00:59:40.995
extra data is getting leaked to
899
00:59:41.470 --> 00:59:47.490
any to the server and presumably the chain surveillance firm they're using as well. That's very important. Together and shit.
900
00:59:47.950 --> 00:59:50.770
I I I find it hard to believe that
901
00:59:52.815 --> 00:59:54.355
that a project will have
902
00:59:54.655 --> 00:59:55.215
a long,
903
00:59:55.775 --> 00:59:56.435
a long
904
00:59:56.735 --> 01:00:00.355
install base after adding chain services. Like they're struggling.
905
01:00:01.210 --> 01:00:03.470
No. I mean, of course. But, you know,
906
01:00:03.770 --> 01:00:05.630
my view on this that, like,
907
01:00:06.090 --> 01:00:07.150
the the problem is
908
01:00:07.610 --> 01:00:08.590
any project
909
01:00:09.154 --> 01:00:10.855
that has capturable people
910
01:00:11.954 --> 01:00:15.575
that does this kind of, like, service will eventually
911
01:00:15.875 --> 01:00:19.810
be presented with 2 choices, either go to jail or, like, you know,
912
01:00:20.350 --> 01:00:21.490
talk itself. Right?
913
01:00:22.030 --> 01:00:34.225
I think it's a matter of time. Close down the fucking thing then. Exactly. No. No. That that's but then then the Wasabi is still an open source project. Anyone can run a coordinator. Close down the fucking company then if you're if you can't do it in in,
914
01:00:35.510 --> 01:00:40.490
if you can't do it in a state where they're at. Happen. Right? Maybe they will close on the company because
915
01:00:41.030 --> 01:00:42.970
it's gonna be very hard to have users,
916
01:00:43.830 --> 01:00:46.485
doing coin join if they're getting,
917
01:00:47.265 --> 01:00:48.565
being sent to chain analytics.
918
01:00:49.185 --> 01:00:50.885
Yeah. It's pretty fucked up. But, you know,
919
01:00:51.505 --> 01:00:56.560
I'm not gonna get into the whole coin mixing. It's just too much drama for my, for my,
920
01:00:57.560 --> 01:00:58.560
taste. But
921
01:01:00.140 --> 01:01:02.195
why is it that the the coin
922
01:01:02.915 --> 01:01:04.454
the the the mixing coin
923
01:01:04.835 --> 01:01:06.535
crowd is so complicated?
924
01:01:07.795 --> 01:01:09.335
It's beyond me.
925
01:01:09.875 --> 01:01:10.375
Anyways,
926
01:01:11.500 --> 01:01:15.680
any other All my favorite all my favorite projects in this space are
927
01:01:18.220 --> 01:01:19.359
a little little bit
928
01:01:19.660 --> 01:01:20.160
crazy.
929
01:01:21.245 --> 01:01:23.025
I mean, you went through your own,
930
01:01:24.765 --> 01:01:30.660
like, feels like a long time ago, but what was it? Like, a year and a half ago, 2 years ago, the hardware wallet
931
01:01:31.200 --> 01:01:33.619
chaos between all the but, you know,
932
01:01:33.920 --> 01:01:35.540
I think that was really
933
01:01:35.840 --> 01:01:37.140
the the problem is
934
01:01:38.734 --> 01:01:41.075
I think it's different. The hardware wallet market
935
01:01:41.535 --> 01:01:44.914
never really had competition for a long time, and then it had competition.
936
01:01:45.670 --> 01:01:48.970
And some players that had a certain sort of, like,
937
01:01:49.750 --> 01:01:51.210
a standing in the market
938
01:01:51.590 --> 01:01:53.210
sort of fell, dropped.
939
01:01:53.670 --> 01:01:55.130
That caused a lot of drama.
940
01:01:57.025 --> 01:02:01.445
You know you know me on Twitter. I have, you know, I I I don't wear gloves.
941
01:02:03.089 --> 01:02:03.589
And,
942
01:02:04.690 --> 01:02:18.005
yeah, but it was different. I think it was more market based, and it was sort of like this market sort of finding itself on how to relate to each other in this competition as well, and it was also whatever you need to say to yourself. Exactly. That's what I taught myself.
943
01:02:18.705 --> 01:02:24.100
And but but he but as you said, it feels like it was a lifetime ago because it was all mostly resolved.
944
01:02:24.400 --> 01:02:28.340
Right? Some players still don't talk to each other, whatever, but like but the drama
945
01:02:28.640 --> 01:02:30.020
greatly went away.
946
01:02:30.575 --> 01:02:33.474
Right? Now on the coin joint space,
947
01:02:33.935 --> 01:02:45.109
it's, like, only worst, and they managed to somehow involve everybody else too. I don't know if it's too much. This point. I think it's I think it's cleared up a bit. I mean, no one defends his hobby now. So
948
01:02:46.025 --> 01:02:48.445
No. But but it leaches to everybody.
949
01:02:49.945 --> 01:02:51.165
I mean, you know, like
950
01:02:51.865 --> 01:02:55.700
well, anyways, I won't get into it. It's not the kind of podcast for that.
951
01:02:56.320 --> 01:02:59.520
I mean, I think there's a yeah. I don't know. There's
952
01:03:00.000 --> 01:03:01.460
fair enough. We can continue.
953
01:03:03.415 --> 01:03:11.560
I'm glad we it was it was a big release. It was I think it was important to bring up Wasabi 2 point o. No. I I think, yeah, I think it's a good point. But don't use it.
954
01:03:12.280 --> 01:03:19.260
Yeah. I, I, yeah, I I didn't bring it up. I I guess it it's probably safe to use with a hardware signing device.
955
01:03:20.675 --> 01:03:30.040
Not not for mixing. If mixing is getting chain analysis, it's not safe to use. Coin the don't use it for coin join, but then also on top of that, by the way, they removed coin control,
956
01:03:30.500 --> 01:03:33.480
like so maybe it's not even good. Just use Sparrow.
957
01:03:33.860 --> 01:03:43.525
So so, Matt, what you're really saying is that, like, we're gonna have to do drinking on the show like you do in the other show, and now I understand why. See. This is what if you do it every week, you
958
01:03:44.325 --> 01:03:47.870
there's no choice. No. Yeah. So let's talk about frequency here.
959
01:03:48.410 --> 01:03:57.465
This is best effort. I you know, maybe I'll do this, like, every couple weeks maybe. Like, 3 months. Maybe a month, you know, maybe it's next year, who knows, right?
960
01:03:59.045 --> 01:04:03.840
So now let's move on to another big part of the show, which is reading
961
01:04:04.860 --> 01:04:06.080
the Bitcoin OpTech
962
01:04:07.660 --> 01:04:08.160
newsletter.
963
01:04:09.180 --> 01:04:10.800
We're just gonna glance over.
964
01:04:11.375 --> 01:04:13.395
For people that don't know, the Bitcoin Ophthak
965
01:04:13.935 --> 01:04:15.235
is an incredible,
966
01:04:16.095 --> 01:04:16.595
incredible,
967
01:04:17.855 --> 01:04:21.109
resource for what happened to that. To that. To that. To that. Dotcom.
968
01:04:22.210 --> 01:04:24.470
Sign up for the for the newsletters.
969
01:04:25.170 --> 01:04:26.390
Subscribe to their Twitter.
970
01:04:27.010 --> 01:04:28.695
It it it really is phenomenal,
971
01:04:29.715 --> 01:04:30.855
really high signal,
972
01:04:31.715 --> 01:04:32.695
to noise there.
973
01:04:34.115 --> 01:04:35.815
Mike Schmidt, I I know.
974
01:04:36.320 --> 01:04:38.340
He's one of the main contributors there.
975
01:04:38.880 --> 01:04:39.380
And,
976
01:04:40.320 --> 01:04:44.020
Yeah. Schmidt is great. Yes. So without further ado,
977
01:04:44.720 --> 01:04:45.380
the news,
978
01:04:46.605 --> 01:04:49.825
full replaced by fee. So there's been some
979
01:04:51.005 --> 01:04:53.665
some talks and there is a couple PRs to remove,
980
01:04:54.525 --> 01:04:55.025
RBF,
981
01:04:55.990 --> 01:04:58.170
which is replaced by fee from the default.
982
01:04:59.190 --> 01:04:59.850
You know,
983
01:05:01.030 --> 01:05:04.170
as a as a sane citizen of Bitcoin,
984
01:05:04.515 --> 01:05:07.655
I don't get involved in these discussions. I still believe,
985
01:05:08.355 --> 01:05:09.655
RBF should be,
986
01:05:10.435 --> 01:05:11.415
on by default
987
01:05:12.195 --> 01:05:14.055
because replace by fee
988
01:05:15.160 --> 01:05:25.275
is essentially the default behavior of bitcoin itself. You can double spend your own transaction if you want to, so might as well make it into an official standardized thing and that's why I like our b f.
989
01:05:26.695 --> 01:05:29.415
So yeah, but there is a PR that's gotten some,
990
01:05:29.895 --> 01:05:33.195
some traction and you know what, it's probably gonna get merged.
991
01:05:35.119 --> 01:05:35.619
Hearts
992
01:05:35.920 --> 01:05:38.020
hearts bleed, that was a nice pun.
993
01:05:40.000 --> 01:05:40.980
Very good pun.
994
01:05:41.865 --> 01:05:43.405
So essentially there was a vulnerability,
995
01:05:44.185 --> 01:05:48.285
on the I believe it I haven't read through it, but, just
996
01:05:48.730 --> 01:05:52.590
from the pun and from the first paragraph here, I imagine is
997
01:05:53.210 --> 01:05:53.710
a
998
01:05:54.010 --> 01:05:57.790
similar to a power artificial analysis attack. They're trying to read
999
01:05:59.174 --> 01:06:01.434
the the computation happening on the chip,
1000
01:06:02.055 --> 01:06:04.075
and then they can essentially,
1001
01:06:04.934 --> 01:06:07.115
through a side channel, like, read
1002
01:06:07.480 --> 01:06:10.140
the private key being generated or used.
1003
01:06:12.680 --> 01:06:17.100
Even on this article here it says that, they don't know the extent
1004
01:06:17.545 --> 01:06:18.444
of the vulnerability.
1005
01:06:18.984 --> 01:06:22.285
And Bitcoin Core also does a lot of things to prevent,
1006
01:06:24.505 --> 01:06:25.005
attacks,
1007
01:06:25.545 --> 01:06:27.750
side channel attacks on on its,
1008
01:06:28.549 --> 01:06:38.045
private key computation. But anyone no one should have a private key on a computer anyways. You should have it on your hardware wallet. So this attack So your hardware wallet or computer?
1009
01:06:38.985 --> 01:06:39.485
Well,
1010
01:06:40.825 --> 01:06:48.119
no. So exactly. So if your if your code card is immune to this because it's not the computer, it's not being attacked by this.
1011
01:06:48.740 --> 01:06:49.720
This is a computer.
1012
01:06:50.100 --> 01:06:51.480
The last one really is,
1013
01:06:52.500 --> 01:06:56.355
go to air what is it? I have a I have a meme website for this.
1014
01:06:56.974 --> 01:07:07.360
Ear gap. Yes. You're the only person who has a bigger domain issue than I do. Oh, good. It's it's, How much do you spend every year on them, and are you downsizing in the bear market?
1015
01:07:09.020 --> 01:07:12.045
The thing is that I'm starting to run out of ideas for domains. Anyways,
1016
01:07:12.425 --> 01:07:12.925
airgapcomputer.com
1017
01:07:14.185 --> 01:07:18.980
But have you cut have you cut the fat at all in the bear market? I've been cutting the fat a little bit.
1018
01:07:19.619 --> 01:07:33.605
Some of them in a bull market, some of the ones I registered are No. Not for the guillotine. No. I yeah. No. I think it adds up. It's like it adds up. But, you know, but, Matt, like, see, the thing is I've sold a few domains for for, like I've never I'm a Huddler.
1019
01:07:34.045 --> 01:07:39.640
For for for, like, for for for essentially what gave me free reign of domains forever,
1020
01:07:41.220 --> 01:07:45.640
in in my company. I do not have to explain my domain behavior to anyone internally,
1021
01:07:46.805 --> 01:07:52.105
because I have, paid ourselves over and over many, many times over. Was a really nice coup.
1022
01:07:53.740 --> 01:07:56.160
Yeah. I mean, that was a that was a good sail too.
1023
01:07:58.220 --> 01:08:00.080
So yeah. It was a nice little
1024
01:08:01.174 --> 01:08:02.075
pump and dump.
1025
01:08:03.095 --> 01:08:06.395
No. Well, I mean, I did offer the rest of the anyways,
1026
01:08:06.775 --> 01:08:07.595
long story.
1027
01:08:09.779 --> 01:08:18.280
So hearts bleed, it would not be an issue at all if you use a harder wallet, so stop listening to the Wookie and buy yourself a cold card.
1028
01:08:18.875 --> 01:08:22.575
Yes, I'm biased on that one because I make it and it is better.
1029
01:08:23.195 --> 01:08:23.695
So
1030
01:08:24.155 --> 01:08:24.895
use that,
1031
01:08:25.435 --> 01:08:33.480
and if you still don't believe me, go to air gap computer dot com. He explains to you why you shouldn't use an air gap computer.
1032
01:08:34.955 --> 01:08:35.615
Yeah. Go,
1033
01:08:36.235 --> 01:08:40.655
go verify MBK's claim by going to the site that MBK created.
1034
01:08:41.435 --> 01:08:41.935
Exactly.
1035
01:08:43.800 --> 01:08:45.739
What is it, trust and verify?
1036
01:08:47.239 --> 01:08:50.540
Trust and verify. That's right. Don't trust and verify guys.
1037
01:08:51.914 --> 01:09:00.710
I really hope people are not, like, taking samples of this conversation to, create and you know You're gonna take it all out of context. It's important. Yeah. Well, you know, it is I mean, I have over
1038
01:09:01.090 --> 01:09:02.790
700 hours of
1039
01:09:04.050 --> 01:09:08.135
of public Bitcoin conversation out there that is oftentimes drunk. So
1040
01:09:09.735 --> 01:09:16.235
Yeah. Well, I mean, I I be the first time. Yeah. I I have a personal policy of not doing recording while I'm inebriated.
1041
01:09:17.690 --> 01:09:19.949
Yeah. Well, you just don't do enough. That's why.
1042
01:09:20.650 --> 01:09:24.030
You if I keep on doing this podcast where I read people's
1043
01:09:24.625 --> 01:09:33.285
updates and I have to discuss the coin joint people, I'm gonna start having a serious drinking problem. Dude, people say to me, they're like, Matt, you seem, like, really tired
1044
01:09:33.730 --> 01:09:41.989
and frustrated on rabbit hole recap today. It's like, everything okay? It's like, I've been doing this for 3 fucking years. Like, sometimes I'm being frustrated and tired. Like, what do you fucking expect?
1045
01:09:43.045 --> 01:09:44.025
That's healthy.
1046
01:09:47.925 --> 01:09:52.270
Alright. So they have, there there was there was some drama about the
1047
01:09:52.650 --> 01:09:55.390
time stamping design on open time stamp.
1048
01:09:55.850 --> 01:09:57.470
I didn't really follow it.
1049
01:09:58.410 --> 01:10:00.750
I It's like a sneaky project that I love.
1050
01:10:01.315 --> 01:10:05.735
Yeah. It's a it's a fun one. It was Peter Todd who created open timestamps.
1051
01:10:07.395 --> 01:10:14.450
I recommend people go read the newsletter to get more on that. And also on the new Rito Anti Cyber method by Waxwing.
1052
01:10:15.150 --> 01:10:19.295
You know you're in a bear market when, people on Twitter are accusing Peter Todd of
1053
01:10:20.255 --> 01:10:21.315
of flooding Bitcoin.
1054
01:10:22.175 --> 01:10:28.410
Well, I mean, you know, who brings up DAO emissions for Bitcoin and does not expect to be called a spook?
1055
01:10:28.970 --> 01:10:47.315
Like, he was just asking for it. Right? No. I mean, like, you'll yeah. I mean, it's like the equivalent of a once you have a 40% dump, like, the price dumps 40%, you're gonna send out a tweet saying that we should increase the 21,000,000 cap. Like, what did you expect? And that's assuming that there is a concern. Right? There is no concern.
1056
01:10:47.630 --> 01:10:52.210
Everything is great. Bitcoin is perfect. Move on. There is no data emissions. We're not gonna accept
1057
01:10:52.510 --> 01:10:58.595
my node and never run data emissions, period. But still it's fucking Peter Todd. Like, he's not a
1058
01:10:59.455 --> 01:11:05.315
Yeah. He's not cheap fuck. But he likes he likes some controversy too. He loves bringing in some controversial topics.
1059
01:11:05.660 --> 01:11:10.960
Good on him. We we we need the controver the controversy. That's how we find problems.
1060
01:11:12.835 --> 01:11:13.335
Alright,
1061
01:11:14.515 --> 01:11:20.055
notable changes to services and client software. You know, Azus added Taproot.
1062
01:11:21.110 --> 01:11:24.329
There you go, we missed that one on our, on our list.
1063
01:11:25.429 --> 01:11:26.250
So Evan,
1064
01:11:26.630 --> 01:11:33.735
we're very sorry. I well, actually, you know what? I didn't add Zeus to the list because I think their last update was a while back. So
1065
01:11:34.195 --> 01:11:36.170
Yeah, but some of these, like, you have updates from
1066
01:11:36.470 --> 01:11:42.250
January, like, I didn't know what to do. I know. I'm not perfect. I just started this. Well, anyway, Zeus is the single best,
1067
01:11:42.845 --> 01:11:44.465
way to interact with,
1068
01:11:45.005 --> 01:11:49.300
lightning node from your phone if you have a 247 lightning node at home.
1069
01:11:49.940 --> 01:11:58.760
Yes. There's basically nothing else that competes with it And, and that I'm aware of. And Evan is doing really good work. Shout out to to Kaludis.
1070
01:11:59.495 --> 01:12:01.675
Matt's favorite wasabi Wallet 2.0.
1071
01:12:03.335 --> 01:12:04.155
Moving on,
1072
01:12:05.015 --> 01:12:07.515
Sparrow adds tab We already covered that one in line. Designing,
1073
01:12:08.270 --> 01:12:10.930
which is because of HWI got upgraded.
1074
01:12:11.310 --> 01:12:12.530
Thanks, Ciao.
1075
01:12:15.070 --> 01:12:17.090
And then release candidates for
1076
01:12:17.665 --> 01:12:21.845
LNG. Carries HWI on his back. Right? It's just him. It's just him.
1077
01:12:22.385 --> 01:12:27.680
Another one man there's a lot of one man legends. No. But, you know, but to be fair though, people do contribute,
1078
01:12:28.620 --> 01:12:29.440
to HWI.
1079
01:12:29.900 --> 01:12:31.920
Like, a lot of the hardware wallets themselves
1080
01:12:32.220 --> 01:12:33.840
have their people help
1081
01:12:35.565 --> 01:12:38.465
implement the changes to HWI for their new releases.
1082
01:12:39.165 --> 01:12:40.625
So it is collaborative,
1083
01:12:40.925 --> 01:12:44.350
but but h but, yes, Chow does carry that on his back.
1084
01:12:44.990 --> 01:12:50.370
And he is the kind of person who does test everything and review everything, right, that's why it takes a little longer.
1085
01:12:52.030 --> 01:12:55.075
Alright, so on the lightning front, of course every,
1086
01:12:56.095 --> 01:12:56.595
the
1087
01:12:57.135 --> 01:12:58.835
3 of the 4 main releases
1088
01:13:00.175 --> 01:13:00.925
of of,
1089
01:13:01.430 --> 01:13:02.810
oh no, sorry. LND
1090
01:13:03.190 --> 01:13:04.330
had a main release.
1091
01:13:06.150 --> 01:13:08.090
LDK had another main release.
1092
01:13:12.885 --> 01:13:13.445
BDK has,
1093
01:13:14.085 --> 01:13:21.180
experimental support for Taproot, descriptors, p s p t. BDK is a very cool project. It does help a lot of devs
1094
01:13:21.800 --> 01:13:24.940
implement a wallet without knowing how to implement a wallet,
1095
01:13:25.480 --> 01:13:27.180
so very bullish on the library.
1096
01:13:27.545 --> 01:13:31.804
Yeah. I mean, BDK is super promising. It's just Yes. Not really there yet. Right?
1097
01:13:32.425 --> 01:13:50.565
Yeah. Well, I mean, writing a wallet is a lot of work, and these guys are doing that with a lot of features at the same time, which is just exponentially harder. But basically, the idea of BDK is, like, it's the base. It could be the base for any new wallet. Right? And then, like, people can build on top of it and and make whatever changes they wanna make, but they don't have to, like,
1098
01:13:51.140 --> 01:14:07.070
they don't have to build from scratch the core logic. Right? Yeah. But none of this stuff is plug and play. Right? You still have to there's a lot of of glue and a lot of stuff you need to write. Supposed to make it easier at least. It does. And then the idea is that that'll bring more competition among wallets and we'll have better wallets and everyone will win.
1099
01:14:07.790 --> 01:14:09.570
Yeah. And it's fun, dude.
1100
01:14:10.670 --> 01:14:12.290
By Block, formerly Square.
1101
01:14:13.150 --> 01:14:17.265
Yes. And so is LDK, right? LDK, which is the same idea
1102
01:14:17.805 --> 01:14:19.745
but but but What about Lightning Core?
1103
01:14:21.485 --> 01:14:24.225
That was an unfortunate choice of name. Core Lightning.
1104
01:14:24.590 --> 01:14:25.090
Unfortunate.
1105
01:14:25.470 --> 01:14:27.650
I I preferred the one with sea lightning,
1106
01:14:29.230 --> 01:14:41.945
because it's written in c. But no. I guess part of the reason is because they're they've been doing more that's not written in c. Oh, I see. The real reason is because they're pissed off at lnd for branding itself as Lightning.
1107
01:14:42.730 --> 01:14:52.455
So they shot back at them. Yeah. I mean, it's kinda like remember blockchain dot info, which was blockchain and, you know, everybody went to blockchain. Yeah. Don't use that site either if you're listening. Exactly.
1108
01:14:53.795 --> 01:14:59.335
I don't think people who listen to a podcast about Bitcoin software updates, would have to be warned about Blockchain.info.
1109
01:14:59.795 --> 01:15:07.810
They get, like, they get an hour and 15 minutes into this fucking rip, and they're like, oh, wow. They mentioned blockchain.info. I'm gonna go check out that wallet. Right. Exactly.
1110
01:15:08.750 --> 01:15:10.370
They survived this long.
1111
01:15:10.905 --> 01:15:11.405
They
1112
01:15:12.264 --> 01:15:17.145
gotta cover it. You gotta cover it just in case. Notable code and documentation changes,
1113
01:15:18.340 --> 01:15:18.500
this week,
1114
01:15:19.220 --> 01:15:21.160
well, in their week, not my week.
1115
01:15:22.100 --> 01:15:24.600
Bitcoin Core, Core Lightning, essentially all the projects.
1116
01:15:24.980 --> 01:15:25.720
And then,
1117
01:15:29.765 --> 01:15:36.320
oh, h w I yeah. H w I, edit the single sig support for back 32 m addresses,
1118
01:15:37.500 --> 01:15:39.280
which helps it tap root.
1119
01:15:39.740 --> 01:15:40.240
Okay.
1120
01:15:41.180 --> 01:15:41.680
Alright.
1121
01:15:42.060 --> 01:15:42.560
Now
1122
01:15:45.625 --> 01:15:48.285
I have a few more things here on the list.
1123
01:15:49.945 --> 01:15:56.760
So next would be, which I did it in the wrong order. There's Blix Wallet. We didn't cover Blix Wallet.
1124
01:15:58.420 --> 01:15:59.960
Blix what? Pretty dope. Blixt
1125
01:16:00.659 --> 01:16:02.855
lightning wallet. Don't know that one.
1126
01:16:04.275 --> 01:16:05.574
You go for it. Android
1127
01:16:05.954 --> 01:16:06.775
and iPhone.
1128
01:16:07.474 --> 01:16:07.974
Okay.
1129
01:16:08.514 --> 01:16:09.815
So it's really cool. Wallet.
1130
01:16:10.560 --> 01:16:15.940
Okay. I'll I'll check that. Well, how do you spell it? Be the what? B l I x t.
1131
01:16:16.320 --> 01:16:20.545
B l I x t. Okay. I wouldn't be surprised if they add NFC.
1132
01:16:21.565 --> 01:16:28.065
It looks like they have it on their road map, but it's not on it yet. Yeah. B l I x t
1133
01:16:28.440 --> 01:16:28.940
Wallet.
1134
01:16:30.360 --> 01:16:32.060
Okay. I'll check that one out.
1135
01:16:32.360 --> 01:16:33.980
It's a pretty powerful wallet.
1136
01:16:34.680 --> 01:16:35.900
Mercury Wallet.
1137
01:16:36.315 --> 01:16:38.735
There's been some good updates to Mercury Wallet.
1138
01:16:39.675 --> 01:16:42.335
The last Splixd Wallet update was on
1139
01:16:44.210 --> 01:16:45.270
March 4th,
1140
01:16:46.450 --> 01:16:47.510
v 0.5.1.
1141
01:16:49.730 --> 01:16:53.055
Alright. And then Mercury Wallet has been I've seen a lot of options
1142
01:16:53.515 --> 01:16:55.935
in the Wallet. Who's who's got That's the
1143
01:16:56.235 --> 01:16:58.095
that's the state chain
1144
01:17:00.150 --> 01:17:00.650
swaps
1145
01:17:01.349 --> 01:17:01.849
wallet.
1146
01:17:02.469 --> 01:17:04.650
It does coin swaps on a state chain.
1147
01:17:05.670 --> 01:17:16.075
It's a privacy focused wallet that uses Okay. Uses a a state chain implementation that's, like, not as good as, I guess what was it Thompson who came up with the original state chains
1148
01:17:16.830 --> 01:17:17.330
proposal?
1149
01:17:18.350 --> 01:17:26.784
Nah, I can't remember. Whoever came up with the original one, it required some kind of protocol change, so they figured out a way to do, like, a slightly less good version
1150
01:17:27.485 --> 01:17:29.425
without any kind of protocol change.
1151
01:17:29.804 --> 01:17:32.385
And you basically switch into their state chain,
1152
01:17:33.610 --> 01:17:37.869
which has reduced custodial risk. But if they're the other counterparty, like, if they're malicious,
1153
01:17:39.050 --> 01:17:42.030
then they could take your money, but if they're not, it requires
1154
01:17:42.635 --> 01:17:43.455
them plus
1155
01:17:43.915 --> 01:17:53.190
one of the participants to collude together to take your money. That's pretty good. But as a result a decent set of trade off? Yeah. As a result, it's off chain, and then you can do all these swaps,
1156
01:17:53.970 --> 01:17:54.870
to gain privacy
1157
01:17:55.250 --> 01:17:59.725
without paying transaction fees, and then you withdraw back to the chain.
1158
01:18:00.105 --> 01:18:00.605
Nice.
1159
01:18:02.345 --> 01:18:03.005
Cool project.
1160
01:18:03.385 --> 01:18:05.565
Yeah. And they've been making a lot of
1161
01:18:06.619 --> 01:18:08.000
lot of progress lately.
1162
01:18:08.540 --> 01:18:10.320
Do do you like privacy, Matt?
1163
01:18:11.099 --> 01:18:14.239
No. Not really. You don't so you don't have anything to hide?
1164
01:18:14.755 --> 01:18:15.735
No. I appreciate
1165
01:18:17.554 --> 01:18:18.375
fuck you.
1166
01:18:19.074 --> 01:18:27.590
Okay. Privacy is one of the most important topics in in Bitcoin today, and hopefully It's a great segue. Good to see so many tools
1167
01:18:27.969 --> 01:18:30.135
coming out that are focused on it.
1168
01:18:30.534 --> 01:18:35.434
Okay. So that's a great segue to, Taproot adoption on the Bitcoin Wiki.
1169
01:18:36.775 --> 01:18:38.235
It's not really a segue.
1170
01:18:40.450 --> 01:18:40.950
Okay.
1171
01:18:41.410 --> 01:18:41.910
So,
1172
01:18:42.770 --> 01:18:43.270
apparently,
1173
01:18:43.730 --> 01:18:45.270
armory is planning,
1174
01:18:47.195 --> 01:18:49.015
is planning Taproot.
1175
01:18:49.555 --> 01:18:55.495
The armory? I know. I'm just amazed. I just I haven't heard that wall in years. I know.
1176
01:18:56.820 --> 01:18:59.880
Anyways, so I don't think anyone should use armory
1177
01:19:00.340 --> 01:19:00.840
anymore.
1178
01:19:03.219 --> 01:19:07.235
Aqua, which is green, let's see here. Who who implemented
1179
01:19:07.855 --> 01:19:08.675
send to
1180
01:19:09.054 --> 01:19:12.675
to Taproot? Is that B coin, Bitcoin Core, Bitcoin Knots,
1181
01:19:14.014 --> 01:19:15.155
Blockstream Green,
1182
01:19:17.320 --> 01:19:18.860
Bitcoin wallet for Android,
1183
01:19:19.240 --> 01:19:20.060
Blue Wallet,
1184
01:19:21.320 --> 01:19:23.500
Breeze didn't and it won't,
1185
01:19:24.225 --> 01:19:24.725
says
1186
01:19:26.465 --> 01:19:27.205
no. Btc.com
1187
01:19:27.825 --> 01:19:28.725
question mark.
1188
01:19:29.905 --> 01:19:30.405
Caravan
1189
01:19:30.840 --> 01:19:34.460
plan. Caravan is from Unchained Capital. Casa plan,
1190
01:19:36.119 --> 01:19:36.940
Sea Lightning,
1191
01:19:38.574 --> 01:19:39.074
yes.
1192
01:19:40.015 --> 01:19:40.515
Coinomi
1193
01:19:41.135 --> 01:19:43.635
Core lightning, you mean? No. Coin nami.
1194
01:19:44.255 --> 01:19:46.675
No. Before that, you said sea lightning. It's core lightning.
1195
01:19:47.510 --> 01:19:50.090
Right now, but it's it's written as sea lightning here.
1196
01:19:50.630 --> 01:19:53.290
Okay. But sea lightning doesn't approve. I refuse. I
1197
01:19:54.310 --> 01:19:56.570
will call it sea lightning to the day I die.
1198
01:19:57.545 --> 01:19:58.605
Okay. Electrum,
1199
01:19:59.945 --> 01:20:00.605
yes. Exodus,
1200
01:20:01.304 --> 01:20:02.925
yes. Fully noted, yes.
1201
01:20:03.945 --> 01:20:05.005
Guarda wallet,
1202
01:20:05.385 --> 01:20:06.284
question mark.
1203
01:20:06.989 --> 01:20:08.770
Joy Market, yes. LND,
1204
01:20:09.150 --> 01:20:09.650
Cumming.
1205
01:20:10.270 --> 01:20:11.330
Mun, yes.
1206
01:20:11.790 --> 01:20:15.585
It's Moon. I always say Mun. I don't know why. Moon with 2 u's. Yes.
1207
01:20:16.145 --> 01:20:19.045
Mycelium question mark. Nunchuck, yes.
1208
01:20:19.425 --> 01:20:20.805
Phoenix question mark.
1209
01:20:21.265 --> 01:20:21.765
Samurai,
1210
01:20:22.145 --> 01:20:22.645
yes.
1211
01:20:23.440 --> 01:20:23.940
Sparrow,
1212
01:20:24.320 --> 01:20:24.820
yes.
1213
01:20:25.120 --> 01:20:27.700
Specter, yes. Trust wallet, yes.
1214
01:20:28.560 --> 01:20:32.985
Uniblo, never heard of that, yes. Wallets of satoshi, yes.
1215
01:20:33.365 --> 01:20:34.825
Wasabi wallet, yes.
1216
01:20:36.085 --> 01:20:38.025
Hardware wallet support is a little trickier,
1217
01:20:38.900 --> 01:20:41.239
but it's essentially just signing to the address.
1218
01:20:41.699 --> 01:20:42.199
So,
1219
01:20:42.659 --> 01:20:47.239
Trezor, yes. Ledger, yes. Keep key, don't use it, and it doesn't.
1220
01:20:48.085 --> 01:20:49.864
Bitbox, yes. Trezor
1221
01:20:50.245 --> 01:20:51.465
with Electrom, yes.
1222
01:20:53.205 --> 01:20:56.105
Bitbox, yes. Keep key, question mark.
1223
01:20:56.880 --> 01:20:59.460
Arcos, question mark. Code card, yes.
1224
01:21:00.239 --> 01:21:01.540
Wallet, question mark.
1225
01:21:03.040 --> 01:21:04.340
Seed signer plan,
1226
01:21:05.994 --> 01:21:06.494
tangent
1227
01:21:07.114 --> 01:21:08.014
question mark,
1228
01:21:09.675 --> 01:21:10.574
block stream,
1229
01:21:10.954 --> 01:21:11.454
yes,
1230
01:21:12.074 --> 01:21:13.534
and keystone plan
1231
01:21:14.370 --> 01:21:15.110
for q122
1232
01:21:16.050 --> 01:21:16.550
so
1233
01:21:17.490 --> 01:21:18.870
I guess it didn't happen.
1234
01:21:21.010 --> 01:21:21.830
Web wallets,
1235
01:21:22.635 --> 01:21:23.135
coinapult,
1236
01:21:23.675 --> 01:21:26.895
question mark, coin dot space slash Are you just reading, taproot support?
1237
01:21:27.355 --> 01:21:28.975
Yes. Okay. Continue.
1238
01:21:29.810 --> 01:21:32.550
BitGo, yes. Bitnob, yes.
1239
01:21:33.170 --> 01:21:36.230
Blockchain dotcom, planned. That's weird.
1240
01:21:36.925 --> 01:21:38.045
They just did,
1241
01:21:38.605 --> 01:21:45.140
hierarchical deterministic like the other day. They never did business. They did that segue like a couple months ago. Something like that too.
1242
01:21:46.100 --> 01:21:48.840
Fireblocks planned. Fireblocks is a big deal,
1243
01:21:49.460 --> 01:21:56.955
because they are the back end of a lot of the exchanges. So if you want to send from an exchange to a top root address, you they would probably need to support that.
1244
01:21:57.895 --> 01:22:05.110
Yeah. Fireblock is actually like a massive centralization risk that very few people ever talk about. Yeah. Yeah. But it's certified, Matt.
1245
01:22:05.730 --> 01:22:07.430
It's certified. It's certified.
1246
01:22:08.290 --> 01:22:09.910
Hold the transactions, yes.
1247
01:22:10.825 --> 01:22:11.325
Coinb.
1248
01:22:12.105 --> 01:22:12.605
In,
1249
01:22:13.145 --> 01:22:15.325
question mark or the question mark.
1250
01:22:16.425 --> 01:22:17.805
Do I go through the exchanges?
1251
01:22:18.425 --> 01:22:18.925
Nah,
1252
01:22:20.030 --> 01:22:20.930
Bitcoin ATM,
1253
01:22:21.470 --> 01:22:23.330
nah. Blockchain Explorers.
1254
01:22:24.670 --> 01:22:26.210
Do you use Taproot yet?
1255
01:22:28.405 --> 01:22:31.145
What me? No. I won't use Taproot for a long time.
1256
01:22:31.844 --> 01:22:36.470
Okay. Don't use anything that's mute. Our store Why am I reading this? Coinkite.com
1257
01:22:37.330 --> 01:22:39.670
still uses one addresses, legacy addresses.
1258
01:22:40.050 --> 01:22:42.470
I feel like this is a good time to remind people that,
1259
01:22:44.105 --> 01:22:50.605
like, that's on the receiver. Like, there's no I guess, except for privacy reasons, there's no reason to to
1260
01:22:51.330 --> 01:22:56.150
to, be upset if a merchant or a person is using an old address
1261
01:22:56.450 --> 01:23:02.545
because the fee savings are dependent on this the fee savings are dependent on the sender, not the receiver. So That's right.
1262
01:23:03.005 --> 01:23:09.080
Well, for a while, we were getting a little bit of hate because people didn't understand that, so we had to I know. That's why I'm repeating it. I'm
1263
01:23:10.180 --> 01:23:10.920
well aware.
1264
01:23:12.980 --> 01:23:13.880
Right, alright.
1265
01:23:15.140 --> 01:23:16.760
Going to the next topic,
1266
01:23:17.495 --> 01:23:18.955
Bitcoin signing devices.
1267
01:23:20.935 --> 01:23:21.435
So
1268
01:23:21.815 --> 01:23:23.355
we started this little initiative,
1269
01:23:23.975 --> 01:23:31.240
that many people have sort of like pushed here and there, but I figured it needed a domain, right? You need to buy domains otherwise things don't exist.
1270
01:23:31.860 --> 01:23:33.080
So sign in device.com
1271
01:23:35.114 --> 01:23:39.054
And the biggest problem is harder wallets or not Did you have to buy that on,
1272
01:23:39.355 --> 01:23:43.054
like you bought that from a previous owner, right? No. No. It was available.
1273
01:23:43.520 --> 01:23:51.780
It was just available for like the usual like dotcom price? Yeah. You just bought it? Yeah. Well, really my price cost. Like I get it for cheaper.
1274
01:23:52.445 --> 01:23:55.265
That's crazy signing device.com was available.
1275
01:23:55.645 --> 01:23:56.145
Yeah.
1276
01:23:57.325 --> 01:23:57.825
Kudos.
1277
01:23:58.365 --> 01:24:00.705
Yeah. So so we made a little website.
1278
01:24:02.070 --> 01:24:02.890
Hardware wallets
1279
01:24:03.350 --> 01:24:04.330
are not wallets,
1280
01:24:04.790 --> 01:24:05.930
they're signing devices.
1281
01:24:06.630 --> 01:24:08.730
Wallets have UTXO information,
1282
01:24:09.030 --> 01:24:10.410
block data information,
1283
01:24:10.875 --> 01:24:14.735
they can construct transactions. Hardware wallets don't know anything, they just sign
1284
01:24:15.195 --> 01:24:15.695
transactions.
1285
01:24:16.155 --> 01:24:17.775
While some do better than others,
1286
01:24:18.315 --> 01:24:18.815
but
1287
01:24:20.180 --> 01:24:28.600
essentially they cannot construct a transaction because they don't have blockchain data. So that's why the p s b t comes from the software wallet to your bitcoin signing device.
1288
01:24:29.835 --> 01:24:33.934
So the more people we can get on the train of calling bitcoin harder wallets
1289
01:24:34.635 --> 01:24:40.000
bitcoin signing devices, the better its gonna be for the round on the next bitcoin hype cycle.
1290
01:24:41.260 --> 01:24:44.480
Because right now it's just us left here, right, that bitcoin crashed.
1291
01:24:44.940 --> 01:24:45.440
So
1292
01:24:46.695 --> 01:24:47.195
there's
1293
01:24:47.575 --> 01:24:49.675
probably nobody that cares about this
1294
01:24:50.135 --> 01:24:51.515
around for now.
1295
01:24:52.135 --> 01:24:55.640
Sorry, nobody that doesn't care about this is around for now,
1296
01:24:56.980 --> 01:24:57.380
but,
1297
01:24:58.260 --> 01:25:03.665
yeah, on the next cycle let's try to get people saying sign in devices and move on from this. We have
1298
01:25:04.284 --> 01:25:12.930
gone through the trouble of going on the cold card website and adding sign in devices everywhere on the text to start properly confusing people with the new term.
1299
01:25:15.150 --> 01:25:16.850
Next here, one more domain,
1300
01:25:18.135 --> 01:25:18.635
bitcoinbinary.org.
1301
01:25:20.615 --> 01:25:24.795
I wanted to give a little update on this one. It's a child project of mine.
1302
01:25:26.449 --> 01:25:28.550
So I went to like a website
1303
01:25:29.010 --> 01:25:29.510
where
1304
01:25:29.969 --> 01:25:35.349
notable members of the community that can code and can build projects from source code
1305
01:25:35.795 --> 01:25:37.575
would post a video of them
1306
01:25:38.115 --> 01:25:40.935
doing the deterministic build. Right?
1307
01:25:41.395 --> 01:25:43.415
Proving on video that they did it.
1308
01:25:44.660 --> 01:25:48.280
So that people that can't have one more source of truth.
1309
01:25:49.140 --> 01:25:53.515
Is it better than them themselves building? Of course not, but it's one more source
1310
01:25:54.555 --> 01:25:55.055
truth.
1311
01:25:55.755 --> 01:25:57.375
And we had a bounty
1312
01:25:58.075 --> 01:26:00.095
for somebody to automate builds,
1313
01:26:01.800 --> 01:26:02.300
and,
1314
01:26:03.080 --> 01:26:05.100
and sort of like we can get around
1315
01:26:05.560 --> 01:26:07.820
of builds, to at least task if they build,
1316
01:26:09.175 --> 01:26:10.375
automatically, and,
1317
01:26:11.015 --> 01:26:23.640
I forgot the name of the of the person, the NIM who did it, but, he claimed the bounty, and now when there's new versions we can get the website to build it with a little video showing that it was built,
1318
01:26:24.980 --> 01:26:29.785
on top of community members to do it. And it's such a simple little thing
1319
01:26:30.565 --> 01:26:33.145
that that exponentially improves their security,
1320
01:26:34.005 --> 01:26:36.505
that, I don't know, it just felt like it needed to exist.
1321
01:26:38.710 --> 01:26:39.850
Love it. Great initiative.
1322
01:26:41.110 --> 01:26:41.610
Yeah.
1323
01:26:41.989 --> 01:26:46.090
If only they would mention that the other podcast that does
1324
01:26:46.655 --> 01:26:47.395
the releases?
1325
01:26:48.575 --> 01:26:51.875
I've definitely mentioned it in the past on Radical Recap.
1326
01:26:54.150 --> 01:26:54.650
Alright.
1327
01:26:55.110 --> 01:26:55.429
So,
1328
01:26:55.989 --> 01:27:01.610
the only mention about price which is not gonna be mentioned about price is an update on BitcoinTreasuries
1329
01:27:02.150 --> 01:27:02.650
dotnet.
1330
01:27:05.595 --> 01:27:08.335
Essentially, the miners all dumped half their coins.
1331
01:27:10.770 --> 01:27:15.190
The the big publicly traded miners, so, so that was reflected on bitcointreasuries.net.
1332
01:27:17.090 --> 01:27:19.830
And mister Saylor has not added more publicly
1333
01:27:22.065 --> 01:27:25.844
to his huddle. So, so we have a lot of entries but they've been pretty much not updated.
1334
01:27:28.640 --> 01:27:31.700
And I think probably Celsius went to 0, so
1335
01:27:32.400 --> 01:27:33.300
there you go.
1336
01:27:35.645 --> 01:27:39.825
Lastly, which I should have got at Probably safe to put Celsius at 0 now.
1337
01:27:41.085 --> 01:27:42.465
No. It's actually minus.
1338
01:27:43.485 --> 01:27:44.305
But yeah.
1339
01:27:45.050 --> 01:27:45.870
Okay. Lastly,
1340
01:27:46.250 --> 01:27:50.910
which I was going to do earlier, but I'll do it now some of the Quaintite updates.
1341
01:27:52.035 --> 01:27:55.415
We have one more product on the on the cards line
1342
01:27:55.875 --> 01:28:02.520
that we haven't talked much about it because we just sort of invented, and then we sort of went through the trouble of getting it out.
1343
01:28:03.220 --> 01:28:04.680
It's called the Sats chip,
1344
01:28:05.860 --> 01:28:06.840
and it's essentially
1345
01:28:08.020 --> 01:28:09.505
a a real NFT,
1346
01:28:10.845 --> 01:28:12.465
the way it was supposed to be.
1347
01:28:13.565 --> 01:28:17.345
It's a way for you to add a chip to a piece of art
1348
01:28:18.420 --> 01:28:18.920
signed
1349
01:28:19.780 --> 01:28:21.080
with Bitcoin Signature,
1350
01:28:24.020 --> 01:28:28.645
and uses sort of like the OpenDive model so you can't really take the privacy of it. Is it a Poincare product?
1351
01:28:29.025 --> 01:28:32.804
Yeah. It's essentially based on the Sats card and the TapCigner.
1352
01:28:33.505 --> 01:28:34.610
And also, I mean, I've just
1353
01:28:35.330 --> 01:28:50.695
seen a lot of artists basically embed OpenTime, so I guess there's a purpose for that. Yeah. Good point. I forgot that. And that's pretty much the reason why we did it is because we didn't want artists to be sort of sticking the Open Dime in the art in ways that may harm the the art or the Open Dime.
1354
01:28:51.160 --> 01:28:55.179
So we wanted to find a a more a better way of doing that.
1355
01:28:55.640 --> 01:28:56.140
And
1356
01:28:57.239 --> 01:28:58.060
we leveraged
1357
01:28:58.875 --> 01:29:01.375
all the firmware that we wrote for TapSigner
1358
01:29:01.915 --> 01:29:04.494
in a way that works for the artists so that,
1359
01:29:04.875 --> 01:29:09.600
essentially, they can they can sign a picture of the art and all the metadata
1360
01:29:10.460 --> 01:29:11.840
and it's a Bitcoin signature,
1361
01:29:12.140 --> 01:29:13.040
it's really cool.
1362
01:29:14.425 --> 01:29:16.125
And there's even a little,
1363
01:29:16.505 --> 01:29:18.685
we released a little command line tool today
1364
01:29:19.545 --> 01:29:21.405
so that they can do that, and
1365
01:29:21.705 --> 01:29:23.005
then there's a little gallery
1366
01:29:23.330 --> 01:29:24.550
on, satschip.com/gallery
1367
01:29:26.449 --> 01:29:27.750
where they can push it.
1368
01:29:29.090 --> 01:29:33.275
I hope to get a few of these on Crypto Graffiti's hands soon and
1369
01:29:34.695 --> 01:29:36.635
and get, get that ball rolling.
1370
01:29:37.895 --> 01:29:39.755
I would just say that
1371
01:29:42.160 --> 01:29:42.820
the NFT
1372
01:29:43.280 --> 01:29:44.260
craze was
1373
01:29:45.520 --> 01:29:50.635
horrible to see, but the, like, the actual physical Bitcoin art is really, really cool.
1374
01:29:51.415 --> 01:29:53.114
It is really cool. I I mean,
1375
01:29:53.495 --> 01:29:54.155
you know,
1376
01:29:54.900 --> 01:29:59.080
this is the difference, right, between buying a JPEG that anyone can copy,
1377
01:29:59.540 --> 01:30:03.075
right, and buying a physical piece of art with a certificate
1378
01:30:03.695 --> 01:30:08.915
that nobody can forge. Exactly. Like, I still don't think I'm at the point in my life where I would buy,
1379
01:30:09.390 --> 01:30:12.130
like, I I don't think the physical art is gonna outperform Bitcoin.
1380
01:30:12.510 --> 01:30:15.730
Of course not. To look at. We don't buy it. It's a cool concept.
1381
01:30:16.325 --> 01:30:20.985
Bitcoins Bitcoiners don't buy art as a store of value. You buy it because you like the art.
1382
01:30:21.925 --> 01:30:31.620
You know? You buy Bitcoin as a art guy. Kinda think that I do think that, like, the rise of Bitcoin could be very good for independent artists. Well, I think it's great. Just launched Bitcoin Park,
1383
01:30:32.375 --> 01:30:34.954
in Nashville, and we have all the walls are,
1384
01:30:36.695 --> 01:30:37.835
are Bitcoin artists,
1385
01:30:38.215 --> 01:30:49.540
and they're available for purchase. Like, we'd we're basically acting as, like, an art gallery. We don't actually own them. You know, Crypto Graffiti was very generous in, in, working with us on the first Satskar
1386
01:30:50.455 --> 01:30:55.835
art, without any sort of, like, sort of, working out how we were gonna make it happen.
1387
01:30:56.455 --> 01:30:59.120
And, we're very, very grateful to him for that.
1388
01:30:59.760 --> 01:31:02.100
And He's just a great dude in general. Yep.
1389
01:31:02.560 --> 01:31:05.300
We we think that, you know, if we can
1390
01:31:05.680 --> 01:31:09.585
make Bitcoin products full of, like, cool independent art, then we
1391
01:31:10.125 --> 01:31:11.425
we are better for that.
1392
01:31:13.645 --> 01:31:15.585
Alright. What else is on my list here?
1393
01:31:16.440 --> 01:31:19.020
The the fully noted NFC beta I mentioned.
1394
01:31:19.880 --> 01:31:20.380
Oh,
1395
01:31:20.680 --> 01:31:25.100
this is coming to cold card. People have asked. We think it's awesome.
1396
01:31:25.805 --> 01:31:26.705
It's a BIP85
1397
01:31:27.405 --> 01:31:28.465
based passwords.
1398
01:31:29.725 --> 01:31:31.665
So we do the BIP85
1399
01:31:32.045 --> 01:31:36.179
seeds now, right, so you can use it to populate your your
1400
01:31:37.280 --> 01:31:42.420
phone app with, with a seed that's terminalistically built so you only have one backup.
1401
01:31:42.925 --> 01:31:44.945
But you're gonna be able to also generate passwords,
1402
01:31:45.804 --> 01:31:48.465
for things, and we're gonna emulate a keyboard
1403
01:31:48.925 --> 01:31:50.145
for input. So,
1404
01:31:50.525 --> 01:31:52.145
if you have your non
1405
01:31:53.030 --> 01:31:56.810
deep cold storage cold card, your just play cold card, your second one,
1406
01:31:57.750 --> 01:32:01.050
you can plug it in and press a button and it will inject
1407
01:32:01.425 --> 01:32:01.925
the
1408
01:32:02.625 --> 01:32:05.925
pip85 password into an input box on the computer.
1409
01:32:07.184 --> 01:32:09.445
That's pretty awesome for
1410
01:32:10.630 --> 01:32:11.370
things like,
1411
01:32:12.070 --> 01:32:13.770
SSH protected keys,
1412
01:32:15.190 --> 01:32:21.385
or, like, you know, big interesting things, like things that you don't care. Sorry. Things that you care about the security,
1413
01:32:21.765 --> 01:32:26.585
not like things that the the service on the other side already has a copy anyways. Right?
1414
01:32:28.750 --> 01:32:31.170
So, yeah, so pretty excited about that one.
1415
01:32:32.830 --> 01:32:36.130
What else? The block clock micro reservation started.
1416
01:32:36.909 --> 01:32:38.290
This is a little
1417
01:32:38.895 --> 01:32:41.475
a bleep version of the block clock
1418
01:32:42.015 --> 01:32:42.515
mini,
1419
01:32:45.295 --> 01:32:47.565
and it's gonna be a $150
1420
01:32:49.520 --> 01:32:53.700
and same functionality, but just tiny little screen. It's very, very cute.
1421
01:32:54.720 --> 01:32:56.020
When does that come out?
1422
01:32:56.655 --> 01:32:58.195
I don't have dates yet.
1423
01:32:58.655 --> 01:33:00.355
I will commit to dates
1424
01:33:01.215 --> 01:33:08.270
once we finalize the front board because we we have it. Right? Like, it works. It's all good, and the firmware is pretty much done.
1425
01:33:09.210 --> 01:33:12.190
The thing is we're still playing with the front plate design,
1426
01:33:14.625 --> 01:33:18.165
and, you know, the world that it is just takes a little longer to do the rounds
1427
01:33:18.545 --> 01:33:21.845
of of iteration with the the PCB makers.
1428
01:33:22.950 --> 01:33:23.450
So
1429
01:33:24.150 --> 01:33:30.895
I just don't wanna promise dates and not keep them. So as soon as I have a better sense of the date, then we'll we'll say it.
1430
01:33:31.935 --> 01:33:37.475
They they we got a lot of reservations. People really like that idea, so pretty excited about it.
1431
01:33:39.110 --> 01:33:40.090
Yeah. It's definitely
1432
01:33:41.590 --> 01:33:46.330
people have just wanted a cheaper block clock for a while. I mean, just because the block clock's fucking awesome.
1433
01:33:46.685 --> 01:33:52.385
Yeah. I mean, it's a big way of thinking about it. Realize, like, the block clock mini, which is, like, the famous one now
1434
01:33:53.085 --> 01:33:57.800
because, like, Dorsey and, like, the ex Thai prime minister and shit have it in their background.
1435
01:33:58.659 --> 01:33:59.639
I should probably congratulations
1436
01:34:00.020 --> 01:34:00.679
on that.
1437
01:34:01.139 --> 01:34:23.340
That was pretty cool. The Thai the Thai dick that's he wasn't I don't think he was a dictator. I don't know. But the Thai president who got, thrown out, was on an interview, and he had the Block Lock Mini behind. But that was born out of the original Block Lock was ridiculously expensive. Right? What was it? Like, 6 k or something? It was essentially a Bitcoin. It was 5 grand when Bitcoin was 5 grand. Yeah.
1438
01:34:24.475 --> 01:34:37.200
Well, you know, but that one had it was it costed a lot to make. So we So is this part of the show just a big CoinKite ad just to end it? Is that what's going on right now? Well, don't worry. We're gonna get to you. Are you gonna send me a payment? To your shills.
1439
01:34:38.860 --> 01:34:40.320
I I just I
1440
01:34:40.835 --> 01:34:48.295
I I make sure to embed the shills throughout the show. Yeah. I noticed that. See, I am a little bit more honest. I have a point guide update section.
1441
01:34:49.555 --> 01:34:50.455
There you go.
1442
01:34:52.340 --> 01:34:55.080
So BTC sessions okay. Now this is notable.
1443
01:34:56.020 --> 01:34:59.720
The man spent 2 hours it's a essentially feature length
1444
01:35:00.095 --> 01:35:01.555
tutorial of cold card.
1445
01:35:02.975 --> 01:35:04.995
I mean it's seriously awesome,
1446
01:35:05.775 --> 01:35:09.900
that that tutorial was pretty cool. I feel like he deserves a shout out for that.
1447
01:35:11.320 --> 01:35:15.100
And we do have the coin kite stable coin now, which is the gift cards.
1448
01:35:16.725 --> 01:35:18.585
I think this is it on my list.
1449
01:35:19.525 --> 01:35:21.865
Matt, do you have anything to shield?
1450
01:35:23.500 --> 01:35:24.000
Nope.
1451
01:35:24.300 --> 01:35:26.160
It's been a pleasure. This is
1452
01:35:26.460 --> 01:35:27.440
a fun rep.
1453
01:35:27.980 --> 01:35:30.615
No. Come on. Give some details. I'll go to Bitcoin Park.
1454
01:35:31.655 --> 01:35:42.620
Oh, I mean, I can't wait for you to come down and check out Bitcoin Park. It's gonna be fucking dope. Yes. I mean, it is it's already dope, but it's getting doper every day. We're on, like, day 14 of it.
NOTE
Transcription provided by Podhome.fm
Created: 3/17/2024 4:24:58 PM
Duration: 6000.666
Channels: 1
1
00:00:02.000 --> 00:00:02.500
2
00:00:02.879 --> 00:00:03.379
Yeah.
3
00:00:04.000 --> 00:00:04.500
So
4
00:00:07.359 --> 00:00:07.859
5
00:00:08.565 --> 00:00:09.065
6
00:00:10.165 --> 00:00:14.424
It's like a big empty canvas out there, isn't it, Matt? So okay.
7
00:00:14.725 --> 00:00:17.550
So hello, and welcome to the Bitcoin review.
8
00:00:18.170 --> 00:00:28.085
Bitcoin dot review. Fuck. Let's start again. Don't start again. We're good. We're good. Fine. Alright. Hello and welcome to the Bitcoin Dot Review because that's the domain. Get it?
9
00:00:28.465 --> 00:00:28.965
So
10
00:00:29.345 --> 00:00:31.525
I started scratching my own itch with this.
11
00:00:32.490 --> 00:00:37.230
It's a best efforts sort of place to talk about Bitcoin projects and software updates.
12
00:00:39.050 --> 00:00:40.510
And we did so we stopped
13
00:00:41.235 --> 00:00:41.735
14
00:00:42.195 --> 00:00:53.800
15
00:00:55.220 --> 00:00:55.720
covering
16
00:00:56.635 --> 00:00:58.415
or or meeting that need.
17
00:00:59.035 --> 00:01:01.295
So then I have to go and do it myself.
18
00:01:02.875 --> 00:01:12.510
19
00:01:13.235 --> 00:01:14.855
20
00:01:15.555 --> 00:01:16.035
and,
21
00:01:16.515 --> 00:01:18.055
you know, the rabbit hole,
22
00:01:18.355 --> 00:01:19.335
the rabbit hole
23
00:01:20.710 --> 00:01:23.690
recap does not cover proper software updates anymore.
24
00:01:24.550 --> 00:01:31.455
And you know, and you guys also cover a bunch of other topics, so you couldn't go through the whole boring list and I wanted to go through the whole boring list and I wanted to go through the whole boring list
25
00:01:32.315 --> 00:01:42.640
26
00:01:43.100 --> 00:01:46.560
27
00:01:47.005 --> 00:01:47.985
Tap that
28
00:01:48.765 --> 00:01:49.265
button.
29
00:01:50.045 --> 00:01:54.545
30
00:01:54.990 --> 00:01:55.490
31
00:01:56.670 --> 00:01:59.570
So okay. So just a couple of things.
32
00:02:00.350 --> 00:02:05.105
So Matt was kind enough to join me on the first episode where I steal his audience,
33
00:02:05.725 --> 00:02:07.185
it was very kind of him.
34
00:02:07.645 --> 00:02:08.145
And
35
00:02:09.005 --> 00:02:10.465
the idea here is
36
00:02:12.210 --> 00:02:13.350
I hope to have
37
00:02:14.930 --> 00:02:17.670
different guests, probably many will repeat
38
00:02:17.970 --> 00:02:19.990
as long as I don't bore them to death,
39
00:02:21.275 --> 00:02:26.975
to help me go through this list. I am not the type of person who enjoys talking to myself
40
00:02:27.515 --> 00:02:29.695
on things, so I like the conversation.
41
00:02:30.709 --> 00:02:32.890
I think you'll add more value to it,
42
00:02:33.829 --> 00:02:34.329
and,
43
00:02:34.790 --> 00:02:38.650
hopefully, you help me see other projects and other updates I've missed.
44
00:02:39.525 --> 00:02:41.865
And the the format will be,
45
00:02:42.965 --> 00:02:43.865
software releases,
46
00:02:44.885 --> 00:02:48.585
and then we'll talk about a few different things like, Taproot adoption,
47
00:02:49.750 --> 00:02:50.570
some initiatives.
48
00:02:51.510 --> 00:02:54.410
I wanna go touch through a few topics
49
00:02:54.950 --> 00:02:57.290
on the Bitcoin OPTAC newsletter.
50
00:02:59.865 --> 00:03:02.605
I will cover some Bitcoin some coin kite updates,
51
00:03:04.265 --> 00:03:06.285
and some of our other websites,
52
00:03:07.220 --> 00:03:15.395
and, you know, whatever other things we wanna talk about at the end. So hopefully, you have about an hour or so of of of stuff to to bore yourself to death.
53
00:03:15.875 --> 00:03:23.415
Let's fucking go. Sounds exciting. Alright. Yeah. So, so not to fully kill the audience from the beginning, we're gonna skip Bitcoin Core
54
00:03:25.150 --> 00:03:30.130
because that one has a wee bit of updates. So we'll start with hwi2.1.1.
55
00:03:34.285 --> 00:03:35.505
Let me get here
56
00:03:36.285 --> 00:03:39.185
the release, and it was surprisingly a small release.
57
00:03:40.100 --> 00:03:41.560
It's, it just adds
58
00:03:41.860 --> 00:03:43.400
Ledger Nano as support.
59
00:03:44.740 --> 00:03:50.255
They changed the yeah. They changed the detection of top root change outputs for Trezor,
60
00:03:51.595 --> 00:03:52.095
and
61
00:03:52.635 --> 00:03:53.295
they fixed
62
00:03:53.595 --> 00:03:54.655
the signing failure
63
00:03:55.129 --> 00:03:56.909
for Ledger Bitcoin app 2.x.
64
00:03:59.370 --> 00:04:00.989
Well, on the plus side,
65
00:04:02.170 --> 00:04:04.705
there is quite a few pull requests that are good there.
66
00:04:05.725 --> 00:04:07.345
67
00:04:08.045 --> 00:04:09.825
they just weren't checking change
68
00:04:10.285 --> 00:04:12.305
for taproot addresses on Trezor.
69
00:04:13.160 --> 00:04:15.340
70
00:04:17.240 --> 00:04:19.580
on h w I, to be honest.
71
00:04:22.475 --> 00:04:27.055
I think oh, you know what? I think if I remember right, I think Trazer had,
72
00:04:27.595 --> 00:04:28.495
some checks
73
00:04:29.360 --> 00:04:32.260
that they did it, and then it broke HWI.
74
00:04:33.120 --> 00:04:37.215
And then I think they removed it, and now they probably fixed it and added again.
75
00:04:37.615 --> 00:04:38.355
Could be wrong.
76
00:04:38.815 --> 00:04:42.995
Somebody please let me know on the oh, yeah. You can go to bitcoin.review,
77
00:04:44.710 --> 00:04:45.690
that's the domain,
78
00:04:46.230 --> 00:04:49.290
and then on the top right there is a button called
79
00:04:50.470 --> 00:04:55.355
submit story or something like that. If you click there you can send your hate mail
80
00:04:55.735 --> 00:04:56.955
directly to me,
81
00:04:57.495 --> 00:04:58.795
which will be very welcome.
82
00:05:00.055 --> 00:05:01.195
Okay, so
83
00:05:02.090 --> 00:05:04.430
yeah. So there is also a pull request there for
84
00:05:05.050 --> 00:05:05.870
tap signer.
85
00:05:06.650 --> 00:05:07.850
We've, we've,
86
00:05:08.490 --> 00:05:10.750
written the code for Andrew
87
00:05:11.415 --> 00:05:14.555
88
00:05:15.175 --> 00:05:19.595
89
00:05:20.120 --> 00:05:27.980
90
00:05:28.575 --> 00:05:42.030
take your show notes, and I'm just gonna read them on rabbit hole recap for our software update section. So I don't have to so I don't have to do all that. So I'm here to support that initiative. It makes it easier for me to track software updates.
91
00:05:42.544 --> 00:05:46.884
But this site isn't just software updates. I see I see the white paper.
92
00:05:47.905 --> 00:05:48.645
I see
93
00:05:49.560 --> 00:05:50.940
something about BIP 85
94
00:05:51.240 --> 00:05:53.980
here. So is this just a new supposed to be a news feed?
95
00:05:54.680 --> 00:05:55.500
96
00:05:55.800 --> 00:06:00.855
originally, bitcoin dot review was going to be a place for me put articles on that we write.
97
00:06:01.475 --> 00:06:08.050
Like, we wrote the BIP 80 5 sort of, like, article there explaining some stuff about BIP 80 5. Right.
98
00:06:08.430 --> 00:06:12.610
But that initiative sort of like fell off the cracks. We didn't have time to do it.
99
00:06:13.070 --> 00:06:13.570
So,
100
00:06:14.510 --> 00:06:16.690
being lazy and not deleting the 2
101
00:06:17.665 --> 00:06:21.125
original entries there, I just added one more entry which is this podcast.
102
00:06:21.825 --> 00:06:26.485
Gotcha. And I need to fix a few things there, but essentially we're going to start putting in
103
00:06:27.650 --> 00:06:28.629
the pods there.
104
00:06:29.650 --> 00:06:33.430
And once I get the links fixed, you're going to get a show notes by clicking on it.
105
00:06:34.325 --> 00:06:34.825
And,
106
00:06:36.565 --> 00:06:38.665
yeah, so that's the home
107
00:06:38.965 --> 00:06:44.220
of the thing, and you can actually subscribe. Awesome. There is an XML there for RSS feeds, yay.
108
00:06:45.880 --> 00:06:49.100
109
00:06:49.455 --> 00:06:51.555
110
00:06:52.255 --> 00:06:53.475
and we support that.
111
00:06:54.095 --> 00:06:54.595
Alright.
112
00:06:55.775 --> 00:06:56.275
Next.
113
00:06:56.650 --> 00:06:59.070
Let's toot our own horns. You know
114
00:06:59.610 --> 00:07:00.270
115
00:07:00.970 --> 00:07:01.630
you can
116
00:07:02.490 --> 00:07:08.925
subscribe via RSS feed, so whenever a channel posts something it comes into your RSS feed. Waiting for the way to automatically update,
117
00:07:09.385 --> 00:07:16.180
118
00:07:18.080 --> 00:07:19.860
Alright. Next update, Matt.
119
00:07:21.280 --> 00:07:24.259
Okay. Cold card mark 4 version 504.
120
00:07:25.074 --> 00:07:25.895
That's us.
121
00:07:26.915 --> 00:07:28.854
So we improved the USB
122
00:07:29.315 --> 00:07:33.815
protocol, we added more encryption to it especially for the HSM mode,
123
00:07:37.210 --> 00:07:38.990
We increased the size
124
00:07:40.889 --> 00:07:41.389
of
125
00:07:41.850 --> 00:07:43.310
the HSM mode,
126
00:07:44.965 --> 00:07:45.865
how it handles
127
00:07:46.165 --> 00:07:48.104
the the the messaging back and forth.
128
00:07:48.965 --> 00:07:52.745
So the the people who are using ck bunker will enjoy these updates.
129
00:07:55.150 --> 00:07:57.570
We now have, regtest support,
130
00:07:58.350 --> 00:07:59.729
for testnet coins
131
00:08:00.325 --> 00:08:01.145
as well.
132
00:08:01.845 --> 00:08:04.265
So if you're a developer, you're gonna appreciate that.
133
00:08:06.245 --> 00:08:07.785
We did a major rework
134
00:08:08.730 --> 00:08:11.310
for all the tests and, again, reg test,
135
00:08:11.930 --> 00:08:13.150
for Bitcoin Core,
136
00:08:13.770 --> 00:08:16.110
and also the Linux support got improved.
137
00:08:17.225 --> 00:08:17.725
So,
138
00:08:18.025 --> 00:08:20.605
you know, we did hear the feedback from
139
00:08:20.905 --> 00:08:22.605
Linux devs using codecard,
140
00:08:23.520 --> 00:08:26.340
and they wanted to do that better, so that is better now.
141
00:08:27.520 --> 00:08:30.020
Some of the NFC stuff got improved,
142
00:08:30.965 --> 00:08:33.065
and Fully Noded now has
143
00:08:34.325 --> 00:08:34.905
a beta
144
00:08:35.925 --> 00:08:36.585
of their,
145
00:08:37.205 --> 00:08:41.420
of Fully Noded for iOS that supports codecard NFC, and it works.
146
00:08:42.280 --> 00:08:47.675
I think it's the first hardware wallet ever to do NFC with an iPhone. Yay. That's awesome.
147
00:08:47.975 --> 00:08:49.035
148
00:08:49.495 --> 00:09:01.430
149
00:09:04.084 --> 00:09:07.704
What else? We fixed it. A year and a half of feedback. But
150
00:09:08.084 --> 00:09:10.185
Yeah. No. You know, you could move fast.
151
00:09:10.620 --> 00:09:14.640
The thing is, like, app devs are sort of, like, a little sort of, like,
152
00:09:15.180 --> 00:09:19.100
more focused on some flashy stuff on lightning and other things. But
153
00:09:19.745 --> 00:09:28.165
Zeus should have NFC soon. Right? That's right. Zeus is working on it. That'll be big. Is working on it. I think there's a couple PRs.
154
00:09:28.630 --> 00:09:29.529
What about BlueWallet?
155
00:09:29.990 --> 00:09:31.529
Yeah, there is a PR there.
156
00:09:31.830 --> 00:09:35.290
I don't know, it hasn't moved much, but it's essentially ready.
157
00:09:36.485 --> 00:09:40.745
I mean, ready for sort of beta dev kind of thing, but it's there.
158
00:09:41.445 --> 00:09:43.690
Hopefully, soon, you'll make it,
159
00:09:44.570 --> 00:09:49.230
and then we'll have it on all of them, and I think it could be very cool. Especially because,
160
00:09:50.170 --> 00:09:51.550
I think it was a square
161
00:09:52.235 --> 00:09:53.535
which is blocks with
162
00:09:55.035 --> 00:09:55.535
Spyro
163
00:09:56.075 --> 00:10:03.820
will launch. Yeah. Once they release with NFC that's just people. That's right. So they're gonna do NFC and, you know, I did have a chat with
164
00:10:05.000 --> 00:10:05.660
with Stick
165
00:10:06.360 --> 00:10:07.580
and with
166
00:10:08.280 --> 00:10:08.780
Charles
167
00:10:09.495 --> 00:10:16.075
at Bitcoin Miami, and both of them are actually pretty interested in NFT as well. So the head of ledger and the head of ledger.
168
00:10:16.390 --> 00:10:40.740
That's right. So they're all excited about NFC as well. So not impossible, we end up seeing, you know, the 2 major competitors we have, also adding NFC, I think, will be fantastic for everybody. Yeah. I mean, if Ledger adds it, that should really push the needle because Ledger's gotta be the most sold, right, by far. Yeah. Oh, yeah. I mean We know they have at least a 1000000 customers because that's all the people that got leaked.
169
00:10:42.515 --> 00:10:45.575
We can count how many emails they have. Yeah.
170
00:10:46.035 --> 00:10:47.095
Right from the source.
171
00:10:48.810 --> 00:10:49.310
Amazing.
172
00:10:49.690 --> 00:10:51.630
Alright. So the other stuff is,
173
00:10:53.130 --> 00:10:53.870
it's small,
174
00:10:55.050 --> 00:10:55.950
mark 4,
175
00:10:57.515 --> 00:10:59.595
mark 4 version 0 3 was,
176
00:11:00.235 --> 00:11:04.495
you know, just more of that. Oh, and there was taproot, pay to taproot support added.
177
00:11:04.850 --> 00:11:06.310
That's important to mention.
178
00:11:07.170 --> 00:11:10.070
It's just that the the version o, 503
179
00:11:11.170 --> 00:11:11.750
and 504
180
00:11:12.130 --> 00:11:15.675
are kind of the same release. They just got split for reasons.
181
00:11:18.454 --> 00:11:23.959
So there there were a bunch of, like, little things. I I recommend if you're a cold card user, go check it out.
182
00:11:24.580 --> 00:11:27.240
Now mark 3, we didn't forget about you.
183
00:11:27.779 --> 00:11:30.200
We also added Pay2 Taproot
184
00:11:30.695 --> 00:11:31.675
on, 415
185
00:11:32.695 --> 00:11:33.435
in May,
186
00:11:35.735 --> 00:11:38.970
and a few sort of, like, little, a few little bug fixes.
187
00:11:39.529 --> 00:11:40.750
There is more
188
00:11:41.370 --> 00:11:48.269
mark 4 features being down ported to mark 3, and the goal is to sort of eventually maybe make
189
00:11:49.545 --> 00:12:03.370
a release that, you know, most of the features that can be back part of the wheel work. So, just wanted to put that out there. Awesome. And are you still selling the MK 3? Yes. We still are. We're still gonna do it for a while.
190
00:12:04.625 --> 00:12:05.525
We're also
191
00:12:06.625 --> 00:12:08.085
using the mark threes
192
00:12:08.705 --> 00:12:13.510
because they're slightly lower cost, and we've already recouped the r and d on it
193
00:12:14.950 --> 00:12:15.450
to
194
00:12:16.070 --> 00:12:16.970
to help
195
00:12:18.630 --> 00:12:19.130
meetups,
196
00:12:19.510 --> 00:12:21.130
especially in developing world
197
00:12:21.695 --> 00:12:22.195
and,
198
00:12:22.794 --> 00:12:27.142
in poor countries to to disseminate hardware wallets
199
00:12:27.741 --> 00:12:29.341
hardware wallet use
200
00:12:29.940 --> 00:12:31.540
signing devices use.
201
00:12:32.950 --> 00:12:40.165
We we figured they can't really afford to buy units to demo and stuff, so we're sort of using the mark 3
202
00:12:40.565 --> 00:12:42.904
as a vehicle to do that. That's awesome.
203
00:12:43.285 --> 00:12:45.625
204
00:12:48.070 --> 00:12:50.730
205
00:12:51.270 --> 00:12:52.890
you know, we're gonna send the hardware.
206
00:12:55.885 --> 00:12:59.985
207
00:13:01.005 --> 00:13:03.185
208
00:13:04.420 --> 00:13:05.720
version 1.5.
209
00:13:08.500 --> 00:13:10.475
I am not a BTC pay
210
00:13:11.035 --> 00:13:14.255
server user, but it is a project that is widely
211
00:13:16.074 --> 00:13:18.495
installed. And the two main things of this new release
212
00:13:18.810 --> 00:13:20.110
are the new dashboard,
213
00:13:20.410 --> 00:13:21.470
it looks jazzy.
214
00:13:22.890 --> 00:13:25.470
They do a very good job at showing all
215
00:13:26.090 --> 00:13:27.710
the statistics of your store,
216
00:13:28.745 --> 00:13:31.004
recent transactions, recent invoices.
217
00:13:32.425 --> 00:13:35.644
I do have a payment processor for our for CoinKite,
218
00:13:36.024 --> 00:13:40.310
on the credit card side, and it's starting to look like that. This is very nice.
219
00:13:41.010 --> 00:13:42.790
There is a dark mode as well.
220
00:13:43.330 --> 00:13:52.035
Very nice. I mean, they've had dark mode for a while, I think. Okay. And then they have this, payout processor. I think they can batch transactions.
221
00:13:53.855 --> 00:13:56.115
Oh, and it also improves the,
222
00:13:57.170 --> 00:13:58.870
how it handles partial
223
00:13:59.730 --> 00:14:01.829
payments on pool transactions.
224
00:14:02.130 --> 00:14:02.630
So,
225
00:14:03.170 --> 00:14:05.125
when they're using pool for
226
00:14:06.705 --> 00:14:07.205
lightning,
227
00:14:07.985 --> 00:14:12.805
they can handle that better. I'm probably not sure. How does the pool payments work on BTCPay?
228
00:14:13.370 --> 00:14:16.269
229
00:14:16.889 --> 00:14:18.269
230
00:14:18.649 --> 00:14:22.509
a based layer kind of guy so I don't use a lot of lightning.
231
00:14:23.165 --> 00:14:36.350
I mean, at CoinKite, you basically you use the in house solution that you guys made. Right? Yeah. No. I'd love to it's it's it's just BTC pay server came after we already had invested, you know, like, years building our own infrastructure.
232
00:14:38.009 --> 00:14:42.565
233
00:14:44.305 --> 00:14:45.365
234
00:14:46.225 --> 00:14:47.820
You know, it's it's like shipping,
235
00:14:48.520 --> 00:14:49.020
sales,
236
00:14:49.400 --> 00:14:51.020
all the stuff is in there,
237
00:14:51.640 --> 00:14:58.895
and it's like very us way of building it. I don't think many people would like to to take that on.
238
00:15:00.635 --> 00:15:03.055
Yeah. So if BTCPay existed
239
00:15:03.355 --> 00:15:05.490
way back then, maybe you would have gone with it.
240
00:15:07.410 --> 00:15:10.550
It's also dot net, which is not my favorite
241
00:15:11.490 --> 00:15:13.110
flavor of spam,
242
00:15:14.195 --> 00:15:21.334
but, but it is very good. And I mean, you know, in c sharp and, you know, dot net is a real language. It's not like this is JavaScript based.
243
00:15:22.410 --> 00:15:22.890
So,
244
00:15:23.290 --> 00:15:25.390
props to them. This looks awesome.
245
00:15:25.930 --> 00:15:29.150
There there's a lot of this really easy. You can enable and disable users,
246
00:15:31.215 --> 00:15:32.515
lots of UI improvements,
247
00:15:33.535 --> 00:15:37.315
and, yeah. I highly recommend people checking this project out.
248
00:15:39.120 --> 00:15:40.260
Okay. Now BlueWallet.
249
00:15:42.480 --> 00:15:42.980
BlueWallet,
250
00:15:44.855 --> 00:15:45.755
So version
251
00:15:46.135 --> 00:15:46.635
6.2.18
252
00:15:50.855 --> 00:15:51.355
Making
253
00:15:51.980 --> 00:15:54.319
a point at not going to the GitHub
254
00:15:54.779 --> 00:15:57.759
release it release because it's just endless,
255
00:15:58.540 --> 00:15:59.600
amount of commits.
256
00:15:59.944 --> 00:16:02.204
257
00:16:02.665 --> 00:16:08.524
258
00:16:08.879 --> 00:16:11.540
unless you are a project contributor
259
00:16:12.720 --> 00:16:16.740
or somebody who truly, truly cares about the commits of a specific project,
260
00:16:18.165 --> 00:16:27.430
you want the summary, right, of the release. So like notable Like why does this matter to me? Yeah, like the notable features, right? So I'm going to put this call out to devs out there.
261
00:16:27.910 --> 00:16:31.130
Do me a favor, you know, on your on your,
262
00:16:32.230 --> 00:16:32.730
Apple,
263
00:16:34.310 --> 00:16:37.050
release notes on the app store or Android or whatever,
264
00:16:37.654 --> 00:16:40.634
or on your release notes at the top, put noteworthy
265
00:16:41.095 --> 00:16:41.834
or summary
266
00:16:42.214 --> 00:16:44.954
of the releases and put something there.
267
00:16:45.350 --> 00:16:53.690
Yeah. Every release note should have a TLDR at the top. Yeah. I I think that's that's why we we try to do that on Twitter and a few others do that on Twitter,
268
00:16:54.825 --> 00:16:56.285
because it does help.
269
00:16:57.945 --> 00:16:58.445
Anyways,
270
00:16:59.145 --> 00:17:01.325
so for blue wallet, 6.2.18,
271
00:17:02.825 --> 00:17:03.710
it says fix,
272
00:17:04.510 --> 00:17:05.010
reorder
273
00:17:05.450 --> 00:17:05.950
wallet
274
00:17:06.390 --> 00:17:06.890
screen
275
00:17:07.330 --> 00:17:07.830
crush.
276
00:17:08.270 --> 00:17:10.370
So we'll go back one more, in January
277
00:17:10.750 --> 00:17:11.970
they released 6.2.17
278
00:17:14.195 --> 00:17:14.695
and
279
00:17:15.235 --> 00:17:19.495
now they show the selected coin summary on coin control screen. That's nice.
280
00:17:20.995 --> 00:17:22.775
Navigate to selected wallet.
281
00:17:24.309 --> 00:17:25.930
Rewarded wallet in clunky
282
00:17:26.470 --> 00:17:30.570
is clunky to use. That's a fix, and they deleted AOPP,
283
00:17:31.190 --> 00:17:32.250
which is great.
284
00:17:33.304 --> 00:17:34.205
What was the
285
00:17:34.664 --> 00:17:36.445
yeah. I know. It's bullshit.
286
00:17:37.225 --> 00:17:39.885
It's it's helping the bad people.
287
00:17:41.340 --> 00:17:43.200
I don't care how people spin it.
288
00:17:44.940 --> 00:17:48.320
289
00:17:49.295 --> 00:17:49.775
290
00:17:50.415 --> 00:17:51.395
Cold core.
291
00:17:51.695 --> 00:17:53.795
292
00:17:54.575 --> 00:17:59.450
that they waited this long to remove it and then still removed it. Well, they removed it in January
293
00:17:59.909 --> 00:18:00.409
294
00:18:01.190 --> 00:18:03.610
So, yeah, now that's actually quite late, isn't it?
295
00:18:04.149 --> 00:18:08.855
296
00:18:09.875 --> 00:18:23.085
297
00:18:23.465 --> 00:18:23.965
298
00:18:24.745 --> 00:18:25.804
299
00:18:26.904 --> 00:18:30.360
this is a project I really like. A lot of people don't know about it.
300
00:18:30.840 --> 00:18:32.540
It's called Cold Core.
301
00:18:33.480 --> 00:18:34.700
It's by James O'Byrne,
302
00:18:36.360 --> 00:18:40.220
and it's essentially a command line Bitcoin wallet.
303
00:18:40.825 --> 00:18:41.725
Very featureful,
304
00:18:43.304 --> 00:18:45.885
very pretty for people who like the command line,
305
00:18:47.385 --> 00:18:47.865
and,
306
00:18:48.664 --> 00:18:49.405
it supports
307
00:18:50.630 --> 00:18:52.170
hardware wallets, which is great.
308
00:18:52.630 --> 00:18:54.650
He built it for him to use. It's called,
309
00:18:54.950 --> 00:18:55.450
Coldcard,
310
00:18:56.764 --> 00:18:57.745
hence, Coldcore.
311
00:18:59.325 --> 00:19:02.065
But I think it works with other hardware wallets if I remember right.
312
00:19:03.164 --> 00:19:04.399
Anyways, so
313
00:19:04.779 --> 00:19:05.759
the 0.31
314
00:19:06.380 --> 00:19:06.880
release
315
00:19:08.220 --> 00:19:14.155
316
00:19:16.055 --> 00:19:17.115
317
00:19:17.575 --> 00:19:19.835
Yeah. Well, you'd still have to connect it. Right?
318
00:19:22.019 --> 00:19:24.760
It's not like plug and play per se.
319
00:19:25.940 --> 00:19:31.675
So anyways, I don't know. Somebody should check it out, and let us know. So in April 17th,
320
00:19:34.215 --> 00:19:36.075
where is I lost it.
321
00:19:37.870 --> 00:19:39.809
I lost it. Oh, release. Here.
322
00:19:40.350 --> 00:19:41.730
Bam. There you go.
323
00:19:42.669 --> 00:19:43.169
So,
324
00:19:43.630 --> 00:19:47.174
the release notes here. So, Wayland clipboard support,
325
00:19:48.914 --> 00:19:49.975
that's that's just
326
00:19:50.835 --> 00:19:51.735
never mind.
327
00:19:52.550 --> 00:19:53.370
Allow specification
328
00:19:53.750 --> 00:19:58.650
for fee rate in repair sand. Well, that's nice. So you can, set your fee rate
329
00:19:59.590 --> 00:20:01.210
and some RPC fixes.
330
00:20:02.865 --> 00:20:05.365
So this is a nerdy wallet with a nerdy update.
331
00:20:05.665 --> 00:20:06.725
It's a great wallet.
332
00:20:09.160 --> 00:20:14.220
333
00:20:14.760 --> 00:20:22.695
334
00:20:23.395 --> 00:20:24.375
about the maintainers
335
00:20:24.760 --> 00:20:26.700
or the main maintainers of the project.
336
00:20:28.040 --> 00:20:32.620
337
00:20:33.235 --> 00:20:47.559
many contributors. Right? But ColdForce is literally an Elburn project. Right? Like, he just carries it on his back. So It's like Sparrow, which is just like a Craig Raw project. That's right. So so James is both a Bitcoin core contributor,
338
00:20:48.740 --> 00:20:49.240
339
00:20:49.940 --> 00:20:51.240
I believe he writes
340
00:20:52.575 --> 00:20:53.554
economic stuff,
341
00:20:54.414 --> 00:20:56.274
and he's also a great DJ.
342
00:20:58.174 --> 00:21:02.950
So that's a little trivia there for people that did not know much about James O'Byrne.
343
00:21:04.050 --> 00:21:04.550
So,
344
00:21:05.970 --> 00:21:07.735
going to fully note it.
345
00:21:09.255 --> 00:21:09.755
The
346
00:21:10.215 --> 00:21:10.715
0.3.3
347
00:21:11.735 --> 00:21:12.235
version,
348
00:21:12.695 --> 00:21:16.955
fixes some bugs where lnd node via my node would fail.
349
00:21:17.350 --> 00:21:19.130
Well that's a nice bug to fix.
350
00:21:20.630 --> 00:21:20.870
And,
351
00:21:21.830 --> 00:21:23.610
it prevented batching from working.
352
00:21:23.910 --> 00:21:25.610
Okay, so there you go.
353
00:21:26.315 --> 00:21:30.555
And why not, go back a couple more versions here because it's so thin. So,
354
00:21:31.275 --> 00:21:45.025
355
00:21:46.044 --> 00:21:50.784
356
00:21:52.740 --> 00:21:55.240
357
00:21:55.540 --> 00:21:56.840
I didn't meet him in Riga.
358
00:21:57.780 --> 00:22:01.080
Yeah. But I met him in in Miami. I got him on stage too,
359
00:22:01.935 --> 00:22:02.675
which is great.
360
00:22:03.295 --> 00:22:05.315
361
00:22:06.735 --> 00:22:09.635
362
00:22:10.260 --> 00:22:13.600
and, like, getting them on stage. I'm like, yeah. I got Fontaine and Craig Raw.
363
00:22:14.700 --> 00:22:15.440
Super excited.
364
00:22:16.140 --> 00:22:17.600
I mean Who who is that?
365
00:22:18.725 --> 00:22:20.345
366
00:22:20.725 --> 00:22:22.565
where it happens. Right? It's,
367
00:22:23.045 --> 00:22:26.505
oh, I mean, what is real Bitcoin? Bitcoin is available to everyone.
368
00:22:27.330 --> 00:22:28.710
Billionaires and plebs.
369
00:22:29.090 --> 00:22:38.155
370
00:22:38.615 --> 00:22:39.115
371
00:22:40.054 --> 00:22:41.595
Alright. So 0.3.0.
372
00:22:43.440 --> 00:22:46.899
If you run a joint market server, you can now connect directly,
373
00:22:47.760 --> 00:22:49.299
if you're using core. That's nice.
374
00:22:50.240 --> 00:22:52.155
So joint market support on,
375
00:22:52.715 --> 00:22:56.815
fully in audit is improving. I guess that's my take from the last few updates.
376
00:22:57.755 --> 00:22:59.695
That's nice. And as I mentioned earlier,
377
00:23:00.240 --> 00:23:02.260
they also have now the
378
00:23:02.640 --> 00:23:04.020
the test lite version,
379
00:23:04.480 --> 00:23:06.260
beta version of NFC.
380
00:23:07.045 --> 00:23:10.665
So thanks, Fontaine, for for doing a lot of awesome work.
381
00:23:11.685 --> 00:23:12.825
Next is
382
00:23:13.125 --> 00:23:13.625
Nunchuk,
383
00:23:14.470 --> 00:23:15.130
which is
384
00:23:16.230 --> 00:23:22.145
Hugo. Hugo is doing a fantastic job with this with this wallet. A lot of people don't know about it.
385
00:23:22.705 --> 00:23:23.525
It's essentially,
386
00:23:24.785 --> 00:23:26.485
multi user, multi sig.
387
00:23:28.385 --> 00:23:28.885
It's
388
00:23:29.830 --> 00:23:32.250
it's very focused on on proper security.
389
00:23:33.430 --> 00:23:35.530
His app is fully native,
390
00:23:36.390 --> 00:23:40.825
so they're coding everything native in all the platforms, which is a bit of a feat.
391
00:23:42.565 --> 00:23:44.425
And, they have essentially
392
00:23:44.885 --> 00:23:45.705
a server
393
00:23:46.660 --> 00:23:50.039
that doesn't really know much about you to just coordinate
394
00:23:50.340 --> 00:23:51.960
messaging between the
395
00:23:52.419 --> 00:23:53.080
the clients.
396
00:23:53.895 --> 00:23:56.475
So that means, you know, you can,
397
00:23:57.175 --> 00:23:59.195
you can sort of propose a transaction
398
00:23:59.895 --> 00:24:06.370
to your your quorum of users in that multisig, and they'll get a message saying, you know, please sign this.
399
00:24:07.390 --> 00:24:12.395
You know, I am me, and I really wanna send it to this address, and then the people can choose to sign it or not.
400
00:24:13.975 --> 00:24:16.635
If you're familiar with an old project called
401
00:24:16.935 --> 00:24:17.435
copay,
402
00:24:18.560 --> 00:24:22.260
it's, it's similar, but, much better, implemented.
403
00:24:24.240 --> 00:24:26.580
And these guys are really plowing through here.
404
00:24:27.845 --> 00:24:29.065
So now they do,
405
00:24:29.684 --> 00:24:30.664
proper full,
406
00:24:31.205 --> 00:24:33.145
end to end encryption for the messaging.
407
00:24:35.590 --> 00:24:38.250
You don't need, and this was, it's
408
00:24:38.630 --> 00:24:41.049
so funny, these are all my requests to Hugo.
409
00:24:43.575 --> 00:24:47.115
Primary key accounts, now you don't need an email to sign up.
410
00:24:47.815 --> 00:24:49.035
There was also me.
411
00:24:50.450 --> 00:24:51.910
Large BSPT support.
412
00:24:52.450 --> 00:24:53.430
Yeah. That's great.
413
00:24:54.690 --> 00:24:57.190
Now they support, they improve the seed signer
414
00:24:57.815 --> 00:24:58.315
work.
415
00:24:58.855 --> 00:25:03.195
They support Signet, which is nice. Signet is essentially test net,
416
00:25:03.815 --> 00:25:05.790
but sort of like a new version of it.
417
00:25:07.710 --> 00:25:12.450
And then going back one more update, they added Taproot support in single sig only.
418
00:25:12.830 --> 00:25:20.345
I don't believe there is a multisig spec yet for Taproot use. So MuSig is still sort of like there's no implementation out there.
419
00:25:23.140 --> 00:25:30.920
And they're doing a bunch of other stuff that I don't know if it's public yet, so I'll keep on moving. Thanks, Hugo. This is a good list of updates.
420
00:25:31.225 --> 00:25:34.125
421
00:25:35.705 --> 00:25:36.205
Their,
422
00:25:38.345 --> 00:25:42.710
their tool is is extremely slick and it's it's definitely
423
00:25:43.010 --> 00:25:43.830
very well,
424
00:25:44.770 --> 00:25:45.750
sorely needed,
425
00:25:46.770 --> 00:25:50.185
even amongst, you know, I'm a keyholder in multiple
426
00:25:50.645 --> 00:25:51.145
multisigs,
427
00:25:52.485 --> 00:25:57.809
that are that are collaborative multisigs with other other people for different organizations and whatnot,
428
00:25:59.790 --> 00:26:02.049
and even among the die hard Bitcoiners,
429
00:26:02.510 --> 00:26:06.345
there is a it is massive pain point, you know, transferring,
430
00:26:06.965 --> 00:26:13.700
PSVTs, partially signed Bitcoin transactions between each other to, like, sign multisig transactions. It's a complete pain in the ass,
431
00:26:14.740 --> 00:26:18.600
and a lot of lost time and mental energy, and it really simplifies it.
432
00:26:19.380 --> 00:26:21.720
My biggest issue right now is I'm pretty sure,
433
00:26:22.475 --> 00:26:31.455
you know, everything's run through these mobile apps, and I'm pretty sure the mobile apps are still closed source. Am I correct on that? Yeah. But, you know, it's pretty hopeless on that sense.
434
00:26:32.620 --> 00:26:41.360
435
00:26:42.065 --> 00:26:48.485
you know, aside from, you know, the hardcore folks, like, they are also local They're not gonna verify it inside Lo No. But they could, and
436
00:26:48.970 --> 00:26:50.590
437
00:26:51.130 --> 00:26:53.070
it's not a case where it's viewable. Right? That.
438
00:26:53.450 --> 00:26:55.470
439
00:26:56.090 --> 00:26:57.230
Android wallets
440
00:26:57.595 --> 00:26:58.335
don't deterministically
441
00:26:58.715 --> 00:27:01.215
build, so that is kind of pointless too.
442
00:27:01.674 --> 00:27:05.455
443
00:27:05.990 --> 00:27:09.270
444
00:27:10.070 --> 00:27:18.305
see, the issue is when you have these wallets that the stack is huge, right? Millions of lines of code because of all the libraries they need to make it run on the phones,
445
00:27:19.885 --> 00:27:21.505
and then it's not deterministically
446
00:27:21.965 --> 00:27:22.465
built.
447
00:27:23.140 --> 00:27:25.800
You know, good luck trying to audit that code.
448
00:27:26.820 --> 00:27:30.600
It's nice to have, but realistically speaking it's pretty brutal.
449
00:27:30.980 --> 00:27:32.075
So I think
450
00:27:32.554 --> 00:27:38.014
more than solid loading at this point, it would be nice to to see deterministically built,
451
00:27:39.034 --> 00:27:39.774
phone wallets
452
00:27:40.260 --> 00:27:41.000
in my view.
453
00:27:41.380 --> 00:27:42.600
Okay. Including Nunchuck?
454
00:27:43.380 --> 00:27:46.440
Yeah. Yeah. All of them. I mean, you know, yeah. Like
455
00:27:46.900 --> 00:27:50.275
456
00:27:50.895 --> 00:27:55.155
one of the biggest holdups in terms of But not all with a stable amount of money.
457
00:27:55.455 --> 00:27:57.290
458
00:28:05.825 --> 00:28:11.125
459
00:28:11.585 --> 00:28:13.045
460
00:28:14.010 --> 00:28:19.230
when you look at the marketing of pretty much all the phone wallets, they all say just put all your funds in it.
461
00:28:21.045 --> 00:28:30.185
462
00:28:30.790 --> 00:28:37.210
463
00:28:39.774 --> 00:28:44.595
But one thing that is nice about it is because they're building things native and they're using
464
00:28:45.215 --> 00:28:47.554
like Bitcoin core methods of doing things,
465
00:28:48.190 --> 00:28:49.490
there is a lot less
466
00:28:49.790 --> 00:28:51.650
sort of, like, bullshit to dig through.
467
00:28:52.030 --> 00:28:56.130
So if they do add deterministic build to it, it should be very easy to
468
00:28:57.775 --> 00:28:58.434
to audit
469
00:28:58.735 --> 00:29:16.845
it. I mean, I know Hugo says he wants to, so Yeah. I mean, you know, it's like a nice to have thing. And he admits it's in beta still. He's he's in beta. Now, you know, now when you have, like, wallets that have, like, Java stacks and sort of, like, you know, major JavaScript stacks and they're serializing, serializing, serializing, serializing, like,
470
00:29:17.385 --> 00:29:17.885
secrets.
471
00:29:18.664 --> 00:29:20.284
That's really when
472
00:29:20.904 --> 00:29:21.404
things
473
00:29:21.705 --> 00:29:23.404
kind of shit hits the fan.
474
00:29:25.370 --> 00:29:28.430
It's hard to audit those projects. And and then
475
00:29:29.130 --> 00:29:40.775
if they are not deterministically built, it's even worse. Right? Because now it's already hard to audit it, and you cannot prove without reauditing every time, so it's it's tricky. Yeah. We wanna see that in all wallets,
476
00:29:41.790 --> 00:29:43.170
especially the ones out of beta.
477
00:29:48.085 --> 00:29:48.585
Alright.
478
00:29:49.925 --> 00:29:50.985
Next is,
479
00:29:52.485 --> 00:29:52.985
green.
480
00:29:54.085 --> 00:29:55.385
Blockstream green.
481
00:29:56.510 --> 00:29:58.370
That's another interesting wallet,
482
00:30:00.110 --> 00:30:02.290
and it's been in the market for a long time,
483
00:30:03.125 --> 00:30:08.905
And, and under, Green Address used to be the name of it, if you don't know the story of the project.
484
00:30:09.820 --> 00:30:12.000
485
00:30:12.300 --> 00:30:13.840
the original green address.
486
00:30:14.620 --> 00:30:18.800
487
00:30:19.154 --> 00:30:21.255
that was meant to be sort of like,
488
00:30:22.434 --> 00:30:22.934
unflagged
489
00:30:23.235 --> 00:30:28.135
or flagged as green addresses so that you know that's not like a drug dealer or something.
490
00:30:28.920 --> 00:30:31.900
Really? Who's, yeah. It was it was an unfortunate name.
491
00:30:32.760 --> 00:30:36.920
492
00:30:37.995 --> 00:30:39.695
it would be a collaborative multisig
493
00:30:40.555 --> 00:30:41.775
with green address
494
00:30:42.235 --> 00:30:49.170
or green wallet, whatever the previous name for green wallet was. I think it was green address. And so if you paid from there, a merchant could trust
495
00:30:49.550 --> 00:30:53.650
a zero confirmation transaction based on Green Address' reputation.
496
00:30:54.350 --> 00:30:59.695
Yep. That was exactly it. And that was, like, what, like, 2013 or 2014 or something like that?
497
00:31:00.154 --> 00:31:02.174
Yeah. Around that time. Maybe a little bit later.
498
00:31:02.554 --> 00:31:05.360
499
00:31:05.740 --> 00:31:13.600
around that time. Concept never got any uptick. I mean, merchant adoption never really happened. So I think the name really sent back the concept too,
500
00:31:14.184 --> 00:31:18.605
because, it was kind of like around the time where there was a lot of talk around
501
00:31:19.304 --> 00:31:22.044
the people blocking transactions that were coming from,
502
00:31:22.424 --> 00:31:28.460
you know, things that they don't agree with. And they wanted to maybe include that at part of the Bitcoin consensus
503
00:31:29.080 --> 00:31:29.820
core code.
504
00:31:31.095 --> 00:31:33.835
So it was kind of bad name choice.
505
00:31:34.215 --> 00:31:37.835
But now it's called Blockstream green, which is great. It looks very pretty.
506
00:31:38.799 --> 00:31:40.100
And in the last update,
507
00:31:41.039 --> 00:31:45.700
they added support, support ID on settings about multisig wallet,
508
00:31:47.254 --> 00:31:47.995
they changed
509
00:31:48.695 --> 00:31:50.794
drop address in transaction list,
510
00:31:51.575 --> 00:31:52.554
updated GDK
511
00:31:54.029 --> 00:31:55.250
to, 0.0.54,
512
00:31:59.470 --> 00:32:04.505
and updated translations. It's kinda cool, they do support quite a few languages if I remember right,
513
00:32:05.765 --> 00:32:07.785
and they have been improving. I
514
00:32:08.245 --> 00:32:10.560
have one green wallet that I use
515
00:32:11.180 --> 00:32:13.280
for a specific purpose, and,
516
00:32:15.100 --> 00:32:18.140
they have been improving. Now they support also a
517
00:32:18.885 --> 00:32:25.065
see, one thing that always drove me insane with that project was the fact that you had to use their nonstandard
518
00:32:25.445 --> 00:32:28.630
way of doing Bitcoin multisig or you couldn't use the wallet.
519
00:32:29.590 --> 00:32:30.330
Now they
520
00:32:31.750 --> 00:32:32.250
support,
521
00:32:33.910 --> 00:32:36.090
like just standard single sig,
522
00:32:37.065 --> 00:32:40.205
as well as a few other forms of of script,
523
00:32:40.825 --> 00:32:41.885
which is nice.
524
00:32:42.745 --> 00:32:48.010
525
00:32:48.790 --> 00:32:54.250
then Blockchain acquired it. It was still kind of ahead of its time, and then they, like, let development
526
00:32:56.385 --> 00:32:58.804
stop. They didn't really have it as a priority,
527
00:32:59.105 --> 00:33:10.025
528
00:33:12.645 --> 00:33:13.145
529
00:33:13.605 --> 00:33:18.105
530
00:33:18.520 --> 00:33:22.700
531
00:33:23.080 --> 00:33:27.420
532
00:33:28.835 --> 00:33:32.055
I know they're working on PSPT support as well which is nice,
533
00:33:33.395 --> 00:33:35.735
and I believe they're also working on
534
00:33:36.340 --> 00:33:39.720
that HWI support because this wallet does support
535
00:33:40.180 --> 00:33:42.360
many different systems with a good UI.
536
00:33:43.434 --> 00:33:49.054
So I am looking forward to having this wallet work with gold cards so I can recommend to people
537
00:33:49.355 --> 00:33:50.894
who want a different wallet
538
00:33:51.490 --> 00:33:53.110
on their desktop or phone.
539
00:33:54.930 --> 00:33:55.430
Alright.
540
00:33:56.450 --> 00:33:57.670
Now the old
541
00:33:58.130 --> 00:34:00.310
good beast, one of my favorite wallets,
542
00:34:00.875 --> 00:34:01.375
Electrum,
543
00:34:03.195 --> 00:34:12.180
also one of the oldest wallets. I believe it's the first wallet after Bitcoin Core with, like, a a reasonable install base. It's that old.
544
00:34:12.640 --> 00:34:14.100
I think they launched in 2011.
545
00:34:17.414 --> 00:34:17.914
So
546
00:34:18.375 --> 00:34:20.474
they did add lightning to Electrum,
547
00:34:21.174 --> 00:34:21.674
which
548
00:34:22.135 --> 00:34:25.515
sort of made things more complicated in a very complicated code base.
549
00:34:27.020 --> 00:34:28.480
So in this last update,
550
00:34:28.780 --> 00:34:29.280
4.2.2
551
00:34:30.780 --> 00:34:31.840
in May 27th,
552
00:34:33.580 --> 00:34:34.780
the lightning
553
00:34:35.835 --> 00:34:37.855
on the lightning part, they added
554
00:34:38.315 --> 00:34:39.855
watching on chain outputs,
555
00:34:41.914 --> 00:34:45.520
enforce relative order of some of the messages
556
00:34:46.220 --> 00:34:46.720
during,
557
00:34:48.780 --> 00:34:49.840
rest reestablishment.
558
00:34:50.780 --> 00:34:55.605
I you know, that that goes into the lightning stuff that I don't really pay too much attention.
559
00:34:58.065 --> 00:35:02.359
I love lightning. It's just it's just too much for me to pay attention to.
560
00:35:04.900 --> 00:35:08.339
561
00:35:09.255 --> 00:35:10.955
Yeah. Well No one cares.
562
00:35:11.815 --> 00:35:19.789
563
00:35:20.089 --> 00:35:21.710
lifetime, it never broke.
564
00:35:23.130 --> 00:35:23.630
So,
565
00:35:24.205 --> 00:35:27.265
like, respect for that is like and also, you know,
566
00:35:28.525 --> 00:35:30.225
maintaining a wallet this size
567
00:35:31.005 --> 00:35:36.190
is is not easy, and maintaining a wallet this size for, you know, these many years also not easy.
568
00:35:37.530 --> 00:35:44.405
I just I just wish they had not added lightning to that wallet. I wish they had made it maybe a side thing or, you know,
569
00:35:44.785 --> 00:35:58.050
maybe electrum lightning or something so you wouldn't be able to like, it was an easy task, like, there was a lot of man hours that went into that. Oh my god. It was monumental effort, and they you know, props to them. They they even started before a lot of the standards were in place.
570
00:36:00.415 --> 00:36:03.555
Similar with BIP 39, which they still don't support by default.
571
00:36:05.349 --> 00:36:12.170
And, but in my opinion, the biggest mistake that we made was putting starting development of Lightning on master branch
572
00:36:12.710 --> 00:36:13.609
that made
573
00:36:14.015 --> 00:36:16.035
Electrum essentially now released for a year.
574
00:36:17.775 --> 00:36:19.475
But they did, and it works,
575
00:36:20.015 --> 00:36:22.994
and they keep on pushing updates out, which is really cool.
576
00:36:23.560 --> 00:36:27.420
So, yeah, on the hardware wallets, smarter pairing during signed transactions,
577
00:36:28.440 --> 00:36:30.940
they fix a few things with keep key.
578
00:36:31.464 --> 00:36:33.724
It's amazing to me that keep key is still around.
579
00:36:34.425 --> 00:36:37.005
The Trezor clone? The Trezor clone,
580
00:36:38.184 --> 00:36:39.645
that went closed source
581
00:36:42.180 --> 00:36:46.040
because it was a different license at that time. It was a pre g p I when they cloned, I think.
582
00:36:46.420 --> 00:36:55.315
583
00:36:55.694 --> 00:37:00.849
584
00:37:02.750 --> 00:37:03.470
585
00:37:04.085 --> 00:37:08.345
don't do it. It's not worth it. Makes no sense. So fix app image,
586
00:37:09.205 --> 00:37:11.625
587
00:37:11.925 --> 00:37:12.425
really
588
00:37:13.070 --> 00:37:17.010
of note here. Fix a security fix, remove support for file
589
00:37:17.310 --> 00:37:19.570
in your eyes on BIP 70.
590
00:37:20.270 --> 00:37:21.170
BIP 70.
591
00:37:22.775 --> 00:37:23.275
Alright.
592
00:37:24.375 --> 00:37:25.515
So next.
593
00:37:27.975 --> 00:37:28.955
Oh, Spectre
594
00:37:29.255 --> 00:37:30.795
d Spectre Desktop.
595
00:37:31.510 --> 00:37:33.030
They have a nice tweet with,
596
00:37:33.910 --> 00:37:36.730
with the noteworthy updates. Thank you, Spectre.
597
00:37:38.550 --> 00:37:41.015
598
00:37:41.494 --> 00:37:43.115
Yes. So is BTCPay.
599
00:37:44.295 --> 00:37:57.050
600
00:37:58.175 --> 00:38:15.520
Essentially, what we do is we have a slightly shorter version of the release notes on Twitter and then a picture of the release notes and then the true fully released notes on GitHub. Yeah. You're a little bit of a hypocrite about it. Like, you could do a little bit better with it. Yeah. I mean, that's that's that's the basis of of being a company, is being a hypocrite.
601
00:38:16.595 --> 00:38:19.575
602
00:38:20.914 --> 00:38:23.494
603
00:38:24.210 --> 00:38:24.710
10.3
604
00:38:25.410 --> 00:38:26.150
is out.
605
00:38:26.450 --> 00:38:28.069
Spook, spook, spook emoji.
606
00:38:29.650 --> 00:38:31.910
June 23rd. So it's recent.
607
00:38:32.714 --> 00:38:36.575
Okay so feature drag and drop for PSVT import. Well that's nice.
608
00:38:37.035 --> 00:38:38.015
So now we can,
609
00:38:38.315 --> 00:38:39.295
I can drag
610
00:38:40.280 --> 00:38:43.340
from my cold cards virtual disk into
611
00:38:43.800 --> 00:38:44.859
Spector desktop
612
00:38:45.400 --> 00:38:45.900
UI?
613
00:38:46.200 --> 00:38:47.260
That's pretty cool.
614
00:38:48.634 --> 00:38:50.654
It should make it a lot easier, and then they have
615
00:38:51.035 --> 00:38:53.775
6 bug fixes. See that's a summary,
616
00:38:54.315 --> 00:38:57.375
2 chores and one docs and one UI.
617
00:38:58.970 --> 00:39:04.430
So yeah, check out the Spectre desktop, it's a good project, and what I love about it it talks directly to core.
618
00:39:06.545 --> 00:39:11.285
It it's a it really is sort of like very little stack that you need to run it.
619
00:39:11.720 --> 00:39:14.940
And their UI does keep on updating and and improving.
620
00:39:15.960 --> 00:39:18.460
621
00:39:18.760 --> 00:39:20.460
stalling on updates to
622
00:39:21.345 --> 00:39:23.605
integrate their own lightning implementation was
623
00:39:23.985 --> 00:39:27.125
we might not have seen Spectre and Spyro get birthed otherwise.
624
00:39:27.825 --> 00:39:28.865
625
00:39:29.265 --> 00:39:33.910
626
00:39:35.089 --> 00:39:36.710
627
00:39:37.010 --> 00:39:37.510
web,
628
00:39:37.865 --> 00:39:40.425
like the the the UI wallet is,
629
00:39:40.905 --> 00:39:41.385
it's,
630
00:39:41.705 --> 00:39:43.645
you either love it or you hate it.
631
00:39:45.145 --> 00:39:51.370
Most of the devs who work on it love it, therefore, it doesn't change. It is also a monumental amount of change. It's
632
00:39:52.550 --> 00:39:54.810
changing UI in complex,
633
00:39:58.055 --> 00:39:58.555
desktop
634
00:39:58.855 --> 00:39:59.835
native software
635
00:40:00.214 --> 00:40:01.035
is complicated,
636
00:40:01.575 --> 00:40:02.714
especially when it's
637
00:40:03.015 --> 00:40:03.755
open source
638
00:40:04.295 --> 00:40:04.795
because
639
00:40:05.820 --> 00:40:06.320
designers
640
00:40:07.340 --> 00:40:07.840
and,
641
00:40:08.620 --> 00:40:10.240
UX people don't code.
642
00:40:11.100 --> 00:40:15.335
And in open source projects like Bitcoin Core is very sort of meritocratic
643
00:40:16.355 --> 00:40:24.840
and sort of self initiated, right? So if you wanna do something, go and do it, but in especially in Bitcoin Core, you're gonna get 10 noes before you get a yes.
644
00:40:27.460 --> 00:40:27.960
So
645
00:40:28.580 --> 00:40:32.760
if if you are the unicorn who can code and do UI,
646
00:40:33.815 --> 00:40:37.435
you're really gonna get 10 nos, but most guys can't code
647
00:40:37.815 --> 00:40:46.890
who can do UI, so they make these pretty UI's and then they sort of like here, somebody called this, which is the other 90% of the work and everybody's just like nope,
648
00:40:47.750 --> 00:40:48.250
right?
649
00:40:48.630 --> 00:40:50.475
So it's a tricky thing.
650
00:40:51.275 --> 00:40:53.535
We appreciate everybody for working on it.
651
00:40:55.595 --> 00:40:56.095
Alright.
652
00:40:56.555 --> 00:40:58.015
So moving on to
653
00:40:58.475 --> 00:40:58.975
Matt's
654
00:40:59.539 --> 00:41:06.119
favorite project, and because he literally dropped the open dimes hat for Sparrow's hat.
655
00:41:06.819 --> 00:41:07.799
It was noticed.
656
00:41:08.180 --> 00:41:09.079
657
00:41:09.445 --> 00:41:10.745
658
00:41:11.685 --> 00:41:13.945
I I I know. We're an old girlfriend.
659
00:41:14.405 --> 00:41:25.040
660
00:41:25.420 --> 00:41:30.674
661
00:41:31.055 --> 00:41:44.980
662
00:41:47.105 --> 00:41:48.885
663
00:41:50.224 --> 00:41:50.724
Sparrow
664
00:41:52.145 --> 00:41:54.885
is a very cool project, relatively new.
665
00:41:55.309 --> 00:41:56.930
Oh, is it 2 years old now?
666
00:41:58.670 --> 00:41:59.710
It's run by
667
00:42:00.109 --> 00:42:02.675
Maybe Les. Craig Craig Wright.
668
00:42:03.635 --> 00:42:05.735
669
00:42:06.035 --> 00:42:06.775
I know.
670
00:42:07.235 --> 00:42:07.735
671
00:42:08.035 --> 00:42:09.735
Craig Craig Wright.
672
00:42:10.950 --> 00:42:12.810
673
00:42:13.430 --> 00:42:16.410
674
00:42:17.625 --> 00:42:24.444
So so, anyways, I met I met Craig in Miami. It was, it was fun. It was fun. It was fun. It was a nice time chatting. Yes.
675
00:42:24.744 --> 00:42:25.724
Very nice lady.
676
00:42:27.970 --> 00:42:30.230
So, so they are pumping features.
677
00:42:30.849 --> 00:42:31.349
Wow.
678
00:42:32.049 --> 00:42:35.430
He he he reminds me of doc hacks. They just pump
679
00:42:36.290 --> 00:42:36.950
and get
680
00:42:37.325 --> 00:42:38.144
shit done.
681
00:42:39.085 --> 00:42:40.144
I lost
682
00:42:41.724 --> 00:42:42.545
the release.
683
00:42:42.924 --> 00:42:49.510
I need to go see that here, Release notes. So Craig is, Craig does not have a good summary of notes.
684
00:42:49.970 --> 00:42:51.670
So we'll go through a few.
685
00:42:52.635 --> 00:42:55.135
So on May 26th they released 1.6.5,
686
00:42:56.795 --> 00:43:00.415
they added a Ledger Nano as support really because it's HWI.
687
00:43:01.180 --> 00:43:05.200
So you notice a pattern that all the wallets that use hwi
688
00:43:06.220 --> 00:43:13.015
will add, you know, it's not just plug and play, but they will go in and add the implementation of the new wallet that's been supported by HWI,
689
00:43:13.714 --> 00:43:16.454
which is a great way of handling all this stuff.
690
00:43:18.230 --> 00:43:22.810
They now allow watch only key stores to enable signing from matching
691
00:43:23.110 --> 00:43:24.650
connected hardware wallets.
692
00:43:25.265 --> 00:43:28.645
Oh, that's cool. So now you can sign connected too.
693
00:43:30.465 --> 00:43:33.205
They can also import gap limits from Electrum.
694
00:43:34.720 --> 00:43:36.740
I think they had different gap limits.
695
00:43:37.040 --> 00:43:41.300
For people that don't know, the gap limits are essentially how many derivation addresses
696
00:43:41.600 --> 00:43:43.540
and the space in between those
697
00:43:44.755 --> 00:43:47.335
you have or generate and start watching.
698
00:43:47.955 --> 00:43:50.855
So now they can match electrons when they import.
699
00:43:51.555 --> 00:43:52.055
So,
700
00:43:53.180 --> 00:43:55.680
Sparrow is a very was very clever
701
00:43:56.140 --> 00:43:57.040
on the beginning
702
00:43:58.140 --> 00:43:59.280
by essentially
703
00:43:59.660 --> 00:44:00.160
importing
704
00:44:01.734 --> 00:44:04.474
the Electrum, which is one of the most used wallets
705
00:44:05.174 --> 00:44:06.635
in the market before,
706
00:44:08.849 --> 00:44:14.390
importing their JSON file, which is their wallet file into Sparrow and just simply working,
707
00:44:15.410 --> 00:44:18.150
which is fantastic. I I love that kind of thinking.
708
00:44:20.355 --> 00:44:23.175
And then they have a bunch of bug fixes on the release,
709
00:44:23.555 --> 00:44:25.735
including one from Andrew Chow.
710
00:44:26.140 --> 00:44:27.359
Andrew Chow is now
711
00:44:27.819 --> 00:44:32.400
a a a signal isn't his he has a key now for Bitcoin Core. Right?
712
00:44:34.205 --> 00:44:34.705
He's,
713
00:44:35.085 --> 00:44:44.810
714
00:44:45.290 --> 00:44:49.070
715
00:44:49.450 --> 00:44:49.950
into
716
00:44:51.325 --> 00:44:51.825
hWI.
717
00:44:52.525 --> 00:44:53.345
We're waiting.
718
00:44:53.805 --> 00:44:54.625
Love you.
719
00:44:56.365 --> 00:45:01.240
720
00:45:02.180 --> 00:45:02.680
721
00:45:03.220 --> 00:45:03.540
That's
722
00:45:04.580 --> 00:45:14.105
723
00:45:14.405 --> 00:45:16.720
like, I'm not gonna say no to you. You can take it.
724
00:45:17.200 --> 00:45:25.055
Just know that you're, like, one of the few in the world who has it right now. That's right. He was super excited about it. It was like this young kid. That's awesome.
725
00:45:26.315 --> 00:45:29.535
726
00:45:30.315 --> 00:45:31.440
looking forward to that.
727
00:45:32.960 --> 00:45:34.099
Right. Bug fixes,
728
00:45:34.480 --> 00:45:37.940
restore hardware wallet from communication in older IO, macOS.
729
00:45:40.675 --> 00:45:43.095
When hiding empty used addresses,
730
00:45:43.635 --> 00:45:47.015
add and remove addresses if address balance changes.
731
00:45:48.700 --> 00:45:52.319
This is a classic programmer wrote the release notes.
732
00:45:53.819 --> 00:45:55.519
Explicitly commit spinner
733
00:45:55.965 --> 00:45:58.145
editor value when closing dialogues.
734
00:45:59.325 --> 00:46:01.505
So essentially they fix the spinning,
735
00:46:03.645 --> 00:46:04.865
of the mouse spinning.
736
00:46:06.020 --> 00:46:09.400
Fixed date sorting in the UTXO table, that's nice,
737
00:46:10.420 --> 00:46:11.720
and a few other ones.
738
00:46:13.175 --> 00:46:15.675
Oh, fix PSPT tap root internal key duplication.
739
00:46:16.295 --> 00:46:18.635
Okay. So they might have had a bug with that.
740
00:46:19.950 --> 00:46:25.089
And set lock all wallet menu control command status on every wallet lock,
741
00:46:25.630 --> 00:46:28.405
and that's just more closing little holes there.
742
00:46:28.885 --> 00:46:33.385
Well, I guess it's too bad we missed because the previous release was a massive release.
743
00:46:35.445 --> 00:46:38.345
They added native support for epom 1,
744
00:46:39.990 --> 00:46:42.569
They added a block stream jade support.
745
00:46:43.750 --> 00:46:45.609
They upgraded to to the newest,
746
00:46:46.695 --> 00:46:49.915
HWI, probably why the subsequent release had the nano,
747
00:46:50.375 --> 00:46:51.595
ledger, s,
748
00:46:53.415 --> 00:46:53.915
support.
749
00:46:55.790 --> 00:46:58.450
There's also taproot signing support now.
750
00:47:00.990 --> 00:47:02.369
Support scanning seeds,
751
00:47:04.785 --> 00:47:06.405
and a bunch of other things.
752
00:47:06.945 --> 00:47:09.445
Very, very good work. That's a lot of work.
753
00:47:11.000 --> 00:47:12.619
So props to Craig.
754
00:47:13.560 --> 00:47:18.700
755
00:47:20.395 --> 00:47:25.215
756
00:47:25.515 --> 00:47:35.100
757
00:47:35.720 --> 00:47:39.305
which is you can very much tell that it's it's a person who
758
00:47:40.085 --> 00:47:41.705
or a group of people who,
759
00:47:42.244 --> 00:47:44.005
like, need they needed a solution on
760
00:47:44.645 --> 00:47:49.309
for for using Bitcoin. They needed a tool for using Bitcoin, so they built it around their own need.
761
00:47:49.930 --> 00:47:53.869
762
00:47:54.265 --> 00:47:59.805
763
00:48:00.265 --> 00:48:08.660
And then and then, you know, ideally, be able to make make some profit, some lean profit on the side of it with it. And,
764
00:48:09.515 --> 00:48:23.390
yeah, so shout out to him, and he is it is a monetized project now because he does have have the coin join built in, so he is making revenue off of it. But if you wanna support him, he has a donation page on spiral wallet dot com. That's great. Like, I I want sort of contributing.
765
00:48:23.849 --> 00:48:25.965
766
00:48:26.365 --> 00:48:27.345
good developer,
767
00:48:27.645 --> 00:48:28.145
good
768
00:48:28.525 --> 00:48:29.025
contributor
769
00:48:29.805 --> 00:48:30.305
to
770
00:48:30.685 --> 00:48:36.770
projects to make a killing, not just a little bit. I hope they all become extremely wealthy from their work.
771
00:48:38.750 --> 00:48:49.664
I mean, that's the ideal situation because the donation model is not sustainable. No. I mean, you know, it's it's what I, you know, like, I I I sort of, like, joke sometimes is bag wear. Right? Like, you can't
772
00:48:50.125 --> 00:48:51.184
you can't maintain
773
00:48:51.724 --> 00:48:56.630
money handling software on on, like, you know, on donations only. Right?
774
00:48:58.530 --> 00:49:07.165
And, you know, Bitcoin Core does have enough money because, you know, a lot of people got in early. A lot of people get grants. It's the base layer.
775
00:49:07.985 --> 00:49:13.150
You know, the side projects, all the the all the the the ecosystem projects. Right?
776
00:49:14.330 --> 00:49:18.030
It's a lot harder and a lot more complicated because, you know, traditionally,
777
00:49:18.970 --> 00:49:23.454
you know, if you wanna make sure, you know, you don't make money, you know,
778
00:49:23.994 --> 00:49:25.694
go work on open source projects.
779
00:49:27.340 --> 00:49:30.720
And then in Bitcoin, like, all those projects have also competition.
780
00:49:31.580 --> 00:49:34.640
So it diminishes even their sort of like their
781
00:49:36.175 --> 00:49:37.875
their their, their market base,
782
00:49:38.175 --> 00:49:44.275
and, it's just it's nice to see people come up with ways of making good money, and I hope they make all the money.
783
00:49:45.830 --> 00:49:46.650
So yeah.
784
00:49:46.950 --> 00:49:49.930
785
00:49:50.310 --> 00:49:56.455
786
00:49:56.755 --> 00:50:01.735
financially to maintain this project. Like, you know, you want people to feel like they have enough value.
787
00:50:02.099 --> 00:50:07.640
788
00:50:09.195 --> 00:50:13.295
and they accept donations, even if they are even if they are monetizing,
789
00:50:14.715 --> 00:50:17.530
still consider donating. It's it shouldn't be it shouldn't
790
00:50:27.914 --> 00:50:35.855
like, right now, like, basically, like, Sparrow is is ramping up his monetization, and it's becoming sustainable. Right? But in the early days,
791
00:50:36.180 --> 00:50:40.839
the donations still help even though he's doing that. And, like, a good example right now is Robosats,
792
00:50:41.619 --> 00:50:43.480
which is this new p to p KYC
793
00:50:44.385 --> 00:50:44.885
free,
794
00:50:45.665 --> 00:50:46.484
no KYC
795
00:50:47.185 --> 00:50:48.244
Bitcoin exchange
796
00:50:48.545 --> 00:50:54.600
that's Tor only. And, like, they're built from the ground up to be sustainable. Like, they take a fee of every transaction.
797
00:50:55.220 --> 00:51:02.985
I love it. But but those fees don't cover development right now still. Right. Right? Like, they're in this bootstrap phase, so I'm donating to RoboSats
798
00:51:03.685 --> 00:51:06.905
even though they have a sustainable model. So I'm just saying that people shouldn't
799
00:51:07.460 --> 00:51:16.120
just look at these things and be like, oh, well, you know, they're monetizing, so I'm not gonna donate. Right. I think another thing too is that, like, it it helps developers
800
00:51:17.865 --> 00:51:20.525
801
00:51:21.625 --> 00:51:22.125
to
802
00:51:23.065 --> 00:51:24.685
to see market signals.
803
00:51:24.985 --> 00:51:25.485
Right?
804
00:51:25.865 --> 00:51:26.365
So
805
00:51:27.300 --> 00:51:40.765
if they see that there is enough donations going to their project, they will put more effort in and build more features and and maybe or maybe they will maybe that's the the thing that makes it they make the decision if they're gonna go full time on it or not.
806
00:51:41.305 --> 00:51:41.805
Right?
807
00:51:42.585 --> 00:51:49.790
Because a lot of times, people just don't know how much market there is out there for what they make. People cheering on Twitter
808
00:51:50.330 --> 00:51:51.310
for the project
809
00:51:51.610 --> 00:51:53.870
doesn't really sort of mean much.
810
00:51:54.714 --> 00:51:59.935
It's very helpful is, like, in terms of, like, spreading the word about the project, but, like, people,
811
00:52:00.555 --> 00:52:01.295
you know,
812
00:52:02.180 --> 00:52:03.720
partying away with their SATs,
813
00:52:04.340 --> 00:52:06.920
to support a project really sort of reinforces
814
00:52:07.700 --> 00:52:14.195
for the maker that there is a market and they should continue. Right? Even if it may not be a lot now, like,
815
00:52:14.495 --> 00:52:20.809
it just signals to them that there is a market that that is willing to pay for it as opposed to just thank them for it. Right?
816
00:52:21.510 --> 00:52:24.410
I I think that's why it's so important to monetize things.
817
00:52:25.805 --> 00:52:26.305
818
00:52:26.765 --> 00:52:30.705
We're on the same page on this. Yep. Alright. So fountain
819
00:52:31.325 --> 00:52:33.025
820
00:52:33.565 --> 00:52:35.569
I'm gonna go you're gonna love this
821
00:52:35.869 --> 00:52:40.049
one. I'm gonna go through the to the app store, release notes,
822
00:52:40.589 --> 00:52:41.809
which is 0.4,
823
00:52:42.109 --> 00:52:43.410
bug fixes and improvements.
824
00:52:43.835 --> 00:52:44.335
0.3,
825
00:52:44.795 --> 00:52:46.095
bug fixes and improvements.
826
00:52:46.635 --> 00:52:47.135
0.319,
827
00:52:48.234 --> 00:52:53.060
828
00:52:53.840 --> 00:53:00.500
I don't I don't have release notes for it. Well, the big one for so so the big one for 0,
829
00:53:01.714 --> 00:53:04.454
the the previous release, what is that, 0.3.0?
830
00:53:06.835 --> 00:53:16.830
Whatever. The the one before 4. The the one before the most recent release, the big improvement was offline listening, which I think is a must for podcasts. Oh, that has to it has to.
831
00:53:17.415 --> 00:53:21.994
So that was a big one. Fountain Podcast is a podcasting 2.0 app,
832
00:53:22.695 --> 00:53:26.395
where you can stream sats to content creators that you enjoy.
833
00:53:28.990 --> 00:53:29.490
So
834
00:53:29.950 --> 00:53:30.450
so,
835
00:53:30.910 --> 00:53:33.250
it's one of the leading ones along with Breezewallet.
836
00:53:34.745 --> 00:53:45.970
Yeah. So offline listening was a big ad for the previous release, and then this release, the big ad is listeners now can earn SaaS. If you listen to a podcast through Fountain Podcasts, you automatically, without
837
00:53:46.510 --> 00:53:48.849
doing anything, just start receiving SATs.
838
00:53:49.309 --> 00:53:53.345
839
00:53:54.444 --> 00:53:56.944
Money goes from the advertiser to
840
00:53:58.350 --> 00:54:01.410
841
00:54:02.190 --> 00:54:03.010
That's great.
842
00:54:03.790 --> 00:54:08.775
It's like a cool concept. They're playing they're, like, tweaking the incentives over there, but it's a pretty cool concept.
843
00:54:09.075 --> 00:54:11.974
The one major negative of Fountain right now
844
00:54:12.355 --> 00:54:15.335
is that the the Lightning Wallet is custodial. So
845
00:54:16.529 --> 00:54:25.755
you have custodial risk there. You shouldn't keep them I I don't have a problem with that. But they are they are actively trying to get away from that, and they'll probably end up using Greenlight,
846
00:54:26.375 --> 00:54:30.475
through Blockstream, which is a trust minimized cloud solution.
847
00:54:30.855 --> 00:54:31.355
848
00:54:31.655 --> 00:54:34.790
Yeah. I mean, realistically speaking, you know, like, lightning
849
00:54:35.570 --> 00:54:41.015
lightning amounts are economically more irrelevant. Right? So it's like it's not, like, the incentive to
850
00:54:41.494 --> 00:54:43.434
rob your own user base is a lot lower.
851
00:54:43.734 --> 00:54:44.615
852
00:54:45.255 --> 00:54:56.500
the way I look at it is like, okay. So, like, how much cash do you have in your back pocket if you go out? Exactly. Like, if you get robbed in that situation and you lose a $100, it's not And realistically speaking, running your own lightning node is a bit of pain in the ass.
853
00:54:57.405 --> 00:55:00.145
854
00:55:00.605 --> 00:55:04.545
855
00:55:05.420 --> 00:55:09.119
the regulators are gonna come after you and make you add KYC, and no one wants KYC.
856
00:55:09.500 --> 00:55:15.994
That's yeah. So Greenlight is actually a really compelling solution here. The major negative of Greenlight is,
857
00:55:17.255 --> 00:55:20.395
the node is offline if the user's app isn't open,
858
00:55:21.255 --> 00:55:26.410
because the user's app is holding the keys. That's what makes a trust minimized. The keys aren't on the server.
859
00:55:26.790 --> 00:55:30.250
Right. But in this particular instance, if it's a listener paying
860
00:55:30.795 --> 00:55:51.025
while they're listening to a podcast, they already have the app open, so green light could be perfect for that. It doesn't solve the problem for the content creator. The content creator basically needs a 247 node always on. Right. Well but Fountain app could also just just handle that for the content creator too. Right? They can they can host the bitcoin dot review. Or, like, Voltage. They could do, like, Voltage
861
00:55:52.285 --> 00:55:56.225
for the 247 node, something like that where you have a hosted node.
862
00:55:57.059 --> 00:55:58.839
863
00:55:59.619 --> 00:56:10.705
You know, that that's another nice thing too. It's like that's like like new and novel. Like, it's nice that people are trying different stuff. They're not just sort of, like, trying to compete on the same sort of spec at some other app.
864
00:56:12.180 --> 00:56:12.839
I agree.
865
00:56:13.220 --> 00:56:20.975
866
00:56:23.135 --> 00:56:30.115
dude. He usually releases a blog put he releases, like, blog post that's pretty good about with the updates, but you should have it in the App Store too.
867
00:56:32.280 --> 00:56:34.840
868
00:56:35.560 --> 00:56:49.280
869
00:56:49.819 --> 00:56:56.375
Because he sent me a whole list of all the updates. It was the first thing I knew. This wasn't there. So I'm gonna move on now to the Bitcoin
870
00:56:56.755 --> 00:56:57.735
871
00:56:58.115 --> 00:56:58.615
uptech.
872
00:57:00.435 --> 00:57:03.255
Do you have any other apps that we may have missed?
873
00:57:07.130 --> 00:57:10.670
874
00:57:11.605 --> 00:57:12.505
875
00:57:13.045 --> 00:57:14.105
876
00:57:14.405 --> 00:57:14.645
The
877
00:57:15.365 --> 00:57:22.099
878
00:57:22.400 --> 00:57:23.220
It does suck.
879
00:57:23.839 --> 00:57:30.579
But I think we're gonna more and more see that happening. And I think a lot of projects that deal with stuff like this,
880
00:57:31.185 --> 00:57:34.885
881
00:57:35.745 --> 00:57:44.450
No. I I don't use Wasabi personally because I I don't really, I use JM. Well, on top of that, if for whatever reason, if you're using a privacy wallet that is
882
00:57:44.830 --> 00:57:47.650
literally over complying, you're paying change surveillance,
883
00:57:47.950 --> 00:57:50.715
it's fine for you. I would add that,
884
00:57:52.215 --> 00:57:56.155
so Wasabi 2.0, the reason I'm bringing it up is because there was a massive change,
885
00:57:56.455 --> 00:57:57.755
in how they do CoinJoin.
886
00:57:59.990 --> 00:58:10.105
You know, it was a fundamental change, and they implemented this new protocol, Wabi Sabi, which, like, on the surface, seems like a pretty cool improvement. You don't have a minimum amount anymore.
887
00:58:11.045 --> 00:58:13.385
The UX is cleaned up a lot,
888
00:58:15.380 --> 00:58:21.640
but it's complicated. Like, the the the method they're using is kind of obscure and complicated.
889
00:58:23.220 --> 00:58:33.914
But isn't it viewed? I I The lead the lead creator of Wacker. I have not, like, looked into it at all. Well, that's one of the issues they have is, like, a lot because they
890
00:58:34.520 --> 00:58:42.860
because they added this change surveillance element, they've lost a lot of their die hard contributors because they're all privacy focused people. Mhmm. So review is minimal.
891
00:58:43.240 --> 00:58:47.875
And then the creator of this Wabi Sabi protocol, which is what is the basis
892
00:58:48.335 --> 00:58:55.170
of Wasabi 2 point o's name, nothing much. He actually has me blocked on Twitter, but I have a lot of respect for that dude. And,
893
00:58:55.890 --> 00:58:59.589
he has a whole thread where he's like, this is unsafe to use.
894
00:59:00.185 --> 00:59:17.520
So Oh. If the creator of the fucking protocol is saying that they implemented it poorly and that he doesn't want anyone to use it, like, that's enough for me. Here's a question. Do they use the chain analysis stuff on the normal wallet use? No, right? Yeah. My understanding is all
895
00:59:17.835 --> 00:59:24.494
oh, no. No. It's only inputs for only, but it's it's for inputs of CoinJoin rounds. So if you're going into a CoinJoin round,
896
00:59:25.170 --> 00:59:32.550
it presumably gets sent to a chain surveillance firm, and then that chain surveillance firm basically gives them the nod yes or no.
897
00:59:32.895 --> 00:59:36.595
But on top of that, the way they've implemented Wabi Sabi, supposedly,
898
00:59:38.815 --> 00:59:40.995
extra data is getting leaked to
899
00:59:41.470 --> 00:59:47.490
any to the server and presumably the chain surveillance firm they're using as well. That's very important. Together and shit.
900
00:59:47.950 --> 00:59:50.770
901
00:59:52.815 --> 00:59:54.355
that a project will have
902
00:59:54.655 --> 00:59:55.215
a long,
903
00:59:55.775 --> 00:59:56.435
a long
904
00:59:56.735 --> 01:00:00.355
install base after adding chain services. Like they're struggling.
905
01:00:01.210 --> 01:00:03.470
No. I mean, of course. But, you know,
906
01:00:03.770 --> 01:00:05.630
my view on this that, like,
907
01:00:06.090 --> 01:00:07.150
the the problem is
908
01:00:07.610 --> 01:00:08.590
any project
909
01:00:09.154 --> 01:00:10.855
that has capturable people
910
01:00:11.954 --> 01:00:15.575
that does this kind of, like, service will eventually
911
01:00:15.875 --> 01:00:19.810
be presented with 2 choices, either go to jail or, like, you know,
912
01:00:20.350 --> 01:00:21.490
talk itself. Right?
913
01:00:22.030 --> 01:00:34.225
914
01:00:35.510 --> 01:00:40.490
915
01:00:41.030 --> 01:00:42.970
it's gonna be very hard to have users,
916
01:00:43.830 --> 01:00:46.485
doing coin join if they're getting,
917
01:00:47.265 --> 01:00:48.565
being sent to chain analytics.
918
01:00:49.185 --> 01:00:50.885
919
01:00:51.505 --> 01:00:56.560
920
01:00:57.560 --> 01:00:58.560
taste. But
921
01:01:00.140 --> 01:01:02.195
why is it that the the coin
922
01:01:02.915 --> 01:01:04.454
the the the mixing coin
923
01:01:04.835 --> 01:01:06.535
crowd is so complicated?
924
01:01:07.795 --> 01:01:09.335
It's beyond me.
925
01:01:09.875 --> 01:01:10.375
Anyways,
926
01:01:11.500 --> 01:01:15.680
927
01:01:18.220 --> 01:01:19.359
a little little bit
928
01:01:19.660 --> 01:01:20.160
crazy.
929
01:01:21.245 --> 01:01:23.025
I mean, you went through your own,
930
01:01:24.765 --> 01:01:30.660
like, feels like a long time ago, but what was it? Like, a year and a half ago, 2 years ago, the hardware wallet
931
01:01:31.200 --> 01:01:33.619
chaos between all the but, you know,
932
01:01:33.920 --> 01:01:35.540
933
01:01:35.840 --> 01:01:37.140
the the problem is
934
01:01:38.734 --> 01:01:41.075
I think it's different. The hardware wallet market
935
01:01:41.535 --> 01:01:44.914
never really had competition for a long time, and then it had competition.
936
01:01:45.670 --> 01:01:48.970
And some players that had a certain sort of, like,
937
01:01:49.750 --> 01:01:51.210
a standing in the market
938
01:01:51.590 --> 01:01:53.210
sort of fell, dropped.
939
01:01:53.670 --> 01:01:55.130
That caused a lot of drama.
940
01:01:57.025 --> 01:02:01.445
You know you know me on Twitter. I have, you know, I I I don't wear gloves.
941
01:02:03.089 --> 01:02:03.589
And,
942
01:02:04.690 --> 01:02:18.005
yeah, but it was different. I think it was more market based, and it was sort of like this market sort of finding itself on how to relate to each other in this competition as well, and it was also whatever you need to say to yourself. Exactly. That's what I taught myself.
943
01:02:18.705 --> 01:02:24.100
And but but he but as you said, it feels like it was a lifetime ago because it was all mostly resolved.
944
01:02:24.400 --> 01:02:28.340
Right? Some players still don't talk to each other, whatever, but like but the drama
945
01:02:28.640 --> 01:02:30.020
greatly went away.
946
01:02:30.575 --> 01:02:33.474
Right? Now on the coin joint space,
947
01:02:33.935 --> 01:02:45.109
948
01:02:46.025 --> 01:02:48.445
949
01:02:49.945 --> 01:02:51.165
I mean, you know, like
950
01:02:51.865 --> 01:02:55.700
well, anyways, I won't get into it. It's not the kind of podcast for that.
951
01:02:56.320 --> 01:02:59.520
952
01:03:00.000 --> 01:03:01.460
fair enough. We can continue.
953
01:03:03.415 --> 01:03:11.560
I'm glad we it was it was a big release. It was I think it was important to bring up Wasabi 2 point o. No. I I think, yeah, I think it's a good point. But don't use it.
954
01:03:12.280 --> 01:03:19.260
Yeah. I, I, yeah, I I didn't bring it up. I I guess it it's probably safe to use with a hardware signing device.
955
01:03:20.675 --> 01:03:30.040
Not not for mixing. If mixing is getting chain analysis, it's not safe to use. Coin the don't use it for coin join, but then also on top of that, by the way, they removed coin control,
956
01:03:30.500 --> 01:03:33.480
like so maybe it's not even good. Just use Sparrow.
957
01:03:33.860 --> 01:03:43.525
958
01:03:44.325 --> 01:03:47.870
there's no choice. No. Yeah. So let's talk about frequency here.
959
01:03:48.410 --> 01:03:57.465
This is best effort. I you know, maybe I'll do this, like, every couple weeks maybe. Like, 3 months. Maybe a month, you know, maybe it's next year, who knows, right?
960
01:03:59.045 --> 01:04:03.840
So now let's move on to another big part of the show, which is reading
961
01:04:04.860 --> 01:04:06.080
the Bitcoin OpTech
962
01:04:07.660 --> 01:04:08.160
newsletter.
963
01:04:09.180 --> 01:04:10.800
We're just gonna glance over.
964
01:04:11.375 --> 01:04:13.395
For people that don't know, the Bitcoin Ophthak
965
01:04:13.935 --> 01:04:15.235
is an incredible,
966
01:04:16.095 --> 01:04:16.595
incredible,
967
01:04:17.855 --> 01:04:21.109
968
01:04:22.210 --> 01:04:24.470
Sign up for the for the newsletters.
969
01:04:25.170 --> 01:04:26.390
970
01:04:27.010 --> 01:04:28.695
It it it really is phenomenal,
971
01:04:29.715 --> 01:04:30.855
really high signal,
972
01:04:31.715 --> 01:04:32.695
to noise there.
973
01:04:34.115 --> 01:04:35.815
Mike Schmidt, I I know.
974
01:04:36.320 --> 01:04:38.340
He's one of the main contributors there.
975
01:04:38.880 --> 01:04:39.380
And,
976
01:04:40.320 --> 01:04:44.020
Yeah. Schmidt is great. Yes. So without further ado,
977
01:04:44.720 --> 01:04:45.380
the news,
978
01:04:46.605 --> 01:04:49.825
full replaced by fee. So there's been some
979
01:04:51.005 --> 01:04:53.665
some talks and there is a couple PRs to remove,
980
01:04:54.525 --> 01:04:55.025
RBF,
981
01:04:55.990 --> 01:04:58.170
which is replaced by fee from the default.
982
01:04:59.190 --> 01:04:59.850
You know,
983
01:05:01.030 --> 01:05:04.170
as a as a sane citizen of Bitcoin,
984
01:05:04.515 --> 01:05:07.655
I don't get involved in these discussions. I still believe,
985
01:05:08.355 --> 01:05:09.655
RBF should be,
986
01:05:10.435 --> 01:05:11.415
on by default
987
01:05:12.195 --> 01:05:14.055
because replace by fee
988
01:05:15.160 --> 01:05:25.275
is essentially the default behavior of bitcoin itself. You can double spend your own transaction if you want to, so might as well make it into an official standardized thing and that's why I like our b f.
989
01:05:26.695 --> 01:05:29.415
So yeah, but there is a PR that's gotten some,
990
01:05:29.895 --> 01:05:33.195
some traction and you know what, it's probably gonna get merged.
991
01:05:35.119 --> 01:05:35.619
Hearts
992
01:05:35.920 --> 01:05:38.020
hearts bleed, that was a nice pun.
993
01:05:40.000 --> 01:05:40.980
Very good pun.
994
01:05:41.865 --> 01:05:43.405
So essentially there was a vulnerability,
995
01:05:44.185 --> 01:05:48.285
on the I believe it I haven't read through it, but, just
996
01:05:48.730 --> 01:05:52.590
from the pun and from the first paragraph here, I imagine is
997
01:05:53.210 --> 01:05:53.710
a
998
01:05:54.010 --> 01:05:57.790
similar to a power artificial analysis attack. They're trying to read
999
01:05:59.174 --> 01:06:01.434
the the computation happening on the chip,
1000
01:06:02.055 --> 01:06:04.075
and then they can essentially,
1001
01:06:04.934 --> 01:06:07.115
through a side channel, like, read
1002
01:06:07.480 --> 01:06:10.140
the private key being generated or used.
1003
01:06:12.680 --> 01:06:17.100
Even on this article here it says that, they don't know the extent
1004
01:06:17.545 --> 01:06:18.444
of the vulnerability.
1005
01:06:18.984 --> 01:06:22.285
And Bitcoin Core also does a lot of things to prevent,
1006
01:06:24.505 --> 01:06:25.005
attacks,
1007
01:06:25.545 --> 01:06:27.750
side channel attacks on on its,
1008
01:06:28.549 --> 01:06:38.045
private key computation. But anyone no one should have a private key on a computer anyways. You should have it on your hardware wallet. So this attack So your hardware wallet or computer?
1009
01:06:38.985 --> 01:06:39.485
1010
01:06:40.825 --> 01:06:48.119
1011
01:06:48.740 --> 01:06:49.720
1012
01:06:50.100 --> 01:06:51.480
1013
01:06:52.500 --> 01:06:56.355
go to air what is it? I have a I have a meme website for this.
1014
01:06:56.974 --> 01:07:07.360
1015
01:07:09.020 --> 01:07:12.045
1016
01:07:12.425 --> 01:07:12.925
airgapcomputer.com
1017
01:07:14.185 --> 01:07:18.980
1018
01:07:19.619 --> 01:07:33.605
Some of them in a bull market, some of the ones I registered are No. Not for the guillotine. No. I yeah. No. I think it adds up. It's like it adds up. But, you know, but, Matt, like, see, the thing is I've sold a few domains for for, like I've never I'm a Huddler.
1019
01:07:34.045 --> 01:07:39.640
1020
01:07:41.220 --> 01:07:45.640
in in my company. I do not have to explain my domain behavior to anyone internally,
1021
01:07:46.805 --> 01:07:52.105
because I have, paid ourselves over and over many, many times over. Was a really nice coup.
1022
01:07:53.740 --> 01:07:56.160
Yeah. I mean, that was a that was a good sail too.
1023
01:07:58.220 --> 01:08:00.080
1024
01:08:01.174 --> 01:08:02.075
pump and dump.
1025
01:08:03.095 --> 01:08:06.395
1026
01:08:06.775 --> 01:08:07.595
long story.
1027
01:08:09.779 --> 01:08:18.280
So hearts bleed, it would not be an issue at all if you use a harder wallet, so stop listening to the Wookie and buy yourself a cold card.
1028
01:08:18.875 --> 01:08:22.575
Yes, I'm biased on that one because I make it and it is better.
1029
01:08:23.195 --> 01:08:23.695
So
1030
01:08:24.155 --> 01:08:24.895
use that,
1031
01:08:25.435 --> 01:08:33.480
and if you still don't believe me, go to air gap computer dot com. He explains to you why you shouldn't use an air gap computer.
1032
01:08:34.955 --> 01:08:35.615
1033
01:08:36.235 --> 01:08:40.655
go verify MBK's claim by going to the site that MBK created.
1034
01:08:41.435 --> 01:08:41.935
1035
01:08:43.800 --> 01:08:45.739
What is it, trust and verify?
1036
01:08:47.239 --> 01:08:50.540
1037
01:08:51.914 --> 01:09:00.710
1038
01:09:01.090 --> 01:09:02.790
1039
01:09:04.050 --> 01:09:08.135
of public Bitcoin conversation out there that is oftentimes drunk. So
1040
01:09:09.735 --> 01:09:16.235
1041
01:09:17.690 --> 01:09:19.949
1042
01:09:20.650 --> 01:09:24.030
1043
01:09:24.625 --> 01:09:33.285
updates and I have to discuss the coin joint people, I'm gonna start having a serious drinking problem. Dude, people say to me, they're like, Matt, you seem, like, really tired
1044
01:09:33.730 --> 01:09:41.989
1045
01:09:43.045 --> 01:09:44.025
That's healthy.
1046
01:09:47.925 --> 01:09:52.270
1047
01:09:52.650 --> 01:09:55.390
time stamping design on open time stamp.
1048
01:09:55.850 --> 01:09:57.470
I didn't really follow it.
1049
01:09:58.410 --> 01:10:00.750
1050
01:10:01.315 --> 01:10:05.735
1051
01:10:07.395 --> 01:10:14.450
I recommend people go read the newsletter to get more on that. And also on the new Rito Anti Cyber method by Waxwing.
1052
01:10:15.150 --> 01:10:19.295
1053
01:10:20.255 --> 01:10:21.315
of flooding Bitcoin.
1054
01:10:22.175 --> 01:10:28.410
1055
01:10:28.970 --> 01:10:47.315
1056
01:10:47.630 --> 01:10:52.210
1057
01:10:52.510 --> 01:10:58.595
1058
01:10:59.455 --> 01:11:05.315
1059
01:11:05.660 --> 01:11:10.960
Good on him. We we we need the controver the controversy. That's how we find problems.
1060
01:11:12.835 --> 01:11:13.335
Alright,
1061
01:11:14.515 --> 01:11:20.055
notable changes to services and client software. You know, Azus added Taproot.
1062
01:11:21.110 --> 01:11:24.329
There you go, we missed that one on our, on our list.
1063
01:11:25.429 --> 01:11:26.250
So Evan,
1064
01:11:26.630 --> 01:11:33.735
we're very sorry. I well, actually, you know what? I didn't add Zeus to the list because I think their last update was a while back. So
1065
01:11:34.195 --> 01:11:36.170
1066
01:11:36.470 --> 01:11:42.250
January, like, I didn't know what to do. I know. I'm not perfect. I just started this. Well, anyway, Zeus is the single best,
1067
01:11:42.845 --> 01:11:44.465
way to interact with,
1068
01:11:45.005 --> 01:11:49.300
lightning node from your phone if you have a 247 lightning node at home.
1069
01:11:49.940 --> 01:11:58.760
Yes. There's basically nothing else that competes with it And, and that I'm aware of. And Evan is doing really good work. Shout out to to Kaludis.
1070
01:11:59.495 --> 01:12:01.675
1071
01:12:03.335 --> 01:12:04.155
Moving on,
1072
01:12:05.015 --> 01:12:07.515
1073
01:12:08.270 --> 01:12:10.930
1074
01:12:11.310 --> 01:12:12.530
Thanks, Ciao.
1075
01:12:15.070 --> 01:12:17.090
And then release candidates for
1076
01:12:17.665 --> 01:12:21.845
LNG. Carries HWI on his back. Right? It's just him. It's just him.
1077
01:12:22.385 --> 01:12:27.680
Another one man there's a lot of one man legends. No. But, you know, but to be fair though, people do contribute,
1078
01:12:28.620 --> 01:12:29.440
to HWI.
1079
01:12:29.900 --> 01:12:31.920
Like, a lot of the hardware wallets themselves
1080
01:12:32.220 --> 01:12:33.840
have their people help
1081
01:12:35.565 --> 01:12:38.465
implement the changes to HWI for their new releases.
1082
01:12:39.165 --> 01:12:40.625
So it is collaborative,
1083
01:12:40.925 --> 01:12:44.350
but but h but, yes, Chow does carry that on his back.
1084
01:12:44.990 --> 01:12:50.370
And he is the kind of person who does test everything and review everything, right, that's why it takes a little longer.
1085
01:12:52.030 --> 01:12:55.075
Alright, so on the lightning front, of course every,
1086
01:12:56.095 --> 01:12:56.595
the
1087
01:12:57.135 --> 01:12:58.835
3 of the 4 main releases
1088
01:13:00.175 --> 01:13:00.925
of of,
1089
01:13:01.430 --> 01:13:02.810
oh no, sorry. LND
1090
01:13:03.190 --> 01:13:04.330
had a main release.
1091
01:13:06.150 --> 01:13:08.090
LDK had another main release.
1092
01:13:12.885 --> 01:13:13.445
BDK has,
1093
01:13:14.085 --> 01:13:21.180
experimental support for Taproot, descriptors, p s p t. BDK is a very cool project. It does help a lot of devs
1094
01:13:21.800 --> 01:13:24.940
implement a wallet without knowing how to implement a wallet,
1095
01:13:25.480 --> 01:13:27.180
so very bullish on the library.
1096
01:13:27.545 --> 01:13:31.804
1097
01:13:32.425 --> 01:13:50.565
Yeah. Well, I mean, writing a wallet is a lot of work, and these guys are doing that with a lot of features at the same time, which is just exponentially harder. But basically, the idea of BDK is, like, it's the base. It could be the base for any new wallet. Right? And then, like, people can build on top of it and and make whatever changes they wanna make, but they don't have to, like,
1098
01:13:51.140 --> 01:14:07.070
they don't have to build from scratch the core logic. Right? Yeah. But none of this stuff is plug and play. Right? You still have to there's a lot of of glue and a lot of stuff you need to write. Supposed to make it easier at least. It does. And then the idea is that that'll bring more competition among wallets and we'll have better wallets and everyone will win.
1099
01:14:07.790 --> 01:14:09.570
Yeah. And it's fun, dude.
1100
01:14:10.670 --> 01:14:12.290
By Block, formerly Square.
1101
01:14:13.150 --> 01:14:17.265
Yes. And so is LDK, right? LDK, which is the same idea
1102
01:14:17.805 --> 01:14:19.745
but but but What about Lightning Core?
1103
01:14:21.485 --> 01:14:24.225
That was an unfortunate choice of name. Core Lightning.
1104
01:14:24.590 --> 01:14:25.090
1105
01:14:25.470 --> 01:14:27.650
I I preferred the one with sea lightning,
1106
01:14:29.230 --> 01:14:41.945
1107
01:14:42.730 --> 01:14:52.455
1108
01:14:53.795 --> 01:14:59.335
I don't think people who listen to a podcast about Bitcoin software updates, would have to be warned about Blockchain.info.
1109
01:14:59.795 --> 01:15:07.810
1110
01:15:08.750 --> 01:15:10.370
1111
01:15:10.905 --> 01:15:11.405
1112
01:15:12.264 --> 01:15:17.145
gotta cover it. You gotta cover it just in case. Notable code and documentation changes,
1113
01:15:18.340 --> 01:15:18.500
1114
01:15:19.220 --> 01:15:21.160
well, in their week, not my week.
1115
01:15:22.100 --> 01:15:24.600
Bitcoin Core, Core Lightning, essentially all the projects.
1116
01:15:24.980 --> 01:15:25.720
And then,
1117
01:15:29.765 --> 01:15:36.320
oh, h w I yeah. H w I, edit the single sig support for back 32 m addresses,
1118
01:15:37.500 --> 01:15:39.280
which helps it tap root.
1119
01:15:39.740 --> 01:15:40.240
Okay.
1120
01:15:41.180 --> 01:15:41.680
Alright.
1121
01:15:42.060 --> 01:15:42.560
Now
1122
01:15:45.625 --> 01:15:48.285
I have a few more things here on the list.
1123
01:15:49.945 --> 01:15:56.760
So next would be, which I did it in the wrong order. There's Blix Wallet. We didn't cover Blix Wallet.
1124
01:15:58.420 --> 01:15:59.960
1125
01:16:00.659 --> 01:16:02.855
1126
01:16:04.275 --> 01:16:05.574
1127
01:16:05.954 --> 01:16:06.775
and iPhone.
1128
01:16:07.474 --> 01:16:07.974
Okay.
1129
01:16:08.514 --> 01:16:09.815
So it's really cool. Wallet.
1130
01:16:10.560 --> 01:16:15.940
Okay. I'll I'll check that. Well, how do you spell it? Be the what? B l I x t.
1131
01:16:16.320 --> 01:16:20.545
B l I x t. Okay. I wouldn't be surprised if they add NFC.
1132
01:16:21.565 --> 01:16:28.065
It looks like they have it on their road map, but it's not on it yet. Yeah. B l I x t
1133
01:16:28.440 --> 01:16:28.940
1134
01:16:30.360 --> 01:16:32.060
Okay. I'll check that one out.
1135
01:16:32.360 --> 01:16:33.980
1136
01:16:34.680 --> 01:16:35.900
Mercury Wallet.
1137
01:16:36.315 --> 01:16:38.735
There's been some good updates to Mercury Wallet.
1138
01:16:39.675 --> 01:16:42.335
The last Splixd Wallet update was on
1139
01:16:44.210 --> 01:16:45.270
March 4th,
1140
01:16:46.450 --> 01:16:47.510
v 0.5.1.
1141
01:16:49.730 --> 01:16:53.055
Alright. And then Mercury Wallet has been I've seen a lot of options
1142
01:16:53.515 --> 01:16:55.935
1143
01:16:56.235 --> 01:16:58.095
1144
01:17:00.150 --> 01:17:00.650
swaps
1145
01:17:01.349 --> 01:17:01.849
wallet.
1146
01:17:02.469 --> 01:17:04.650
It does coin swaps on a state chain.
1147
01:17:05.670 --> 01:17:16.075
It's a privacy focused wallet that uses Okay. Uses a a state chain implementation that's, like, not as good as, I guess what was it Thompson who came up with the original state chains
1148
01:17:16.830 --> 01:17:17.330
proposal?
1149
01:17:18.350 --> 01:17:26.784
Nah, I can't remember. Whoever came up with the original one, it required some kind of protocol change, so they figured out a way to do, like, a slightly less good version
1150
01:17:27.485 --> 01:17:29.425
without any kind of protocol change.
1151
01:17:29.804 --> 01:17:32.385
And you basically switch into their state chain,
1152
01:17:33.610 --> 01:17:37.869
which has reduced custodial risk. But if they're the other counterparty, like, if they're malicious,
1153
01:17:39.050 --> 01:17:42.030
then they could take your money, but if they're not, it requires
1154
01:17:42.635 --> 01:17:43.455
them plus
1155
01:17:43.915 --> 01:17:53.190
one of the participants to collude together to take your money. That's pretty good. But as a result a decent set of trade off? Yeah. As a result, it's off chain, and then you can do all these swaps,
1156
01:17:53.970 --> 01:17:54.870
to gain privacy
1157
01:17:55.250 --> 01:17:59.725
without paying transaction fees, and then you withdraw back to the chain.
1158
01:18:00.105 --> 01:18:00.605
Nice.
1159
01:18:02.345 --> 01:18:03.005
Cool project.
1160
01:18:03.385 --> 01:18:05.565
Yeah. And they've been making a lot of
1161
01:18:06.619 --> 01:18:08.000
lot of progress lately.
1162
01:18:08.540 --> 01:18:10.320
1163
01:18:11.099 --> 01:18:14.239
No. Not really. You don't so you don't have anything to hide?
1164
01:18:14.755 --> 01:18:15.735
1165
01:18:17.554 --> 01:18:18.375
fuck you.
1166
01:18:19.074 --> 01:18:27.590
Okay. Privacy is one of the most important topics in in Bitcoin today, and hopefully It's a great segue. Good to see so many tools
1167
01:18:27.969 --> 01:18:30.135
coming out that are focused on it.
1168
01:18:30.534 --> 01:18:35.434
1169
01:18:36.775 --> 01:18:38.235
It's not really a segue.
1170
01:18:40.450 --> 01:18:40.950
Okay.
1171
01:18:41.410 --> 01:18:41.910
So,
1172
01:18:42.770 --> 01:18:43.270
apparently,
1173
01:18:43.730 --> 01:18:45.270
armory is planning,
1174
01:18:47.195 --> 01:18:49.015
is planning Taproot.
1175
01:18:49.555 --> 01:18:55.495
1176
01:18:56.820 --> 01:18:59.880
1177
01:19:00.340 --> 01:19:00.840
anymore.
1178
01:19:03.219 --> 01:19:07.235
Aqua, which is green, let's see here. Who who implemented
1179
01:19:07.855 --> 01:19:08.675
send to
1180
01:19:09.054 --> 01:19:12.675
to Taproot? Is that B coin, Bitcoin Core, Bitcoin Knots,
1181
01:19:14.014 --> 01:19:15.155
Blockstream Green,
1182
01:19:17.320 --> 01:19:18.860
Bitcoin wallet for Android,
1183
01:19:19.240 --> 01:19:20.060
Blue Wallet,
1184
01:19:21.320 --> 01:19:23.500
Breeze didn't and it won't,
1185
01:19:24.225 --> 01:19:24.725
says
1186
01:19:26.465 --> 01:19:27.205
no. Btc.com
1187
01:19:27.825 --> 01:19:28.725
question mark.
1188
01:19:29.905 --> 01:19:30.405
Caravan
1189
01:19:30.840 --> 01:19:34.460
plan. Caravan is from Unchained Capital. Casa plan,
1190
01:19:36.119 --> 01:19:36.940
Sea Lightning,
1191
01:19:38.574 --> 01:19:39.074
yes.
1192
01:19:40.015 --> 01:19:40.515
Coinomi
1193
01:19:41.135 --> 01:19:43.635
Core lightning, you mean? No. Coin nami.
1194
01:19:44.255 --> 01:19:46.675
1195
01:19:47.510 --> 01:19:50.090
1196
01:19:50.630 --> 01:19:53.290
1197
01:19:54.310 --> 01:19:56.570
1198
01:19:57.545 --> 01:19:58.605
Okay. Electrum,
1199
01:19:59.945 --> 01:20:00.605
yes. Exodus,
1200
01:20:01.304 --> 01:20:02.925
yes. Fully noted, yes.
1201
01:20:03.945 --> 01:20:05.005
Guarda wallet,
1202
01:20:05.385 --> 01:20:06.284
question mark.
1203
01:20:06.989 --> 01:20:08.770
Joy Market, yes. LND,
1204
01:20:09.150 --> 01:20:09.650
Cumming.
1205
01:20:10.270 --> 01:20:11.330
Mun, yes.
1206
01:20:11.790 --> 01:20:15.585
It's Moon. I always say Mun. I don't know why. Moon with 2 u's. Yes.
1207
01:20:16.145 --> 01:20:19.045
Mycelium question mark. Nunchuck, yes.
1208
01:20:19.425 --> 01:20:20.805
Phoenix question mark.
1209
01:20:21.265 --> 01:20:21.765
Samurai,
1210
01:20:22.145 --> 01:20:22.645
yes.
1211
01:20:23.440 --> 01:20:23.940
Sparrow,
1212
01:20:24.320 --> 01:20:24.820
yes.
1213
01:20:25.120 --> 01:20:27.700
Specter, yes. Trust wallet, yes.
1214
01:20:28.560 --> 01:20:32.985
Uniblo, never heard of that, yes. Wallets of satoshi, yes.
1215
01:20:33.365 --> 01:20:34.825
Wasabi wallet, yes.
1216
01:20:36.085 --> 01:20:38.025
Hardware wallet support is a little trickier,
1217
01:20:38.900 --> 01:20:41.239
but it's essentially just signing to the address.
1218
01:20:41.699 --> 01:20:42.199
So,
1219
01:20:42.659 --> 01:20:47.239
Trezor, yes. Ledger, yes. Keep key, don't use it, and it doesn't.
1220
01:20:48.085 --> 01:20:49.864
Bitbox, yes. Trezor
1221
01:20:50.245 --> 01:20:51.465
with Electrom, yes.
1222
01:20:53.205 --> 01:20:56.105
Bitbox, yes. Keep key, question mark.
1223
01:20:56.880 --> 01:20:59.460
Arcos, question mark. Code card, yes.
1224
01:21:00.239 --> 01:21:01.540
Wallet, question mark.
1225
01:21:03.040 --> 01:21:04.340
Seed signer plan,
1226
01:21:05.994 --> 01:21:06.494
tangent
1227
01:21:07.114 --> 01:21:08.014
question mark,
1228
01:21:09.675 --> 01:21:10.574
block stream,
1229
01:21:10.954 --> 01:21:11.454
yes,
1230
01:21:12.074 --> 01:21:13.534
and keystone plan
1231
01:21:14.370 --> 01:21:15.110
for q122
1232
01:21:16.050 --> 01:21:16.550
so
1233
01:21:17.490 --> 01:21:18.870
I guess it didn't happen.
1234
01:21:21.010 --> 01:21:21.830
Web wallets,
1235
01:21:22.635 --> 01:21:23.135
coinapult,
1236
01:21:23.675 --> 01:21:26.895
1237
01:21:27.355 --> 01:21:28.975
Yes. Okay. Continue.
1238
01:21:29.810 --> 01:21:32.550
1239
01:21:33.170 --> 01:21:36.230
Blockchain dotcom, planned. That's weird.
1240
01:21:36.925 --> 01:21:38.045
They just did,
1241
01:21:38.605 --> 01:21:45.140
hierarchical deterministic like the other day. They never did business. They did that segue like a couple months ago. Something like that too.
1242
01:21:46.100 --> 01:21:48.840
Fireblocks planned. Fireblocks is a big deal,
1243
01:21:49.460 --> 01:21:56.955
because they are the back end of a lot of the exchanges. So if you want to send from an exchange to a top root address, you they would probably need to support that.
1244
01:21:57.895 --> 01:22:05.110
1245
01:22:05.730 --> 01:22:07.430
1246
01:22:08.290 --> 01:22:09.910
Hold the transactions, yes.
1247
01:22:10.825 --> 01:22:11.325
Coinb.
1248
01:22:12.105 --> 01:22:12.605
In,
1249
01:22:13.145 --> 01:22:15.325
question mark or the question mark.
1250
01:22:16.425 --> 01:22:17.805
Do I go through the exchanges?
1251
01:22:18.425 --> 01:22:18.925
Nah,
1252
01:22:20.030 --> 01:22:20.930
Bitcoin ATM,
1253
01:22:21.470 --> 01:22:23.330
nah. Blockchain Explorers.
1254
01:22:24.670 --> 01:22:26.210
1255
01:22:28.405 --> 01:22:31.145
1256
01:22:31.844 --> 01:22:36.470
1257
01:22:37.330 --> 01:22:39.670
1258
01:22:40.050 --> 01:22:42.470
1259
01:22:44.105 --> 01:22:50.605
like, that's on the receiver. Like, there's no I guess, except for privacy reasons, there's no reason to to
1260
01:22:51.330 --> 01:22:56.150
to, be upset if a merchant or a person is using an old address
1261
01:22:56.450 --> 01:23:02.545
because the fee savings are dependent on this the fee savings are dependent on the sender, not the receiver. So That's right.
1262
01:23:03.005 --> 01:23:09.080
1263
01:23:10.180 --> 01:23:10.920
1264
01:23:12.980 --> 01:23:13.880
1265
01:23:15.140 --> 01:23:16.760
Going to the next topic,
1266
01:23:17.495 --> 01:23:18.955
Bitcoin signing devices.
1267
01:23:20.935 --> 01:23:21.435
So
1268
01:23:21.815 --> 01:23:23.355
we started this little initiative,
1269
01:23:23.975 --> 01:23:31.240
that many people have sort of like pushed here and there, but I figured it needed a domain, right? You need to buy domains otherwise things don't exist.
1270
01:23:31.860 --> 01:23:33.080
So sign in device.com
1271
01:23:35.114 --> 01:23:39.054
1272
01:23:39.355 --> 01:23:43.054
like you bought that from a previous owner, right? No. No. It was available.
1273
01:23:43.520 --> 01:23:51.780
It was just available for like the usual like dotcom price? Yeah. You just bought it? Yeah. Well, really my price cost. Like I get it for cheaper.
1274
01:23:52.445 --> 01:23:55.265
That's crazy signing device.com was available.
1275
01:23:55.645 --> 01:23:56.145
1276
01:23:57.325 --> 01:23:57.825
Kudos.
1277
01:23:58.365 --> 01:24:00.705
Yeah. So so we made a little website.
1278
01:24:02.070 --> 01:24:02.890
Hardware wallets
1279
01:24:03.350 --> 01:24:04.330
are not wallets,
1280
01:24:04.790 --> 01:24:05.930
they're signing devices.
1281
01:24:06.630 --> 01:24:08.730
Wallets have UTXO information,
1282
01:24:09.030 --> 01:24:10.410
block data information,
1283
01:24:10.875 --> 01:24:14.735
they can construct transactions. Hardware wallets don't know anything, they just sign
1284
01:24:15.195 --> 01:24:15.695
transactions.
1285
01:24:16.155 --> 01:24:17.775
While some do better than others,
1286
01:24:18.315 --> 01:24:18.815
but
1287
01:24:20.180 --> 01:24:28.600
essentially they cannot construct a transaction because they don't have blockchain data. So that's why the p s b t comes from the software wallet to your bitcoin signing device.
1288
01:24:29.835 --> 01:24:33.934
So the more people we can get on the train of calling bitcoin harder wallets
1289
01:24:34.635 --> 01:24:40.000
bitcoin signing devices, the better its gonna be for the round on the next bitcoin hype cycle.
1290
01:24:41.260 --> 01:24:44.480
Because right now it's just us left here, right, that bitcoin crashed.
1291
01:24:44.940 --> 01:24:45.440
So
1292
01:24:46.695 --> 01:24:47.195
there's
1293
01:24:47.575 --> 01:24:49.675
probably nobody that cares about this
1294
01:24:50.135 --> 01:24:51.515
around for now.
1295
01:24:52.135 --> 01:24:55.640
Sorry, nobody that doesn't care about this is around for now,
1296
01:24:56.980 --> 01:24:57.380
but,
1297
01:24:58.260 --> 01:25:03.665
yeah, on the next cycle let's try to get people saying sign in devices and move on from this. We have
1298
01:25:04.284 --> 01:25:12.930
gone through the trouble of going on the cold card website and adding sign in devices everywhere on the text to start properly confusing people with the new term.
1299
01:25:15.150 --> 01:25:16.850
Next here, one more domain,
1300
01:25:18.135 --> 01:25:18.635
bitcoinbinary.org.
1301
01:25:20.615 --> 01:25:24.795
I wanted to give a little update on this one. It's a child project of mine.
1302
01:25:26.449 --> 01:25:28.550
So I went to like a website
1303
01:25:29.010 --> 01:25:29.510
where
1304
01:25:29.969 --> 01:25:35.349
notable members of the community that can code and can build projects from source code
1305
01:25:35.795 --> 01:25:37.575
would post a video of them
1306
01:25:38.115 --> 01:25:40.935
doing the deterministic build. Right?
1307
01:25:41.395 --> 01:25:43.415
Proving on video that they did it.
1308
01:25:44.660 --> 01:25:48.280
So that people that can't have one more source of truth.
1309
01:25:49.140 --> 01:25:53.515
Is it better than them themselves building? Of course not, but it's one more source
1310
01:25:54.555 --> 01:25:55.055
truth.
1311
01:25:55.755 --> 01:25:57.375
And we had a bounty
1312
01:25:58.075 --> 01:26:00.095
for somebody to automate builds,
1313
01:26:01.800 --> 01:26:02.300
and,
1314
01:26:03.080 --> 01:26:05.100
and sort of like we can get around
1315
01:26:05.560 --> 01:26:07.820
of builds, to at least task if they build,
1316
01:26:09.175 --> 01:26:10.375
automatically, and,
1317
01:26:11.015 --> 01:26:23.640
I forgot the name of the of the person, the NIM who did it, but, he claimed the bounty, and now when there's new versions we can get the website to build it with a little video showing that it was built,
1318
01:26:24.980 --> 01:26:29.785
on top of community members to do it. And it's such a simple little thing
1319
01:26:30.565 --> 01:26:33.145
that that exponentially improves their security,
1320
01:26:34.005 --> 01:26:36.505
that, I don't know, it just felt like it needed to exist.
1321
01:26:38.710 --> 01:26:39.850
1322
01:26:41.110 --> 01:26:41.610
1323
01:26:41.989 --> 01:26:46.090
If only they would mention that the other podcast that does
1324
01:26:46.655 --> 01:26:47.395
the releases?
1325
01:26:48.575 --> 01:26:51.875
1326
01:26:54.150 --> 01:26:54.650
1327
01:26:55.110 --> 01:26:55.429
So,
1328
01:26:55.989 --> 01:27:01.610
the only mention about price which is not gonna be mentioned about price is an update on BitcoinTreasuries
1329
01:27:02.150 --> 01:27:02.650
dotnet.
1330
01:27:05.595 --> 01:27:08.335
Essentially, the miners all dumped half their coins.
1331
01:27:10.770 --> 01:27:15.190
The the big publicly traded miners, so, so that was reflected on bitcointreasuries.net.
1332
01:27:17.090 --> 01:27:19.830
And mister Saylor has not added more publicly
1333
01:27:22.065 --> 01:27:25.844
to his huddle. So, so we have a lot of entries but they've been pretty much not updated.
1334
01:27:28.640 --> 01:27:31.700
And I think probably Celsius went to 0, so
1335
01:27:32.400 --> 01:27:33.300
there you go.
1336
01:27:35.645 --> 01:27:39.825
1337
01:27:41.085 --> 01:27:42.465
1338
01:27:43.485 --> 01:27:44.305
But yeah.
1339
01:27:45.050 --> 01:27:45.870
Okay. Lastly,
1340
01:27:46.250 --> 01:27:50.910
which I was going to do earlier, but I'll do it now some of the Quaintite updates.
1341
01:27:52.035 --> 01:27:55.415
We have one more product on the on the cards line
1342
01:27:55.875 --> 01:28:02.520
that we haven't talked much about it because we just sort of invented, and then we sort of went through the trouble of getting it out.
1343
01:28:03.220 --> 01:28:04.680
It's called the Sats chip,
1344
01:28:05.860 --> 01:28:06.840
and it's essentially
1345
01:28:08.020 --> 01:28:09.505
a a real NFT,
1346
01:28:10.845 --> 01:28:12.465
the way it was supposed to be.
1347
01:28:13.565 --> 01:28:17.345
It's a way for you to add a chip to a piece of art
1348
01:28:18.420 --> 01:28:18.920
signed
1349
01:28:19.780 --> 01:28:21.080
with Bitcoin Signature,
1350
01:28:24.020 --> 01:28:28.645
and uses sort of like the OpenDive model so you can't really take the privacy of it. Is it a Poincare product?
1351
01:28:29.025 --> 01:28:32.804
Yeah. It's essentially based on the Sats card and the TapCigner.
1352
01:28:33.505 --> 01:28:34.610
1353
01:28:35.330 --> 01:28:50.695
1354
01:28:51.160 --> 01:28:55.179
So we wanted to find a a more a better way of doing that.
1355
01:28:55.640 --> 01:28:56.140
And
1356
01:28:57.239 --> 01:28:58.060
we leveraged
1357
01:28:58.875 --> 01:29:01.375
all the firmware that we wrote for TapSigner
1358
01:29:01.915 --> 01:29:04.494
in a way that works for the artists so that,
1359
01:29:04.875 --> 01:29:09.600
essentially, they can they can sign a picture of the art and all the metadata
1360
01:29:10.460 --> 01:29:11.840
and it's a Bitcoin signature,
1361
01:29:12.140 --> 01:29:13.040
it's really cool.
1362
01:29:14.425 --> 01:29:16.125
And there's even a little,
1363
01:29:16.505 --> 01:29:18.685
we released a little command line tool today
1364
01:29:19.545 --> 01:29:21.405
so that they can do that, and
1365
01:29:21.705 --> 01:29:23.005
then there's a little gallery
1366
01:29:23.330 --> 01:29:24.550
on, satschip.com/gallery
1367
01:29:26.449 --> 01:29:27.750
where they can push it.
1368
01:29:29.090 --> 01:29:33.275
I hope to get a few of these on Crypto Graffiti's hands soon and
1369
01:29:34.695 --> 01:29:36.635
and get, get that ball rolling.
1370
01:29:37.895 --> 01:29:39.755
1371
01:29:42.160 --> 01:29:42.820
the NFT
1372
01:29:43.280 --> 01:29:44.260
craze was
1373
01:29:45.520 --> 01:29:50.635
horrible to see, but the, like, the actual physical Bitcoin art is really, really cool.
1374
01:29:51.415 --> 01:29:53.114
1375
01:29:53.495 --> 01:29:54.155
you know,
1376
01:29:54.900 --> 01:29:59.080
this is the difference, right, between buying a JPEG that anyone can copy,
1377
01:29:59.540 --> 01:30:03.075
right, and buying a physical piece of art with a certificate
1378
01:30:03.695 --> 01:30:08.915
1379
01:30:09.390 --> 01:30:12.130
like, I I don't think the physical art is gonna outperform Bitcoin.
1380
01:30:12.510 --> 01:30:15.730
Of course not. To look at. We don't buy it. It's a cool concept.
1381
01:30:16.325 --> 01:30:20.985
1382
01:30:21.925 --> 01:30:31.620
1383
01:30:32.375 --> 01:30:34.954
in Nashville, and we have all the walls are,
1384
01:30:36.695 --> 01:30:37.835
are Bitcoin artists,
1385
01:30:38.215 --> 01:30:49.540
and they're available for purchase. Like, we'd we're basically acting as, like, an art gallery. We don't actually own them. You know, Crypto Graffiti was very generous in, in, working with us on the first Satskar
1386
01:30:50.455 --> 01:30:55.835
1387
01:30:56.455 --> 01:30:59.120
And, we're very, very grateful to him for that.
1388
01:30:59.760 --> 01:31:02.100
And He's just a great dude in general. Yep.
1389
01:31:02.560 --> 01:31:05.300
We we think that, you know, if we can
1390
01:31:05.680 --> 01:31:09.585
make Bitcoin products full of, like, cool independent art, then we
1391
01:31:10.125 --> 01:31:11.425
we are better for that.
1392
01:31:13.645 --> 01:31:15.585
Alright. What else is on my list here?
1393
01:31:16.440 --> 01:31:19.020
The the fully noted NFC beta I mentioned.
1394
01:31:19.880 --> 01:31:20.380
Oh,
1395
01:31:20.680 --> 01:31:25.100
this is coming to cold card. People have asked. We think it's awesome.
1396
01:31:25.805 --> 01:31:26.705
It's a BIP85
1397
01:31:27.405 --> 01:31:28.465
based passwords.
1398
01:31:29.725 --> 01:31:31.665
So we do the BIP85
1399
01:31:32.045 --> 01:31:36.179
seeds now, right, so you can use it to populate your your
1400
01:31:37.280 --> 01:31:42.420
phone app with, with a seed that's terminalistically built so you only have one backup.
1401
01:31:42.925 --> 01:31:44.945
But you're gonna be able to also generate passwords,
1402
01:31:45.804 --> 01:31:48.465
for things, and we're gonna emulate a keyboard
1403
01:31:48.925 --> 01:31:50.145
for input. So,
1404
01:31:50.525 --> 01:31:52.145
if you have your non
1405
01:31:53.030 --> 01:31:56.810
deep cold storage cold card, your just play cold card, your second one,
1406
01:31:57.750 --> 01:32:01.050
you can plug it in and press a button and it will inject
1407
01:32:01.425 --> 01:32:01.925
the
1408
01:32:02.625 --> 01:32:05.925
pip85 password into an input box on the computer.
1409
01:32:07.184 --> 01:32:09.445
That's pretty awesome for
1410
01:32:10.630 --> 01:32:11.370
things like,
1411
01:32:12.070 --> 01:32:13.770
SSH protected keys,
1412
01:32:15.190 --> 01:32:21.385
or, like, you know, big interesting things, like things that you don't care. Sorry. Things that you care about the security,
1413
01:32:21.765 --> 01:32:26.585
not like things that the the service on the other side already has a copy anyways. Right?
1414
01:32:28.750 --> 01:32:31.170
So, yeah, so pretty excited about that one.
1415
01:32:32.830 --> 01:32:36.130
What else? The block clock micro reservation started.
1416
01:32:36.909 --> 01:32:38.290
This is a little
1417
01:32:38.895 --> 01:32:41.475
a bleep version of the block clock
1418
01:32:42.015 --> 01:32:42.515
mini,
1419
01:32:45.295 --> 01:32:47.565
and it's gonna be a $150
1420
01:32:49.520 --> 01:32:53.700
and same functionality, but just tiny little screen. It's very, very cute.
1421
01:32:54.720 --> 01:32:56.020
1422
01:32:56.655 --> 01:32:58.195
1423
01:32:58.655 --> 01:33:00.355
I will commit to dates
1424
01:33:01.215 --> 01:33:08.270
once we finalize the front board because we we have it. Right? Like, it works. It's all good, and the firmware is pretty much done.
1425
01:33:09.210 --> 01:33:12.190
The thing is we're still playing with the front plate design,
1426
01:33:14.625 --> 01:33:18.165
and, you know, the world that it is just takes a little longer to do the rounds
1427
01:33:18.545 --> 01:33:21.845
of of iteration with the the PCB makers.
1428
01:33:22.950 --> 01:33:23.450
So
1429
01:33:24.150 --> 01:33:30.895
I just don't wanna promise dates and not keep them. So as soon as I have a better sense of the date, then we'll we'll say it.
1430
01:33:31.935 --> 01:33:37.475
They they we got a lot of reservations. People really like that idea, so pretty excited about it.
1431
01:33:39.110 --> 01:33:40.090
1432
01:33:41.590 --> 01:33:46.330
people have just wanted a cheaper block clock for a while. I mean, just because the block clock's fucking awesome.
1433
01:33:46.685 --> 01:33:52.385
Yeah. I mean, it's a big way of thinking about it. Realize, like, the block clock mini, which is, like, the famous one now
1434
01:33:53.085 --> 01:33:57.800
because, like, Dorsey and, like, the ex Thai prime minister and shit have it in their background.
1435
01:33:58.659 --> 01:33:59.639
I should probably congratulations
1436
01:34:00.020 --> 01:34:00.679
on that.
1437
01:34:01.139 --> 01:34:23.340
That was pretty cool. The Thai the Thai dick that's he wasn't I don't think he was a dictator. I don't know. But the Thai president who got, thrown out, was on an interview, and he had the Block Lock Mini behind. But that was born out of the original Block Lock was ridiculously expensive. Right? What was it? Like, 6 k or something? It was essentially a Bitcoin. It was 5 grand when Bitcoin was 5 grand. Yeah.
1438
01:34:24.475 --> 01:34:37.200
Well, you know, but that one had it was it costed a lot to make. So we So is this part of the show just a big CoinKite ad just to end it? Is that what's going on right now? Well, don't worry. We're gonna get to you. Are you gonna send me a payment? To your shills.
1439
01:34:38.860 --> 01:34:40.320
I I just I
1440
01:34:40.835 --> 01:34:48.295
1441
01:34:49.555 --> 01:34:50.455
1442
01:34:52.340 --> 01:34:55.080
1443
01:34:56.020 --> 01:34:59.720
The man spent 2 hours it's a essentially feature length
1444
01:35:00.095 --> 01:35:01.555
tutorial of cold card.
1445
01:35:02.975 --> 01:35:04.995
I mean it's seriously awesome,
1446
01:35:05.775 --> 01:35:09.900
that that tutorial was pretty cool. I feel like he deserves a shout out for that.
1447
01:35:11.320 --> 01:35:15.100
And we do have the coin kite stable coin now, which is the gift cards.
1448
01:35:16.725 --> 01:35:18.585
I think this is it on my list.
1449
01:35:19.525 --> 01:35:21.865
Matt, do you have anything to shield?
1450
01:35:23.500 --> 01:35:24.000
1451
01:35:24.300 --> 01:35:26.160
It's been a pleasure. This is
1452
01:35:26.460 --> 01:35:27.440
a fun rep.
1453
01:35:27.980 --> 01:35:30.615
1454
01:35:31.655 --> 01:35:42.620