ТРАНСКРИПЦИЯ 🔗
WEBVTT
1
00:00:01.830 --> 00:00:06.110
Hello and welcome to the Bitcoin.review podcast, where we explore developments
2
00:00:06.110 --> 00:00:09.210
and projects with the people who actually make them happen.
3
00:00:09.510 --> 00:00:13.130
The show is supported by Bot 2.0, SaaT Streaming and CoinKite.
4
00:00:13.350 --> 00:00:15.350
If you're a new listener, I'm NVK.
5
00:00:15.630 --> 00:00:19.230
I run CoinKite, where we've been helping people secure their Bitcoins for over
6
00:00:19.230 --> 00:00:19.650
a decade.
7
00:00:20.050 --> 00:00:22.950
We make the cold card and fun products like the Block Clock.
8
00:00:23.150 --> 00:00:25.690
You can find more information about it on CoinKite.com.
9
00:00:29.050 --> 00:00:34.890
Hello and welcome back to the Bitcoin.review, the show that no one listens to.
10
00:00:35.390 --> 00:00:37.550
Welcome back, Mr. Rob Hamilton.
11
00:00:38.190 --> 00:00:39.250
Thanks for having me.
12
00:00:39.830 --> 00:00:40.810
Mr. Odell.
13
00:00:41.510 --> 00:00:42.430
Good to be here.
14
00:00:43.270 --> 00:00:44.890
And the man who ships, Craig.
15
00:00:45.690 --> 00:00:47.810
Yeah, another Bitcoin review.
16
00:00:48.130 --> 00:00:49.650
Let's see what's going on in the world.
17
00:00:49.810 --> 00:00:50.710
Not much, I think.
18
00:00:51.470 --> 00:00:52.050
That's right.
19
00:00:52.050 --> 00:00:57.490
I mean, since this is against my will, I'm going to put that out there, but
20
00:00:57.490 --> 00:01:03.410
Odell wants to address some of the drama of Core, Filters and Operate Turn.
21
00:01:03.489 --> 00:01:04.670
So we want to hear his opinion.
22
00:01:05.430 --> 00:01:05.970
Oh, no.
23
00:01:06.290 --> 00:01:07.710
I'll be back in 30 minutes.
24
00:01:09.130 --> 00:01:10.390
I'm filtering this out.
25
00:01:11.270 --> 00:01:12.730
I mean, this is fake news.
26
00:01:13.490 --> 00:01:14.430
What's your opinion?
27
00:01:15.350 --> 00:01:15.750
No, no, no.
28
00:01:15.750 --> 00:01:16.490
What's your opinion?
29
00:01:17.390 --> 00:01:25.450
My opinion, as I've stated many times on Rabbit Hole Recap, is that the witch
30
00:01:25.450 --> 00:01:30.570
hunt element of the Operate Turn debate is really disappointing, but kind of
31
00:01:30.570 --> 00:01:31.230
unavoidable.
32
00:01:31.750 --> 00:01:34.130
I feel like that's just what happens in social.
33
00:01:34.510 --> 00:01:36.410
That's what social prioritizes.
34
00:01:37.210 --> 00:01:42.650
But the bright side to me is that I think the newer people are starting to
35
00:01:42.650 --> 00:01:49.850
realize what the key fundamental check on developers is in this ecosystem,
36
00:01:49.850 --> 00:01:55.470
which is that all code is open source, that anyone can verify it or modify it
37
00:01:55.470 --> 00:01:59.170
without permission, and that ultimately you are in control of what you decide
38
00:01:59.170 --> 00:02:03.430
to run, which was kind of lost, I think, on people.
39
00:02:03.630 --> 00:02:07.870
People were starting to get into the flow of basically auto-updates, just
40
00:02:07.870 --> 00:02:12.130
clicking update, seeing the bright blue button on their umbrella or start nine
41
00:02:12.130 --> 00:02:14.030
and just immediately clicking it.
42
00:02:14.630 --> 00:02:18.790
And I think now there will be at least more thought in that process.
43
00:02:19.010 --> 00:02:22.490
And I think that is probably the single biggest takeaway and single biggest
44
00:02:22.490 --> 00:02:23.670
benefit from all of this.
45
00:02:24.510 --> 00:02:26.770
Yeah, that's my overarching take.
46
00:02:26.870 --> 00:02:28.870
But I'm really curious on your opinion, RVK.
47
00:02:29.150 --> 00:02:33.250
No, but wait, outside of the meta part, what do you actually think about the
48
00:02:33.250 --> 00:02:34.950
Operate Turn and the filter change?
49
00:02:35.730 --> 00:02:38.990
I think I liked it the way it was.
50
00:02:39.170 --> 00:02:44.550
I don't really understand exactly why this is the hill that some people want to
51
00:02:44.550 --> 00:02:45.010
die on.
52
00:02:45.570 --> 00:02:51.270
It was already configurable, so if you wanted to raise your limit on your own
53
00:02:51.270 --> 00:02:52.790
node, you could easily do that.
54
00:02:53.530 --> 00:03:00.590
So I know right now it seems like the main PR that probably will get merged
55
00:03:00.590 --> 00:03:07.010
increases the limit, keeps the configuration, and marks it deprecated, which
56
00:03:07.010 --> 00:03:09.790
probably means that they're just going to remove the option in the next
57
00:03:09.790 --> 00:03:10.210
release.
58
00:03:10.690 --> 00:03:15.130
There is some discussion about the meaning of deprecation, but...
59
00:03:15.130 --> 00:03:15.890
Yeah, exactly.
60
00:03:15.890 --> 00:03:19.570
Now everyone's arguing about the semantics of what deprecation means, which is
61
00:03:19.570 --> 00:03:20.770
incredibly productive.
62
00:03:21.550 --> 00:03:26.290
But I think ultimately, I want to see node operators have more options, not
63
00:03:26.290 --> 00:03:26.710
less.
64
00:03:27.330 --> 00:03:32.190
I think, ideally, we see as many people run nodes to interact with the network
65
00:03:32.190 --> 00:03:33.570
in a trust-minimized way.
66
00:03:34.110 --> 00:03:40.270
But the core of the network will always be like a hardcore ride-or-die type
67
00:03:40.270 --> 00:03:41.630
of class, I think.
68
00:03:41.630 --> 00:03:46.530
And for those people, I think we should have more options, not less.
69
00:03:46.670 --> 00:03:48.990
I don't think we should be treating them like grandmas.
70
00:03:49.410 --> 00:03:52.990
I think we should be expecting them to be practicing personal responsibility
71
00:03:52.990 --> 00:03:56.170
and be more educated on the situations.
72
00:03:56.870 --> 00:04:00.790
And so give them more sovereignty, give them more agency, not less going
73
00:04:00.790 --> 00:04:01.770
forward would be better.
74
00:04:02.270 --> 00:04:04.250
You're spot on in some things there.
75
00:04:04.410 -->
Load full transcript
00:04:08.090
I mean, reality is most people...
76
00:04:08.090 --> 00:04:12.190
Now people are trying to dunk on core, on knots as well.
77
00:04:12.970 --> 00:04:17.050
And most people don't even check the binary signature of the core client they
78
00:04:17.050 --> 00:04:19.329
download from a website and just run it.
79
00:04:19.529 --> 00:04:20.750
They have no idea what they're doing.
80
00:04:21.210 --> 00:04:24.430
And also running a node doesn't mean anything unless you actually have
81
00:04:24.430 --> 00:04:27.250
economical capacity going through that node.
82
00:04:28.130 --> 00:04:30.090
So let's move on to Craig.
83
00:04:30.130 --> 00:04:32.550
Do you want to voice some opinions on the topic as well?
84
00:04:33.550 --> 00:04:38.170
Yeah, I mean, I concur with the sort of meta thoughts.
85
00:04:38.850 --> 00:04:45.170
And it's really nice to see people caring on the good side about running nodes.
86
00:04:45.370 --> 00:04:49.230
If this is what it takes to get people to care about running nodes, well,
87
00:04:49.250 --> 00:04:50.890
that's, I guess, a good thing.
88
00:04:51.570 --> 00:04:57.110
But if I was to look at the whole how important is this issue on the
89
00:04:57.110 --> 00:05:03.090
grand scheme of things, it feels to me a bit like people are looking to cross
90
00:05:03.090 --> 00:05:07.830
a road at a zebra crossing and they're wondering about whether they should walk
91
00:05:07.830 --> 00:05:12.190
on the black parts or the white parts while a bus is bearing down on them.
92
00:05:12.970 --> 00:05:17.530
And that bus is really this court case we have, samurai wallet.
93
00:05:17.890 --> 00:05:22.530
We have a court case which will decide the ability whether we can run nodes or
94
00:05:22.530 --> 00:05:24.450
not, certainly in the United States.
95
00:05:24.450 --> 00:05:30.590
And it just seems like that is a more important, like if I could see 10
96
00:05:30.590 --> 00:05:36.470
% of the outrage directed towards the op-return issue on that particular issue,
97
00:05:36.590 --> 00:05:37.530
that would be good.
98
00:05:37.690 --> 00:05:42.810
But that's obviously a lot of nuance and complexity and legal arguments.
99
00:05:43.150 --> 00:05:44.430
So you don't see it.
100
00:05:44.510 --> 00:05:50.910
But for me, that is a far more critical issue right now than how much data
101
00:05:50.910 --> 00:05:52.890
can be placed in an op-return.
102
00:05:53.790 --> 00:05:58.430
I think you touched a few points there, very important.
103
00:05:59.290 --> 00:06:05.490
And my sentiment around this is starting to become very bearish on some aspects
104
00:06:05.490 --> 00:06:06.210
of the core.
105
00:06:06.570 --> 00:06:09.110
It feels like a lot of work is make work.
106
00:06:09.510 --> 00:06:12.070
A lot of this shit is completely unnecessary.
107
00:06:12.850 --> 00:06:15.470
And we have a lot of bigger fish to fry.
108
00:06:15.850 --> 00:06:20.490
But because people can't do big things like covenants or whatever, they sort of
109
00:06:20.490 --> 00:06:22.250
like start arguing about the little things.
110
00:06:22.250 --> 00:06:24.930
Maybe there's just too much philanthropic money in Bitcoin.
111
00:06:25.370 --> 00:06:28.470
Like it's just too many people working and people need some shit to do and now
112
00:06:28.470 --> 00:06:31.010
they want to change shit that doesn't need to be changed.
113
00:06:31.730 --> 00:06:36.370
I mean, could we maybe improve some fee estimation with this?
114
00:06:36.670 --> 00:06:36.790
Maybe.
115
00:06:38.130 --> 00:06:41.270
Does it actually move the needle on Bitcoin advancement?
116
00:06:41.790 --> 00:06:42.770
Fuck no, it doesn't.
117
00:06:43.250 --> 00:06:49.990
Does it cause a lot of grievances and issues and people quitting Twitter and
118
00:06:49.990 --> 00:06:50.770
all kinds of shit?
119
00:06:50.770 --> 00:06:51.090
Definitely.
120
00:06:51.770 --> 00:06:56.570
So it seems to me like the make work caused by too much money that is
121
00:06:56.570 --> 00:07:03.190
not economically market based is causing a lot of noise.
122
00:07:03.870 --> 00:07:07.330
While, you know, we have the Samurai case and there's a bunch of other things
123
00:07:07.330 --> 00:07:10.650
of similar importance going on that nobody gives a fuck.
124
00:07:11.290 --> 00:07:14.510
But you know, like Odell said, at least people are arguing about nodes and
125
00:07:14.510 --> 00:07:15.570
learning how to run a node.
126
00:07:16.030 --> 00:07:17.990
I do think we do need more distros.
127
00:07:17.990 --> 00:07:23.410
I think a little bit more competition to see who makes the official, unofficial
128
00:07:23.410 --> 00:07:25.610
release of core is important.
129
00:07:25.850 --> 00:07:28.630
I think deifying core developers is terrible.
130
00:07:28.750 --> 00:07:29.390
It's terrible for them.
131
00:07:29.410 --> 00:07:30.910
And I bet most of them don't like it.
132
00:07:31.730 --> 00:07:34.710
I think we have too much like of this theatric.
133
00:07:34.910 --> 00:07:37.090
Oh, we're so grateful for their work.
134
00:07:37.170 --> 00:07:39.030
They're fucking saints and this and that.
135
00:07:39.150 --> 00:07:40.550
It's just too much, man.
136
00:07:40.970 --> 00:07:43.570
You know, we need to tone it down.
137
00:07:43.690 --> 00:07:45.490
Like it's not a simple issue.
138
00:07:45.790 --> 00:07:46.790
Mr. Rob.
139
00:07:47.410 --> 00:07:48.970
At a very high level.
140
00:07:49.190 --> 00:07:55.230
I'll just say that my personal perspective is on removing the restriction for
141
00:07:55.230 --> 00:07:55.810
the opera turn.
142
00:07:56.190 --> 00:07:59.670
That's a longer conversation outside the meta core governance.
143
00:08:00.590 --> 00:08:00.710
Yeah.
144
00:08:00.890 --> 00:08:05.190
And for me, there's almost like two discussions, right?
145
00:08:05.230 --> 00:08:09.170
There's like the at the protocol level, understanding this proposal change
146
00:08:09.170 --> 00:08:12.090
versus the meta discussion on how
Bitcoin governance works.
147
00:08:12.930 --> 00:08:17.110
I think the one on the meta discussion is a lot messier in trying to untangle.
148
00:08:17.310 --> 00:08:17.810
I'd agree.
149
00:08:18.290 --> 00:08:21.270
It's funny because the my initial gut reaction is we need competing
150
00:08:21.270 --> 00:08:22.950
implementations like like a theorem.
151
00:08:23.530 --> 00:08:28.790
But the difference here is that the nature of Bitcoin consensus code is that
152
00:08:28.790 --> 00:08:30.790
it's pretty well understood.
153
00:08:30.970 --> 00:08:35.090
And even something like knots, which does a couple policy changes to my
154
00:08:35.090 --> 00:08:39.250
understanding and knowledge doesn't do a consensus change for anything, right?
155
00:08:39.289 --> 00:08:44.970
It's all policy dot CP files and all of these extra things and adding features.
156
00:08:44.970 --> 00:08:46.950
I personally run core.
157
00:08:47.210 --> 00:08:49.170
My company, Anchor Watch, runs core.
158
00:08:49.630 --> 00:08:52.810
I think if you're looking at alternate implementations, there's certain
159
00:08:52.810 --> 00:08:56.050
developer operations hygiene that needs to start being looked at.
160
00:08:56.250 --> 00:09:00.630
Like Luke just direct rips from his local into master and like makes releases.
161
00:09:01.190 --> 00:09:05.130
There's this thing called GUX, which used to be the Gideon signature chain.
162
00:09:05.630 --> 00:09:09.990
And so you have like 15, 20, it's like somewhere between 12 and like 20
163
00:09:09.990 --> 00:09:11.930
different developers on core.
164
00:09:12.130 --> 00:09:15.810
When a new release gets made, they all build it on their own separate machines
165
00:09:15.810 --> 00:09:19.690
and sign with their PGP key that, hey, this is the exact binary I got to.
166
00:09:20.170 --> 00:09:24.590
For knots, it's Luke and like three other people and two of them I think work
167
00:09:24.590 --> 00:09:25.890
at Ocean, right?
168
00:09:25.930 --> 00:09:29.070
So like it's not the same level of distributed people that are like not
169
00:09:29.070 --> 00:09:29.830
trusting verifying.
170
00:09:29.990 --> 00:09:32.690
I know NDK opened up with most people aren't checking signatures.
171
00:09:33.070 --> 00:09:34.790
I'm one of the people that do, right?
172
00:09:34.910 --> 00:09:35.490
I'm also like...
173
00:09:36.110 --> 00:09:36.270
Liar!
174
00:09:38.510 --> 00:09:40.450
And there's levels of checking it, right?
175
00:09:40.490 --> 00:09:43.630
There's doing the full deterministic reproducible build and checking the
176
00:09:43.630 --> 00:09:45.150
signature chains of the devs.
177
00:09:45.230 --> 00:09:47.590
And there's also just checking the sign binary, right?
178
00:09:47.690 --> 00:09:50.410
Like there's levels to how deep you want to go down that rabbit hole.
179
00:09:51.030 --> 00:09:55.730
I don't think a lot of the current crew of the core devs or they're not
180
00:09:55.730 --> 00:09:58.570
used to having this much public attention on them from a wider circle.
181
00:09:58.870 --> 00:10:04.590
I noticed that GMax came out of like, you know, his retirement or whatever to
182
00:10:04.590 --> 00:10:10.190
come comment on the poll request, voicing his support and basically saying, I
183
00:10:10.190 --> 00:10:12.950
haven't seen a good argument yet in this poll request.
184
00:10:13.030 --> 00:10:15.730
And if they want to come forward, I'll, you know, deconstruct those arguments.
185
00:10:15.970 --> 00:10:17.550
I haven't seen people responding to him yet.
186
00:10:18.030 --> 00:10:22.030
But I think it's interesting to see him kind of come out and trying to firm
187
00:10:22.030 --> 00:10:24.770
up structure from like Bitcoin as a software project.
188
00:10:25.350 --> 00:10:26.110
But it's messy.
189
00:10:26.450 --> 00:10:27.330
It's really messy.
190
00:10:27.850 --> 00:10:31.790
The beautiful thing about Bitcoin too is unless you're using like actually
191
00:10:31.790 --> 00:10:35.010
nothing in this new release so far, you could just run version 29 for a long
192
00:10:35.010 --> 00:10:35.270
time.
193
00:10:35.710 --> 00:10:38.910
You should be really running version 21, but that's a different story.
194
00:10:38.910 --> 00:10:41.110
21 is when Taproot got activated.
195
00:10:42.370 --> 00:10:44.010
Segwit was 14, right?
196
00:10:44.230 --> 00:10:45.010
Segwit was 14.
197
00:10:45.810 --> 00:10:47.730
Yeah, no, you can roll back to 14, I think.
198
00:10:47.930 --> 00:10:48.050
Yeah.
199
00:10:48.610 --> 00:10:49.050
You could.
200
00:10:49.390 --> 00:10:52.370
You wouldn't be enforcing the consensus rules on your node for receiving money.
201
00:10:52.950 --> 00:10:56.350
But the other part of this too is just the nature of the miners, right?
202
00:10:56.490 --> 00:10:59.590
And there's a difference between consensus rules and policy.
203
00:11:00.050 --> 00:11:03.550
And you only need like five to 10% of the network to enforce a policy
204
00:11:03.550 --> 00:11:05.450
rule for it to be effective across the network.
205
00:11:05.450 --> 00:11:08.730
Most miners don't run core spec.
206
00:11:09.110 --> 00:11:13.510
They run patches of core because all of them have their special needs.
207
00:11:13.710 --> 00:11:20.290
So we already have distros in a way of core at the largest hash rates.
208
00:11:20.650 --> 00:11:20.750
Yeah.
209
00:11:21.130 --> 00:11:27.290
I think ephemeral core group wanted to de-escalate and lower the temperature.
210
00:11:27.670 --> 00:11:31.150
I would highly recommend releasing more distros.
211
00:11:31.650 --> 00:11:34.750
Binary is complete with different options on them.
212
00:11:34.750 --> 00:11:40.790
I know it's very counter to the engineer mindset to have different sort of
213
00:11:40.790 --> 00:11:42.850
releases when it comes to software like this.
214
00:11:43.190 --> 00:11:45.910
But maybe it helps go somewhere.
215
00:11:46.070 --> 00:11:49.570
I mean, you know, if it wasn't for Shaoling Fry, we
wouldn't have a UASF
216
00:11:49.570 --> 00:11:50.370
release, right?
217
00:11:50.450 --> 00:11:55.250
Like I think it's important and it helps people also have an escape valve,
218
00:11:55.570 --> 00:11:58.390
right, for the pressure, I think.
219
00:11:58.390 --> 00:12:05.230
And also like belittling like the users, you know, it's not a great way of
220
00:12:05.230 --> 00:12:06.370
attacking this problem.
221
00:12:07.070 --> 00:12:10.390
You know, there's a lot of users out there that are big economic actors in this
222
00:12:10.390 --> 00:12:10.730
space.
223
00:12:11.010 --> 00:12:11.490
Yeah.
224
00:12:11.830 --> 00:12:16.070
You know, they may sound retarded on Twitter, but it doesn't make them small
225
00:12:16.070 --> 00:12:16.790
ruddlers either.
226
00:12:16.910 --> 00:12:18.250
You're talking about Mr. Hoddle, right?
227
00:12:21.290 --> 00:12:23.490
Actually, Mr. Hoddle is pro-change.
228
00:12:24.010 --> 00:12:25.550
He wants four airdrops.
229
00:12:25.910 --> 00:12:27.290
Yes, airdrops, please.
230
00:12:27.290 --> 00:12:31.350
I mean, I have another question on that tangent for you guys.
231
00:12:31.530 --> 00:12:35.670
I mean, so I'm also pro-competing implementations.
232
00:12:36.170 --> 00:12:37.830
Once again, just more choice, the better.
233
00:12:38.270 --> 00:12:42.210
As long as the consensus code is sacred, right?
234
00:12:42.330 --> 00:12:43.330
That's the risk, Matt.
235
00:12:43.490 --> 00:12:43.910
I know.
236
00:12:44.250 --> 00:12:45.810
But try not to fuck with that too much.
237
00:12:46.290 --> 00:12:52.830
But with all that said, do you guys think the chances we see a successful soft
238
00:12:52.830 --> 00:12:57.010
fork of any of the current proposals has pretty much gone to zero at this
239
00:12:57.010 --> 00:12:57.330
point?
240
00:12:57.470 --> 00:12:58.170
I don't know.
241
00:12:58.250 --> 00:12:59.150
I just won my airdrop.
242
00:12:59.330 --> 00:12:59.650
I disagree.
243
00:13:00.050 --> 00:13:00.410
I don't know.
244
00:13:00.530 --> 00:13:05.610
I think, you know, once we're in a world where the Bitcoin kernel is a thing,
245
00:13:05.750 --> 00:13:09.210
where it actually exists, I think that is a different world from today.
246
00:13:09.310 --> 00:13:12.010
I think we're going to see what NVK is asking for.
247
00:13:12.330 --> 00:13:16.310
We're going to see a lot of different flavors of Bitcoin built on the Bitcoin
248
00:13:16.310 --> 00:13:17.350
kernel coming out.
249
00:13:17.470 --> 00:13:20.270
I'd love to see a flavor which has an address index in it.
250
00:13:20.310 --> 00:13:21.610
For example, that would be great.
251
00:13:21.650 --> 00:13:22.050
Yes.
252
00:13:22.050 --> 00:13:26.270
So people didn't have to install Bitcoin Core and an Electrum server.
253
00:13:26.450 --> 00:13:26.690
Right.
254
00:13:26.750 --> 00:13:27.670
Just to get going.
255
00:13:27.790 --> 00:13:30.270
Wouldn't it be great if we just had one installation?
256
00:13:30.430 --> 00:13:32.470
That would be something that users actually want.
257
00:13:32.890 --> 00:13:36.850
Well, imagine if people were working on that instead of, like, arguing about
258
00:13:36.850 --> 00:13:37.330
filters.
259
00:13:38.190 --> 00:13:38.290
Right.
260
00:13:38.650 --> 00:13:39.090
Exactly.
261
00:13:39.250 --> 00:13:39.450
Right.
262
00:13:39.630 --> 00:13:43.330
And that, to be fair, there's many Bitcoin Core devs who are working on the
263
00:13:43.330 --> 00:13:45.130
Bitcoin kernel, and they want this as well.
264
00:13:45.230 --> 00:13:45.410
Right.
265
00:13:45.430 --> 00:13:47.190
They want to have this.
266
00:13:47.290 --> 00:13:47.430
Yeah.
267
00:13:47.530 --> 00:13:49.710
So it's not like it's being pushed back on.
268
00:13:49.710 --> 00:13:52.050
But it is hard to do, from what I understand.
269
00:13:52.190 --> 00:13:53.010
It is moving forward.
270
00:13:53.130 --> 00:13:57.130
It's a multi-, a many-year effort that is gradually moving forward.
271
00:13:57.270 --> 00:13:58.410
There are people working on it.
272
00:13:58.470 --> 00:14:00.470
But that's the day that I'm looking forward to.
273
00:14:01.450 --> 00:14:01.750
Okay.
274
00:14:02.250 --> 00:14:07.110
Is there anything else on this topic that is worth addressing, or should we
275
00:14:07.110 --> 00:14:08.070
move on with our lives?
276
00:14:09.150 --> 00:14:10.670
Most of it's been said at this point.
277
00:14:11.290 --> 00:14:12.650
Yeah, I agree with Craig.
278
00:14:12.890 --> 00:14:17.910
So the Libitcoin kernel is the idea of separating the consensus from everything
279
00:14:17.910 --> 00:14:21.090
else, so that you can safely build out these other implementations.
280
00:14:21.350 --> 00:14:22.250
That makes sense to me.
281
00:14:22.650 --> 00:14:27.470
Now, my point is, on these current software proposals, like the amount of
282
00:14:27.470 --> 00:14:33.350
contention we've seen over a policy change, which is not consensus-based and
283
00:14:33.350 --> 00:14:38.770
can be overridden by sending transactions directly to miners already, how do
284
00:14:38.770 --> 00:14:44.030
you see something like CTV actually successfully getting pushed through?
285
00:14:44.490 --> 00:14:45.150
No, no, no, no.
286
00:14:45.150 --> 00:14:48.950
See, like, that's a monumental consensus change, Matt.
287
00:14:49.310 --> 00:14:53.090
Like, you know, and depending how it's done, it can be a hard one.
288
00:14:53.250 --> 00:14:54.110
That's my point.
289
00:14:54.650 --> 00:14:55.290
No, no, no, no.
290
00:14:55.330 --> 00:14:59.510
Well, like, I think the only thing you're going to end up seeing is the soft
291
00:14:59.510 --> 00:15:04.650
consensus, so standardness things being changed, and also additional features
292
00:15:04.650 --> 00:15:07.310
or other things that are non-related to consensus.
293
00:15:07.970 --> 00:15:09.410
If you change consensus, you fork.
294
00:15:10.130 --> 00:15:16.590
I think I would take the other side of that insofar as, even for policy things,
295
00:15:16.630 --> 00:15:20.230
if this PR gets merged, even with all this hullabaloo and all this stuff, like,
296
00:15:20.730 --> 00:15:25.010
the maintainers have acted, GMAX has come out of the woods to act it, like, all
297
00:15:25.010 --> 00:15:29.130
of the graybeards in Bitcoin are for the PR being merged as a policy thing
298
00:15:29.130 --> 00:15:29.630
right now.
299
00:15:30.430 --> 00:15:30.610
Right?
300
00:15:31.230 --> 00:15:35.690
Well, but, you know, like, I really don't like this idea of just blindly
301
00:15:35.690 --> 00:15:38.990
trusting people too, because, like, you know, GMAX doesn't believe in harder
302
00:15:38.990 --> 00:15:39.450
wallets.
303
00:15:40.250 --> 00:15:45.270
You know, like, everybody in this space, you know, has massive blindsides,
304
00:15:45.450 --> 00:15:45.630
right?
305
00:15:46.130 --> 00:15:50.330
And, like, folks have been, you know, he's been busy in BSV forums trolling
306
00:15:50.330 --> 00:15:51.550
them for the last five years.
307
00:15:53.390 --> 00:15:54.970
That is a good retirement, though.
308
00:15:55.610 --> 00:15:59.510
If you tell me my retirement was I get to troll BSVers on Reddit, like, that's
309
00:15:59.510 --> 00:16:00.390
a pretty good gig.
310
00:16:00.730 --> 00:16:01.070
Sure.
311
00:16:03.450 --> 00:16:07.870
You know, like, again, like, I still think that the best course of action here
312
00:16:07.870 --> 00:16:09.630
is, like, just stop upgrading.
313
00:16:10.370 --> 00:16:10.850
That's it.
314
00:16:10.910 --> 00:16:12.030
It really is that simple.
315
00:16:12.030 --> 00:16:17.590
Like, you know, you can wait out a lot of this insanity, bullshit, by just not
316
00:16:17.590 --> 00:16:18.010
updating.
317
00:16:18.570 --> 00:16:21.390
You know, like, honestly, Matt, like, as much as I want to see CCTV, we're not
318
00:16:21.390 --> 00:16:21.890
going to see it.
319
00:16:22.230 --> 00:16:22.950
It's not going to happen.
320
00:16:23.430 --> 00:16:25.690
We're going to, like, we're essentially ossified.
321
00:16:26.490 --> 00:16:27.510
No, that's my point.
322
00:16:27.610 --> 00:16:31.370
I agree with you, but Rob doesn't, which I think there's a lot of people still
323
00:16:31.370 --> 00:16:32.330
in denial here.
324
00:16:33.030 --> 00:16:35.670
Those people can end up hard forking if they want to.
325
00:16:36.330 --> 00:16:37.610
It'd be a soft fork to start.
326
00:16:37.670 --> 00:16:38.570
It wouldn't be a hard fork.
327
00:16:38.850 --> 00:16:41.150
You don't have to do a hard fork to use up success.
328
00:16:41.150 --> 00:16:45.410
We designed TypeScript explicitly to not have to be hard forks to add new
329
00:16:45.410 --> 00:16:45.730
things.
330
00:16:46.650 --> 00:16:49.330
I need to see the implementation before we...
331
00:16:49.330 --> 00:16:53.430
Yeah, I mean, hard fork, soft fork, for those that are still awake, like, is a
332
00:16:53.430 --> 00:16:56.570
different distinction in a loosening versus a tightening of the consensus
333
00:16:56.570 --> 00:16:57.010
rules.
334
00:16:57.310 --> 00:16:57.510
Yes.
335
00:16:57.590 --> 00:17:02.490
And Taproot was explicitly designed around using what's called op success.
336
00:17:03.170 --> 00:17:05.829
So their op code's like, oh, if you see op success, you can just automatically
337
00:17:05.829 --> 00:17:06.589
spend it, right?
338
00:17:06.869 --> 00:17:10.130
And then of soft fork in the future, say, hey, instead of anyone can spend it,
339
00:17:10.130 --> 00:17:14.089
it's now this subset of behavior, whether it's CTV, Checksick from Stack,
340
00:17:14.190 --> 00:17:14.770
whatever it is.
341
00:17:14.990 --> 00:17:21.130
I think in the order of operations to actually have like a fork is you need
342
00:17:21.130 --> 00:17:22.130
to have an activation client.
343
00:17:22.310 --> 00:17:25.990
One step back from an activation client, you're going to want people who are
344
00:17:26.530 --> 00:17:29.550
showing that they're able to, with this proposed activation client, like using
345
00:17:29.550 --> 00:17:32.590
either Inquisition or Signet, like, hey, these are the things that we can do.
346
00:17:32.850 --> 00:17:34.510
I don't think that stuff is dead.
347
00:17:35.030 --> 00:17:39.750
I don't understand why it would be dead because people are upset about JPEGs.
348
00:17:39.750 --> 00:17:43.390
And if anything, then like, that's a really rough spot where you can get
349
00:17:43.390 --> 00:17:47.090
psyoped into making Bitcoin worse money because people are peeing in your men
350
00:17:47.090 --> 00:17:47.290
pool.
351
00:17:47.770 --> 00:17:50.230
Like that's, we're worried about nation state attacks and you literally can get
352
00:17:50.230 --> 00:17:52.770
trolled by people on the internet into just making Bitcoin worse money.
353
00:17:53.810 --> 00:17:53.910
Yeah.
354
00:17:54.550 --> 00:18:00.370
I think it's easy to look at this opportune thing and think of the way
355
00:18:00.370 --> 00:18:01.390
everything's going to go.
356
00:18:01.670 --> 00:18:07.570
But look, there were a highly motivated and very vocal opposition to this
357
00:18:07.570 --> 00:18:08.150
change.
358
00:18:08.150 --> 00:18:10.970
That's not always going to be the case for every SOC4.
359
00:18:11.430 --> 00:18:16.510
We know that there are certain changes, consensus changes that have to happen
360
00:18:16.510 --> 00:18:20.150
because of bugs that currently exist and will occur in the future.
361
00:18:20.650 --> 00:18:24.770
So, you know, we're going to have to get to that point at some point in
362
00:18:24.770 --> 00:18:25.150
the future.
363
00:18:25.350 --> 00:18:26.870
But there's only Unix timecode.
364
00:18:27.650 --> 00:18:29.010
Well, it still exists.
365
00:18:29.410 --> 00:18:29.730
Unix.
366
00:18:29.990 --> 00:18:34.750
The point is that, you know, I think it's, we shouldn't read too much into it.
367
00:18:35.170 --> 00:18:37.450
You know, spam is this very emotive issue.
368
00:18:37.450 --> 00:18:38.850
People hate
spam.
369
00:18:38.990 --> 00:18:40.630
They get all upset about it.
370
00:18:40.890 --> 00:18:42.490
It is one of those issues.
371
00:18:42.630 --> 00:18:47.690
I'm not saying that CTV doesn't have other things, but I don't actually know of
372
00:18:47.690 --> 00:18:50.490
any vocal groups right now who are opposed to it.
373
00:18:50.850 --> 00:18:52.470
There's more just a general...
374
00:18:52.470 --> 00:18:55.170
Core is opposed to CTV, pretty much.
375
00:18:55.690 --> 00:18:58.470
Well, I think that they're just not convinced.
376
00:18:58.650 --> 00:18:59.810
I wouldn't say they're opposed.
377
00:18:59.950 --> 00:19:00.970
They're just not convinced.
378
00:19:01.710 --> 00:19:02.970
Yeah, I don't think they're opposed.
379
00:19:03.090 --> 00:19:07.790
And there was actually some good discussion at OpNex around maybe CTV, you only
380
00:19:07.790 --> 00:19:08.630
put it in tap script.
381
00:19:08.730 --> 00:19:10.750
You can make it even simpler of an upgrade if you don't have to worry about
382
00:19:10.750 --> 00:19:11.610
legacy script anymore.
383
00:19:11.690 --> 00:19:12.750
Make it tap root only, right?
384
00:19:12.810 --> 00:19:15.490
People were kind of walking through and kind of iterating this out.
385
00:19:16.070 --> 00:19:20.210
And I think also from a coalition standpoint, the VM cohort realized that they
386
00:19:20.210 --> 00:19:23.850
can use CTV to cut down and make it a lot more efficient, right?
387
00:19:23.870 --> 00:19:25.890
So that was someone that was like, we don't need anything, or if anything,
388
00:19:25.990 --> 00:19:26.450
TxHash.
389
00:19:26.550 --> 00:19:30.530
Like, I think coalition building is a slow thing that develops over time.
390
00:19:30.990 --> 00:19:36.210
I think it's wrong to say looking at things today that it will never change
391
00:19:36.210 --> 00:19:36.490
again.
392
00:19:36.930 --> 00:19:39.250
That's a timeline and horizon that we can't be too sure.
393
00:19:39.630 --> 00:19:42.850
On the flip side, me to say definitely something's going to happen would be way
394
00:19:42.850 --> 00:19:44.770
too premature on the other side of it.
395
00:19:45.370 --> 00:19:45.750
I don't know.
396
00:19:46.270 --> 00:19:46.790
Like, we'll see.
397
00:19:46.870 --> 00:19:48.050
We'll see how Bitcoin continues to develop.
398
00:19:48.330 --> 00:19:52.010
I want Bitcoin to keep on improving, whether that's within current consensus
399
00:19:52.010 --> 00:19:55.390
rules or over time being thoughtful about adding new features like we've done
400
00:19:55.390 --> 00:19:55.730
before.
401
00:19:56.050 --> 00:19:58.350
But I don't think that history's set in stone yet.
402
00:19:59.130 --> 00:20:03.030
I guess we can all agree that we're all optimists on number go up, at least.
403
00:20:03.030 --> 00:20:05.890
That, yeah, no one's doubting that.
404
00:20:06.250 --> 00:20:06.650
There you go.
405
00:20:06.850 --> 00:20:13.730
I just, Rob, can you just walk through how, we've never seen a
contentious soft
406
00:20:13.730 --> 00:20:16.870
fork attempted to be pushed through on Bitcoin before.
407
00:20:17.630 --> 00:20:20.850
Have you, like Taproot was like easy breezy.
408
00:20:21.850 --> 00:20:26.930
Segwit was like, the people that were on this side of the hard fork were pretty
409
00:20:26.930 --> 00:20:28.290
agreed to it.
410
00:20:28.310 --> 00:20:30.790
Yeah, they were the soft fork for Segwit.
411
00:20:30.890 --> 00:20:31.750
We were the hard fork.
412
00:20:31.750 --> 00:20:38.650
Okay, so imagine a scenario where 50% of the hash rate, nice round number,
413
00:20:38.950 --> 00:20:43.830
decides to run an activation client for a soft fork that most people don't want
414
00:20:43.830 --> 00:20:45.970
and the network responds to that.
415
00:20:46.310 --> 00:20:47.150
How does that look?
416
00:20:47.230 --> 00:20:48.510
What happens in that situation?
417
00:20:49.030 --> 00:20:54.530
If you had 50% of the hash rate choose to activate something, you would have
418
00:20:54.530 --> 00:20:56.930
the other 50% not enforcing it.
419
00:20:57.150 --> 00:21:00.810
And so what would happen is the first block that used an upgrade, like walking
420
00:21:00.810 --> 00:21:04.130
through it, the first block where there was a behavior, where let's say I use
421
00:21:04.130 --> 00:21:04.990
CTV for something.
422
00:21:05.410 --> 00:21:08.970
Let's say I put 1,000 Bitcoin in the CTV address and I go and spend
423
00:21:08.970 --> 00:21:09.190
it.
424
00:21:09.610 --> 00:21:12.590
There would be a fork with 50% of the hash rate that would say, ah,
425
00:21:12.630 --> 00:21:14.990
that's CTV, so you can only spend it X, Y, and Z way.
426
00:21:15.370 --> 00:21:18.730
The other fork with the other 50% hash rate would be like, this fucking idiot,
427
00:21:18.910 --> 00:21:22.150
he just put his money in an anyone can spend address and they would just steal
428
00:21:22.150 --> 00:21:22.650
it, right?
429
00:21:22.690 --> 00:21:23.790
They would just instantly steal it.
430
00:21:24.230 --> 00:21:28.210
And then a new block would get found by the half that took the coins.
431
00:21:28.730 --> 00:21:31.810
And then the other nodes would reject that being like, ah, no, you violated the
432
00:21:31.810 --> 00:21:32.730
rule that we're enforcing.
433
00:21:33.130 --> 00:21:34.110
And then you would have a chain split.
434
00:21:35.270 --> 00:21:36.230
You'd have a hard fork.
435
00:21:36.950 --> 00:21:38.310
Well, it's not a hard fork, it's a chain split.
436
00:21:41.330 --> 00:21:44.570
Welcome to Bitcoin.review. Yeah, this is a chain split, not a hard fork.
437
00:21:44.910 --> 00:21:45.390
Yeah, sure.
438
00:21:45.530 --> 00:21:49.630
It's a, what is it, a transitory chain, arbitrary, whatever you want to call
439
00:21:49.630 --> 00:21:49.730
it.
440
00:21:49.730 --> 00:21:49.990
Anyways.
441
00:21:50.330 --> 00:21:52.850
I mean, if anyone's going to get pedantic about the definitions and technically
442
00:21:52.850 --> 00:21:58.170
actually, it's Bitcoin.review. If you want the higher level summary, you can go
443
00:21:58.170 --> 00:21:59.830
to other podcasts that kind of do list shows.
444
00:22:03.670 --> 00:22:04.390
Anyways.
445
00:22:05.190 --> 00:22:05.610
All right.
446
00:22:05.870 --> 00:22:07.290
Should we get on to software updates?
447
00:22:07.930 --> 00:22:09.490
We can take other tangents as we go.
448
00:22:10.390 --> 00:22:14.190
CodeCard, we released a small, lots of bug fixes today.
449
00:22:14.770 --> 00:22:19.470
Nothing too interesting, but bug fixes nonetheless.
450
00:22:20.750 --> 00:22:26.230
BDK version 0.22.0, improved syncing experience for Electrum and Explora.
451
00:22:26.790 --> 00:22:30.850
Relevant transactions that are missing can now be evicted with the help of
452
00:22:30.850 --> 00:22:34.350
Sync, Request Builder, and a few other things.
453
00:22:35.370 --> 00:22:41.370
Cove Wallet version 0.4.0, support for imported wallets with key expressions,
454
00:22:42.210 --> 00:22:46.110
add support for using Cove with Crux, create CSV file for transactions with
455
00:22:46.110 --> 00:22:50.270
fiat values for each transaction type of transaction, useful for tax reporting.
456
00:22:51.130 --> 00:22:52.370
So Cove is doing very well.
457
00:22:52.450 --> 00:22:54.050
It should be coming out of beta very soon.
458
00:22:54.470 --> 00:22:56.070
You know, I keep on banging on this project.
459
00:22:56.070 --> 00:22:58.910
Please go join the test flight.
460
00:22:59.430 --> 00:22:59.970
Give feedback.
461
00:23:00.650 --> 00:23:02.170
This project is awesome.
462
00:23:02.410 --> 00:23:08.130
It's the simple but real, like phone wallet that we needed.
463
00:23:08.910 --> 00:23:12.730
Steve Myers did a really great demo last night at Nash BitDev showing the tap
464
00:23:12.730 --> 00:23:13.410
signer integration.
465
00:23:13.650 --> 00:23:14.450
It was a huge hit.
466
00:23:14.730 --> 00:23:17.090
It's a clean UX, works really nicely.
467
00:23:17.430 --> 00:23:21.070
And the Cove Wallet, like I think you described it before this way, MBK is this
468
00:23:21.070 --> 00:23:25.530
like your basic layer one, just like boomer on-chain Bitcoin wallet.
469
00:23:25.530 --> 00:23:26.750
And it's clean, minimal.
470
00:23:26.870 --> 00:23:27.250
That's good.
471
00:23:27.770 --> 00:23:29.910
Yeah, it's the phone wallet we can send people to.
472
00:23:30.310 --> 00:23:33.990
It's seed-based and it doesn't have lightning sort of complexities on it.
473
00:23:34.270 --> 00:23:35.770
I think it's much needed.
474
00:23:36.310 --> 00:23:37.750
It's Sparrow Wallet for mobile.
475
00:23:38.310 --> 00:23:38.790
There you go.
476
00:23:40.030 --> 00:23:41.570
No, no, it doesn't have all the tools.
477
00:23:41.670 --> 00:23:42.350
That's the whole point.
478
00:23:42.870 --> 00:23:43.110
Yeah.
479
00:23:43.490 --> 00:23:44.830
Can you do coin control on that?
480
00:23:44.970 --> 00:23:45.130
Yeah.
481
00:23:45.490 --> 00:23:45.790
Yes.
482
00:23:46.210 --> 00:23:46.530
Oh, you can?
483
00:23:46.650 --> 00:23:47.110
Oh, there you go.
484
00:23:47.350 --> 00:23:50.690
I don't know if it's out or coming, but kind of, yes, soon.
485
00:23:51.010 --> 00:23:51.230
Okay.
486
00:23:51.890 --> 00:23:58.490
Yeah, I mean, you can't put a desktop screen on a phone, but, you know, it
487
00:23:58.490 --> 00:23:59.850
just can't be done.
488
00:24:00.310 --> 00:24:00.870
Not yet anyway.
489
00:24:01.830 --> 00:24:02.050
Yeah.
490
00:24:02.810 --> 00:24:03.410
What else?
491
00:24:03.570 --> 00:24:05.130
BTC Pay Server updated.
492
00:24:06.210 --> 00:24:11.290
Nunchuck version 1.68 updated for Android.
493
00:24:12.050 --> 00:24:13.070
Bitcoin Keeper updated.
494
00:24:14.130 --> 00:24:15.430
Bitcoin Safe updated.
495
00:24:16.130 --> 00:24:18.950
Let's see if there is anything super big deal here.
496
00:24:19.090 --> 00:24:27.410
Wasabi Wallet version 2.6.0. They added 1.58 block filters and now synchronize
497
00:24:27.410 --> 00:24:30.410
with BIT 1.58 without requiring a backend indexer.
498
00:24:30.490 --> 00:24:31.050
That's nice.
499
00:24:31.730 --> 00:24:36.870
So they actually always used BIT 1.58 filters, so I wasn't aware of the need
500
00:24:36.870 --> 00:24:38.090
for an indexer before.
501
00:24:38.750 --> 00:24:43.730
I think they are the only wallets that uses BIT 1.58, like actual wallet, like
502
00:24:43.730 --> 00:24:47.110
as opposed to a lightning node like LND or whatever.
503
00:24:47.390 --> 00:24:51.330
But I'm probably wrong, but maybe someone else knows of a different one.
504
00:24:51.730 --> 00:24:52.050
I don't know.
505
00:24:52.090 --> 00:24:53.530
I think they were bundling something before.
506
00:24:53.710 --> 00:24:54.690
Zeus uses it.
507
00:24:55.270 --> 00:24:55.590
Okay.
508
00:24:55.990 --> 00:24:56.370
Nice.
509
00:24:56.590 --> 00:24:57.390
Yeah, that's right.
510
00:24:57.450 --> 00:25:00.970
I actually listened to your pod with...
511
00:25:00.970 --> 00:25:01.470
Evan.
512
00:25:02.050 --> 00:25:02.890
Evan, thank you.
513
00:25:03.310 --> 00:25:07.790
And he said that there was some performance issues, which I understand because
514
00:25:07.790 --> 00:25:12.090
it is quite a heavy protocol to try and sync with.
515
00:25:12.390 --> 00:25:16.430
I mean, it's great from a privacy point of view, definitely well thought out
516
00:25:16.430 --> 00:25:22.030
there, but has challenges and that's always an issue for the user experience
517
00:25:22.030 --> 00:25:25.710
because everyone just expects everything to happen instantly.
518
00:25:26.130 --> 00:25:30.030
And if you don't think that's true, then try and sit down with somebody and
519
00:25:30.030 --> 00:25:35.130
introduce them to Bitcoin with a wallet that uses BIT 1.58 filters.
520
00:25:35.430 --> 00:25:37.110
It's a very different experience.
521
00:25:38.070 --> 00:25:38.270
Yeah.
522
00:25:39.450 --> 00:25:42.810
Again, if only Core could have an indexer.
523
00:25:43.810 --> 00:25:46.650
RoboSats version 0.77 updated.
524
00:25:47.090 --> 00:25:52.990
Umbro version 1.4.1. File search.
525
00:25:53.950 --> 00:25:54.390
UI.
526
00:25:55.050 --> 00:25:56.090
Anything here?
527
00:25:56.350 --> 00:25:56.730
Interesting.
528
00:25:57.910 --> 00:26:02.490
Zapwrite added Taproot support and payment profiles.
529
00:26:03.270 --> 00:26:04.190
Orders export.
530
00:26:05.310 --> 00:26:07.790
Add CSV support for feature orders.
531
00:26:08.390 --> 00:26:09.950
Unchain SegWit Vaults.
532
00:26:09.950 --> 00:26:13.410
Add support for Unchain's new SegWit Vaults.
533
00:26:13.410 --> 00:26:16.150
Wait, Unchain now supports SegWit?
534
00:26:16.670 --> 00:26:17.830
Or is that...
535
00:26:17.830 --> 00:26:18.210
I don't know.
536
00:26:18.950 --> 00:26:20.770
Unchain's new SegWit Vaults.
537
00:26:20.930 --> 00:26:21.190
Yeah.
538
00:26:22.230 --> 00:26:27.230
Blockstream Satellite version 2.5.1. It's nice that Starlink has a little
539
00:26:27.230 --> 00:26:30.070
competition still on running nodes remotely.
540
00:26:30.950 --> 00:26:37.090
Installation of GRDVBS2RX on Debian Bookworm.
541
00:26:37.090 --> 00:26:40.490
User addition to video group configuration.
542
00:26:40.690 --> 00:26:42.070
TBS USB receiver.
543
00:26:43.110 --> 00:26:44.910
And they changed a few other things.
544
00:26:46.130 --> 00:26:46.850
Stratum work.
545
00:26:47.470 --> 00:26:53.150
Add page that displays full block template data as parsed from mining.autify
546
00:26:53.150 --> 00:26:54.930
message for each pool.
547
00:26:55.810 --> 00:26:57.630
And a few other changes.
548
00:26:58.950 --> 00:26:59.470
SeedHammer.
549
00:26:59.750 --> 00:27:03.830
Open source hardware design files for SeedHammer 2 machine released.
550
00:27:03.830 --> 00:27:07.270
Oh, they integrated NFC.
551
00:27:07.750 --> 00:27:08.310
It's pretty cool.
552
00:27:08.770 --> 00:27:10.150
It's going to come out soon.
553
00:27:11.230 --> 00:27:19.830
ESPminer version 2.7.0. Improve AP mode stability for stopping a bunch of
554
00:27:19.830 --> 00:27:20.310
updates.
555
00:27:20.590 --> 00:27:22.170
That's the Lodo mining.
556
00:27:23.350 --> 00:27:26.350
Man, people are too busy arguing, not shipping enough.
557
00:27:27.190 --> 00:27:29.130
This list is too short here for Bitcoin.
558
00:27:30.290 --> 00:27:31.810
It's all a sign up.
559
00:27:32.950 --> 00:27:33.950
Project Spotlight.
560
00:27:34.050 --> 00:27:35.410
Bitcoin feature matrix.
561
00:27:35.810 --> 00:27:39.850
A tool to track interoperability of Bitcoin products and services.
562
00:27:40.610 --> 00:27:41.150
Oh, look at that.
563
00:27:41.790 --> 00:27:44.090
Another Secp256k1Lab.
564
00:27:44.510 --> 00:27:46.010
Another implementation.
565
00:27:46.210 --> 00:27:49.930
An insecure implementation related to blah, blah, blah, blah, blah.
566
00:27:50.050 --> 00:27:51.050
Written in Python.
567
00:27:51.610 --> 00:27:54.010
Intended for prototyping experimentation education.
568
00:27:54.630 -->
00:27:54.990
That's cool.
569
00:27:55.610 --> 00:27:58.490
Wouldn't use it for real money, but just to like click around and do some
570
00:27:58.490 --> 00:27:58.750
stuff.
571
00:27:58.830 --> 00:27:59.150
Why not?
572
00:28:01.930 --> 00:28:03.250
GPG, GPGAP.
573
00:28:03.830 --> 00:28:06.410
AirGap GPG signing Bitcoin style.
574
00:28:06.930 --> 00:28:07.150
Oh, yeah.
575
00:28:07.210 --> 00:28:11.410
So you can now do GPG signing on Crooks, which is really cool.
576
00:28:11.750 --> 00:28:12.230
Very cool.
577
00:28:12.490 --> 00:28:12.650
Yeah.
578
00:28:12.810 --> 00:28:14.050
Awesome use for that.
579
00:28:15.370 --> 00:28:16.430
Who is this, Johnny?
580
00:28:16.870 --> 00:28:18.830
NVK validation tweet.
581
00:28:18.990 --> 00:28:24.410
A cooked demo response for a Bitcoin Rust script for testing data on Signet.
582
00:28:25.190 --> 00:28:26.530
I heard about this.
583
00:28:26.530 --> 00:28:26.970
Yeah.
584
00:28:27.070 --> 00:28:28.870
Portland Hoddle, you're asking him to.
585
00:28:29.510 --> 00:28:29.710
Yeah.
586
00:28:29.910 --> 00:28:34.230
Basically, you threw out a challenge to make some mock data, and then he said
587
00:28:34.230 --> 00:28:35.310
you could just use BDK for this.
588
00:28:35.970 --> 00:28:41.730
I also vibe coded a transaction generator that creates like multi-chained
589
00:28:41.730 --> 00:28:43.530
transactions and consolidations.
590
00:28:43.730 --> 00:28:44.130
Yeah.
591
00:28:44.330 --> 00:28:45.830
I posted, I think, on my GitHub.
592
00:28:46.770 --> 00:28:50.490
Untested, of course, because, you know, vibe coding is great for doing the
593
00:28:50.490 --> 00:28:51.750
code, not testing the code.
594
00:28:54.610 --> 00:28:59.250
BriberBrother, an alternative mempool to help Bitcoin miners identify and
595
00:28:59.250 --> 00:29:02.930
include non-standard transactions that follow consensus rules, but aren't
596
00:29:02.930 --> 00:29:06.230
typically relayed through the P2P network.
597
00:29:07.250 --> 00:29:07.510
Interesting.
598
00:29:09.050 --> 00:29:10.330
I'm looking at it.
599
00:29:11.150 --> 00:29:13.870
StockMath, the Bitcoin modeling engine.
600
00:29:14.970 --> 00:29:19.790
NomadBuild, self-sovereign Bitcoin axe firmware builder and flash shares.
601
00:29:19.790 --> 00:29:23.290
Man, the BitAxe shit show has been interesting.
602
00:29:24.050 --> 00:29:27.410
So apparently when you buy hardware from them, don't, please, guys, don't get
603
00:29:27.410 --> 00:29:28.710
mad at me if I get this wrong.
604
00:29:28.810 --> 00:29:29.070
Okay.
605
00:29:29.370 --> 00:29:30.270
The two people listening.
606
00:29:31.590 --> 00:29:37.670
So as I understand, when you buy hardware from them, you pay a mandatory
607
00:29:37.670 --> 00:29:43.510
donation to Osmo, which is their like open source little foundation or
608
00:29:43.510 --> 00:29:43.910
something.
609
00:29:44.510 --> 00:29:49.030
It's a mandatory donation, which is, you know, guys.
610
00:29:49.790 --> 00:29:53.990
If you really
want to generate hate, have a mandatory donation.
611
00:29:54.590 --> 00:29:57.170
Just embed it on the cost of the product.
612
00:29:57.710 --> 00:30:02.210
You know, like it's, oh, what a shit show.
613
00:30:03.250 --> 00:30:06.210
Making false hardware, man, is tricky.
614
00:30:06.790 --> 00:30:09.230
And everybody eventually finds that out.
615
00:30:11.690 --> 00:30:15.430
HashCommand, an Electrum application for controlling Bitcoin miners, local
616
00:30:15.430 --> 00:30:18.070
network, mainly BitAxe, USB miner devices.
617
00:30:19.670 --> 00:30:19.970
All right.
618
00:30:20.790 --> 00:30:22.210
Vulnerability disclosures.
619
00:30:23.270 --> 00:30:31.350
So CVE 2024-52919 remote crash due to address message spam part disclosure.
620
00:30:32.370 --> 00:30:33.650
This is on Bitcoin Core.
621
00:30:34.170 --> 00:30:35.290
Version 22.
622
00:30:35.910 --> 00:30:36.310
Yeah.
623
00:30:36.990 --> 00:30:38.290
Which you can still run.
624
00:30:38.510 --> 00:30:38.810
Okay.
625
00:30:39.230 --> 00:30:44.590
Like all the Bitcoin attacks, like a Bitcoin Core CVEs and things that people
626
00:30:44.590 --> 00:30:48.530
keep on like crying about and thinking it's like the end of the world, they're
627
00:30:48.530 --> 00:30:50.510
all just things that can just crash your node.
628
00:30:52.130 --> 00:30:52.650
That's it.
629
00:30:52.850 --> 00:30:57.010
I would say probably if you are an individual, deep cold storage, you have your
630
00:30:57.010 --> 00:31:01.230
node to like have your copy of the blockchain if you need to spend, less of
631
00:31:01.230 --> 00:31:01.710
a concern.
632
00:31:02.070 --> 00:31:04.870
If you're a business, you don't want to have your node go offline.
633
00:31:05.930 --> 00:31:07.530
Maybe more problems there.
634
00:31:07.810 --> 00:31:07.930
Right.
635
00:31:08.050 --> 00:31:10.330
And that kind of like if your node needs to be on all the time because
636
00:31:10.330 --> 00:31:11.950
you're serving customers blockchain data.
637
00:31:11.950 --> 00:31:16.510
We don't fully buy that because I have a bunch of old nodes running out there
638
00:31:16.510 --> 00:31:17.930
and nobody has taken them down.
639
00:31:18.970 --> 00:31:23.430
So it's great that people find these vulnerabilities and we fixed it.
640
00:31:24.090 --> 00:31:28.250
I mean, you definitely do agree with Rob that there are certain situations in
641
00:31:28.250 --> 00:31:32.050
business operations where you don't want the chance of your node going down.
642
00:31:32.190 --> 00:31:32.790
Oh, absolutely.
643
00:31:33.030 --> 00:31:34.210
But here's the thing, right?
644
00:31:34.810 --> 00:31:40.070
You know, when you have like mission critical infrastructure updating that
645
00:31:40.070 --> 00:31:42.870
mission critical infrastructure introduces new unknowns.
646
00:31:43.530 --> 00:31:46.010
And, you know, normally if it's working, don't mess with it.
647
00:31:46.070 --> 00:31:48.390
It goes a long way in business infrastructure.
648
00:31:49.150 --> 00:31:51.710
So updating business infrastructure is not that simple.
649
00:31:52.030 --> 00:31:55.050
And updating nodes for miners is also not that simple.
650
00:31:55.610 --> 00:31:57.190
So it's tricky.
651
00:31:58.050 --> 00:31:59.910
So guys, there's a challenge out there.
652
00:32:00.090 --> 00:32:02.730
Find NVK's nodes and take them down.
653
00:32:04.290 --> 00:32:05.250
Thanks, Craig.
654
00:32:06.010 --> 00:32:07.950
I wasn't going to say it, but I was thinking it.
655
00:32:07.950 --> 00:32:10.930
But no one's awake at this point of the show anyway.
656
00:32:11.150 --> 00:32:12.050
Nobody listens to the show.
657
00:32:13.110 --> 00:32:16.510
No, but I mean, you know, I think that there is a lot of truth to
658
00:32:16.510 --> 00:32:23.430
the fact that the majority of people are safe so long as there are some people
659
00:32:23.430 --> 00:32:24.270
who upgrade.
660
00:32:24.690 --> 00:32:24.870
Yes.
661
00:32:25.130 --> 00:32:29.810
There's just this kind of, because it makes the sort of, is it worthwhile for
662
00:32:29.810 --> 00:32:31.590
me to develop an attack around this?
663
00:32:31.730 --> 00:32:38.390
So much less interesting if you know that, you know, not only can the attack be
664
00:32:38.390 --> 00:32:43.670
mitigated with a simple upgrade, but chances are the person that you're going
665
00:32:43.670 --> 00:32:45.150
to attack has upgraded anyway.
666
00:32:45.670 --> 00:32:47.970
You know, it just, it kind of just like, oh, well, I might as well not
667
00:32:47.970 --> 00:32:48.430
even bother.
668
00:32:48.650 --> 00:32:51.510
So I think we all benefit even if we don't upgrade.
669
00:32:52.370 --> 00:32:52.590
Yep.
670
00:32:52.890 --> 00:32:55.290
It is a version of herd immunity.
671
00:32:57.230 --> 00:32:58.950
It's just to make a little bit more contentious.
672
00:33:02.910 --> 00:33:07.790
CD-2025-43707, critical bug in Rust.
673
00:33:08.070 --> 00:33:11.330
Miniscript library causes transaction signing crashes.
674
00:33:11.930 --> 00:33:12.410
Yep.
675
00:33:12.650 --> 00:33:17.470
So this was an interesting corner case with some uses of descriptors.
676
00:33:17.570 --> 00:33:19.410
The wizard sardine guys stumbled across.
677
00:33:19.910 --> 00:33:22.770
There's a blog post in the show notes for those out there who want to go
678
00:33:22.770 --> 00:33:23.110
read it.
679
00:33:23.190 --> 00:33:30.210
In short, if you set a threshold condition, which means you're doing something
680
00:33:30.210 --> 00:33:33.390
more than just only keys because that uses the multi-argument for like multi
681
00:33:33.390 --> 00:33:37.710
-sig, but the threshold argument anyway with threshold, if you said three
682
00:33:37.710 --> 00:33:41.450
conditions and it was a three of three conditions, it would cause on some
683
00:33:41.450 --> 00:33:43.170
corner cases for the compiler to crash.
684
00:33:43.390 --> 00:33:47.070
Wasn't really a money losing bug in the sense that once this is patched,
if you
685
00:33:47.070 --> 00:33:49.650
make money there and set it all up, it wouldn't be an issue.
686
00:33:49.750 --> 00:33:52.270
It didn't impact us at AnchorWatch at all.
687
00:33:52.510 --> 00:33:54.950
And that didn't impact the wizard sardine guys either because they were just
688
00:33:54.950 --> 00:33:56.410
trying to test and work on new things.
689
00:33:56.810 --> 00:33:58.590
But yeah, it's always good just to...
690
00:33:58.590 --> 00:34:03.270
On that note, like we really need more testing on MiniScript.
691
00:34:03.570 --> 00:34:04.090
Yeah.
692
00:34:04.470 --> 00:34:06.350
This is actually the compiler too.
693
00:34:06.470 --> 00:34:07.909
This wasn't even like the signing stuff.
694
00:34:07.969 --> 00:34:10.190
This is just like making of the descriptor.
695
00:34:10.290 --> 00:34:13.070
So it's all upstream from wallet software and core.
696
00:34:13.469 --> 00:34:17.750
The MiniScript compiler is basically what takes your high level semantic policy
697
00:34:17.750 --> 00:34:21.230
language of conceptually what you want to secure your money with and puts it
698
00:34:21.230 --> 00:34:24.810
into Bitcoin script with an output descriptor and like the actual encoding of
699
00:34:24.810 --> 00:34:27.449
the vault and all the PSPTs and all that information.
700
00:34:28.070 --> 00:34:31.270
That in between translation is where this got pinched.
701
00:34:32.270 --> 00:34:34.730
And so you want to be doing more testing.
702
00:34:34.909 --> 00:34:35.230
Absolutely.
703
00:34:35.750 --> 00:34:39.389
We do a lot of strict sanity checking and very strong opinions on the stuff
704
00:34:39.389 --> 00:34:40.590
that we're using in production.
705
00:34:40.770 --> 00:34:42.650
We put a lot of testing and effort and work into it.
706
00:34:42.969 --> 00:34:43.110
Yeah.
707
00:34:43.170 --> 00:34:45.170
So more testing, always welcome.
708
00:34:46.469 --> 00:34:51.389
Hackers breach lock bit, ransomware gang, dark web affiliate panels.
709
00:34:52.389 --> 00:34:55.469
I feel like I'm reading like an AI summary of something here.
710
00:34:55.469 --> 00:35:01.590
Exposing nearly 60,000 Bitcoin wallet addresses and 4,400 negotiated messages
711
00:35:01.590 --> 00:35:03.070
between attackers and victims.
712
00:35:03.730 --> 00:35:04.350
Okay.
713
00:35:04.930 --> 00:35:05.530
All right.
714
00:35:06.290 --> 00:35:07.410
All these questions.
715
00:35:08.370 --> 00:35:11.070
It's all Johnny here asking up return shit.
716
00:35:11.150 --> 00:35:11.750
I'm pretty sure.
717
00:35:12.950 --> 00:35:15.590
What's the difference between testnet and signet?
718
00:35:15.810 --> 00:35:17.690
And what are the benefits of each?
719
00:35:18.070 --> 00:35:18.350
Okay.
720
00:35:18.410 --> 00:35:19.110
Well, that's a good one.
721
00:35:19.670 --> 00:35:20.530
Rob, do you want to take it?
722
00:35:22.130 --> 00:35:28.150
So testnet and its forms of testnet three and testnet four, they are basically
723
00:35:28.150 --> 00:35:30.910
almost identical to the main Bitcoin network.
724
00:35:31.210 --> 00:35:34.410
And this is most impactful for mining.
725
00:35:34.870 --> 00:35:39.110
So on testnet three and four, you actually can point your ASICs or your bid
726
00:35:39.110 --> 00:35:43.390
axes or whatever, and you can point your hash there and it allows you, it's of
727
00:35:43.390 --> 00:35:46.450
most use to miners because it allows them to know, hey, if I plug in my
728
00:35:46.450 --> 00:35:49.570
hash rate, like it's my pool configure correctly, allows you to make sure maybe
729
00:35:49.570 --> 00:35:53.090
if you're making, if you're like hypothetically marathoning, you wanted to make
730
00:35:53.090 --> 00:35:56.590
some nonstandard blocks and you want to be like, hey, does my code allow
731
00:35:56.590 --> 00:35:58.530
garbage in that forks the network?
732
00:35:58.710 --> 00:36:02.210
Like you can do it in a sandbox environment with a much lower hash rate to
733
00:36:02.210 --> 00:36:02.830
test things out.
734
00:36:03.650 --> 00:36:07.950
Signet, SIG means for signature is instead of there being proof of work mining,
735
00:36:08.590 --> 00:36:13.870
there is a team of developers who at a Poisson distribution of like how often
736
00:36:13.870 --> 00:36:18.850
blocks get found, will sign a message and that signature acts as a valid proof
737
00:36:18.850 --> 00:36:21.050
of work block and to make more coins.
738
00:36:21.310 --> 00:36:25.690
And so in that sense, testnets more egalitarian in that like it's a, anyone can
739
00:36:25.690 --> 00:36:27.070
bind there and do whatever the heck they want.
740
00:36:27.470 --> 00:36:33.350
And signet is, you know, more controlled for making sure that they are able to
741
00:36:33.350 --> 00:36:34.690
like actually see things, right.
742
00:36:34.710 --> 00:36:37.130
They're able to make sure that my transaction is going to get confirmed in a
743
00:36:37.130 --> 00:36:37.730
regular manner.
744
00:36:37.930 --> 00:36:40.710
You're not going to be able to mine the block yourself, but it's signet is
745
00:36:40.710 --> 00:36:41.590
definitely the go-to place.
746
00:36:41.590 --> 00:36:45.530
If you're testing any reliable application and there's forks of this too, like
747
00:36:45.530 --> 00:36:48.450
mutiny net, which does blocks every 30 seconds, you can fork and make your own
748
00:36:48.450 --> 00:36:50.110
signet if you want to do your own things.
749
00:36:50.790 --> 00:36:54.710
Also testnets, since it is adversarial and anyone can mine, people love to be
750
00:36:54.710 --> 00:36:56.430
dicks all the time and like reorg the chain.
751
00:36:56.850 --> 00:36:57.410
And you know why?
752
00:36:57.630 --> 00:37:00.190
Because they can, you really don't need a better reason than that.
753
00:37:00.270 --> 00:37:03.330
People with, you know, a couple hundred bucks and, you know, hash power and
754
00:37:03.330 --> 00:37:06.590
just kind of dicking around and reorging blocks, which is actually kind of nice
755
00:37:06.590 --> 00:37:09.030
for testing the Bitcoin consensus code and what reorgs look like, right.
756
00:37:09.070 --> 00:37:10.650
You have, it happens all the time on testnet.
757
00:37:11.210 --> 00:37:13.450
So, um, yeah, that's a high level summary between the two.
758
00:37:14.610 --> 00:37:14.950
Thank you, Rob.
759
00:37:15.230 --> 00:37:20.290
Can you explain a simple terms that op check contract verified does?
760
00:37:21.250 --> 00:37:22.450
Is this also for me?
761
00:37:23.510 --> 00:37:24.690
It's up to you.
762
00:37:25.270 --> 00:37:28.890
From what I understand of check contract verify, I haven't done much direct
763
00:37:28.890 --> 00:37:29.270
look into it.
764
00:37:29.330 --> 00:37:30.990
I think the BIP just got merged.
765
00:37:31.290 --> 00:37:32.770
Yeah, I don't know.
766
00:37:33.250 --> 00:37:33.850
It's brand new.
767
00:37:33.890 --> 00:37:38.330
So Salvatore over at ledgers built this out and it's basically a high level
768
00:37:38.330 --> 00:37:43.090
concept where you can commit to doing more advanced contracts.
769
00:37:43.230 --> 00:37:47.470
If we get something like an op vault, it's probably more likely to be a CTV
770
00:37:47.470 --> 00:37:50.250
plus check contract verify than an op fault.
771
00:37:50.710 --> 00:37:53.770
That's just like, we're because op vault is very narrowly focused on the
772
00:37:53.770 --> 00:37:54.450
vaulting of the coins.
773
00:37:54.550 --> 00:37:56.810
Whereas check contract verify does that and many other things.
774
00:37:56.910 --> 00:38:02.010
So it's a more general purpose application for enforcing coins, like, uh, only
775
00:38:02.010 --> 00:38:06.390
spend coins at this transaction has this kind of output, you know, basically
776
00:38:06.390 --> 00:38:09.550
allowing more general frameworks for how money gets moved around.
777
00:38:09.810 --> 00:38:12.170
I can't, I don't want to give you a more detailed example of that because I
778
00:38:12.170 --> 00:38:16.890
haven't done the research myself, but it's a more generalizing contract system,
779
00:38:17.010 --> 00:38:20.970
recurring payments, multiple step enforcement to move money around all that
780
00:38:20.970 --> 00:38:21.410
kind of stuff.
781
00:38:22.470 --> 00:38:22.570
Yeah.
782
00:38:22.610 --> 00:38:23.430
I've been out of the loop.
783
00:38:23.850 --> 00:38:28.310
Once the discussions got more interesting on the mailing list, I turned off the
784
00:38:28.310 --> 00:38:28.890
mailing list.
785
00:38:31.750 --> 00:38:35.910
I normally just check out when those things start to happen.
786
00:38:35.910 --> 00:38:39.550
I think we're years and years away from that being a more fleshed out.
787
00:38:40.110 --> 00:38:40.250
Yeah.
788
00:38:41.170 --> 00:38:41.470
Okay.
789
00:38:41.530 --> 00:38:43.510
The last question I already talked in the beginning.
790
00:38:43.810 --> 00:38:43.910
Yeah.
791
00:38:44.070 --> 00:38:49.950
I mean, still, it's interesting to see how, you know, over time these
proposals
792
00:38:49.950 --> 00:38:50.610
get better.
793
00:38:50.790 --> 00:38:57.170
I mean, the, uh, guy who proposed op vault is now saying that op CCV is
794
00:38:57.170 --> 00:38:59.450
better is, is a better replacement.
795
00:38:59.630 --> 00:39:00.490
That's James O'Byrne.
796
00:39:00.770 --> 00:39:01.090
Yeah.
797
00:39:01.530 --> 00:39:01.770
Yeah.
798
00:39:01.770 --> 00:39:06.330
So, you know, isn't that an interesting indication of how taking your time over
799
00:39:06.330 --> 00:39:10.090
these, these things is actually potentially beneficial.
800
00:39:10.290 --> 00:39:11.190
There's a lot of markets.
801
00:39:12.170 --> 00:39:14.870
And CTV has been there for five years and no one's come up with something
802
00:39:14.870 --> 00:39:15.390
better yet.
803
00:39:15.590 --> 00:39:19.270
So it's every day that CTV hangs around and no one's come up with a better
804
00:39:19.270 --> 00:39:20.070
way of going about.
805
00:39:20.070 --> 00:39:22.090
This is a adding to the Lindy effect.
806
00:39:22.270 --> 00:39:23.750
And there's a five Bitcoin bug bounty.
807
00:39:23.930 --> 00:39:26.890
If someone finds a bug in CTV, that's been sitting there for years.
808
00:39:26.990 --> 00:39:28.030
No one's found a break in it yet.
809
00:39:28.150 --> 00:39:31.990
I'd agree though, Craig, that lighting the stuff, sit down, marinate, have time
810
00:39:31.990 --> 00:39:36.410
does a lot for speaking to the strength of, you know, battle testing things and
811
00:39:36.410 --> 00:39:38.790
seeing if people can revisit primitives and do it even better.
812
00:39:39.790 --> 00:39:40.010
Yeah.
813
00:39:40.330 --> 00:39:42.310
Well, I mean, at least we can change VIPs now.
814
00:39:42.890 --> 00:39:43.230
That's right.
815
00:39:43.630 --> 00:39:43.790
Yeah.
816
00:39:48.750 --> 00:39:49.550
All right.
817
00:39:49.730 --> 00:39:50.810
Uh, other software.
818
00:39:51.550 --> 00:39:52.410
Let's see here.
819
00:39:53.410 --> 00:39:54.170
Anything here.
820
00:39:54.190 --> 00:39:55.410
You guys want to talk about.
821
00:39:56.470 --> 00:39:57.490
Simple X updates.
822
00:39:57.850 --> 00:39:59.130
I haven't checked that simple X yet.
823
00:39:59.130 --> 00:39:59.530
I've heard good things.
824
00:39:59.530 --> 00:40:04.170
I mean, really all I wanted to do is really talk to Craig about the features
825
00:40:04.170 --> 00:40:05.190
I've requested.
826
00:40:05.510 --> 00:40:07.490
And is this Sparrow dot review now?
827
00:40:08.050 --> 00:40:08.830
Yeah, exactly.
828
00:40:08.970 --> 00:40:11.090
And how does he feel about some of my requests?
829
00:40:11.950 --> 00:40:12.650
Go ahead.
830
00:40:12.990 --> 00:40:13.850
Go, go ahead.
831
00:40:13.990 --> 00:40:14.370
Let's talk.
832
00:40:15.110 --> 00:40:19.650
I mean, like, no, I mean, it was like some simple stuff, like, uh, adding a
833
00:40:19.650 --> 00:40:25.250
total of Bitcoin on the send to multi output, because we don't have a total
834
00:40:25.250 --> 00:40:25.610
there.
835
00:40:26.290 --> 00:40:29.490
So let's see how many, how many acts I get on the, on this panel.
836
00:40:29.970 --> 00:40:31.470
Odell is shaking his back.
837
00:40:32.970 --> 00:40:33.070
Back.
838
00:40:33.650 --> 00:40:34.510
Good to hear.
839
00:40:35.250 --> 00:40:37.410
That'd be really helpful for open sets.
840
00:40:37.930 --> 00:40:38.210
Yes.
841
00:40:38.810 --> 00:40:44.930
Another one is the thing that you wanted to wait for court to ever do, which
842
00:40:44.930 --> 00:40:50.030
is the, I wanted to map out so you can, you can own essentially like when
843
00:40:50.030 --> 00:40:56.170
you migrate from one wallet to another, I want to migrate UTXO mapping so that
844
00:40:56.170 --> 00:40:59.430
you don't make a, a send everything to a new TXO.
845
00:40:59.690 --> 00:41:03.530
Like you create just like, it just imitates the same mapping and transfers
846
00:41:03.530 --> 00:41:03.810
them.
847
00:41:04.570 --> 00:41:07.990
It doesn't, the timing of the transaction needs to be okay, but it doesn't have
848
00:41:07.990 --> 00:41:08.810
to be anything crazy.
849
00:41:08.950 --> 00:41:12.490
It could just say, Hey, you know, randomly pick times within a week.
850
00:41:12.790 --> 00:41:13.890
And it's like, fuck it.
851
00:41:14.010 --> 00:41:14.490
Good enough.
852
00:41:15.230 --> 00:41:15.730
Timing analysis.
853
00:41:16.070 --> 00:41:20.870
And I just keep running because, you know, core is not going to do this server
854
00:41:20.870 --> 00:41:23.010
side for at least another 50 years.
855
00:41:23.330 --> 00:41:23.450
Yeah.
856
00:41:23.790 --> 00:41:24.150
I know.
857
00:41:24.290 --> 00:41:24.590
I know.
858
00:41:24.590 --> 00:41:26.750
But, but yeah, agreed.
859
00:41:26.870 --> 00:41:29.630
It's definitely something I want to do for sure.
860
00:41:30.310 --> 00:41:30.570
All right.
861
00:41:30.650 --> 00:41:33.950
And my latest, my latest feature request was a key teleport.
862
00:41:34.490 --> 00:41:39.430
I bumped into this issue twice already since I added the feature, I was helping
863
00:41:39.430 --> 00:41:44.030
somebody recover their funds and they needed a way to send me their private
864
00:41:44.030 --> 00:41:44.250
key.
865
00:41:44.790 --> 00:41:48.510
So be really nice to just receive that straight into Sparrow.
866
00:41:48.730 --> 00:41:52.610
So I don't have like never clear text with me because it was remote thing.
867
00:41:52.610 --> 00:41:56.770
And so I had to explain how to set up PGP on a fucking clean machine.
868
00:41:57.050 --> 00:41:57.910
It was fucking disaster.
869
00:41:59.470 --> 00:42:00.270
Sounds painful.
870
00:42:00.970 --> 00:42:03.170
Oh, it was very painful because they were, yeah.
871
00:42:03.390 --> 00:42:03.790
Anyways.
872
00:42:04.490 --> 00:42:06.710
So, yeah, so that was, that was the other one.
873
00:42:06.770 --> 00:42:07.450
I think that's it.
874
00:42:07.530 --> 00:42:09.450
Like you've included a lot of my requests.
875
00:42:09.730 --> 00:42:10.690
So very helpful.
876
00:42:11.590 --> 00:42:13.630
Did you get, look into the bug that I found?
877
00:42:13.710 --> 00:42:15.990
It's not, I guess bug, maybe, maybe not.
878
00:42:16.290 --> 00:42:17.850
So I'll tell the full story.
879
00:42:17.970 --> 00:42:21.730
So on Cygnet, it's hard to get coins at times.
880
00:42:21.730 --> 00:42:25.850
So AJ Towns, who's one of the Cygnet developers has something where you
881
00:42:25.850 --> 00:42:29.750
basically run proof of work mining on your computer for Bitcoin inquisition.
882
00:42:29.930 --> 00:42:34.070
And then when you do enough, you every Cygnet block, he gives coins out as like
883
00:42:34.070 --> 00:42:34.650
a faucet.
884
00:42:35.070 --> 00:42:38.050
And I had that running on a server for a couple of days.
885
00:42:38.310 --> 00:42:40.770
And the problem is, is every block you get a couple of UTXOs.
886
00:42:40.870 --> 00:42:44.030
So all of a sudden I had thousands of UTXOs in my Sparrow wallet for my
887
00:42:44.030 --> 00:42:44.850
Cygnet Sparrow wallet.
888
00:42:45.230 --> 00:42:48.350
And it wouldn't let me send because it wasn't syncing up all the way to the
889
00:42:48.350 --> 00:42:49.170
end of the chain state.
890
00:42:49.170 --> 00:42:53.870
And so I had to actually load a Bitcoin core because Bitcoin core, let me
891
00:42:53.870 --> 00:42:56.250
actually move the thousands of UTXOs to do consolidation.
892
00:42:56.470 --> 00:42:58.830
And then once I consolidate everything Sparrow was working fine.
893
00:42:58.970 --> 00:43:00.210
Again, I sent you the links to that.
894
00:43:00.290 --> 00:43:02.670
I could probably, I gave you the seed phrase too.
895
00:43:02.750 --> 00:43:03.850
So you could see it on your side.
896
00:43:03.950 --> 00:43:05.670
I could probably replicate it and set it up again.
897
00:43:05.670 --> 00:43:08.350
If you want to go take a spin on that, it's probably an edge case, but
898
00:43:08.350 --> 00:43:12.770
it was thousands of UTXOs and then it would refuse to sync to let me actually
899
00:43:12.770 --> 00:43:13.890
be able to spend transactions.
900
00:43:14.770 --> 00:43:14.890
Yeah.
901
00:43:15.030 --> 00:43:17.310
I didn't actually get a chance to look, look at that.
902
00:43:17.390 --> 00:43:17.790
Sorry, Rob.
903
00:43:17.950 --> 00:43:21.670
I'll get, but it might be a server issue because what the server has to do
904
00:43:21.670 --> 00:43:24.430
is get the history of those particular addresses.
905
00:43:24.490 --> 00:43:27.250
And that might just be falling over on that.
906
00:43:27.970 --> 00:43:28.570
That's a good point.
907
00:43:28.950 --> 00:43:30.210
It may have entirely been server side.
908
00:43:30.510 --> 00:43:30.710
Okay.
909
00:43:31.210 --> 00:43:33.330
Did you try and connect Sparrow to Bitcoin core?
910
00:43:33.790 --> 00:43:35.370
I did not, but I should have done that.
911
00:43:35.410 --> 00:43:36.330
I could do that next time.
912
00:43:36.450 --> 00:43:40.450
I may actually just turn on the server
again and dust myself, you know, a
913
00:43:40.450 --> 00:43:44.930
couple hundred Cygnet stats over thousands of UTXOs and then give that a go and
914
00:43:44.930 --> 00:43:45.950
see if I can fix it.
915
00:43:45.950 --> 00:43:47.010
If I just directly connect to core.
916
00:43:47.570 --> 00:43:47.690
Yeah.
917
00:43:47.790 --> 00:43:51.370
Typically the client is not the one who has to bear the heavy burden there.
918
00:43:51.410 --> 00:43:54.610
It's actually usually the server that does.
919
00:43:54.830 --> 00:43:58.510
And the server is typically the one that tends to fall over in those kinds of
920
00:43:58.510 --> 00:43:59.270
situations.
921
00:43:59.470 --> 00:44:02.990
Here's his trivia for NVK and Odell.
922
00:44:03.090 --> 00:44:04.390
Do you guys know what Cormoran is?
923
00:44:04.850 --> 00:44:05.130
Yeah.
924
00:44:06.230 --> 00:44:06.830
You mean the bird?
925
00:44:07.630 --> 00:44:08.070
No.
926
00:44:09.010 --> 00:44:13.530
So when you, when you collect, you connect your Sparrow to a Bitcoin core node,
927
00:44:13.730 --> 00:44:15.330
it creates a wallet called Cormoran.
928
00:44:15.330 --> 00:44:18.310
So your Bitcoin node actually adds a wallet called Cormoran.
929
00:44:18.410 --> 00:44:19.570
And that's how Sparrow does.
930
00:44:19.590 --> 00:44:21.570
It's like handshake connection and like does operations.
931
00:44:22.030 --> 00:44:23.250
Uh, same.
932
00:44:23.590 --> 00:44:25.250
It loves the bird references.
933
00:44:25.710 --> 00:44:25.950
Yeah.
934
00:44:26.370 --> 00:44:29.210
This is like a little Easter egg for people who are actually doing stuff, you
935
00:44:29.210 --> 00:44:29.430
know?
936
00:44:29.750 --> 00:44:30.230
Yeah.
937
00:44:30.390 --> 00:44:30.650
Yeah.
938
00:44:30.830 --> 00:44:31.070
Yeah.
939
00:44:31.210 --> 00:44:33.290
No, it's actually the name of the library.
940
00:44:33.430 --> 00:44:39.170
So it's like a, a library inside Sparrow, which is very much like EPS or, um,
941
00:44:39.250 --> 00:44:39.990
BWT.
942
00:44:39.990 --> 00:44:43.770
If you've ever heard of those and basically uses Bitcoin cause wallet
943
00:44:43.770 --> 00:44:45.150
functionality as a backend.
944
00:44:45.150 --> 00:44:49.910
So Bitcoin cause wallets actually scanning the chain, adding transactions that
945
00:44:49.910 --> 00:44:51.010
are relevant to the wallet.
946
00:44:51.150 --> 00:44:56.430
And then Sparrow is then through Cormorant querying that Bitcoin core wallet
947
00:44:56.430 --> 00:44:59.510
called Cormorant in order to get the transactions.
948
00:45:00.050 --> 00:45:02.750
So it's a, it's a tried and tested path.
949
00:45:03.270 --> 00:45:03.390
Great.
950
00:45:03.710 --> 00:45:08.430
Until we have an address index in Bitcoin core, it's a, it's a decent path to
951
00:45:08.430 --> 00:45:08.690
use.
952
00:45:09.270 --> 00:45:13.850
Craig, have you ever thought about just bringing the indexer inside of Sparrow?
953
00:45:14.870 --> 00:45:15.130
Yeah.
954
00:45:15.130 --> 00:45:19.230
Yeah, I have, I have, um, cause you know, like every time you depend on core
955
00:45:19.230 --> 00:45:21.310
is might as well just, it's always like that.
956
00:45:21.430 --> 00:45:23.230
It's like, Oh, you know, for sure.
957
00:45:23.330 --> 00:45:27.270
But you, you don't want to, you know, you want to be able to close Sparrow.
958
00:45:27.410 --> 00:45:29.230
It's like, it's like, it should be a cold wallet.
959
00:45:29.370 --> 00:45:29.630
Yes.
960
00:45:30.110 --> 00:45:33.690
So you, you, you don't want to try and make clients into servers and servers
961
00:45:33.690 --> 00:45:34.330
into clients.
962
00:45:34.350 --> 00:45:36.910
Like there's a reason that we have a client server architecture to
963
00:45:36.910 --> 00:45:37.350
architecture.
964
00:45:37.630 --> 00:45:39.010
It's, it kind of works well.
965
00:45:39.190 --> 00:45:42.810
And from like a user experience point of view, from an engineering point of
966
00:45:42.810 --> 00:45:44.310
view, it all works, works well.
967
00:45:45.030 --> 00:45:49.250
And then also these address index servers, these elect electrum surf servers,
968
00:45:49.410 --> 00:45:51.670
like they, they require a lot of work.
969
00:45:51.730 --> 00:45:53.550
They're, they're not easy to write.
970
00:45:53.730 --> 00:45:54.010
Yeah.
971
00:45:54.210 --> 00:45:58.590
And we've had many people like there's actually many more of them than you
972
00:45:58.590 --> 00:45:59.170
might imagine.
973
00:45:59.250 --> 00:46:03.270
There's so many abandoned attempts at writing an electrum server.
974
00:46:03.390 --> 00:46:06.970
If you go and dig around and get GitHub, I still find one every few months,
975
00:46:07.050 --> 00:46:07.570
months or so.
976
00:46:07.630 --> 00:46:08.310
Somebody tried.
977
00:46:08.810 --> 00:46:11.090
The reality is that they are not easy to write.
978
00:46:11.090 --> 00:46:15.970
That's probably why the core devs chose not to try and make one, even though I
979
00:46:15.970 --> 00:46:19.490
think that was the wrong choice because they just aren't that, that easy to do.
980
00:46:19.650 --> 00:46:20.570
But that's where it should be.
981
00:46:21.010 --> 00:46:21.790
Yeah, absolutely.
982
00:46:22.270 --> 00:46:23.290
That is where it should be.
983
00:46:24.270 --> 00:46:24.570
Yeah.
984
00:46:24.630 --> 00:46:27.370
Plus you'd be indexing data locally, right?
985
00:46:27.650 --> 00:46:29.150
That would be, it's a lot nicer.
986
00:46:29.890 --> 00:46:30.290
Yeah.
987
00:46:30.570 --> 00:46:34.570
I mean, I think we can agree in hindsight perhaps, and there are arguments for
988
00:46:34.570 --> 00:46:38.550
and against, but in hindsight, it would mean better taking the effort spent on
989
00:46:38.550 --> 00:46:41.910
the Bitcoin core wallets and putting that into an address index.
990
00:46:42.490 --> 00:46:44.290
Just open an issue on core.
991
00:46:45.570 --> 00:46:46.230
Absolutely.
992
00:46:49.390 --> 00:46:50.830
All right.
993
00:46:51.790 -->
00:46:54.350
Software releases and project updates here for Nostr.
994
00:46:54.450 --> 00:46:59.730
Just Nostr messaging layer security, MLS library released.
995
00:47:00.270 --> 00:47:00.810
That's awesome.
996
00:47:01.410 --> 00:47:04.110
That's been released because we desperately need that.
997
00:47:04.490 --> 00:47:08.850
For other people trying to do Bitcoin things on Nostr, don't unless you use
998
00:47:08.850 --> 00:47:09.670
something like MLS.
999
00:47:10.270 --> 00:47:14.990
It's the wrong carrier, guys, to do privacy things unless you use something
1000
00:47:14.990 --> 00:47:15.510
like MLS.
1001
00:47:16.350 --> 00:47:16.690
Yeah.
1002
00:47:16.770 --> 00:47:21.470
I mean, even with MLS, like, you know, you are putting sensitive data.
1003
00:47:21.670 --> 00:47:22.470
I assume it's sensitive.
1004
00:47:22.590 --> 00:47:23.930
Otherwise you wouldn't encrypt it.
1005
00:47:24.010 --> 00:47:26.610
You're putting sensitive data onto a server.
1006
00:47:27.210 --> 00:47:32.610
That server has no deletion policy, certainly no deletion policy you have any
1007
00:47:32.610 --> 00:47:33.570
control over.
1008
00:47:34.070 --> 00:47:39.670
And what happens in 10 years, 15, 20 years when we live in a post quantum
1009
00:47:39.670 --> 00:47:46.270
world, those messages that you sent are now open for anyone to read.
1010
00:47:46.810 --> 00:47:48.390
And people will read them.
1011
00:47:48.570 --> 00:47:48.710
Yeah.
1012
00:47:48.910 --> 00:47:53.470
They will be fed into some AI and information will come out.
1013
00:47:53.610 --> 00:47:59.090
So, you know, it's just a better world where you don't have data that can be
1014
00:47:59.090 --> 00:48:02.310
hacked versus a world where you have data that can be hacked.
1015
00:48:02.510 --> 00:48:03.490
That's how I see it.
1016
00:48:03.490 --> 00:48:10.110
This is a huge reason why we've always, always told people, don't upload your
1017
00:48:10.110 --> 00:48:14.570
cold card backup file into the cloud or a computer.
1018
00:48:14.770 --> 00:48:19.690
Keep it on the micro SD because you just never know tomorrow, you know, like
1019
00:48:19.690 --> 00:48:23.270
that encryption one day could be broken and that data would be available.
1020
00:48:23.270 --> 00:48:28.190
Right now, if that backup file is buried somewhere, you know, it would just
1021
00:48:28.190 --> 00:48:29.110
probably be forgotten.
1022
00:48:29.250 --> 00:48:30.310
It would be molded alone.
1023
00:48:30.810 --> 00:48:31.070
Right?
1024
00:48:31.170 --> 00:48:34.530
Like, so yes, always think about forward privacy.
1025
00:48:35.290 --> 00:48:38.390
You know, it's not what privacy can do to you today.
1026
00:48:39.710 --> 00:48:44.950
Anyways, next, Primal got updated, demos got updated.
1027
00:48:45.810 --> 00:48:51.850
Oh, by the way, back to a little bit, I was giving Tidwell some friendly fire.
1028
00:48:52.490 --> 00:48:58.010
You know, I have a massive gripe with that website, with the Stalkers news or
1029
00:48:58.010 --> 00:48:58.790
something like that.
1030
00:48:58.790 --> 00:49:03.130
Like you have to pay to post, you have to pay to reply.
1031
00:49:03.330 --> 00:49:04.230
And it's a walled garden.
1032
00:49:04.370 --> 00:49:06.870
I do not understand why people post there to do that.
1033
00:49:07.030 --> 00:49:07.690
Post on Twitter.
1034
00:49:07.910 --> 00:49:09.550
At least there is like a large audience.
1035
00:49:10.310 --> 00:49:10.870
Like that thing.
1036
00:49:11.170 --> 00:49:14.150
Wasn't like that guy going to migrate that thing to Nostra or something.
1037
00:49:14.270 --> 00:49:15.070
And that never happened.
1038
00:49:15.950 --> 00:49:16.630
Keon, right?
1039
00:49:17.870 --> 00:49:18.270
Yes.
1040
00:49:19.350 --> 00:49:24.010
I'm no one to tell him what to do, but like, just, it's just like, we
1041
00:49:24.010 --> 00:49:25.310
don't need more walled gardens.
1042
00:49:26.430 --> 00:49:28.090
It's weird that it's not Nostra.
1043
00:49:28.730 --> 00:49:30.230
That they're not Nostra events.
1044
00:49:31.290 --> 00:49:34.630
Well, I mean, you know, like people want to make a business and, you know, like
1045
00:49:34.630 --> 00:49:37.650
I understand in that sense, you want to, he wants to own the information.
1046
00:49:38.370 --> 00:49:38.730
Yeah.
1047
00:49:38.730 --> 00:49:40.650
He doesn't want to give up his network effect.
1048
00:49:41.210 --> 00:49:41.570
Yes.
1049
00:49:42.830 --> 00:49:44.850
Which it's not going to go anywhere either.
1050
00:49:44.970 --> 00:49:49.490
Like it's a, you didn't used to have to pay to post.
1051
00:49:49.550 --> 00:49:50.290
You have to pay to post.
1052
00:49:50.450 --> 00:49:53.910
No, I haven't used it basically since Nostra came out.
1053
00:49:54.130 --> 00:49:56.510
Or you have to pay to reply or something like that.
1054
00:49:57.770 --> 00:49:59.170
Anyways, don't like it.
1055
00:49:59.910 --> 00:50:01.330
That was just very random.
1056
00:50:01.810 --> 00:50:06.170
No, it's because it's the, so like, so the problem is a lot of people joined
1057
00:50:06.170 --> 00:50:11.310
Nostra a year ago, two years ago on, on a different client that didn't work.
1058
00:50:11.590 --> 00:50:15.230
And then they all get set up wrong and then they hate Nostra.
1059
00:50:15.310 --> 00:50:15.510
Right.
1060
00:50:15.890 --> 00:50:19.030
And then I have to get them to go on Primo and try Primo.
1061
00:50:19.150 --> 00:50:21.990
And then they go like, Oh, this actually works, you know?
1062
00:50:22.050 --> 00:50:25.610
And then they have to clean up their relay list, you know?
1063
00:50:25.610 --> 00:50:30.170
And then anyways, yeah, I think that's our biggest, our biggest issue has been
1064
00:50:30.170 --> 00:50:31.450
pretty frustrating.
1065
00:50:31.590 --> 00:50:34.770
See the lack of Bitcoin or usage of Nostra.
1066
00:50:35.170 --> 00:50:40.190
And I think the single biggest issue is that a lot of Bitcoiners had a first
1067
00:50:40.190 --> 00:50:41.150
touch with Nostra.
1068
00:50:41.610 --> 00:50:44.970
It was not stable and they haven't come back and try it again.
1069
00:50:45.510 --> 00:50:48.090
And that's a hard hurdle to beat.
1070
00:50:48.210 --> 00:50:51.370
It's, it's hard enough getting someone to try something for the first time, but
1071
00:50:51.370 --> 00:50:55.470
when their first touch is a bad touch point, it's even harder to get them back.
1072
00:50:55.470 --> 00:50:57.890
Bad touch, bad touch.
1073
00:51:02.610 --> 00:51:07.810
You know, I've told Milian many times, that's the founder of Primo, that, you
1074
00:51:07.810 --> 00:51:14.870
know, we really need like some good reply sort of UI for long form posts
1075
00:51:14.870 --> 00:51:20.410
because all the keyboard warriors like the Reddit or Hacker News format of like
1076
00:51:20.410 --> 00:51:25.430
writing a lot and all the stuff being displayed in this horrible trees, you
1077
00:51:25.430 --> 00:51:30.310
know, at this horrible trees is what promotes keyboard warring, which is what
1078
00:51:30.310 --> 00:51:31.250
the users want.
1079
00:51:31.550 --> 00:51:33.350
You know, they don't want to win.
1080
00:51:33.450 --> 00:51:34.390
They want to be right.
1081
00:51:34.690 --> 00:51:34.910
Right.
1082
00:51:35.050 --> 00:51:37.930
So they just keep on fucking like going and doing that.
1083
00:51:38.710 --> 00:51:41.010
Gmax, for example, huge fan of that format.
1084
00:51:41.430 --> 00:51:42.710
That's why he's on Reddit still.
1085
00:51:44.370 --> 00:51:49.330
So anyway, so Milian, if you're listening, please add the keyboard warrior mode
1086
00:51:49.330 --> 00:51:50.950
for a long form posts.
1087
00:51:50.950 --> 00:51:54.570
And I think maybe we can get some of that discussion moving over to Nostr.
1088
00:51:55.130 --> 00:52:02.570
It's of huge importance in history keeping that we have Bitcoin discussions on
1089
00:52:02.570 --> 00:52:05.870
open protocols the same way that the money is open.
1090
00:52:06.230 --> 00:52:11.290
And hopefully we remove the Nostr derangement syndrome from so many Bitcoiners.
1091
00:52:12.550 --> 00:52:13.890
That rant is over.
1092
00:52:16.450 --> 00:52:18.850
Okay, a bunch of other stuff here.
1093
00:52:19.610 --> 00:52:20.570
What else, guys?
1094
00:52:20.870 --> 00:52:24.410
Is there anything that we have to fix on my house?
1095
00:52:25.290 --> 00:52:29.170
Any of the things that we make that is of a way you guys don't like,
1096
00:52:29.210 --> 00:52:32.690
because I'm also happy to take some flack because you guys are all users.
1097
00:52:33.890 --> 00:52:35.010
Immediately, nothing comes.
1098
00:52:36.210 --> 00:52:39.970
Can we, can you make it so the block clocks update quicker?
1099
00:52:40.190 --> 00:52:45.370
I know it kills the eating screen, but like I'm my own, like I should be
1100
00:52:45.370 --> 00:52:49.170
able to practice personal responsibility and kill my eating screen quicker.
1101
00:52:50.290 --> 00:52:51.650
I don't know, man.
1102
00:52:51.850 --> 00:52:56.010
Then people fucking contact support and it's like, Oh, my digits are dead.
1103
00:52:56.090 --> 00:52:58.650
And then it's a tricky one.
1104
00:52:59.850 --> 00:53:04.110
Maybe if we add something that like requires some proof of work in order to get
1105
00:53:04.110 --> 00:53:05.870
in there and change the setting.
1106
00:53:06.210 --> 00:53:07.850
You need edge firmware for the block clock.
1107
00:53:08.490 --> 00:53:09.350
There you go.
1108
00:53:10.370 --> 00:53:10.530
Yeah.
1109
00:53:10.570 --> 00:53:12.930
Give me edge firmware with 30 second updates.
1110
00:53:13.570 --> 00:53:14.270
30 seconds.
1111
00:53:14.350 --> 00:53:14.650
Okay.
1112
00:53:15.450 --> 00:53:16.830
High time preference, Matt.
1113
00:53:17.030 --> 00:53:18.030
That's, that's fine.
1114
00:53:18.030 --> 00:53:20.150
I mean, it's just for the fee rate.
1115
00:53:20.530 --> 00:53:21.470
It's just the block height.
1116
00:53:21.570 --> 00:53:23.750
Every 30 seconds, you're just refreshing the block height.
1117
00:53:23.950 --> 00:53:27.370
You know, it's going to like, listen, this, this, this is good for my bottom
1118
00:53:27.370 --> 00:53:27.650
line.
1119
00:53:27.730 --> 00:53:29.330
People are going to have to buy more clocks.
1120
00:53:29.470 --> 00:53:30.590
This is going to kill the digits.
1121
00:53:31.270 --> 00:53:33.650
It's just, I'm trying to avoid that, but okay.
1122
00:53:34.550 --> 00:53:39.110
30 second updates on the clock for a minute.
1123
00:53:39.930 --> 00:53:40.330
Okay.
1124
00:53:40.550 --> 00:53:40.950
Noted.
1125
00:53:41.690 --> 00:53:44.850
Not directly you guys, but we were talking about this last night, the stats
1126
00:53:44.850 --> 00:53:45.130
card.
1127
00:53:45.130 --> 00:53:49.050
What's the best wallet to use with the stats card right now that you would
1128
00:53:49.050 --> 00:53:49.430
recommend?
1129
00:53:49.950 --> 00:53:52.430
So, so Nunchuck is pretty good.
1130
00:53:52.830 --> 00:53:53.050
Okay.
1131
00:53:53.290 --> 00:53:57.350
I think Cove might have support soon.
1132
00:53:57.670 --> 00:53:57.890
Okay.
1133
00:53:58.970 --> 00:54:02.070
Keeper, Bitcoin Keeper supports it well as well.
1134
00:54:03.330 --> 00:54:08.310
Craig, does Sparrow support it, but you need the USB NFC thingy, right?
1135
00:54:08.650 --> 00:54:10.190
You need the NFC thing.
1136
00:54:10.290 --> 00:54:10.490
Yeah.
1137
00:54:10.690 --> 00:54:10.950
Yeah.
1138
00:54:11.090 --> 00:54:16.870
I mean, it's, I've actually quite, I quite enjoy using it there, but, you know,
1139
00:54:16.970 --> 00:54:20.370
obviously I realize that not many people are going to often buy the separate
1140
00:54:20.370 --> 00:54:23.750
NFC device, but it does work pretty well.
1141
00:54:24.470 --> 00:54:31.810
It is beyond me why Apple, out of all the players in the space, does not
1142
00:54:31.810 --> 00:54:38.370
have NFC on their computers because, you know, people tap shit and, you know,
1143
00:54:38.450 --> 00:54:42.250
like, Matt almost spit his beer.
1144
00:54:43.530 --> 00:54:45.030
And I think we need it.
1145
00:54:45.770 --> 00:54:46.050
Anyways.
1146
00:54:47.210 --> 00:54:51.990
Well, I mean, I think the only feedback I could give is that I think the,
1147
00:54:51.990 --> 00:54:56.690
the cube probably needs an upgrade to its case.
1148
00:54:56.990 --> 00:54:59.690
And I quite like the clear case.
1149
00:55:00.030 --> 00:55:03.090
I think it's got that cypherpunk ethos to it.
1150
00:55:03.150 --> 00:55:07.810
But, you know, if you've used the Ledger Flex, and I know you have, Rob.
1151
00:55:07.810 --> 00:55:08.370
Yeah.
1152
00:55:08.510 --> 00:55:12.630
It is, it is a really nice piece of hardware to hold in your hand.
1153
00:55:12.830 --> 00:55:13.010
Yes.
1154
00:55:13.110 --> 00:55:15.750
Now, it's just not the same thing as a cold card.
1155
00:55:15.870 --> 00:55:19.610
And I get that, but it is still a nice piece of hardware to hold in
1156
00:55:19.610 --> 00:55:19.950
your hand.
1157
00:55:20.070 --> 00:55:20.170
Yeah.
1158
00:55:20.250 --> 00:55:23.810
So we've been having these discussions with an industrial design firm we've
1159
00:55:23.810 --> 00:55:24.470
been talking to.
1160
00:55:24.830 --> 00:55:30.190
And like, it's so annoying because all of this is born out of trying to be
1161
00:55:30.190 --> 00:55:31.570
clear, not frosted.
1162
00:55:32.010 --> 00:55:33.370
It's kind of a funny problem.
1163
00:55:33.570 --> 00:55:33.890
Okay.
1164
00:55:33.890 --> 00:55:37.350
And it's like a full on human perception issue.
1165
00:55:37.750 --> 00:55:42.150
And we've tested this, you know, with people and stuff.
1166
00:55:42.350 --> 00:55:48.230
And it's so funny because when you do a clear, and we use polycarbonate, which
1167
00:55:48.230 --> 00:55:49.550
is very hard plastic, right?
1168
00:55:50.010 --> 00:55:51.190
It gives a nice feel.
1169
00:55:51.610 --> 00:55:57.130
But if you don't frost the case, you know, and it's just clear, it scratches
1170
00:55:57.130 --> 00:56:00.770
and then it looks cheap and it gives you that cheap feel.
1171
00:56:00.770 --> 00:56:06.150
So we are considering frosting the case a little bit like we did with the Mark
1172
00:56:06.150 --> 00:56:09.770
IV for future versions of the queue.
1173
00:56:10.370 --> 00:56:14.110
And also for future versions of like, you know, Mark V or whatever.
1174
00:56:14.450 --> 00:56:17.050
We're also like looking into tweaking that.
1175
00:56:17.650 --> 00:56:20.690
There is a lot of conversations internally about that.
1176
00:56:21.250 --> 00:56:23.490
But again, it's tricky, right?
1177
00:56:24.030 --> 00:56:32.190
We, you know, Ledger costs like maybe 20, 30 bucks inside of parts and material
1178
00:56:32.190 --> 00:56:32.710
kind of thing.
1179
00:56:32.930 --> 00:56:35.090
And they do it at a different scale that we do.
1180
00:56:35.370 --> 00:56:38.910
We cost a lot more internally in a smaller scale.
1181
00:56:39.470 --> 00:56:41.590
So
the economics are tricky.
1182
00:56:41.690 --> 00:56:46.350
Like we're essentially like giving you three, four times more hardware in terms
1183
00:56:46.350 --> 00:56:48.990
of value there than they do.
1184
00:56:50.090 --> 00:56:53.150
But yeah, no, it is a criticism that is well taken.
1185
00:56:53.150 --> 00:56:56.010
And we do want to fix it.
1186
00:56:56.050 --> 00:57:01.270
It bothers me when people say, you know, it feels cheap or whatever, but, you
1187
00:57:01.270 --> 00:57:02.170
know.
1188
00:57:03.530 --> 00:57:06.830
I guess in other things related to that, I've had to do this with the queue
1189
00:57:06.830 --> 00:57:07.670
a couple of times.
1190
00:57:07.870 --> 00:57:08.270
I'm not sure.
1191
00:57:08.430 --> 00:57:09.310
It's an easy fix.
1192
00:57:10.110 --> 00:57:13.390
Occasionally I'll try and use the QR and it'll just say camera, not red.
1193
00:57:13.510 --> 00:57:15.970
And I have to like take out the batteries and put the battery back in.
1194
00:57:16.150 --> 00:57:18.450
I'm not sure if that's like a connectivity thing or if there's something I
1195
00:57:18.450 --> 00:57:18.870
could be doing.
1196
00:57:19.150 --> 00:57:20.030
Are you running latest?
1197
00:57:20.830 --> 00:57:21.090
Yeah.
1198
00:57:21.970 --> 00:57:26.790
Well, I mean, no, no, send us the QR and send us the, we want to
1199
00:57:26.790 --> 00:57:27.430
repro that.
1200
00:57:27.850 --> 00:57:28.910
No, no, it's not.
1201
00:57:29.230 --> 00:57:33.170
It's physically the device, like the QR connections loose or something.
1202
00:57:33.250 --> 00:57:36.190
And I've had it happen on, because I have a couple of queues where like, I
1203
00:57:36.190 --> 00:57:37.850
don't know, I could be doing, maybe it's the QR.
1204
00:57:38.090 --> 00:57:40.470
I'll send you the, I'll send you the QR and I'll reproduce it and let you
1205
00:57:40.470 --> 00:57:40.630
know.
1206
00:57:40.710 --> 00:57:44.050
But like, no, no, I want to, I want to reproduce that or find the problem.
1207
00:57:44.150 --> 00:57:45.230
I'll get the error message too.
1208
00:57:45.310 --> 00:57:46.350
It's like a unique error message.
1209
00:57:46.490 --> 00:57:47.050
It feels for Jesus.
1210
00:57:47.050 --> 00:57:49.150
I have to be recording to get this kind of feedback.
1211
00:57:49.790 --> 00:57:52.030
It's, but the fix is I just take out the batteries and put them back in.
1212
00:57:52.090 --> 00:57:52.730
And it's totally fine.
1213
00:57:52.890 --> 00:57:54.110
No, I want to fix it.
1214
00:57:54.370 --> 00:57:54.790
No, I agree.
1215
00:57:55.150 --> 00:57:55.910
You asked for it.
1216
00:57:56.230 --> 00:57:56.330
Yeah.
1217
00:57:57.690 --> 00:57:58.710
I love this.
1218
00:57:59.150 --> 00:58:02.350
We, we need the, we need people to participate in the product development.
1219
00:58:03.050 --> 00:58:03.170
Yeah.
1220
00:58:03.310 --> 00:58:04.310
Maybe that's what we should do.
1221
00:58:04.370 --> 00:58:09.710
I should start a new podcast where we just invite people and we give each other
1222
00:58:09.710 --> 00:58:13.710
a feedback product roadmap, open forum.
1223
00:58:13.890 --> 00:58:14.070
Yeah.
1224
00:58:14.150 --> 00:58:14.330
Yeah.
1225
00:58:14.470 --> 00:58:14.830
Yes.
1226
00:58:15.730 --> 00:58:19.770
I think the other piece, the other piece that makes the Q feel a little bit
1227
00:58:19.770 --> 00:58:20.850
cheaper is the keyboard.
1228
00:58:21.630 --> 00:58:22.150
Yeah.
1229
00:58:22.210 --> 00:58:23.010
The squishy keyboard.
1230
00:58:23.390 --> 00:58:24.310
I like that.
1231
00:58:24.410 --> 00:58:25.830
The MK4 keyboard.
1232
00:58:25.910 --> 00:58:28.310
I've, it feels really nice in hand.
1233
00:58:28.570 --> 00:58:28.950
Yeah.
1234
00:58:29.430 --> 00:58:31.430
I don't get the same feel from the Q.
1235
00:58:31.650 --> 00:58:34.930
I wanted to license the Blackberry keyboard.
1236
00:58:35.110 --> 00:58:38.170
I'm sick, but it's very tricky.
1237
00:58:38.850 --> 00:58:43.950
So yeah, we are, that's also on the list of future versions to task.
1238
00:58:45.170 --> 00:58:51.670
And, uh, so the, yes, the keyboard, the plastic, what else?
1239
00:58:52.410 --> 00:58:55.270
I mean, there's a bunch of things I want to change personally.
1240
00:58:55.390 --> 00:58:59.350
My list is very long, very long.
1241
00:58:59.970 --> 00:59:02.970
You're now, you're now signing descriptors, right?
1242
00:59:03.010 --> 00:59:04.890
You're signing more data when you do exports.
1243
00:59:04.990 --> 00:59:06.670
Now the descriptors are being signed.
1244
00:59:07.490 --> 00:59:08.330
That's good.
1245
00:59:08.570 --> 00:59:09.550
I like that.
1246
00:59:09.990 --> 00:59:11.690
Anything, everything should be signed.
1247
00:59:11.910 --> 00:59:12.970
Everything should be signed.
1248
00:59:12.970 --> 00:59:14.230
Everything should be signed.
1249
00:59:14.230 --> 00:59:14.330
It'd be cool.
1250
00:59:14.470 --> 00:59:15.550
Does that work for the QR too?
1251
00:59:15.610 --> 00:59:17.830
If you're signing via the QR, does it give like a sign payload?
1252
00:59:17.950 --> 00:59:18.570
Could you do that?
1253
00:59:19.110 --> 00:59:20.350
So that you can know the QR is signed?
1254
00:59:20.930 --> 00:59:21.430
Can't remember.
1255
00:59:21.550 --> 00:59:22.110
I have to check.
1256
00:59:22.230 --> 00:59:24.370
Maybe a BBQR spec for signed message return.
1257
00:59:24.690 --> 00:59:28.310
That's probably part of the BBQR spec already though, for signed messages.
1258
00:59:28.670 --> 00:59:31.090
Cause you can just wrap the message that you're trying to send back in a
1259
00:59:31.090 --> 00:59:31.410
signature.
1260
00:59:31.810 --> 00:59:35.490
The signed message, yes, but I can't remember if the detached signature, that's
1261
00:59:35.490 --> 00:59:36.650
what we do for those.
1262
00:59:36.990 --> 00:59:37.270
We'll go.
1263
00:59:37.850 --> 00:59:38.450
It'd be a cool option.
1264
00:59:39.010 --> 00:59:39.310
Yeah.
1265
00:59:40.530 --> 00:59:44.450
Um, I mean, even more
than that would be amazing if there was an ephemeral
1266
00:59:44.450 --> 00:59:47.690
handshake between the hardware wallet and the desktop wallet.
1267
00:59:48.390 --> 00:59:48.590
Yes.
1268
00:59:48.710 --> 00:59:49.750
Or the phone wallet.
1269
00:59:50.190 --> 00:59:54.190
And then, and then you're like, you know, a nice encrypted tunnel between the
1270
00:59:54.190 --> 00:59:54.410
two.
1271
00:59:55.010 --> 00:59:59.590
That's what the, a lot of the wallets that, um, that have preparatory software
1272
00:59:59.590 --> 01:00:00.290
can do.
1273
01:00:00.810 --> 01:00:00.930
Yeah.
1274
01:00:01.550 --> 01:00:04.090
Sounds like, uh, Craig and you should talk about that.
1275
01:00:04.170 --> 01:00:06.830
It sounds like a hardware wallet coordinator conversation.
1276
01:00:06.930 --> 01:00:09.130
I think we talked about this like years ago.
1277
01:00:09.630 --> 01:00:09.810
Yeah.
1278
01:00:09.990 --> 01:00:11.370
But it's not an easy problem.
1279
01:00:11.370 --> 01:00:12.510
No, not at all.
1280
01:00:13.150 --> 01:00:13.290
Yeah.
1281
01:00:13.390 --> 01:00:16.790
I mean, obviously that's what the USB does, right?
1282
01:00:16.850 --> 01:00:20.930
It sets up this encrypted tunnel, everything signed back and back and forth.
1283
01:00:21.050 --> 01:00:24.930
So most of the, not actually not, not most, I stand corrected.
1284
01:00:25.070 --> 01:00:25.890
I correct myself.
1285
01:00:26.210 --> 01:00:31.170
Some of the hardware wallets have an encrypted tunnel and, and most do not.
1286
01:00:31.350 --> 01:00:31.630
Yes.
1287
01:00:32.010 --> 01:00:37.810
But, um, you know, if you're sending QR codes back and forth, you know, I don't
1288
01:00:37.810 --> 01:00:37.970
know.
1289
01:00:38.030 --> 01:00:40.630
Is it, is it, does it matter as much to you then?
1290
01:00:41.730 --> 01:00:43.790
I've been, you know, my paranoid self.
1291
01:00:44.790 --> 01:00:50.150
As, uh, always wants things to be signed, but in signing away, see my, my
1292
01:00:50.150 --> 01:00:53.810
preference on this, just generally speaking is, is the devices should be
1293
01:00:53.810 --> 01:00:58.510
checking signatures, knowing the sender, essentially some, some, if he, some,
1294
01:00:58.590 --> 01:01:02.250
some holiday kind of thing, I don't want the users to be checking those
1295
01:01:02.250 --> 01:01:02.630
signatures.
1296
01:01:02.630 --> 01:01:06.230
Cause as a user is kind of, you know, if your environment is already fucked,
1297
01:01:06.330 --> 01:01:09.670
you could be like, Oh, I got a false positive too.
1298
01:01:09.810 --> 01:01:09.950
Right.
1299
01:01:10.830 --> 01:01:16.650
So, yeah, I mean, if it just feels a little, uh, little, uh, is this really
1300
01:01:16.650 --> 01:01:17.190
going to help?
1301
01:01:17.230 --> 01:01:20.850
You know, it's like, you're going to point the QR code at the application.
1302
01:01:21.070 --> 01:01:21.750
I mean, sure.
1303
01:01:21.790 --> 01:01:25.510
If you pointed a different application and then
that application then gets
1304
01:01:25.510 --> 01:01:28.690
access, then you could maybe alleviate that issue.
1305
01:01:28.950 --> 01:01:32.810
But it's, it's like, do we not have better things to work on?
1306
01:01:33.530 --> 01:01:34.470
I don't know.
1307
01:01:35.070 --> 01:01:41.330
I mean, you know, we already have pretty amazing setup, uh, between the two,
1308
01:01:41.730 --> 01:01:43.370
the hardware and the software.
1309
01:01:43.570 --> 01:01:46.270
So like, you know, kind of like looking for things to do here.
1310
01:01:47.770 --> 01:01:49.410
I've got plenty of things to do.
1311
01:01:49.750 --> 01:01:50.650
I've got lots.
1312
01:01:52.010 --> 01:01:52.650
That's right.
1313
01:01:52.790 --> 01:01:53.230
That's right.
1314
01:01:53.810 --> 01:01:54.450
All right, boys.
1315
01:01:54.970 --> 01:01:57.650
Uh, is there any other topics you guys want to address?
1316
01:01:57.910 --> 01:01:59.270
Don't forget the boosts.
1317
01:01:59.750 --> 01:02:01.530
Oh, the boosts, the boosts.
1318
01:02:01.650 --> 01:02:02.110
Thank you.
1319
01:02:02.310 --> 01:02:03.590
Come on Mr. Value for value.
1320
01:02:04.490 --> 01:02:08.290
You know, I once I actually did a boost on this other podcast like two weeks
1321
01:02:08.290 --> 01:02:12.170
ago, because I was going to be speaking at bit devs in Philadelphia, Bitcoin,
1322
01:02:12.270 --> 01:02:15.150
John, and I donated them sass and they didn't even read the boost.
1323
01:02:15.390 --> 01:02:15.830
Hmm.
1324
01:02:16.190 --> 01:02:18.190
So other, other shows out there, skip the boosts.
1325
01:02:18.390 --> 01:02:25.710
I am just happy that, uh, again, we've been pod conf disapproved, which is
1326
01:02:25.710 --> 01:02:26.050
perfect.
1327
01:02:26.090 --> 01:02:30.270
So I hope this episode was also maybe approved.
1328
01:02:30.550 --> 01:02:31.330
Maybe we made it.
1329
01:02:31.470 --> 01:02:32.050
I don't know.
1330
01:02:32.190 --> 01:02:32.850
Well, that was here.
1331
01:02:32.850 --> 01:02:34.030
So maybe we made it.
1332
01:02:34.070 --> 01:02:35.630
We have a professional podcaster.
1333
01:02:36.030 --> 01:02:38.710
This is due to Rheindell where pod comp disapproved by Rob Palmer.
1334
01:02:38.970 --> 01:02:39.270
Yes.
1335
01:02:39.830 --> 01:02:43.030
Aren't I the only one here that's pod comp disapproved?
1336
01:02:43.230 --> 01:02:43.730
I think so.
1337
01:02:44.050 --> 01:02:45.270
No, we are disapproved.
1338
01:02:45.710 --> 01:02:46.590
I'm fully approved.
1339
01:02:47.190 --> 01:02:47.430
Yeah.
1340
01:02:48.350 --> 01:02:48.750
Why?
1341
01:02:50.010 --> 01:02:52.150
I said, dude, because we had Rheindell on last show.
1342
01:02:52.250 --> 01:02:53.510
So it's pod comp disapproved now.
1343
01:02:53.950 --> 01:02:56.330
Uh, we've always been disapproved.
1344
01:02:56.490 --> 01:02:58.270
We have never had a show that was approved.
1345
01:03:00.530 --> 01:03:03.150
I mean, Rob is definitely approved.
1346
01:03:03.570 --> 01:03:03.750
Yeah.
1347
01:03:04.430 --> 01:03:10.270
He has all the, he has all the paraphernalia, but that's his buying his
1348
01:03:10.270 --> 01:03:10.690
approval.
1349
01:03:10.790 --> 01:03:11.650
That doesn't count.
1350
01:03:12.610 --> 01:03:15.550
Average Gary up next was great.
1351
01:03:15.930 --> 01:03:21.650
Run your test net for CTV plus CS, C S F S client.
1352
01:03:21.910 --> 01:03:24.130
They're going to need to change that acronym, man.
1353
01:03:24.710 --> 01:03:26.210
It's very hard to say it.
1354
01:03:26.230 --> 01:03:26.430
Yeah.
1355
01:03:27.310 --> 01:03:37.230
Uh, has S V two enabled branch to DB near zero pink money, fire, fire, fire,
1356
01:03:37.350 --> 01:03:43.210
user for fire, fire, fire, wartime mon and not the men pool monkey.
1357
01:03:43.650 --> 01:03:44.510
Oh, right.
1358
01:03:44.910 --> 01:03:45.310
Okay.
1359
01:03:45.750 --> 01:03:46.930
BTC con board.
1360
01:03:47.730 --> 01:03:48.590
Lots of emojis.
1361
01:03:49.630 --> 01:03:50.430
Thanks guys.
1362
01:03:51.830 --> 01:03:56.070
Tech tip of the day, a free online cryptography course repository.
1363
01:03:56.070 --> 01:04:02.050
Alfred menace includes video slides, exercises, solutions, news items.
1364
01:04:02.550 --> 01:04:03.290
go check out that.
1365
01:04:03.550 --> 01:04:05.610
Go check out the show notes as usual.
1366
01:04:05.890 --> 01:04:11.050
We have pages and pages and pages and pages of show notes.
1367
01:04:11.490 --> 01:04:15.970
All the details that we didn't cover on the show, I guess.
1368
01:04:16.090 --> 01:04:21.670
Uh, any final thoughts, Rob final thoughts, uh, just keep on building.
1369
01:04:22.250 --> 01:04:26.550
If you're not building, just hang out, touch grass, spend time with family,
1370
01:04:26.730 --> 01:04:30.030
make a family, get some sunlight summers here.
1371
01:04:30.270 --> 01:04:32.850
It's good vibes all around and don't upgrade your Bitcoin note.
1372
01:04:33.530 --> 01:04:36.470
If you're too confused about what's going to just, just hang out and chill.
1373
01:04:36.590 --> 01:04:37.470
It's all going to be okay.
1374
01:04:37.850 --> 01:04:39.450
Bitcoin is going to keep on rolling along.
1375
01:04:40.490 --> 01:04:41.310
Uh, Craig.
1376
01:04:42.370 --> 01:04:44.390
Uh, yeah, I don't have too much to add to that.
1377
01:04:44.670 --> 01:04:49.550
Um, yeah, try not to get too, uh, worked up about the drama online.
1378
01:04:50.010 --> 01:04:55.070
Uh, it will eventually pass in the way that everyone will be kind of okay with.
1379
01:04:55.070 --> 01:04:59.730
In some way that will kind of find their little corner and they will have their
1380
01:04:59.730 --> 01:05:02.790
tribe and things will, uh, figure themselves out.
1381
01:05:02.890 --> 01:05:07.930
So, uh, don't, don't get too upset about it, but there are some important
1382
01:05:07.930 --> 01:05:10.090
issues that I touched on earlier.
1383
01:05:10.470 --> 01:05:13.830
Those are issues which, uh, could do with some more attention.
1384
01:05:13.850 --> 01:05:18.210
So, uh, I would definitely, uh, think a little bit more about that.
1385
01:05:18.930 --> 01:05:22.790
Mr. Adele to Craig's point.
1386
01:05:22.790 --> 01:05:26.970
If you want to donate to the samurai legal defense fund, uh, go to P2P rights
1387
01:05:26.970 --> 01:05:27.730
.org.
1388
01:05:28.390 --> 01:05:31.910
And if you've tried Nostra in the past, or if you've never tried it before,
1389
01:05:32.590 --> 01:05:34.890
consider downloading primal in your favorite app store.
1390
01:05:35.590 --> 01:05:40.150
And, uh, joining us over there, I think you'll be pleasantly surprised at, uh,
1391
01:05:40.430 --> 01:05:43.030
how far the app has come since you've last used it.
1392
01:05:44.030 --> 01:05:44.470
Guys.
1393
01:05:44.850 --> 01:05:46.210
Thank you so much for coming.
1394
01:05:46.430 --> 01:05:47.970
This was fun as usual.
1395
01:05:49.070 --> 01:05:51.270
Craig made a lot of promises on features.
1396
01:05:51.370 --> 01:05:52.410
He's going to add.
1397
01:05:53.550 --> 01:05:55.510
Rob is going to fix mini script.
1398
01:05:56.350 --> 01:05:58.750
And, uh, guys, thank you so much for coming.
1399
01:05:59.130 --> 01:05:59.430
Thank you.
1400
01:06:00.130 --> 01:06:00.410
Ciao.
1401
01:06:03.590 --> 01:06:04.490
Thanks for listening.
1402
01:06:04.750 --> 01:06:06.810
For more resources, check the show notes.
1403
01:06:07.050 --> 01:06:08.550
We put a lot of effort into them.
1404
01:06:08.810 --> 01:06:10.830
And remember, we don't have a crystal ball.
1405
01:06:11.030 --> 01:06:12.490
So let us know about your project.
1406
01:06:12.810 --> 01:06:16.450
Visit bitcoin.review to find out how to get in touch.