Jan. 12, 2022
CD50: bitcoin nodes and the @raspibolt project with @openoms and @stadicus3000
EPISODE: 50
BLOCK: 718215
PRICE: 2338 sats per dollar
TOPICS: bitcoin nodes, raspibolt, hardware tradeoffs, lightning tradeoffs, migrating nodes, transaction fees, raspibolt.org
@openoms: https://twitter.com/openoms
@stadicus3000: https://twitter.com/stadicus3000
@raspibolt: https://twitter.com/raspibolt
streamed live every tuesday:
https://citadeldispatch.com
twitch: https://twitch.tv/citadeldispatch
bitcointv: https://bitcointv.com/video-channels/citadeldispatch/videos
podcast: https://anchor.fm/citadeldispatch
telegram: https://t.me/citadeldispatch
support the show: https://citadeldispatch.com/contribute/
stream sats to the show: https://www.fountain.fm/
join the chat: http://citadel.chat/
00:01 - Bill Miller's investment in Bitcoin
00:29 - Interview with Bill Miller on Consuelo Mack WealthTrack
01:43 - Bill Miller's personal net worth in Bitcoin
53:51 - Setting up a new node and ensuring it works properly
55:19 - Moving from a 32-bit to 64-bit architecture for LND database
57:21 - Discussion on the number of channels to have open
WEBVTT
NOTE
Transcription provided by Podhome.fm
Created: 3/17/2024 8:08:42 PM
Duration: 6561.698
Channels: 1
1
00:00:01.599 --> 00:00:09.780
On WealthTrack, why investment legend Bill Miller has gone really big on Bitcoin. I think the average investor should ask himself or herself, what do you have in your portfolio
2
00:00:10.304 --> 00:00:14.724
that has this kind of track record? Number 1, is so is very, very under penetrated,
3
00:00:15.424 --> 00:00:19.925
can provide a service of insurance against financial catastrophe that no one else can provide,
4
00:00:20.529 --> 00:00:29.189
and, and can go up 10 times or 50 times. The answer is nothing. Why Bill Miller has gone big on Bitcoin is on Consuelo Mack WealthTrack.
5
00:00:29.645 --> 00:00:37.185
Hello, and welcome to this edition of WEALTHTRACK. I'm Consuelo Mack. This week is part 2 of our interview with legendary value investor Bill Miller.
6
00:00:37.660 --> 00:00:42.559
As longtime WEALTHTRACK viewers know, Miller has been a guest of ours since our launch in 2,005
7
00:00:43.579 --> 00:00:45.920
and doesn't do many TV interviews.
8
00:00:46.325 --> 00:00:47.625
As he told me recently,
9
00:00:48.004 --> 00:00:53.225
time is his scarcest resource. So we are delighted that he is with us again this week.
10
00:00:53.590 --> 00:00:57.690
Miller is the founder, owner and chief investment officer of Miller Value Partners,
11
00:00:57.990 --> 00:00:59.850
a firm he founded in 1999
12
00:01:00.605 --> 00:01:04.545
while working at Legg Mason, but took over completely in 2017.
13
00:01:05.805 --> 00:01:08.225
As most of you know, Miller holds the unbeaten
14
00:01:09.520 --> 00:01:10.580
S and P 500
15
00:01:10.960 --> 00:01:12.260
for 15 consecutive
16
00:01:12.560 --> 00:01:14.020
years from 1991
17
00:01:14.560 --> 00:01:15.140
to 2,005
18
00:01:15.875 --> 00:01:23.174
with the Legg Mason Capital Management Value Trust Fund. His flagship, Miller Opportunity Trust Fund, which he created in 1999
19
00:01:23.830 --> 00:01:26.970
and has co managed with Samantha Macklemore since 2014,
20
00:01:27.990 --> 00:01:28.650
has $2,400,000,000
21
00:01:29.590 --> 00:01:34.915
in assets and has had many market beating years interspersed with some sizable declines.
22
00:01:35.375 --> 00:01:41.155
But today's conversation is not about Miller Opportunity Trust. It's about his personal portfolio.
23
00:01:41.720 --> 00:01:42.780
And here's the headline.
24
00:01:43.479 --> 00:01:48.140
Half of Miller's personal net worth is in bitcoin and a few other cryptocurrency
25
00:01:48.840 --> 00:01:49.340
investments.
26
00:01:49.825 --> 00:01:51.045
And it's leveraged.
27
00:01:51.505 --> 00:01:54.645
I asked Miller why he has gone so big on Bitcoin
28
00:01:54.945 --> 00:01:56.645
in his personal account.
29
00:01:57.180 --> 00:02:03.520
I'd say it's a combination of of things as it would have to be to allow something to get that bigger part of your portfolio because,
30
00:02:04.095 --> 00:02:08.095
you know, it's it it goes against many of the tenants of, of,
31
00:02:08.815 --> 00:02:09.955
financial discipline.
32
00:02:10.975 --> 00:02:13.155
On the other hand, the the people that actually
33
00:02:13.660 --> 00:02:15.360
are the richest people in the country,
34
00:02:15.740 --> 00:02:18.080
all are massively concentrated. You know,
35
00:02:18.459 --> 00:02:21.120
Buffett and Berkshire, Jeff Bezos, Mark Zuckerberg.
36
00:02:21.655 --> 00:02:25.435
So they're not they're not widely diversified, but they may be they're they're highly concentrated.
37
00:02:25.894 --> 00:02:35.070
And I think that's because they have a high degree of confidence or or have a high degree of confidence in the in the value of those investments. But my my thinking here was that,
38
00:02:36.010 --> 00:02:40.995
I I heard a talk on on Bitcoin given by the person who's known as patient 0
39
00:02:41.375 --> 00:02:43.715
in the Bitcoin world, Wences Casares.
40
00:02:44.495 --> 00:02:44.815
And,
41
00:02:45.615 --> 00:02:46.115
Wences
42
00:02:46.810 --> 00:02:50.510
gave a talk at at the Allen Company Sun Valley Conference,
43
00:02:50.810 --> 00:02:53.230
and he let off his talk. This is 2014,
44
00:02:53.530 --> 00:02:54.430
I wanna say.
45
00:02:54.890 --> 00:03:01.614
He let off his talk by saying that they're asking how anybody owned Bitcoin. No. Nobody in the audience owned it except for him.
46
00:03:01.915 --> 00:03:06.175
And did anybody know what it was? And a few scattered hands went up.
47
00:03:07.360 --> 00:03:09.599
And he said, well, let me explain to you,
48
00:03:10.480 --> 00:03:11.780
why I own Bitcoin.
49
00:03:12.239 --> 00:03:13.439
And he said, and it's because
50
00:03:13.945 --> 00:03:17.565
I I understand why you wouldn't understand it because you all live in America,
51
00:03:18.105 --> 00:03:22.125
and you have a rule of law, and you have, you know, orderly governments.
52
00:03:22.860 --> 00:03:27.680
And in most in most times, you have, you know, low relatively low inflation and a prosperous economy.
53
00:03:28.220 --> 00:03:30.400
And he said, but I'm from Argentina,
54
00:03:30.845 --> 00:03:41.290
and my family's been there a 150 years. And we've been wiped out 4 separate times by the Argentinian government seizing our assets, nationalizing the banks, inflating us out with hyperinflation.
55
00:03:42.069 --> 00:03:43.370
And he said, so Bitcoin
56
00:03:43.750 --> 00:03:45.450
can't be touched by the government.
57
00:03:45.750 --> 00:03:48.010
It's a it's a peer to peer decentralized
58
00:03:48.470 --> 00:03:48.970
independent
59
00:03:49.715 --> 00:03:53.815
network. It's a ledger that records every transaction that's public. It's immutable.
60
00:03:54.355 --> 00:04:03.800
And he said, so the government if you have Bitcoin, the government cannot take it away from you. And he he said, so it's it's an think of it as an insurance policy.
61
00:04:04.500 --> 00:04:11.314
And he went into it and talked about it. And I thought, you know and he talked about putting 1% of your liquid net worth in Bitcoin, and I thought that was sensible.
62
00:04:11.775 --> 00:04:17.235
He laid out what it what it could do if it worked. He he said then that it was very risky because then it was about $200.
63
00:04:17.760 --> 00:04:19.620
But I I bought some then and
64
00:04:19.920 --> 00:04:22.020
I bought a little bit more over time and it became
65
00:04:22.400 --> 00:04:29.104
$500, and then I stopped buying it. And I didn't buy it for years until just the spring of this year. It hit a $66,000
66
00:04:30.685 --> 00:04:31.425
high price.
67
00:04:31.805 --> 00:04:33.985
And then in 4 weeks, it was in half.
68
00:04:34.639 --> 00:04:37.060
Now Bitcoin has gone up on average a 170%
69
00:04:37.440 --> 00:04:39.220
a year for the last 11 years.
70
00:04:39.600 --> 00:04:44.555
Now but that's not every year. It's just an average. It's gone down 3 different times by more than 80%.
71
00:04:45.414 --> 00:04:57.090
So that's that is, you know, a very volatile and therefore very dangerous if you're especially if you're levered. You can be if you're on some of these exchanges. They'll loan you 50 to 1 on on your Bitcoin.
72
00:04:57.550 --> 00:04:58.050
But
73
00:04:58.865 --> 00:05:05.365
each time it's been stopped at around the 80 low eighties level, and it's come back. And this this time, I started buying it again at $30,000
74
00:05:05.985 --> 00:05:06.965
down from 66.
75
00:05:07.570 --> 00:05:08.310
And my reasoning was
76
00:05:09.010 --> 00:05:28.060
there's a lot more people using it now. There's a lot more money going into it in the venture capital world. There are a lot of people who are skeptics who are now at least, trying it out. And, and I thought maybe maybe 50% is a good stopping point for it. But if it goes about down 80 or 85, I'll buy it all the way down. Well, it did stop right around 50% and slowly started its way
77
00:05:28.680 --> 00:05:31.979
back up again. But I I bought a fair amount, at, you know, at the $30,000
78
00:05:32.440 --> 00:05:35.775
range and have been adding to various Bitcoin related,
79
00:05:36.715 --> 00:05:38.255
investments since then.
80
00:06:11.675 --> 00:06:13.615
Happy Bitcoin Tuesday, freaks.
81
00:06:13.915 --> 00:06:16.575
It's your boy Odell here for Citadel dispatch
82
00:06:17.680 --> 00:06:24.900
50. It's been 50 Citadel Dispatches. Let's fucking go. I hope you guys appreciated the little cameo by my dogs,
83
00:06:25.680 --> 00:06:27.105
during that intro clip.
84
00:06:27.745 --> 00:06:33.845
City of Dispatch is an interactive live show about Bitcoin distributed systems, privacy, and open source software.
85
00:06:36.060 --> 00:06:40.720
I want to do a quick shout out to all the supporters of the show who keep this show,
86
00:06:41.500 --> 00:06:45.280
ad free and sponsor free, focused purely on actionable Bitcoin discussion.
87
00:06:46.215 --> 00:06:49.995
You guys make this show possible, and I really do appreciate all the support.
88
00:06:50.695 --> 00:06:56.210
The easiest way to support the show is via podcasting 2 point o apps. My two favorite are fountain podcasts
89
00:06:56.750 --> 00:06:57.889
and Breeze Wallet.
90
00:06:58.349 --> 00:07:09.545
You simply download the app, load it up with sats, search for serial dispatch, and then while you listen, to the podcast, you're able to stream Sats directly to my note. It's really fucking cool.
91
00:07:10.889 --> 00:07:13.470
Literally, any day of the week, I can just sign in.
92
00:07:13.849 --> 00:07:25.115
I can just open up my my Bitcoin node, and I just see a ton of I just I just see SAP payments coming in, you know, 3 sats per minute, 5 sats per minute, 20 sats per minute,
93
00:07:25.575 --> 00:07:27.515
just streaming into my node. It's really
94
00:07:27.990 --> 00:07:31.050
really cool, rewarding experience to to see that happen.
95
00:07:32.070 --> 00:07:33.290
And also, as always,
96
00:07:33.590 --> 00:07:37.610
huge shout out to the freaks who join us in the live chat every week.
97
00:07:38.345 --> 00:07:42.445
You can access the live chat through the Twitter, YouTube, and Twitch streams.
98
00:07:44.265 --> 00:07:45.165
You can also
99
00:07:45.545 --> 00:07:45.785
view
100
00:07:47.150 --> 00:07:51.650
this is the first little dispatch that you're able to view it directly on bitcoin tv.com
101
00:07:51.950 --> 00:07:54.050
as well. Unfortunately, if you participate
102
00:07:55.095 --> 00:07:59.675
in the livestream through Bitcoin TV, you cannot actually be a part of the live chat.
103
00:08:00.775 --> 00:08:05.000
Gonna try and figure out a way to to make that work, but it is an option now.
104
00:08:05.800 --> 00:08:06.620
And as always,
105
00:08:07.000 --> 00:08:11.180
you can listen to the podcast, on your favorite podcasting app,
106
00:08:11.560 --> 00:08:13.980
by just searching Citadel Dispatch or
107
00:08:14.305 --> 00:08:15.845
watching the archives on bitcointv.com,
108
00:08:17.025 --> 00:08:18.405
YouTube, and Twitch.
109
00:08:19.025 --> 00:08:20.305
So with all that said,
110
00:08:20.785 --> 00:08:24.360
this is an episode that I am very excited about.
111
00:08:24.980 --> 00:08:26.680
It should be a really fun conversation.
112
00:08:27.380 --> 00:08:28.200
We have
113
00:08:28.580 --> 00:08:30.920
long time many time guest,
114
00:08:31.625 --> 00:08:34.285
Open Arms here with us. Open Arms, how's it going?
115
00:08:35.225 --> 00:08:37.645
Ohio. It's, honored to be here again.
116
00:08:38.870 --> 00:08:41.589
The honor is all mine. Thank you for joining us. And,
117
00:08:42.630 --> 00:08:43.610
we have Statikus,
118
00:08:44.310 --> 00:08:46.970
lead maintainer of the raspi bolt project here.
119
00:08:47.355 --> 00:08:48.975
The focus of today's conversation
120
00:08:49.355 --> 00:08:53.694
will be Bitcoin nodes and specifically the raspi bolt project. How's it going, Staticus?
121
00:08:54.555 --> 00:08:56.415
Hey, Matt. It's going great. Thanks.
122
00:08:57.149 --> 00:08:57.649
Cheers.
123
00:08:57.950 --> 00:09:03.970
Well, let's fucking do this. So where do you guys wanna start? What is the raspybold project, and why should people care?
124
00:09:05.685 --> 00:09:09.144
I guess I can open with that one. So
125
00:09:09.445 --> 00:09:11.545
to understand where the Raspberry Bolt
126
00:09:12.404 --> 00:09:13.225
comes from,
127
00:09:14.870 --> 00:09:15.449
I think
128
00:09:15.829 --> 00:09:19.850
it's important to realize that it's it's it's been my personal project
129
00:09:20.310 --> 00:09:21.370
for a long time.
130
00:09:21.990 --> 00:09:23.610
So it's basically me
131
00:09:24.165 --> 00:09:25.705
documenting my own learnings.
132
00:09:26.405 --> 00:09:31.705
This is why it started out as a medium article back in the days, like, I don't know, 2017
133
00:09:32.165 --> 00:09:32.905
or so,
134
00:09:33.730 --> 00:09:35.030
how to set up
135
00:09:36.770 --> 00:09:40.230
a bitcoin full node with lightning on a Raspberry Pi.
136
00:09:41.145 --> 00:09:45.005
So back then, there was that wasn't really a thing. So I just
137
00:09:45.385 --> 00:09:48.605
tried to figure it out myself, had some other
138
00:09:49.030 --> 00:09:52.890
articles. Damien Me, for example, had some cool stuff online.
139
00:09:53.830 --> 00:09:57.210
But it just grew from there. I moved it over to GitHub,
140
00:09:59.464 --> 00:10:00.285
started answering
141
00:10:00.904 --> 00:10:04.125
issues and pull requests, all that stuff.
142
00:10:04.584 --> 00:10:06.045
So it's still a guide.
143
00:10:06.819 --> 00:10:09.560
It's not something you can download. It's really,
144
00:10:10.500 --> 00:10:12.120
something you do yourself.
145
00:10:13.220 --> 00:10:13.720
But
146
00:10:14.665 --> 00:10:15.165
it's,
147
00:10:15.704 --> 00:10:17.644
I think, a pretty decent
148
00:10:19.464 --> 00:10:20.605
reference guide
149
00:10:20.985 --> 00:10:23.620
how to set up the Raspberry Pi
150
00:10:24.160 --> 00:10:26.339
Bitcoin full node you want to have
151
00:10:26.800 --> 00:10:28.180
and build yourself.
152
00:10:31.045 --> 00:10:31.545
So
153
00:10:32.805 --> 00:10:33.365
we had
154
00:10:34.725 --> 00:10:35.945
I think we've had,
155
00:10:37.190 --> 00:10:38.970
I mean, I had open arms on
156
00:10:39.670 --> 00:10:40.970
the show to discuss.
157
00:10:41.750 --> 00:10:46.085
We had a big panel with a bunch of the leading node project implementations
158
00:10:46.465 --> 00:10:47.365
in terms of
159
00:10:49.585 --> 00:10:51.905
these actual dedicated 247 nodes,
160
00:10:53.330 --> 00:10:59.270
that you run on dedicated hardware, oftentimes Raspberry Pi, sometimes, you know, other single board chips.
161
00:11:01.045 --> 00:11:03.225
We had that. We also had,
162
00:11:04.805 --> 00:11:06.585
Nix Bitcoin on separately.
163
00:11:07.525 --> 00:11:10.005
So the freaks are very much aware of,
164
00:11:10.570 --> 00:11:14.269
this this concept of running a, you know, a a 247
165
00:11:14.649 --> 00:11:15.709
Bitcoin node,
166
00:11:16.649 --> 00:11:17.550
on a
167
00:11:17.930 --> 00:11:18.990
dedicated machine
168
00:11:19.875 --> 00:11:21.095
that is cheap hardware.
169
00:11:22.755 --> 00:11:23.255
So
170
00:11:24.035 --> 00:11:30.600
I'm I'm looking forward to diving deep in the weeds here. I I think, you know, most of the freaks are prepared for that and enjoy that type of conversation.
171
00:11:31.540 --> 00:11:33.320
But before we get there, I mean,
172
00:11:34.180 --> 00:11:37.560
it is almost it has been normalized. Somehow, it's been normalized,
173
00:11:39.205 --> 00:11:46.585
in a good way, this this concept. But when Raspberry Bolt when you first started working on on the Raspberry Bolt project,
174
00:11:47.829 --> 00:11:48.230
I
175
00:11:48.630 --> 00:11:50.570
was was it the first main,
176
00:11:52.470 --> 00:11:55.529
I guess, guide or project to run a raspi
177
00:11:56.584 --> 00:11:57.084
lightning
178
00:11:58.985 --> 00:12:01.404
node? I I think in a way you can say that.
179
00:12:02.345 --> 00:12:03.324
There are
180
00:12:04.310 --> 00:12:04.810
articles
181
00:12:05.350 --> 00:12:10.890
back then, but that were more like one time things. So not ongoing projects.
182
00:12:11.750 --> 00:12:12.250
And
183
00:12:13.655 --> 00:12:14.875
I I did that myself,
184
00:12:15.335 --> 00:12:19.755
on medium. But I think as soon as I moved it over to GitHub and,
185
00:12:20.135 --> 00:12:22.320
like, did continuous improvements,
186
00:12:22.699 --> 00:12:23.199
updates,
187
00:12:24.620 --> 00:12:30.320
seem to it that all the download links are always up to date. I think back then, it was the first
188
00:12:31.965 --> 00:12:32.465
live
189
00:12:32.845 --> 00:12:34.705
guide, if you can say that.
190
00:12:35.245 --> 00:12:37.425
That was always up to date and actually
191
00:12:38.500 --> 00:12:43.399
started to to get some, like, people involved and follow follow along.
192
00:12:47.435 --> 00:12:52.335
I mean, we've come we've come tremendously far. Did you did you say when you started it?
193
00:12:54.370 --> 00:12:58.790
So I I tried to think back. I'm not quite sure, but I think,
194
00:12:59.410 --> 00:13:05.255
I started tinkering. So I've been working with Raspberry Pis for a long time for my
195
00:13:05.795 --> 00:13:10.190
streaming client for retro Pis for console games and stuff like that.
196
00:13:11.310 --> 00:13:12.530
So I was basically
197
00:13:13.070 --> 00:13:20.055
pissed off that every time I wanted to connect to pit Bitcoin core, I first had to sync, like, I don't know, hours
198
00:13:20.515 --> 00:13:21.395
until I could,
199
00:13:22.515 --> 00:13:25.575
verify my own transactions. So it came naturally
200
00:13:26.115 --> 00:13:29.095
to this concept of a 247 note,
201
00:13:29.709 --> 00:13:32.690
and building on a Raspberry Pi for me was pretty natural.
202
00:13:33.550 --> 00:13:36.209
And that was also, I think, in the summer of 2017,
203
00:13:36.990 --> 00:13:41.635
like, during the block size wars. Like, there was UASF, the Node Fix movement.
204
00:13:42.255 --> 00:13:45.315
And that also got me, like, thinking and appreciating
205
00:13:46.095 --> 00:13:46.755
a lot
206
00:13:47.550 --> 00:13:48.530
how important
207
00:13:48.990 --> 00:13:53.170
running your own Bitcoin node is for keeping Bitcoin decentralized.
208
00:13:54.110 --> 00:13:59.925
I think this is why I also started to dig deeper into it and all also started to publicly,
209
00:14:00.625 --> 00:14:01.845
document my learnings.
210
00:14:05.710 --> 00:14:07.250
Yeah. I mean so
211
00:14:08.270 --> 00:14:08.930
I guess
212
00:14:09.950 --> 00:14:12.690
yeah. So, I mean, it's been about probably, like, 3 years,
213
00:14:13.070 --> 00:14:13.570
since
214
00:14:13.895 --> 00:14:15.915
Raspberry Bolt, first started.
215
00:14:16.695 --> 00:14:23.410
Yeah. I guess so. I mean, back then, it was like I think it started pretty quickly with lightning, but it was still on test net
216
00:14:24.209 --> 00:14:26.709
then. And I actually started it with Eclair.
217
00:14:30.290 --> 00:14:36.815
But I think LND then was the 1st lightning implementation that switched to mainnet. So
218
00:14:37.675 --> 00:14:38.415
I basically
219
00:14:38.875 --> 00:14:39.375
just
220
00:14:39.950 --> 00:14:41.490
kicked out Eclair and,
221
00:14:42.190 --> 00:14:43.890
switched to LND back then.
222
00:14:45.070 --> 00:14:51.214
That's interesting. I wonder if that I mean, that's gotta be one of the main reasons LND became such a dominant implementation. Right?
223
00:14:51.515 --> 00:14:53.615
That it was just first to go mainnet.
224
00:14:54.714 --> 00:14:59.720
Yeah. And I guess for all the web devs, it's also just much more, like,
225
00:15:00.820 --> 00:15:04.840
common to use WebSockets. So if if you look at c lightning,
226
00:15:05.394 --> 00:15:06.675
you use, like,
227
00:15:07.154 --> 00:15:18.040
Linux sockets and stuff like that. I think it's much harder to build a web application on top of that. And LND just was, like, more familiar, I think, to whole to the whole deaf community.
228
00:15:18.820 --> 00:15:19.320
Cool.
229
00:15:21.445 --> 00:15:23.945
So open arms, where do you think we should go from here?
230
00:15:25.845 --> 00:15:30.825
No. I I I loved loved the deep dive in history. I just, there is a link
231
00:15:31.670 --> 00:15:37.690
I I posted in the chat about, the history of lightning from brainstorm to beta. So, basically, it goes
232
00:15:38.795 --> 00:15:39.375
as it
233
00:15:39.835 --> 00:15:40.335
as
234
00:15:40.795 --> 00:15:43.375
it goes through the history, it's basically 2018,
235
00:15:43.915 --> 00:15:45.055
March 20
236
00:15:45.675 --> 00:15:46.760
28th when,
237
00:15:47.800 --> 00:15:52.060
when multiple implementations are going to main net and and there is
238
00:15:52.840 --> 00:15:55.340
a transaction between c lightning and lnd.
239
00:15:55.675 --> 00:15:58.575
So that's kind of the start of of of the main net
240
00:15:59.195 --> 00:15:59.695
network.
241
00:16:00.635 --> 00:16:01.935
And have you know that
242
00:16:02.779 --> 00:16:10.880
the test net was very active before then and obviously before, like, even Segwit activated. And the recipe board was then there to kind of
243
00:16:12.774 --> 00:16:17.274
try it out and buy a blocaccino, as you say in the guide. I think it's right here.
244
00:16:17.654 --> 00:16:20.475
So Fantastic. So that's been, yeah, that's been something
245
00:16:21.900 --> 00:16:26.000
I've been looking at during that period. And then, you know, pretty much
246
00:16:26.620 --> 00:16:29.975
this summer after or, like, you know, like, after March,
247
00:16:30.435 --> 00:16:33.175
I did build the did build the recipe both myself.
248
00:16:33.635 --> 00:16:36.455
And, looking at my GitHub, I I fold fold
249
00:16:36.835 --> 00:16:46.335
the guide and the, like, the extras repo in, like, in beginning of August 2018. So splitting up it's been there and already the community was building then.
250
00:16:46.895 --> 00:16:52.335
Mhmm. So it's, it's been great. All the reckless hashtag I can remember. And, also, I was,
251
00:16:52.895 --> 00:17:00.930
you know, losing some channels without any kind of backup then, and, you know, it's just because of a power glitch and stuff like that.
252
00:17:01.310 --> 00:17:03.170
So it was definitely reckless indeed.
253
00:17:04.095 --> 00:17:06.915
Definitely. And I remember that beginning of 2018,
254
00:17:07.215 --> 00:17:09.075
it was pretty easy to already
255
00:17:09.455 --> 00:17:09.955
switch
256
00:17:10.370 --> 00:17:15.270
to main net if you wanted to, but you had to do some code changes and compile it yourself.
257
00:17:15.730 --> 00:17:19.670
And the developers really backed the community not to do that.
258
00:17:20.455 --> 00:17:23.035
And I also respected that and did not
259
00:17:23.414 --> 00:17:25.275
provide instructions on how
260
00:17:26.054 --> 00:17:27.835
to go on main net before,
261
00:17:28.135 --> 00:17:28.520
like,
262
00:17:29.080 --> 00:17:32.860
the developers gave their their go ahead, and they felt comfortable
263
00:17:33.800 --> 00:17:37.980
with, like, being only reckless, not reckless reckless.
264
00:17:38.404 --> 00:17:39.044
Do you
265
00:17:39.365 --> 00:17:47.945
well, I guess, first off, for the the freaks because I already put it up on the screen for those watching the video. But for the freaks listening into the podcast feeds,
266
00:17:49.740 --> 00:17:50.960
you can it's raspibolt.org.
267
00:17:52.620 --> 00:17:54.320
Very easy to remember domain.
268
00:17:56.305 --> 00:17:59.525
All the materials are neatly laid out on that website,
269
00:17:59.985 --> 00:18:02.085
so go check that out after the show.
270
00:18:04.190 --> 00:18:06.210
Yeah. I mean, the whole the whole reckless
271
00:18:06.990 --> 00:18:07.490
meme
272
00:18:07.950 --> 00:18:09.570
when lightning went mainnet,
273
00:18:11.470 --> 00:18:12.450
seemed very
274
00:18:14.575 --> 00:18:19.475
counter to Bitcoin in a lot of ways. I mean, I I think Bitcoin is always very conservative,
275
00:18:19.935 --> 00:18:20.595
kind of,
276
00:18:22.400 --> 00:18:25.860
basically the opposite of reckless in terms of the way
277
00:18:26.799 --> 00:18:30.485
people treat using Bitcoin or at least the way the more
278
00:18:31.505 --> 00:18:34.565
enthusiast community or hardcore community treats using Bitcoin.
279
00:18:36.705 --> 00:18:39.684
Do you guy you guys still think that lightning is reckless?
280
00:18:40.290 --> 00:18:41.429
Like, do you think that
281
00:18:42.370 --> 00:18:46.309
is still the case? Are we still, like, almost in a beta mode of lightning?
282
00:18:49.414 --> 00:18:52.235
Personally, I don't really think so. I mean,
283
00:18:52.774 --> 00:19:04.009
of course, if you don't really know what you're doing and setting up a note without the basic understanding what you're doing and putting, like, 1,000 of dollars in that, I guess that's still reckless.
284
00:19:04.630 --> 00:19:05.130
But
285
00:19:05.675 --> 00:19:06.975
if you have some, like,
286
00:19:07.435 --> 00:19:08.815
good knowledge on
287
00:19:09.195 --> 00:19:10.495
how to run a server
288
00:19:11.035 --> 00:19:12.015
and how to,
289
00:19:12.555 --> 00:19:13.055
like,
290
00:19:14.059 --> 00:19:19.919
run software in a secure and hardened way, I think, Lightning is pretty stable.
291
00:19:21.875 --> 00:19:22.855
I mean, I know
292
00:19:23.395 --> 00:19:28.535
I don't think I passed the point yet where I mean, when I first started using Lightning, I kinda just,
293
00:19:30.260 --> 00:19:36.840
you know, started fucking around with it and playing around with it. And I kinda just operated under the assumption I was gonna lose my money.
294
00:19:37.215 --> 00:19:40.915
And I don't know if I still I I don't know if I've left that
295
00:19:41.375 --> 00:19:43.235
assumption yet. I think I still
296
00:19:44.770 --> 00:19:48.630
operate under the assumption that basically any funds I have on my Lightning Nodes,
297
00:19:49.250 --> 00:19:50.630
can be lost at will.
298
00:19:51.865 --> 00:19:55.965
Yeah. I guess that's that's a good starting point. I think you can build from that.
299
00:19:56.665 --> 00:19:58.105
I mean, because what we had the
300
00:19:59.210 --> 00:20:04.110
I was presenting at the HRF Oslo Freedom Forum earlier this year
301
00:20:06.195 --> 00:20:07.735
or earlier last year.
302
00:20:08.755 --> 00:20:10.615
And when I got off stage,
303
00:20:11.394 --> 00:20:12.774
I think Stefan Lovera
304
00:20:13.750 --> 00:20:17.690
came up to me and and said to me, he's like, Matt, did you see that lightning vulnerability?
305
00:20:18.950 --> 00:20:20.330
And, like, when you read
306
00:20:20.755 --> 00:20:26.695
the vulnerability disclosure, it almost made it seem like people could just drain funds at will if you had, like, a malicious peer.
307
00:20:29.200 --> 00:20:30.419
And it didn't happen.
308
00:20:31.279 --> 00:20:35.620
Like, one of my nodes has, you know, 200 channels or something. Like, I don't know all the peers,
309
00:20:36.715 --> 00:20:41.695
and it didn't happen. But I remember the first thing I was like, oh, well, I either lost my money or I didn't.
310
00:20:45.650 --> 00:20:50.630
Yeah. I guess that's a scary thing if you have, like, really lots of funds on there.
311
00:20:51.409 --> 00:20:59.895
But, I mean, in the end, it's a hot wallet. Right? So Yeah. That could also happen with if you have a Bitcoin on chain hot wallet somewhere,
312
00:21:00.690 --> 00:21:02.470
if there's any vulnerability
313
00:21:02.770 --> 00:21:05.510
anywhere on the system, your funds are always
314
00:21:06.130 --> 00:21:07.350
somehow at risk.
315
00:21:08.135 --> 00:21:10.795
So I think that's one of the main drawbacks of lightning.
316
00:21:11.255 --> 00:21:16.795
But it's okay. It's a different use case. And it's just important to know that
317
00:21:17.140 --> 00:21:17.640
having
318
00:21:18.260 --> 00:21:21.160
a lot of money in a hot wallet connected to the Internet
319
00:21:21.780 --> 00:21:23.799
is probably not for your life savings.
320
00:21:24.725 --> 00:21:29.225
I mean, it's definitely not. Right? You have your savings and your cold storage, and then,
321
00:21:30.644 --> 00:21:35.770
this is almost either spending cash or operating flow if you're running a routing node.
322
00:21:36.070 --> 00:21:36.570
Exactly.
323
00:21:37.990 --> 00:21:39.450
So, I mean, I personally
324
00:21:39.830 --> 00:21:41.530
if if the freaks go back, I mean,
325
00:21:41.835 --> 00:21:44.655
dispatch is is has almost been every week.
326
00:21:45.434 --> 00:21:46.655
Took a couple breaks,
327
00:21:47.195 --> 00:21:48.015
last year.
328
00:21:49.720 --> 00:21:55.900
As I mean, if you do basic math, I mean, it's still dispatched 50 and started at the very end of last year.
329
00:21:57.355 --> 00:21:59.295
And a rabbit hole recap is every week.
330
00:21:59.675 --> 00:22:04.575
So the freaks are and I admit this every day. I mean, the freaks are very aware that I completely
331
00:22:06.475 --> 00:22:07.135
you know,
332
00:22:07.580 --> 00:22:12.080
I was completely wrong about a sustained high fee market. I thought we'd
333
00:22:12.620 --> 00:22:16.000
see a sustained high fee market, sooner rather than later.
334
00:22:16.365 --> 00:22:21.265
I still think I expect it going forward, but, I mean, as you can see, I have a live look of,
335
00:22:22.845 --> 00:22:24.145
mempool dot space
336
00:22:24.780 --> 00:22:28.880
on the screen right now, and 1 separate byte is confirming next block.
337
00:22:29.820 --> 00:22:38.095
Does what how how do you how do you view the fee market? How do you view do you think fees will go up? How do you when you talk to people about,
338
00:22:38.715 --> 00:22:40.174
the advantages of lightning,
339
00:22:40.700 --> 00:22:46.320
do you square that with the fact that you can just do one sapro byte and get in the next block?
340
00:22:50.315 --> 00:22:50.815
So
341
00:22:51.195 --> 00:22:58.000
I guess there are different use cases to Bitcoin. Like, Bitcoin is something else for everybody who joins
342
00:22:58.300 --> 00:22:58.960
the network.
343
00:22:59.740 --> 00:23:04.480
And I think lightning bought us a lot of time in term in terms of,
344
00:23:05.355 --> 00:23:05.855
like,
345
00:23:06.315 --> 00:23:08.495
mempool and block space
346
00:23:09.115 --> 00:23:09.855
just because
347
00:23:10.875 --> 00:23:13.370
people that now use Lightning, they
348
00:23:14.410 --> 00:23:16.110
basically don't take up any,
349
00:23:17.130 --> 00:23:17.870
block space.
350
00:23:18.250 --> 00:23:21.470
So I think that suppresses the the fees a lot.
351
00:23:21.885 --> 00:23:24.385
But there are other use cases like sending
352
00:23:25.005 --> 00:23:25.505
funds
353
00:23:26.125 --> 00:23:35.730
to to an exchange to if you want to sell or withdraw them into your cold storage. And I think that's probably more the case if you're, like, in a really FOMO driven
354
00:23:36.350 --> 00:23:38.370
hype cycle. So I would still
355
00:23:40.095 --> 00:23:40.595
expect
356
00:23:41.855 --> 00:23:45.075
fees to rise during, like, peak. Like, 2017
357
00:23:45.455 --> 00:23:48.195
was insane. I think I paid up to $30
358
00:23:48.575 --> 00:23:49.075
once,
359
00:23:49.540 --> 00:23:50.680
but only once.
360
00:23:52.100 --> 00:23:53.880
But I think that can happen again,
361
00:23:54.260 --> 00:23:55.880
but we're we're buying time
362
00:23:56.340 --> 00:23:57.480
with lightning, definitely.
363
00:23:58.794 --> 00:24:03.855
Yeah. I mean, I tend to one of the ways I tend to frame it is is almost like a release valve
364
00:24:04.394 --> 00:24:07.695
in times of high fee pressure, and it kind of could
365
00:24:08.620 --> 00:24:10.720
provide the network with the ability to,
366
00:24:12.860 --> 00:24:20.785
not stay at a high fee level for as long as it would otherwise. But one of the key aspects here is, I mean, every Lightning channel is an open and
367
00:24:21.165 --> 00:24:22.705
requires an open and close,
368
00:24:23.165 --> 00:24:25.745
which is an on which is 2 on chain transactions.
369
00:24:26.590 --> 00:24:29.410
So if you're not prepared for that ahead of time,
370
00:24:31.710 --> 00:24:33.970
you're you're not going to get the fee savings
371
00:24:34.684 --> 00:24:42.225
of Lightning in a high fee environment. If we have a high fee environment in a week or 2 weeks, not that I'm saying that we will, we probably will not,
372
00:24:43.530 --> 00:24:49.550
That's not the time to really open the channels. The time to open in the channels is when it's 1 separate byte. Mhmm.
373
00:24:50.090 --> 00:24:51.790
OpenOps, do you have any thoughts here?
374
00:24:53.154 --> 00:25:00.860
Well, I think it's it's a good approach to think of using lightning as a saving approach because it's definitely not a a way to make money.
375
00:25:01.900 --> 00:25:02.720
If you have
376
00:25:03.500 --> 00:25:04.000
something
377
00:25:04.460 --> 00:25:06.320
some use for it, then,
378
00:25:06.780 --> 00:25:08.535
you know, open channels. But I
379
00:25:09.015 --> 00:25:12.475
I I don't really believe in this kind of preemptively
380
00:25:14.535 --> 00:25:16.120
working towards the
381
00:25:16.520 --> 00:25:20.700
or or preparing for the high fee market. Because to be honest, even then,
382
00:25:22.120 --> 00:25:24.755
if you want to send a lightning transaction, you would just
383
00:25:25.235 --> 00:25:28.295
just a Bitcoin transaction. You would just think twice that,
384
00:25:28.755 --> 00:25:30.295
should I open a channel rather?
385
00:25:30.675 --> 00:25:40.549
Does this beer have a node? Does this exchange by then have a node? Does this, you know, friend of mine or this shop have a node? And if I would stay on chain,
386
00:25:41.395 --> 00:25:44.295
I would just rather open a channel then. And then,
387
00:25:45.235 --> 00:25:53.640
you know, you have the fee savings for the next payment because the next one you will be able to to spend on lightning either to that shop or peer
388
00:25:54.180 --> 00:25:56.600
or through the lightning network to anywhere else.
389
00:25:58.775 --> 00:26:01.595
Right. Because, like, at its core, Lightning is essentially,
390
00:26:02.775 --> 00:26:05.860
batch Bitcoin transactions. So instead of sending one transaction,
391
00:26:09.220 --> 00:26:09.720
Exactly.
392
00:26:10.020 --> 00:26:12.440
Yeah. So you still get fee savings in that situation.
393
00:26:14.115 --> 00:26:15.414
Okay. Cool. I think
394
00:26:15.794 --> 00:26:17.495
the bite lightning already,
395
00:26:19.715 --> 00:26:25.670
helps us scale Bitcoin a lot, But, of course, it's it's it's not done scaling. Right?
396
00:26:26.050 --> 00:26:28.310
So once we're like,
397
00:26:29.065 --> 00:26:35.804
dual funded channels will become the norm or channel factories where you can open, like, one big channel with multiple peers.
398
00:26:36.270 --> 00:26:39.330
Something like that, I think, would probably be the next step
399
00:26:40.110 --> 00:26:41.730
of lightning scaling.
400
00:26:42.270 --> 00:26:49.075
And I'm not sure what comes after that, but I guess we'll I think Andreas Antonopoulos once said we're constantly
401
00:26:49.615 --> 00:26:50.115
not
402
00:26:50.575 --> 00:26:54.995
failing to scale or something like that. So it's always, like, pushing the boundaries,
403
00:26:55.630 --> 00:26:58.850
like, a few weeks or a few years in front of us.
404
00:27:01.630 --> 00:27:07.715
Oh, yeah. I mean, a 100%. I mean, I I like to remind the freaks that, you know, most of the things that will
405
00:27:08.255 --> 00:27:08.995
be developed,
406
00:27:10.175 --> 00:27:14.035
in Bitcoin land, I don't even think we can really fathom them yet.
407
00:27:15.360 --> 00:27:20.180
I don't think we should rest on that and just assume that will be the case, but at the same time,
408
00:27:20.720 --> 00:27:23.060
we should be humble enough to realize that,
409
00:27:25.025 --> 00:27:29.125
our small human brains can't really understand the implications so far ahead of time.
410
00:27:30.465 --> 00:27:34.165
I know I've been caught off guard way, way, way many times.
411
00:27:37.330 --> 00:27:40.070
So open arms, where do you think we should go next in this conversation?
412
00:27:45.065 --> 00:27:50.205
So we went through the history, and we heard about the rest of the world's history. I mean, because
413
00:27:50.530 --> 00:27:54.210
get get into the details of it a bit. I mean, should we just,
414
00:27:54.850 --> 00:27:55.590
skim through
415
00:27:56.210 --> 00:27:58.554
what we do when we are setting
416
00:27:59.095 --> 00:28:00.394
up a lightning node.
417
00:28:00.934 --> 00:28:03.434
Let's do it. Yeah. Yeah. Sure.
418
00:28:03.735 --> 00:28:06.134
I mean, maybe taking a step back and,
419
00:28:06.830 --> 00:28:10.690
giving a quick overview what the rest of the bolt is or is not
420
00:28:10.990 --> 00:28:11.490
versus
421
00:28:11.790 --> 00:28:13.410
other node implementations
422
00:28:14.505 --> 00:28:17.965
could help and then dive into what how it actually works.
423
00:28:20.505 --> 00:28:23.005
Yeah. Let's do that. So so what what is,
424
00:28:24.440 --> 00:28:30.059
you know, I've had the Raspberry Pi Blitz team on. I've had Roni Dojo team on. I've had
425
00:28:30.935 --> 00:28:32.475
pretty much everyone but Umbralon.
426
00:28:33.735 --> 00:28:38.235
How is how is Raspberry Bolt different than, let's say, Raspberry Blitz?
427
00:28:39.039 --> 00:28:40.799
Cool. Yeah. So let me,
428
00:28:41.519 --> 00:28:46.980
preface that with that I fear for every node that joins the network. I think
429
00:28:47.335 --> 00:28:48.955
this is our all shared
430
00:28:49.575 --> 00:28:50.075
goal.
431
00:28:50.455 --> 00:28:54.235
The more people around their own node and actually use it, the better.
432
00:28:56.030 --> 00:28:56.190
With
433
00:28:56.910 --> 00:28:58.610
in in light of the the differences.
434
00:28:59.150 --> 00:29:01.010
So I think the recipe vault
435
00:29:01.310 --> 00:29:02.290
is the only
436
00:29:03.185 --> 00:29:06.405
project. So to say that it's just a guide.
437
00:29:06.865 --> 00:29:08.485
So there's nothing to download.
438
00:29:08.865 --> 00:29:09.845
It's a website,
439
00:29:10.545 --> 00:29:13.000
and it's it's getting pretty big.
440
00:29:13.540 --> 00:29:14.040
And
441
00:29:14.580 --> 00:29:16.680
it basically takes you by the hand
442
00:29:17.700 --> 00:29:19.960
and lays out command by command
443
00:29:20.665 --> 00:29:21.485
how you can
444
00:29:22.745 --> 00:29:23.965
set up your own
445
00:29:24.665 --> 00:29:25.965
do everything yourself
446
00:29:26.425 --> 00:29:26.925
Bitcoin
447
00:29:27.545 --> 00:29:31.960
full node with lightning, with with many bonus guides and stuff like that.
448
00:29:32.500 --> 00:29:38.675
But in the end, it's it's not only about having the node in the end. It's also about
449
00:29:39.375 --> 00:29:39.875
knowing
450
00:29:40.735 --> 00:29:43.715
how it's built, how how you set it up yourself,
451
00:29:44.335 --> 00:29:44.835
and
452
00:29:45.570 --> 00:29:53.510
not trusting someone else to just, like, download an image and and run it. So it's it's it's as much a learning experience
453
00:29:55.845 --> 00:29:57.065
as running a node.
454
00:29:57.765 --> 00:30:02.905
And I guess it's not for everybody, and it doesn't need to be because I I'm always amazed how
455
00:30:03.279 --> 00:30:03.779
many
456
00:30:04.320 --> 00:30:04.820
projects
457
00:30:05.520 --> 00:30:09.779
there are out there. And it seems like every project has found its niche.
458
00:30:10.135 --> 00:30:12.794
So the recipe vault is really, like, more about learning.
459
00:30:13.335 --> 00:30:25.010
And it's it's pretty universal, so it only uses step in commands. So you can not only use it on a Raspberry Pi, you can reuse it on a virtual private server, on a virtual machine. Everything that can run Debian
460
00:30:25.549 --> 00:30:26.530
is able to
461
00:30:26.904 --> 00:30:27.725
run the Respibault.
462
00:30:30.184 --> 00:30:32.044
And then, of course, like the Respibilts,
463
00:30:32.985 --> 00:30:35.325
Rud Sol and his team, like,
464
00:30:36.440 --> 00:30:36.940
as
465
00:30:37.320 --> 00:30:37.820
mentioned,
466
00:30:39.960 --> 00:30:43.340
they basically built on top of the recipe vault,
467
00:30:43.880 --> 00:30:44.380
but,
468
00:30:45.325 --> 00:30:50.465
with the focus on lightning hack days, which full mode does quite quite often.
469
00:30:52.525 --> 00:31:00.429
And they basically automated the whole thing, which is awesome. In the beginning, it was just like the recipe vault automated with shell scripts,
470
00:31:00.855 --> 00:31:08.235
but that was just the beginning. And now they build, like, awesome stuff on top of that. They they you their own menu system,
471
00:31:09.460 --> 00:31:10.900
many, many options you can,
472
00:31:12.260 --> 00:31:15.480
switch on. But it's still, like, more of a
473
00:31:16.755 --> 00:31:17.655
a hack day.
474
00:31:18.355 --> 00:31:26.750
I think the target audience are are are more, like, people that want to to go down to the command line, understand how it's working, like more tinkerers.
475
00:31:28.650 --> 00:31:31.390
So that's that's like an awesome project. I really,
476
00:31:31.850 --> 00:31:33.390
I also run it myself.
477
00:31:34.835 --> 00:31:41.495
And then, of course, are, like, the more, like, UI focused notes, like Umbrel, my notes, like the Citadel.
478
00:31:44.289 --> 00:31:49.030
These are really, really cool because it allow they allow, like, normies.
479
00:31:49.730 --> 00:31:53.510
Like, I wasn't once as well before I fell down the rabbit hole
480
00:31:54.845 --> 00:32:03.345
So just, like, download an image, put it into the Raspberry Pi, spin it up, and connect your browser, and that's basically it. You're on you're now a sovereign
481
00:32:03.950 --> 00:32:06.050
peer on the Bitcoin blockchain.
482
00:32:07.230 --> 00:32:09.810
And I find this especially important
483
00:32:10.190 --> 00:32:12.905
if you then connect your hardware wallet to it
484
00:32:13.385 --> 00:32:13.885
Because
485
00:32:14.425 --> 00:32:17.805
many projects put it more the focus more on lightning.
486
00:32:18.745 --> 00:32:19.545
But I'm really
487
00:32:20.960 --> 00:32:26.900
for me, that's more like the cherry on top. I care much more about the underlying blockchain and validating
488
00:32:27.935 --> 00:32:28.915
my own transactions
489
00:32:29.295 --> 00:32:33.475
on chain with my hardware wallet directly on my own full node.
490
00:32:34.655 --> 00:32:40.440
So that might be another difference. The the Raspberry Bolt really builds the the on chain part first
491
00:32:41.700 --> 00:32:44.920
and lightning comes on top while other projects
492
00:32:45.325 --> 00:32:47.745
basically advertise them as Lightning nodes.
493
00:32:48.205 --> 00:32:51.745
And many didn't even allow you to connect your
494
00:32:52.540 --> 00:32:56.880
harder wallets to them, like through a Electrum server or something like that.
495
00:32:59.235 --> 00:33:02.455
And, yeah, one one last thing like Nix Bitcoin.
496
00:33:03.075 --> 00:33:10.539
I was trying to get more into it. It's it has a steep learning curve, but I really appreciate what the these guys are doing.
497
00:33:12.120 --> 00:33:16.700
Can't really do them justice explaining it. It's just like a super hard and
498
00:33:17.384 --> 00:33:18.205
no compromise
499
00:33:18.825 --> 00:33:19.965
security focused,
500
00:33:22.105 --> 00:33:22.605
reproducibly
501
00:33:23.225 --> 00:33:23.725
built
502
00:33:24.745 --> 00:33:26.044
Bitcoin full note
503
00:33:26.550 --> 00:33:27.050
distribution
504
00:33:27.750 --> 00:33:29.130
built on Nix OS.
505
00:33:29.750 --> 00:33:30.250
So
506
00:33:30.630 --> 00:33:35.485
that's really, really cool to see. And I think if I find the time someday, this
507
00:33:36.025 --> 00:33:39.164
is probably what I'm gonna experiment with next.
508
00:33:40.105 --> 00:33:41.325
Yeah. I mean, I had
509
00:33:43.200 --> 00:33:45.360
some of the guys from Nix Bitcoin on,
510
00:33:45.760 --> 00:33:46.260
cildispatch
511
00:33:46.800 --> 00:33:48.500
42. So that's cildispatch.com/cd42.
512
00:33:52.855 --> 00:33:57.595
If any of the freaks have missed that episode and are interested in going back and listening.
513
00:33:59.095 --> 00:34:01.275
Open Arms, do you have anything to add on there?
514
00:34:02.490 --> 00:34:11.835
By the way, as always, feel free to just jump in. Don't don't feel like I need to be, you know, host host Odell over here. You're you're welcome to jump in at any point.
515
00:34:12.935 --> 00:34:14.555
Right. Thanks. Well,
516
00:34:15.655 --> 00:34:24.980
no. I I I do like the the approach of of of Skye of basing basing everything on on self validating and just going step by step. I've been when I've,
517
00:34:25.440 --> 00:34:26.500
you know, come into,
518
00:34:27.165 --> 00:34:29.265
basically, come into running a full node
519
00:34:29.885 --> 00:34:30.385
through
520
00:34:31.245 --> 00:34:33.885
running a lightning node. So I I've, first of all
521
00:34:35.560 --> 00:34:36.060
well,
522
00:34:36.360 --> 00:34:40.540
wanted to use, like, Electrum and, you know, like, between core as well as
523
00:34:41.800 --> 00:34:48.954
running a lightning node and it I understand that how important that is to get, like, a solid foundation. And then the
524
00:34:50.155 --> 00:35:00.619
I needed to understand how how it is all built up, and this was the guide which I just, you know, kept coming back to. I mean, now there are for example, for Lightning, there is like, the Lightning
525
00:35:01.480 --> 00:35:01.980
Labs
526
00:35:02.440 --> 00:35:06.035
have kind of a node builder's guide or,
527
00:35:06.595 --> 00:35:12.750
similar quite extensive documentation, but how to use l and d itself or how to set it up in in various
528
00:35:13.450 --> 00:35:13.950
environments.
529
00:35:14.490 --> 00:35:14.990
But
530
00:35:16.410 --> 00:35:17.069
that is
531
00:35:18.250 --> 00:35:22.695
basically aimed for, like, an the industrial use. But if you want to sit down yourself,
532
00:35:23.075 --> 00:35:35.289
you would you would start hacking away with with, you know now I have now I need to get into using Linux as an operating system and as I and I was coming from Windows so far. So how do I do this? And then,
533
00:35:35.825 --> 00:35:37.365
you know, there are basic commands
534
00:35:37.984 --> 00:35:39.285
you can use. And
535
00:35:39.585 --> 00:35:50.360
from 0, and I I do this. I tell this from experience. One of my first exposures to using Linux was going through the s p boat guide, and it was just, you know, it was
536
00:35:50.660 --> 00:36:00.225
it was a great drilling point, and I kept coming back to it. Oh, how do I do do this and that? And, you know, there's been just a couple of sentences of explanation just to do it. So,
537
00:36:00.765 --> 00:36:04.580
you know, thanks for that, and and and that is great. And it still remained
538
00:36:05.120 --> 00:36:08.505
this, you know, focus on this approach, which is,
539
00:36:09.785 --> 00:36:11.724
yeah, exactly. It's quite quite unique.
540
00:36:14.184 --> 00:36:17.164
So there are different people coming into into
541
00:36:17.800 --> 00:36:22.540
interacting with Bitcoin. Like, if someone is interested, you know, in it for the technology,
542
00:36:23.160 --> 00:36:25.580
then, you know, they would they would come to learn,
543
00:36:25.905 --> 00:36:28.645
and then this would be the route I would send them send
544
00:36:29.105 --> 00:36:30.165
them down on.
545
00:36:31.585 --> 00:36:34.480
If someone is, you know, like, a big investor,
546
00:36:35.660 --> 00:36:40.880
coming in with, you know, 1,000,000 of dollars like the gentleman you've seen in the big in the clip in the beginning,
547
00:36:41.515 --> 00:36:43.454
then, you know, I would definitely not
548
00:36:43.835 --> 00:36:47.295
ask them to kind of, okay, let's start typing these comments,
549
00:36:47.595 --> 00:36:48.795
but they would need to be
550
00:36:49.600 --> 00:36:50.900
have a service provided.
551
00:36:51.360 --> 00:36:57.060
But, you know, in a in a way You don't think you don't think Bill Miller should, follow the Raspberry Bolt guide?
552
00:36:57.615 --> 00:36:59.795
Well, I think he should, but he won't.
553
00:37:00.255 --> 00:37:01.075
I don't think,
554
00:37:01.695 --> 00:37:09.970
you know, it it I don't think that would be a suggestion he would want to hear, So it would be not the right thing to say it. Do you think there's an argument for
555
00:37:13.345 --> 00:37:13.845
maybe,
556
00:37:14.385 --> 00:37:16.005
people that started with,
557
00:37:16.944 --> 00:37:17.444
RaspiBlitz
558
00:37:18.145 --> 00:37:22.484
or Ronin Dojo or an Umbral or or something similar to that,
559
00:37:23.760 --> 00:37:30.260
and maybe they're still using it as their main node to also on the side go through RAS by Bolt's guide and
560
00:37:30.925 --> 00:37:37.505
maybe set it up that way so they can understand more about how everything is working under the hood because all of these node implementations are
561
00:37:37.805 --> 00:37:39.500
they have a lot of similarities. Right?
562
00:37:40.700 --> 00:37:44.320
Well, in terms of having the base operating system, it's,
563
00:37:44.620 --> 00:37:51.415
like like, DB and Linux distro based in most, except Ronin Dojo is using Manjaro, which is like Arch.
564
00:37:52.515 --> 00:37:55.815
It's it's it's slightly different. You have slightly different commands
565
00:37:56.359 --> 00:37:57.820
with the same kind of logic.
566
00:38:00.920 --> 00:38:02.220
So I would
567
00:38:02.760 --> 00:38:09.645
definitely recommend everyone to kind of go into it, course through it. And maybe if someone would decide to build,
568
00:38:10.105 --> 00:38:11.005
like, a more
569
00:38:11.465 --> 00:38:13.005
resilient, a bit more serious
570
00:38:13.790 --> 00:38:16.530
node to provide some service maybe or, you know,
571
00:38:17.150 --> 00:38:17.650
serve
572
00:38:18.270 --> 00:38:20.930
the needs of, you know, Billy Uncle Jim,
573
00:38:22.375 --> 00:38:26.875
to serve, for example, a Manpoo list instance or, like, an Electrum server to some
574
00:38:27.415 --> 00:38:33.390
others, and the Raspberry Pi will be a bit underpowered for that, and then they will now start on a
575
00:38:34.030 --> 00:38:35.970
on just a computer in the corner,
576
00:38:36.675 --> 00:38:37.175
then
577
00:38:38.195 --> 00:38:40.775
exactly this would be the time just to
578
00:38:41.475 --> 00:38:52.990
not to take something off the shelf, but just build it themselves. And then this would be the right guy to look into, and you might need some modifications in in a couple of cases. But, I mean, it's it's pretty much
579
00:38:54.575 --> 00:38:57.555
same on any computer running Linux. Right?
580
00:38:58.975 --> 00:39:01.635
So this was one of the the main goals.
581
00:39:03.089 --> 00:39:05.109
Is now in version 3,
582
00:39:06.769 --> 00:39:07.430
with a
583
00:39:07.730 --> 00:39:08.230
nice
584
00:39:08.769 --> 00:39:21.260
neon glow layout. That was just it's just like 1 or 2 months old, the current guide. And one of the major changes was to get rid of all Raspberry Pi specific commands.
585
00:39:22.039 --> 00:39:27.260
So it's it's much easier to set up the Wi Fi using a respi config or something like that.
586
00:39:27.720 --> 00:39:28.220
But
587
00:39:28.855 --> 00:39:35.115
I really wanted to have it as universal as possible. So if openums mentions that, okay, now,
588
00:39:35.895 --> 00:39:37.595
the Raspberry Pi is no longer
589
00:39:38.200 --> 00:39:39.980
has no longer the oomph you need.
590
00:39:40.920 --> 00:39:43.820
It should be possible to have exactly the same,
591
00:39:44.520 --> 00:39:45.020
setup,
592
00:39:46.205 --> 00:39:52.465
for example, on a on a cloud server or, like, on a on a virtual private server or on a
593
00:39:54.340 --> 00:39:56.280
NUC, like, Intel NUC based,
594
00:39:56.980 --> 00:39:58.520
hardware you host yourself.
595
00:39:59.380 --> 00:40:05.545
The only changes would probably be that you don't need to download the ARM 64, the binaries, but the Intel
596
00:40:05.925 --> 00:40:08.984
ones. But that's like a a very easy
597
00:40:09.470 --> 00:40:15.650
change to do. Everything else should be exactly the same because it uses only plain Debian commands.
598
00:40:17.125 --> 00:40:19.145
I mean, the Raspi the Raspis
599
00:40:19.525 --> 00:40:20.505
are very underpowered,
600
00:40:21.845 --> 00:40:24.345
but they're also really cheap and efficient and
601
00:40:25.110 --> 00:40:26.330
easy to work with.
602
00:40:26.870 --> 00:40:30.810
I mean, the Raspi when Raspi Bolt first when you first released
603
00:40:31.190 --> 00:40:35.095
v one of Raspi Bolt, I mean, that must have been on Raspberry Pi Threes
604
00:40:35.635 --> 00:40:40.695
Yes. Which were really underpowered. And now most people use Raspberry Fours. Right?
605
00:40:41.170 --> 00:40:45.830
Exactly. So I would even say that like a Raspberry Pi 4 with 8 gigabytes of RAM,
606
00:40:46.130 --> 00:40:46.450
it
607
00:40:47.810 --> 00:40:48.310
it's
608
00:40:48.675 --> 00:40:53.975
almost overkill for this kind of setup unless you have, like, hundreds of channels.
609
00:40:54.355 --> 00:40:56.295
But, of course, that's like regular
610
00:40:57.010 --> 00:40:58.869
scaling in IT terms.
611
00:40:59.490 --> 00:41:00.950
But I think my
612
00:41:01.250 --> 00:41:03.430
pies are mostly idle. They have
613
00:41:03.730 --> 00:41:07.115
way too much oomph for that stuff they do.
614
00:41:08.295 --> 00:41:14.235
But for example, on the Raspberry Pi 3, it was not a it it was not possible to verify the blockchain
615
00:41:14.630 --> 00:41:18.170
directly on the device. So the older versions of the guide
616
00:41:18.550 --> 00:41:20.010
made you download the
617
00:41:20.310 --> 00:41:22.330
blockchain to your regular computer,
618
00:41:22.945 --> 00:41:27.125
like run through the whole indexing stuff and then copied over
619
00:41:27.665 --> 00:41:28.965
to the to the pie.
620
00:41:29.345 --> 00:41:32.550
This now is no longer necessary. You can just
621
00:41:33.110 --> 00:41:35.610
wait 2 days and everything is indexed.
622
00:41:36.390 --> 00:41:43.005
I think that's that's pretty cool. And, I mean, if you what what you get for $60 or so is is really amazing.
623
00:41:44.665 --> 00:41:46.265
I mean, we just recently had,
624
00:41:46.665 --> 00:41:50.045
Craig Rall, lead maintainer of Spiro Wallet. I mean, he released,
625
00:41:52.410 --> 00:41:56.430
like, a performance analysis breakdown of ElectrumX and Electris
626
00:41:56.890 --> 00:41:58.110
Electrum Rust Server
627
00:42:00.365 --> 00:42:01.905
using RAASPI Fours.
628
00:42:03.484 --> 00:42:04.545
And I guess
629
00:42:05.645 --> 00:42:10.329
most of these projects are using Electrum Rust Server. It's not practical to,
630
00:42:11.430 --> 00:42:13.530
run Electrum x on them.
631
00:42:13.990 --> 00:42:16.490
And he he's I mean, his analysis
632
00:42:16.790 --> 00:42:17.930
seemed to
633
00:42:18.725 --> 00:42:20.825
make clear and, I mean, I've noticed it myself
634
00:42:21.365 --> 00:42:25.225
that, you know, it's not an ideal situation really. Like, if you're using
635
00:42:27.330 --> 00:42:33.270
an Electrum server running on a raspi and you have a wallet that is very deep, that has a lot of,
636
00:42:33.890 --> 00:42:36.630
UTXO history, a lot of transaction history,
637
00:42:37.425 --> 00:42:39.765
they tend to really struggle still.
638
00:42:40.225 --> 00:42:45.605
Yeah. That's true. So, I mean That's also an inherent limitation of Electris
639
00:42:45.985 --> 00:42:46.485
itself.
640
00:42:47.690 --> 00:42:48.190
ElectrumX
641
00:42:48.490 --> 00:42:48.990
is
642
00:42:50.570 --> 00:42:51.869
harder to set up,
643
00:42:52.570 --> 00:42:54.225
but it for, like
644
00:42:55.185 --> 00:43:01.445
I I work at ShiftCrypto. Right? So we do run our own Electrum servers for our clients with the hardware wallets.
645
00:43:02.145 --> 00:43:02.645
And
646
00:43:03.060 --> 00:43:04.280
we use Electrum
647
00:43:04.740 --> 00:43:05.880
X for that
648
00:43:06.180 --> 00:43:07.240
because it
649
00:43:07.540 --> 00:43:09.000
Elektrus is not built
650
00:43:09.380 --> 00:43:09.880
to
651
00:43:10.465 --> 00:43:11.685
serve, like, 1,000
652
00:43:12.385 --> 00:43:13.045
and 1,000
653
00:43:13.345 --> 00:43:15.205
of clients at the same time.
654
00:43:16.305 --> 00:43:21.270
But you're running those on professional servers? Yeah. Of course. Not the right side of the That's true. Yeah.
655
00:43:21.890 --> 00:43:22.390
Yeah.
656
00:43:22.849 --> 00:43:23.910
I mean, I
657
00:43:25.725 --> 00:43:28.465
I wouldn't agree on that, like, the pie
658
00:43:29.405 --> 00:43:31.185
is too much. It is
659
00:43:31.645 --> 00:43:34.705
absolutely the bare minimum. The the the
660
00:43:35.069 --> 00:43:36.609
r p 3 was
661
00:43:37.470 --> 00:43:43.890
not suitable to do this. And whoever comes to me asking that, oh, can I do this on a Raspberry Pi 3?
662
00:43:44.295 --> 00:43:47.675
Well, I mean, they can, you know, it is a wrong question
663
00:43:48.055 --> 00:43:49.515
because no one should.
664
00:43:50.055 --> 00:43:50.714
And then
665
00:43:51.335 --> 00:43:52.714
Raspberry Pi 4
666
00:43:53.539 --> 00:43:54.279
does have
667
00:43:54.900 --> 00:43:57.799
I mean, the processor power is not that different.
668
00:43:58.260 --> 00:44:05.865
The RAM, obviously, you know, versus 1 gigabyte, 4 gigabytes, or 8 is is is great. But then just this this simple
669
00:44:06.325 --> 00:44:06.825
power,
670
00:44:07.365 --> 00:44:10.500
the emperors, it can give to the disk.
671
00:44:11.279 --> 00:44:15.859
It's just even that is just hardly enough for to power 1 disk. And the biggest
672
00:44:16.675 --> 00:44:24.615
problem with, you know, the resiliency of this of these setups is that single disk is prone to fail because there is no battery.
673
00:44:24.950 --> 00:44:26.650
They should be connected to UPS.
674
00:44:27.190 --> 00:44:27.690
And
675
00:44:28.150 --> 00:44:29.210
A battery backup?
676
00:44:29.589 --> 00:44:31.770
Yeah. Battery backup. And then you you wouldn't
677
00:44:32.305 --> 00:44:35.685
you cannot even think of, like, running RAID or, you know, duplicating,
678
00:44:36.865 --> 00:44:45.170
your your your data. Like, you know, data security basically is terrible, which is a very bad choice, very bad pair with lightning.
679
00:44:45.710 --> 00:44:47.010
Right. Because with lightning,
680
00:44:47.945 --> 00:44:50.285
I mean, with lightning, you want if if
681
00:44:51.065 --> 00:44:51.545
if,
682
00:44:52.025 --> 00:44:57.450
your your your your state is constantly changing and you need to constantly update your state,
683
00:44:58.410 --> 00:45:00.430
You don't wanna have an old state, otherwise,
684
00:45:00.810 --> 00:45:01.869
you get penalized
685
00:45:02.410 --> 00:45:06.645
and you can lose funds that way. And the main way of backing up,
686
00:45:07.345 --> 00:45:08.805
short of actually doing,
687
00:45:09.985 --> 00:45:13.525
constant, like, almost a RAID configuration where you're having constantly
688
00:45:15.370 --> 00:45:18.730
backing it up to a second drive is this idea of,
689
00:45:20.650 --> 00:45:38.240
static static channel backups where you actually lose all your channels in that situation. Everything gets settled on chain. So it's, like, not an ideal backup situation. You'd prefer if you just didn't have the drive failure in the first place. So yes. Exactly. So the subject to channel backup is just a list of your peers where the node,
690
00:45:38.625 --> 00:45:42.405
in a failover situation, can connect to and ping them
691
00:45:42.705 --> 00:45:46.725
to force close the channels themselves. If they are offline, funds are stuck.
692
00:45:48.290 --> 00:45:51.270
You know, that is that is not not much use.
693
00:45:51.650 --> 00:45:52.310
The actual
694
00:45:52.610 --> 00:45:58.385
channel database, the database of the of the states of the lightning channels is is most valuable information,
695
00:45:58.845 --> 00:46:07.880
which indeed you need to back up in real time, which you can you can do. Like, especially with c lightning, it has a plug in which has which can do real time backups
696
00:46:08.579 --> 00:46:10.280
even to an off-site location.
697
00:46:10.755 --> 00:46:14.535
But then what you get, you need to run another server. Right?
698
00:46:14.914 --> 00:46:20.380
Right. I mean, you would need to do this anyway for backups, but, I mean, you would need to have your
699
00:46:21.000 --> 00:46:21.500
main
700
00:46:21.800 --> 00:46:22.300
machine,
701
00:46:23.800 --> 00:46:27.900
working quite quite as reliably as well. So I think that that is the biggest kind of
702
00:46:28.664 --> 00:46:34.525
bottleneck or or a drawback or weakness of of of the Raspberry Pi that it cannot it's not able to
703
00:46:35.224 --> 00:46:40.789
power, like, 2 disks just by itself. And then you can use external power. You have an extra cable,
704
00:46:41.569 --> 00:46:47.005
you know, and then another thing that with which the cats or, you know, like a young child can play with.
705
00:46:47.805 --> 00:46:49.904
You know, again, not not ideal.
706
00:46:51.484 --> 00:46:55.424
And this is specifically for Lightning. If, I mean, if it's on chain funds,
707
00:46:56.125 --> 00:46:56.625
then
708
00:46:57.800 --> 00:47:00.780
I I always channel my inner Zoolander. Like, with Lightning,
709
00:47:01.160 --> 00:47:02.540
the keys are in the computer.
710
00:47:03.080 --> 00:47:04.060
With with
711
00:47:04.625 --> 00:47:14.760
on chain, the keys are ideally being are not being held on the actual node itself. So if the node fails, it's just it's just a way of interacting with the network. It's not actually holding your secrets.
712
00:47:15.620 --> 00:47:16.440
Yeah. Exactly.
713
00:47:16.820 --> 00:47:21.400
I think we're we're probably having a a bit of different use cases in mind.
714
00:47:21.865 --> 00:47:26.444
For me, it's really the Raspberry Pi is the perfect device to have your own
715
00:47:26.825 --> 00:47:30.349
at home Bitcoin full node for on chain use,
716
00:47:31.369 --> 00:47:36.029
query the network. Yeah. Like a direct participant of the peer to peer network
717
00:47:36.569 --> 00:47:37.710
and run a lightning,
718
00:47:38.525 --> 00:47:40.625
node on top for your personal use.
719
00:47:41.085 --> 00:47:49.400
But I'd never use it for, like, a business or if you have I mean, I probably have, like, 20 channels or so, and for that, it's perfectly fine.
720
00:47:51.380 --> 00:47:53.240
But, of course, if you're looking into
721
00:47:53.994 --> 00:47:54.815
this redundancy
722
00:47:55.275 --> 00:47:55.775
or,
723
00:47:56.075 --> 00:47:58.175
like, hold, like, large funds
724
00:47:58.475 --> 00:48:01.375
or even need, like, guaranteed 247
725
00:48:01.755 --> 00:48:04.730
uptime for a business because otherwise you can't take any,
726
00:48:05.349 --> 00:48:05.849
payments,
727
00:48:06.470 --> 00:48:06.970
then
728
00:48:07.270 --> 00:48:09.690
a Raspberry Pi is probably not the,
729
00:48:10.230 --> 00:48:11.210
the right choice.
730
00:48:11.515 --> 00:48:14.655
Then I'd definitely go with something that actually has a case
731
00:48:15.035 --> 00:48:17.215
and a decent power supply and
732
00:48:17.515 --> 00:48:18.895
allows you to have,
733
00:48:19.250 --> 00:48:20.869
like, all the stuff neatly
734
00:48:21.250 --> 00:48:23.430
connected directly and not everything
735
00:48:24.130 --> 00:48:27.205
dangling off USB hubs and stuff like that.
736
00:48:28.645 --> 00:48:36.105
Yeah. Agree. But, yes, I've, you know, kind of just stropening this this argument that, you know, I I'm I'm
737
00:48:36.860 --> 00:48:40.160
building recipe blitzes and, you know, I
738
00:48:40.780 --> 00:48:43.440
do develop this software and, you know, I do
739
00:48:43.740 --> 00:48:45.840
think that it is a great way to start.
740
00:48:47.045 --> 00:48:55.144
But then, indeed, you would need to scale up if you are, you know, doing something serious with your node. Like, for example, 20 channels is just about
741
00:48:55.710 --> 00:48:57.809
which, you know, I would say,
742
00:48:58.670 --> 00:48:59.170
acceptable.
743
00:48:59.470 --> 00:49:02.609
But if you go up, for example, to 50 so just
744
00:49:03.395 --> 00:49:13.369
just take a quick calculation of what does it cost to force close 50 channels if you are lucky. Yeah. And, oh, and, oh, so your the disc fails. It does fail, you know, one
745
00:49:13.670 --> 00:49:16.730
in every 3 years, I would say, you know, it's
746
00:49:17.270 --> 00:49:18.970
quite likely. And then
747
00:49:19.855 --> 00:49:24.915
even with the SSDs, I mean, the hard disks are even even even worse, but don't even go there.
748
00:49:26.415 --> 00:49:34.920
And then you would need to restore, for example, the static channel backup, which you have been, you know, cleverly set up to to have saved somewhere
749
00:49:35.300 --> 00:49:37.000
automatically or or,
750
00:49:37.515 --> 00:49:39.694
there is a guide for that investment board.
751
00:49:42.315 --> 00:49:43.454
So 50 times,
752
00:49:44.320 --> 00:49:44.820
what,
753
00:49:45.280 --> 00:49:46.260
$5 transaction?
754
00:49:46.560 --> 00:49:49.300
Force closes are are are bigger, and
755
00:49:49.840 --> 00:49:52.820
they for security, they are using a high fee,
756
00:49:54.065 --> 00:49:56.244
so they should confirm in the next block.
757
00:49:56.625 --> 00:49:57.845
So let's say,
758
00:49:58.305 --> 00:49:59.125
$10 each.
759
00:49:59.425 --> 00:49:59.925
That's
760
00:50:00.545 --> 00:50:01.445
that's $500.
761
00:50:02.400 --> 00:50:05.059
You can get quite decent competitor for that.
762
00:50:07.599 --> 00:50:16.325
And you might have, you know, invested it before you had the 50 channels or you have the 50 channels now, you might invested it invested into hardware,
763
00:50:16.625 --> 00:50:17.125
migrate
764
00:50:17.425 --> 00:50:19.525
the nodes over, which is perfectly
765
00:50:19.985 --> 00:50:20.485
possible.
766
00:50:21.450 --> 00:50:26.990
And then you have a good computer and less risk of needing to close all your channels, for example.
767
00:50:28.885 --> 00:50:32.025
So, yeah, just just be aware of of of the limitations
768
00:50:32.805 --> 00:50:36.025
of it. And, yeah, don't don't be very
769
00:50:37.620 --> 00:50:41.400
to start, but then recognize when you need to need to step up.
770
00:50:41.700 --> 00:50:42.600
Hashtag reckless.
771
00:50:43.540 --> 00:50:45.160
Yeah. No disagreement there.
772
00:50:45.540 --> 00:50:45.860
So
773
00:50:46.405 --> 00:50:52.585
I mean, that's an interesting framing that in a lot of ways, you're kind of when you start with the raspi, you're you're basically
774
00:50:53.445 --> 00:50:57.470
deferring a potential cost rather than doing the cost upfront.
775
00:50:58.730 --> 00:50:59.550
We have,
776
00:51:00.330 --> 00:51:05.385
the j plus one in the comments. I feel like this is a good jumping point based on
777
00:51:05.685 --> 00:51:06.985
your previous comment
778
00:51:07.845 --> 00:51:10.105
asking about if you guys have any experience
779
00:51:10.470 --> 00:51:12.970
about migrating off a pie to new hardware,
780
00:51:13.830 --> 00:51:15.690
and, like, what that process entails.
781
00:51:16.230 --> 00:51:17.850
Any tips or tricks there?
782
00:51:20.375 --> 00:51:22.795
I guess for the lightning part, Openhouse is
783
00:51:23.095 --> 00:51:23.835
much more
784
00:51:24.375 --> 00:51:24.875
experienced,
785
00:51:26.055 --> 00:51:26.980
than I am.
786
00:51:27.700 --> 00:51:32.980
But I would say set if you migrate to new hardware, you can just set it up,
787
00:51:33.380 --> 00:51:36.359
at in terms of the rest pie, bolt.
788
00:51:36.674 --> 00:51:37.575
Just set it up
789
00:51:37.875 --> 00:51:39.815
new. You can copy over the blockchain.
790
00:51:41.714 --> 00:51:42.775
If I'm not mistaken,
791
00:51:43.234 --> 00:51:43.734
probably
792
00:51:44.260 --> 00:51:45.160
set up lightning
793
00:51:45.620 --> 00:51:51.880
part, run it once, and close it down again. And I think after that, you can pretty much copy the the old,
794
00:51:53.875 --> 00:51:59.095
directories over. Right? You just need to make sure that never ever the old note goes online again.
795
00:52:00.390 --> 00:52:00.890
Yep.
796
00:52:01.830 --> 00:52:03.130
No. That's, that's
797
00:52:03.670 --> 00:52:04.170
basically
798
00:52:04.790 --> 00:52:15.415
just it. It it's not that difficult. I mean, and people need to understand then why the old node doesn't it must not go online ever again because it has
799
00:52:16.069 --> 00:52:19.289
a previous state of this the channels.
800
00:52:19.750 --> 00:52:23.609
And once that database have been running in another instance,
801
00:52:24.069 --> 00:52:24.890
those dates
802
00:52:25.305 --> 00:52:27.965
states obviously get updated with with the peers
803
00:52:28.745 --> 00:52:42.420
as well as on that instance. And then if you boot up the old one again I mean, you could boot up, but if you would run l and d or c lightning on the on the old one again, then you would try to
804
00:52:43.015 --> 00:52:43.994
build on the
805
00:52:45.174 --> 00:52:48.075
the previous states, which then your peers would penalize
806
00:52:48.454 --> 00:52:49.914
and losing all your channel
807
00:52:50.320 --> 00:52:53.220
funds. All the channel funds would go on to the,
808
00:52:53.920 --> 00:52:58.545
to the other side, which is which is a penalty mechanism of of of the current
809
00:52:58.944 --> 00:53:01.765
Lightning protocol. So it's important to prevent,
810
00:53:02.065 --> 00:53:04.405
but you can easily do that when you are moving
811
00:53:05.025 --> 00:53:06.005
between hardwares.
812
00:53:06.464 --> 00:53:07.285
You take
813
00:53:08.410 --> 00:53:11.310
so what what do you have for for lightning? You have
814
00:53:11.849 --> 00:53:12.910
a wallet file,
815
00:53:13.210 --> 00:53:15.310
which is like a wallet dotdb
816
00:53:16.295 --> 00:53:18.635
for lnd. It's like an HSM secret
817
00:53:19.974 --> 00:53:21.035
for c lightning.
818
00:53:21.415 --> 00:53:24.635
It it contains the keys with from which the Bitcoin keys
819
00:53:25.280 --> 00:53:26.260
are derived from.
820
00:53:26.720 --> 00:53:30.500
And then you have another file which is called the channel DB
821
00:53:31.040 --> 00:53:32.180
or the lightning
822
00:53:33.135 --> 00:53:33.635
SQLite,
823
00:53:34.494 --> 00:53:36.435
which is a database of your lightning
824
00:53:36.815 --> 00:53:37.315
net
825
00:53:37.855 --> 00:53:39.234
lightning channel states,
826
00:53:40.150 --> 00:53:40.650
which
827
00:53:41.670 --> 00:53:43.930
is containing the keys for the off chain funds,
828
00:53:44.470 --> 00:53:48.250
which is the ones in the lightning channel. So, basically, these two files
829
00:53:48.615 --> 00:53:57.435
just needs to be moved to the new instance. And as as Stelica said, it's a great practice to make sure that the new setup works by just, you know,
830
00:53:58.440 --> 00:54:04.780
running a new node on it and make sure that there are no, you know, bugs or, like, things which are would
831
00:54:05.640 --> 00:54:06.700
stop you from
832
00:54:07.855 --> 00:54:09.954
stop it from working. And then
833
00:54:10.494 --> 00:54:14.435
you can just take these old files and put it in place of the of the
834
00:54:16.100 --> 00:54:16.920
new ones.
835
00:54:17.300 --> 00:54:20.520
So your old ones would move in place to this
836
00:54:21.620 --> 00:54:22.120
new
837
00:54:22.660 --> 00:54:23.160
setup.
838
00:54:23.860 --> 00:54:24.360
And
839
00:54:25.815 --> 00:54:27.755
while you're moving, you would need
840
00:54:28.055 --> 00:54:29.434
to rename those directories
841
00:54:30.214 --> 00:54:33.434
or I mean, don't delete them key backups, but
842
00:54:34.570 --> 00:54:36.830
just move them and make sure it won't be a functional
843
00:54:38.170 --> 00:54:39.470
software again when
844
00:54:40.090 --> 00:54:41.150
the computer starts
845
00:54:42.275 --> 00:54:43.655
with the same day score,
846
00:54:43.955 --> 00:54:45.255
with the old disk again.
847
00:54:45.875 --> 00:54:46.375
So
848
00:54:46.835 --> 00:54:48.435
and, also, I mean, I've done
849
00:54:48.915 --> 00:54:52.055
in terms of moving to a completely new type of machine,
850
00:54:52.420 --> 00:54:52.920
Like,
851
00:54:53.300 --> 00:54:54.119
there's been
852
00:54:54.819 --> 00:54:56.119
a problem recently
853
00:54:56.420 --> 00:54:57.880
when we discovered
854
00:54:58.260 --> 00:55:00.920
that when the LND database, general database,
855
00:55:01.465 --> 00:55:03.485
does grow above 1 gigabytes,
856
00:55:03.865 --> 00:55:07.005
which is if you are, like, running rebalance scripts or,
857
00:55:07.785 --> 00:55:09.485
you know, having a lot of payments
858
00:55:10.010 --> 00:55:13.790
and or making a lot of payments that can happen fairly quickly
859
00:55:14.170 --> 00:55:18.030
within couple of months really with, like, you know, 20, 30 channels.
860
00:55:19.105 --> 00:55:19.585
And,
861
00:55:20.065 --> 00:55:22.645
it stops working on the 32 bit
862
00:55:23.185 --> 00:55:24.325
Raspberry Pi
863
00:55:25.185 --> 00:55:28.130
OS, which is which is a good thing that the
864
00:55:28.930 --> 00:55:33.910
Raspberry Pi itself, Raspberry Pi 3 and 4 themselves is 64 bit compatible.
865
00:55:35.819 --> 00:55:44.020
But the default operating system which the Raspberry Pi Foundation does distribute to be compatible with zeros and everything else is 32 bit
866
00:55:44.900 --> 00:55:48.680
and that is not supported by LND, for example. So we need to
867
00:55:49.140 --> 00:55:52.520
move a lot of nodes. I mean, I did a couple myself
868
00:55:52.945 --> 00:55:58.405
from this 32 bit architecture to 64 bit 1, which was which is was
869
00:55:58.705 --> 00:56:01.710
clearly not recommended in the in the documentation
870
00:56:02.570 --> 00:56:03.870
of l and d, for example.
871
00:56:04.490 --> 00:56:06.590
But then it worked without without problems.
872
00:56:06.890 --> 00:56:09.934
Yeah. Hashtag reckless. You know, the first one I was sweating, but,
873
00:56:10.494 --> 00:56:12.355
second one was not that bad.
874
00:56:12.734 --> 00:56:14.515
And then I moved further
875
00:56:14.815 --> 00:56:15.315
to
876
00:56:16.575 --> 00:56:21.630
when these databases now, you know, grow to be, like, you know, 6, 7, 8 gigabytes
877
00:56:22.250 --> 00:56:22.750
and,
878
00:56:23.130 --> 00:56:25.630
you know, the number of the channels are growing,
879
00:56:25.930 --> 00:56:26.750
I moved them
880
00:56:28.925 --> 00:56:30.145
to proper x8664
881
00:56:31.165 --> 00:56:33.905
bit architecture, which is like an old server,
882
00:56:35.910 --> 00:56:38.650
which you can you can get for, like, you know, 2 £200
883
00:56:40.470 --> 00:56:40.970
ish.
884
00:56:41.510 --> 00:56:42.710
You know, something which,
885
00:56:43.350 --> 00:56:44.090
has, like,
886
00:56:46.315 --> 00:56:47.934
5, 6 years old,
887
00:56:48.954 --> 00:56:50.015
industrial setup.
888
00:56:50.954 --> 00:57:02.040
So it is not not a big investment, but then you can start stacking disks in it and, like, and fall down all sorts of rabbit holes about data security and integrity and etcetera.
889
00:57:04.384 --> 00:57:18.130
And then even between operating systems, you know, these files, the, like, developed database and the channel database, these these can be moved. So it's it's doable. Just need to be careful where where you put things and don't destroy data and then just concentrate on not
890
00:57:18.910 --> 00:57:19.410
running
891
00:57:19.790 --> 00:57:21.330
old instances as well.
892
00:57:21.635 --> 00:57:24.295
But with all that said, I mean, you're of the belief that
893
00:57:25.234 --> 00:57:29.175
people just shouldn't even have them most people shouldn't even have that many channels open.
894
00:57:29.714 --> 00:57:30.694
They should just,
895
00:57:31.930 --> 00:57:33.710
you know, keep it to the bare minimum
896
00:57:34.490 --> 00:57:38.430
and and maybe even why even migrate in that situation? Why not just
897
00:57:40.065 --> 00:57:40.885
close channels
898
00:57:41.185 --> 00:57:44.725
and close those few channels you have and open new ones on the
899
00:57:45.105 --> 00:57:46.140
on the new node?
900
00:57:47.339 --> 00:57:53.660
Well, I mean, you you want to want to save on churn fees. I mean, it depends. Now it's easy when it's 1 set per byte, confirms next block, but,
901
00:57:54.460 --> 00:57:59.155
or no? It's is it 8 8 sets per byte? But, still Oh, big spending.
902
00:58:00.734 --> 00:58:05.950
Yeah. Yeah. Because if you don't care about your notes, that's as a routing note, for example,
903
00:58:07.050 --> 00:58:07.550
then
904
00:58:08.090 --> 00:58:11.550
closing channels and opening. If you have, like, 5 or 10 channels,
905
00:58:12.455 --> 00:58:13.595
It's probably also
906
00:58:14.135 --> 00:58:19.595
a a good way to do it. But, I mean, Open Arms came out swinging and was like, you're not gonna make any money anyway.
907
00:58:21.040 --> 00:58:24.100
So at least don't throw, like, 6¢ out of the window.
908
00:58:26.400 --> 00:58:26.900
Yeah.
909
00:58:27.235 --> 00:58:31.815
Well, you can you won't make money, but you can save and you can do things
910
00:58:32.915 --> 00:58:35.575
you can do things which you You can look for them. Platform.
911
00:58:36.115 --> 00:58:36.870
Yeah. Exactly.
912
00:58:38.790 --> 00:58:44.570
Cool. I mean, it's like, yeah, it's like, why why would you buy a car a car which would consume less? Right?
913
00:58:45.775 --> 00:58:46.275
Awesome.
914
00:58:46.655 --> 00:58:52.515
I mean, we had another comment in the chat about someone saying they like to use a
915
00:58:52.859 --> 00:58:58.560
brand new Mac mini with the their m one chip and a 2 terabyte SSD in it,
916
00:58:59.420 --> 00:59:03.205
for their node. Do you have any feedback for that person?
917
00:59:05.425 --> 00:59:06.885
Awesome. Go for it.
918
00:59:08.625 --> 00:59:09.125
Cool.
919
00:59:10.549 --> 00:59:13.290
Do you know open arms? Is, like, is it arm 64
920
00:59:13.990 --> 00:59:19.049
with the m one? Yes. Yes. I think so. I didn't work. Yeah. I I I didn't
921
00:59:23.055 --> 00:59:25.075
try the machine itself, but
922
00:59:25.535 --> 00:59:27.875
I've heard tests that it was, like,
923
00:59:28.255 --> 00:59:36.410
validating the whole chain in, like, 4 hours or so Oh, wow. When it came out. And, you know, it's certainly powerful enough to be,
924
00:59:37.109 --> 00:59:38.730
able to deal with the situation.
925
00:59:39.975 --> 00:59:45.035
But, you know, run Linux on it. I mean, I don't know. Does it commit like a fixed operating system?
926
00:59:45.575 --> 00:59:47.515
Don't use closed source operating systems?
927
00:59:48.170 --> 00:59:50.190
Can can you run Linux on m 1?
928
00:59:50.730 --> 00:59:52.190
I'm sure you can. Yeah.
929
00:59:53.210 --> 00:59:54.910
They're not doing some kind of
930
00:59:55.425 --> 00:59:56.405
Secure Elements
931
00:59:56.785 --> 00:59:58.165
bullshit in there or something?
932
01:00:00.305 --> 01:00:01.445
I have no idea.
933
01:00:02.385 --> 01:00:04.885
Well, like, you need, like, the signing key? I don't know.
934
01:00:05.490 --> 01:00:10.069
I've never tried it. Then jailbreak it. You know? Yes. Yeah. Jailbreak it. Exactly.
935
01:00:10.530 --> 01:00:11.750
Jailbreak your $2,000
936
01:00:12.050 --> 01:00:14.630
computer or whatever it is. A $1,000 computer.
937
01:00:16.265 --> 01:00:17.325
But, yeah, I mean,
938
01:00:17.704 --> 01:00:22.345
if if your node is holding, if you care about your privacy, if your node's holding a decent amount of funds,
939
01:00:24.099 --> 01:00:26.839
running the closed source OSX platform,
940
01:00:27.619 --> 01:00:30.839
that Mac should get shipped with by default is a
941
01:00:31.700 --> 01:00:32.680
dangerous game.
942
01:00:36.725 --> 01:00:38.505
So where do we wanna go from here?
943
01:00:41.960 --> 01:00:42.460
So
944
01:00:42.840 --> 01:00:45.500
open up suggested before to
945
01:00:46.600 --> 01:00:49.020
do a quick run through the guide,
946
01:00:49.464 --> 01:00:55.484
and I wanted to take a step back. But I guess we we took a step back and took a little walk
947
01:00:55.865 --> 01:00:56.605
from there,
948
01:00:57.930 --> 01:00:58.430
Maybe
949
01:00:58.809 --> 01:00:59.309
going
950
01:00:59.770 --> 01:01:06.109
through the quickly through the individual parts of the guide and give some comments here and there could be something.
951
01:01:06.494 --> 01:01:07.315
Let's do
952
01:01:08.645 --> 01:01:09.395
it. Cool.
953
01:01:10.415 --> 01:01:10.915
So,
954
01:01:13.910 --> 01:01:16.410
of course, like, if you if you go to raspi bolt.org,
955
01:01:16.950 --> 01:01:20.410
it gives you some, like, okay, what is it?
956
01:01:21.385 --> 01:01:22.045
How is structured?
957
01:01:23.065 --> 01:01:26.845
There's, like, I think, a pretty important part about the community
958
01:01:27.625 --> 01:01:32.060
where you can like, if you run into problems, you can open an an issue on GitHub.
959
01:01:32.520 --> 01:01:33.820
There's a knowledge base.
960
01:01:34.520 --> 01:01:35.820
There's a Reddit sub.
961
01:01:36.440 --> 01:01:38.265
You can join the Telegram group.
962
01:01:39.305 --> 01:01:41.644
So there's lots of people that
963
01:01:41.944 --> 01:01:44.045
want to help you if you're stuck somewhere.
964
01:01:45.144 --> 01:01:52.590
And from there, it's basically separated in 3 parts, like the the Raspberry Pi itself, including the operating system,
965
01:01:52.970 --> 01:01:56.030
then the Bitcoin on chain part, and then lightning.
966
01:01:57.125 --> 01:01:57.625
And
967
01:01:58.005 --> 01:02:00.425
after that, this is, like, the core guide.
968
01:02:02.005 --> 01:02:04.265
We aim to have, like, a high
969
01:02:06.849 --> 01:02:11.349
maintenance guarantee on the core guide. So it should be should mostly be up to date.
970
01:02:12.369 --> 01:02:14.035
If there's, like, something that
971
01:02:14.595 --> 01:02:18.135
no longer works, we're we're very happy to fix it quickly.
972
01:02:18.674 --> 01:02:24.170
But then there's also the bonus section, and this is more meant to be a collection of additional,
973
01:02:24.710 --> 01:02:25.770
optional guides,
974
01:02:26.390 --> 01:02:28.010
also from external contributors.
975
01:02:28.710 --> 01:02:33.345
And I think it's it can be pretty interesting to just have a collection of
976
01:02:33.645 --> 01:02:34.944
fun stuff to do.
977
01:02:35.325 --> 01:02:36.224
But, of course,
978
01:02:37.780 --> 01:02:44.760
stuff like that can become outdated, and it's not really possible to keep everything up to date in that bonus guide section.
979
01:02:45.565 --> 01:02:50.305
But this is really what I imagine a bit have, like, a a really well maintained core section
980
01:02:50.845 --> 01:02:52.065
and a a good,
981
01:02:52.765 --> 01:02:53.985
collection of
982
01:02:54.540 --> 01:02:58.160
individual guides or fun stuff to do on top of that,
983
01:03:00.220 --> 01:03:03.280
installing other applications and all that
984
01:03:03.580 --> 01:03:04.285
fun stuff.
985
01:03:07.005 --> 01:03:07.505
So,
986
01:03:08.285 --> 01:03:11.184
I mean, basically, the first thing you do is get a Raspberry
987
01:03:11.724 --> 01:03:12.224
Pi.
988
01:03:14.800 --> 01:03:18.660
The one thing that is really important, get the official power adapter.
989
01:03:19.280 --> 01:03:22.954
I've had I've I've wasted so much of my own time
990
01:03:23.255 --> 01:03:24.315
with using, like,
991
01:03:25.255 --> 01:03:27.355
regular USB adapters. And
992
01:03:28.110 --> 01:03:34.610
if you want to have a stable Raspberry Pi, just use the official one. This is the the one learning I took after
993
01:03:35.285 --> 01:03:36.184
hours of wasted,
994
01:03:38.165 --> 01:03:39.145
kernel panics
995
01:03:39.605 --> 01:03:40.345
and shutdowns.
996
01:03:42.085 --> 01:03:44.265
After that, you just install the
997
01:03:44.589 --> 01:03:49.970
the operating system. And as OpenNoms mentioned, it's really important to get the 64 bit,
998
01:03:50.270 --> 01:03:51.569
Raspberry Pi OS,
999
01:03:51.945 --> 01:03:53.965
which officially is still in beta,
1000
01:03:54.825 --> 01:03:56.845
but it works really well.
1001
01:03:57.785 --> 01:04:02.609
It's been running, I think, for months now on my note without a single restart.
1002
01:04:03.230 --> 01:04:04.609
I don't really think,
1003
01:04:05.710 --> 01:04:06.210
there's
1004
01:04:07.025 --> 01:04:07.525
much
1005
01:04:07.825 --> 01:04:09.285
instability in it.
1006
01:04:09.585 --> 01:04:12.965
So that's that's pretty cool. It's based on Debian, so
1007
01:04:13.560 --> 01:04:14.940
it's really a standard
1008
01:04:15.320 --> 01:04:16.280
Debian based,
1009
01:04:16.600 --> 01:04:17.100
Linux
1010
01:04:17.560 --> 01:04:18.060
system.
1011
01:04:19.240 --> 01:04:20.380
The cool thing is,
1012
01:04:21.000 --> 01:04:22.220
the Raspberry Pi
1013
01:04:22.744 --> 01:04:23.724
also provides
1014
01:04:24.744 --> 01:04:25.404
an application
1015
01:04:25.704 --> 01:04:27.085
to actually flash,
1016
01:04:28.424 --> 01:04:29.644
the operating system.
1017
01:04:30.770 --> 01:04:34.310
And what's really cool is that you can flash it directly on a SSD.
1018
01:04:34.690 --> 01:04:38.790
So you don't really need to use a micro s s a micro SD card
1019
01:04:39.125 --> 01:04:41.785
because in my experience, this is the weakest
1020
01:04:42.085 --> 01:04:43.625
part of the node.
1021
01:04:44.725 --> 01:04:46.345
Micro SD cards just
1022
01:04:46.840 --> 01:04:50.700
are not meant for constant write read and write operations.
1023
01:04:51.480 --> 01:04:51.980
So
1024
01:04:52.360 --> 01:04:59.785
after a year a year or or a bit more, maybe a bit less, they tend to wear out, at least mine did.
1025
01:05:00.645 --> 01:05:01.145
So
1026
01:05:02.970 --> 01:05:03.630
you can
1027
01:05:04.010 --> 01:05:04.750
write the
1028
01:05:05.210 --> 01:05:07.390
operating system directly on the SSD
1029
01:05:07.770 --> 01:05:16.915
and boot for directly from the SSD. You don't even need a micro SD card. I think that's that's pretty cool and improves the overall stability of the node a lot.
1030
01:05:19.170 --> 01:05:20.630
It's an it's an interesting,
1031
01:05:21.410 --> 01:05:27.895
change you have done with the it came in the v three, isn't it? Yeah. Exactly. Because it it it wasn't like that. And,
1032
01:05:30.355 --> 01:05:33.335
I have mixed feeling about mixed feelings about this because
1033
01:05:34.220 --> 01:05:36.460
it's easy to change a micro SD card, but then
1034
01:05:37.660 --> 01:05:40.720
I mean, even with my regular computer, you know, it's like, running
1035
01:05:41.099 --> 01:05:43.520
without partitions on your disk. Right?
1036
01:05:43.825 --> 01:05:47.045
That you have, like, just all eggs in 1 basket kind of
1037
01:05:47.345 --> 01:05:48.485
kind of thing. So,
1038
01:05:48.785 --> 01:05:53.890
I like having a a micro SD in in a setup like this because then you have just
1039
01:05:54.350 --> 01:05:56.290
a a separate physical device to
1040
01:05:56.750 --> 01:06:00.690
to replicate some of the things. For example, this this status channel backup
1041
01:06:00.990 --> 01:06:01.490
on.
1042
01:06:01.895 --> 01:06:05.035
So if one fails, you don't have everything failed.
1043
01:06:07.255 --> 01:06:09.735
Yeah. And that's the important part. So what we,
1044
01:06:10.610 --> 01:06:15.030
plan to do, like, in the next weeks, I guess, it's top list.
1045
01:06:15.730 --> 01:06:16.230
Actually,
1046
01:06:16.850 --> 01:06:18.325
as part of the core guides,
1047
01:06:18.805 --> 01:06:21.945
just plug in them, like a USB thumb drive
1048
01:06:22.724 --> 01:06:29.380
and directly store the static channel backup on that one. So we do have then redundancy again.
1049
01:06:30.160 --> 01:06:31.859
And we also include
1050
01:06:32.560 --> 01:06:33.220
a a little
1051
01:06:33.600 --> 01:06:34.065
guide,
1052
01:06:34.545 --> 01:06:37.605
how to upload and sync the static channel,
1053
01:06:38.545 --> 01:06:42.085
backup file to your own private GitHub repository
1054
01:06:42.385 --> 01:06:44.260
as like as a like a
1055
01:06:44.560 --> 01:06:48.100
let's say, a cloud drive or something like that.
1056
01:06:48.880 --> 01:06:52.055
Yes. It's an encrypted file, so you can basically put it anywhere you like.
1057
01:06:52.855 --> 01:06:53.355
Exactly.
1058
01:06:54.775 --> 01:07:00.795
Yeah. So and then, I mean, micro SDs indeed fail. They do access these 2, unfortunately.
1059
01:07:01.170 --> 01:07:01.829
But then
1060
01:07:02.369 --> 01:07:04.770
you you really so as just
1061
01:07:05.490 --> 01:07:05.990
as,
1062
01:07:06.530 --> 01:07:11.515
you mentioned with the power supply, it really depends on the quality you buy
1063
01:07:12.135 --> 01:07:12.635
and
1064
01:07:13.495 --> 01:07:15.755
if it is what is written on the box.
1065
01:07:16.730 --> 01:07:21.630
Because we say, like, you know, buy buy a power supply which provides 3 amperes or more.
1066
01:07:22.010 --> 01:07:26.915
Well, not all of them are capable of doing that what is written on it. So,
1067
01:07:27.535 --> 01:07:30.915
indeed, I do for sure one is a good choice, but there are a couple like,
1068
01:07:33.615 --> 01:07:34.115
shop
1069
01:07:34.690 --> 01:07:37.349
does sell one which is called universal,
1070
01:07:38.609 --> 01:07:44.255
power supply, which is good quality as well and been been proving itself. And then regarding the SD cards,
1071
01:07:44.635 --> 01:07:50.335
we really found that, like, the endurance models from, like, some disk or
1072
01:07:50.715 --> 01:07:51.215
something
1073
01:07:52.859 --> 01:07:58.915
do the job much better in terms of, they have been designed to be Mhmm. Installed in, like,
1074
01:07:59.475 --> 01:08:01.975
you know, dashboard cameras and stuff like that, which are,
1075
01:08:02.355 --> 01:08:03.655
like, written constantly,
1076
01:08:04.755 --> 01:08:05.975
and they supposed to
1077
01:08:06.275 --> 01:08:08.950
last for a good couple of 1,000 hours.
1078
01:08:10.050 --> 01:08:12.070
So if you would happen to use
1079
01:08:12.370 --> 01:08:14.150
a micro SD, then
1080
01:08:14.450 --> 01:08:14.950
then
1081
01:08:15.625 --> 01:08:17.005
then use a good one.
1082
01:08:17.465 --> 01:08:19.565
I I can I wouldn't recommend that?
1083
01:08:19.865 --> 01:08:31.739
But then with the SSD, you would you should probably have some speed up as well. So the operating system would run faster if you are booting if you are booting from that. So it's a it's it's a really good, yeah, technical solution for sure.
1084
01:08:33.575 --> 01:08:40.955
Cool. Yeah. And it it sometimes I mean, even if there should be a problem with the operating system, you still can
1085
01:08:41.980 --> 01:08:45.760
flash it on a micro SD card and still boot from that. So
1086
01:08:46.780 --> 01:08:48.800
it's not like you're locked out
1087
01:08:49.115 --> 01:08:51.135
because just because everything's on the same
1088
01:08:51.515 --> 01:08:56.975
drive. But, yeah, I fully agree redundancy, especially with the backups, is super important.
1089
01:09:01.340 --> 01:09:02.400
Very good points.
1090
01:09:04.139 --> 01:09:07.114
Then Don't use the cheap SD card for sure.
1091
01:09:07.894 --> 01:09:11.994
No. Definitely not. No. You are already building something very affordable.
1092
01:09:12.934 --> 01:09:15.195
So, yeah, choose choose the parts wisely.
1093
01:09:16.489 --> 01:09:22.989
That's all I can say because loads of like, half of the issues are hardware based with these kind of things. Mhmm. Yeah.
1094
01:09:23.605 --> 01:09:27.945
And and, you you know, I I do have, like, quite a bit of experience with other,
1095
01:09:28.804 --> 01:09:32.265
single board computers as well. For example, the Rok Pro
1096
01:09:32.580 --> 01:09:33.080
64.
1097
01:09:33.699 --> 01:09:34.099
Yes.
1098
01:09:35.380 --> 01:09:43.195
And in my experience, I didn't find a board that comes close to the, like, uptime and reliability of a Raspberry Pi.
1099
01:09:43.735 --> 01:09:44.395
So even
1100
01:09:45.255 --> 01:09:47.034
even with a rock pro 64,
1101
01:09:47.490 --> 01:09:49.030
if you run them, like, 247,
1102
01:09:49.410 --> 01:09:49.910
there's
1103
01:09:50.530 --> 01:09:57.110
from time to time, it can be, like, 3 months, but it can also be just 2 weeks. There's a kernel panic, and it just freezes.
1104
01:09:57.785 --> 01:09:59.085
That really, really sucks
1105
01:09:59.545 --> 01:10:03.085
if you're not at home to reboot your node and you want to make some payments.
1106
01:10:03.945 --> 01:10:07.460
So that's very interesting. I mean, sorry. A little derailing your,
1107
01:10:08.100 --> 01:10:17.764
kind of walk through of the guide. Mhmm. But my favorite part, actually, which is which is in the in the FAQ, I think, and on just getting get there on the end.
1108
01:10:18.864 --> 01:10:22.885
It's not in the FAQ. It's in the bonus section, I guess, where you can
1109
01:10:23.340 --> 01:10:25.360
use different computers like
1110
01:10:25.660 --> 01:10:27.840
like the. Yeah. Yeah. There is hardware
1111
01:10:28.220 --> 01:10:28.720
setup,
1112
01:10:29.100 --> 01:10:29.840
which is
1113
01:10:31.665 --> 01:10:39.045
the famous top thumb droid was, you know, the basis of many many things. Like, most famously, I think it has been running
1114
01:10:40.730 --> 01:10:42.110
the set of his place
1115
01:10:42.410 --> 01:10:42.910
initially,
1116
01:10:43.770 --> 01:10:46.910
before he he scaled up, obviously. It picked up a bit.
1117
01:10:48.225 --> 01:10:50.805
And I did use these as well because
1118
01:10:51.345 --> 01:10:56.245
I've, just, you know, came to the rest of the day. Place was running on an originally?
1119
01:10:56.920 --> 01:10:58.620
Yeah. I didn't know that.
1120
01:10:58.920 --> 01:11:00.220
In Bitcoin Quala's
1121
01:11:00.680 --> 01:11:02.780
closet, I think. So Yeah. Exactly.
1122
01:11:04.135 --> 01:11:09.675
That's the I I think that is there is even, like, a picture of it, on theater somewhere. A lightning collar.
1123
01:11:10.295 --> 01:11:10.795
Yes.
1124
01:11:13.790 --> 01:11:16.370
So so yes. So so so just
1125
01:11:16.670 --> 01:11:19.250
obviously everything starts with getting the hardware.
1126
01:11:19.710 --> 01:11:21.410
It is interesting to find
1127
01:11:21.745 --> 01:11:27.264
to to hear your experience about the rock pro because in this old radio guide, you still, recommending these,
1128
01:11:28.225 --> 01:11:29.605
x u 4 and hcone
1129
01:11:30.400 --> 01:11:31.320
ones Mhmm.
1130
01:11:31.740 --> 01:11:33.780
Which are especially the hcone
1131
01:11:34.400 --> 01:11:36.100
has, like, a built in adapter.
1132
01:11:36.720 --> 01:11:39.300
So you can put the disk right attached
1133
01:11:39.615 --> 01:11:44.115
to the board, very stable, has a huge heat sink around it, which is the case as well.
1134
01:11:44.735 --> 01:11:46.835
But the problem is it has,
1135
01:11:47.390 --> 01:11:58.534
like, a 7th generation processor, which is only 30 32 bit, but it's not possible to run 64 bit on it. So I would consider that a little I mean, I I would consider that outdated.
1136
01:12:01.155 --> 01:12:11.690
But then there is the pro 64, which is popular with other projects like running Dojo, for example. They are I think they just released the new kind of preview at nodes, which is built based on it.
1137
01:12:12.235 --> 01:12:14.415
And and and you yourself had a lot of experience,
1138
01:12:14.875 --> 01:12:15.775
working with ShiftCrypto
1139
01:12:16.555 --> 01:12:17.615
with the bit BitBox
1140
01:12:18.795 --> 01:12:19.295
projects.
1141
01:12:20.230 --> 01:12:22.410
Space. Yeah. Bitbox space that was,
1142
01:12:23.110 --> 01:12:27.850
which was an it's it's an amazing and still up. Right? It's just, it's maintained?
1143
01:12:28.755 --> 01:12:35.415
Not really. No. No. I think if we ever pick it up, then we need to do redo a lot of stuff. Yeah. It's been iced.
1144
01:12:36.034 --> 01:12:37.015
Yeah. Exactly.
1145
01:12:37.590 --> 01:12:43.130
But that's Yes. I I was under the impression that it's good to yep. Yeah. I I wouldn't blame the the hardware,
1146
01:12:43.590 --> 01:12:44.615
specifically, but
1147
01:12:45.415 --> 01:12:47.195
I think we we built on the,
1148
01:12:48.695 --> 01:12:49.195
distribution.
1149
01:12:50.375 --> 01:12:54.315
And it might just as well be that there are, like, some
1150
01:12:54.650 --> 01:12:57.230
some NUCs in in in the distributions
1151
01:12:57.850 --> 01:13:08.415
that are not like the official ones. And with many boards, there aren't any official distributions. Right? Yeah. I mean, it's a rock chip as well. It is a it is a chip which is not
1152
01:13:08.715 --> 01:13:09.935
that widely used.
1153
01:13:10.235 --> 01:13:10.735
Mhmm.
1154
01:13:11.595 --> 01:13:12.410
So the
1155
01:13:12.890 --> 01:13:13.390
kernel
1156
01:13:14.330 --> 01:13:14.830
written
1157
01:13:15.290 --> 01:13:18.270
for it is basically not that well tested.
1158
01:13:18.970 --> 01:13:21.390
And that's been a problem with the previous,
1159
01:13:23.035 --> 01:13:24.335
kind of rock 64
1160
01:13:24.795 --> 01:13:30.895
board as well, which just, you know, many of them has been have been like, they were physically
1161
01:13:33.480 --> 01:13:36.540
they were, like, dead on arrival or or they were, like,
1162
01:13:37.000 --> 01:13:42.934
doing calculation errors, which is obviously not acceptable for for a Bitcoin node. Right? And the rock support 64
1163
01:13:43.474 --> 01:13:47.735
got much better and it also has like a PCI Express port where you can
1164
01:13:48.900 --> 01:13:49.400
apply
1165
01:13:50.340 --> 01:13:51.000
an NVMe
1166
01:13:51.540 --> 01:13:55.960
SSD. Exactly. So the ones which are usually found in laptops or, like,
1167
01:13:57.075 --> 01:13:57.575
systems
1168
01:13:58.115 --> 01:13:59.415
built for speed.
1169
01:14:00.835 --> 01:14:02.695
And that that that is very good.
1170
01:14:04.195 --> 01:14:04.935
The hackle
1171
01:14:05.650 --> 01:14:08.390
projects or HAC0, they call it, by
1172
01:14:08.770 --> 01:14:09.830
Nicolas Dore
1173
01:14:10.930 --> 01:14:15.110
with BTC based server, they were distributing these orders. So I have one with his
1174
01:14:15.635 --> 01:14:16.535
golden signature.
1175
01:14:18.114 --> 01:14:24.695
Cool. So as of now, you have, like, a a shift crypto SSD razor in it. Right?
1176
01:14:25.219 --> 01:14:29.960
Oh, no. That's something I wanted to come to. And, again, with the next stuff, I'm sorry.
1177
01:14:30.340 --> 01:14:30.659
But,
1178
01:14:31.619 --> 01:14:37.445
I have 2 of those. One from the hack 0, one I got personally from you, and a hack day in Munich Mhmm.
1179
01:14:38.625 --> 01:14:38.945
Which,
1180
01:14:40.210 --> 01:14:49.429
I did say that I will once run a server, well, there will be, you know, SSDs in the PCI Express ports, and that that's just what I have put together in last week,
1181
01:14:51.455 --> 01:14:51.955
where
1182
01:14:52.335 --> 01:14:54.915
on the motherboard, I can just, you know, put these,
1183
01:14:56.335 --> 01:14:58.275
PCI Express to NVMe
1184
01:14:58.655 --> 01:14:59.155
adapters
1185
01:14:59.770 --> 01:15:03.470
and, have much more space. And Mhmm. They are fantastically
1186
01:15:04.090 --> 01:15:05.150
fast as well.
1187
01:15:05.850 --> 01:15:10.735
So Cool. Yeah. And I have this shift script to logo on them. So it's
1188
01:15:11.115 --> 01:15:12.415
it's it looks really nice.
1189
01:15:14.635 --> 01:15:15.135
Yeah.
1190
01:15:15.515 --> 01:15:17.775
But at at least something came out of that.
1191
01:15:19.570 --> 01:15:20.790
Well, it's yeah.
1192
01:15:21.250 --> 01:15:24.869
You can you can buy these kind of adapters for, like, 4, £5.
1193
01:15:26.130 --> 01:15:27.995
So, like, up to $10 or so,
1194
01:15:28.955 --> 01:15:30.335
but they don't look as nice.
1195
01:15:30.715 --> 01:15:37.455
And they have a for Yeah. They have a different different alignment. They have so if you want to put it on the Rogue Pro
1196
01:15:37.880 --> 01:15:40.860
64, then they would stick out on one end, which
1197
01:15:41.560 --> 01:15:44.940
which wouldn't be the best. In a motherboard, it's fine.
1198
01:15:45.320 --> 01:15:46.700
They would design for that.
1199
01:15:48.185 --> 01:15:50.925
But yeah. Yeah. I think that's that's all my comments on the hardware.
1200
01:15:51.625 --> 01:15:57.005
Cool. Yeah. So coming back, I think, the Raspberry Pi is just like a pretty
1201
01:15:57.400 --> 01:15:57.900
well
1202
01:15:58.360 --> 01:16:00.220
vetted and very reliable,
1203
01:16:01.400 --> 01:16:02.060
piece of
1204
01:16:02.600 --> 01:16:03.740
cheap hardware.
1205
01:16:04.280 --> 01:16:07.265
So it's probably not for, like, huge servers,
1206
01:16:07.885 --> 01:16:11.025
but in my experience, it's the most stable one. And
1207
01:16:11.645 --> 01:16:15.185
the problem is when we when we started building the Bitbox base,
1208
01:16:16.330 --> 01:16:21.630
the Raspberry Pi 4 wasn't out. So it wasn't even announced. So we had to look for something else.
1209
01:16:22.090 --> 01:16:26.844
Yeah. And but but looking back now, I probably would just build on the Raspberry Pi 4.
1210
01:16:29.225 --> 01:16:32.920
Yeah. The, yeah, the the other big drawback of the Raspberry
1211
01:16:33.380 --> 01:16:35.000
Pi is that closed source
1212
01:16:35.300 --> 01:16:36.600
kind of GPU
1213
01:16:37.620 --> 01:16:38.840
Yep. That's true. OS
1214
01:16:39.380 --> 01:16:40.200
called ThreadX
1215
01:16:40.905 --> 01:16:41.805
owned by Microsoft.
1216
01:16:43.785 --> 01:16:44.285
And
1217
01:16:45.145 --> 01:16:47.805
it's just running as a binary blob underneath,
1218
01:16:49.210 --> 01:16:51.550
which is not true to the old droid
1219
01:16:51.929 --> 01:16:54.830
or the old either the oldroids or the old pro,
1220
01:16:55.929 --> 01:16:57.070
single board computers.
1221
01:16:58.385 --> 01:17:03.685
So, I mean, that that is something which we just need to kind of live with. It's a trade off.
1222
01:17:05.050 --> 01:17:10.349
There is no fully open source hardware at all, but this is a bit less open source than the others.
1223
01:17:12.225 --> 01:17:17.285
I mean, here, the software is not fully open source either, the, operating system itself.
1224
01:17:18.864 --> 01:17:22.005
So there's something to keep in mind if you want to go
1225
01:17:22.849 --> 01:17:24.230
on the full verification
1226
01:17:24.929 --> 01:17:25.429
route.
1227
01:17:26.929 --> 01:17:27.429
Yep.
1228
01:17:28.210 --> 01:17:28.690
That's,
1229
01:17:29.090 --> 01:17:33.695
I think there there are quite a few points that can be improved maybe over time.
1230
01:17:34.074 --> 01:17:34.955
Do you think that,
1231
01:17:36.315 --> 01:17:39.670
that becomes an even larger concern as as it becomes,
1232
01:17:40.370 --> 01:17:43.430
more common for people to be running Bitcoin nodes on their SPA's.
1233
01:17:44.290 --> 01:17:45.170
Like, I feel like it's
1234
01:17:48.125 --> 01:17:49.025
you know, one of
1235
01:17:49.725 --> 01:17:51.265
the often cited advantages
1236
01:17:51.725 --> 01:17:53.905
is that it's off the shelf parts.
1237
01:17:54.285 --> 01:18:00.130
It's not Bitcoin specific, but, you know, when we start hitting numbers like 10,000, 20,000
1238
01:18:00.590 --> 01:18:02.610
Bitcoin nodes running on RASPIs,
1239
01:18:03.475 --> 01:18:05.735
doesn't that argument kinda get thrown out the window?
1240
01:18:07.475 --> 01:18:10.135
I think that's why it's most important to offer alternatives.
1241
01:18:10.950 --> 01:18:23.994
Like, there is this old rate chapter in the in the guide as we do with the as well for I even released a couple of, like, SD card images for these older it's, which I've used still using one myself.
1242
01:18:24.695 --> 01:18:28.954
And and then scale out and, you know, use
1243
01:18:29.310 --> 01:18:31.890
every kind of thing which can run Linux, basically.
1244
01:18:33.150 --> 01:18:38.290
And and aim and work for for fully open source hardware, which is, you know, something
1245
01:18:39.054 --> 01:18:41.875
or or at least different approaches and different architectures.
1246
01:18:42.815 --> 01:18:49.040
I think that's the solution. You cannot rely on on the adjustment, the Raspberry Pi, I don't think. And we shouldn't
1247
01:18:49.420 --> 01:18:51.520
give the impression that we are doing this.
1248
01:18:54.925 --> 01:18:56.225
Yeah. That's a good point.
1249
01:18:57.405 --> 01:18:57.905
So
1250
01:18:58.365 --> 01:18:59.265
about security,
1251
01:18:59.725 --> 01:19:02.145
if if you allow me to go back to the guide.
1252
01:19:03.040 --> 01:19:04.659
Please. After installing
1253
01:19:04.960 --> 01:19:09.780
the the operating system, I think the one chapter that I feel is
1254
01:19:10.425 --> 01:19:11.085
the most
1255
01:19:11.705 --> 01:19:12.205
underrepresented
1256
01:19:12.745 --> 01:19:13.885
with other projects
1257
01:19:14.425 --> 01:19:18.525
is how to actually secure your like, the platform itself.
1258
01:19:19.860 --> 01:19:22.040
So the Raspberry Bolt guides
1259
01:19:22.420 --> 01:19:24.360
immediately recommends you to,
1260
01:19:24.820 --> 01:19:28.755
create your own SSH login keys. So there's, like, a passwordless
1261
01:19:29.215 --> 01:19:29.715
login.
1262
01:19:31.935 --> 01:19:33.395
You enable the firewall.
1263
01:19:33.855 --> 01:19:34.915
There's, like, a
1264
01:19:38.360 --> 01:19:40.060
fail to ban that does, like,
1265
01:19:40.760 --> 01:19:44.460
rate limiting on on login trials and stuff like that.
1266
01:19:45.225 --> 01:19:45.725
And
1267
01:19:46.425 --> 01:19:55.390
one thing I feel is sometimes overlooked as well even for local network use is that I think everything that is transmitted over the Internet or
1268
01:19:56.330 --> 01:19:58.110
to a browser, let's say, like that,
1269
01:19:59.690 --> 01:20:04.335
if it contains, like, sensitive information, it probably should go over h d GPS.
1270
01:20:05.594 --> 01:20:07.135
So not in plain text.
1271
01:20:07.514 --> 01:20:11.454
So it also immediately makes you install NGINX
1272
01:20:11.930 --> 01:20:12.670
reverse proxy,
1273
01:20:13.770 --> 01:20:14.270
server
1274
01:20:14.730 --> 01:20:17.630
that can then be used by all other applications
1275
01:20:18.010 --> 01:20:18.510
like,
1276
01:20:19.275 --> 01:20:22.574
write the lightning or mempool or whatever you use.
1277
01:20:23.915 --> 01:20:33.699
I think the drawback is that some from time to time, you get some scary warnings in the browser because you don't have, like, your official own domain with a proper SSL certificate.
1278
01:20:34.320 --> 01:20:36.420
So the browser cannot really verify
1279
01:20:38.425 --> 01:20:39.224
if the,
1280
01:20:39.945 --> 01:20:42.045
the the certificate is is valid.
1281
01:20:42.425 --> 01:20:44.764
But if you accept it once usually,
1282
01:20:46.140 --> 01:20:47.440
then the browser
1283
01:20:47.820 --> 01:20:51.760
stores that certificate, and then you have a, like, fully end to end encrypted
1284
01:20:52.300 --> 01:20:52.800
communication
1285
01:20:53.100 --> 01:20:54.640
with your pi even
1286
01:20:55.215 --> 01:20:56.035
with the browser.
1287
01:20:56.895 --> 01:21:01.795
So I it always made me look really cringe if you, like, log in to
1288
01:21:02.415 --> 01:21:03.440
a ready made,
1289
01:21:04.480 --> 01:21:05.940
full note. And it
1290
01:21:06.640 --> 01:21:11.540
sometimes actually showed your seed words, which is, like, super bad in the browser
1291
01:21:12.304 --> 01:21:15.045
over in in not even through SSL
1292
01:21:15.985 --> 01:21:18.244
or made you log in without
1293
01:21:18.545 --> 01:21:19.925
2FA or anything,
1294
01:21:20.440 --> 01:21:24.220
just like transmitting the password over clear text for every
1295
01:21:24.760 --> 01:21:27.925
smart fridge to to see? Yeah.
1296
01:21:29.985 --> 01:21:39.100
Yeah. Yeah. These these chapters, again, it's something, you know, which you can come back to anytime when you're setting up a a Linux server. Best practice is
1297
01:21:39.560 --> 01:21:41.260
to, you know, you run to VPS
1298
01:21:41.719 --> 01:21:47.054
and then what to do with it. I mean, these steps should be done on every kind of computer where you run anything
1299
01:21:47.835 --> 01:21:50.974
or or which has access to your network, which does have
1300
01:21:51.989 --> 01:21:55.270
computers, which don't do run anything. So it is,
1301
01:21:56.230 --> 01:21:58.010
it is a great part and very important.
1302
01:21:58.389 --> 01:22:00.489
SSL is absolutely and the and the
1303
01:22:00.975 --> 01:22:06.115
self signed certificate question, I mean, this is because you are not reaching out for a third party
1304
01:22:08.335 --> 01:22:09.460
to verify this
1305
01:22:09.860 --> 01:22:14.120
certificate with them or kind of or, like, ask the permission for
1306
01:22:15.460 --> 01:22:17.640
of a third party to use that certificate.
1307
01:22:17.945 --> 01:22:23.724
So then your browser won't be able to check with that third party that this is this is something official,
1308
01:22:24.264 --> 01:22:24.925
in quotes.
1309
01:22:25.784 --> 01:22:28.489
But then if you compare the numbers,
1310
01:22:28.790 --> 01:22:29.929
the fingerprints
1311
01:22:30.389 --> 01:22:31.849
can be verified, which
1312
01:22:32.150 --> 01:22:33.210
fingerprint you can
1313
01:22:33.590 --> 01:22:41.974
see on your machine serving the web page, and then you can compare it to the fingerprint which appears in your browser, which you can just see on that,
1314
01:22:43.270 --> 01:22:43.989
there is usually,
1315
01:22:44.469 --> 01:22:46.730
like, a lock icon next to the URL,
1316
01:22:47.750 --> 01:22:49.370
where you can see the certificate
1317
01:22:49.965 --> 01:22:51.905
and the details of the fingerprint.
1318
01:22:52.365 --> 01:22:57.585
That one you can compare to the to the server in your control, and then you can be completely
1319
01:22:58.380 --> 01:23:06.000
sure that it is coming from that place. It's similar as, similar to, like, verifying the signal or, like, a matrix peer.
1320
01:23:06.465 --> 01:23:09.525
Mhmm. But it happens with emojis in matrix, for example, isn't it?
1321
01:23:09.905 --> 01:23:10.965
So yeah.
1322
01:23:12.065 --> 01:23:12.565
Nice.
1323
01:23:13.105 --> 01:23:14.565
Yeah. And I think one
1324
01:23:15.600 --> 01:23:16.580
thing that we,
1325
01:23:17.440 --> 01:23:17.940
really,
1326
01:23:18.800 --> 01:23:23.060
narrowed the guide towards is that the the whole Raspberry Bolt,
1327
01:23:23.760 --> 01:23:24.580
node now
1328
01:23:25.135 --> 01:23:25.635
only,
1329
01:23:27.055 --> 01:23:28.755
runs over the Tor network.
1330
01:23:29.535 --> 01:23:34.880
So not every communication goes over Tor, but everything that is Bitcoin specific like lightning,
1331
01:23:35.440 --> 01:23:38.179
bitcoin, also all the remote login,
1332
01:23:38.560 --> 01:23:40.659
all the connections coming from the outside,
1333
01:23:41.280 --> 01:23:43.060
everything goes over Tor.
1334
01:23:43.440 --> 01:23:43.940
And
1335
01:23:45.285 --> 01:23:47.465
this is, of course, for privacy reasons.
1336
01:23:48.405 --> 01:23:50.185
We don't want to advertise
1337
01:23:50.565 --> 01:23:53.385
our own IP address, which can be geolocated
1338
01:23:53.685 --> 01:23:58.090
and tell the world, hey. At this house, there's there's somebody with Bitcoin.
1339
01:23:59.349 --> 01:24:01.750
But it's also if if I think back,
1340
01:24:03.095 --> 01:24:10.555
when people wanted to connect to their lightning note with there's, like, the the the universal plug and play
1341
01:24:10.935 --> 01:24:12.650
option in LME,
1342
01:24:13.190 --> 01:24:15.270
which mostly didn't work,
1343
01:24:15.670 --> 01:24:17.770
depending on your network setup.
1344
01:24:18.150 --> 01:24:20.970
It was, like, just a huge pain to
1345
01:24:21.574 --> 01:24:23.434
manually configure your router,
1346
01:24:24.855 --> 01:24:25.835
do, like, the
1347
01:24:26.454 --> 01:24:27.114
the dynamic
1348
01:24:27.415 --> 01:24:29.755
IP setup that you can actually reach
1349
01:24:30.460 --> 01:24:31.440
your own node
1350
01:24:31.900 --> 01:24:32.880
in your home
1351
01:24:33.420 --> 01:24:35.440
from the outside world,
1352
01:24:36.300 --> 01:24:40.805
basically going through your own router and then back to the node.
1353
01:24:41.185 --> 01:24:44.405
And this is so much easier if you just use Tor
1354
01:24:44.785 --> 01:24:49.045
because Tor just like calls from your notes to the outside world
1355
01:24:49.600 --> 01:24:50.740
into the Tor network.
1356
01:24:51.120 --> 01:24:52.180
It has its own,
1357
01:24:52.560 --> 01:24:53.540
onion address,
1358
01:24:54.000 --> 01:25:04.175
and that doesn't change. And everything is end to end encrypted in any case. So it's it's not only secure and, like, more private, but also much, much,
1359
01:25:04.795 --> 01:25:06.014
more user friendly
1360
01:25:06.450 --> 01:25:09.030
to to connect to your own node from anywhere.
1361
01:25:10.050 --> 01:25:12.950
Like, UX wise, it's it's extremely easy.
1362
01:25:14.425 --> 01:25:18.125
You don't have to do any, like, port forwarding or anything on your router. Exactly.
1363
01:25:18.745 --> 01:25:20.505
But it's worth noting that,
1364
01:25:20.905 --> 01:25:23.760
Tor does have some reliability issues. So,
1365
01:25:25.340 --> 01:25:29.120
you will experience those from time to time, and it can be quite slow.
1366
01:25:31.195 --> 01:25:32.815
I didn't have a full
1367
01:25:34.235 --> 01:25:39.375
I think I was always able to reach my note, but you're right. From time to time, it can be very slow.
1368
01:25:40.500 --> 01:25:46.200
And that can of course, if you're using, like, a web interface that with a lot of connections
1369
01:25:46.555 --> 01:25:49.375
a lot of images and stuff that can be very serious.
1370
01:25:50.075 --> 01:25:57.110
But, also, if you connect, like, your your wallet to your own Electrum server, If it needs to look up a lot of,
1371
01:25:57.570 --> 01:26:03.590
addresses and stuff like that, that is significantly slower than using just like a plain net,
1372
01:26:04.975 --> 01:26:06.755
electron server. That's true.
1373
01:26:09.135 --> 01:26:11.315
Yeah. When you are using the terminal, we can
1374
01:26:12.170 --> 01:26:15.070
feel the lag of typing. Yeah. True.
1375
01:26:16.570 --> 01:26:24.304
And now even, like, SSH over Tor is is in the standard guide. So you can log in to your command line from everywhere.
1376
01:26:25.485 --> 01:26:26.945
It's surprisingly easy.
1377
01:26:27.645 --> 01:26:35.310
Mhmm. But it's it's it's worth to note that it's also it's easy, but it's same easy for everyone else who knows that hidden address.
1378
01:26:35.690 --> 01:26:38.095
So when when it does leak,
1379
01:26:38.715 --> 01:26:40.255
that information somehow,
1380
01:26:41.035 --> 01:26:51.020
like, you were using a a couple of versions back. You were using Mhmm. The Brave Browser, for example, which then pinged the clear net DNS server
1381
01:26:51.400 --> 01:26:52.940
with the only an address.
1382
01:26:53.525 --> 01:26:56.745
So publicized it to the ISP or the VPN provider,
1383
01:26:58.085 --> 01:27:00.645
then, you know, someone else can kind of,
1384
01:27:01.605 --> 01:27:02.985
try to guess your password
1385
01:27:03.590 --> 01:27:04.570
or or the password
1386
01:27:04.949 --> 01:27:09.210
of the service, which is which is running behind that, hidden service.
1387
01:27:11.284 --> 01:27:12.905
I mean, there are ways to
1388
01:27:13.525 --> 01:27:15.225
use key authentication
1389
01:27:15.605 --> 01:27:17.864
with Tor as well just like with SSH.
1390
01:27:18.880 --> 01:27:22.020
It's a bit more kind of cumbersome, but if you're like using
1391
01:27:23.120 --> 01:27:26.020
using SSH, you already should use key authentication.
1392
01:27:27.245 --> 01:27:29.985
So just to be aware that this is like a public domain.
1393
01:27:31.085 --> 01:27:32.785
Like, having an Internet address
1394
01:27:33.245 --> 01:27:33.985
is just
1395
01:27:35.340 --> 01:27:46.545
it it's just running through the Tor network, which has I mean, there's a twist there. Right? Because it's it's I mean, it could be thought of similar to, like, Bitcoin keys, right, where it's it's locally generated.
1396
01:27:47.405 --> 01:27:50.945
Yes. There are so many possibilities that we can It's unguessable.
1397
01:27:51.565 --> 01:27:56.430
Right. No one can well, we can assume that no one has the capability of brute forcing
1398
01:27:57.210 --> 01:27:57.710
that,
1399
01:27:58.570 --> 01:28:10.315
specific onion address. But if it leaks, then you have you have issues on your hand because other people can use that onion address, and you wanna make sure that whatever authentication that is, if it's a strong password or whatnot,
1400
01:28:11.270 --> 01:28:15.690
that that is is secure enough that you're not gonna get brute force at that point.
1401
01:28:16.550 --> 01:28:22.355
Absolutely. This is also why it's passwordless login through, like, SSH keys only.
1402
01:28:22.895 --> 01:28:23.715
And the
1403
01:28:24.335 --> 01:28:27.795
that has failed to ban. I think if you try to log in
1404
01:28:28.960 --> 01:28:34.100
10 times in 5 minutes or so, you're just, like, immediately banned for 10 minutes or so.
1405
01:28:34.960 --> 01:28:36.740
So I would say SSH
1406
01:28:37.875 --> 01:28:40.135
itself is probably very secure.
1407
01:28:40.435 --> 01:28:44.295
Like, it's it's pretty common to have this port exposed.
1408
01:28:45.310 --> 01:28:51.650
But, of course, everything else should be secure as well. And I I think I read a a question in the very beginning why,
1409
01:28:52.350 --> 01:28:53.890
every web service
1410
01:28:54.454 --> 01:28:57.994
is now, like, separated and segregated into its own,
1411
01:28:58.375 --> 01:28:59.195
Linux user.
1412
01:28:59.974 --> 01:29:00.474
And
1413
01:29:01.094 --> 01:29:02.635
it it's not a perfect
1414
01:29:04.310 --> 01:29:04.810
protection,
1415
01:29:05.670 --> 01:29:06.650
but let's say
1416
01:29:07.030 --> 01:29:07.530
somebody
1417
01:29:08.230 --> 01:29:08.730
would,
1418
01:29:10.150 --> 01:29:10.650
find
1419
01:29:11.030 --> 01:29:11.610
a vulnerability
1420
01:29:11.989 --> 01:29:13.645
in, I don't know, whatever
1421
01:29:14.745 --> 01:29:18.285
whatever web service is reachable over Tor
1422
01:29:19.145 --> 01:29:23.005
and could gain access to to stuff it shouldn't have,
1423
01:29:23.580 --> 01:29:25.600
like SQL injection or whatever.
1424
01:29:26.140 --> 01:29:30.800
But that breach would still then be contained in this one
1425
01:29:31.340 --> 01:29:32.640
non root user
1426
01:29:33.825 --> 01:29:40.005
That that might be able to, for example, query Bitcoin Core, but it wouldn't have right access to anything.
1427
01:29:40.760 --> 01:29:44.860
So if an attacker would somehow get into,
1428
01:29:45.640 --> 01:29:49.100
your note, and I think every web service is a probably
1429
01:29:49.594 --> 01:29:52.495
is is a is a is a potential vulnerability.
1430
01:29:53.835 --> 01:29:59.215
It it still should be contained in that specific user, which basically doesn't have
1431
01:29:59.550 --> 01:30:04.690
right access to anything. It might be able to query some stuff, but it cannot do much damage.
1432
01:30:06.030 --> 01:30:15.595
Well, I and we could go with an example of, like, RTL, which is has its own user, the right lightning interface, which is awesome. And I'm I'm no way saying it's it's vulnerable,
1433
01:30:16.215 --> 01:30:17.835
but, you know, in a hypothetical
1434
01:30:18.780 --> 01:30:19.280
scenario,
1435
01:30:19.980 --> 01:30:21.760
if it would be. And
1436
01:30:22.780 --> 01:30:23.280
then
1437
01:30:24.139 --> 01:30:32.264
the attacker would possibly be able to extract the admin macaroon, for example, of to gain access to the funds on lightning. But,
1438
01:30:33.685 --> 01:30:34.344
I mean,
1439
01:30:35.445 --> 01:30:43.460
you wouldn't be able to access the other users, which, for example, there could be another hot wallet, for example, join markets running on the node,
1440
01:30:44.815 --> 01:30:46.594
under a separate user
1441
01:30:46.895 --> 01:30:49.315
with hot funds and keys there as well,
1442
01:30:50.014 --> 01:30:51.635
I mean, there is some protection,
1443
01:30:52.974 --> 01:30:53.474
against
1444
01:30:54.160 --> 01:30:54.820
that by
1445
01:30:55.440 --> 01:30:57.940
separating into different users,
1446
01:30:58.320 --> 01:31:02.179
especially if, you know, they have, like, web services running as well.
1447
01:31:03.145 --> 01:31:09.645
Yeah. Exactly. And I think this it's it's not perfect. It's not a silver bullet, but it's it's just best practice.
1448
01:31:10.025 --> 01:31:10.844
And I think the
1449
01:31:12.350 --> 01:31:15.890
because this is, like, handled directly by the operating system itself,
1450
01:31:16.430 --> 01:31:22.050
the the protection against, like, breaking out of that user is is much higher than, for example,
1451
01:31:23.215 --> 01:31:23.715
than
1452
01:31:24.335 --> 01:31:27.074
being able to break out of a Docker container,
1453
01:31:27.534 --> 01:31:28.034
which
1454
01:31:28.574 --> 01:31:32.420
many assume Docker is somehow, like, almost like a virtual machine
1455
01:31:32.880 --> 01:31:34.980
and give some security protection.
1456
01:31:35.599 --> 01:31:39.059
But because Docker actually runs as a pseudo user,
1457
01:31:39.625 --> 01:31:41.805
if you're able to break out of a Docker,
1458
01:31:42.425 --> 01:31:42.925
container,
1459
01:31:43.625 --> 01:31:45.085
that can be pretty serious.
1460
01:31:45.545 --> 01:31:47.965
So it's it's not really a security solution.
1461
01:31:49.300 --> 01:31:56.760
But I also need to say that I'm not no way an expert Docker expert. So Yeah. Yes. It's same as me. And I think most of these,
1462
01:31:57.945 --> 01:31:58.445
including,
1463
01:31:58.905 --> 01:31:59.965
you know, the user
1464
01:32:02.425 --> 01:32:04.605
separation and Docker containers,
1465
01:32:05.380 --> 01:32:10.280
system d services, and everything else, it depends a lot on how you use them.
1466
01:32:10.740 --> 01:32:15.205
And what we can do is is kind of provide the best
1467
01:32:15.745 --> 01:32:16.245
practices
1468
01:32:16.705 --> 01:32:17.525
as there is,
1469
01:32:18.625 --> 01:32:19.125
to,
1470
01:32:19.985 --> 01:32:23.810
you know, to use the tools available the best possible way.
1471
01:32:24.770 --> 01:32:25.510
You can
1472
01:32:27.250 --> 01:32:30.930
so, yeah, none of them are are are silver bullets, but,
1473
01:32:32.050 --> 01:32:33.590
you can do the job well.
1474
01:32:34.695 --> 01:32:36.875
So well, we already spent, like,
1475
01:32:37.335 --> 01:32:37.835
almost
1476
01:32:38.215 --> 01:32:42.395
1 and a half hours, and we're only in the preparation phase of the guide.
1477
01:32:44.520 --> 01:32:45.180
I mean,
1478
01:32:45.640 --> 01:32:46.860
as a quick overview,
1479
01:32:49.880 --> 01:33:00.415
now that the system is, like, ready, it's it's basically a a vanilla server now. It has everything that you need to run additional applications on that server.
1480
01:33:00.860 --> 01:33:03.760
And from it there, the guide goes on. You
1481
01:33:04.300 --> 01:33:05.520
download and
1482
01:33:05.980 --> 01:33:08.159
verify very, very importantly.
1483
01:33:08.965 --> 01:33:10.344
It explains exactly
1484
01:33:10.804 --> 01:33:13.225
step by step how you can verify,
1485
01:33:14.405 --> 01:33:17.864
the signatures of Bitcoin Core so that you know that
1486
01:33:18.410 --> 01:33:22.910
the Bitcoin Core you downloaded and are going to run is actually the official
1487
01:33:23.610 --> 01:33:24.110
vetted,
1488
01:33:25.610 --> 01:33:27.310
built of Bitcoin Core.
1489
01:33:28.355 --> 01:33:28.855
This
1490
01:33:29.235 --> 01:33:31.975
will sync with the whole network, download
1491
01:33:33.395 --> 01:33:37.469
the blockchain. Of course, you I guess everybody here knows that.
1492
01:33:38.969 --> 01:33:40.329
And on top of that,
1493
01:33:40.889 --> 01:33:43.949
we installed the Electrum Elektra's server.
1494
01:33:44.365 --> 01:33:48.545
So that actually makes it possible to then connect any,
1495
01:33:49.565 --> 01:33:50.065
wallet
1496
01:33:50.365 --> 01:33:51.905
to your own full node,
1497
01:33:52.449 --> 01:33:53.909
that supports the Electrum,
1498
01:33:54.449 --> 01:33:54.949
protocol,
1499
01:33:55.570 --> 01:33:57.750
be it harder wallets or,
1500
01:33:58.449 --> 01:34:00.550
any other third party wallet.
1501
01:34:01.835 --> 01:34:04.735
And very important for privacy reasons,
1502
01:34:05.355 --> 01:34:08.014
there's also the Bitcoin Explorer. Like, it's a
1503
01:34:08.715 --> 01:34:09.295
a minimal,
1504
01:34:09.830 --> 01:34:10.929
very lightweight,
1505
01:34:11.510 --> 01:34:13.290
Bitcoin blockchain explorer.
1506
01:34:13.750 --> 01:34:17.369
So you can actually look up everything, every block, every transaction
1507
01:34:17.830 --> 01:34:22.565
directly on your note. Because, otherwise, if you just go to any public,
1508
01:34:23.425 --> 01:34:27.205
blockchain explorer, of course, you're leaking a lot of private information
1509
01:34:27.660 --> 01:34:29.760
of what you're interested in. And
1510
01:34:30.620 --> 01:34:36.480
these third parties can then connect multiple addresses you with your IP address and all that stuff.
1511
01:34:38.045 --> 01:34:45.665
So this is this is where I come from. The Bitcoin part is really, really important for me. And once that is really set up,
1512
01:34:49.230 --> 01:34:49.969
the default,
1513
01:34:50.510 --> 01:34:51.010
lightning
1514
01:34:51.630 --> 01:34:53.650
client that is used is lnd,
1515
01:34:54.875 --> 01:34:57.455
which is pretty straightforward to set up.
1516
01:34:58.955 --> 01:35:03.135
And we also install right the lightning to actually make it manageable
1517
01:35:04.239 --> 01:35:06.900
through the browser. So you can manage your
1518
01:35:07.360 --> 01:35:09.620
lightning node, all the channels, everything.
1519
01:35:11.565 --> 01:35:16.625
And but this is just, like, the the core guide, the standard as it is now. There are many
1520
01:35:17.165 --> 01:35:17.665
bonus
1521
01:35:18.285 --> 01:35:18.765
guides.
1522
01:35:19.325 --> 01:35:20.785
There's are many
1523
01:35:21.100 --> 01:35:25.679
open poll requests actually for additional bonus guides for sea lightning,
1524
01:35:26.300 --> 01:35:27.920
for thunder hop,
1525
01:35:28.385 --> 01:35:30.245
for many other
1526
01:35:31.745 --> 01:35:32.245
applications
1527
01:35:33.025 --> 01:35:34.885
that we would like to include.
1528
01:35:35.840 --> 01:35:37.700
The goal is to have, like, one,
1529
01:35:38.560 --> 01:35:41.220
like, pretty minimal standard configuration,
1530
01:35:41.760 --> 01:35:47.765
but then you can put everything you want on top of that. So for example, join market or,
1531
01:35:49.905 --> 01:35:54.085
via guard VPN. We have an open pool request. Thunderhub, mempool,
1532
01:35:54.625 --> 01:35:55.010
bisque,
1533
01:35:56.289 --> 01:35:58.710
various management scripts, all that stuff.
1534
01:36:00.369 --> 01:36:01.110
And I think,
1535
01:36:02.130 --> 01:36:03.349
I mentioned that
1536
01:36:03.650 --> 01:36:06.455
it started as a, like, a personal project.
1537
01:36:07.155 --> 01:36:08.535
But I'm basically
1538
01:36:10.355 --> 01:36:12.909
I couldn't manage all the the contributions,
1539
01:36:13.210 --> 01:36:15.949
all the the issues anymore. And this is why
1540
01:36:16.489 --> 01:36:20.829
I now this is more this has transformed to a community project.
1541
01:36:21.285 --> 01:36:24.665
There are multiple maintainers now and many people
1542
01:36:25.045 --> 01:36:25.545
answering
1543
01:36:25.845 --> 01:36:27.385
all questions on GitHub.
1544
01:36:28.165 --> 01:36:28.665
And
1545
01:36:28.990 --> 01:36:29.570
I think
1546
01:36:30.590 --> 01:36:37.250
one thing is, telling that more people are actually interested in writing even more additional
1547
01:36:37.855 --> 01:36:38.835
bonus guides,
1548
01:36:39.215 --> 01:36:41.235
and we severely lack reviewers.
1549
01:36:42.015 --> 01:36:43.475
So if anyone here
1550
01:36:43.775 --> 01:36:45.075
is interested in
1551
01:36:45.790 --> 01:36:47.410
trying out some new stuff,
1552
01:36:47.790 --> 01:36:53.810
giving feedback on new bonus guides, that that'd be really a a great help.
1553
01:36:55.225 --> 01:37:01.645
Because in the end, if everybody's writing guides and I need to review review them all in the end,
1554
01:37:02.025 --> 01:37:03.725
that's not really going to scale.
1555
01:37:07.429 --> 01:37:11.449
Yeah. I do like the how the community has has been built.
1556
01:37:12.550 --> 01:37:13.050
Like,
1557
01:37:14.054 --> 01:37:14.554
really
1558
01:37:14.934 --> 01:37:16.235
I mean, there are some
1559
01:37:16.855 --> 01:37:17.355
names
1560
01:37:18.054 --> 01:37:20.074
we mentioned, like, definitely, like,
1561
01:37:22.140 --> 01:37:28.540
colleague under under the pseudonym of, like, Pillars of Indra. He's, like, coordinating lots of,
1562
01:37:29.205 --> 01:37:31.465
Yeah. Like, weekly reviews How about the chat?
1563
01:37:31.845 --> 01:37:32.665
Yeah. Exactly.
1564
01:37:33.845 --> 01:37:36.265
Weekly reviews on the r
1565
01:37:36.960 --> 01:37:38.559
slash recipe board on on,
1566
01:37:40.639 --> 01:37:41.860
Reddit, that is.
1567
01:37:42.239 --> 01:37:44.179
And there is this Telegram group
1568
01:37:45.945 --> 01:37:48.365
called the recipe board as well, which has
1569
01:37:49.065 --> 01:37:53.700
has picked up a lot of activity in the past couple of months, really. And I've been enjoying,
1570
01:37:54.080 --> 01:37:56.980
you know, lurking in there as well because, I mean, obviously,
1571
01:37:57.440 --> 01:38:01.300
there are a lot of solutions which, you know, I do learn from people who
1572
01:38:02.615 --> 01:38:03.675
trying to set up
1573
01:38:03.975 --> 01:38:05.595
their own note from the scratch.
1574
01:38:06.295 --> 01:38:06.955
And then,
1575
01:38:07.975 --> 01:38:10.875
you know, I do apply it myself as well.
1576
01:38:12.470 --> 01:38:19.655
So, yeah, it it it's worse to join these even if you are, you know, working with some other kind of system. Like, for example, verifying
1577
01:38:20.115 --> 01:38:22.215
the Bitcoin core signature or the other binaries,
1578
01:38:22.915 --> 01:38:23.975
PGP verification
1579
01:38:24.595 --> 01:38:28.370
is really something you can just come to when you are setting up
1580
01:38:28.850 --> 01:38:36.844
your Bitcoin node on your laptop and just wonder, oh, how how how how is how was that that I should verify this? And then you can go to the website,
1581
01:38:37.784 --> 01:38:38.684
and it's there.
1582
01:38:41.625 --> 01:38:44.320
That's, yeah, that's been a slight disconnected from the
1583
01:38:45.040 --> 01:38:49.380
comment from the community. I just wanted to note that, it's just so useful.
1584
01:38:50.480 --> 01:38:51.780
Absolutely. And
1585
01:38:52.885 --> 01:38:57.865
fun thing, for for a long time, I didn't even know there was a, a Raspberry Bolt subreddit
1586
01:38:59.125 --> 01:39:04.700
until they pinged me. So it it already had, like, over a 100 subscribers before I actually
1587
01:39:05.080 --> 01:39:07.260
got aware of it. That's awesome.
1588
01:39:10.945 --> 01:39:18.885
Gotta love when that just happens organically. Yeah. And I I cannot shout out enough to Indra and how he manages that stuff. He that's really awesome.
1589
01:39:22.769 --> 01:39:23.269
Great.
1590
01:39:24.449 --> 01:39:26.630
I mean, this has been a fantastic conversation.
1591
01:39:27.329 --> 01:39:29.655
We're about to hit an hour and 40 minutes.
1592
01:39:31.235 --> 01:39:34.455
Do you guys have anything else you wanna discuss before we wrap it up?
1593
01:39:36.790 --> 01:39:38.330
Do we have a hard limits here?
1594
01:39:39.190 --> 01:39:44.890
Yeah. I mean, let's I'm I'm aiming for the top of the hour, so we got 13 minutes. We got some time.
1595
01:39:48.785 --> 01:39:54.690
So I don't have anything pressing for me. It was it's it's a pleasure to to be here, talk with you, Matt, and,
1596
01:39:55.250 --> 01:39:56.390
open almost and
1597
01:39:57.410 --> 01:40:02.390
make, a little bit of noise for the recipe bolt guide. It's like my
1598
01:40:02.715 --> 01:40:03.855
my brainchild
1599
01:40:04.235 --> 01:40:08.335
that's that has now grown wings and is
1600
01:40:08.875 --> 01:40:13.660
I'm actually also happy that it's no longer only on my shoulders. So that's that's really good.
1601
01:40:15.000 --> 01:40:16.380
And, yeah, I mean,
1602
01:40:17.080 --> 01:40:27.255
anybody who's interested in, actually learning how a node works, I think it's a good place to stop by, have a look, maybe join the Telegram group or the subreddit.
1603
01:40:28.195 --> 01:40:31.300
And if you want to go ahead and try some stuff,
1604
01:40:32.260 --> 01:40:33.880
it's it's it's actually fun.
1605
01:40:35.380 --> 01:40:37.559
Don't be afraid of the command line.
1606
01:40:37.940 --> 01:40:43.054
It's good to to be overwhelmed. It's it's more accessible than than you would expect.
1607
01:40:44.155 --> 01:40:50.870
I mean, I appreciate you both. I appreciate your work. It sounded to me like Open Arms had something you wanted to talk about. You got something for us, Open Arms?
1608
01:40:52.690 --> 01:40:54.070
Well, I just keep commenting
1609
01:40:54.530 --> 01:40:55.590
as things come
1610
01:40:57.010 --> 01:41:00.165
up. You know, these are my favorite topics, so definitely.
1611
01:41:02.785 --> 01:41:03.845
Live and breathe.
1612
01:41:05.910 --> 01:41:07.450
No. I mean, this has been fantastic.
1613
01:41:09.510 --> 01:41:13.130
I guess let's just end it with some final thoughts. Final thoughts, open arms.
1614
01:41:13.430 --> 01:41:14.090
Hit us.
1615
01:41:17.405 --> 01:41:18.385
Run your nose
1616
01:41:18.845 --> 01:41:19.985
and use it.
1617
01:41:22.540 --> 01:41:25.199
Yes. I love it. Short and sweet. Thank you.
1618
01:41:26.699 --> 01:41:28.080
Staticus, final thoughts.
1619
01:41:29.715 --> 01:41:34.135
I cheer for every note that is actually, like, used in the wild,
1620
01:41:35.475 --> 01:41:36.535
be it for lightning
1621
01:41:36.915 --> 01:41:37.415
or
1622
01:41:38.300 --> 01:41:38.960
I think
1623
01:41:39.900 --> 01:41:41.120
all sometimes overlooked
1624
01:41:41.660 --> 01:41:46.640
even more importantly to verify your own, like, large transactions coming in,
1625
01:41:47.054 --> 01:41:48.675
typically going to hardware wallets.
1626
01:41:49.375 --> 01:41:50.755
So having your own
1627
01:41:51.375 --> 01:41:53.155
definite truth of
1628
01:41:53.775 --> 01:41:57.780
what's the state of the blockchain. And if you actually got
1629
01:41:58.160 --> 01:42:03.060
genuine Bitcoin, I think that's something every true Bitcoiner should be able to do.
1630
01:42:04.445 --> 01:42:05.345
Thank you, Statikis.
1631
01:42:06.285 --> 01:42:16.100
Yes. To interact with the Bitcoin network, you're gonna need to use a Bitcoin node. If you're not using your own Bitcoin node, you're using someone else's Bitcoin node and you're trusting them with your privacy
1632
01:42:16.720 --> 01:42:24.065
and verification of your Bitcoin. Whether that is real Bitcoin, whether the rules that you think the network is following are actually being followed.
1633
01:42:24.845 --> 01:42:29.619
That is enforced by the node that you are using. So if you're using someone else's node,
1634
01:42:30.320 --> 01:42:32.580
you are trusting them with that responsibility.
1635
01:42:34.080 --> 01:42:36.500
With all that said, this was an absolutely fantastic
1636
01:42:36.935 --> 01:42:39.435
conversation. I wanna thank our guests once again.
1637
01:42:40.135 --> 01:42:43.195
I hope to have you both back on at some time soon.
1638
01:42:44.580 --> 01:42:47.480
Open Arms, I think you're number 1 most
1639
01:42:48.100 --> 01:42:51.400
you you've been on the show more than anyone else besides me.
1640
01:42:51.995 --> 01:42:56.335
So I really do appreciate you taking the time out to to come on every time,
1641
01:42:56.875 --> 01:42:59.740
and I look forward to whatever interesting topic,
1642
01:43:00.140 --> 01:43:02.240
our next conversation will be based on.
1643
01:43:02.700 --> 01:43:10.835
As always, I wanna thank the freaks for joining us, for this conversation. I hope you all enjoyed it. Your feedback is always appreciated. You can contact me,
1644
01:43:12.094 --> 01:43:12.335
via
1645
01:43:12.975 --> 01:43:14.995
all my contact information is at mattodel.com.
1646
01:43:16.239 --> 01:43:19.699
You can support the show and see previous episodes at silldispatch.com.
1647
01:43:20.480 --> 01:43:22.739
You can also support the show via merch,
1648
01:43:23.655 --> 01:43:24.395
at silodispatch.com/stack.
1649
01:43:26.775 --> 01:43:29.114
With all that said, I love you all.
1650
01:43:29.815 --> 01:43:31.195
Thank you, guys. Cheers.
1651
01:43:33.520 --> 01:43:36.980
Cheers. It's been a pleasure. Yeah. Thanks a lot. It's Sandro again.
1652
01:47:46.475 --> 01:47:49.855
Love you, freaks. Hope you enjoyed that conversation as much as I did.
1653
01:47:50.395 --> 01:47:54.574
I'll see you up for rabbit hole recap on Thursday at 2:30 EST, 19:30
1654
01:47:54.955 --> 01:47:55.455
UTC,
1655
01:47:56.400 --> 01:48:00.340
and we have another Citadel dispatch on Tuesday 18th
1656
01:48:01.120 --> 01:48:09.835
at 5 EST, 22 100 UTC. That's gonna be a really fun conversation on KYC and different trade offs with Zelco, Diverter, LaserHodl,
1657
01:48:10.295 --> 01:48:16.090
and Stefan Lovera, so make sure to tune in for that. I think it's gonna be a lot of fun and a good discussion.
1658
01:48:17.510 --> 01:48:19.449
As many of you know, I've been helping
1659
01:48:20.045 --> 01:48:20.785
Bitcoin Magazine,
1660
01:48:21.485 --> 01:48:24.145
put together their upcoming Bitcoin conference,
1661
01:48:25.085 --> 01:48:26.465
April 6th through 9th
1662
01:48:27.005 --> 01:48:27.825
in Miami.
1663
01:48:28.920 --> 01:48:32.300
Just a little heads up that prices do increase on Friday.
1664
01:48:33.160 --> 01:48:36.775
So if you haven't bought a ticket, you're considering doing it, you know, I am helping them
1665
01:48:37.094 --> 01:48:42.155
significantly with the programming for the open source stage. There's gonna be a lot of really good discussions there,
1666
01:48:43.815 --> 01:48:51.340
both on the 2 GA days, but also on industry day. Before the 2 GA days, we're going to be doing a very highly technical
1667
01:48:51.880 --> 01:48:53.020
focused discussions.
1668
01:48:53.639 --> 01:49:01.965
That's gonna be almost bit dev style. So if you haven't bought a ticket, you're considering buying a ticket, I was able to secure us, the code open source.
1669
01:49:02.665 --> 01:49:04.525
Do not share that code on Twitter.
1670
01:49:05.180 --> 01:49:07.120
I do not get a cut from that code.
1671
01:49:07.900 --> 01:49:12.480
It all goes to you. It's a full 21% off. So do not share it on Twitter. Otherwise,
1672
01:49:13.525 --> 01:49:16.344
they told me they will disable it. So cheers.
1673
01:49:16.645 --> 01:49:19.065
Love you all. Stay on with Stacks ads.
NOTE
Transcription provided by Podhome.fm
Created: 3/17/2024 8:08:42 PM
Duration: 6561.698
Channels: 1
1
00:00:01.599 --> 00:00:09.780
2
00:00:10.304 --> 00:00:14.724
that has this kind of track record? Number 1, is so is very, very under penetrated,
3
00:00:15.424 --> 00:00:19.925
can provide a service of insurance against financial catastrophe that no one else can provide,
4
00:00:20.529 --> 00:00:29.189
and, and can go up 10 times or 50 times. The answer is nothing. Why Bill Miller has gone big on Bitcoin is on Consuelo Mack WealthTrack.
5
00:00:29.645 --> 00:00:37.185
6
00:00:37.660 --> 00:00:42.559
As longtime WEALTHTRACK viewers know, Miller has been a guest of ours since our launch in 2,005
7
00:00:43.579 --> 00:00:45.920
and doesn't do many TV interviews.
8
00:00:46.325 --> 00:00:47.625
As he told me recently,
9
00:00:48.004 --> 00:00:53.225
time is his scarcest resource. So we are delighted that he is with us again this week.
10
00:00:53.590 --> 00:00:57.690
Miller is the founder, owner and chief investment officer of Miller Value Partners,
11
00:00:57.990 --> 00:00:59.850
a firm he founded in 1999
12
00:01:00.605 --> 00:01:04.545
while working at Legg Mason, but took over completely in 2017.
13
00:01:05.805 --> 00:01:08.225
As most of you know, Miller holds the unbeaten
14
00:01:09.520 --> 00:01:10.580
S and P 500
15
00:01:10.960 --> 00:01:12.260
for 15 consecutive
16
00:01:12.560 --> 00:01:14.020
years from 1991
17
00:01:14.560 --> 00:01:15.140
to 2,005
18
00:01:15.875 --> 00:01:23.174
with the Legg Mason Capital Management Value Trust Fund. His flagship, Miller Opportunity Trust Fund, which he created in 1999
19
00:01:23.830 --> 00:01:26.970
and has co managed with Samantha Macklemore since 2014,
20
00:01:27.990 --> 00:01:28.650
has $2,400,000,000
21
00:01:29.590 --> 00:01:34.915
in assets and has had many market beating years interspersed with some sizable declines.
22
00:01:35.375 --> 00:01:41.155
But today's conversation is not about Miller Opportunity Trust. It's about his personal portfolio.
23
00:01:41.720 --> 00:01:42.780
And here's the headline.
24
00:01:43.479 --> 00:01:48.140
Half of Miller's personal net worth is in bitcoin and a few other cryptocurrency
25
00:01:48.840 --> 00:01:49.340
investments.
26
00:01:49.825 --> 00:01:51.045
And it's leveraged.
27
00:01:51.505 --> 00:01:54.645
I asked Miller why he has gone so big on Bitcoin
28
00:01:54.945 --> 00:01:56.645
in his personal account.
29
00:01:57.180 --> 00:02:03.520
30
00:02:04.095 --> 00:02:08.095
you know, it's it it goes against many of the tenants of, of,
31
00:02:08.815 --> 00:02:09.955
financial discipline.
32
00:02:10.975 --> 00:02:13.155
On the other hand, the the people that actually
33
00:02:13.660 --> 00:02:15.360
are the richest people in the country,
34
00:02:15.740 --> 00:02:18.080
all are massively concentrated. You know,
35
00:02:18.459 --> 00:02:21.120
Buffett and Berkshire, Jeff Bezos, Mark Zuckerberg.
36
00:02:21.655 --> 00:02:25.435
So they're not they're not widely diversified, but they may be they're they're highly concentrated.
37
00:02:25.894 --> 00:02:35.070
And I think that's because they have a high degree of confidence or or have a high degree of confidence in the in the value of those investments. But my my thinking here was that,
38
00:02:36.010 --> 00:02:40.995
I I heard a talk on on Bitcoin given by the person who's known as patient 0
39
00:02:41.375 --> 00:02:43.715
in the Bitcoin world, Wences Casares.
40
00:02:44.495 --> 00:02:44.815
And,
41
00:02:45.615 --> 00:02:46.115
Wences
42
00:02:46.810 --> 00:02:50.510
gave a talk at at the Allen Company Sun Valley Conference,
43
00:02:50.810 --> 00:02:53.230
and he let off his talk. This is 2014,
44
00:02:53.530 --> 00:02:54.430
I wanna say.
45
00:02:54.890 --> 00:03:01.614
He let off his talk by saying that they're asking how anybody owned Bitcoin. No. Nobody in the audience owned it except for him.
46
00:03:01.915 --> 00:03:06.175
And did anybody know what it was? And a few scattered hands went up.
47
00:03:07.360 --> 00:03:09.599
And he said, well, let me explain to you,
48
00:03:10.480 --> 00:03:11.780
why I own Bitcoin.
49
00:03:12.239 --> 00:03:13.439
And he said, and it's because
50
00:03:13.945 --> 00:03:17.565
I I understand why you wouldn't understand it because you all live in America,
51
00:03:18.105 --> 00:03:22.125
and you have a rule of law, and you have, you know, orderly governments.
52
00:03:22.860 --> 00:03:27.680
And in most in most times, you have, you know, low relatively low inflation and a prosperous economy.
53
00:03:28.220 --> 00:03:30.400
And he said, but I'm from Argentina,
54
00:03:30.845 --> 00:03:41.290
and my family's been there a 150 years. And we've been wiped out 4 separate times by the Argentinian government seizing our assets, nationalizing the banks, inflating us out with hyperinflation.
55
00:03:42.069 --> 00:03:43.370
And he said, so Bitcoin
56
00:03:43.750 --> 00:03:45.450
can't be touched by the government.
57
00:03:45.750 --> 00:03:48.010
It's a it's a peer to peer decentralized
58
00:03:48.470 --> 00:03:48.970
independent
59
00:03:49.715 --> 00:03:53.815
network. It's a ledger that records every transaction that's public. It's immutable.
60
00:03:54.355 --> 00:04:03.800
And he said, so the government if you have Bitcoin, the government cannot take it away from you. And he he said, so it's it's an think of it as an insurance policy.
61
00:04:04.500 --> 00:04:11.314
And he went into it and talked about it. And I thought, you know and he talked about putting 1% of your liquid net worth in Bitcoin, and I thought that was sensible.
62
00:04:11.775 --> 00:04:17.235
He laid out what it what it could do if it worked. He he said then that it was very risky because then it was about $200.
63
00:04:17.760 --> 00:04:19.620
But I I bought some then and
64
00:04:19.920 --> 00:04:22.020
I bought a little bit more over time and it became
65
00:04:22.400 --> 00:04:29.104
$500, and then I stopped buying it. And I didn't buy it for years until just the spring of this year. It hit a $66,000
66
00:04:30.685 --> 00:04:31.425
high price.
67
00:04:31.805 --> 00:04:33.985
And then in 4 weeks, it was in half.
68
00:04:34.639 --> 00:04:37.060
Now Bitcoin has gone up on average a 170%
69
00:04:37.440 --> 00:04:39.220
a year for the last 11 years.
70
00:04:39.600 --> 00:04:44.555
Now but that's not every year. It's just an average. It's gone down 3 different times by more than 80%.
71
00:04:45.414 --> 00:04:57.090
So that's that is, you know, a very volatile and therefore very dangerous if you're especially if you're levered. You can be if you're on some of these exchanges. They'll loan you 50 to 1 on on your Bitcoin.
72
00:04:57.550 --> 00:04:58.050
But
73
00:04:58.865 --> 00:05:05.365
each time it's been stopped at around the 80 low eighties level, and it's come back. And this this time, I started buying it again at $30,000
74
00:05:05.985 --> 00:05:06.965
down from 66.
75
00:05:07.570 --> 00:05:08.310
And my reasoning was
76
00:05:09.010 --> 00:05:28.060
there's a lot more people using it now. There's a lot more money going into it in the venture capital world. There are a lot of people who are skeptics who are now at least, trying it out. And, and I thought maybe maybe 50% is a good stopping point for it. But if it goes about down 80 or 85, I'll buy it all the way down. Well, it did stop right around 50% and slowly started its way
77
00:05:28.680 --> 00:05:31.979
back up again. But I I bought a fair amount, at, you know, at the $30,000
78
00:05:32.440 --> 00:05:35.775
range and have been adding to various Bitcoin related,
79
00:05:36.715 --> 00:05:38.255
investments since then.
80
00:06:11.675 --> 00:06:13.615
81
00:06:13.915 --> 00:06:16.575
It's your boy Odell here for Citadel dispatch
82
00:06:17.680 --> 00:06:24.900
50. It's been 50 Citadel Dispatches. Let's fucking go. I hope you guys appreciated the little cameo by my dogs,
83
00:06:25.680 --> 00:06:27.105
during that intro clip.
84
00:06:27.745 --> 00:06:33.845
City of Dispatch is an interactive live show about Bitcoin distributed systems, privacy, and open source software.
85
00:06:36.060 --> 00:06:40.720
I want to do a quick shout out to all the supporters of the show who keep this show,
86
00:06:41.500 --> 00:06:45.280
ad free and sponsor free, focused purely on actionable Bitcoin discussion.
87
00:06:46.215 --> 00:06:49.995
You guys make this show possible, and I really do appreciate all the support.
88
00:06:50.695 --> 00:06:56.210
The easiest way to support the show is via podcasting 2 point o apps. My two favorite are fountain podcasts
89
00:06:56.750 --> 00:06:57.889
and Breeze Wallet.
90
00:06:58.349 --> 00:07:09.545
You simply download the app, load it up with sats, search for serial dispatch, and then while you listen, to the podcast, you're able to stream Sats directly to my note. It's really fucking cool.
91
00:07:10.889 --> 00:07:13.470
Literally, any day of the week, I can just sign in.
92
00:07:13.849 --> 00:07:25.115
I can just open up my my Bitcoin node, and I just see a ton of I just I just see SAP payments coming in, you know, 3 sats per minute, 5 sats per minute, 20 sats per minute,
93
00:07:25.575 --> 00:07:27.515
just streaming into my node. It's really
94
00:07:27.990 --> 00:07:31.050
really cool, rewarding experience to to see that happen.
95
00:07:32.070 --> 00:07:33.290
And also, as always,
96
00:07:33.590 --> 00:07:37.610
huge shout out to the freaks who join us in the live chat every week.
97
00:07:38.345 --> 00:07:42.445
You can access the live chat through the Twitter, YouTube, and Twitch streams.
98
00:07:44.265 --> 00:07:45.165
You can also
99
00:07:45.545 --> 00:07:45.785
view
100
00:07:47.150 --> 00:07:51.650
this is the first little dispatch that you're able to view it directly on bitcoin tv.com
101
00:07:51.950 --> 00:07:54.050
as well. Unfortunately, if you participate
102
00:07:55.095 --> 00:07:59.675
in the livestream through Bitcoin TV, you cannot actually be a part of the live chat.
103
00:08:00.775 --> 00:08:05.000
Gonna try and figure out a way to to make that work, but it is an option now.
104
00:08:05.800 --> 00:08:06.620
And as always,
105
00:08:07.000 --> 00:08:11.180
you can listen to the podcast, on your favorite podcasting app,
106
00:08:11.560 --> 00:08:13.980
by just searching Citadel Dispatch or
107
00:08:14.305 --> 00:08:15.845
watching the archives on bitcointv.com,
108
00:08:17.025 --> 00:08:18.405
YouTube, and Twitch.
109
00:08:19.025 --> 00:08:20.305
So with all that said,
110
00:08:20.785 --> 00:08:24.360
this is an episode that I am very excited about.
111
00:08:24.980 --> 00:08:26.680
It should be a really fun conversation.
112
00:08:27.380 --> 00:08:28.200
We have
113
00:08:28.580 --> 00:08:30.920
long time many time guest,
114
00:08:31.625 --> 00:08:34.285
Open Arms here with us. Open Arms, how's it going?
115
00:08:35.225 --> 00:08:37.645
116
00:08:38.870 --> 00:08:41.589
117
00:08:42.630 --> 00:08:43.610
we have Statikus,
118
00:08:44.310 --> 00:08:46.970
lead maintainer of the raspi bolt project here.
119
00:08:47.355 --> 00:08:48.975
The focus of today's conversation
120
00:08:49.355 --> 00:08:53.694
will be Bitcoin nodes and specifically the raspi bolt project. How's it going, Staticus?
121
00:08:54.555 --> 00:08:56.415
122
00:08:57.149 --> 00:08:57.649
123
00:08:57.950 --> 00:09:03.970
Well, let's fucking do this. So where do you guys wanna start? What is the raspybold project, and why should people care?
124
00:09:05.685 --> 00:09:09.144
125
00:09:09.445 --> 00:09:11.545
to understand where the Raspberry Bolt
126
00:09:12.404 --> 00:09:13.225
comes from,
127
00:09:14.870 --> 00:09:15.449
I think
128
00:09:15.829 --> 00:09:19.850
it's important to realize that it's it's it's been my personal project
129
00:09:20.310 --> 00:09:21.370
for a long time.
130
00:09:21.990 --> 00:09:23.610
So it's basically me
131
00:09:24.165 --> 00:09:25.705
documenting my own learnings.
132
00:09:26.405 --> 00:09:31.705
This is why it started out as a medium article back in the days, like, I don't know, 2017
133
00:09:32.165 --> 00:09:32.905
or so,
134
00:09:33.730 --> 00:09:35.030
how to set up
135
00:09:36.770 --> 00:09:40.230
a bitcoin full node with lightning on a Raspberry Pi.
136
00:09:41.145 --> 00:09:45.005
So back then, there was that wasn't really a thing. So I just
137
00:09:45.385 --> 00:09:48.605
tried to figure it out myself, had some other
138
00:09:49.030 --> 00:09:52.890
articles. Damien Me, for example, had some cool stuff online.
139
00:09:53.830 --> 00:09:57.210
But it just grew from there. I moved it over to GitHub,
140
00:09:59.464 --> 00:10:00.285
started answering
141
00:10:00.904 --> 00:10:04.125
issues and pull requests, all that stuff.
142
00:10:04.584 --> 00:10:06.045
So it's still a guide.
143
00:10:06.819 --> 00:10:09.560
It's not something you can download. It's really,
144
00:10:10.500 --> 00:10:12.120
something you do yourself.
145
00:10:13.220 --> 00:10:13.720
But
146
00:10:14.665 --> 00:10:15.165
it's,
147
00:10:15.704 --> 00:10:17.644
I think, a pretty decent
148
00:10:19.464 --> 00:10:20.605
reference guide
149
00:10:20.985 --> 00:10:23.620
how to set up the Raspberry Pi
150
00:10:24.160 --> 00:10:26.339
Bitcoin full node you want to have
151
00:10:26.800 --> 00:10:28.180
and build yourself.
152
00:10:31.045 --> 00:10:31.545
153
00:10:32.805 --> 00:10:33.365
we had
154
00:10:34.725 --> 00:10:35.945
I think we've had,
155
00:10:37.190 --> 00:10:38.970
I mean, I had open arms on
156
00:10:39.670 --> 00:10:40.970
the show to discuss.
157
00:10:41.750 --> 00:10:46.085
We had a big panel with a bunch of the leading node project implementations
158
00:10:46.465 --> 00:10:47.365
in terms of
159
00:10:49.585 --> 00:10:51.905
these actual dedicated 247 nodes,
160
00:10:53.330 --> 00:10:59.270
that you run on dedicated hardware, oftentimes Raspberry Pi, sometimes, you know, other single board chips.
161
00:11:01.045 --> 00:11:03.225
We had that. We also had,
162
00:11:04.805 --> 00:11:06.585
Nix Bitcoin on separately.
163
00:11:07.525 --> 00:11:10.005
So the freaks are very much aware of,
164
00:11:10.570 --> 00:11:14.269
this this concept of running a, you know, a a 247
165
00:11:14.649 --> 00:11:15.709
Bitcoin node,
166
00:11:16.649 --> 00:11:17.550
on a
167
00:11:17.930 --> 00:11:18.990
dedicated machine
168
00:11:19.875 --> 00:11:21.095
that is cheap hardware.
169
00:11:22.755 --> 00:11:23.255
So
170
00:11:24.035 --> 00:11:30.600
I'm I'm looking forward to diving deep in the weeds here. I I think, you know, most of the freaks are prepared for that and enjoy that type of conversation.
171
00:11:31.540 --> 00:11:33.320
But before we get there, I mean,
172
00:11:34.180 --> 00:11:37.560
it is almost it has been normalized. Somehow, it's been normalized,
173
00:11:39.205 --> 00:11:46.585
in a good way, this this concept. But when Raspberry Bolt when you first started working on on the Raspberry Bolt project,
174
00:11:47.829 --> 00:11:48.230
I
175
00:11:48.630 --> 00:11:50.570
was was it the first main,
176
00:11:52.470 --> 00:11:55.529
I guess, guide or project to run a raspi
177
00:11:56.584 --> 00:11:57.084
lightning
178
00:11:58.985 --> 00:12:01.404
179
00:12:02.345 --> 00:12:03.324
There are
180
00:12:04.310 --> 00:12:04.810
articles
181
00:12:05.350 --> 00:12:10.890
back then, but that were more like one time things. So not ongoing projects.
182
00:12:11.750 --> 00:12:12.250
And
183
00:12:13.655 --> 00:12:14.875
I I did that myself,
184
00:12:15.335 --> 00:12:19.755
on medium. But I think as soon as I moved it over to GitHub and,
185
00:12:20.135 --> 00:12:22.320
like, did continuous improvements,
186
00:12:22.699 --> 00:12:23.199
updates,
187
00:12:24.620 --> 00:12:30.320
seem to it that all the download links are always up to date. I think back then, it was the first
188
00:12:31.965 --> 00:12:32.465
live
189
00:12:32.845 --> 00:12:34.705
guide, if you can say that.
190
00:12:35.245 --> 00:12:37.425
That was always up to date and actually
191
00:12:38.500 --> 00:12:43.399
started to to get some, like, people involved and follow follow along.
192
00:12:47.435 --> 00:12:52.335
193
00:12:54.370 --> 00:12:58.790
194
00:12:59.410 --> 00:13:05.255
I started tinkering. So I've been working with Raspberry Pis for a long time for my
195
00:13:05.795 --> 00:13:10.190
streaming client for retro Pis for console games and stuff like that.
196
00:13:11.310 --> 00:13:12.530
So I was basically
197
00:13:13.070 --> 00:13:20.055
pissed off that every time I wanted to connect to pit Bitcoin core, I first had to sync, like, I don't know, hours
198
00:13:20.515 --> 00:13:21.395
until I could,
199
00:13:22.515 --> 00:13:25.575
verify my own transactions. So it came naturally
200
00:13:26.115 --> 00:13:29.095
to this concept of a 247 note,
201
00:13:29.709 --> 00:13:32.690
and building on a Raspberry Pi for me was pretty natural.
202
00:13:33.550 --> 00:13:36.209
And that was also, I think, in the summer of 2017,
203
00:13:36.990 --> 00:13:41.635
like, during the block size wars. Like, there was UASF, the Node Fix movement.
204
00:13:42.255 --> 00:13:45.315
And that also got me, like, thinking and appreciating
205
00:13:46.095 --> 00:13:46.755
a lot
206
00:13:47.550 --> 00:13:48.530
how important
207
00:13:48.990 --> 00:13:53.170
running your own Bitcoin node is for keeping Bitcoin decentralized.
208
00:13:54.110 --> 00:13:59.925
I think this is why I also started to dig deeper into it and all also started to publicly,
209
00:14:00.625 --> 00:14:01.845
document my learnings.
210
00:14:05.710 --> 00:14:07.250
211
00:14:08.270 --> 00:14:08.930
I guess
212
00:14:09.950 --> 00:14:12.690
yeah. So, I mean, it's been about probably, like, 3 years,
213
00:14:13.070 --> 00:14:13.570
since
214
00:14:13.895 --> 00:14:15.915
Raspberry Bolt, first started.
215
00:14:16.695 --> 00:14:23.410
216
00:14:24.209 --> 00:14:26.709
then. And I actually started it with Eclair.
217
00:14:30.290 --> 00:14:36.815
But I think LND then was the 1st lightning implementation that switched to mainnet. So
218
00:14:37.675 --> 00:14:38.415
I basically
219
00:14:38.875 --> 00:14:39.375
just
220
00:14:39.950 --> 00:14:41.490
kicked out Eclair and,
221
00:14:42.190 --> 00:14:43.890
switched to LND back then.
222
00:14:45.070 --> 00:14:51.214
223
00:14:51.515 --> 00:14:53.615
That it was just first to go mainnet.
224
00:14:54.714 --> 00:14:59.720
225
00:15:00.820 --> 00:15:04.840
common to use WebSockets. So if if you look at c lightning,
226
00:15:05.394 --> 00:15:06.675
you use, like,
227
00:15:07.154 --> 00:15:18.040
Linux sockets and stuff like that. I think it's much harder to build a web application on top of that. And LND just was, like, more familiar, I think, to whole to the whole deaf community.
228
00:15:18.820 --> 00:15:19.320
Cool.
229
00:15:21.445 --> 00:15:23.945
230
00:15:25.845 --> 00:15:30.825
231
00:15:31.670 --> 00:15:37.690
I I posted in the chat about, the history of lightning from brainstorm to beta. So, basically, it goes
232
00:15:38.795 --> 00:15:39.375
as it
233
00:15:39.835 --> 00:15:40.335
as
234
00:15:40.795 --> 00:15:43.375
it goes through the history, it's basically 2018,
235
00:15:43.915 --> 00:15:45.055
March 20
236
00:15:45.675 --> 00:15:46.760
28th when,
237
00:15:47.800 --> 00:15:52.060
when multiple implementations are going to main net and and there is
238
00:15:52.840 --> 00:15:55.340
a transaction between c lightning and lnd.
239
00:15:55.675 --> 00:15:58.575
So that's kind of the start of of of the main net
240
00:15:59.195 --> 00:15:59.695
network.
241
00:16:00.635 --> 00:16:01.935
And have you know that
242
00:16:02.779 --> 00:16:10.880
the test net was very active before then and obviously before, like, even Segwit activated. And the recipe board was then there to kind of
243
00:16:12.774 --> 00:16:17.274
try it out and buy a blocaccino, as you say in the guide. I think it's right here.
244
00:16:17.654 --> 00:16:20.475
So Fantastic. So that's been, yeah, that's been something
245
00:16:21.900 --> 00:16:26.000
I've been looking at during that period. And then, you know, pretty much
246
00:16:26.620 --> 00:16:29.975
this summer after or, like, you know, like, after March,
247
00:16:30.435 --> 00:16:33.175
I did build the did build the recipe both myself.
248
00:16:33.635 --> 00:16:36.455
And, looking at my GitHub, I I fold fold
249
00:16:36.835 --> 00:16:46.335
the guide and the, like, the extras repo in, like, in beginning of August 2018. So splitting up it's been there and already the community was building then.
250
00:16:46.895 --> 00:16:52.335
Mhmm. So it's, it's been great. All the reckless hashtag I can remember. And, also, I was,
251
00:16:52.895 --> 00:17:00.930
you know, losing some channels without any kind of backup then, and, you know, it's just because of a power glitch and stuff like that.
252
00:17:01.310 --> 00:17:03.170
So it was definitely reckless indeed.
253
00:17:04.095 --> 00:17:06.915
254
00:17:07.215 --> 00:17:09.075
it was pretty easy to already
255
00:17:09.455 --> 00:17:09.955
switch
256
00:17:10.370 --> 00:17:15.270
to main net if you wanted to, but you had to do some code changes and compile it yourself.
257
00:17:15.730 --> 00:17:19.670
And the developers really backed the community not to do that.
258
00:17:20.455 --> 00:17:23.035
And I also respected that and did not
259
00:17:23.414 --> 00:17:25.275
provide instructions on how
260
00:17:26.054 --> 00:17:27.835
to go on main net before,
261
00:17:28.135 --> 00:17:28.520
like,
262
00:17:29.080 --> 00:17:32.860
the developers gave their their go ahead, and they felt comfortable
263
00:17:33.800 --> 00:17:37.980
with, like, being only reckless, not reckless reckless.
264
00:17:38.404 --> 00:17:39.044
265
00:17:39.365 --> 00:17:47.945
well, I guess, first off, for the the freaks because I already put it up on the screen for those watching the video. But for the freaks listening into the podcast feeds,
266
00:17:49.740 --> 00:17:50.960
you can it's raspibolt.org.
267
00:17:52.620 --> 00:17:54.320
Very easy to remember domain.
268
00:17:56.305 --> 00:17:59.525
All the materials are neatly laid out on that website,
269
00:17:59.985 --> 00:18:02.085
so go check that out after the show.
270
00:18:04.190 --> 00:18:06.210
Yeah. I mean, the whole the whole reckless
271
00:18:06.990 --> 00:18:07.490
meme
272
00:18:07.950 --> 00:18:09.570
when lightning went mainnet,
273
00:18:11.470 --> 00:18:12.450
seemed very
274
00:18:14.575 --> 00:18:19.475
counter to Bitcoin in a lot of ways. I mean, I I think Bitcoin is always very conservative,
275
00:18:19.935 --> 00:18:20.595
kind of,
276
00:18:22.400 --> 00:18:25.860
basically the opposite of reckless in terms of the way
277
00:18:26.799 --> 00:18:30.485
people treat using Bitcoin or at least the way the more
278
00:18:31.505 --> 00:18:34.565
enthusiast community or hardcore community treats using Bitcoin.
279
00:18:36.705 --> 00:18:39.684
Do you guy you guys still think that lightning is reckless?
280
00:18:40.290 --> 00:18:41.429
Like, do you think that
281
00:18:42.370 --> 00:18:46.309
is still the case? Are we still, like, almost in a beta mode of lightning?
282
00:18:49.414 --> 00:18:52.235
283
00:18:52.774 --> 00:19:04.009
of course, if you don't really know what you're doing and setting up a note without the basic understanding what you're doing and putting, like, 1,000 of dollars in that, I guess that's still reckless.
284
00:19:04.630 --> 00:19:05.130
But
285
00:19:05.675 --> 00:19:06.975
if you have some, like,
286
00:19:07.435 --> 00:19:08.815
good knowledge on
287
00:19:09.195 --> 00:19:10.495
how to run a server
288
00:19:11.035 --> 00:19:12.015
and how to,
289
00:19:12.555 --> 00:19:13.055
like,
290
00:19:14.059 --> 00:19:19.919
run software in a secure and hardened way, I think, Lightning is pretty stable.
291
00:19:21.875 --> 00:19:22.855
292
00:19:23.395 --> 00:19:28.535
I don't think I passed the point yet where I mean, when I first started using Lightning, I kinda just,
293
00:19:30.260 --> 00:19:36.840
you know, started fucking around with it and playing around with it. And I kinda just operated under the assumption I was gonna lose my money.
294
00:19:37.215 --> 00:19:40.915
And I don't know if I still I I don't know if I've left that
295
00:19:41.375 --> 00:19:43.235
assumption yet. I think I still
296
00:19:44.770 --> 00:19:48.630
operate under the assumption that basically any funds I have on my Lightning Nodes,
297
00:19:49.250 --> 00:19:50.630
can be lost at will.
298
00:19:51.865 --> 00:19:55.965
299
00:19:56.665 --> 00:19:58.105
300
00:19:59.210 --> 00:20:04.110
I was presenting at the HRF Oslo Freedom Forum earlier this year
301
00:20:06.195 --> 00:20:07.735
or earlier last year.
302
00:20:08.755 --> 00:20:10.615
And when I got off stage,
303
00:20:11.394 --> 00:20:12.774
I think Stefan Lovera
304
00:20:13.750 --> 00:20:17.690
came up to me and and said to me, he's like, Matt, did you see that lightning vulnerability?
305
00:20:18.950 --> 00:20:20.330
And, like, when you read
306
00:20:20.755 --> 00:20:26.695
the vulnerability disclosure, it almost made it seem like people could just drain funds at will if you had, like, a malicious peer.
307
00:20:29.200 --> 00:20:30.419
And it didn't happen.
308
00:20:31.279 --> 00:20:35.620
Like, one of my nodes has, you know, 200 channels or something. Like, I don't know all the peers,
309
00:20:36.715 --> 00:20:41.695
and it didn't happen. But I remember the first thing I was like, oh, well, I either lost my money or I didn't.
310
00:20:45.650 --> 00:20:50.630
311
00:20:51.409 --> 00:20:59.895
But, I mean, in the end, it's a hot wallet. Right? So Yeah. That could also happen with if you have a Bitcoin on chain hot wallet somewhere,
312
00:21:00.690 --> 00:21:02.470
if there's any vulnerability
313
00:21:02.770 --> 00:21:05.510
anywhere on the system, your funds are always
314
00:21:06.130 --> 00:21:07.350
somehow at risk.
315
00:21:08.135 --> 00:21:10.795
So I think that's one of the main drawbacks of lightning.
316
00:21:11.255 --> 00:21:16.795
But it's okay. It's a different use case. And it's just important to know that
317
00:21:17.140 --> 00:21:17.640
having
318
00:21:18.260 --> 00:21:21.160
a lot of money in a hot wallet connected to the Internet
319
00:21:21.780 --> 00:21:23.799
is probably not for your life savings.
320
00:21:24.725 --> 00:21:29.225
321
00:21:30.644 --> 00:21:35.770
this is almost either spending cash or operating flow if you're running a routing node.
322
00:21:36.070 --> 00:21:36.570
Exactly.
323
00:21:37.990 --> 00:21:39.450
So, I mean, I personally
324
00:21:39.830 --> 00:21:41.530
if if the freaks go back, I mean,
325
00:21:41.835 --> 00:21:44.655
dispatch is is has almost been every week.
326
00:21:45.434 --> 00:21:46.655
Took a couple breaks,
327
00:21:47.195 --> 00:21:48.015
last year.
328
00:21:49.720 --> 00:21:55.900
As I mean, if you do basic math, I mean, it's still dispatched 50 and started at the very end of last year.
329
00:21:57.355 --> 00:21:59.295
And a rabbit hole recap is every week.
330
00:21:59.675 --> 00:22:04.575
So the freaks are and I admit this every day. I mean, the freaks are very aware that I completely
331
00:22:06.475 --> 00:22:07.135
you know,
332
00:22:07.580 --> 00:22:12.080
I was completely wrong about a sustained high fee market. I thought we'd
333
00:22:12.620 --> 00:22:16.000
see a sustained high fee market, sooner rather than later.
334
00:22:16.365 --> 00:22:21.265
I still think I expect it going forward, but, I mean, as you can see, I have a live look of,
335
00:22:22.845 --> 00:22:24.145
mempool dot space
336
00:22:24.780 --> 00:22:28.880
on the screen right now, and 1 separate byte is confirming next block.
337
00:22:29.820 --> 00:22:38.095
Does what how how do you how do you view the fee market? How do you view do you think fees will go up? How do you when you talk to people about,
338
00:22:38.715 --> 00:22:40.174
the advantages of lightning,
339
00:22:40.700 --> 00:22:46.320
do you square that with the fact that you can just do one sapro byte and get in the next block?
340
00:22:50.315 --> 00:22:50.815
341
00:22:51.195 --> 00:22:58.000
I guess there are different use cases to Bitcoin. Like, Bitcoin is something else for everybody who joins
342
00:22:58.300 --> 00:22:58.960
the network.
343
00:22:59.740 --> 00:23:04.480
And I think lightning bought us a lot of time in term in terms of,
344
00:23:05.355 --> 00:23:05.855
like,
345
00:23:06.315 --> 00:23:08.495
mempool and block space
346
00:23:09.115 --> 00:23:09.855
just because
347
00:23:10.875 --> 00:23:13.370
people that now use Lightning, they
348
00:23:14.410 --> 00:23:16.110
basically don't take up any,
349
00:23:17.130 --> 00:23:17.870
block space.
350
00:23:18.250 --> 00:23:21.470
So I think that suppresses the the fees a lot.
351
00:23:21.885 --> 00:23:24.385
But there are other use cases like sending
352
00:23:25.005 --> 00:23:25.505
funds
353
00:23:26.125 --> 00:23:35.730
to to an exchange to if you want to sell or withdraw them into your cold storage. And I think that's probably more the case if you're, like, in a really FOMO driven
354
00:23:36.350 --> 00:23:38.370
hype cycle. So I would still
355
00:23:40.095 --> 00:23:40.595
expect
356
00:23:41.855 --> 00:23:45.075
fees to rise during, like, peak. Like, 2017
357
00:23:45.455 --> 00:23:48.195
was insane. I think I paid up to $30
358
00:23:48.575 --> 00:23:49.075
once,
359
00:23:49.540 --> 00:23:50.680
but only once.
360
00:23:52.100 --> 00:23:53.880
But I think that can happen again,
361
00:23:54.260 --> 00:23:55.880
but we're we're buying time
362
00:23:56.340 --> 00:23:57.480
with lightning, definitely.
363
00:23:58.794 --> 00:24:03.855
364
00:24:04.394 --> 00:24:07.695
in times of high fee pressure, and it kind of could
365
00:24:08.620 --> 00:24:10.720
provide the network with the ability to,
366
00:24:12.860 --> 00:24:20.785
not stay at a high fee level for as long as it would otherwise. But one of the key aspects here is, I mean, every Lightning channel is an open and
367
00:24:21.165 --> 00:24:22.705
requires an open and close,
368
00:24:23.165 --> 00:24:25.745
which is an on which is 2 on chain transactions.
369
00:24:26.590 --> 00:24:29.410
So if you're not prepared for that ahead of time,
370
00:24:31.710 --> 00:24:33.970
you're you're not going to get the fee savings
371
00:24:34.684 --> 00:24:42.225
of Lightning in a high fee environment. If we have a high fee environment in a week or 2 weeks, not that I'm saying that we will, we probably will not,
372
00:24:43.530 --> 00:24:49.550
That's not the time to really open the channels. The time to open in the channels is when it's 1 separate byte. Mhmm.
373
00:24:50.090 --> 00:24:51.790
OpenOps, do you have any thoughts here?
374
00:24:53.154 --> 00:25:00.860
375
00:25:01.900 --> 00:25:02.720
If you have
376
00:25:03.500 --> 00:25:04.000
something
377
00:25:04.460 --> 00:25:06.320
some use for it, then,
378
00:25:06.780 --> 00:25:08.535
you know, open channels. But I
379
00:25:09.015 --> 00:25:12.475
I I don't really believe in this kind of preemptively
380
00:25:14.535 --> 00:25:16.120
working towards the
381
00:25:16.520 --> 00:25:20.700
or or preparing for the high fee market. Because to be honest, even then,
382
00:25:22.120 --> 00:25:24.755
if you want to send a lightning transaction, you would just
383
00:25:25.235 --> 00:25:28.295
just a Bitcoin transaction. You would just think twice that,
384
00:25:28.755 --> 00:25:30.295
should I open a channel rather?
385
00:25:30.675 --> 00:25:40.549
Does this beer have a node? Does this exchange by then have a node? Does this, you know, friend of mine or this shop have a node? And if I would stay on chain,
386
00:25:41.395 --> 00:25:44.295
I would just rather open a channel then. And then,
387
00:25:45.235 --> 00:25:53.640
you know, you have the fee savings for the next payment because the next one you will be able to to spend on lightning either to that shop or peer
388
00:25:54.180 --> 00:25:56.600
or through the lightning network to anywhere else.
389
00:25:58.775 --> 00:26:01.595
390
00:26:02.775 --> 00:26:05.860
batch Bitcoin transactions. So instead of sending one transaction,
391
00:26:09.220 --> 00:26:09.720
Exactly.
392
00:26:10.020 --> 00:26:12.440
Yeah. So you still get fee savings in that situation.
393
00:26:14.115 --> 00:26:15.414
394
00:26:15.794 --> 00:26:17.495
the bite lightning already,
395
00:26:19.715 --> 00:26:25.670
helps us scale Bitcoin a lot, But, of course, it's it's it's not done scaling. Right?
396
00:26:26.050 --> 00:26:28.310
So once we're like,
397
00:26:29.065 --> 00:26:35.804
dual funded channels will become the norm or channel factories where you can open, like, one big channel with multiple peers.
398
00:26:36.270 --> 00:26:39.330
Something like that, I think, would probably be the next step
399
00:26:40.110 --> 00:26:41.730
of lightning scaling.
400
00:26:42.270 --> 00:26:49.075
And I'm not sure what comes after that, but I guess we'll I think Andreas Antonopoulos once said we're constantly
401
00:26:49.615 --> 00:26:50.115
not
402
00:26:50.575 --> 00:26:54.995
failing to scale or something like that. So it's always, like, pushing the boundaries,
403
00:26:55.630 --> 00:26:58.850
like, a few weeks or a few years in front of us.
404
00:27:01.630 --> 00:27:07.715
405
00:27:08.255 --> 00:27:08.995
be developed,
406
00:27:10.175 --> 00:27:14.035
in Bitcoin land, I don't even think we can really fathom them yet.
407
00:27:15.360 --> 00:27:20.180
I don't think we should rest on that and just assume that will be the case, but at the same time,
408
00:27:20.720 --> 00:27:23.060
we should be humble enough to realize that,
409
00:27:25.025 --> 00:27:29.125
our small human brains can't really understand the implications so far ahead of time.
410
00:27:30.465 --> 00:27:34.165
I know I've been caught off guard way, way, way many times.
411
00:27:37.330 --> 00:27:40.070
So open arms, where do you think we should go next in this conversation?
412
00:27:45.065 --> 00:27:50.205
413
00:27:50.530 --> 00:27:54.210
get get into the details of it a bit. I mean, should we just,
414
00:27:54.850 --> 00:27:55.590
skim through
415
00:27:56.210 --> 00:27:58.554
what we do when we are setting
416
00:27:59.095 --> 00:28:00.394
up a lightning node.
417
00:28:00.934 --> 00:28:03.434
418
00:28:03.735 --> 00:28:06.134
I mean, maybe taking a step back and,
419
00:28:06.830 --> 00:28:10.690
giving a quick overview what the rest of the bolt is or is not
420
00:28:10.990 --> 00:28:11.490
versus
421
00:28:11.790 --> 00:28:13.410
other node implementations
422
00:28:14.505 --> 00:28:17.965
could help and then dive into what how it actually works.
423
00:28:20.505 --> 00:28:23.005
424
00:28:24.440 --> 00:28:30.059
you know, I've had the Raspberry Pi Blitz team on. I've had Roni Dojo team on. I've had
425
00:28:30.935 --> 00:28:32.475
pretty much everyone but Umbralon.
426
00:28:33.735 --> 00:28:38.235
How is how is Raspberry Bolt different than, let's say, Raspberry Blitz?
427
00:28:39.039 --> 00:28:40.799
428
00:28:41.519 --> 00:28:46.980
preface that with that I fear for every node that joins the network. I think
429
00:28:47.335 --> 00:28:48.955
this is our all shared
430
00:28:49.575 --> 00:28:50.075
goal.
431
00:28:50.455 --> 00:28:54.235
The more people around their own node and actually use it, the better.
432
00:28:56.030 --> 00:28:56.190
With
433
00:28:56.910 --> 00:28:58.610
in in light of the the differences.
434
00:28:59.150 --> 00:29:01.010
So I think the recipe vault
435
00:29:01.310 --> 00:29:02.290
is the only
436
00:29:03.185 --> 00:29:06.405
project. So to say that it's just a guide.
437
00:29:06.865 --> 00:29:08.485
So there's nothing to download.
438
00:29:08.865 --> 00:29:09.845
It's a website,
439
00:29:10.545 --> 00:29:13.000
and it's it's getting pretty big.
440
00:29:13.540 --> 00:29:14.040
And
441
00:29:14.580 --> 00:29:16.680
it basically takes you by the hand
442
00:29:17.700 --> 00:29:19.960
and lays out command by command
443
00:29:20.665 --> 00:29:21.485
how you can
444
00:29:22.745 --> 00:29:23.965
set up your own
445
00:29:24.665 --> 00:29:25.965
do everything yourself
446
00:29:26.425 --> 00:29:26.925
Bitcoin
447
00:29:27.545 --> 00:29:31.960
full node with lightning, with with many bonus guides and stuff like that.
448
00:29:32.500 --> 00:29:38.675
But in the end, it's it's not only about having the node in the end. It's also about
449
00:29:39.375 --> 00:29:39.875
knowing
450
00:29:40.735 --> 00:29:43.715
how it's built, how how you set it up yourself,
451
00:29:44.335 --> 00:29:44.835
and
452
00:29:45.570 --> 00:29:53.510
not trusting someone else to just, like, download an image and and run it. So it's it's it's as much a learning experience
453
00:29:55.845 --> 00:29:57.065
as running a node.
454
00:29:57.765 --> 00:30:02.905
And I guess it's not for everybody, and it doesn't need to be because I I'm always amazed how
455
00:30:03.279 --> 00:30:03.779
many
456
00:30:04.320 --> 00:30:04.820
projects
457
00:30:05.520 --> 00:30:09.779
there are out there. And it seems like every project has found its niche.
458
00:30:10.135 --> 00:30:12.794
So the recipe vault is really, like, more about learning.
459
00:30:13.335 --> 00:30:25.010
And it's it's pretty universal, so it only uses step in commands. So you can not only use it on a Raspberry Pi, you can reuse it on a virtual private server, on a virtual machine. Everything that can run Debian
460
00:30:25.549 --> 00:30:26.530
is able to
461
00:30:26.904 --> 00:30:27.725
run the Respibault.
462
00:30:30.184 --> 00:30:32.044
And then, of course, like the Respibilts,
463
00:30:32.985 --> 00:30:35.325
Rud Sol and his team, like,
464
00:30:36.440 --> 00:30:36.940
as
465
00:30:37.320 --> 00:30:37.820
mentioned,
466
00:30:39.960 --> 00:30:43.340
they basically built on top of the recipe vault,
467
00:30:43.880 --> 00:30:44.380
but,
468
00:30:45.325 --> 00:30:50.465
with the focus on lightning hack days, which full mode does quite quite often.
469
00:30:52.525 --> 00:31:00.429
And they basically automated the whole thing, which is awesome. In the beginning, it was just like the recipe vault automated with shell scripts,
470
00:31:00.855 --> 00:31:08.235
but that was just the beginning. And now they build, like, awesome stuff on top of that. They they you their own menu system,
471
00:31:09.460 --> 00:31:10.900
many, many options you can,
472
00:31:12.260 --> 00:31:15.480
switch on. But it's still, like, more of a
473
00:31:16.755 --> 00:31:17.655
a hack day.
474
00:31:18.355 --> 00:31:26.750
I think the target audience are are are more, like, people that want to to go down to the command line, understand how it's working, like more tinkerers.
475
00:31:28.650 --> 00:31:31.390
So that's that's like an awesome project. I really,
476
00:31:31.850 --> 00:31:33.390
I also run it myself.
477
00:31:34.835 --> 00:31:41.495
And then, of course, are, like, the more, like, UI focused notes, like Umbrel, my notes, like the Citadel.
478
00:31:44.289 --> 00:31:49.030
These are really, really cool because it allow they allow, like, normies.
479
00:31:49.730 --> 00:31:53.510
Like, I wasn't once as well before I fell down the rabbit hole
480
00:31:54.845 --> 00:32:03.345
So just, like, download an image, put it into the Raspberry Pi, spin it up, and connect your browser, and that's basically it. You're on you're now a sovereign
481
00:32:03.950 --> 00:32:06.050
peer on the Bitcoin blockchain.
482
00:32:07.230 --> 00:32:09.810
And I find this especially important
483
00:32:10.190 --> 00:32:12.905
if you then connect your hardware wallet to it
484
00:32:13.385 --> 00:32:13.885
Because
485
00:32:14.425 --> 00:32:17.805
many projects put it more the focus more on lightning.
486
00:32:18.745 --> 00:32:19.545
But I'm really
487
00:32:20.960 --> 00:32:26.900
for me, that's more like the cherry on top. I care much more about the underlying blockchain and validating
488
00:32:27.935 --> 00:32:28.915
my own transactions
489
00:32:29.295 --> 00:32:33.475
on chain with my hardware wallet directly on my own full node.
490
00:32:34.655 --> 00:32:40.440
So that might be another difference. The the Raspberry Bolt really builds the the on chain part first
491
00:32:41.700 --> 00:32:44.920
and lightning comes on top while other projects
492
00:32:45.325 --> 00:32:47.745
basically advertise them as Lightning nodes.
493
00:32:48.205 --> 00:32:51.745
And many didn't even allow you to connect your
494
00:32:52.540 --> 00:32:56.880
harder wallets to them, like through a Electrum server or something like that.
495
00:32:59.235 --> 00:33:02.455
And, yeah, one one last thing like Nix Bitcoin.
496
00:33:03.075 --> 00:33:10.539
I was trying to get more into it. It's it has a steep learning curve, but I really appreciate what the these guys are doing.
497
00:33:12.120 --> 00:33:16.700
Can't really do them justice explaining it. It's just like a super hard and
498
00:33:17.384 --> 00:33:18.205
no compromise
499
00:33:18.825 --> 00:33:19.965
security focused,
500
00:33:22.105 --> 00:33:22.605
reproducibly
501
00:33:23.225 --> 00:33:23.725
built
502
00:33:24.745 --> 00:33:26.044
Bitcoin full note
503
00:33:26.550 --> 00:33:27.050
distribution
504
00:33:27.750 --> 00:33:29.130
built on Nix OS.
505
00:33:29.750 --> 00:33:30.250
So
506
00:33:30.630 --> 00:33:35.485
that's really, really cool to see. And I think if I find the time someday, this
507
00:33:36.025 --> 00:33:39.164
is probably what I'm gonna experiment with next.
508
00:33:40.105 --> 00:33:41.325
509
00:33:43.200 --> 00:33:45.360
some of the guys from Nix Bitcoin on,
510
00:33:45.760 --> 00:33:46.260
cildispatch
511
00:33:46.800 --> 00:33:48.500
42. So that's cildispatch.com/cd42.
512
00:33:52.855 --> 00:33:57.595
If any of the freaks have missed that episode and are interested in going back and listening.
513
00:33:59.095 --> 00:34:01.275
Open Arms, do you have anything to add on there?
514
00:34:02.490 --> 00:34:11.835
By the way, as always, feel free to just jump in. Don't don't feel like I need to be, you know, host host Odell over here. You're you're welcome to jump in at any point.
515
00:34:12.935 --> 00:34:14.555
516
00:34:15.655 --> 00:34:24.980
no. I I I do like the the approach of of of Skye of basing basing everything on on self validating and just going step by step. I've been when I've,
517
00:34:25.440 --> 00:34:26.500
you know, come into,
518
00:34:27.165 --> 00:34:29.265
basically, come into running a full node
519
00:34:29.885 --> 00:34:30.385
through
520
00:34:31.245 --> 00:34:33.885
running a lightning node. So I I've, first of all
521
00:34:35.560 --> 00:34:36.060
well,
522
00:34:36.360 --> 00:34:40.540
wanted to use, like, Electrum and, you know, like, between core as well as
523
00:34:41.800 --> 00:34:48.954
running a lightning node and it I understand that how important that is to get, like, a solid foundation. And then the
524
00:34:50.155 --> 00:35:00.619
I needed to understand how how it is all built up, and this was the guide which I just, you know, kept coming back to. I mean, now there are for example, for Lightning, there is like, the Lightning
525
00:35:01.480 --> 00:35:01.980
Labs
526
00:35:02.440 --> 00:35:06.035
have kind of a node builder's guide or,
527
00:35:06.595 --> 00:35:12.750
similar quite extensive documentation, but how to use l and d itself or how to set it up in in various
528
00:35:13.450 --> 00:35:13.950
environments.
529
00:35:14.490 --> 00:35:14.990
But
530
00:35:16.410 --> 00:35:17.069
that is
531
00:35:18.250 --> 00:35:22.695
basically aimed for, like, an the industrial use. But if you want to sit down yourself,
532
00:35:23.075 --> 00:35:35.289
you would you would start hacking away with with, you know now I have now I need to get into using Linux as an operating system and as I and I was coming from Windows so far. So how do I do this? And then,
533
00:35:35.825 --> 00:35:37.365
you know, there are basic commands
534
00:35:37.984 --> 00:35:39.285
you can use. And
535
00:35:39.585 --> 00:35:50.360
from 0, and I I do this. I tell this from experience. One of my first exposures to using Linux was going through the s p boat guide, and it was just, you know, it was
536
00:35:50.660 --> 00:36:00.225
it was a great drilling point, and I kept coming back to it. Oh, how do I do do this and that? And, you know, there's been just a couple of sentences of explanation just to do it. So,
537
00:36:00.765 --> 00:36:04.580
you know, thanks for that, and and and that is great. And it still remained
538
00:36:05.120 --> 00:36:08.505
this, you know, focus on this approach, which is,
539
00:36:09.785 --> 00:36:11.724
yeah, exactly. It's quite quite unique.
540
00:36:14.184 --> 00:36:17.164
So there are different people coming into into
541
00:36:17.800 --> 00:36:22.540
interacting with Bitcoin. Like, if someone is interested, you know, in it for the technology,
542
00:36:23.160 --> 00:36:25.580
then, you know, they would they would come to learn,
543
00:36:25.905 --> 00:36:28.645
and then this would be the route I would send them send
544
00:36:29.105 --> 00:36:30.165
them down on.
545
00:36:31.585 --> 00:36:34.480
If someone is, you know, like, a big investor,
546
00:36:35.660 --> 00:36:40.880
coming in with, you know, 1,000,000 of dollars like the gentleman you've seen in the big in the clip in the beginning,
547
00:36:41.515 --> 00:36:43.454
then, you know, I would definitely not
548
00:36:43.835 --> 00:36:47.295
ask them to kind of, okay, let's start typing these comments,
549
00:36:47.595 --> 00:36:48.795
but they would need to be
550
00:36:49.600 --> 00:36:50.900
have a service provided.
551
00:36:51.360 --> 00:36:57.060
552
00:36:57.615 --> 00:36:59.795
553
00:37:00.255 --> 00:37:01.075
I don't think,
554
00:37:01.695 --> 00:37:09.970
you know, it it I don't think that would be a suggestion he would want to hear, So it would be not the right thing to say it. Do you think there's an argument for
555
00:37:13.345 --> 00:37:13.845
556
00:37:14.385 --> 00:37:16.005
people that started with,
557
00:37:16.944 --> 00:37:17.444
RaspiBlitz
558
00:37:18.145 --> 00:37:22.484
or Ronin Dojo or an Umbral or or something similar to that,
559
00:37:23.760 --> 00:37:30.260
and maybe they're still using it as their main node to also on the side go through RAS by Bolt's guide and
560
00:37:30.925 --> 00:37:37.505
maybe set it up that way so they can understand more about how everything is working under the hood because all of these node implementations are
561
00:37:37.805 --> 00:37:39.500
they have a lot of similarities. Right?
562
00:37:40.700 --> 00:37:44.320
563
00:37:44.620 --> 00:37:51.415
like like, DB and Linux distro based in most, except Ronin Dojo is using Manjaro, which is like Arch.
564
00:37:52.515 --> 00:37:55.815
It's it's it's slightly different. You have slightly different commands
565
00:37:56.359 --> 00:37:57.820
with the same kind of logic.
566
00:38:00.920 --> 00:38:02.220
So I would
567
00:38:02.760 --> 00:38:09.645
definitely recommend everyone to kind of go into it, course through it. And maybe if someone would decide to build,
568
00:38:10.105 --> 00:38:11.005
like, a more
569
00:38:11.465 --> 00:38:13.005
resilient, a bit more serious
570
00:38:13.790 --> 00:38:16.530
node to provide some service maybe or, you know,
571
00:38:17.150 --> 00:38:17.650
serve
572
00:38:18.270 --> 00:38:20.930
the needs of, you know, Billy Uncle Jim,
573
00:38:22.375 --> 00:38:26.875
to serve, for example, a Manpoo list instance or, like, an Electrum server to some
574
00:38:27.415 --> 00:38:33.390
others, and the Raspberry Pi will be a bit underpowered for that, and then they will now start on a
575
00:38:34.030 --> 00:38:35.970
on just a computer in the corner,
576
00:38:36.675 --> 00:38:37.175
then
577
00:38:38.195 --> 00:38:40.775
exactly this would be the time just to
578
00:38:41.475 --> 00:38:52.990
not to take something off the shelf, but just build it themselves. And then this would be the right guy to look into, and you might need some modifications in in a couple of cases. But, I mean, it's it's pretty much
579
00:38:54.575 --> 00:38:57.555
same on any computer running Linux. Right?
580
00:38:58.975 --> 00:39:01.635
581
00:39:03.089 --> 00:39:05.109
Is now in version 3,
582
00:39:06.769 --> 00:39:07.430
with a
583
00:39:07.730 --> 00:39:08.230
nice
584
00:39:08.769 --> 00:39:21.260
neon glow layout. That was just it's just like 1 or 2 months old, the current guide. And one of the major changes was to get rid of all Raspberry Pi specific commands.
585
00:39:22.039 --> 00:39:27.260
So it's it's much easier to set up the Wi Fi using a respi config or something like that.
586
00:39:27.720 --> 00:39:28.220
But
587
00:39:28.855 --> 00:39:35.115
I really wanted to have it as universal as possible. So if openums mentions that, okay, now,
588
00:39:35.895 --> 00:39:37.595
the Raspberry Pi is no longer
589
00:39:38.200 --> 00:39:39.980
has no longer the oomph you need.
590
00:39:40.920 --> 00:39:43.820
It should be possible to have exactly the same,
591
00:39:44.520 --> 00:39:45.020
setup,
592
00:39:46.205 --> 00:39:52.465
for example, on a on a cloud server or, like, on a on a virtual private server or on a
593
00:39:54.340 --> 00:39:56.280
NUC, like, Intel NUC based,
594
00:39:56.980 --> 00:39:58.520
hardware you host yourself.
595
00:39:59.380 --> 00:40:05.545
The only changes would probably be that you don't need to download the ARM 64, the binaries, but the Intel
596
00:40:05.925 --> 00:40:08.984
ones. But that's like a a very easy
597
00:40:09.470 --> 00:40:15.650
change to do. Everything else should be exactly the same because it uses only plain Debian commands.
598
00:40:17.125 --> 00:40:19.145
599
00:40:19.525 --> 00:40:20.505
are very underpowered,
600
00:40:21.845 --> 00:40:24.345
but they're also really cheap and efficient and
601
00:40:25.110 --> 00:40:26.330
easy to work with.
602
00:40:26.870 --> 00:40:30.810
I mean, the Raspi when Raspi Bolt first when you first released
603
00:40:31.190 --> 00:40:35.095
v one of Raspi Bolt, I mean, that must have been on Raspberry Pi Threes
604
00:40:35.635 --> 00:40:40.695
Yes. Which were really underpowered. And now most people use Raspberry Fours. Right?
605
00:40:41.170 --> 00:40:45.830
606
00:40:46.130 --> 00:40:46.450
it
607
00:40:47.810 --> 00:40:48.310
it's
608
00:40:48.675 --> 00:40:53.975
almost overkill for this kind of setup unless you have, like, hundreds of channels.
609
00:40:54.355 --> 00:40:56.295
But, of course, that's like regular
610
00:40:57.010 --> 00:40:58.869
scaling in IT terms.
611
00:40:59.490 --> 00:41:00.950
But I think my
612
00:41:01.250 --> 00:41:03.430
pies are mostly idle. They have
613
00:41:03.730 --> 00:41:07.115
way too much oomph for that stuff they do.
614
00:41:08.295 --> 00:41:14.235
But for example, on the Raspberry Pi 3, it was not a it it was not possible to verify the blockchain
615
00:41:14.630 --> 00:41:18.170
directly on the device. So the older versions of the guide
616
00:41:18.550 --> 00:41:20.010
made you download the
617
00:41:20.310 --> 00:41:22.330
blockchain to your regular computer,
618
00:41:22.945 --> 00:41:27.125
like run through the whole indexing stuff and then copied over
619
00:41:27.665 --> 00:41:28.965
to the to the pie.
620
00:41:29.345 --> 00:41:32.550
This now is no longer necessary. You can just
621
00:41:33.110 --> 00:41:35.610
wait 2 days and everything is indexed.
622
00:41:36.390 --> 00:41:43.005
I think that's that's pretty cool. And, I mean, if you what what you get for $60 or so is is really amazing.
623
00:41:44.665 --> 00:41:46.265
624
00:41:46.665 --> 00:41:50.045
Craig Rall, lead maintainer of Spiro Wallet. I mean, he released,
625
00:41:52.410 --> 00:41:56.430
like, a performance analysis breakdown of ElectrumX and Electris
626
00:41:56.890 --> 00:41:58.110
Electrum Rust Server
627
00:42:00.365 --> 00:42:01.905
using RAASPI Fours.
628
00:42:03.484 --> 00:42:04.545
And I guess
629
00:42:05.645 --> 00:42:10.329
most of these projects are using Electrum Rust Server. It's not practical to,
630
00:42:11.430 --> 00:42:13.530
run Electrum x on them.
631
00:42:13.990 --> 00:42:16.490
And he he's I mean, his analysis
632
00:42:16.790 --> 00:42:17.930
seemed to
633
00:42:18.725 --> 00:42:20.825
make clear and, I mean, I've noticed it myself
634
00:42:21.365 --> 00:42:25.225
that, you know, it's not an ideal situation really. Like, if you're using
635
00:42:27.330 --> 00:42:33.270
an Electrum server running on a raspi and you have a wallet that is very deep, that has a lot of,
636
00:42:33.890 --> 00:42:36.630
UTXO history, a lot of transaction history,
637
00:42:37.425 --> 00:42:39.765
they tend to really struggle still.
638
00:42:40.225 --> 00:42:45.605
639
00:42:45.985 --> 00:42:46.485
itself.
640
00:42:47.690 --> 00:42:48.190
ElectrumX
641
00:42:48.490 --> 00:42:48.990
is
642
00:42:50.570 --> 00:42:51.869
harder to set up,
643
00:42:52.570 --> 00:42:54.225
but it for, like
644
00:42:55.185 --> 00:43:01.445
I I work at ShiftCrypto. Right? So we do run our own Electrum servers for our clients with the hardware wallets.
645
00:43:02.145 --> 00:43:02.645
And
646
00:43:03.060 --> 00:43:04.280
we use Electrum
647
00:43:04.740 --> 00:43:05.880
X for that
648
00:43:06.180 --> 00:43:07.240
because it
649
00:43:07.540 --> 00:43:09.000
Elektrus is not built
650
00:43:09.380 --> 00:43:09.880
to
651
00:43:10.465 --> 00:43:11.685
serve, like, 1,000
652
00:43:12.385 --> 00:43:13.045
and 1,000
653
00:43:13.345 --> 00:43:15.205
of clients at the same time.
654
00:43:16.305 --> 00:43:21.270
655
00:43:21.890 --> 00:43:22.390
656
00:43:22.849 --> 00:43:23.910
I mean, I
657
00:43:25.725 --> 00:43:28.465
I wouldn't agree on that, like, the pie
658
00:43:29.405 --> 00:43:31.185
is too much. It is
659
00:43:31.645 --> 00:43:34.705
absolutely the bare minimum. The the the
660
00:43:35.069 --> 00:43:36.609
r p 3 was
661
00:43:37.470 --> 00:43:43.890
not suitable to do this. And whoever comes to me asking that, oh, can I do this on a Raspberry Pi 3?
662
00:43:44.295 --> 00:43:47.675
Well, I mean, they can, you know, it is a wrong question
663
00:43:48.055 --> 00:43:49.515
because no one should.
664
00:43:50.055 --> 00:43:50.714
And then
665
00:43:51.335 --> 00:43:52.714
Raspberry Pi 4
666
00:43:53.539 --> 00:43:54.279
does have
667
00:43:54.900 --> 00:43:57.799
I mean, the processor power is not that different.
668
00:43:58.260 --> 00:44:05.865
The RAM, obviously, you know, versus 1 gigabyte, 4 gigabytes, or 8 is is is great. But then just this this simple
669
00:44:06.325 --> 00:44:06.825
power,
670
00:44:07.365 --> 00:44:10.500
the emperors, it can give to the disk.
671
00:44:11.279 --> 00:44:15.859
It's just even that is just hardly enough for to power 1 disk. And the biggest
672
00:44:16.675 --> 00:44:24.615
problem with, you know, the resiliency of this of these setups is that single disk is prone to fail because there is no battery.
673
00:44:24.950 --> 00:44:26.650
They should be connected to UPS.
674
00:44:27.190 --> 00:44:27.690
And
675
00:44:28.150 --> 00:44:29.210
676
00:44:29.589 --> 00:44:31.770
677
00:44:32.305 --> 00:44:35.685
you cannot even think of, like, running RAID or, you know, duplicating,
678
00:44:36.865 --> 00:44:45.170
your your your data. Like, you know, data security basically is terrible, which is a very bad choice, very bad pair with lightning.
679
00:44:45.710 --> 00:44:47.010
680
00:44:47.945 --> 00:44:50.285
I mean, with lightning, you want if if
681
00:44:51.065 --> 00:44:51.545
if,
682
00:44:52.025 --> 00:44:57.450
your your your your state is constantly changing and you need to constantly update your state,
683
00:44:58.410 --> 00:45:00.430
You don't wanna have an old state, otherwise,
684
00:45:00.810 --> 00:45:01.869
you get penalized
685
00:45:02.410 --> 00:45:06.645
and you can lose funds that way. And the main way of backing up,
686
00:45:07.345 --> 00:45:08.805
short of actually doing,
687
00:45:09.985 --> 00:45:13.525
constant, like, almost a RAID configuration where you're having constantly
688
00:45:15.370 --> 00:45:18.730
backing it up to a second drive is this idea of,
689
00:45:20.650 --> 00:45:38.240
static static channel backups where you actually lose all your channels in that situation. Everything gets settled on chain. So it's, like, not an ideal backup situation. You'd prefer if you just didn't have the drive failure in the first place. So yes. Exactly. So the subject to channel backup is just a list of your peers where the node,
690
00:45:38.625 --> 00:45:42.405
691
00:45:42.705 --> 00:45:46.725
to force close the channels themselves. If they are offline, funds are stuck.
692
00:45:48.290 --> 00:45:51.270
You know, that is that is not not much use.
693
00:45:51.650 --> 00:45:52.310
The actual
694
00:45:52.610 --> 00:45:58.385
channel database, the database of the of the states of the lightning channels is is most valuable information,
695
00:45:58.845 --> 00:46:07.880
which indeed you need to back up in real time, which you can you can do. Like, especially with c lightning, it has a plug in which has which can do real time backups
696
00:46:08.579 --> 00:46:10.280
even to an off-site location.
697
00:46:10.755 --> 00:46:14.535
But then what you get, you need to run another server. Right?
698
00:46:14.914 --> 00:46:20.380
Right. I mean, you would need to do this anyway for backups, but, I mean, you would need to have your
699
00:46:21.000 --> 00:46:21.500
main
700
00:46:21.800 --> 00:46:22.300
machine,
701
00:46:23.800 --> 00:46:27.900
working quite quite as reliably as well. So I think that that is the biggest kind of
702
00:46:28.664 --> 00:46:34.525
bottleneck or or a drawback or weakness of of of the Raspberry Pi that it cannot it's not able to
703
00:46:35.224 --> 00:46:40.789
power, like, 2 disks just by itself. And then you can use external power. You have an extra cable,
704
00:46:41.569 --> 00:46:47.005
you know, and then another thing that with which the cats or, you know, like a young child can play with.
705
00:46:47.805 --> 00:46:49.904
You know, again, not not ideal.
706
00:46:51.484 --> 00:46:55.424
707
00:46:56.125 --> 00:46:56.625
then
708
00:46:57.800 --> 00:47:00.780
I I always channel my inner Zoolander. Like, with Lightning,
709
00:47:01.160 --> 00:47:02.540
the keys are in the computer.
710
00:47:03.080 --> 00:47:04.060
With with
711
00:47:04.625 --> 00:47:14.760
on chain, the keys are ideally being are not being held on the actual node itself. So if the node fails, it's just it's just a way of interacting with the network. It's not actually holding your secrets.
712
00:47:15.620 --> 00:47:16.440
713
00:47:16.820 --> 00:47:21.400
I think we're we're probably having a a bit of different use cases in mind.
714
00:47:21.865 --> 00:47:26.444
For me, it's really the Raspberry Pi is the perfect device to have your own
715
00:47:26.825 --> 00:47:30.349
at home Bitcoin full node for on chain use,
716
00:47:31.369 --> 00:47:36.029
query the network. Yeah. Like a direct participant of the peer to peer network
717
00:47:36.569 --> 00:47:37.710
and run a lightning,
718
00:47:38.525 --> 00:47:40.625
node on top for your personal use.
719
00:47:41.085 --> 00:47:49.400
But I'd never use it for, like, a business or if you have I mean, I probably have, like, 20 channels or so, and for that, it's perfectly fine.
720
00:47:51.380 --> 00:47:53.240
But, of course, if you're looking into
721
00:47:53.994 --> 00:47:54.815
this redundancy
722
00:47:55.275 --> 00:47:55.775
or,
723
00:47:56.075 --> 00:47:58.175
like, hold, like, large funds
724
00:47:58.475 --> 00:48:01.375
or even need, like, guaranteed 247
725
00:48:01.755 --> 00:48:04.730
uptime for a business because otherwise you can't take any,
726
00:48:05.349 --> 00:48:05.849
payments,
727
00:48:06.470 --> 00:48:06.970
then
728
00:48:07.270 --> 00:48:09.690
a Raspberry Pi is probably not the,
729
00:48:10.230 --> 00:48:11.210
the right choice.
730
00:48:11.515 --> 00:48:14.655
Then I'd definitely go with something that actually has a case
731
00:48:15.035 --> 00:48:17.215
and a decent power supply and
732
00:48:17.515 --> 00:48:18.895
allows you to have,
733
00:48:19.250 --> 00:48:20.869
like, all the stuff neatly
734
00:48:21.250 --> 00:48:23.430
connected directly and not everything
735
00:48:24.130 --> 00:48:27.205
dangling off USB hubs and stuff like that.
736
00:48:28.645 --> 00:48:36.105
737
00:48:36.860 --> 00:48:40.160
building recipe blitzes and, you know, I
738
00:48:40.780 --> 00:48:43.440
do develop this software and, you know, I do
739
00:48:43.740 --> 00:48:45.840
think that it is a great way to start.
740
00:48:47.045 --> 00:48:55.144
But then, indeed, you would need to scale up if you are, you know, doing something serious with your node. Like, for example, 20 channels is just about
741
00:48:55.710 --> 00:48:57.809
which, you know, I would say,
742
00:48:58.670 --> 00:48:59.170
acceptable.
743
00:48:59.470 --> 00:49:02.609
But if you go up, for example, to 50 so just
744
00:49:03.395 --> 00:49:13.369
just take a quick calculation of what does it cost to force close 50 channels if you are lucky. Yeah. And, oh, and, oh, so your the disc fails. It does fail, you know, one
745
00:49:13.670 --> 00:49:16.730
in every 3 years, I would say, you know, it's
746
00:49:17.270 --> 00:49:18.970
quite likely. And then
747
00:49:19.855 --> 00:49:24.915
even with the SSDs, I mean, the hard disks are even even even worse, but don't even go there.
748
00:49:26.415 --> 00:49:34.920
And then you would need to restore, for example, the static channel backup, which you have been, you know, cleverly set up to to have saved somewhere
749
00:49:35.300 --> 00:49:37.000
automatically or or,
750
00:49:37.515 --> 00:49:39.694
there is a guide for that investment board.
751
00:49:42.315 --> 00:49:43.454
So 50 times,
752
00:49:44.320 --> 00:49:44.820
what,
753
00:49:45.280 --> 00:49:46.260
$5 transaction?
754
00:49:46.560 --> 00:49:49.300
Force closes are are are bigger, and
755
00:49:49.840 --> 00:49:52.820
they for security, they are using a high fee,
756
00:49:54.065 --> 00:49:56.244
so they should confirm in the next block.
757
00:49:56.625 --> 00:49:57.845
So let's say,
758
00:49:58.305 --> 00:49:59.125
$10 each.
759
00:49:59.425 --> 00:49:59.925
That's
760
00:50:00.545 --> 00:50:01.445
that's $500.
761
00:50:02.400 --> 00:50:05.059
You can get quite decent competitor for that.
762
00:50:07.599 --> 00:50:16.325
And you might have, you know, invested it before you had the 50 channels or you have the 50 channels now, you might invested it invested into hardware,
763
00:50:16.625 --> 00:50:17.125
migrate
764
00:50:17.425 --> 00:50:19.525
the nodes over, which is perfectly
765
00:50:19.985 --> 00:50:20.485
possible.
766
00:50:21.450 --> 00:50:26.990
And then you have a good computer and less risk of needing to close all your channels, for example.
767
00:50:28.885 --> 00:50:32.025
So, yeah, just just be aware of of of the limitations
768
00:50:32.805 --> 00:50:36.025
of it. And, yeah, don't don't be very
769
00:50:37.620 --> 00:50:41.400
to start, but then recognize when you need to need to step up.
770
00:50:41.700 --> 00:50:42.600
Hashtag reckless.
771
00:50:43.540 --> 00:50:45.160
772
00:50:45.540 --> 00:50:45.860
773
00:50:46.405 --> 00:50:52.585
I mean, that's an interesting framing that in a lot of ways, you're kind of when you start with the raspi, you're you're basically
774
00:50:53.445 --> 00:50:57.470
deferring a potential cost rather than doing the cost upfront.
775
00:50:58.730 --> 00:50:59.550
We have,
776
00:51:00.330 --> 00:51:05.385
the j plus one in the comments. I feel like this is a good jumping point based on
777
00:51:05.685 --> 00:51:06.985
your previous comment
778
00:51:07.845 --> 00:51:10.105
asking about if you guys have any experience
779
00:51:10.470 --> 00:51:12.970
about migrating off a pie to new hardware,
780
00:51:13.830 --> 00:51:15.690
and, like, what that process entails.
781
00:51:16.230 --> 00:51:17.850
Any tips or tricks there?
782
00:51:20.375 --> 00:51:22.795
783
00:51:23.095 --> 00:51:23.835
much more
784
00:51:24.375 --> 00:51:24.875
experienced,
785
00:51:26.055 --> 00:51:26.980
than I am.
786
00:51:27.700 --> 00:51:32.980
But I would say set if you migrate to new hardware, you can just set it up,
787
00:51:33.380 --> 00:51:36.359
at in terms of the rest pie, bolt.
788
00:51:36.674 --> 00:51:37.575
Just set it up
789
00:51:37.875 --> 00:51:39.815
new. You can copy over the blockchain.
790
00:51:41.714 --> 00:51:42.775
If I'm not mistaken,
791
00:51:43.234 --> 00:51:43.734
probably
792
00:51:44.260 --> 00:51:45.160
set up lightning
793
00:51:45.620 --> 00:51:51.880
part, run it once, and close it down again. And I think after that, you can pretty much copy the the old,
794
00:51:53.875 --> 00:51:59.095
directories over. Right? You just need to make sure that never ever the old note goes online again.
795
00:52:00.390 --> 00:52:00.890
796
00:52:01.830 --> 00:52:03.130
No. That's, that's
797
00:52:03.670 --> 00:52:04.170
basically
798
00:52:04.790 --> 00:52:15.415
just it. It it's not that difficult. I mean, and people need to understand then why the old node doesn't it must not go online ever again because it has
799
00:52:16.069 --> 00:52:19.289
a previous state of this the channels.
800
00:52:19.750 --> 00:52:23.609
And once that database have been running in another instance,
801
00:52:24.069 --> 00:52:24.890
those dates
802
00:52:25.305 --> 00:52:27.965
states obviously get updated with with the peers
803
00:52:28.745 --> 00:52:42.420
as well as on that instance. And then if you boot up the old one again I mean, you could boot up, but if you would run l and d or c lightning on the on the old one again, then you would try to
804
00:52:43.015 --> 00:52:43.994
build on the
805
00:52:45.174 --> 00:52:48.075
the previous states, which then your peers would penalize
806
00:52:48.454 --> 00:52:49.914
and losing all your channel
807
00:52:50.320 --> 00:52:53.220
funds. All the channel funds would go on to the,
808
00:52:53.920 --> 00:52:58.545
to the other side, which is which is a penalty mechanism of of of the current
809
00:52:58.944 --> 00:53:01.765
Lightning protocol. So it's important to prevent,
810
00:53:02.065 --> 00:53:04.405
but you can easily do that when you are moving
811
00:53:05.025 --> 00:53:06.005
between hardwares.
812
00:53:06.464 --> 00:53:07.285
You take
813
00:53:08.410 --> 00:53:11.310
so what what do you have for for lightning? You have
814
00:53:11.849 --> 00:53:12.910
a wallet file,
815
00:53:13.210 --> 00:53:15.310
which is like a wallet dotdb
816
00:53:16.295 --> 00:53:18.635
for lnd. It's like an HSM secret
817
00:53:19.974 --> 00:53:21.035
for c lightning.
818
00:53:21.415 --> 00:53:24.635
It it contains the keys with from which the Bitcoin keys
819
00:53:25.280 --> 00:53:26.260
are derived from.
820
00:53:26.720 --> 00:53:30.500
And then you have another file which is called the channel DB
821
00:53:31.040 --> 00:53:32.180
or the lightning
822
00:53:33.135 --> 00:53:33.635
SQLite,
823
00:53:34.494 --> 00:53:36.435
which is a database of your lightning
824
00:53:36.815 --> 00:53:37.315
net
825
00:53:37.855 --> 00:53:39.234
lightning channel states,
826
00:53:40.150 --> 00:53:40.650
which
827
00:53:41.670 --> 00:53:43.930
is containing the keys for the off chain funds,
828
00:53:44.470 --> 00:53:48.250
which is the ones in the lightning channel. So, basically, these two files
829
00:53:48.615 --> 00:53:57.435
just needs to be moved to the new instance. And as as Stelica said, it's a great practice to make sure that the new setup works by just, you know,
830
00:53:58.440 --> 00:54:04.780
running a new node on it and make sure that there are no, you know, bugs or, like, things which are would
831
00:54:05.640 --> 00:54:06.700
stop you from
832
00:54:07.855 --> 00:54:09.954
stop it from working. And then
833
00:54:10.494 --> 00:54:14.435
you can just take these old files and put it in place of the of the
834
00:54:16.100 --> 00:54:16.920
new ones.
835
00:54:17.300 --> 00:54:20.520
So your old ones would move in place to this
836
00:54:21.620 --> 00:54:22.120
new
837
00:54:22.660 --> 00:54:23.160
setup.
838
00:54:23.860 --> 00:54:24.360
And
839
00:54:25.815 --> 00:54:27.755
while you're moving, you would need
840
00:54:28.055 --> 00:54:29.434
to rename those directories
841
00:54:30.214 --> 00:54:33.434
or I mean, don't delete them key backups, but
842
00:54:34.570 --> 00:54:36.830
just move them and make sure it won't be a functional
843
00:54:38.170 --> 00:54:39.470
software again when
844
00:54:40.090 --> 00:54:41.150
the computer starts
845
00:54:42.275 --> 00:54:43.655
with the same day score,
846
00:54:43.955 --> 00:54:45.255
with the old disk again.
847
00:54:45.875 --> 00:54:46.375
So
848
00:54:46.835 --> 00:54:48.435
and, also, I mean, I've done
849
00:54:48.915 --> 00:54:52.055
in terms of moving to a completely new type of machine,
850
00:54:52.420 --> 00:54:52.920
Like,
851
00:54:53.300 --> 00:54:54.119
there's been
852
00:54:54.819 --> 00:54:56.119
a problem recently
853
00:54:56.420 --> 00:54:57.880
when we discovered
854
00:54:58.260 --> 00:55:00.920
that when the LND database, general database,
855
00:55:01.465 --> 00:55:03.485
does grow above 1 gigabytes,
856
00:55:03.865 --> 00:55:07.005
which is if you are, like, running rebalance scripts or,
857
00:55:07.785 --> 00:55:09.485
you know, having a lot of payments
858
00:55:10.010 --> 00:55:13.790
and or making a lot of payments that can happen fairly quickly
859
00:55:14.170 --> 00:55:18.030
within couple of months really with, like, you know, 20, 30 channels.
860
00:55:19.105 --> 00:55:19.585
And,
861
00:55:20.065 --> 00:55:22.645
it stops working on the 32 bit
862
00:55:23.185 --> 00:55:24.325
Raspberry Pi
863
00:55:25.185 --> 00:55:28.130
OS, which is which is a good thing that the
864
00:55:28.930 --> 00:55:33.910
Raspberry Pi itself, Raspberry Pi 3 and 4 themselves is 64 bit compatible.
865
00:55:35.819 --> 00:55:44.020
But the default operating system which the Raspberry Pi Foundation does distribute to be compatible with zeros and everything else is 32 bit
866
00:55:44.900 --> 00:55:48.680
and that is not supported by LND, for example. So we need to
867
00:55:49.140 --> 00:55:52.520
move a lot of nodes. I mean, I did a couple myself
868
00:55:52.945 --> 00:55:58.405
from this 32 bit architecture to 64 bit 1, which was which is was
869
00:55:58.705 --> 00:56:01.710
clearly not recommended in the in the documentation
870
00:56:02.570 --> 00:56:03.870
of l and d, for example.
871
00:56:04.490 --> 00:56:06.590
But then it worked without without problems.
872
00:56:06.890 --> 00:56:09.934
Yeah. Hashtag reckless. You know, the first one I was sweating, but,
873
00:56:10.494 --> 00:56:12.355
second one was not that bad.
874
00:56:12.734 --> 00:56:14.515
And then I moved further
875
00:56:14.815 --> 00:56:15.315
to
876
00:56:16.575 --> 00:56:21.630
when these databases now, you know, grow to be, like, you know, 6, 7, 8 gigabytes
877
00:56:22.250 --> 00:56:22.750
and,
878
00:56:23.130 --> 00:56:25.630
you know, the number of the channels are growing,
879
00:56:25.930 --> 00:56:26.750
I moved them
880
00:56:28.925 --> 00:56:30.145
to proper x8664
881
00:56:31.165 --> 00:56:33.905
bit architecture, which is like an old server,
882
00:56:35.910 --> 00:56:38.650
which you can you can get for, like, you know, 2 £200
883
00:56:40.470 --> 00:56:40.970
ish.
884
00:56:41.510 --> 00:56:42.710
You know, something which,
885
00:56:43.350 --> 00:56:44.090
has, like,
886
00:56:46.315 --> 00:56:47.934
5, 6 years old,
887
00:56:48.954 --> 00:56:50.015
industrial setup.
888
00:56:50.954 --> 00:57:02.040
So it is not not a big investment, but then you can start stacking disks in it and, like, and fall down all sorts of rabbit holes about data security and integrity and etcetera.
889
00:57:04.384 --> 00:57:18.130
And then even between operating systems, you know, these files, the, like, developed database and the channel database, these these can be moved. So it's it's doable. Just need to be careful where where you put things and don't destroy data and then just concentrate on not
890
00:57:18.910 --> 00:57:19.410
running
891
00:57:19.790 --> 00:57:21.330
old instances as well.
892
00:57:21.635 --> 00:57:24.295
893
00:57:25.234 --> 00:57:29.175
people just shouldn't even have them most people shouldn't even have that many channels open.
894
00:57:29.714 --> 00:57:30.694
They should just,
895
00:57:31.930 --> 00:57:33.710
you know, keep it to the bare minimum
896
00:57:34.490 --> 00:57:38.430
and and maybe even why even migrate in that situation? Why not just
897
00:57:40.065 --> 00:57:40.885
close channels
898
00:57:41.185 --> 00:57:44.725
and close those few channels you have and open new ones on the
899
00:57:45.105 --> 00:57:46.140
on the new node?
900
00:57:47.339 --> 00:57:53.660
901
00:57:54.460 --> 00:57:59.155
or no? It's is it 8 8 sets per byte? But, still Oh, big spending.
902
00:58:00.734 --> 00:58:05.950
903
00:58:07.050 --> 00:58:07.550
then
904
00:58:08.090 --> 00:58:11.550
closing channels and opening. If you have, like, 5 or 10 channels,
905
00:58:12.455 --> 00:58:13.595
It's probably also
906
00:58:14.135 --> 00:58:19.595
907
00:58:21.040 --> 00:58:24.100
908
00:58:26.400 --> 00:58:26.900
909
00:58:27.235 --> 00:58:31.815
Well, you can you won't make money, but you can save and you can do things
910
00:58:32.915 --> 00:58:35.575
you can do things which you You can look for them. Platform.
911
00:58:36.115 --> 00:58:36.870
Yeah. Exactly.
912
00:58:38.790 --> 00:58:44.570
Cool. I mean, it's like, yeah, it's like, why why would you buy a car a car which would consume less? Right?
913
00:58:45.775 --> 00:58:46.275
914
00:58:46.655 --> 00:58:52.515
I mean, we had another comment in the chat about someone saying they like to use a
915
00:58:52.859 --> 00:58:58.560
brand new Mac mini with the their m one chip and a 2 terabyte SSD in it,
916
00:58:59.420 --> 00:59:03.205
for their node. Do you have any feedback for that person?
917
00:59:05.425 --> 00:59:06.885
918
00:59:08.625 --> 00:59:09.125
919
00:59:10.549 --> 00:59:13.290
920
00:59:13.990 --> 00:59:19.049
921
00:59:23.055 --> 00:59:25.075
try the machine itself, but
922
00:59:25.535 --> 00:59:27.875
I've heard tests that it was, like,
923
00:59:28.255 --> 00:59:36.410
validating the whole chain in, like, 4 hours or so Oh, wow. When it came out. And, you know, it's certainly powerful enough to be,
924
00:59:37.109 --> 00:59:38.730
able to deal with the situation.
925
00:59:39.975 --> 00:59:45.035
But, you know, run Linux on it. I mean, I don't know. Does it commit like a fixed operating system?
926
00:59:45.575 --> 00:59:47.515
Don't use closed source operating systems?
927
00:59:48.170 --> 00:59:50.190
928
00:59:50.730 --> 00:59:52.190
929
00:59:53.210 --> 00:59:54.910
930
00:59:55.425 --> 00:59:56.405
Secure Elements
931
00:59:56.785 --> 00:59:58.165
bullshit in there or something?
932
01:00:00.305 --> 01:00:01.445
933
01:00:02.385 --> 01:00:04.885
934
01:00:05.490 --> 01:00:10.069
I've never tried it. Then jailbreak it. You know? Yes. Yeah. Jailbreak it. Exactly.
935
01:00:10.530 --> 01:00:11.750
Jailbreak your $2,000
936
01:00:12.050 --> 01:00:14.630
computer or whatever it is. A $1,000 computer.
937
01:00:16.265 --> 01:00:17.325
But, yeah, I mean,
938
01:00:17.704 --> 01:00:22.345
if if your node is holding, if you care about your privacy, if your node's holding a decent amount of funds,
939
01:00:24.099 --> 01:00:26.839
running the closed source OSX platform,
940
01:00:27.619 --> 01:00:30.839
that Mac should get shipped with by default is a
941
01:00:31.700 --> 01:00:32.680
dangerous game.
942
01:00:36.725 --> 01:00:38.505
So where do we wanna go from here?
943
01:00:41.960 --> 01:00:42.460
944
01:00:42.840 --> 01:00:45.500
open up suggested before to
945
01:00:46.600 --> 01:00:49.020
do a quick run through the guide,
946
01:00:49.464 --> 01:00:55.484
and I wanted to take a step back. But I guess we we took a step back and took a little walk
947
01:00:55.865 --> 01:00:56.605
from there,
948
01:00:57.930 --> 01:00:58.430
Maybe
949
01:00:58.809 --> 01:00:59.309
going
950
01:00:59.770 --> 01:01:06.109
through the quickly through the individual parts of the guide and give some comments here and there could be something.
951
01:01:06.494 --> 01:01:07.315
952
01:01:08.645 --> 01:01:09.395
953
01:01:10.415 --> 01:01:10.915
So,
954
01:01:13.910 --> 01:01:16.410
of course, like, if you if you go to raspi bolt.org,
955
01:01:16.950 --> 01:01:20.410
it gives you some, like, okay, what is it?
956
01:01:21.385 --> 01:01:22.045
How is structured?
957
01:01:23.065 --> 01:01:26.845
There's, like, I think, a pretty important part about the community
958
01:01:27.625 --> 01:01:32.060
where you can like, if you run into problems, you can open an an issue on GitHub.
959
01:01:32.520 --> 01:01:33.820
There's a knowledge base.
960
01:01:34.520 --> 01:01:35.820
There's a Reddit sub.
961
01:01:36.440 --> 01:01:38.265
You can join the Telegram group.
962
01:01:39.305 --> 01:01:41.644
So there's lots of people that
963
01:01:41.944 --> 01:01:44.045
want to help you if you're stuck somewhere.
964
01:01:45.144 --> 01:01:52.590
And from there, it's basically separated in 3 parts, like the the Raspberry Pi itself, including the operating system,
965
01:01:52.970 --> 01:01:56.030
then the Bitcoin on chain part, and then lightning.
966
01:01:57.125 --> 01:01:57.625
And
967
01:01:58.005 --> 01:02:00.425
after that, this is, like, the core guide.
968
01:02:02.005 --> 01:02:04.265
We aim to have, like, a high
969
01:02:06.849 --> 01:02:11.349
maintenance guarantee on the core guide. So it should be should mostly be up to date.
970
01:02:12.369 --> 01:02:14.035
If there's, like, something that
971
01:02:14.595 --> 01:02:18.135
no longer works, we're we're very happy to fix it quickly.
972
01:02:18.674 --> 01:02:24.170
But then there's also the bonus section, and this is more meant to be a collection of additional,
973
01:02:24.710 --> 01:02:25.770
optional guides,
974
01:02:26.390 --> 01:02:28.010
also from external contributors.
975
01:02:28.710 --> 01:02:33.345
And I think it's it can be pretty interesting to just have a collection of
976
01:02:33.645 --> 01:02:34.944
fun stuff to do.
977
01:02:35.325 --> 01:02:36.224
But, of course,
978
01:02:37.780 --> 01:02:44.760
stuff like that can become outdated, and it's not really possible to keep everything up to date in that bonus guide section.
979
01:02:45.565 --> 01:02:50.305
But this is really what I imagine a bit have, like, a a really well maintained core section
980
01:02:50.845 --> 01:02:52.065
and a a good,
981
01:02:52.765 --> 01:02:53.985
collection of
982
01:02:54.540 --> 01:02:58.160
individual guides or fun stuff to do on top of that,
983
01:03:00.220 --> 01:03:03.280
installing other applications and all that
984
01:03:03.580 --> 01:03:04.285
fun stuff.
985
01:03:07.005 --> 01:03:07.505
So,
986
01:03:08.285 --> 01:03:11.184
I mean, basically, the first thing you do is get a Raspberry
987
01:03:11.724 --> 01:03:12.224
Pi.
988
01:03:14.800 --> 01:03:18.660
The one thing that is really important, get the official power adapter.
989
01:03:19.280 --> 01:03:22.954
I've had I've I've wasted so much of my own time
990
01:03:23.255 --> 01:03:24.315
with using, like,
991
01:03:25.255 --> 01:03:27.355
regular USB adapters. And
992
01:03:28.110 --> 01:03:34.610
if you want to have a stable Raspberry Pi, just use the official one. This is the the one learning I took after
993
01:03:35.285 --> 01:03:36.184
hours of wasted,
994
01:03:38.165 --> 01:03:39.145
kernel panics
995
01:03:39.605 --> 01:03:40.345
and shutdowns.
996
01:03:42.085 --> 01:03:44.265
After that, you just install the
997
01:03:44.589 --> 01:03:49.970
the operating system. And as OpenNoms mentioned, it's really important to get the 64 bit,
998
01:03:50.270 --> 01:03:51.569
Raspberry Pi OS,
999
01:03:51.945 --> 01:03:53.965
which officially is still in beta,
1000
01:03:54.825 --> 01:03:56.845
but it works really well.
1001
01:03:57.785 --> 01:04:02.609
It's been running, I think, for months now on my note without a single restart.
1002
01:04:03.230 --> 01:04:04.609
I don't really think,
1003
01:04:05.710 --> 01:04:06.210
there's
1004
01:04:07.025 --> 01:04:07.525
much
1005
01:04:07.825 --> 01:04:09.285
instability in it.
1006
01:04:09.585 --> 01:04:12.965
So that's that's pretty cool. It's based on Debian, so
1007
01:04:13.560 --> 01:04:14.940
it's really a standard
1008
01:04:15.320 --> 01:04:16.280
Debian based,
1009
01:04:16.600 --> 01:04:17.100
Linux
1010
01:04:17.560 --> 01:04:18.060
system.
1011
01:04:19.240 --> 01:04:20.380
The cool thing is,
1012
01:04:21.000 --> 01:04:22.220
the Raspberry Pi
1013
01:04:22.744 --> 01:04:23.724
also provides
1014
01:04:24.744 --> 01:04:25.404
an application
1015
01:04:25.704 --> 01:04:27.085
to actually flash,
1016
01:04:28.424 --> 01:04:29.644
the operating system.
1017
01:04:30.770 --> 01:04:34.310
And what's really cool is that you can flash it directly on a SSD.
1018
01:04:34.690 --> 01:04:38.790
So you don't really need to use a micro s s a micro SD card
1019
01:04:39.125 --> 01:04:41.785
because in my experience, this is the weakest
1020
01:04:42.085 --> 01:04:43.625
part of the node.
1021
01:04:44.725 --> 01:04:46.345
Micro SD cards just
1022
01:04:46.840 --> 01:04:50.700
are not meant for constant write read and write operations.
1023
01:04:51.480 --> 01:04:51.980
So
1024
01:04:52.360 --> 01:04:59.785
after a year a year or or a bit more, maybe a bit less, they tend to wear out, at least mine did.
1025
01:05:00.645 --> 01:05:01.145
So
1026
01:05:02.970 --> 01:05:03.630
you can
1027
01:05:04.010 --> 01:05:04.750
write the
1028
01:05:05.210 --> 01:05:07.390
operating system directly on the SSD
1029
01:05:07.770 --> 01:05:16.915
and boot for directly from the SSD. You don't even need a micro SD card. I think that's that's pretty cool and improves the overall stability of the node a lot.
1030
01:05:19.170 --> 01:05:20.630
1031
01:05:21.410 --> 01:05:27.895
change you have done with the it came in the v three, isn't it? Yeah. Exactly. Because it it it wasn't like that. And,
1032
01:05:30.355 --> 01:05:33.335
I have mixed feeling about mixed feelings about this because
1033
01:05:34.220 --> 01:05:36.460
it's easy to change a micro SD card, but then
1034
01:05:37.660 --> 01:05:40.720
I mean, even with my regular computer, you know, it's like, running
1035
01:05:41.099 --> 01:05:43.520
without partitions on your disk. Right?
1036
01:05:43.825 --> 01:05:47.045
That you have, like, just all eggs in 1 basket kind of
1037
01:05:47.345 --> 01:05:48.485
kind of thing. So,
1038
01:05:48.785 --> 01:05:53.890
I like having a a micro SD in in a setup like this because then you have just
1039
01:05:54.350 --> 01:05:56.290
a a separate physical device to
1040
01:05:56.750 --> 01:06:00.690
to replicate some of the things. For example, this this status channel backup
1041
01:06:00.990 --> 01:06:01.490
on.
1042
01:06:01.895 --> 01:06:05.035
So if one fails, you don't have everything failed.
1043
01:06:07.255 --> 01:06:09.735
1044
01:06:10.610 --> 01:06:15.030
plan to do, like, in the next weeks, I guess, it's top list.
1045
01:06:15.730 --> 01:06:16.230
Actually,
1046
01:06:16.850 --> 01:06:18.325
as part of the core guides,
1047
01:06:18.805 --> 01:06:21.945
just plug in them, like a USB thumb drive
1048
01:06:22.724 --> 01:06:29.380
and directly store the static channel backup on that one. So we do have then redundancy again.
1049
01:06:30.160 --> 01:06:31.859
And we also include
1050
01:06:32.560 --> 01:06:33.220
a a little
1051
01:06:33.600 --> 01:06:34.065
guide,
1052
01:06:34.545 --> 01:06:37.605
how to upload and sync the static channel,
1053
01:06:38.545 --> 01:06:42.085
backup file to your own private GitHub repository
1054
01:06:42.385 --> 01:06:44.260
as like as a like a
1055
01:06:44.560 --> 01:06:48.100
let's say, a cloud drive or something like that.
1056
01:06:48.880 --> 01:06:52.055
1057
01:06:52.855 --> 01:06:53.355
Exactly.
1058
01:06:54.775 --> 01:07:00.795
Yeah. So and then, I mean, micro SDs indeed fail. They do access these 2, unfortunately.
1059
01:07:01.170 --> 01:07:01.829
But then
1060
01:07:02.369 --> 01:07:04.770
you you really so as just
1061
01:07:05.490 --> 01:07:05.990
as,
1062
01:07:06.530 --> 01:07:11.515
you mentioned with the power supply, it really depends on the quality you buy
1063
01:07:12.135 --> 01:07:12.635
and
1064
01:07:13.495 --> 01:07:15.755
if it is what is written on the box.
1065
01:07:16.730 --> 01:07:21.630
Because we say, like, you know, buy buy a power supply which provides 3 amperes or more.
1066
01:07:22.010 --> 01:07:26.915
Well, not all of them are capable of doing that what is written on it. So,
1067
01:07:27.535 --> 01:07:30.915
indeed, I do for sure one is a good choice, but there are a couple like,
1068
01:07:33.615 --> 01:07:34.115
shop
1069
01:07:34.690 --> 01:07:37.349
does sell one which is called universal,
1070
01:07:38.609 --> 01:07:44.255
power supply, which is good quality as well and been been proving itself. And then regarding the SD cards,
1071
01:07:44.635 --> 01:07:50.335
we really found that, like, the endurance models from, like, some disk or
1072
01:07:50.715 --> 01:07:51.215
something
1073
01:07:52.859 --> 01:07:58.915
do the job much better in terms of, they have been designed to be Mhmm. Installed in, like,
1074
01:07:59.475 --> 01:08:01.975
you know, dashboard cameras and stuff like that, which are,
1075
01:08:02.355 --> 01:08:03.655
like, written constantly,
1076
01:08:04.755 --> 01:08:05.975
and they supposed to
1077
01:08:06.275 --> 01:08:08.950
last for a good couple of 1,000 hours.
1078
01:08:10.050 --> 01:08:12.070
So if you would happen to use
1079
01:08:12.370 --> 01:08:14.150
a micro SD, then
1080
01:08:14.450 --> 01:08:14.950
then
1081
01:08:15.625 --> 01:08:17.005
then use a good one.
1082
01:08:17.465 --> 01:08:19.565
I I can I wouldn't recommend that?
1083
01:08:19.865 --> 01:08:31.739
But then with the SSD, you would you should probably have some speed up as well. So the operating system would run faster if you are booting if you are booting from that. So it's a it's it's a really good, yeah, technical solution for sure.
1084
01:08:33.575 --> 01:08:40.955
1085
01:08:41.980 --> 01:08:45.760
flash it on a micro SD card and still boot from that. So
1086
01:08:46.780 --> 01:08:48.800
it's not like you're locked out
1087
01:08:49.115 --> 01:08:51.135
because just because everything's on the same
1088
01:08:51.515 --> 01:08:56.975
drive. But, yeah, I fully agree redundancy, especially with the backups, is super important.
1089
01:09:01.340 --> 01:09:02.400
1090
01:09:04.139 --> 01:09:07.114
Then Don't use the cheap SD card for sure.
1091
01:09:07.894 --> 01:09:11.994
1092
01:09:12.934 --> 01:09:15.195
So, yeah, choose choose the parts wisely.
1093
01:09:16.489 --> 01:09:22.989
That's all I can say because loads of like, half of the issues are hardware based with these kind of things. Mhmm. Yeah.
1094
01:09:23.605 --> 01:09:27.945
1095
01:09:28.804 --> 01:09:32.265
single board computers as well. For example, the Rok Pro
1096
01:09:32.580 --> 01:09:33.080
64.
1097
01:09:33.699 --> 01:09:34.099
Yes.
1098
01:09:35.380 --> 01:09:43.195
And in my experience, I didn't find a board that comes close to the, like, uptime and reliability of a Raspberry Pi.
1099
01:09:43.735 --> 01:09:44.395
So even
1100
01:09:45.255 --> 01:09:47.034
even with a rock pro 64,
1101
01:09:47.490 --> 01:09:49.030
if you run them, like, 247,
1102
01:09:49.410 --> 01:09:49.910
there's
1103
01:09:50.530 --> 01:09:57.110
from time to time, it can be, like, 3 months, but it can also be just 2 weeks. There's a kernel panic, and it just freezes.
1104
01:09:57.785 --> 01:09:59.085
That really, really sucks
1105
01:09:59.545 --> 01:10:03.085
if you're not at home to reboot your node and you want to make some payments.
1106
01:10:03.945 --> 01:10:07.460
1107
01:10:08.100 --> 01:10:17.764
kind of walk through of the guide. Mhmm. But my favorite part, actually, which is which is in the in the FAQ, I think, and on just getting get there on the end.
1108
01:10:18.864 --> 01:10:22.885
It's not in the FAQ. It's in the bonus section, I guess, where you can
1109
01:10:23.340 --> 01:10:25.360
use different computers like
1110
01:10:25.660 --> 01:10:27.840
like the. Yeah. Yeah. There is hardware
1111
01:10:28.220 --> 01:10:28.720
setup,
1112
01:10:29.100 --> 01:10:29.840
which is
1113
01:10:31.665 --> 01:10:39.045
the famous top thumb droid was, you know, the basis of many many things. Like, most famously, I think it has been running
1114
01:10:40.730 --> 01:10:42.110
the set of his place
1115
01:10:42.410 --> 01:10:42.910
initially,
1116
01:10:43.770 --> 01:10:46.910
before he he scaled up, obviously. It picked up a bit.
1117
01:10:48.225 --> 01:10:50.805
And I did use these as well because
1118
01:10:51.345 --> 01:10:56.245
I've, just, you know, came to the rest of the day. Place was running on an originally?
1119
01:10:56.920 --> 01:10:58.620
1120
01:10:58.920 --> 01:11:00.220
In Bitcoin Quala's
1121
01:11:00.680 --> 01:11:02.780
closet, I think. So Yeah. Exactly.
1122
01:11:04.135 --> 01:11:09.675
1123
01:11:10.295 --> 01:11:10.795
Yes.
1124
01:11:13.790 --> 01:11:16.370
So so yes. So so so just
1125
01:11:16.670 --> 01:11:19.250
obviously everything starts with getting the hardware.
1126
01:11:19.710 --> 01:11:21.410
It is interesting to find
1127
01:11:21.745 --> 01:11:27.264
to to hear your experience about the rock pro because in this old radio guide, you still, recommending these,
1128
01:11:28.225 --> 01:11:29.605
x u 4 and hcone
1129
01:11:30.400 --> 01:11:31.320
ones Mhmm.
1130
01:11:31.740 --> 01:11:33.780
Which are especially the hcone
1131
01:11:34.400 --> 01:11:36.100
has, like, a built in adapter.
1132
01:11:36.720 --> 01:11:39.300
So you can put the disk right attached
1133
01:11:39.615 --> 01:11:44.115
to the board, very stable, has a huge heat sink around it, which is the case as well.
1134
01:11:44.735 --> 01:11:46.835
But the problem is it has,
1135
01:11:47.390 --> 01:11:58.534
like, a 7th generation processor, which is only 30 32 bit, but it's not possible to run 64 bit on it. So I would consider that a little I mean, I I would consider that outdated.
1136
01:12:01.155 --> 01:12:11.690
But then there is the pro 64, which is popular with other projects like running Dojo, for example. They are I think they just released the new kind of preview at nodes, which is built based on it.
1137
01:12:12.235 --> 01:12:14.415
And and and you yourself had a lot of experience,
1138
01:12:14.875 --> 01:12:15.775
working with ShiftCrypto
1139
01:12:16.555 --> 01:12:17.615
with the bit BitBox
1140
01:12:18.795 --> 01:12:19.295
projects.
1141
01:12:20.230 --> 01:12:22.410
Space. Yeah. Bitbox space that was,
1142
01:12:23.110 --> 01:12:27.850
which was an it's it's an amazing and still up. Right? It's just, it's maintained?
1143
01:12:28.755 --> 01:12:35.415
1144
01:12:36.034 --> 01:12:37.015
Yeah. Exactly.
1145
01:12:37.590 --> 01:12:43.130
1146
01:12:43.590 --> 01:12:44.615
1147
01:12:45.415 --> 01:12:47.195
I think we we built on the,
1148
01:12:48.695 --> 01:12:49.195
distribution.
1149
01:12:50.375 --> 01:12:54.315
And it might just as well be that there are, like, some
1150
01:12:54.650 --> 01:12:57.230
some NUCs in in in the distributions
1151
01:12:57.850 --> 01:13:08.415
1152
01:13:08.715 --> 01:13:09.935
that widely used.
1153
01:13:10.235 --> 01:13:10.735
1154
01:13:11.595 --> 01:13:12.410
1155
01:13:12.890 --> 01:13:13.390
kernel
1156
01:13:14.330 --> 01:13:14.830
written
1157
01:13:15.290 --> 01:13:18.270
for it is basically not that well tested.
1158
01:13:18.970 --> 01:13:21.390
And that's been a problem with the previous,
1159
01:13:23.035 --> 01:13:24.335
kind of rock 64
1160
01:13:24.795 --> 01:13:30.895
board as well, which just, you know, many of them has been have been like, they were physically
1161
01:13:33.480 --> 01:13:36.540
they were, like, dead on arrival or or they were, like,
1162
01:13:37.000 --> 01:13:42.934
doing calculation errors, which is obviously not acceptable for for a Bitcoin node. Right? And the rock support 64
1163
01:13:43.474 --> 01:13:47.735
got much better and it also has like a PCI Express port where you can
1164
01:13:48.900 --> 01:13:49.400
apply
1165
01:13:50.340 --> 01:13:51.000
an NVMe
1166
01:13:51.540 --> 01:13:55.960
SSD. Exactly. So the ones which are usually found in laptops or, like,
1167
01:13:57.075 --> 01:13:57.575
systems
1168
01:13:58.115 --> 01:13:59.415
built for speed.
1169
01:14:00.835 --> 01:14:02.695
And that that that is very good.
1170
01:14:04.195 --> 01:14:04.935
The hackle
1171
01:14:05.650 --> 01:14:08.390
projects or HAC0, they call it, by
1172
01:14:08.770 --> 01:14:09.830
Nicolas Dore
1173
01:14:10.930 --> 01:14:15.110
with BTC based server, they were distributing these orders. So I have one with his
1174
01:14:15.635 --> 01:14:16.535
golden signature.
1175
01:14:18.114 --> 01:14:24.695
1176
01:14:25.219 --> 01:14:29.960
1177
01:14:30.340 --> 01:14:30.659
But,
1178
01:14:31.619 --> 01:14:37.445
I have 2 of those. One from the hack 0, one I got personally from you, and a hack day in Munich Mhmm.
1179
01:14:38.625 --> 01:14:38.945
Which,
1180
01:14:40.210 --> 01:14:49.429
I did say that I will once run a server, well, there will be, you know, SSDs in the PCI Express ports, and that that's just what I have put together in last week,
1181
01:14:51.455 --> 01:14:51.955
where
1182
01:14:52.335 --> 01:14:54.915
on the motherboard, I can just, you know, put these,
1183
01:14:56.335 --> 01:14:58.275
PCI Express to NVMe
1184
01:14:58.655 --> 01:14:59.155
adapters
1185
01:14:59.770 --> 01:15:03.470
and, have much more space. And Mhmm. They are fantastically
1186
01:15:04.090 --> 01:15:05.150
fast as well.
1187
01:15:05.850 --> 01:15:10.735
So Cool. Yeah. And I have this shift script to logo on them. So it's
1188
01:15:11.115 --> 01:15:12.415
it's it looks really nice.
1189
01:15:14.635 --> 01:15:15.135
1190
01:15:15.515 --> 01:15:17.775
But at at least something came out of that.
1191
01:15:19.570 --> 01:15:20.790
1192
01:15:21.250 --> 01:15:24.869
You can you can buy these kind of adapters for, like, 4, £5.
1193
01:15:26.130 --> 01:15:27.995
So, like, up to $10 or so,
1194
01:15:28.955 --> 01:15:30.335
but they don't look as nice.
1195
01:15:30.715 --> 01:15:37.455
And they have a for Yeah. They have a different different alignment. They have so if you want to put it on the Rogue Pro
1196
01:15:37.880 --> 01:15:40.860
64, then they would stick out on one end, which
1197
01:15:41.560 --> 01:15:44.940
which wouldn't be the best. In a motherboard, it's fine.
1198
01:15:45.320 --> 01:15:46.700
They would design for that.
1199
01:15:48.185 --> 01:15:50.925
But yeah. Yeah. I think that's that's all my comments on the hardware.
1200
01:15:51.625 --> 01:15:57.005
1201
01:15:57.400 --> 01:15:57.900
well
1202
01:15:58.360 --> 01:16:00.220
vetted and very reliable,
1203
01:16:01.400 --> 01:16:02.060
piece of
1204
01:16:02.600 --> 01:16:03.740
cheap hardware.
1205
01:16:04.280 --> 01:16:07.265
So it's probably not for, like, huge servers,
1206
01:16:07.885 --> 01:16:11.025
but in my experience, it's the most stable one. And
1207
01:16:11.645 --> 01:16:15.185
the problem is when we when we started building the Bitbox base,
1208
01:16:16.330 --> 01:16:21.630
the Raspberry Pi 4 wasn't out. So it wasn't even announced. So we had to look for something else.
1209
01:16:22.090 --> 01:16:26.844
Yeah. And but but looking back now, I probably would just build on the Raspberry Pi 4.
1210
01:16:29.225 --> 01:16:32.920
1211
01:16:33.380 --> 01:16:35.000
Pi is that closed source
1212
01:16:35.300 --> 01:16:36.600
kind of GPU
1213
01:16:37.620 --> 01:16:38.840
1214
01:16:39.380 --> 01:16:40.200
1215
01:16:40.905 --> 01:16:41.805
owned by Microsoft.
1216
01:16:43.785 --> 01:16:44.285
And
1217
01:16:45.145 --> 01:16:47.805
it's just running as a binary blob underneath,
1218
01:16:49.210 --> 01:16:51.550
which is not true to the old droid
1219
01:16:51.929 --> 01:16:54.830
or the old either the oldroids or the old pro,
1220
01:16:55.929 --> 01:16:57.070
single board computers.
1221
01:16:58.385 --> 01:17:03.685
So, I mean, that that is something which we just need to kind of live with. It's a trade off.
1222
01:17:05.050 --> 01:17:10.349
There is no fully open source hardware at all, but this is a bit less open source than the others.
1223
01:17:12.225 --> 01:17:17.285
I mean, here, the software is not fully open source either, the, operating system itself.
1224
01:17:18.864 --> 01:17:22.005
So there's something to keep in mind if you want to go
1225
01:17:22.849 --> 01:17:24.230
on the full verification
1226
01:17:24.929 --> 01:17:25.429
route.
1227
01:17:26.929 --> 01:17:27.429
1228
01:17:28.210 --> 01:17:28.690
That's,
1229
01:17:29.090 --> 01:17:33.695
I think there there are quite a few points that can be improved maybe over time.
1230
01:17:34.074 --> 01:17:34.955
1231
01:17:36.315 --> 01:17:39.670
that becomes an even larger concern as as it becomes,
1232
01:17:40.370 --> 01:17:43.430
more common for people to be running Bitcoin nodes on their SPA's.
1233
01:17:44.290 --> 01:17:45.170
Like, I feel like it's
1234
01:17:48.125 --> 01:17:49.025
you know, one of
1235
01:17:49.725 --> 01:17:51.265
the often cited advantages
1236
01:17:51.725 --> 01:17:53.905
is that it's off the shelf parts.
1237
01:17:54.285 --> 01:18:00.130
It's not Bitcoin specific, but, you know, when we start hitting numbers like 10,000, 20,000
1238
01:18:00.590 --> 01:18:02.610
Bitcoin nodes running on RASPIs,
1239
01:18:03.475 --> 01:18:05.735
doesn't that argument kinda get thrown out the window?
1240
01:18:07.475 --> 01:18:10.135
1241
01:18:10.950 --> 01:18:23.994
Like, there is this old rate chapter in the in the guide as we do with the as well for I even released a couple of, like, SD card images for these older it's, which I've used still using one myself.
1242
01:18:24.695 --> 01:18:28.954
And and then scale out and, you know, use
1243
01:18:29.310 --> 01:18:31.890
every kind of thing which can run Linux, basically.
1244
01:18:33.150 --> 01:18:38.290
And and aim and work for for fully open source hardware, which is, you know, something
1245
01:18:39.054 --> 01:18:41.875
or or at least different approaches and different architectures.
1246
01:18:42.815 --> 01:18:49.040
I think that's the solution. You cannot rely on on the adjustment, the Raspberry Pi, I don't think. And we shouldn't
1247
01:18:49.420 --> 01:18:51.520
give the impression that we are doing this.
1248
01:18:54.925 --> 01:18:56.225
1249
01:18:57.405 --> 01:18:57.905
So
1250
01:18:58.365 --> 01:18:59.265
about security,
1251
01:18:59.725 --> 01:19:02.145
if if you allow me to go back to the guide.
1252
01:19:03.040 --> 01:19:04.659
Please. After installing
1253
01:19:04.960 --> 01:19:09.780
the the operating system, I think the one chapter that I feel is
1254
01:19:10.425 --> 01:19:11.085
the most
1255
01:19:11.705 --> 01:19:12.205
underrepresented
1256
01:19:12.745 --> 01:19:13.885
with other projects
1257
01:19:14.425 --> 01:19:18.525
is how to actually secure your like, the platform itself.
1258
01:19:19.860 --> 01:19:22.040
So the Raspberry Bolt guides
1259
01:19:22.420 --> 01:19:24.360
immediately recommends you to,
1260
01:19:24.820 --> 01:19:28.755
create your own SSH login keys. So there's, like, a passwordless
1261
01:19:29.215 --> 01:19:29.715
login.
1262
01:19:31.935 --> 01:19:33.395
You enable the firewall.
1263
01:19:33.855 --> 01:19:34.915
There's, like, a
1264
01:19:38.360 --> 01:19:40.060
fail to ban that does, like,
1265
01:19:40.760 --> 01:19:44.460
rate limiting on on login trials and stuff like that.
1266
01:19:45.225 --> 01:19:45.725
And
1267
01:19:46.425 --> 01:19:55.390
one thing I feel is sometimes overlooked as well even for local network use is that I think everything that is transmitted over the Internet or
1268
01:19:56.330 --> 01:19:58.110
to a browser, let's say, like that,
1269
01:19:59.690 --> 01:20:04.335
if it contains, like, sensitive information, it probably should go over h d GPS.
1270
01:20:05.594 --> 01:20:07.135
So not in plain text.
1271
01:20:07.514 --> 01:20:11.454
So it also immediately makes you install NGINX
1272
01:20:11.930 --> 01:20:12.670
reverse proxy,
1273
01:20:13.770 --> 01:20:14.270
server
1274
01:20:14.730 --> 01:20:17.630
that can then be used by all other applications
1275
01:20:18.010 --> 01:20:18.510
like,
1276
01:20:19.275 --> 01:20:22.574
write the lightning or mempool or whatever you use.
1277
01:20:23.915 --> 01:20:33.699
I think the drawback is that some from time to time, you get some scary warnings in the browser because you don't have, like, your official own domain with a proper SSL certificate.
1278
01:20:34.320 --> 01:20:36.420
So the browser cannot really verify
1279
01:20:38.425 --> 01:20:39.224
if the,
1280
01:20:39.945 --> 01:20:42.045
the the certificate is is valid.
1281
01:20:42.425 --> 01:20:44.764
But if you accept it once usually,
1282
01:20:46.140 --> 01:20:47.440
then the browser
1283
01:20:47.820 --> 01:20:51.760
stores that certificate, and then you have a, like, fully end to end encrypted
1284
01:20:52.300 --> 01:20:52.800
communication
1285
01:20:53.100 --> 01:20:54.640
with your pi even
1286
01:20:55.215 --> 01:20:56.035
with the browser.
1287
01:20:56.895 --> 01:21:01.795
So I it always made me look really cringe if you, like, log in to
1288
01:21:02.415 --> 01:21:03.440
a ready made,
1289
01:21:04.480 --> 01:21:05.940
full note. And it
1290
01:21:06.640 --> 01:21:11.540
sometimes actually showed your seed words, which is, like, super bad in the browser
1291
01:21:12.304 --> 01:21:15.045
over in in not even through SSL
1292
01:21:15.985 --> 01:21:18.244
or made you log in without
1293
01:21:18.545 --> 01:21:19.925
2FA or anything,
1294
01:21:20.440 --> 01:21:24.220
just like transmitting the password over clear text for every
1295
01:21:24.760 --> 01:21:27.925
smart fridge to to see? Yeah.
1296
01:21:29.985 --> 01:21:39.100
1297
01:21:39.560 --> 01:21:41.260
to, you know, you run to VPS
1298
01:21:41.719 --> 01:21:47.054
and then what to do with it. I mean, these steps should be done on every kind of computer where you run anything
1299
01:21:47.835 --> 01:21:50.974
or or which has access to your network, which does have
1300
01:21:51.989 --> 01:21:55.270
computers, which don't do run anything. So it is,
1301
01:21:56.230 --> 01:21:58.010
it is a great part and very important.
1302
01:21:58.389 --> 01:22:00.489
SSL is absolutely and the and the
1303
01:22:00.975 --> 01:22:06.115
self signed certificate question, I mean, this is because you are not reaching out for a third party
1304
01:22:08.335 --> 01:22:09.460
to verify this
1305
01:22:09.860 --> 01:22:14.120
certificate with them or kind of or, like, ask the permission for
1306
01:22:15.460 --> 01:22:17.640
of a third party to use that certificate.
1307
01:22:17.945 --> 01:22:23.724
So then your browser won't be able to check with that third party that this is this is something official,
1308
01:22:24.264 --> 01:22:24.925
in quotes.
1309
01:22:25.784 --> 01:22:28.489
But then if you compare the numbers,
1310
01:22:28.790 --> 01:22:29.929
the fingerprints
1311
01:22:30.389 --> 01:22:31.849
can be verified, which
1312
01:22:32.150 --> 01:22:33.210
fingerprint you can
1313
01:22:33.590 --> 01:22:41.974
see on your machine serving the web page, and then you can compare it to the fingerprint which appears in your browser, which you can just see on that,
1314
01:22:43.270 --> 01:22:43.989
there is usually,
1315
01:22:44.469 --> 01:22:46.730
like, a lock icon next to the URL,
1316
01:22:47.750 --> 01:22:49.370
where you can see the certificate
1317
01:22:49.965 --> 01:22:51.905
and the details of the fingerprint.
1318
01:22:52.365 --> 01:22:57.585
That one you can compare to the to the server in your control, and then you can be completely
1319
01:22:58.380 --> 01:23:06.000
sure that it is coming from that place. It's similar as, similar to, like, verifying the signal or, like, a matrix peer.
1320
01:23:06.465 --> 01:23:09.525
Mhmm. But it happens with emojis in matrix, for example, isn't it?
1321
01:23:09.905 --> 01:23:10.965
So yeah.
1322
01:23:12.065 --> 01:23:12.565
Nice.
1323
01:23:13.105 --> 01:23:14.565
1324
01:23:15.600 --> 01:23:16.580
thing that we,
1325
01:23:17.440 --> 01:23:17.940
really,
1326
01:23:18.800 --> 01:23:23.060
narrowed the guide towards is that the the whole Raspberry Bolt,
1327
01:23:23.760 --> 01:23:24.580
node now
1328
01:23:25.135 --> 01:23:25.635
only,
1329
01:23:27.055 --> 01:23:28.755
runs over the Tor network.
1330
01:23:29.535 --> 01:23:34.880
So not every communication goes over Tor, but everything that is Bitcoin specific like lightning,
1331
01:23:35.440 --> 01:23:38.179
bitcoin, also all the remote login,
1332
01:23:38.560 --> 01:23:40.659
all the connections coming from the outside,
1333
01:23:41.280 --> 01:23:43.060
everything goes over Tor.
1334
01:23:43.440 --> 01:23:43.940
And
1335
01:23:45.285 --> 01:23:47.465
this is, of course, for privacy reasons.
1336
01:23:48.405 --> 01:23:50.185
We don't want to advertise
1337
01:23:50.565 --> 01:23:53.385
our own IP address, which can be geolocated
1338
01:23:53.685 --> 01:23:58.090
and tell the world, hey. At this house, there's there's somebody with Bitcoin.
1339
01:23:59.349 --> 01:24:01.750
But it's also if if I think back,
1340
01:24:03.095 --> 01:24:10.555
when people wanted to connect to their lightning note with there's, like, the the the universal plug and play
1341
01:24:10.935 --> 01:24:12.650
option in LME,
1342
01:24:13.190 --> 01:24:15.270
which mostly didn't work,
1343
01:24:15.670 --> 01:24:17.770
depending on your network setup.
1344
01:24:18.150 --> 01:24:20.970
It was, like, just a huge pain to
1345
01:24:21.574 --> 01:24:23.434
manually configure your router,
1346
01:24:24.855 --> 01:24:25.835
do, like, the
1347
01:24:26.454 --> 01:24:27.114
the dynamic
1348
01:24:27.415 --> 01:24:29.755
IP setup that you can actually reach
1349
01:24:30.460 --> 01:24:31.440
your own node
1350
01:24:31.900 --> 01:24:32.880
in your home
1351
01:24:33.420 --> 01:24:35.440
from the outside world,
1352
01:24:36.300 --> 01:24:40.805
basically going through your own router and then back to the node.
1353
01:24:41.185 --> 01:24:44.405
And this is so much easier if you just use Tor
1354
01:24:44.785 --> 01:24:49.045
because Tor just like calls from your notes to the outside world
1355
01:24:49.600 --> 01:24:50.740
into the Tor network.
1356
01:24:51.120 --> 01:24:52.180
It has its own,
1357
01:24:52.560 --> 01:24:53.540
onion address,
1358
01:24:54.000 --> 01:25:04.175
and that doesn't change. And everything is end to end encrypted in any case. So it's it's not only secure and, like, more private, but also much, much,
1359
01:25:04.795 --> 01:25:06.014
more user friendly
1360
01:25:06.450 --> 01:25:09.030
to to connect to your own node from anywhere.
1361
01:25:10.050 --> 01:25:12.950
1362
01:25:14.425 --> 01:25:18.125
You don't have to do any, like, port forwarding or anything on your router. Exactly.
1363
01:25:18.745 --> 01:25:20.505
But it's worth noting that,
1364
01:25:20.905 --> 01:25:23.760
Tor does have some reliability issues. So,
1365
01:25:25.340 --> 01:25:29.120
you will experience those from time to time, and it can be quite slow.
1366
01:25:31.195 --> 01:25:32.815
1367
01:25:34.235 --> 01:25:39.375
I think I was always able to reach my note, but you're right. From time to time, it can be very slow.
1368
01:25:40.500 --> 01:25:46.200
And that can of course, if you're using, like, a web interface that with a lot of connections
1369
01:25:46.555 --> 01:25:49.375
a lot of images and stuff that can be very serious.
1370
01:25:50.075 --> 01:25:57.110
But, also, if you connect, like, your your wallet to your own Electrum server, If it needs to look up a lot of,
1371
01:25:57.570 --> 01:26:03.590
addresses and stuff like that, that is significantly slower than using just like a plain net,
1372
01:26:04.975 --> 01:26:06.755
electron server. That's true.
1373
01:26:09.135 --> 01:26:11.315
1374
01:26:12.170 --> 01:26:15.070
feel the lag of typing. Yeah. True.
1375
01:26:16.570 --> 01:26:24.304
1376
01:26:25.485 --> 01:26:26.945
It's surprisingly easy.
1377
01:26:27.645 --> 01:26:35.310
1378
01:26:35.690 --> 01:26:38.095
So when when it does leak,
1379
01:26:38.715 --> 01:26:40.255
that information somehow,
1380
01:26:41.035 --> 01:26:51.020
like, you were using a a couple of versions back. You were using Mhmm. The Brave Browser, for example, which then pinged the clear net DNS server
1381
01:26:51.400 --> 01:26:52.940
with the only an address.
1382
01:26:53.525 --> 01:26:56.745
So publicized it to the ISP or the VPN provider,
1383
01:26:58.085 --> 01:27:00.645
then, you know, someone else can kind of,
1384
01:27:01.605 --> 01:27:02.985
try to guess your password
1385
01:27:03.590 --> 01:27:04.570
or or the password
1386
01:27:04.949 --> 01:27:09.210
of the service, which is which is running behind that, hidden service.
1387
01:27:11.284 --> 01:27:12.905
I mean, there are ways to
1388
01:27:13.525 --> 01:27:15.225
use key authentication
1389
01:27:15.605 --> 01:27:17.864
with Tor as well just like with SSH.
1390
01:27:18.880 --> 01:27:22.020
It's a bit more kind of cumbersome, but if you're like using
1391
01:27:23.120 --> 01:27:26.020
using SSH, you already should use key authentication.
1392
01:27:27.245 --> 01:27:29.985
So just to be aware that this is like a public domain.
1393
01:27:31.085 --> 01:27:32.785
Like, having an Internet address
1394
01:27:33.245 --> 01:27:33.985
is just
1395
01:27:35.340 --> 01:27:46.545
1396
01:27:47.405 --> 01:27:50.945
Yes. There are so many possibilities that we can It's unguessable.
1397
01:27:51.565 --> 01:27:56.430
Right. No one can well, we can assume that no one has the capability of brute forcing
1398
01:27:57.210 --> 01:27:57.710
that,
1399
01:27:58.570 --> 01:28:10.315
specific onion address. But if it leaks, then you have you have issues on your hand because other people can use that onion address, and you wanna make sure that whatever authentication that is, if it's a strong password or whatnot,
1400
01:28:11.270 --> 01:28:15.690
that that is is secure enough that you're not gonna get brute force at that point.
1401
01:28:16.550 --> 01:28:22.355
1402
01:28:22.895 --> 01:28:23.715
And the
1403
01:28:24.335 --> 01:28:27.795
that has failed to ban. I think if you try to log in
1404
01:28:28.960 --> 01:28:34.100
10 times in 5 minutes or so, you're just, like, immediately banned for 10 minutes or so.
1405
01:28:34.960 --> 01:28:36.740
So I would say SSH
1406
01:28:37.875 --> 01:28:40.135
itself is probably very secure.
1407
01:28:40.435 --> 01:28:44.295
Like, it's it's pretty common to have this port exposed.
1408
01:28:45.310 --> 01:28:51.650
But, of course, everything else should be secure as well. And I I think I read a a question in the very beginning why,
1409
01:28:52.350 --> 01:28:53.890
every web service
1410
01:28:54.454 --> 01:28:57.994
is now, like, separated and segregated into its own,
1411
01:28:58.375 --> 01:28:59.195
Linux user.
1412
01:28:59.974 --> 01:29:00.474
And
1413
01:29:01.094 --> 01:29:02.635
it it's not a perfect
1414
01:29:04.310 --> 01:29:04.810
protection,
1415
01:29:05.670 --> 01:29:06.650
but let's say
1416
01:29:07.030 --> 01:29:07.530
somebody
1417
01:29:08.230 --> 01:29:08.730
would,
1418
01:29:10.150 --> 01:29:10.650
find
1419
01:29:11.030 --> 01:29:11.610
a vulnerability
1420
01:29:11.989 --> 01:29:13.645
in, I don't know, whatever
1421
01:29:14.745 --> 01:29:18.285
whatever web service is reachable over Tor
1422
01:29:19.145 --> 01:29:23.005
and could gain access to to stuff it shouldn't have,
1423
01:29:23.580 --> 01:29:25.600
like SQL injection or whatever.
1424
01:29:26.140 --> 01:29:30.800
But that breach would still then be contained in this one
1425
01:29:31.340 --> 01:29:32.640
non root user
1426
01:29:33.825 --> 01:29:40.005
That that might be able to, for example, query Bitcoin Core, but it wouldn't have right access to anything.
1427
01:29:40.760 --> 01:29:44.860
So if an attacker would somehow get into,
1428
01:29:45.640 --> 01:29:49.100
your note, and I think every web service is a probably
1429
01:29:49.594 --> 01:29:52.495
is is a is a is a potential vulnerability.
1430
01:29:53.835 --> 01:29:59.215
It it still should be contained in that specific user, which basically doesn't have
1431
01:29:59.550 --> 01:30:04.690
right access to anything. It might be able to query some stuff, but it cannot do much damage.
1432
01:30:06.030 --> 01:30:15.595
1433
01:30:16.215 --> 01:30:17.835
but, you know, in a hypothetical
1434
01:30:18.780 --> 01:30:19.280
scenario,
1435
01:30:19.980 --> 01:30:21.760
if it would be. And
1436
01:30:22.780 --> 01:30:23.280
then
1437
01:30:24.139 --> 01:30:32.264
the attacker would possibly be able to extract the admin macaroon, for example, of to gain access to the funds on lightning. But,
1438
01:30:33.685 --> 01:30:34.344
I mean,
1439
01:30:35.445 --> 01:30:43.460
you wouldn't be able to access the other users, which, for example, there could be another hot wallet, for example, join markets running on the node,
1440
01:30:44.815 --> 01:30:46.594
under a separate user
1441
01:30:46.895 --> 01:30:49.315
with hot funds and keys there as well,
1442
01:30:50.014 --> 01:30:51.635
I mean, there is some protection,
1443
01:30:52.974 --> 01:30:53.474
against
1444
01:30:54.160 --> 01:30:54.820
that by
1445
01:30:55.440 --> 01:30:57.940
separating into different users,
1446
01:30:58.320 --> 01:31:02.179
especially if, you know, they have, like, web services running as well.
1447
01:31:03.145 --> 01:31:09.645
1448
01:31:10.025 --> 01:31:10.844
And I think the
1449
01:31:12.350 --> 01:31:15.890
because this is, like, handled directly by the operating system itself,
1450
01:31:16.430 --> 01:31:22.050
the the protection against, like, breaking out of that user is is much higher than, for example,
1451
01:31:23.215 --> 01:31:23.715
than
1452
01:31:24.335 --> 01:31:27.074
being able to break out of a Docker container,
1453
01:31:27.534 --> 01:31:28.034
which
1454
01:31:28.574 --> 01:31:32.420
many assume Docker is somehow, like, almost like a virtual machine
1455
01:31:32.880 --> 01:31:34.980
and give some security protection.
1456
01:31:35.599 --> 01:31:39.059
But because Docker actually runs as a pseudo user,
1457
01:31:39.625 --> 01:31:41.805
if you're able to break out of a Docker,
1458
01:31:42.425 --> 01:31:42.925
container,
1459
01:31:43.625 --> 01:31:45.085
that can be pretty serious.
1460
01:31:45.545 --> 01:31:47.965
So it's it's not really a security solution.
1461
01:31:49.300 --> 01:31:56.760
But I also need to say that I'm not no way an expert Docker expert. So Yeah. Yes. It's same as me. And I think most of these,
1462
01:31:57.945 --> 01:31:58.445
1463
01:31:58.905 --> 01:31:59.965
you know, the user
1464
01:32:02.425 --> 01:32:04.605
separation and Docker containers,
1465
01:32:05.380 --> 01:32:10.280
system d services, and everything else, it depends a lot on how you use them.
1466
01:32:10.740 --> 01:32:15.205
And what we can do is is kind of provide the best
1467
01:32:15.745 --> 01:32:16.245
practices
1468
01:32:16.705 --> 01:32:17.525
as there is,
1469
01:32:18.625 --> 01:32:19.125
to,
1470
01:32:19.985 --> 01:32:23.810
you know, to use the tools available the best possible way.
1471
01:32:24.770 --> 01:32:25.510
You can
1472
01:32:27.250 --> 01:32:30.930
so, yeah, none of them are are are silver bullets, but,
1473
01:32:32.050 --> 01:32:33.590
you can do the job well.
1474
01:32:34.695 --> 01:32:36.875
1475
01:32:37.335 --> 01:32:37.835
almost
1476
01:32:38.215 --> 01:32:42.395
1 and a half hours, and we're only in the preparation phase of the guide.
1477
01:32:44.520 --> 01:32:45.180
I mean,
1478
01:32:45.640 --> 01:32:46.860
as a quick overview,
1479
01:32:49.880 --> 01:33:00.415
now that the system is, like, ready, it's it's basically a a vanilla server now. It has everything that you need to run additional applications on that server.
1480
01:33:00.860 --> 01:33:03.760
And from it there, the guide goes on. You
1481
01:33:04.300 --> 01:33:05.520
download and
1482
01:33:05.980 --> 01:33:08.159
verify very, very importantly.
1483
01:33:08.965 --> 01:33:10.344
It explains exactly
1484
01:33:10.804 --> 01:33:13.225
step by step how you can verify,
1485
01:33:14.405 --> 01:33:17.864
the signatures of Bitcoin Core so that you know that
1486
01:33:18.410 --> 01:33:22.910
the Bitcoin Core you downloaded and are going to run is actually the official
1487
01:33:23.610 --> 01:33:24.110
vetted,
1488
01:33:25.610 --> 01:33:27.310
built of Bitcoin Core.
1489
01:33:28.355 --> 01:33:28.855
This
1490
01:33:29.235 --> 01:33:31.975
will sync with the whole network, download
1491
01:33:33.395 --> 01:33:37.469
the blockchain. Of course, you I guess everybody here knows that.
1492
01:33:38.969 --> 01:33:40.329
And on top of that,
1493
01:33:40.889 --> 01:33:43.949
we installed the Electrum Elektra's server.
1494
01:33:44.365 --> 01:33:48.545
So that actually makes it possible to then connect any,
1495
01:33:49.565 --> 01:33:50.065
wallet
1496
01:33:50.365 --> 01:33:51.905
to your own full node,
1497
01:33:52.449 --> 01:33:53.909
that supports the Electrum,
1498
01:33:54.449 --> 01:33:54.949
protocol,
1499
01:33:55.570 --> 01:33:57.750
be it harder wallets or,
1500
01:33:58.449 --> 01:34:00.550
any other third party wallet.
1501
01:34:01.835 --> 01:34:04.735
And very important for privacy reasons,
1502
01:34:05.355 --> 01:34:08.014
there's also the Bitcoin Explorer. Like, it's a
1503
01:34:08.715 --> 01:34:09.295
a minimal,
1504
01:34:09.830 --> 01:34:10.929
very lightweight,
1505
01:34:11.510 --> 01:34:13.290
Bitcoin blockchain explorer.
1506
01:34:13.750 --> 01:34:17.369
So you can actually look up everything, every block, every transaction
1507
01:34:17.830 --> 01:34:22.565
directly on your note. Because, otherwise, if you just go to any public,
1508
01:34:23.425 --> 01:34:27.205
blockchain explorer, of course, you're leaking a lot of private information
1509
01:34:27.660 --> 01:34:29.760
of what you're interested in. And
1510
01:34:30.620 --> 01:34:36.480
these third parties can then connect multiple addresses you with your IP address and all that stuff.
1511
01:34:38.045 --> 01:34:45.665
So this is this is where I come from. The Bitcoin part is really, really important for me. And once that is really set up,
1512
01:34:49.230 --> 01:34:49.969
the default,
1513
01:34:50.510 --> 01:34:51.010
lightning
1514
01:34:51.630 --> 01:34:53.650
client that is used is lnd,
1515
01:34:54.875 --> 01:34:57.455
which is pretty straightforward to set up.
1516
01:34:58.955 --> 01:35:03.135
And we also install right the lightning to actually make it manageable
1517
01:35:04.239 --> 01:35:06.900
through the browser. So you can manage your
1518
01:35:07.360 --> 01:35:09.620
lightning node, all the channels, everything.
1519
01:35:11.565 --> 01:35:16.625
And but this is just, like, the the core guide, the standard as it is now. There are many
1520
01:35:17.165 --> 01:35:17.665
bonus
1521
01:35:18.285 --> 01:35:18.765
guides.
1522
01:35:19.325 --> 01:35:20.785
There's are many
1523
01:35:21.100 --> 01:35:25.679
open poll requests actually for additional bonus guides for sea lightning,
1524
01:35:26.300 --> 01:35:27.920
for thunder hop,
1525
01:35:28.385 --> 01:35:30.245
for many other
1526
01:35:31.745 --> 01:35:32.245
applications
1527
01:35:33.025 --> 01:35:34.885
that we would like to include.
1528
01:35:35.840 --> 01:35:37.700
The goal is to have, like, one,
1529
01:35:38.560 --> 01:35:41.220
like, pretty minimal standard configuration,
1530
01:35:41.760 --> 01:35:47.765
but then you can put everything you want on top of that. So for example, join market or,
1531
01:35:49.905 --> 01:35:54.085
via guard VPN. We have an open pool request. Thunderhub, mempool,
1532
01:35:54.625 --> 01:35:55.010
bisque,
1533
01:35:56.289 --> 01:35:58.710
various management scripts, all that stuff.
1534
01:36:00.369 --> 01:36:01.110
And I think,
1535
01:36:02.130 --> 01:36:03.349
I mentioned that
1536
01:36:03.650 --> 01:36:06.455
it started as a, like, a personal project.
1537
01:36:07.155 --> 01:36:08.535
But I'm basically
1538
01:36:10.355 --> 01:36:12.909
I couldn't manage all the the contributions,
1539
01:36:13.210 --> 01:36:15.949
all the the issues anymore. And this is why
1540
01:36:16.489 --> 01:36:20.829
I now this is more this has transformed to a community project.
1541
01:36:21.285 --> 01:36:24.665
There are multiple maintainers now and many people
1542
01:36:25.045 --> 01:36:25.545
answering
1543
01:36:25.845 --> 01:36:27.385
all questions on GitHub.
1544
01:36:28.165 --> 01:36:28.665
And
1545
01:36:28.990 --> 01:36:29.570
I think
1546
01:36:30.590 --> 01:36:37.250
one thing is, telling that more people are actually interested in writing even more additional
1547
01:36:37.855 --> 01:36:38.835
bonus guides,
1548
01:36:39.215 --> 01:36:41.235
and we severely lack reviewers.
1549
01:36:42.015 --> 01:36:43.475
So if anyone here
1550
01:36:43.775 --> 01:36:45.075
is interested in
1551
01:36:45.790 --> 01:36:47.410
trying out some new stuff,
1552
01:36:47.790 --> 01:36:53.810
giving feedback on new bonus guides, that that'd be really a a great help.
1553
01:36:55.225 --> 01:37:01.645
Because in the end, if everybody's writing guides and I need to review review them all in the end,
1554
01:37:02.025 --> 01:37:03.725
that's not really going to scale.
1555
01:37:07.429 --> 01:37:11.449
1556
01:37:12.550 --> 01:37:13.050
Like,
1557
01:37:14.054 --> 01:37:14.554
really
1558
01:37:14.934 --> 01:37:16.235
I mean, there are some
1559
01:37:16.855 --> 01:37:17.355
names
1560
01:37:18.054 --> 01:37:20.074
we mentioned, like, definitely, like,
1561
01:37:22.140 --> 01:37:28.540
colleague under under the pseudonym of, like, Pillars of Indra. He's, like, coordinating lots of,
1562
01:37:29.205 --> 01:37:31.465
1563
01:37:31.845 --> 01:37:32.665
1564
01:37:33.845 --> 01:37:36.265
Weekly reviews on the r
1565
01:37:36.960 --> 01:37:38.559
slash recipe board on on,
1566
01:37:40.639 --> 01:37:41.860
Reddit, that is.
1567
01:37:42.239 --> 01:37:44.179
And there is this Telegram group
1568
01:37:45.945 --> 01:37:48.365
called the recipe board as well, which has
1569
01:37:49.065 --> 01:37:53.700
has picked up a lot of activity in the past couple of months, really. And I've been enjoying,
1570
01:37:54.080 --> 01:37:56.980
you know, lurking in there as well because, I mean, obviously,
1571
01:37:57.440 --> 01:38:01.300
there are a lot of solutions which, you know, I do learn from people who
1572
01:38:02.615 --> 01:38:03.675
trying to set up
1573
01:38:03.975 --> 01:38:05.595
their own note from the scratch.
1574
01:38:06.295 --> 01:38:06.955
And then,
1575
01:38:07.975 --> 01:38:10.875
you know, I do apply it myself as well.
1576
01:38:12.470 --> 01:38:19.655
So, yeah, it it it's worse to join these even if you are, you know, working with some other kind of system. Like, for example, verifying
1577
01:38:20.115 --> 01:38:22.215
the Bitcoin core signature or the other binaries,
1578
01:38:22.915 --> 01:38:23.975
PGP verification
1579
01:38:24.595 --> 01:38:28.370
is really something you can just come to when you are setting up
1580
01:38:28.850 --> 01:38:36.844
your Bitcoin node on your laptop and just wonder, oh, how how how how is how was that that I should verify this? And then you can go to the website,
1581
01:38:37.784 --> 01:38:38.684
and it's there.
1582
01:38:41.625 --> 01:38:44.320
That's, yeah, that's been a slight disconnected from the
1583
01:38:45.040 --> 01:38:49.380
comment from the community. I just wanted to note that, it's just so useful.
1584
01:38:50.480 --> 01:38:51.780
1585
01:38:52.885 --> 01:38:57.865
fun thing, for for a long time, I didn't even know there was a, a Raspberry Bolt subreddit
1586
01:38:59.125 --> 01:39:04.700
until they pinged me. So it it already had, like, over a 100 subscribers before I actually
1587
01:39:05.080 --> 01:39:07.260
got aware of it. That's awesome.
1588
01:39:10.945 --> 01:39:18.885
Gotta love when that just happens organically. Yeah. And I I cannot shout out enough to Indra and how he manages that stuff. He that's really awesome.
1589
01:39:22.769 --> 01:39:23.269
1590
01:39:24.449 --> 01:39:26.630
I mean, this has been a fantastic conversation.
1591
01:39:27.329 --> 01:39:29.655
We're about to hit an hour and 40 minutes.
1592
01:39:31.235 --> 01:39:34.455
Do you guys have anything else you wanna discuss before we wrap it up?
1593
01:39:36.790 --> 01:39:38.330
1594
01:39:39.190 --> 01:39:44.890
1595
01:39:48.785 --> 01:39:54.690
1596
01:39:55.250 --> 01:39:56.390
open almost and
1597
01:39:57.410 --> 01:40:02.390
make, a little bit of noise for the recipe bolt guide. It's like my
1598
01:40:02.715 --> 01:40:03.855
my brainchild
1599
01:40:04.235 --> 01:40:08.335
that's that has now grown wings and is
1600
01:40:08.875 --> 01:40:13.660
I'm actually also happy that it's no longer only on my shoulders. So that's that's really good.
1601
01:40:15.000 --> 01:40:16.380
And, yeah, I mean,
1602
01:40:17.080 --> 01:40:27.255
anybody who's interested in, actually learning how a node works, I think it's a good place to stop by, have a look, maybe join the Telegram group or the subreddit.
1603
01:40:28.195 --> 01:40:31.300
And if you want to go ahead and try some stuff,
1604
01:40:32.260 --> 01:40:33.880
it's it's it's actually fun.
1605
01:40:35.380 --> 01:40:37.559
Don't be afraid of the command line.
1606
01:40:37.940 --> 01:40:43.054
1607
01:40:44.155 --> 01:40:50.870
I mean, I appreciate you both. I appreciate your work. It sounded to me like Open Arms had something you wanted to talk about. You got something for us, Open Arms?
1608
01:40:52.690 --> 01:40:54.070
1609
01:40:54.530 --> 01:40:55.590
as things come
1610
01:40:57.010 --> 01:41:00.165
up. You know, these are my favorite topics, so definitely.
1611
01:41:02.785 --> 01:41:03.845
1612
01:41:05.910 --> 01:41:07.450
1613
01:41:09.510 --> 01:41:13.130
I guess let's just end it with some final thoughts. Final thoughts, open arms.
1614
01:41:13.430 --> 01:41:14.090
Hit us.
1615
01:41:17.405 --> 01:41:18.385
1616
01:41:18.845 --> 01:41:19.985
and use it.
1617
01:41:22.540 --> 01:41:25.199
1618
01:41:26.699 --> 01:41:28.080
Staticus, final thoughts.
1619
01:41:29.715 --> 01:41:34.135
1620
01:41:35.475 --> 01:41:36.535
be it for lightning
1621
01:41:36.915 --> 01:41:37.415
or
1622
01:41:38.300 --> 01:41:38.960
I think
1623
01:41:39.900 --> 01:41:41.120
all sometimes overlooked
1624
01:41:41.660 --> 01:41:46.640
even more importantly to verify your own, like, large transactions coming in,
1625
01:41:47.054 --> 01:41:48.675
typically going to hardware wallets.
1626
01:41:49.375 --> 01:41:50.755
So having your own
1627
01:41:51.375 --> 01:41:53.155
definite truth of
1628
01:41:53.775 --> 01:41:57.780
what's the state of the blockchain. And if you actually got
1629
01:41:58.160 --> 01:42:03.060
genuine Bitcoin, I think that's something every true Bitcoiner should be able to do.
1630
01:42:04.445 --> 01:42:05.345
1631
01:42:06.285 --> 01:42:16.100
Yes. To interact with the Bitcoin network, you're gonna need to use a Bitcoin node. If you're not using your own Bitcoin node, you're using someone else's Bitcoin node and you're trusting them with your privacy
1632
01:42:16.720 --> 01:42:24.065
and verification of your Bitcoin. Whether that is real Bitcoin, whether the rules that you think the network is following are actually being followed.
1633
01:42:24.845 --> 01:42:29.619
That is enforced by the node that you are using. So if you're using someone else's node,
1634
01:42:30.320 --> 01:42:32.580
you are trusting them with that responsibility.
1635
01:42:34.080 --> 01:42:36.500
With all that said, this was an absolutely fantastic
1636
01:42:36.935 --> 01:42:39.435
conversation. I wanna thank our guests once again.
1637
01:42:40.135 --> 01:42:43.195
I hope to have you both back on at some time soon.
1638
01:42:44.580 --> 01:42:47.480
Open Arms, I think you're number 1 most
1639
01:42:48.100 --> 01:42:51.400
you you've been on the show more than anyone else besides me.
1640
01:42:51.995 --> 01:42:56.335
So I really do appreciate you taking the time out to to come on every time,
1641
01:42:56.875 --> 01:42:59.740
and I look forward to whatever interesting topic,
1642
01:43:00.140 --> 01:43:02.240
our next conversation will be based on.
1643
01:43:02.700 --> 01:43:10.835
As always, I wanna thank the freaks for joining us, for this conversation. I hope you all enjoyed it. Your feedback is always appreciated. You can contact me,
1644
01:43:12.094 --> 01:43:12.335
via
1645
01:43:12.975 --> 01:43:14.995
all my contact information is at mattodel.com.
1646
01:43:16.239 --> 01:43:19.699
You can support the show and see previous episodes at silldispatch.com.
1647
01:43:20.480 --> 01:43:22.739
You can also support the show via merch,
1648
01:43:23.655 --> 01:43:24.395
at silodispatch.com/stack.
1649
01:43:26.775 --> 01:43:29.114
With all that said, I love you all.
1650
01:43:29.815 --> 01:43:31.195
Thank you, guys. Cheers.
1651
01:43:33.520 --> 01:43:36.980
1652
01:47:46.475 --> 01:47:49.855
1653
01:47:50.395 --> 01:47:54.574
I'll see you up for rabbit hole recap on Thursday at 2:30 EST, 19:30
1654
01:47:54.955 --> 01:47:55.455
UTC,
1655
01:47:56.400 --> 01:48:00.340
and we have another Citadel dispatch on Tuesday 18th
1656
01:48:01.120 --> 01:48:09.835
at 5 EST, 22 100 UTC. That's gonna be a really fun conversation on KYC and different trade offs with Zelco, Diverter, LaserHodl,
1657
01:48:10.295 --> 01:48:16.090
and Stefan Lovera, so make sure to tune in for that. I think it's gonna be a lot of fun and a good discussion.
1658
01:48:17.510 --> 01:48:19.449
As many of you know, I've been helping
1659
01:48:20.045 --> 01:48:20.785
Bitcoin Magazine,
1660
01:48:21.485 --> 01:48:24.145
put together their upcoming Bitcoin conference,
1661
01:48:25.085 --> 01:48:26.465
April 6th through 9th
1662
01:48:27.005 --> 01:48:27.825
in Miami.
1663
01:48:28.920 --> 01:48:32.300
Just a little heads up that prices do increase on Friday.
1664
01:48:33.160 --> 01:48:36.775
So if you haven't bought a ticket, you're considering doing it, you know, I am helping them
1665
01:48:37.094 --> 01:48:42.155
significantly with the programming for the open source stage. There's gonna be a lot of really good discussions there,
1666
01:48:43.815 --> 01:48:51.340
both on the 2 GA days, but also on industry day. Before the 2 GA days, we're going to be doing a very highly technical
1667
01:48:51.880 --> 01:48:53.020
focused discussions.
1668
01:48:53.639 --> 01:49:01.965
That's gonna be almost bit dev style. So if you haven't bought a ticket, you're considering buying a ticket, I was able to secure us, the code open source.
1669
01:49:02.665 --> 01:49:04.525
Do not share that code on Twitter.
1670
01:49:05.180 --> 01:49:07.120
I do not get a cut from that code.
1671
01:49:07.900 --> 01:49:12.480
It all goes to you. It's a full 21% off. So do not share it on Twitter. Otherwise,
1672
01:49:13.525 --> 01:49:16.344
they told me they will disable it. So cheers.
1673
01:49:16.645 --> 01:49:19.065
Love you all. Stay on with Stacks ads.
