BR086 - Electrum, Wasabi, Bitkey, Bitcoin Safe, Spark, Bitcoin Keeper, OP_CAT Privacy, FROST X nostr, btcd FindAndDelete bug + MORE ft. Rijndael & Ben

WEBVTT
1
00:00:01.840 --> 00:00:06.080
Hello and welcome to the Bitcoin.review podcast, where we explore developments
2
00:00:06.080 --> 00:00:09.180
and projects with the people who actually make them happen.
3
00:00:09.500 --> 00:00:13.100
The show is supported by Pod 2.0, SaaT Streaming and CoinKite.
4
00:00:13.360 --> 00:00:15.340
If you're a new listener, I'm NVK.
5
00:00:15.620 --> 00:00:19.200
I run CoinKite, where we've been helping people secure their Bitcoins for over
6
00:00:19.200 --> 00:00:19.620
a decade.
7
00:00:20.100 --> 00:00:22.920
We make the cold card and fun products like the Block Clock.
8
00:00:23.120 --> 00:00:25.680
You can find more information about it on CoinKite.com.
9
00:00:29.420 --> 00:00:31.659
Hello and welcome to the jungle.
10
00:00:32.080 --> 00:00:32.500
Just kidding.
11
00:00:32.740 --> 00:00:38.180
Welcome to Bitcoin.review. Today I have with me Mr. Ben the Car Man.
12
00:00:39.200 --> 00:00:40.500
Yo, yo, good to be back.
13
00:00:41.120 --> 00:00:43.860
I have his co-worker, Rundell.
14
00:00:44.640 --> 00:00:45.840
Hello, good to be here.
15
00:00:46.960 --> 00:00:52.320
And man, it's been a minute since we since we've had a list because the Nostril
16
00:00:52.320 --> 00:00:57.080
Rising series took over, like, I think probably like three weeks of releases
17
00:00:57.080 --> 00:00:58.700
and there might still more coming out.
18
00:00:59.300 --> 00:01:00.740
People really like that one.
19
00:01:00.960 --> 00:01:02.080
Different kind of thing.
20
00:01:02.780 --> 00:01:06.620
Not so nerdy, but it's nice to have a list again.
21
00:01:06.800 --> 00:01:07.640
It's been a while.
22
00:01:08.160 --> 00:01:11.860
Yeah, I think there's what, like seven episodes of Nostril Rising out?
23
00:01:12.240 --> 00:01:13.400
Like there's a bunch of them.
24
00:01:13.640 --> 00:01:15.160
Oh, so then there is definitely more coming.
25
00:01:15.160 --> 00:01:17.200
I think we recorded nine or ten.
26
00:01:17.680 --> 00:01:17.880
Oh, wow.
27
00:01:18.560 --> 00:01:20.180
Yeah, we're probably going to record a few more.
28
00:01:21.020 --> 00:01:26.540
It's the best evergreen content to to give to a Nostril Derangement Syndrome
29
00:01:26.540 --> 00:01:27.740
suffering human being.
30
00:01:29.300 --> 00:01:31.320
And Nostril is rising.
31
00:01:32.560 --> 00:01:35.780
All right, what else on the housekeeping here?
32
00:01:36.000 --> 00:01:42.160
We have some new tutorials for CodeCard and we are opening an office in Latin
33
00:01:42.160 --> 00:01:42.880
America.
34
00:01:44.220 --> 00:01:47.340
Location unknown and undisclosed.
35
00:01:48.120 --> 00:01:49.500
That's a bad way of putting it.
36
00:01:49.980 --> 00:01:52.900
We added Bitcoin per share to the Bitcoin treasuries.
37
00:01:53.620 --> 00:01:56.180
There is the Grumpy Surfer stats card.
38
00:01:56.280 --> 00:02:00.300
And people really like my energy reading company stuff.
39
00:02:02.300 --> 00:02:02.920
OK, yeah.
40
00:02:03.180 --> 00:02:04.580
OK, can we get to the commits now?
41
00:02:04.980 --> 00:02:05.580
There you go.
42
00:02:05.680 --> 00:02:06.860
Vulnerability disclosures.
43
00:02:08.440 --> 00:02:16.100
CVE 2024 38365 BTCD find and delete bug disclosure.
44
00:02:17.840 --> 00:02:18.620
And then there was.
45
00:02:19.640 --> 00:02:21.540
Do you guys follow that one?
46
00:02:21.660 --> 00:02:25.460
Was that the one that you just you could just crash for or no?
47
00:02:26.440 --> 00:02:31.900
If I remember right, I think this was the one where I think this was like
48
00:02:31.900 --> 00:02:34.140
related to CodeSeparator.
49
00:02:34.900 --> 00:02:40.300
Yeah, it's a bug in Bitcoin or BTCD, like the implementation of Bitcoin.
50
00:02:41.100 --> 00:02:46.100
And yeah, like CodeSeparator pre-segwit is like super complicated.
51
00:02:46.580 --> 00:02:49.820
And there's like a niche case where they implemented it wrong.
52
00:02:50.460 --> 00:02:53.080
So it would cause like a full on chain split.
53
00:02:53.700 --> 00:02:55.560
I mean, you know, no one really runs BTCD.
54
00:02:55.820 --> 00:03:01.220
So it's not a huge risk, but it is like, you know, one of the reasons
55
00:03:01.220 --> 00:03:05.540
why we don't do multiple invitations of Bitcoin cores, because like this is
56
00:03:05.540 --> 00:03:07.920
very hard to replicate.
57
00:03:09.160 --> 00:03:13.880
CodeSeparator and legacy script is just an unending source of pain and
58
00:03:13.880 --> 00:03:14.480
suffering, right?
59
00:03:14.540 --> 00:03:19.880
Like there's a bunch of like relay rules to not let you send legacy
60
00:03:19.880 --> 00:03:25.280
transactions with like multiple code separators in them, because it basically
61
00:03:25.280 --> 00:03:32.140
causes like a cache miss for the SIG hash cache, like you have to recompute the
62
00:03:32.140 --> 00:03:34.240
whole signature hash and then re-sign it.
63
00:03:34.480 --> 00:03:39.420
And so there's a lot of just like gross behavior that can be enabled by abusing
64
00:03:39.420 --> 00:03:40.240
opcode separator.
65
00:03:41.640 --> 00:03:47.200
Yeah, I think like maybe people don't appreciate because normally like a lot of
66
00:03:47.200 --> 00:03:49.160
protocols just have a spec, right?
67
00:03:49.480 --> 00:03:54.720
And then people just follow the spec and you can build your implementation from
68
00:03:54.720 --> 00:03:55.320
the spec.
69
00:03:55.320 --> 00:04:00.320
I mean, like for example, Nostra is like that, you follow the NIPs, right, and
70
00:04:00.320 --> 00:04:05.260
you implement each NIP and boom, you're like, you know, it works.
71
00:04:05.700 --> 00:04:10.260
And if you have bugs, that's your problem, you know, like with Bitcoin it's a
72
00:04:10.260 --> 00:04:14.480
little bit more complicated than that because there is no spec, you know,
73
00:04:14.640 --> 00:04:17.920
there's the code is the protocol, the protocol is the code and that's the
74
00:04:17.920 --> 00:04:18.760
consensus code.
75
00:04:19.279 --> 00:04:21.400
So it makes it very tricky.
76
00:04:22.040 --> 00:04:27.560
In a way, it was kind of like an maybe an accidental good thing because it
77
00:04:27.560 --> 00:04:31.820
forced everybody to remain in a hard consensus without too much like bike
78
00:04:31.820 --> 00:04:32.120
shedding.
79
00:04:33.580 --> 00:04:41.480
But it's tricky, you know, it's either you squirt like a fox, there really is
80
00:04:41.480 --> 00:04:43.300
no way around that.
81
00:04:43.840 --> 00:04:48.000
I like Luke Jr.'s approach, you know, as controversial as it could be.
82
00:04:48.000 --> 00:04:52.380
It's like, you know, you just have like a more conservative version of Core
83
00:04:52.380 --> 00:04:56.320
with tiny little preferences that may cause some drama.
84
00:04:56.480 --> 00:04:59.940
Or, you know, Peter's got LibreRelay, which goes the other direction, right?
85
00:05:00.000 --> 00:05:03.080
He takes Core and then he relaxes a bunch of restrictions.
86
00:05:03.400 --> 00:05:05.640
And so it's like a more liberal version of Core.
87
00:05:06.020 --> 00:05:06.280
Yes.
88
00:05:06.880 --> 00:05:11.540
Yeah, I don't know if I want a liberal version of Core for my consensus, for
89
00:05:11.540 --> 00:05:13.800
my validation of my coins, that could be tricky.
90
00:05:14.660 --> 00:05:18.320
Yeah, I mean, the good news is that it's only relay policy that gets touched.
91
00:05:18.480 --> 00:05:20.020
It's none of the consensus bits.
92
00:05:20.620 --> 00:05:25.320
So the worst thing that happens is you have a more accurate mempool and you can
93
00:05:25.320 --> 00:05:27.040
like more accurately estimate fees.
94
00:05:27.500 --> 00:05:27.620
Right.
95
00:05:28.360 --> 00:05:30.900
I guess for that purpose, it's not bad.
96
00:05:31.240 --> 00:05:31.640
Good thing.
97
00:05:32.360 --> 00:05:32.580
All right.
98
00:05:32.600 --> 00:05:39.360
Another disclosure, CV 2024-35-202, remotely rechargeable assertion crash in
99
00:05:39.360 --> 00:05:40.280
Bitcoin Core.
100
00:05:41.020 --> 00:05:44.500
A high severity vulnerability in Bitcoin Core allows daggers to remotely crash
101
00:05:44.500 --> 00:05:44.720
nodes.
102
00:05:45.660 --> 00:05:50.840
We talked, I think, about this maybe briefly in a recent episode, like I think
103
00:05:50.840 --> 00:05:55.140
like people attribute a little bit too much intensity to this ones of like
104
00:05:55.140 --> 00:05:55.860
crashing cores.
105
00:05:56.100 --> 00:05:56.740
Like, OK, great.
106
00:05:56.860 --> 00:06:00.140
I mean, it's a problem for the Lightning people, but like it's not a real
107
00:06:00.140 --> 00:06:05.140
problem for like self-validating Bitcoin economic nodes.
108
00:06:05.760 --> 00:06:06.820
What's the worst that can happen?
109
00:06:06.900 --> 00:06:07.780
Somebody crashes their node.
110
00:06:09.140 --> 00:06:13.500
Yeah, it's like more concern if like someone knows they can crash like a
111
00:06:13.500 --> 00:06:17.640
certain like person or entities node of like, oh, I'm going to attack Coinbase
112
00:06:17.640 --> 00:06:19.560
and just take down all their nodes repeatedly.
113
00:06:20.480 --> 00:06:23.920
Yeah, or like being able to do it on demand and say, like, as part of
114
00:06:23.920 --> 00:06:25.580
this attack, I'm going to crash this node.
115
00:06:26.200 --> 00:06:32.200
Yeah, I had like a prod 24.1 node that I haven't upgraded in years because
116
00:06:32.200 --> 00:06:33.120
it's just doing its job.
117
00:06:33.240 --> 00:06:36.260
And this is the one that got me to finally like upgrade it.
118
00:06:36.760 --> 00:06:40.520
So I'm finally running like a more modern version of Core for that node.
119
00:06:41.500 --> 00:06:45.020
OK, I support people running multiple versions.
120
00:06:45.200 --> 00:06:48.840
I think it's the, especially if you're a big economical actor, like, you know,
121
00:06:48.860 --> 00:06:49.960
just run many versions.
122
00:06:50.840 --> 00:06:52.140
It keeps everybody honest.
123
00:06:53.660 --> 00:07:00.280
And all right, Crux, a bug in Crux beta version at 24.10, point beta 6
124
00:07:00.280 --> 00:07:03.180
to beta 8 affects BIP85 password generation.
125
00:07:03.380 --> 00:07:07.540
Users should record and replace passwords created in this version as they may
126
00:07:07.540 --> 00:07:07.900
be in cry.
127
00:07:07.920 --> 00:07:09.120
That's the problem.
128
00:07:10.880 --> 00:07:17.120
And we just had the BIP85 drama with Core 2 with the BIP that somebody changed
129
00:07:17.120 --> 00:07:20.980
the BIP should have been marked as final, but it wasn't.
130
00:07:21.780 --> 00:07:25.860
So anyways, upgrade your Crux and replace those passwords.
131
00:07:26.780 --> 00:07:30.260
Good for them coming out to this immediately as they found out.
132
00:07:31.040 --> 00:07:32.200
Love that project.
133
00:07:32.740 --> 00:07:38.700
Nostar client Coracle has been unintentionally sending user session data to
134
00:07:38.700 --> 00:07:42.020
BugsNag when recording errors.
135
00:07:42.200 --> 00:07:43.220
Yes, I saw that one.
136
00:07:44.060 --> 00:07:48.980
Yeah, so HodaBod said that, you know, like he immediately deleted, you know,
137
00:07:49.080 --> 00:07:50.720
the logs and all that stuff.
138
00:07:50.960 --> 00:07:52.560
But brutal.
139
00:07:53.520 --> 00:07:57.960
Dear JavaScript developer, get closer to the speaker.
140
00:07:58.960 --> 00:08:02.220
Stop using cloud tools on your shit.
141
00:08:03.140 --> 00:08:07.700
You know, like I know all these things make promises about, you know, security
142
00:08:07.700 --> 00:08:08.480
and all these things.
143
00:08:08.520 --> 00:08:11.300
But the problem is you never know when you have a bug.
144
00:08:12.020 --> 00:08:14.620
Same reason why we do, you know, air gap.
145
00:08:14.780 --> 00:08:19.660
Do we know our code is good and very strong and, you know, our USB isolation
146
00:08:19.660 --> 00:08:20.220
is great?
147
00:08:20.320 --> 00:08:20.620
Yes.
148
00:08:20.660 --> 00:08:22.260
But we don't know when we have a bug.
149
00:08:22.900 --> 00:08:23.300
Right.
150
00:08:24.220 --> 00:08:28.480
You know, looking at this, it looks like private keys got logged out to BugsNag
151
00:08:28.480 --> 00:08:28.820
also.
152
00:08:29.680 --> 00:08:34.700
So yes, you know, a good outcome out of this would be if it pushes on.
153
00:08:35.559 --> 00:08:39.500
I know there's a spec out for like delegating a child key, right?
154
00:08:39.640 --> 00:08:43.000
So if there's more, if this yeah, if this pushes on that, that would be great
155
00:08:43.000 --> 00:08:47.440
because everybody who had kind of their root key and BugsNag, you've just got
156
00:08:47.440 --> 00:08:48.960
to assume that it's compromised at this point.
157
00:08:50.460 --> 00:08:55.660
Sorry, you know, it's yeah, I have to narrate for everybody because this is
158
00:08:55.660 --> 00:08:56.620
radio, not video.
159
00:08:57.240 --> 00:09:00.680
NVK is sitting here with no shirt on, literally lobbing coconuts into the
160
00:09:00.680 --> 00:09:03.060
jungle while we're talking about BugsNag.
161
00:09:05.420 --> 00:09:08.580
It's it's I am contributing to the biome of the forest.
162
00:09:09.560 --> 00:09:13.180
Listen, if you handle private keys, stop using cloud shit.
163
00:09:13.760 --> 00:09:14.700
That's one thing.
164
00:09:15.500 --> 00:09:18.940
I know, you know, all these tools help you develop your code.
165
00:09:18.940 --> 00:09:22.400
Better and get, you know, like improve UX and those things.
166
00:09:22.500 --> 00:09:26.720
But like if you handle private keys, please don't use cloud shit.
167
00:09:27.060 --> 00:09:30.120
Only use your client's local environment.
168
00:09:31.240 --> 00:09:37.480
The other thing is there is a Frost spec and implementation coming to Noster.
169
00:09:37.920 --> 00:09:42.080
So there was going to be a bounty or there is a bounty for the Frost
170
00:09:42.080 --> 00:09:42.700
implementation.
171
00:09:43.920 --> 00:09:48.340
And somebody implemented, I think, before the bounty came out.
172
00:09:48.340 --> 00:09:55.500
So if you are a Frost cryptographer that could review or audit Frost, which
173
00:09:55.500 --> 00:09:59.880
probably is just Jonah Schneller listening to this podcast, maybe one more
174
00:09:59.880 --> 00:10:00.360
person.
175
00:10:01.160 --> 00:10:06.600
Anyways, anyone that could help audit that implementation, please get in touch.
176
00:10:06.720 --> 00:10:09.380
I'll get in touch with the show and I'll put you in touch with the right
177
00:10:09.380 --> 00:10:12.140
person because it's not public yet.
178
00:10:12.580 --> 00:10:16.540
So I don't want to say who or what or how, but do get in touch.
179
00:10:16.540 --> 00:10:19.140
And, you know, I will send you the right direction.
180
00:10:19.900 --> 00:10:24.240
You know, Nick Farrow did a project like a year and a half ago called Froster.
181
00:10:24.380 --> 00:10:26.380
And it was a Frost signer for Noster.
182
00:10:27.060 --> 00:10:30.560
He and I made a two of three and then it was like a little mini
183
00:10:30.560 --> 00:10:31.360
shitpost out.
184
00:10:32.320 --> 00:10:35.440
So whoever's working on this, I would definitely ping Nick Farrow.
185
00:10:35.540 --> 00:10:38.520
He probably has thoughts and opinions and he has some experience implementing
186
00:10:38.520 --> 00:10:38.760
it.
187
00:10:39.160 --> 00:10:40.520
He's definitely a good person to talk to.
188
00:10:41.120 --> 00:10:41.820
Oh, that's great.
189
00:10:42.220 --> 00:10:42.800
There you go.
190
00:10:43.280 --> 00:10:47.300
And I'm sure that the only people who care about this problem and care about
191
00:10:47.300 --> 00:10:48.940
the implementation as well, listen to the show.
192
00:10:49.540 --> 00:10:53.300
So Venn diagram completed.
193
00:10:54.180 --> 00:10:54.820
All right.
194
00:10:55.040 --> 00:10:59.320
Next is Bitcoin software releases and project updates.
195
00:11:00.760 --> 00:11:09.920
Electrum version 4.5.7. You add historical exchange rate providers, lightning,
196
00:11:10.300 --> 00:11:19.260
fix, update, update fee right away, Qt desktop, GUI, version 4.5.6, new ad
197
00:11:19.260 --> 00:11:26.680
support, testnet 4, set stricter Unix permissions for log files, QML, GUI
198
00:11:26.680 --> 00:11:32.200
updated on Android and hardware wallets, a cold card, export multi-sig wallet
199
00:11:32.200 --> 00:11:40.560
to cold card over USB, Trezor ad support for new device safe 5, Ledger ad
200
00:11:40.560 --> 00:11:48.660
support for new device flax, CLI RPC changed, require a password for LNP and
201
00:11:48.660 --> 00:11:49.780
similar comments.
202
00:11:50.400 --> 00:11:55.780
Electrum releases a reproducibly built version into the official F3 depository.
203
00:11:57.540 --> 00:12:03.200
It's like the macaroni client that predates all the other clients.
204
00:12:03.880 --> 00:12:06.460
That's still like, you know, still around.
205
00:12:07.560 --> 00:12:11.460
Yeah, I just love that Electrum is still adding support for new stuff and
206
00:12:11.460 --> 00:12:12.580
putting out new features.
207
00:12:12.820 --> 00:12:16.900
It's been it's just this like, you know, thing that's always been there.
208
00:12:17.000 --> 00:12:18.020
It's incredibly useful.
209
00:12:18.760 --> 00:12:22.520
You know, for a while when I was doing wallet dev stuff and we wanted to
210
00:12:22.520 --> 00:12:27.280
be able to test against other wallets on Signet, it was one of like the easiest
211
00:12:27.280 --> 00:12:28.360
things to use.
212
00:12:28.400 --> 00:12:29.540
It just works out of the box.
213
00:12:29.600 --> 00:12:31.300
It's a fantastic piece of software.
214
00:12:31.300 --> 00:12:35.520
You know, make all the wallets have Excel like UX.
215
00:12:36.220 --> 00:12:37.760
Yeah, you know, it really is.
216
00:12:37.920 --> 00:12:38.140
Yeah, totally.
217
00:12:38.780 --> 00:12:44.600
I find Electrum works very well if you have sub, I'd say sub a thousand UTXOs
218
00:12:45.140 --> 00:12:46.080
addresses there.
219
00:12:46.580 --> 00:12:50.280
If you go over there, it starts to really, really become a problem.
220
00:12:50.380 --> 00:12:52.000
For some reason, it doesn't index.
221
00:12:52.100 --> 00:12:56.640
So if any Electrum developers listening, for some reason, when you have like
222
00:12:56.640 --> 00:13:01.400
past ten, fifty thousand addresses there, even though they're all old and
223
00:13:01.400 --> 00:13:03.740
unused, it doesn't index.
224
00:13:04.020 --> 00:13:05.300
It doesn't keep the index.
225
00:13:05.640 --> 00:13:07.820
When you quit, it seems to toss it out.
226
00:13:08.340 --> 00:13:14.820
So instead of like maybe rechecking on what's when the index is already there
227
00:13:15.400 --> 00:13:18.360
slowly on the background or something, it kind of like makes everything
228
00:13:18.360 --> 00:13:21.160
disappear and it goes through.
229
00:13:21.280 --> 00:13:24.020
It goes faster, but it goes through everything again.
230
00:13:24.380 --> 00:13:26.160
It makes it like nearly unusable.
231
00:13:27.020 --> 00:13:34.300
Also, for anybody who's stuck out there, figure out how to dump your XPRIV
232
00:13:34.300 --> 00:13:38.300
because Electrum still hates BIP39 seeds.
233
00:13:38.920 --> 00:13:39.060
Yep.
234
00:13:40.120 --> 00:13:41.640
Let's see if I can find it here.
235
00:13:41.800 --> 00:13:42.020
Oh, yeah.
236
00:13:43.140 --> 00:13:43.700
Electrum.
237
00:13:43.960 --> 00:13:45.840
I saved the command here somewhere.
238
00:13:47.380 --> 00:13:48.240
There you go.
239
00:13:48.640 --> 00:13:54.580
So for anybody who's stuck with a seed on Electrum, I can't help with the seed
240
00:13:54.580 --> 00:13:56.460
itself, but I can help with the XPRIV.
241
00:13:57.120 --> 00:13:58.960
It was not easy finding this.
242
00:13:59.580 --> 00:14:04.400
So it's just wallet.keystore.get underscore root underscore.
243
00:14:05.340 --> 00:14:06.340
I know that's for the fingerprint.
244
00:14:07.720 --> 00:14:08.720
Come on.
245
00:14:08.780 --> 00:14:09.740
Did I lose it?
246
00:14:09.820 --> 00:14:11.260
I had to read it somewhere.
247
00:14:12.440 --> 00:14:13.060
Unbelievable.
248
00:14:14.420 --> 00:14:14.860
No.
249
00:14:17.480 --> 00:14:18.420
Never mind.
250
00:14:19.120 --> 00:14:20.220
And it's gone.
251
00:14:20.600 --> 00:14:21.920
I'll put on the show notes.
252
00:14:22.000 --> 00:14:23.860
I'll find it and put it in the show notes.
253
00:14:24.120 --> 00:14:25.100
That's so funny.
254
00:14:25.720 --> 00:14:26.100
Brutal.
255
00:14:27.240 --> 00:14:29.820
Anyways, going back to the list here.
256
00:14:31.380 --> 00:14:36.760
All right, Nunchuck Android version 1.9.53 revamped home screen and user
257
00:14:36.760 --> 00:14:40.980
onboarding experience allow users to clone a decoy wallet from existing
258
00:14:40.980 --> 00:14:41.680
wallets.
259
00:14:42.440 --> 00:14:45.280
I think that's true for the current iOS version as well.
260
00:14:46.540 --> 00:14:49.460
Bitcoin Keeper tap signer experience overhauled.
261
00:14:49.980 --> 00:14:53.100
Download encrypted backups of your tap signer.
262
00:14:53.100 --> 00:14:58.400
Change the cards pin and unblock the cards if rate limited.
263
00:14:59.560 --> 00:15:04.340
Key signer improvement, associate contacts with signing keys, better options
264
00:15:04.340 --> 00:15:10.420
for exporting and securing keys, wallet data management, wallet import and
265
00:15:10.420 --> 00:15:13.100
export options, improve file sharing the app.
266
00:15:13.860 --> 00:15:19.940
Version 1.2.15 is canary wallet, even with recovery key flexibility to only
267
00:15:19.940 --> 00:15:23.540
create vaults and hide, delete them for security reasons.
268
00:15:23.860 --> 00:15:28.160
I'm just thrilled that there's more wallets that are supporting kind of the
269
00:15:28.160 --> 00:15:31.880
control plane parts of the tap signer, like pin management and like because,
270
00:15:32.100 --> 00:15:33.880
yes, I love my tap signer.
271
00:15:34.040 --> 00:15:37.520
I use it in kind of some funky ways, but for a while it's like, all
272
00:15:37.520 --> 00:15:41.700
right, I've got to have my USB NFC reader to be able to do things like
273
00:15:41.700 --> 00:15:44.360
pin reset if if like this one app goes away.
274
00:15:44.460 --> 00:15:48.340
So it's nice to have multiple apps supporting it makes it more usable.
275
00:15:48.340 --> 00:15:49.600
It does.
276
00:15:50.360 --> 00:15:51.680
You know, NFC is not easy.
277
00:15:52.280 --> 00:15:53.860
I think that's a huge part of the problem.
278
00:15:54.700 --> 00:15:58.760
A lot of like app devs have a hard time, but I think it slowly will
279
00:15:58.760 --> 00:16:04.000
sort of become the norm, especially when BigKey maybe opens up to other
280
00:16:04.000 --> 00:16:04.460
wallets.
281
00:16:05.260 --> 00:16:06.920
Maybe that also helps push a little bit.
282
00:16:08.420 --> 00:16:15.100
Yeah, and also Ben, Ben is a clown world, Ben is now full time on Bitcoin
283
00:16:15.100 --> 00:16:15.920
Keeper.
284
00:16:16.740 --> 00:16:17.740
So it's a good thing.
285
00:16:18.340 --> 00:16:19.300
We're everywhere.
286
00:16:20.280 --> 00:16:20.860
I know, right?
287
00:16:21.900 --> 00:16:23.740
Does that explain the clone quality?
288
00:16:25.920 --> 00:16:27.140
What's it written in?
289
00:16:28.140 --> 00:16:29.140
I'm just kidding.
290
00:16:29.500 --> 00:16:30.040
TypeScript.
291
00:16:30.380 --> 00:16:31.260
It's JavaScript.
292
00:16:33.160 --> 00:16:37.980
Is it a bin allowed to claim their business if they called in JavaScript?
293
00:16:38.900 --> 00:16:39.660
Yeah, that's OK.
294
00:16:40.300 --> 00:16:42.520
I've had to do my own fair share of JavaScript.
295
00:16:42.820 --> 00:16:43.780
It's a big tent, Ben.
296
00:16:44.040 --> 00:16:44.400
Yeah.
297
00:16:45.240 --> 00:16:46.260
All bins are fungible.
298
00:16:46.980 --> 00:16:47.340
OK.
299
00:16:49.140 --> 00:16:56.980
BISC 2 version 2.1.2 optimized reputation system, consolidated chat rooms based
300
00:16:56.980 --> 00:17:04.619
on user feedback, Wasabi wallet version 2.3.0.0, ASTAR integration, better BTC
301
00:17:04.619 --> 00:17:10.060
amount formatting, more insight into the transaction, beta payment in CoinJoin
302
00:17:10.060 --> 00:17:13.500
RPC only, add TransferSafe 5 and CodeCard Q support.
303
00:17:14.819 --> 00:17:16.960
The payments inside the CoinJoin is cool.
304
00:17:16.960 --> 00:17:22.619
I know Max had been talking about that for years, like since like 2020 or
305
00:17:22.619 --> 00:17:22.900
something.
306
00:17:23.420 --> 00:17:28.460
And it's cool to see it like actually finally happening where you can like
307
00:17:28.460 --> 00:17:32.180
basically register an input and then you just give a token to someone and they
308
00:17:32.180 --> 00:17:32.960
register an output.
309
00:17:33.180 --> 00:17:37.340
So you don't even know what's address the user received it on that you're
310
00:17:37.340 --> 00:17:37.900
sending to.
311
00:17:38.480 --> 00:17:39.440
Oh, that's cool.
312
00:17:39.560 --> 00:17:40.180
That is cool.
313
00:17:40.480 --> 00:17:40.720
Yeah.
314
00:17:41.320 --> 00:17:45.920
What's the state of the coordinator on Wasabi?
315
00:17:46.060 --> 00:17:47.100
Because there is one, right?
316
00:17:47.140 --> 00:17:50.980
And they don't charge fees so that they don't go to jail or something like
317
00:17:50.980 --> 00:17:51.280
that.
318
00:17:51.980 --> 00:17:53.740
I don't think they're running one anymore.
319
00:17:53.920 --> 00:17:55.080
It's just like an open market.
320
00:17:55.520 --> 00:17:59.860
But yeah, but there kind of is no market because none of them can charge fees.
321
00:18:00.820 --> 00:18:01.300
Right.
322
00:18:01.820 --> 00:18:06.640
I mean, we're going to have to go back to a make or taker model for
323
00:18:06.640 --> 00:18:07.240
these things.
324
00:18:07.360 --> 00:18:08.920
There really is no way around it.
325
00:18:10.080 --> 00:18:11.620
Tornado Cash is still running too, right?
326
00:18:13.040 --> 00:18:14.840
Yeah, Tornado Cash is still running.
327
00:18:15.500 --> 00:18:19.500
Like all the front ends are all enforcing sanctions.
328
00:18:20.160 --> 00:18:23.980
So in theory, you know, you can write like a contract or write a transaction
329
00:18:23.980 --> 00:18:26.100
that it just hits the contract directly.
330
00:18:26.260 --> 00:18:27.760
But I think in practice, nobody does.
331
00:18:27.920 --> 00:18:29.800
Like it's still running, but the volume is very low.
332
00:18:30.480 --> 00:18:30.700
Right.
333
00:18:31.680 --> 00:18:36.620
I mean, listen, the liquidity of privacy is going to go somewhere, right?
334
00:18:36.660 --> 00:18:38.000
Because the demand is there.
335
00:18:38.580 --> 00:18:42.060
Maybe there are already other tools out there that we just won't find out until
336
00:18:42.060 --> 00:18:46.660
it becomes a little bit more open to people who are not that invested into the
337
00:18:46.660 --> 00:18:48.720
privacy needs due to their needs.
338
00:18:49.560 --> 00:18:53.360
That's normally how it happens to a lot of these tools is they're like, oh,
339
00:18:53.440 --> 00:18:55.140
look, I just found out about this project.
340
00:18:55.260 --> 00:18:59.240
It's been running for the last five years quietly and it has a lot of money
341
00:18:59.240 --> 00:18:59.580
in it.
342
00:18:59.640 --> 00:18:59.740
Right.
343
00:18:59.800 --> 00:19:02.220
Like that's often how these things go.
344
00:19:03.580 --> 00:19:07.140
Can we do a Tornado Cash like thing if Opcat comes about?
345
00:19:08.180 --> 00:19:09.520
I don't know.
346
00:19:09.660 --> 00:19:14.160
I've been trying to think through what that would look like.
347
00:19:14.280 --> 00:19:19.360
I think you could build a bridge to some other execution environment where you
348
00:19:19.360 --> 00:19:21.180
could do a Tornado Cash like thing.
349
00:19:21.440 --> 00:19:25.280
I was trying to think of how you would do Tornado Cash on like L1 and
350
00:19:25.280 --> 00:19:30.300
what you kind of want to be able to do is put money into some construct
351
00:19:30.300 --> 00:19:35.900
and get out like some proof that you put the money in and then be able
352
00:19:35.900 --> 00:19:37.580
to come along later and claim that.
353
00:19:38.540 --> 00:19:40.520
You know, you might be able to do that.
354
00:19:40.700 --> 00:19:43.560
It's a little bit different with like UTXOs than like the account model because
355
00:19:43.560 --> 00:19:47.280
you can kind of point to individual outputs and say, this is where the money
356
00:19:47.280 --> 00:19:47.740
came from.
357
00:19:48.280 --> 00:19:52.120
So I think what you'd want to be able to do is almost have it be
358
00:19:52.120 --> 00:19:56.580
like a coin swap where I put some money into one UTXO and then I can
359
00:19:56.580 --> 00:19:58.380
withdraw it from a different UTXO.
360
00:19:58.660 --> 00:20:04.600
But the trick there is you need to have some state mechanism to either make
361
00:20:04.600 --> 00:20:09.200
sure that then I can't go and withdraw money from other UTXOs or when I put
362
00:20:09.200 --> 00:20:13.220
money in, I need to have that linked somehow with the one that I can withdraw
363
00:20:13.220 --> 00:20:13.620
from.
364
00:20:13.780 --> 00:20:15.780
But you need to do that in like a non-public way.
365
00:20:16.220 --> 00:20:19.080
So I think there's some like ways to do it, but it's not going to look
366
00:20:19.080 --> 00:20:20.060
like Tornado Cash.
367
00:20:20.160 --> 00:20:21.500
It's going to be something different.
368
00:20:22.040 --> 00:20:30.260
You know, like for the upcat enjoyers and the upcat peddlers and the upcat...
369
00:20:30.260 --> 00:20:31.440
What other groups are there?
370
00:20:31.540 --> 00:20:32.080
There's a few.
371
00:20:32.600 --> 00:20:33.720
Many breeds of cats.
372
00:20:33.720 --> 00:20:34.640
Haters.
373
00:20:35.560 --> 00:20:36.120
Haters.
374
00:20:36.220 --> 00:20:37.040
There's definitely some haters.
375
00:20:37.740 --> 00:20:37.880
Yeah.
376
00:20:37.960 --> 00:20:38.800
No, I know the haters.
377
00:20:39.020 --> 00:20:39.420
It's OK.
378
00:20:39.620 --> 00:20:41.300
Like hate, it's a waste of time.
379
00:20:42.200 --> 00:20:43.880
It can be a disenjoyer.
380
00:20:44.480 --> 00:20:45.020
That's OK.
381
00:20:45.460 --> 00:20:46.780
Or disrespector.
382
00:20:46.940 --> 00:20:48.500
I support disrespectors too.
383
00:20:48.780 --> 00:20:52.380
That's another very reasonable and helpful kind of people.
384
00:20:53.160 --> 00:20:58.700
Anyways, if upcat was shown to create an interesting new privacy model for
385
00:20:58.700 --> 00:21:04.760
coin, it wouldn't be CoinJoin per se, but, you know, for some kind of a privacy
386
00:21:04.760 --> 00:21:10.440
enhancing coin swap, I think would be a lot more...
387
00:21:10.440 --> 00:21:12.460
Would bring more people to the upcat tent.
388
00:21:13.060 --> 00:21:16.000
That could be the thing that actually pushes over, right?
389
00:21:16.060 --> 00:21:22.700
Because the privacy folks are quite passionate about the privacy tools.
390
00:21:23.040 --> 00:21:28.860
So maybe that brings about enough support to even get a fork sooner than later.
391
00:21:29.700 --> 00:21:36.340
Anyways, I want to see privacy done on-chain properly without coordinators.
392
00:21:36.900 --> 00:21:37.820
That needs to happen.
393
00:21:38.300 --> 00:21:39.660
For now, use JoyMarkets.
394
00:21:40.320 --> 00:21:46.780
Yeah, I made a prototype coin swap implementation like a year ago using adapter
395
00:21:46.780 --> 00:21:49.400
signatures and taproot keys.
396
00:21:49.640 --> 00:21:50.320
And that's pretty cool.
397
00:21:50.480 --> 00:21:55.460
Like you can do a two-party coin swap that just looks like, you know, I
398
00:21:55.460 --> 00:21:59.260
make two transactions and NBK makes two transactions, but behind the scenes,
399
00:21:59.360 --> 00:22:00.980
we've actually swapped GTXOs.
400
00:22:01.340 --> 00:22:04.300
And you can do that with like adapter signatures in a really privacy-preserving
401
00:22:04.300 --> 00:22:04.620
way.
402
00:22:04.980 --> 00:22:09.900
I think what you want to do is you need it to be multi-party or
403
00:22:09.900 --> 00:22:14.500
like multi-participant so that you don't have like liquidity problems.
404
00:22:15.160 --> 00:22:20.040
So figuring out how to make that be a, you know, end-party swap, I think
405
00:22:20.040 --> 00:22:21.360
is like the real unlock.
406
00:22:21.600 --> 00:22:23.880
And yeah, maybe there's a way we can do that with Covenants.
407
00:22:24.140 --> 00:22:24.560
That'd be cool.
408
00:22:24.560 --> 00:22:29.800
Well, just wave your hands for now and make it that, you know, UpCat fixes
409
00:22:29.800 --> 00:22:30.320
everything.
410
00:22:31.860 --> 00:22:32.120
All right.
411
00:22:32.600 --> 00:22:33.220
Fully noted.
412
00:22:33.340 --> 00:22:35.840
Release is fully noted and unified on the App Store.
413
00:22:37.120 --> 00:22:38.040
Oh, fully noted.
414
00:22:38.220 --> 00:22:40.780
JoyMarket is now a dedicated JoyMarket client.
415
00:22:41.220 --> 00:22:42.060
Connect over Tor.
416
00:22:42.320 --> 00:22:43.860
No private keys on device.
417
00:22:44.140 --> 00:22:45.060
Full market taker.
418
00:22:45.180 --> 00:22:47.180
Fidelity bond functionality and more.
419
00:22:47.400 --> 00:22:48.040
That's cool.
420
00:22:49.780 --> 00:22:50.280
All right.
421
00:22:50.280 --> 00:22:55.880
Oh, Unified Payjoin Wallet is a Payjoin-capable Bitcoin Core client.
422
00:22:56.020 --> 00:22:58.280
B2B over Nostra and connect via Tor.
423
00:22:59.420 --> 00:23:04.740
Crux Installer version 0.0.20-beta major update.
424
00:23:04.860 --> 00:23:10.200
Now users can, after download and verify an official firmware, select between
425
00:23:10.200 --> 00:23:12.920
to flush or to make AirGap update.
426
00:23:13.240 --> 00:23:13.440
Cool.
427
00:23:14.680 --> 00:23:24.500
Bolts Exchange Client version 2.1.10. U3XO version 0.2.0. Utils simplify,
428
00:23:24.700 --> 00:23:26.560
export proof of positions.
429
00:23:27.420 --> 00:23:30.520
Revert utils simplify and export proof of positions.
430
00:23:31.680 --> 00:23:35.920
U3XO use slices from Standard Lib.
431
00:23:37.130 --> 00:23:40.640
Utils simplify and proof positions.
432
00:23:41.440 --> 00:23:41.740
Neat.
433
00:23:42.560 --> 00:23:50.360
Bitcoin Safe version 1.0.0-b1-beta version used with caution.
434
00:23:51.080 --> 00:23:53.500
Easy multi-sig wallet safe setup.
435
00:23:54.840 --> 00:23:59.280
I don't know much about this project, so please proceed with caution.
436
00:24:00.140 --> 00:24:01.580
Easy multi-sig wallet setup.
437
00:24:01.700 --> 00:24:06.900
Setup step-by-step instructions for a multi-sig setup with PDF backup sheets.
438
00:24:07.660 --> 00:24:13.820
Full support for CodeCard, CodeCard Q, Bitbox 2, Jade, Spectre, DIY support,
439
00:24:14.080 --> 00:24:22.880
QR, USB, SD card, secure hardware ciders only, just a bunch of stuff here.
440
00:24:23.360 --> 00:24:25.200
I don't know much about this project, do you guys?
441
00:24:26.440 --> 00:24:30.960
I never heard of it, but it looks like very full-featured, like has support for
442
00:24:30.960 --> 00:24:34.960
like basically every hardware wallet, like BDK, PowerTrade BDK.
443
00:24:35.300 --> 00:24:36.080
Lots of languages.
444
00:24:36.080 --> 00:24:37.780
There's a lot going on here.
445
00:24:38.200 --> 00:24:39.580
Oh, it's Microsoft.
446
00:24:40.920 --> 00:24:41.800
It's Windows.
447
00:24:42.920 --> 00:24:47.180
It's got like wallet chat between, for sharing PSPTs between computers.
448
00:24:47.340 --> 00:24:48.120
I mean, that's kind of cool.
449
00:24:49.100 --> 00:24:49.380
Yeah.
450
00:24:50.720 --> 00:24:52.620
But don't do this on Windows, people.
451
00:24:53.560 --> 00:24:56.120
I opened the GitHub just while we were chatting.
452
00:24:56.920 --> 00:24:58.140
I'm going to play with this.
453
00:24:58.240 --> 00:25:02.260
I haven't used it, like, you know, caveat emptor, etc.
454
00:25:02.260 --> 00:25:07.420
It looks like if you took Electrum, but then you redid Electrum today, having
455
00:25:07.420 --> 00:25:10.520
seen mempool space, this is what you would build, right?
456
00:25:10.620 --> 00:25:14.660
It looks like that, I don't know, Windows form builder type like UI.
457
00:25:14.980 --> 00:25:15.600
It is Windows.
458
00:25:15.980 --> 00:25:20.240
But the dudes also built like mempool space visualizations into it.
459
00:25:20.280 --> 00:25:21.320
It looks wild.
460
00:25:22.460 --> 00:25:23.120
It does.
461
00:25:23.260 --> 00:25:24.220
It does have that vibe.
462
00:25:24.380 --> 00:25:25.420
I'm taking a look here.
463
00:25:25.900 --> 00:25:26.080
Yeah.
464
00:25:26.380 --> 00:25:28.180
So I'm just excited about that.
465
00:25:28.520 --> 00:25:30.060
The icons are the same as Electrum.
466
00:25:30.740 --> 00:25:30.960
Yeah.
467
00:25:30.960 --> 00:25:31.060
Yeah.
468
00:25:31.120 --> 00:25:34.380
No, it looks like Electrum and mempool space had a baby.
469
00:25:34.700 --> 00:25:36.120
It's kind of great.
470
00:25:36.860 --> 00:25:37.260
It is.
471
00:25:37.440 --> 00:25:38.000
It's Python.
472
00:25:38.700 --> 00:25:39.280
Is it Python?
473
00:25:39.960 --> 00:25:40.360
Yeah.
474
00:25:40.760 --> 00:25:41.520
Yeah, it is Python.
475
00:25:41.820 --> 00:25:42.800
So maybe somebody can.
476
00:25:43.220 --> 00:25:43.800
Oh, it's.
477
00:25:43.960 --> 00:25:44.360
Oh, OK.
478
00:25:44.420 --> 00:25:45.360
So it's not just Windows.
479
00:25:46.180 --> 00:25:51.580
You can target a build to Mac or Ubuntu or whatever.
480
00:25:51.780 --> 00:25:52.000
OK.
481
00:25:52.180 --> 00:25:52.480
Cool.
482
00:25:52.800 --> 00:25:53.140
Nice.
483
00:25:53.880 --> 00:25:55.060
It looks like it's just in Python.
484
00:25:55.420 --> 00:25:56.500
So it runs anywhere.
485
00:25:56.940 --> 00:25:57.180
Yeah.
486
00:25:57.180 --> 00:25:57.280
Yeah.
487
00:25:57.400 --> 00:26:01.420
It's probably using what, like TK enter or something for the for the UI,
488
00:26:01.840 --> 00:26:02.580
whatever that thing is called.
489
00:26:02.760 --> 00:26:03.260
I don't know.
490
00:26:03.280 --> 00:26:05.060
It looks like it doesn't look like QT.
491
00:26:05.760 --> 00:26:05.980
Yeah.
492
00:26:06.680 --> 00:26:06.960
Yeah.
493
00:26:07.040 --> 00:26:07.940
It's QT.
494
00:26:08.540 --> 00:26:09.460
They're using PyQT.
495
00:26:10.540 --> 00:26:13.100
I just dug into the UI part of the code.
496
00:26:13.360 --> 00:26:13.500
Cool.
497
00:26:13.900 --> 00:26:14.400
Love it.
498
00:26:15.060 --> 00:26:15.320
Nice.
499
00:26:15.580 --> 00:26:16.240
I love this.
500
00:26:16.380 --> 00:26:21.180
Like this is probably a dude who has his coins and he's like, hey, I'm
501
00:26:21.180 --> 00:26:23.160
unsatisfied with every wallet out there.
502
00:26:23.220 --> 00:26:25.320
I'm just going to build my own and make it available to all.
503
00:26:25.380 --> 00:26:25.720
Hell yeah.
504
00:26:25.720 --> 00:26:25.820
Yeah.
505
00:26:26.180 --> 00:26:27.960
There is no other way.
506
00:26:29.080 --> 00:26:33.940
Tell you what, like nothing teaches you how Bitcoin works more than building a
507
00:26:33.940 --> 00:26:34.160
wallet.
508
00:26:34.960 --> 00:26:39.460
Like, like everybody who like really wants to understand how Bitcoin works, go
509
00:26:39.460 --> 00:26:42.940
write a wallet, you know, feel free to never put real money in it.
510
00:26:43.020 --> 00:26:43.140
Right.
511
00:26:43.180 --> 00:26:47.520
But like write a wallet, put it on Signet or Testnet 4, send coins around like
512
00:26:47.520 --> 00:26:51.280
you will learn way better than all the books and podcasts in the world how
513
00:26:51.280 --> 00:26:51.900
Bitcoin works.
514
00:26:52.400 --> 00:26:52.700
Yes.
515
00:26:53.430 --> 00:26:57.440
There is nothing like serializing a Bitcoin transaction to make sure for you to
516
00:26:57.440 --> 00:26:59.680
understand if you want to continue further or not.
517
00:27:01.180 --> 00:27:02.880
This is not for me.
518
00:27:03.040 --> 00:27:03.140
Right.
519
00:27:03.180 --> 00:27:04.240
Like back away.
520
00:27:06.660 --> 00:27:12.460
Joinster app version 0.1.1 Kotlin implementation for Joinster.
521
00:27:13.640 --> 00:27:21.480
BitKey app version 2024.71.0. You can now select MoonPay and BitKey app to sell
522
00:27:21.480 --> 00:27:21.980
Bitcoin.
523
00:27:22.680 --> 00:27:27.260
Australian or CAD are now available as display currencies.
524
00:27:28.140 --> 00:27:31.000
Transaction history wallet descriptor now available for export.
525
00:27:31.840 --> 00:27:35.640
Currency display is now appearing in the settings menu.
526
00:27:36.500 --> 00:27:40.040
Do you guys know if you can export an XBRIV from the BitKey?
527
00:27:40.820 --> 00:27:41.440
You cannot.
528
00:27:42.200 --> 00:27:47.780
How do you recover outside of the stack, outside of the BitKey stack?
529
00:27:48.840 --> 00:27:52.620
All the recovery methods are like inside the BitKey stack.
530
00:27:52.940 --> 00:27:59.560
Like there's ways of recovering individual keys or if you can't recover
531
00:27:59.560 --> 00:28:01.660
individual keys, you can do a wallet sweep.
532
00:28:01.840 --> 00:28:08.020
So like a new two or three basically, but they don't give you any raw
533
00:28:08.020 --> 00:28:11.020
cryptographic keys like anywhere in the stack.
534
00:28:11.820 --> 00:28:16.120
I keep on saying that's like the it's like the Klaus Schwab replacement wallet.
535
00:28:18.080 --> 00:28:22.920
Yeah, I mean, it's really meant for people where it's like the biggest threat
536
00:28:22.920 --> 00:28:25.880
to their coins is that they're going to like mishandle a seed phrase or
537
00:28:25.880 --> 00:28:27.160
mishandle a backup, right?
538
00:28:27.240 --> 00:28:28.800
Like that's that's like who it's built for.
539
00:28:30.820 --> 00:28:37.300
Bitcoin Jungle mobile app version 1.3.0. This update adds a new transaction
540
00:28:37.300 --> 00:28:43.320
statistics screen from the settings, allowing you to do some reporting on your
541
00:28:43.320 --> 00:28:44.480
own transaction history.
542
00:28:45.400 --> 00:28:46.600
Bitcoin Jungle really works.
543
00:28:47.760 --> 00:28:52.680
Simple Bitcoin wallet version 2.6. Drop harder wallet support, drop built-in
544
00:28:52.680 --> 00:28:55.340
Tor support, drop LNURL support.
545
00:28:56.380 --> 00:28:57.880
I guess the wallet's getting simpler.
546
00:28:59.380 --> 00:29:00.280
I know, right?
547
00:29:02.920 --> 00:29:05.600
Yeah, version three is going to be simplest Bitcoin wallet.
548
00:29:06.540 --> 00:29:07.020
Yes.
549
00:29:07.680 --> 00:29:12.940
It's funny because I wanted to use a simple Bitcoin wallet for a FOSS Bitcoin
550
00:29:12.940 --> 00:29:14.840
project that's being worked on right now.
551
00:29:15.080 --> 00:29:15.320
Sure.
552
00:29:15.320 --> 00:29:17.660
But, you know, it was taken.
553
00:29:18.100 --> 00:29:21.460
So the project is called Cove.
554
00:29:22.080 --> 00:29:24.280
It's going to be a very cool, simple wallet.
555
00:29:25.700 --> 00:29:30.700
All right, Datum Gateway version 0.2-beta initial public release.
556
00:29:31.220 --> 00:29:32.000
This is pretty cool.
557
00:29:32.660 --> 00:29:33.680
I love this.
558
00:29:34.480 --> 00:29:39.820
I think this is finally the fire that Stratum V2 needed in the ass to get
559
00:29:39.820 --> 00:29:40.420
things moving.
560
00:29:41.300 --> 00:29:44.520
It is backwards compatible with Stratum V2.
561
00:29:45.320 --> 00:29:50.800
I think it's compatible with Stratum V1 because it's a gateway and you speak
562
00:29:50.800 --> 00:29:53.600
Stratum V1 to the gateway and then it speaks Datum.
563
00:29:53.680 --> 00:29:55.980
I think it was supposed to work with V2 as well.
564
00:29:56.580 --> 00:29:57.060
Oh, OK.
565
00:29:57.440 --> 00:29:58.160
I didn't realize that.
566
00:29:58.640 --> 00:30:02.720
I thought all the controversy was that it wasn't because everyone was mad when
567
00:30:02.720 --> 00:30:04.320
I just used V2.
568
00:30:04.540 --> 00:30:07.100
Yeah, because I thought the whole point was that they didn't want to make
569
00:30:07.100 --> 00:30:09.920
everybody mad by also adding V2 support.
570
00:30:10.600 --> 00:30:11.360
But maybe I'm wrong.
571
00:30:12.280 --> 00:30:13.140
Anyways, that's cool.
572
00:30:13.220 --> 00:30:13.600
It's great.
573
00:30:13.700 --> 00:30:14.560
We need more of this.
574
00:30:14.560 --> 00:30:19.660
We need all the templating in the individuals as we can get as soon as
575
00:30:19.660 --> 00:30:20.160
possible.
576
00:30:20.680 --> 00:30:21.780
Very important.
577
00:30:22.640 --> 00:30:26.160
Yeah, there's been a few blocks already mined with it, too, which is cool.
578
00:30:26.640 --> 00:30:26.860
Yeah.
579
00:30:28.820 --> 00:30:35.660
ESPminer version 2.3.0 allow connecting to open Wi-Fi networks set the file CPU
580
00:30:35.660 --> 00:30:41.400
frequency to 240 megahertz and a few other things here.
581
00:30:42.230 --> 00:30:51.560
Brains Toolbox version 24.09. Blockstream Green iOS version 4.0.36 allow re
582
00:30:51.560 --> 00:30:56.740
-deposit of expired UTXOs, liquid multi-sig accounts, QR mode for a single-sig
583
00:30:56.740 --> 00:31:02.420
watch only, recovery phrase, import QR view, still no PSPT support.
584
00:31:03.220 --> 00:31:05.360
I've been saying that for what, like three, four years now?
585
00:31:07.720 --> 00:31:14.780
Debify app version 0.0.52, cold card mark for integration.
586
00:31:14.960 --> 00:31:16.260
Now you can start your escrow.
587
00:31:16.600 --> 00:31:17.540
This is super cool.
588
00:31:17.740 --> 00:31:19.000
We worked with them on this.
589
00:31:19.920 --> 00:31:24.300
The guys from Debify are really pushing and they have actually like they're
590
00:31:24.300 --> 00:31:30.000
improving their access to cheaper capital, like cheaper dollars, so they can
591
00:31:30.000 --> 00:31:31.660
offer better interest rates and things.
592
00:31:32.780 --> 00:31:34.280
I think it's still KYC free.
593
00:31:35.360 --> 00:31:37.620
It's an interesting little project.
594
00:31:38.600 --> 00:31:40.540
Cold card queue support is coming soon, too.
595
00:31:41.640 --> 00:31:44.220
Well, I mean, it should work for both, work for one works for the other.
596
00:31:45.960 --> 00:31:52.560
Nirvati version 0.1.0. Nirvati is an open source project trying to make self
597
00:31:52.560 --> 00:31:53.980
-hosting easy for everyone.
598
00:31:55.040 --> 00:31:57.720
Self-hosting of what?
599
00:31:59.640 --> 00:32:03.720
Adopts a copyleft license to ensure decentralized frequency.
600
00:32:03.720 --> 00:32:07.670
I don't know, we'll probably go read about that later.
601
00:32:08.560 --> 00:32:17.920
BTCmap-Android version 0.8.0, show, place comments, hide ATMs by default.
602
00:32:18.740 --> 00:32:28.060
Kyoto version 0.4.0, an implementation of Bitcoin improvement proposal 157.158.
603
00:32:28.860 --> 00:32:34.000
Yeah, it's like a compact block filter wallet, basically.
604
00:32:34.300 --> 00:32:39.860
So if you want to use like Neutrino filters for your wallet, then this is an
605
00:32:39.860 --> 00:32:41.620
implementation of it.
606
00:32:42.260 --> 00:32:42.520
Cool.
607
00:32:43.260 --> 00:32:45.300
That should make the wallet sync very fast.
608
00:32:46.320 --> 00:32:47.280
For phones is great.
609
00:32:48.420 --> 00:32:52.620
I think these guys are working on like, this is their proof of concept.
610
00:32:52.860 --> 00:32:56.060
They eventually want to get like a lot of it upstream into BDK.
611
00:32:56.340 --> 00:32:57.280
That would be awesome.
612
00:32:57.280 --> 00:32:59.540
Because right now BDK is only like Electrum only.
613
00:33:00.000 --> 00:33:01.680
So that'd be great.
614
00:33:02.340 --> 00:33:02.720
Very neat.
615
00:33:04.000 --> 00:33:08.360
Bitcoin Dictionary version 2.0, add double title system for terms that cannot
616
00:33:08.360 --> 00:33:09.020
be translated.
617
00:33:10.340 --> 00:33:13.620
Add EPUB version, a bunch of other things.
618
00:33:14.780 --> 00:33:20.400
Project Spotlight 2140.dev, European nonprofit organization dedicated to
619
00:33:20.400 --> 00:33:22.620
support Bitcoin research and development.
620
00:33:22.920 --> 00:33:25.840
Oh yeah, that was by Ruben and Josie.
621
00:33:26.640 --> 00:33:32.680
Yeah, I ran into Josie last week at TabConf and he's super excited about this.
622
00:33:34.320 --> 00:33:38.580
Everybody should check it out if you want to work on, you know, Bitcoin kind of
623
00:33:38.580 --> 00:33:40.040
protocol development full time.
624
00:33:40.200 --> 00:33:45.260
Like they're trying to provide like a stable funding path and lots of support.
625
00:33:45.500 --> 00:33:49.780
Like they've got office space and they're trying to be able to like hire smart
626
00:33:49.780 --> 00:33:51.600
people who want to work on Bitcoin stuff full time.
627
00:33:52.200 --> 00:33:52.540
Nice.
628
00:33:52.640 --> 00:33:56.960
It's more like like an incubator of people kind of thing.
629
00:33:57.100 --> 00:33:59.440
Like there's like, you know, it's not just a grant.
630
00:34:00.740 --> 00:34:01.360
Yeah, yeah.
631
00:34:01.680 --> 00:34:07.639
Instead of it being like project based grants, it's more of like people based.
632
00:34:07.880 --> 00:34:11.360
I know it's probably closer to like a chain code kind of thing where it's like
633
00:34:11.360 --> 00:34:15.980
stable, long term funding to be a person working on Bitcoin full time instead
634
00:34:15.980 --> 00:34:17.820
of like, here's some money to go do this thing.
635
00:34:18.100 --> 00:34:18.360
Right.
636
00:34:18.760 --> 00:34:19.320
Very cool.
637
00:34:20.159 --> 00:34:22.920
There's another one announced last night, too.
638
00:34:23.060 --> 00:34:28.360
I don't think you have it on the list, but local host by BitDevJ.
639
00:34:29.580 --> 00:34:35.560
I put in the chat, but similar model, a chain competitor.
640
00:34:36.780 --> 00:34:44.560
But I think they highlight in the post, they're poaching merch and Ava started
641
00:34:44.560 --> 00:34:44.920
out.
642
00:34:45.440 --> 00:34:46.639
So that's really cool.
643
00:34:47.340 --> 00:34:47.980
Nice.
644
00:34:49.300 --> 00:34:53.580
Rewind Bitcoin, Bitcoin wallet in beta that lets you reverse taft.
645
00:34:54.100 --> 00:34:55.320
Just nothing like rollbacks.
646
00:34:56.320 --> 00:35:01.380
Rewinds vault lock funds starting a countdown when unlocked to allow, what is
647
00:35:01.380 --> 00:35:04.660
this, a time, like a mini script?
648
00:35:04.860 --> 00:35:05.540
Sounds like a vault.
649
00:35:06.460 --> 00:35:12.360
Yeah, they say it's, they're describing it as a vault, but how does it work?
650
00:35:12.360 --> 00:35:16.480
It's got to be pre-signed transactions like a deleted key covenant.
651
00:35:17.140 --> 00:35:18.660
It's got to be deleted key covenant.
652
00:35:19.240 --> 00:35:20.500
And it's risk-free.
653
00:35:20.940 --> 00:35:21.460
Okay.
654
00:35:22.160 --> 00:35:22.520
All right.
655
00:35:24.940 --> 00:35:28.460
I'm sure somebody will reach out to us at some point to try to explain.
656
00:35:30.820 --> 00:35:35.400
Bitcoinutils.dev, utility resources website offering various Bitcoin-related
657
00:35:35.400 --> 00:35:37.120
cryptographic and encoding tools.
658
00:35:37.120 --> 00:35:43.100
By Vojtak Strand, I can't say that.
659
00:35:43.880 --> 00:35:44.940
It looks like a check name.
660
00:35:46.440 --> 00:35:50.680
Standalone Bitcoin consensus engine and standalone binary exposing the
661
00:35:50.680 --> 00:35:53.560
historical Bitcoin consensus engine.
662
00:35:54.520 --> 00:35:59.860
Fabric, a trustless distributed DNS resolver for Bitcoin spaces.
663
00:36:01.200 --> 00:36:03.440
Wow, so it's more like DHT.
664
00:36:06.340 --> 00:36:11.780
L402 middleware, a middleware library for Rust that provides handler functions
665
00:36:11.780 --> 00:36:18.480
to accept micro transactions before serving ad-free content or any paid APIs.
666
00:36:19.600 --> 00:36:25.580
NodeWatch, a CLI dashboard for monitoring your Bitcoin full node, providing
667
00:36:25.580 --> 00:36:30.800
essential information such as node status, transaction fees, Bitcoin price, and
668
00:36:30.800 --> 00:36:31.340
more.
669
00:36:32.620 --> 00:36:38.160
Bitcoindquick, a dockerized Bitcoin core container for quickly spinning up and
670
00:36:38.160 --> 00:36:42.740
prune node with ZMQ support for running public pools.
671
00:36:44.800 --> 00:36:48.820
Chorley, reward your kids with sats for completing chores.
672
00:36:49.060 --> 00:36:51.080
Create a custom chore list for your kids.
673
00:36:51.240 --> 00:36:52.660
Set up automatic payouts.
674
00:36:53.880 --> 00:36:57.480
Satofi, Bitcoin coffee machines.
675
00:36:58.220 --> 00:36:59.060
I think they're DIY.
676
00:37:00.660 --> 00:37:03.140
CoinVote, endorse your candidates with Bitcoin.
677
00:37:03.460 --> 00:37:06.000
No, don't waste your Bitcoin on candidates.
678
00:37:06.540 --> 00:37:07.560
Hard pass.
679
00:37:09.040 --> 00:37:11.880
We don't want governments having Bitcoin.
680
00:37:12.040 --> 00:37:13.300
We want people having Bitcoin.
681
00:37:14.240 --> 00:37:21.280
Bitcoin prediction markets place bets by sending lightning payments and receive
682
00:37:21.280 --> 00:37:23.000
winnings to your lightning address.
683
00:37:24.360 --> 00:37:31.300
LiquiSabi, CoinJoin Explorer, monitor and publish WabiSabi's coordinators
684
00:37:31.300 --> 00:37:32.860
advertised on Noster.
685
00:37:34.080 --> 00:37:39.000
CoinDemo, an interactive visual introduction into how mining works.
686
00:37:40.220 --> 00:37:41.880
More vulnerability disclosures.
687
00:37:42.800 --> 00:37:47.100
Golden Jackal's specialized tool set for targeting air gap systems in the
688
00:37:47.100 --> 00:37:48.300
espionage campaigns.
689
00:37:48.900 --> 00:37:49.180
Neat.
690
00:37:50.220 --> 00:37:55.820
For the people that don't understand why you need side channel defenses and
691
00:37:55.820 --> 00:38:00.460
things of such and why you don't use Raspberry Pis for Bitcoin, go read some of
692
00:38:00.460 --> 00:38:00.700
this.
693
00:38:01.720 --> 00:38:02.300
There is a link.
694
00:38:03.760 --> 00:38:07.760
Radiant Capital, hack exploits, multi-sig approval process and hardware wallet
695
00:38:07.760 --> 00:38:08.480
compromise.
696
00:38:09.520 --> 00:38:10.240
Radiant Capital.
697
00:38:10.420 --> 00:38:13.820
Oh, was this the one that they exploited?
698
00:38:14.410 --> 00:38:19.720
Ethereum smart contract, but they also gave the wrong transactions for the
699
00:38:19.720 --> 00:38:20.620
clients to sign.
700
00:38:20.800 --> 00:38:22.060
I think this might have been it.
701
00:38:23.320 --> 00:38:23.440
Yeah.
702
00:38:25.180 --> 00:38:30.740
Locate X, US law enforcement tool enables wireless smartphone tracking.
703
00:38:31.520 --> 00:38:32.500
How surprised.
704
00:38:34.310 --> 00:38:35.140
Not again.
705
00:38:35.780 --> 00:38:36.800
Not again.
706
00:38:38.100 --> 00:38:41.580
Hackers target Android users with Qualcomm zero day vulnerability.
707
00:38:41.940 --> 00:38:42.300
Nice.
708
00:38:44.860 --> 00:38:46.760
Your phones are not safe.
709
00:38:47.640 --> 00:38:49.080
Don't use phones for Bitcoin.
710
00:38:49.540 --> 00:38:51.120
I mean, for real amounts of Bitcoin.
711
00:38:52.260 --> 00:38:55.600
Because like, I guess like the point that I'm making here is that like all
712
00:38:55.600 --> 00:38:59.960
these things are being used to target like people of interest, but like these
713
00:38:59.960 --> 00:39:01.580
tools can also be used to take your Bitcoin.
714
00:39:03.280 --> 00:39:09.180
Research conducted by Jonas Hoffman and Kim Dong with the applied cryptography
715
00:39:09.180 --> 00:39:15.160
group at ETH Zurich discovers flaws in five end-to-end encrypted cloud
716
00:39:15.160 --> 00:39:15.940
services.
717
00:39:17.420 --> 00:39:19.800
You can go read the details here.
718
00:39:19.920 --> 00:39:24.580
Security analysis reveals weakness in WeChat's MMTLS encryption protocol.
719
00:39:24.780 --> 00:39:26.080
Yeah, I'm so surprised.
720
00:39:26.480 --> 00:39:28.200
And I'm sure it was just a weakness.
721
00:39:29.940 --> 00:39:30.820
Definitely not a backdoor.
722
00:39:31.380 --> 00:39:33.060
Yeah, definitely not a backdoor.
723
00:39:34.020 --> 00:39:41.140
Impromptu tool tracking LLM agents into improper tool use demonstrates the risk
724
00:39:41.140 --> 00:39:44.160
of AI chatbot exploited by hidden malicious prompts.
725
00:39:44.920 --> 00:39:46.000
We've seen this before.
726
00:39:46.860 --> 00:39:52.260
Tails version 6.8.1 release an emergency release to fix critical security
727
00:39:52.260 --> 00:39:54.180
vulnerability in the Tor browser.
728
00:39:56.080 --> 00:39:59.900
And critical use after free vulnerability.
729
00:40:00.360 --> 00:40:01.460
This one was really funny.
730
00:40:01.460 --> 00:40:08.300
Yeah, this was a like arbitrary code execution vulnerability in Firefox from a
731
00:40:08.300 --> 00:40:13.820
bug in the animation timeline, which is like browsers are so freaking
732
00:40:13.820 --> 00:40:14.300
complicated.
733
00:40:14.460 --> 00:40:17.400
It's like, cool, an animation bug is going to let somebody pwn your machine.
734
00:40:17.900 --> 00:40:22.800
Yes, and it's like people may not understand that there is like millions of
735
00:40:22.800 --> 00:40:24.040
lines of code in a browser.
736
00:40:24.640 --> 00:40:26.520
Like it's a lot.
737
00:40:27.880 --> 00:40:29.540
The browser is unsafe.
738
00:40:29.540 --> 00:40:32.620
It's remote execution of code in your machine.
739
00:40:33.100 --> 00:40:34.040
It's pretty crazy.
740
00:40:35.720 --> 00:40:38.080
Privacy and other related projects.
741
00:40:38.380 --> 00:40:48.140
Simple Wax version 6.1. Sideband version 1.1.1. It's all the RNSXLXMF stuff.
742
00:40:49.020 --> 00:40:51.680
Reticulum Mesh Chat also updated.
743
00:40:52.040 --> 00:40:53.580
Tor browser also updated.
744
00:40:54.800 --> 00:40:55.800
Project Spotlight.
745
00:40:56.680 --> 00:41:04.000
PubKY Core, an open protocol for per-public-key backend for censorship
746
00:41:04.000 --> 00:41:05.920
-resistant web applications.
747
00:41:07.210 --> 00:41:08.700
More DTH.
748
00:41:10.930 --> 00:41:13.060
It always ends in DTH.
749
00:41:14.500 --> 00:41:20.140
I think this is from Carvalho's company.
750
00:41:20.140 --> 00:41:27.140
Like Synonym, they do, what is it, Bitkit or whatever.
751
00:41:27.380 --> 00:41:31.700
I think this is like maybe what they're doing now.
752
00:41:32.320 --> 00:41:37.240
They were using some of the same stuff that's underneath HolePunch.
753
00:41:37.460 --> 00:41:41.580
I don't know if they've rebranded it to this or if this is new, but it
754
00:41:41.580 --> 00:41:46.420
looks like all these PubKey projects are coming out of that group.
755
00:41:46.420 --> 00:41:50.540
Maybe this helps him with the zero-confirmation transaction.
756
00:41:51.880 --> 00:41:52.920
Yeah, right.
757
00:41:53.040 --> 00:41:55.980
Just send your zero-conf transaction over this protocol.
758
00:41:56.480 --> 00:41:56.860
That's right.
759
00:41:58.440 --> 00:41:58.780
All right.
760
00:41:59.240 --> 00:41:59.520
Lightning.
761
00:41:59.780 --> 00:42:00.440
Project Spotlight.
762
00:42:00.600 --> 00:42:04.960
Blockstream launches Simplicity on Liquid TaskNet and introduces Symfony, a
763
00:42:04.960 --> 00:42:08.320
high-level language for writing Bitcoin smart contracts.
764
00:42:09.520 --> 00:42:14.480
Spark, a trust-minimized solution designed to scale Bitcoin and extend the
765
00:42:14.480 --> 00:42:15.320
Lightning network.
766
00:42:16.560 --> 00:42:18.040
Yeah, this is pretty cool.
767
00:42:18.220 --> 00:42:21.640
It's kind of making their own L2, kind of not.
768
00:42:21.900 --> 00:42:25.380
It's basically like ARK and StateChain had a baby.
769
00:42:26.160 --> 00:42:30.400
Then you have a Lightning gateway that LightSpark runs for all the users to be
770
00:42:30.400 --> 00:42:32.740
able to interact with the broader network.
771
00:42:34.060 --> 00:42:38.960
It has a few trust assumptions, but I think it's good enough for them to call
772
00:42:38.960 --> 00:42:43.020
it non-custodial legally and that should work for them.
773
00:42:43.220 --> 00:42:44.280
But it's kind of interesting.
774
00:42:45.480 --> 00:42:50.580
Yeah, we need more ideas that are departure from Lightning.
775
00:42:51.920 --> 00:42:55.420
LightSpark, I mean, these guys are pros and they're going to push the shit hard
776
00:42:55.420 --> 00:42:57.100
and they understand payments.
777
00:42:58.420 --> 00:43:04.820
They're more on the TradFi kind of crowd, but I think there's some interesting
778
00:43:04.820 --> 00:43:06.100
stuff probably coming from them.
779
00:43:06.800 --> 00:43:07.540
Yeah, it's pretty cool.
780
00:43:08.020 --> 00:43:12.220
My understanding is like most of their devs are like, they got into Bitcoin
781
00:43:12.220 --> 00:43:18.600
through LightSpark and they'll come up with their own L2 within a year, which
782
00:43:18.600 --> 00:43:20.440
is pretty impressive.
783
00:43:21.500 --> 00:43:26.360
They've also got some pretty good-sized enterprise customers at this point.
784
00:43:26.820 --> 00:43:32.400
So it'll be cool to see if this actually starts rolling out in unusual places,
785
00:43:32.540 --> 00:43:32.700
right?
786
00:43:32.800 --> 00:43:36.060
I'm pretty sure LightSpark did the Lightning implementation for Coinbase.
787
00:43:36.380 --> 00:43:41.020
I have no idea if that'll get rolled out, but if that's the kind of customers
788
00:43:41.020 --> 00:43:44.560
that they have, it would be interesting to start seeing this stuff actually get
789
00:43:44.560 --> 00:43:45.560
deployed pretty quickly.
790
00:43:46.200 --> 00:43:50.140
I think there was a shake in the force kind of thing.
791
00:43:50.360 --> 00:43:54.760
I think something changed, like I said, about six months, a year ago.
792
00:43:55.400 --> 00:44:01.560
The Overton window completely shifted to corporate being okay with Bitcoin
793
00:44:01.560 --> 00:44:06.460
stuff, as long as it's CIO-compatible service providers.
794
00:44:07.440 --> 00:44:12.240
Something changed, and I think we're going to start seeing some random stuff,
795
00:44:12.440 --> 00:44:16.180
like some complete random bank is going to come and show up a Lightning on
796
00:44:16.180 --> 00:44:23.260
their app or something, or from a completely unexpected place, like Coca-Cola
797
00:44:23.260 --> 00:44:27.760
or something just quietly starts using it, don't even tell anybody, and then
798
00:44:27.760 --> 00:44:31.160
just sort of comes out that they were using it for six months or something.
799
00:44:31.300 --> 00:44:31.640
You know what I mean?
800
00:44:31.680 --> 00:44:33.860
That kind of weird place.
801
00:44:35.180 --> 00:44:35.840
Yeah, I'm here for it.
802
00:44:36.460 --> 00:44:37.280
That's right.
803
00:44:38.300 --> 00:44:38.660
All right.
804
00:44:39.260 --> 00:44:43.180
Blockbuster, seamless content monetization with Lightning Network.
805
00:44:44.300 --> 00:44:50.960
Software releases Core Lightning version 24.08.2. I mean, you guys jump in on
806
00:44:50.960 --> 00:44:54.260
this Lightning stuff if there's anything here you want to talk about.
807
00:44:54.260 --> 00:45:00.300
LDK Node 0.4.0. Phoenix updated.
808
00:45:01.680 --> 00:45:12.460
Zeus version 0.9.1. Breeze SDK Core Greenlight version 0.6.2. Albi
809
00:45:12.460 --> 00:45:13.180
updated.
810
00:45:15.060 --> 00:45:19.280
Cashew me now supports restoring e-cash from a seed phrase.
811
00:45:19.500 --> 00:45:20.500
That's nice.
812
00:45:21.300 --> 00:45:22.300
That's huge.
813
00:45:22.980 --> 00:45:24.740
Where do they store the state?
814
00:45:26.040 --> 00:45:26.920
Probably Noster.
815
00:45:27.640 --> 00:45:28.520
Well, Noster, right?
816
00:45:28.860 --> 00:45:29.060
Okay.
817
00:45:29.900 --> 00:45:33.840
I know like for Fetiment, they just store it with the guardians because you're
818
00:45:33.840 --> 00:45:34.740
already trusting them.
819
00:45:35.240 --> 00:45:36.320
But you already trust them.
820
00:45:36.420 --> 00:45:38.640
It's not RUGU, so you might as well trust them with your state.
821
00:45:38.840 --> 00:45:39.060
Right.
822
00:45:39.340 --> 00:45:43.020
I don't know if you can do that in Cashew, but yeah.
823
00:45:43.460 --> 00:45:48.980
Well, yeah, I mean, Cashew, I know a lot of the Cashew apps just keep it
824
00:45:48.980 --> 00:45:52.140
in local browser storage, right?
825
00:45:52.140 --> 00:45:54.640
Because a lot of the Cashew apps are PWAs.
826
00:45:55.140 --> 00:46:00.720
And so you get some site namespaced local storage, like a little local
827
00:46:00.720 --> 00:46:01.000
database.
828
00:46:01.580 --> 00:46:03.660
That's what a bunch of them do.
829
00:46:03.940 --> 00:46:06.920
I don't know if, but yeah, if you can restore from a seed phrase, then it's
830
00:46:06.920 --> 00:46:08.860
got to be doing it off box somewhere.
831
00:46:09.940 --> 00:46:10.140
Yeah.
832
00:46:11.360 --> 00:46:16.540
Micro Bolt version 2.0. Micro Bolt self-hosted Bitcoin enlightening full node
833
00:46:16.540 --> 00:46:17.980
guide on personal computer.
834
00:46:19.060 --> 00:46:21.380
Geyser October 2024.
835
00:46:21.380 --> 00:46:22.700
Private messages.
836
00:46:23.360 --> 00:46:25.820
Creator can request buyer and pub.
837
00:46:26.220 --> 00:46:28.380
Creator can reward confirmation message.
838
00:46:29.300 --> 00:46:30.280
A bunch of other updates.
839
00:46:30.780 --> 00:46:30.880
Okay.
840
00:46:31.040 --> 00:46:34.460
If anybody from Geyser is listening, please fix your liquidity.
841
00:46:35.280 --> 00:46:42.500
I tried donating to the, Peter Todd was mentioning that there was no funds for
842
00:46:42.500 --> 00:46:43.400
open timestamps.
843
00:46:43.520 --> 00:46:47.480
And I thought like, you know, enough people use it that there was, I tried
844
00:46:47.480 --> 00:46:52.040
sending a bit of money there and computer said no.
845
00:46:52.620 --> 00:46:53.540
So I had to send half.
846
00:46:56.200 --> 00:47:02.000
You know, if you're going to take donations, make sure you can accept the
847
00:47:02.000 --> 00:47:02.400
donations.
848
00:47:03.620 --> 00:47:07.300
It was not like, you know, it's like 500 bucks kind of thing.
849
00:47:08.780 --> 00:47:12.760
LN markets add options to cash in from trade margin.
850
00:47:14.360 --> 00:47:16.640
Zaprite introduces sandbox environments.
851
00:47:16.640 --> 00:47:18.160
All right.
852
00:47:18.340 --> 00:47:19.700
Nostra project spotlights.
853
00:47:20.760 --> 00:47:20.880
Okay.
854
00:47:21.720 --> 00:47:24.400
Nostra pool notifications and Android.
855
00:47:25.200 --> 00:47:26.560
White noise live demo.
856
00:47:27.440 --> 00:47:32.560
White noise is Jeff G's MLS messaging implementation.
857
00:47:33.580 --> 00:47:34.780
This is super cool.
858
00:47:35.660 --> 00:47:36.400
Good name too.
859
00:47:37.220 --> 00:47:37.340
Yeah.
860
00:47:37.360 --> 00:47:38.260
White noise is a great name.
861
00:47:38.860 --> 00:47:39.720
It really is.
862
00:47:41.800 --> 00:47:47.520
Nostrastic bridge to publish Nostra posts and send and receive DMs over LoRa
863
00:47:47.520 --> 00:47:48.880
using MeshTastic.
864
00:47:49.660 --> 00:47:52.160
Oh, by the way, we have a prototype.
865
00:47:52.660 --> 00:47:57.460
We've rebuilt SatsLink from the previous intent to a new one.
866
00:47:58.380 --> 00:48:05.720
So the prototype should be in the office in a few weeks where it's, well, then
867
00:48:05.720 --> 00:48:06.900
we have to write a lot of code.
868
00:48:06.900 --> 00:48:13.200
But the hardware, hopefully this version or a similar version of this is like,
869
00:48:13.220 --> 00:48:13.760
would be ready.
870
00:48:14.060 --> 00:48:16.560
It supports MeshTastic to start.
871
00:48:16.920 --> 00:48:24.160
And then we are adding APRS and maybe even FSK and a few other little things.
872
00:48:25.000 --> 00:48:26.860
Is it still ESP32?
873
00:48:27.580 --> 00:48:28.140
Yes.
874
00:48:28.680 --> 00:48:28.960
Yes.
875
00:48:29.140 --> 00:48:30.160
It's still ESP base.
876
00:48:30.260 --> 00:48:30.640
Oh, wait.
877
00:48:31.820 --> 00:48:32.040
Shit.
878
00:48:32.120 --> 00:48:32.940
I can't remember now.
879
00:48:33.560 --> 00:48:34.280
Wrong timing.
880
00:48:34.440 --> 00:48:35.760
I have different projects in my head.
881
00:48:36.360 --> 00:48:40.380
I could swear we had added an STM chip because I think there was an STM
882
00:48:40.380 --> 00:48:47.000
chip we wanted to use that had the die for the MeshTastic stuff, the LoRa stuff
883
00:48:47.000 --> 00:48:48.280
from ESP.
884
00:48:48.920 --> 00:48:50.800
I think they licensed that part of the die.
885
00:48:51.220 --> 00:48:54.660
And it was part of the same chip where you get the STM stuff on it
886
00:48:54.660 --> 00:48:56.460
too, like the ARM stuff.
887
00:48:57.240 --> 00:48:58.900
Anyways, I can't remember now.
888
00:48:59.820 --> 00:49:03.680
You know, when you move things from a bench to another and you're like have
889
00:49:03.680 --> 00:49:06.940
different projects going on, these things all get mangled.
890
00:49:08.000 --> 00:49:11.060
Once it sends out, it's like, forget about this one.
891
00:49:11.160 --> 00:49:12.240
Now go on to the next thing.
892
00:49:13.760 --> 00:49:14.080
All right.
893
00:49:15.080 --> 00:49:17.440
AlgorRelay, an algorithm relay for Noster.
894
00:49:18.420 --> 00:49:21.260
This is all more on the DVM stuff.
895
00:49:22.400 --> 00:49:26.920
PPERelay, a pair of relays that changes part event basics.
896
00:49:28.820 --> 00:49:30.980
SearchRelay, NIP50 SearchRelay.
897
00:49:30.980 --> 00:49:34.240
Flotilla, NosterRelay based on communities.
898
00:49:34.540 --> 00:49:35.680
Flotilla looks kind of cool.
899
00:49:35.880 --> 00:49:42.380
I think they're trying to go after the Gen Z Discord crowd.
900
00:49:43.420 --> 00:49:47.540
It's still backed by Noster, but it's a different UI, which I'm all about.
901
00:49:48.680 --> 00:49:50.780
Noster is such a low-level primitive.
902
00:49:51.200 --> 00:49:54.600
Anytime people want to build new UIs around it, I think it's great.
903
00:49:55.000 --> 00:49:56.700
I mean, Discord needs to die.
904
00:49:57.320 --> 00:49:57.760
Yeah.
905
00:49:57.760 --> 00:50:02.560
Like, I seriously like the amount of communities I want to participate, but I
906
00:50:02.560 --> 00:50:04.440
won't just because it's on Discord.
907
00:50:04.720 --> 00:50:04.920
Yeah.
908
00:50:05.040 --> 00:50:08.980
Because I don't want to have yet another app talking shit in another world
909
00:50:08.980 --> 00:50:09.340
garden.
910
00:50:10.020 --> 00:50:11.640
I feel the same way about Telegram.
911
00:50:11.860 --> 00:50:16.680
I hate Telegram and the amount of like Bitcoin discussion and like groups that
912
00:50:16.680 --> 00:50:20.080
are trying to do things that all form around Telegram.
913
00:50:20.180 --> 00:50:20.740
I hate it.
914
00:50:20.860 --> 00:50:21.560
Like it's the worst.
915
00:50:21.720 --> 00:50:25.740
I think it's just that Telegram has the right tools for you to build open
916
00:50:25.740 --> 00:50:26.100
groups.
917
00:50:26.100 --> 00:50:30.840
It's very easy to just start an open group, although they limit you on how many
918
00:50:30.840 --> 00:50:32.840
custom URLs you can have.
919
00:50:33.080 --> 00:50:36.380
It's kind of annoying and you can't pay to change that.
920
00:50:37.260 --> 00:50:41.400
I feel like Telegram only exists to enable crime kind of thing.
921
00:50:41.500 --> 00:50:44.560
You know, like it's like they make all their money from it and they sort of
922
00:50:44.560 --> 00:50:47.700
have all the wrong tools for you.
923
00:50:47.800 --> 00:50:54.180
Like, for example, like they literally like allow scam, spam, like that's how
924
00:50:54.180 --> 00:50:55.780
they make their money from that.
925
00:50:55.780 --> 00:51:00.820
That's like you can almost feel right, like the whole UX and all the tools on
926
00:51:00.820 --> 00:51:05.760
Telegram are designed so that scams can happen and you can't do anything to
927
00:51:05.760 --> 00:51:07.880
protect your users from spam and scam.
928
00:51:08.480 --> 00:51:09.700
I hate Telegram.
929
00:51:11.740 --> 00:51:14.000
Do you guys have an opcat Telegram?
930
00:51:14.960 --> 00:51:20.760
No, I mean, like there's a bunch of Telegram groups that are like Covenant's
931
00:51:20.760 --> 00:51:24.640
sort of interest group and it talks about like all Covenant related stuff.
932
00:51:24.640 --> 00:51:28.440
There's, you know, groups talking about specific projects that use cat, but
933
00:51:28.440 --> 00:51:31.480
there's not like a cat enjoyers group per se.
934
00:51:32.020 --> 00:51:32.120
Right.
935
00:51:32.620 --> 00:51:33.940
We do have a Discord though.
936
00:51:34.320 --> 00:51:35.460
We do have a Discord though.
937
00:51:36.800 --> 00:51:38.620
And our Discord is the best.
938
00:51:39.460 --> 00:51:39.640
Right.
939
00:51:41.820 --> 00:51:48.060
Nosweet.net share or clone any tweet on Noster with URL and without any
940
00:51:48.060 --> 00:51:48.920
permission or anything.
941
00:51:49.060 --> 00:51:50.260
Well, this is kind of interesting.
942
00:51:50.700 --> 00:51:51.940
I need that often.
943
00:51:52.500 --> 00:51:52.760
OK.
944
00:51:53.880 --> 00:51:58.380
Docster, a simple document management system on Noster allows users to create
945
00:51:58.380 --> 00:51:59.700
and delegate documents.
946
00:52:00.620 --> 00:52:01.160
That's cool.
947
00:52:01.660 --> 00:52:03.400
Yeah, that could be cool.
948
00:52:04.180 --> 00:52:06.780
In 20 years, SharePoint will be replaced by Docster.
949
00:52:07.220 --> 00:52:07.860
That's right.
950
00:52:09.040 --> 00:52:10.680
Talk about another thing that needs to die.
951
00:52:13.700 --> 00:52:17.660
Translator, a new Noster service offering automated translations of Noster
952
00:52:17.660 --> 00:52:22.800
videos and Rx Noster, a library based on RxJS.
953
00:52:23.260 --> 00:52:24.060
Moving on.
954
00:52:25.540 --> 00:52:27.240
Software releases and project updates.
955
00:52:27.600 --> 00:52:29.760
OK, I'm going to skip these.
956
00:52:30.600 --> 00:52:33.140
Yeah, I think every single Noster client had an update.
957
00:52:33.420 --> 00:52:34.200
For real.
958
00:52:34.360 --> 00:52:36.200
Yes, literally every single one of them.
959
00:52:36.340 --> 00:52:38.320
Yes, they update like there's no tomorrow.
960
00:52:39.300 --> 00:52:39.700
All right, man.
961
00:52:39.800 --> 00:52:43.640
Thanks to everyone who streamed the sats and shout out to a few top boosters
962
00:52:43.640 --> 00:52:44.040
here.
963
00:52:44.040 --> 00:52:45.420
Ape me friend here.
964
00:52:45.600 --> 00:52:47.320
It's our die hard, right?
965
00:52:47.520 --> 00:52:49.800
Ride or die, as the kids call it.
966
00:52:50.700 --> 00:52:54.960
Listening to the end if you count 30 minutes of sleep listening at the end.
967
00:52:56.740 --> 00:52:57.540
All right.
968
00:52:57.880 --> 00:52:59.160
Nobody listens to the spot.
969
00:52:59.300 --> 00:52:59.940
It's all lies.
970
00:53:00.840 --> 00:53:02.960
T-dub, proof of listening.
971
00:53:04.080 --> 00:53:06.940
Here's how to make a classic grilled cheese sandwich.
972
00:53:08.000 --> 00:53:08.700
Very good.
973
00:53:09.240 --> 00:53:09.440
Yeah.
974
00:53:11.140 --> 00:53:12.640
BTC on board.
975
00:53:13.580 --> 00:53:14.860
More mini script, please.
976
00:53:15.140 --> 00:53:15.940
I'm not Rob.
977
00:53:16.960 --> 00:53:20.320
Yeah, we do have our mini script influencers here on the pod often.
978
00:53:21.060 --> 00:53:25.840
Average Gary, sats link revival, but I already used my preorder money for a
979
00:53:25.840 --> 00:53:26.420
second queue.
980
00:53:27.120 --> 00:53:27.600
Rugged.
981
00:53:29.700 --> 00:53:32.640
I mean, like we don't know yet when it's going to launch.
982
00:53:32.900 --> 00:53:33.660
Just, you know, it's good.
983
00:53:34.320 --> 00:53:35.760
We'll keep your price in line.
984
00:53:36.540 --> 00:53:38.840
It's good that you use your preorder money.
985
00:53:38.840 --> 00:53:40.500
So that it's not stuck in the system.
986
00:53:41.580 --> 00:53:43.100
So it might take a little while still.
987
00:53:43.560 --> 00:53:44.500
So don't worry.
988
00:53:45.520 --> 00:53:46.440
Von photo.
989
00:53:47.140 --> 00:53:47.880
Send some sats.
990
00:53:48.180 --> 00:53:49.240
Bright stats.
991
00:53:49.660 --> 00:53:52.840
Keep an eye on your wife flash attack vectors.
992
00:53:53.140 --> 00:53:53.500
It's true.
993
00:53:54.440 --> 00:53:58.040
Were you here, Wendell, when my wife flashed me behind the camera?
994
00:53:58.860 --> 00:53:59.960
No, I heard about it though.
995
00:54:00.240 --> 00:54:03.280
It was, yeah, it was very distracting.
996
00:54:06.360 --> 00:54:07.540
Tip of the day.
997
00:54:07.540 --> 00:54:10.620
Especially because she's not the type that does that often.
998
00:54:10.980 --> 00:54:13.140
So it was very unexpected.
999
00:54:14.320 --> 00:54:15.340
Tech tip of the day.
1000
00:54:16.260 --> 00:54:18.420
Recommended by Fiat Jaff, D arrow.
1001
00:54:19.100 --> 00:54:23.200
An open source browser extended for crowdsourcing, better titles and thumbnails
1002
00:54:23.200 --> 00:54:23.860
on YouTube.
1003
00:54:26.240 --> 00:54:30.540
Earth Do, the open source privacy focus alternative to Google sign-in.
1004
00:54:30.860 --> 00:54:32.680
Jesus Christ, please stop using Google sign-in.
1005
00:54:32.800 --> 00:54:34.400
That story got no air.
1006
00:54:34.660 --> 00:54:35.880
He got killed by Google.
1007
00:54:36.480 --> 00:54:38.220
I'm still so annoyed by it.
1008
00:54:38.380 --> 00:54:39.120
Wait, what story?
1009
00:54:39.620 --> 00:54:40.600
Google affected?
1010
00:54:40.700 --> 00:54:43.140
Google single sign-on got hacked.
1011
00:54:43.400 --> 00:54:50.400
People figure out how to do DNS hijack on custom domains, on Google, on anybody
1012
00:54:50.400 --> 00:54:53.900
that didn't have Google workspace.
1013
00:54:54.960 --> 00:55:01.760
So they figure out how to hijack DNSs using the Google form shit or whatever.
1014
00:55:01.760 --> 00:55:07.020
And they managed to essentially create Google single sign-on for like every
1015
00:55:07.020 --> 00:55:10.060
company on earth that didn't have Google single sign-on set up for their
1016
00:55:10.060 --> 00:55:10.420
domains.
1017
00:55:10.980 --> 00:55:15.320
And then went in and got into all kinds of company stuff.
1018
00:55:16.140 --> 00:55:18.840
Like what's the name of that stupid app everybody hates?
1019
00:55:19.740 --> 00:55:21.320
Slack, things like that.
1020
00:55:21.740 --> 00:55:23.140
It was a disaster.
1021
00:55:23.940 --> 00:55:25.000
Absolute disaster.
1022
00:55:25.300 --> 00:55:26.420
That's pretty bad.
1023
00:55:26.960 --> 00:55:31.340
Yeah, no, it was probably the biggest hack of the last 10 years.
1024
00:55:31.340 --> 00:55:34.600
And literally nobody talked about it because they killed the story.
1025
00:55:36.040 --> 00:55:36.640
Amazed.
1026
00:55:38.040 --> 00:55:41.320
Earthdew, the open source privacy-focused alternative to Google.
1027
00:55:41.580 --> 00:55:43.200
Oh yeah, I already talked about that one.
1028
00:55:44.220 --> 00:55:45.260
Bitcoin Optac.
1029
00:55:45.620 --> 00:55:47.720
Any topics here you guys want to bring up?
1030
00:55:48.000 --> 00:55:48.920
Let me know.
1031
00:55:49.900 --> 00:55:54.060
I think the first one they have like 1.75 channel announcements.
1032
00:55:54.360 --> 00:55:58.460
I think that was discussed at the big lightning summit in Tokyo.
1033
00:55:58.460 --> 00:56:02.960
So we'll see like a bit devs at Tabcov.
1034
00:56:03.880 --> 00:56:06.660
Some give an overview of everything that happened.
1035
00:56:08.240 --> 00:56:13.000
Everything's like instruments incrementally moving forward, which is good.
1036
00:56:13.520 --> 00:56:18.960
And like 12 is kind of like done now, which is exciting and all that stuff.
1037
00:56:19.100 --> 00:56:23.860
So it seems like we're actually making progress in lightning, even though it
1038
00:56:23.860 --> 00:56:25.040
doesn't feel like it day to day.
1039
00:56:26.300 --> 00:56:32.820
Yeah, Lalu wrote up notes from the Ellen developer summit.
1040
00:56:33.480 --> 00:56:34.380
They're on Delving Bitcoin.
1041
00:56:34.620 --> 00:56:37.160
They're very detailed and they're like a really good read.
1042
00:56:37.240 --> 00:56:40.560
If you're interested in what's going on in lightning, it's like a really
1043
00:56:40.560 --> 00:56:41.620
pleasant read.
1044
00:56:42.240 --> 00:56:42.820
Neat.
1045
00:56:43.300 --> 00:56:50.180
Did you guys go to Japan for the Bitcoin Tokyo or the other lightning stuff?
1046
00:56:51.220 --> 00:56:52.300
I wasn't invited.
1047
00:56:53.040 --> 00:56:54.240
Not a lightning dev.
1048
00:56:55.340 --> 00:56:58.680
Once you put on the wizard hat, they kicked you out of all the all the
1049
00:56:58.680 --> 00:56:59.180
cool clubs.
1050
00:56:59.760 --> 00:57:00.500
Oh, I see.
1051
00:57:00.780 --> 00:57:02.920
You guys are putting on Groton stuff now?
1052
00:57:04.380 --> 00:57:05.240
No, I'm just kidding.
1053
00:57:06.020 --> 00:57:09.860
No, it's just like a lightning like protocol dev.
1054
00:57:10.320 --> 00:57:11.300
Yeah, protocol dev.
1055
00:57:11.460 --> 00:57:13.140
Like even me, I wouldn't be invited to this.
1056
00:57:13.280 --> 00:57:16.040
It's like it's like 30 or 40 people that go.
1057
00:57:16.280 --> 00:57:21.380
It's like core contributors of like Eclair, Sea Lightning, L&D.
1058
00:57:22.040 --> 00:57:22.480
LDK.
1059
00:57:22.960 --> 00:57:23.400
LDK.
1060
00:57:23.680 --> 00:57:23.880
Yeah.
1061
00:57:23.880 --> 00:57:25.380
So it's not PODCONF approved.
1062
00:57:26.020 --> 00:57:27.140
No, that's right.
1063
00:57:27.840 --> 00:57:33.180
By the way, we keep on being denied our PODCONF approval.
1064
00:57:33.480 --> 00:57:35.760
Like they denied us again recently.
1065
00:57:36.000 --> 00:57:36.520
That's insane.
1066
00:57:37.040 --> 00:57:38.500
It really is pretty offensive.
1067
00:57:38.720 --> 00:57:42.940
I mean, like we try hard here to talk about all the things that we were
1068
00:57:42.940 --> 00:57:44.120
supposed to talk about.
1069
00:57:44.700 --> 00:57:47.020
I don't know what we're missing to be approved.
1070
00:57:48.340 --> 00:57:51.300
Is there like management you can complain to?
1071
00:57:52.700 --> 00:57:55.780
There's probably multiple levels of management you can complain to.
1072
00:57:56.420 --> 00:57:59.500
I mean, you know, all I want is the hat and T-shirt so I can
1073
00:57:59.500 --> 00:58:00.580
wear it at the conferences.
1074
00:58:02.200 --> 00:58:03.800
Well, Rob has those.
1075
00:58:03.880 --> 00:58:04.820
I've seen him with them.
1076
00:58:05.860 --> 00:58:09.940
Yeah, I feel like he's going to keep flexing on us until we get them.
1077
00:58:10.660 --> 00:58:12.800
Yeah, I mean, I don't know what else to say.
1078
00:58:12.920 --> 00:58:14.140
I mean, maybe I just need to...
1079
00:58:14.840 --> 00:58:15.540
We can have...
1080
00:58:16.320 --> 00:58:19.600
What if we have like an ETF episode?
1081
00:58:20.680 --> 00:58:21.920
Yeah, there we go.
1082
00:58:22.940 --> 00:58:29.260
You know, we can also have a trading course where we tell people how to buy
1083
00:58:29.260 --> 00:58:30.800
on green, sell on red, right?
1084
00:58:31.060 --> 00:58:32.160
Is that how it works?
1085
00:58:32.780 --> 00:58:33.120
Perfect.
1086
00:58:33.940 --> 00:58:36.120
Yeah, I don't know.
1087
00:58:36.160 --> 00:58:37.320
I just feel left out.
1088
00:58:37.600 --> 00:58:38.840
Very disappointing, you know?
1089
00:58:39.000 --> 00:58:43.560
You run a POD for this long and you don't get to be part of those
1090
00:58:43.560 --> 00:58:43.980
circles.
1091
00:58:44.720 --> 00:58:46.320
All right, business and finance.
1092
00:58:46.740 --> 00:58:47.400
I'm going to skip.
1093
00:58:48.120 --> 00:58:51.320
Although this River offer is kind of interesting.
1094
00:58:52.160 --> 00:58:56.900
I know it's a little Tradefy-ish, but I was talking to Alex and asking him
1095
00:58:56.900 --> 00:58:57.420
about it.
1096
00:58:58.360 --> 00:59:02.340
They're going to implement so that Bitcoin companies can use it as their
1097
00:59:02.340 --> 00:59:03.060
checking account.
1098
00:59:03.800 --> 00:59:07.080
Because Bitcoiners are all short fiat, right?
1099
00:59:07.500 --> 00:59:15.500
And nobody has a lot of fiat savings to put in a interest bearing account on
1100
00:59:15.500 --> 00:59:16.080
the fiat side.
1101
00:59:16.080 --> 00:59:18.160
But they all have operation accounts, right?
1102
00:59:18.720 --> 00:59:23.240
It would be really cool to be receiving interest on the operations account.
1103
00:59:23.760 --> 00:59:26.580
But to have an operations account, you need to be able to pay other things.
1104
00:59:26.800 --> 00:59:29.880
But anyways, I just found that interesting.
1105
00:59:30.980 --> 00:59:31.960
Yeah, I think it's exciting.
1106
00:59:32.520 --> 00:59:35.800
Really nice to have these as a bank account.
1107
00:59:36.060 --> 00:59:37.580
Get rid of my normal bank.
1108
00:59:37.920 --> 00:59:38.560
That's right.
1109
00:59:39.040 --> 00:59:44.020
And you keep on sending me my Bitcoin interest into my Bitcoin wallet, not into
1110
00:59:44.020 --> 00:59:45.780
fiat stuff.
1111
00:59:46.700 --> 00:59:51.500
Bitcoin Illustrator NoGood releases the art of NoGood, a self-published art
1112
00:59:51.500 --> 00:59:54.120
book showcasing five years of Bitcoin-themed illustrations.
1113
00:59:54.360 --> 00:59:55.100
It's beautiful.
1114
00:59:56.780 --> 00:59:57.500
Funding.
1115
00:59:58.000 --> 01:00:03.780
Bitcoin Freedom Technologies Research Firm 1A1Z releases a report covering how
1116
01:00:03.780 --> 01:00:05.600
Bitcoin Core development is funded.
1117
01:00:06.380 --> 01:00:12.560
OpenSats, we've released a million other funding grants recently.
1118
01:00:13.640 --> 01:00:15.980
Spyro announces grant renewals.
1119
01:00:16.460 --> 01:00:21.980
There's a lot of money these days for people to go work on non-profit Bitcoin
1120
01:00:21.980 --> 01:00:22.440
work.
1121
01:00:22.620 --> 01:00:23.380
You love to see it.
1122
01:00:23.660 --> 01:00:25.060
Pretty crazy, actually.
1123
01:00:25.840 --> 01:00:26.100
Yeah.
1124
01:00:27.000 --> 01:00:28.620
Tens of millions of dollars.
1125
01:00:29.280 --> 01:00:29.520
Hundreds.
1126
01:00:29.780 --> 01:00:32.980
It probably crossed hundreds of millions of dollars now.
1127
01:00:33.360 --> 01:00:33.680
Yeah.
1128
01:00:34.360 --> 01:00:36.620
It's quite crazy how quickly it happened, too.
1129
01:00:36.900 --> 01:00:40.540
I feel like four or five years ago, we were all like, there's no money in
1130
01:00:40.540 --> 01:00:40.840
Bitcoin.
1131
01:00:41.040 --> 01:00:41.660
It's dying.
1132
01:00:42.560 --> 01:00:44.580
Now, here we are.
1133
01:00:45.600 --> 01:00:45.700
Yeah.
1134
01:00:46.880 --> 01:00:47.760
All right.
1135
01:00:48.500 --> 01:00:49.180
Privacy.
1136
01:00:50.820 --> 01:00:59.020
Oh, Simple X, they wired the original Bitcoin hater outfit of, between quotes,
1137
01:00:59.120 --> 01:01:03.020
journalists, attacked Simple X because they have privacy.
1138
01:01:03.800 --> 01:01:05.240
Very, very uncouth.
1139
01:01:06.480 --> 01:01:07.460
And that's it.
1140
01:01:07.660 --> 01:01:11.720
I mean, oh, Libsac 256k1.
1141
01:01:11.720 --> 01:01:13.080
Finally has MuSig.
1142
01:01:13.760 --> 01:01:14.320
Yeah.
1143
01:01:14.720 --> 01:01:15.540
MuSig was merged.
1144
01:01:15.620 --> 01:01:18.640
I think we covered this in the last episode of the list.
1145
01:01:19.340 --> 01:01:20.580
It's nice to see it here again.
1146
01:01:21.080 --> 01:01:22.020
That's really cool.
1147
01:01:23.280 --> 01:01:24.580
Anything else here, guys?
1148
01:01:24.700 --> 01:01:28.780
I think we've covered all the politics stuff I'm not going to cover.
1149
01:01:29.920 --> 01:01:36.800
There was one news and noteworthy thing that we skipped over just to give a
1150
01:01:36.800 --> 01:01:37.680
pointer to people.
1151
01:01:38.340 --> 01:01:40.140
The BitKey team put out a paper.
1152
01:01:40.140 --> 01:01:44.780
It's called, I don't like the title because I don't think it describes what's
1153
01:01:44.780 --> 01:01:45.000
in it.
1154
01:01:45.080 --> 01:01:46.380
But it's actually a really good paper.
1155
01:01:46.520 --> 01:01:52.260
It's called Unlocking Mass-Market Self-Custody Secure and Private Smartphone
1156
01:01:52.260 --> 01:01:53.120
Bitcoin Wallets.
1157
01:01:53.360 --> 01:01:55.720
So that's a very marketing-y title.
1158
01:01:56.080 --> 01:02:02.780
But what's in the paper is they get into how BitKey is doing Frost integration.
1159
01:02:03.240 --> 01:02:06.640
They get into where all the different keys are held.
1160
01:02:06.640 --> 01:02:11.160
They get into the backend signer architecture and how that thing is locked
1161
01:02:11.160 --> 01:02:11.580
down.
1162
01:02:12.360 --> 01:02:16.400
There's some work that they're doing around using zero-knowledge proofs to
1163
01:02:16.400 --> 01:02:20.460
involve the backend signer in a privacy-preserving way.
1164
01:02:21.040 --> 01:02:26.340
So there's a bunch of really cutting-edge stuff being done around proof of
1165
01:02:26.340 --> 01:02:29.860
solvency, around blinded pins, around Frost.
1166
01:02:30.160 --> 01:02:35.300
And they wrote a paper describing all the gory details.
1167
01:02:35.300 --> 01:02:41.500
So if you're interested in those kinds of tools being incorporated into Bitcoin
1168
01:02:41.500 --> 01:02:45.540
wallets, they released the paper last week at TabConf, and there's some really
1169
01:02:45.540 --> 01:02:46.240
good stuff in it.
1170
01:02:46.860 --> 01:02:47.280
Nice.
1171
01:02:48.260 --> 01:02:50.280
They do like to release papers.
1172
01:02:53.420 --> 01:02:55.860
Remember when they did the architecture stuff?
1173
01:02:56.440 --> 01:02:57.120
There was a whole…
1174
01:02:57.760 --> 01:02:58.320
Yeah.
1175
01:02:58.760 --> 01:02:59.040
Neat.
1176
01:02:59.240 --> 01:03:00.220
I will check it out.
1177
01:03:00.840 --> 01:03:01.060
Yeah.
1178
01:03:02.200 --> 01:03:03.240
Very good, guys.
1179
01:03:03.240 --> 01:03:08.840
We've, I think people will listen to this one whole because we've covered all
1180
01:03:08.840 --> 01:03:09.620
of it in an hour.
1181
01:03:12.860 --> 01:03:14.680
Hopefully it's PodConf approved now.
1182
01:03:15.360 --> 01:03:15.580
Yeah.
1183
01:03:15.680 --> 01:03:17.900
I mean, we were low on tangents on this one.
1184
01:03:18.700 --> 01:03:18.920
Yeah.
1185
01:03:19.800 --> 01:03:21.620
Sorry to anyone that didn't fall asleep.
1186
01:03:21.820 --> 01:03:22.740
We tried our best.
1187
01:03:23.280 --> 01:03:23.540
Yeah.
1188
01:03:23.580 --> 01:03:24.300
Sorry, guys.
1189
01:03:24.460 --> 01:03:25.520
We're a little rusty.
1190
01:03:25.720 --> 01:03:28.240
It's been like a few weeks since we had a list.
1191
01:03:28.800 --> 01:03:29.360
It's been a minute.
1192
01:03:29.360 --> 01:03:33.600
Yeah, we need to get back into our groove and find the correct tangents.
1193
01:03:34.060 --> 01:03:39.140
As the orange president would say, we need to learn how to weave again.
1194
01:03:41.520 --> 01:03:42.460
That's great.
1195
01:03:45.020 --> 01:03:50.320
Anyways, do you guys have any updates on your DeGen stuff?
1196
01:03:51.020 --> 01:03:52.040
Updates coming soon.
1197
01:03:52.740 --> 01:03:58.840
I will say I'm giving a talk at OpNext in two weeks, I think, in Boston.
1198
01:03:59.460 --> 01:04:02.680
I'm going to leak a little bit of alpha, but it's okay, because everybody's
1199
01:04:02.680 --> 01:04:03.220
asleep already.
1200
01:04:03.860 --> 01:04:09.100
Something that I think has been missing from a lot of the Covenant and SoftFork
1201
01:04:09.100 --> 01:04:15.600
discussion has been, how are people actually going to use these things post
1202
01:04:15.600 --> 01:04:19.460
-activation to build applications and tools and services?
1203
01:04:20.180 --> 01:04:24.180
Something that I think we saw happen with Taproot was Taproot activated, and
1204
01:04:24.180 --> 01:04:27.500
then it took a long time for things to start getting rolled out.
1205
01:04:27.500 --> 01:04:30.860
We just talked about Music finally just got merged into LibSec.
1206
01:04:31.640 --> 01:04:36.880
With any of these Covenant proposals, having developer tooling that you can use
1207
01:04:36.880 --> 01:04:42.280
to actually build stuff with it is something that's not a core part of the
1208
01:04:42.280 --> 01:04:47.200
conversation, but it's an important piece of actually realizing the benefits.
1209
01:04:47.960 --> 01:04:52.120
Something that we've been working on internally is, if we think Cat or
1210
01:04:52.120 --> 01:04:58.740
something like Cat is going to happen, how do you safely, reliably, and
1211
01:04:58.740 --> 01:05:03.840
effectively build complex applications that use these crazy Cat scripts?
1212
01:05:03.980 --> 01:05:04.800
So, a Cat speaking?
1213
01:05:05.160 --> 01:05:05.720
Yeah, right.
1214
01:05:05.980 --> 01:05:07.460
Man, that would have been a great name.
1215
01:05:07.560 --> 01:05:09.220
Where were you a while ago?
1216
01:05:09.280 --> 01:05:15.140
Anyway, we're building some tooling internally to make it easier to compose Cat
1217
01:05:15.140 --> 01:05:15.640
scripts together.
1218
01:05:15.640 --> 01:05:20.880
So, going to be talking about that, opening that up, but also just talking
1219
01:05:20.880 --> 01:05:26.440
about design principles and what are the parts of application development that
1220
01:05:26.440 --> 01:05:32.520
are really hard when you have complex Covenants and interactions between them?
1221
01:05:32.580 --> 01:05:36.360
There's a lot of stuff around witness building and stack management that just
1222
01:05:36.360 --> 01:05:37.040
gets really hard.
1223
01:05:37.040 --> 01:05:45.960
I still don't understand why the JPEG people want Covenants or Cat.
1224
01:05:46.700 --> 01:05:52.660
Maybe I knew at some point, I kind of forgot, but why is it?
1225
01:05:53.480 --> 01:06:00.000
Yeah, I think there's kind of two or three different directions that the JPEG
1226
01:06:00.000 --> 01:06:03.260
people want to be able to do things in.
1227
01:06:03.260 --> 01:06:05.660
One direction is vaults.
1228
01:06:06.620 --> 01:06:11.040
If you have all your money in a small number of UTXOs in a Bitcoin wallet,
1229
01:06:11.680 --> 01:06:16.420
being able to have velocity control or some ability to claw back.
1230
01:06:17.200 --> 01:06:24.580
Something that the JPEG enjoyers are exposed to more frequently than other
1231
01:06:24.580 --> 01:06:31.900
users of Bitcoin is their Bitcoin wallets interacting with internet services.
1232
01:06:32.650 --> 01:06:37.500
You've got some JPEGs in your wallet, you want to prove that you have control
1233
01:06:37.500 --> 01:06:42.440
over them to some Discord bot, but you want to make sure that your JPEGs can't
1234
01:06:42.440 --> 01:06:42.840
be stolen.
1235
01:06:43.220 --> 01:06:48.940
So having more sophisticated spending policy and having flow control or
1236
01:06:48.940 --> 01:06:53.160
velocity control over your wallet is something that I think is important for
1237
01:06:53.160 --> 01:06:57.980
all Bitcoiners, but it's felt acutely by the JPEG enjoyers.
1238
01:06:57.980 --> 01:07:04.380
And then also, I think people want to be able to do more complex kinds of
1239
01:07:04.380 --> 01:07:07.720
Bitcoin transactions with Bitcoin native assets.
1240
01:07:07.900 --> 01:07:12.380
So there's a service out there that'll let you borrow Bitcoin against your
1241
01:07:12.380 --> 01:07:17.140
JPEGs, using DLCs and using PSBTs.
1242
01:07:17.560 --> 01:07:21.620
It'd be really great to be able to make those multi-party or be able to
1243
01:07:21.620 --> 01:07:24.900
buy or sell those positions and just make them more liquid.
1244
01:07:24.900 --> 01:07:29.380
So I'd say security and more complicated kinds of contracts.
1245
01:07:29.560 --> 01:07:34.060
Okay, so it's not really JPEG specific because all this stuff is like things
1246
01:07:34.060 --> 01:07:35.860
that normal Bitcoiners want.
1247
01:07:36.440 --> 01:07:38.520
Yeah, it's not JPEG specific.
1248
01:07:38.680 --> 01:07:44.600
It's just that the JPEG enjoyers have a market where you can buy and sell
1249
01:07:44.600 --> 01:07:50.560
things with Bitcoin that are, you know, incomparable with Bitcoin script.
1250
01:07:50.560 --> 01:07:54.280
So like you can do atomic trades in the same way that like you can't do
1251
01:07:54.280 --> 01:07:57.020
an atomic swap for like a car or a sandwich.
1252
01:07:57.180 --> 01:08:01.820
I know, but you can do that with like for like lightning contracts purposes,
1253
01:08:02.020 --> 01:08:02.120
right?
1254
01:08:02.420 --> 01:08:08.840
Yeah, because like you guys are so cat oriented on the branding of the
1255
01:08:08.840 --> 01:08:12.300
wizarding that like I thought that was like something that was like very
1256
01:08:12.300 --> 01:08:14.560
specific to the JPEGs.
1257
01:08:14.720 --> 01:08:19.060
And it seems to me that everything you guys talking about is all sort of things
1258
01:08:19.060 --> 01:08:20.300
that every Bitcoiner wants.
1259
01:08:21.140 --> 01:08:26.120
Yeah, I mean, I think, you know, the reason why we're pushing cat is it's like
1260
01:08:26.120 --> 01:08:28.700
a really general purpose construct.
1261
01:08:29.160 --> 01:08:33.939
So like we think that it might be a way to kind of get through some
1262
01:08:33.939 --> 01:08:37.500
of the bike shedding about like, oh, I want this proposal because it enables
1263
01:08:37.500 --> 01:08:41.760
thing X but not Y or somebody says I want this other thing that enables thing
1264
01:08:41.760 --> 01:08:42.979
Y but not Z.
1265
01:08:43.500 --> 01:08:47.420
Cat kind of enables everything like everything's kind of annoying to do in cat,
1266
01:08:47.500 --> 01:08:48.319
but you can do it.
1267
01:08:48.319 --> 01:08:52.779
And then if you can do it in cat, but it's a little bit clunky, then
1268
01:08:52.779 --> 01:08:56.380
we can actually go and look at what people are using it for on chain and
1269
01:08:56.380 --> 01:09:00.960
say, hey, look, this amount of block space is being used for vaults.
1270
01:09:01.040 --> 01:09:05.180
So maybe we should fork in op vault and make it more efficient or, oh, this,
1271
01:09:05.899 --> 01:09:10.260
you know, so much usage is going towards crazy lightning construction.
1272
01:09:10.520 --> 01:09:12.060
So maybe we should like optimize that.
1273
01:09:12.140 --> 01:09:15.760
But instead of like, arguing about it from first principles, we can actually
1274
01:09:15.760 --> 01:09:17.720
use like the market to decide.
1275
01:09:18.359 --> 01:09:22.840
And then the other thing that we like about cat is it's useful for things like,
1276
01:09:22.960 --> 01:09:24.359
you know, validating Merkle trees.
1277
01:09:24.840 --> 01:09:28.779
And it's useful for like stitching parts of scripts together, which we think
1278
01:09:28.779 --> 01:09:32.899
are important for bridging to like other L2s where you can have different
1279
01:09:32.899 --> 01:09:37.899
transaction semantics than what lightning gives you or better or, you know,
1280
01:09:37.920 --> 01:09:39.640
more interesting than what lightning gives you.
1281
01:09:39.960 --> 01:09:42.359
And then also cats are just very memeable, right?
1282
01:09:42.359 --> 01:09:46.439
I don't know, but again, like every single like, because I kind of like tuned
1283
01:09:46.439 --> 01:09:50.800
out a little bit of like controversies and things like that.
1284
01:09:50.800 --> 01:09:54.800
And like, yeah, there is literally nothing on that that sounds to me like
1285
01:09:54.800 --> 01:10:00.180
something either controversial that like JPEG disrespectors don't want, like
1286
01:10:00.180 --> 01:10:03.260
everything there like sounds great to me.
1287
01:10:04.120 --> 01:10:08.300
So I was just curious, you know, like it's like there is no gotcha.
1288
01:10:08.600 --> 01:10:10.360
OK, interesting.
1289
01:10:10.900 --> 01:10:15.520
I mean, you know, like the first non-trivial cat covenant that we released was
1290
01:10:15.520 --> 01:10:16.480
a vault, right?
1291
01:10:16.620 --> 01:10:21.380
Like the first cat covenant that I put on Twitter was this like circular thing
1292
01:10:21.380 --> 01:10:23.260
where you can only send the money back to yourself forever.
1293
01:10:23.580 --> 01:10:26.200
But like the first one that we put on GitHub was like a vault.
1294
01:10:26.600 --> 01:10:31.640
And, you know, it's like I think the JPEG enjoyers want the same thing that
1295
01:10:31.640 --> 01:10:34.740
every Bitcoin or once they want to be able to like do more stuff with their
1296
01:10:34.740 --> 01:10:35.140
Bitcoin.
1297
01:10:35.360 --> 01:10:36.460
Not lose UTXOs.
1298
01:10:36.460 --> 01:10:37.340
Yeah, yeah.
1299
01:10:37.580 --> 01:10:42.240
And be able to say like, hey, there's a trade that we can do right now,
1300
01:10:42.320 --> 01:10:45.500
but it's very like capital inefficient because everything is a two is like a
1301
01:10:45.500 --> 01:10:47.480
two party trade.
1302
01:10:47.620 --> 01:10:48.000
Yeah.
1303
01:10:48.040 --> 01:10:51.200
But what we really want to be able to do is say, put everybody in a
1304
01:10:51.200 --> 01:10:53.360
pile and make it like more capital efficient.
1305
01:10:53.580 --> 01:10:56.120
And it turns out that's also what you need for like payment infrastructure.
1306
01:10:56.400 --> 01:10:56.580
Right.
1307
01:10:56.680 --> 01:11:00.840
So we're trying to build the same kind of primitives that I think all
1308
01:11:00.840 --> 01:11:01.720
Bitcoiners want.
1309
01:11:01.720 --> 01:11:06.000
It's just we're doing it in a market where people are trading for meme coins
1310
01:11:06.000 --> 01:11:06.740
and JPEGs.
1311
01:11:07.980 --> 01:11:13.460
Yeah, no, I mean, it's yeah, it's I'm always like weirded out when like the
1312
01:11:13.460 --> 01:11:16.560
controversy like exists where there isn't one.
1313
01:11:17.040 --> 01:11:20.580
I mean, I can understand that people who are against covenant, covenants is
1314
01:11:20.580 --> 01:11:20.700
right.
1315
01:11:20.740 --> 01:11:23.180
Like that's very reasonable like position, right?
1316
01:11:23.180 --> 01:11:25.740
Like you don't want to change Bitcoin to have covenants like fair.
1317
01:11:26.600 --> 01:11:28.240
You know, lots of people don't want that.
1318
01:11:29.440 --> 01:11:29.660
Cool.
1319
01:11:30.300 --> 01:11:33.060
So cat has nothing to do with the JPEGs.
1320
01:11:33.780 --> 01:11:38.620
It's just more Bitcoin or shit that happens to be useful to the JPEG enjoyers.
1321
01:11:40.100 --> 01:11:42.480
That's that clear is that.
1322
01:11:42.980 --> 01:11:45.700
All right, guys, listen, this this was great.
1323
01:11:46.200 --> 01:11:48.400
It was probably the fastest list we have ever done.
1324
01:11:48.820 --> 01:11:50.760
I really appreciate your time.
1325
01:11:51.000 --> 01:11:55.140
I'm looking forward to seeing the covenant stuff and the cat stuff we're going
1326
01:11:55.140 --> 01:11:55.940
to be working on.
1327
01:11:55.940 --> 01:11:59.720
I want to see covenants for for many reasons, as you guys all know.
1328
01:11:59.900 --> 01:12:01.860
And I've harped here enough about that before.
1329
01:12:02.720 --> 01:12:08.660
And I hope to have you guys soon again on another list to to take a
1330
01:12:08.660 --> 01:12:14.420
lot of weaving tangents and and know you like a real person, as they call it.
1331
01:12:15.220 --> 01:12:15.560
That's right.
1332
01:12:15.960 --> 01:12:16.460
That's right.
1333
01:12:17.040 --> 01:12:17.940
Appreciate it, guys.
1334
01:12:18.060 --> 01:12:18.520
Thank you.
1335
01:12:19.000 --> 01:12:19.300
Great.
1336
01:12:19.520 --> 01:12:19.820
Thanks.
1337
01:12:20.340 --> 01:12:21.000
Thank you.
1338
01:12:21.220 --> 01:12:21.900
Thank you, Ben.
1339
01:12:23.600 --> 01:12:26.200
Thanks for listening.
1340
01:12:26.460 --> 01:12:28.520
For more resources, check the show notes.
1341
01:12:28.800 --> 01:12:30.280
We put a lot of effort into them.
1342
01:12:30.580 --> 01:12:32.560
And remember, we don't have a crystal ball.
1343
01:12:32.780 --> 01:12:34.200
So let us know about your project.
1344
01:12:34.540 --> 01:12:38.160
Visit Bitcoin.review to find out how to get in touch.