Bitcoin.Review E6: A Review of Updates to Popular Bitcoin Projects with NVK, Bitstein, and Pierre Rochard
Software Releases and Project Updates
- 00:01:41 COLDCARD Mk4 5.0.7 - Sep 9, 2022 (bit.ly/3BClP0f)
00:05:56 Core Lightning v0.12.0 - Aug 24, 2022 (bit.ly/3S5lr1m) - 00:12:43 Blockclock 1.2.0 - Sep 15, 2022 (bit.ly/3BxSILG)
- 00:13:34 Spectre desktop v1.12.0 - Aug 26, 2022 (bit.ly/3qSWBWK)
- 00:16:28 Joinmarket v0.9.7 - Aug 28, 2022 (bit.ly/3qWoH3f)
- 00:17:50 NPM package for SeedXOR. (bit.ly/3C8BOFb)
- 00:25:56 RoboSats on Umbrel (bit.ly/3fcjDFa)
- 00:27:19 Ledger adding miniscript (bit.ly/3UmX4xX)
- 00:29:16 Trezor & Wasabi Join Forces To Make Bitcoin More Private (bit.ly/3BXXJOV)
- 00:30:03 Fulcrum added to bitcoinbinary (bit.ly/3DK4xBc)
- 00:37:51 btcd v0.23.1-beta, Aug 31 2022 (bit.ly/3Urjwpv)
- 00:38:04 Zeus v0.6.6, Aug 26 2022 (bit.ly/3f9vpjD)
- 00:39:24 Nunchuk implements bip21, Aug 31 2022 (bit.ly/3BZWG14)
- 00:39:57 BISQ v1.9.5, Aug 22 2022 (bit.ly/3LyPrR5)
- 00:41:01 Fountain Podcasts v0.4.8 (bit.ly/3f1ZTnH)
- 01:33:44 ATEC608A NRND (bit.ly/3xGWmBZ)
- 01:39:26 ETH merge (bit.ly/3SlgfWR)
- 01:51:21 Spiral - Private info retrieval block explorer (bit.ly/3BDto70)
- 01:56:03 US Treasury OFAC Releases Clarifications on Tornado Cash Sanctions (bit.ly/3S1PEyl)
- 01:57:05 BIP Proposal: Wallet Labels Export Format (bit.ly/3Sj5c17)
- 02:00:51 STARK - Zero knowledge bitcoin blockchain state prover (bit.ly/3C0oT8b)
- 02:03:09 Mullvad VPN hardware device (bit.ly/3f9LV3p)
Noteworthy
- 00:53:47 BIPBounty: Tax Deductible Bitcoin Bug Bounties (bit.ly/3LMxP4l)
- 00:59:34 Fedimint grant season (bit.ly/3S32zjP)
- 01:00:00 Tether Holds Firm on Decision Not To Freeze Tornado Cash Addresses (bit.ly/3UwFgAg)
- 01:01:04 New York Digital Investment Group Announces Lightning Accelerator Project “in Wolf’s Clothing” (bit.ly/3xHo1Ti)
- 01:01:49 Tadge Dryja joins Lightspark (https://bit.ly/3SoAZNG)
- 01:11:26 Shoutout, no bullshit bitcoin - (bit.ly/3DEqB05)
- 01:12:22 LN Explorer (bit.ly/3xIYF7k)
- 01:16:34 Ledger wallets now available at Best Buy (bit.ly/3BA10mr)
Bitcoin Optech Newsletter:
- 01:24:13 Bitcoin Core #23202 extends the psbtbumpfee RPC
- 01:25:08 Eclair #2387 adds support for fee bumping and signet
- 01:25:27 LDK #1652 updates support for onion messages w/ ability to send reply paths and decode them when received
- 01:25:36 HWI #627 adds support for P2TR keypath spends using the BitBox02 hardware signing device
- 01:33:22 BDK begins verifying both ECDSA and schnorr signatures immediately after the wallet creates them
02:18:00 Events:
- OsloPlebs
- Austin Bitcoin Design Club
- BitBlockBoom
- Baltic Honeybadger
- BTCAzores
- Bitcoin Amsterdam
- The Bitcoin Collective
- Atlanta Bitcoin Conf
- Adopting Bitcoin
- Unconfiscatable
- Africa Bitcoin Conf
01:41 - COLDCARD Mk4 5.0.7 Sep 9 2022 bit.ly3BClP0f
05:56 - Core Lightning v0.12.0 Aug 24 2022 bit.ly3S5lr1m
12:43 - Blockclock 1.2.0 Sep 15 2022 bit.ly3BxSILG
13:34 - Spectre desktop v1.12.0 Aug 26 2022 bit.ly3qSWBWK
16:28 - Joinmarket v0.9.7 Aug 28 2022 bit.ly3qWoH3f
17:50 - NPM package for SeedXOR. bit.ly3C8BOFb
25:56 - RoboSats on Umbrel bit.ly3fcjDFa
27:19 - Ledger adding miniscript bit.ly3UmX4xX
29:16 - Trezor amp Wasabi Join Forces To Make Bitcoin More Private bit.ly3BXXJOV
30:03 - Fulcrum added to bitcoinbinary bit.ly3DK4xBc
37:51 - btcd v0.23.1beta Aug 31 2022 bit.ly3Urjwpv
38:04 - Zeus v0.6.6 Aug 26 2022 bit.ly3f9vpjD
39:24 - Nunchuk implements bip21 Aug 31 2022 bit.ly3BZWG14
39:57 - BISQ v1.9.5 Aug 22 2022 bit.ly3LyPrR5
41:01 - Fountain Podcasts v0.4.8 bit.ly3f1ZTnH
53:47 - BIPBounty Tax Deductible Bitcoin Bug Bounties nbspbit.ly3LMxP4l
59:34 - Fedimint grant season bit.ly3S32zjP
01:00:00 - Tether Holds Firm on Decision Not To Freeze Tornado Cash Addressesnbspbit.ly3UwFgAg
01:01:04 - New York Digital Investment Group Announces Lightning Accelerator Project in Wolfs Clothing
01:01:49 - Tadge Dryja joins Lightspark httpsbit.ly3SoAZNG
01:11:26 - Shoutout no bullshit bitcoin bit.ly3DEqB05
01:12:22 - LN Explorer bit.ly3xIYF7k
01:16:34 - Ledger wallets now available at Best Buy bit.ly3BA10mr Bitcoin Optech Newsletter
01:24:13 - Bitcoin Core 23202 extends the psbtbumpfee RPC
01:25:08 - nbspEclair 2387 adds support for fee bumping and signet
01:25:27 - nbspLDK 1652 updates support for onion messages w ability to send reply paths and decode them
01:25:36 - HWI 627 adds support for P2TR keypath spends using the BitBox02 hardware signing device
01:33:22 - BDK begins verifying both ECDSA and schnorr signatures immediately after the wallet creates them
01:33:44 - ATEC608A NRND bit.ly3xGWmBZ
01:39:26 - ETH merge bit.ly3SlgfWR
01:51:21 - Spiral Private info retrieval block explorer bit.ly3BDto70
01:56:03 - US Treasury OFAC Releases Clarifications on Tornado Cash Sanctions bit.ly3S1PEyl
01:57:05 - BIP Proposal Wallet Labels Export Format bit.ly3Sj5c17
02:00:51 - STARK Zero knowledge bitcoin blockchain state prover bit.ly3C0oT8b
02:03:09 - Mullvad VPN hardware device bit.ly3f9LV3p Noteworthy
02:18:00 - Events OsloPlebs Austin Bitcoin Design Club BitBlockBoom Baltic Honeybadger BTCAzores
NOTE
Transcription provided by Podhome.fm
Created: 3/17/2024 4:22:52 PM
Duration: 8685.558
Channels: 1
1
00:00:07.965 --> 00:00:10.465
2
00:00:12.205 --> 00:00:17.119
The podcast where we fail at boringly reading the latest release notes and discuss project
3
00:00:17.580 --> 00:00:18.080
updates.
4
00:00:21.740 --> 00:00:27.125
So, this week we come back to the list. It's, I think episode 6
5
00:00:27.505 --> 00:00:33.525
and people seem to really have enjoyed the the wallet expert table on episode 5.
6
00:00:34.140 --> 00:00:37.120
But it's time for the list, and it's a beast of a list.
7
00:00:37.980 --> 00:00:43.775
I'm very, very happy to have more folks join. And today we have, Michael Gold
8
00:00:44.655 --> 00:00:46.115
Stein, known as Beatzstein,
9
00:00:46.975 --> 00:00:48.835
and we have Pierre Richard,
10
00:00:49.375 --> 00:00:51.235
known as Bitcoin is Savings,
11
00:00:51.970 --> 00:00:58.790
and we have, our returning guest, Matt O'Dell. It's, it's nice to have you guys. Thanks for having us on Rodolfo.
12
00:01:00.370 --> 00:01:01.510
13
00:01:02.594 --> 00:01:10.935
14
00:01:11.680 --> 00:01:12.340
Alright, guys.
15
00:01:12.720 --> 00:01:15.860
So Bedstein and Pierre are new to the show.
16
00:01:16.880 --> 00:01:19.540
So, essentially, what we do here is
17
00:01:19.985 --> 00:01:22.085
we go through the software list,
18
00:01:23.025 --> 00:01:24.705
and we also talk about
19
00:01:26.840 --> 00:01:29.100
you're gonna have to cut this off. It's so bad.
20
00:01:31.240 --> 00:01:31.740
Anyways,
21
00:01:32.440 --> 00:01:35.100
let's just stuff the list on the chat.
22
00:01:36.665 --> 00:01:40.605
This is so good. Anyways, we don't cut anything in this show. Alright.
23
00:01:41.305 --> 00:01:43.885
So I'm gonna start strong here.
24
00:01:44.400 --> 00:01:46.420
So cold card mark 4 5.0.7
25
00:01:48.240 --> 00:01:48.980
is coming,
26
00:01:49.760 --> 00:01:51.140
probably next week.
27
00:01:52.145 --> 00:01:55.844
Enhancements is in older versions, multisig and FC import,
28
00:01:56.704 --> 00:02:00.965
not offered in the micro SD when it was inserted. Now it's now it's there.
29
00:02:01.810 --> 00:02:03.990
There is a new this one was a huge
30
00:02:04.690 --> 00:02:07.270
thing for me. It was a new menu wrap around.
31
00:02:07.810 --> 00:02:14.335
So when you get to the bottom of any menu, it goes back to the top. So you don't have to go all the way back to the top.
32
00:02:15.035 --> 00:02:27.500
33
00:02:27.865 --> 00:02:31.545
34
00:02:32.025 --> 00:02:32.925
no. It's like,
35
00:02:33.225 --> 00:02:38.480
36
00:02:40.940 --> 00:02:43.915
37
00:02:44.694 --> 00:02:45.915
a straylight orbit.
38
00:02:46.454 --> 00:02:51.834
I don't know exactly what he's working on, but he's been contributing a lot of, HSM updates.
39
00:02:52.760 --> 00:02:55.180
So there is a new command to ignore
40
00:02:55.480 --> 00:02:57.180
HSM command over USB
41
00:02:57.560 --> 00:02:58.300
by default,
42
00:02:58.840 --> 00:03:00.300
that's a security improvement.
43
00:03:01.125 --> 00:03:03.705
Now you can do dynamic HSM white listing
44
00:03:04.325 --> 00:03:09.224
so so that you can pick the the outputs that you want to to attest
45
00:03:10.060 --> 00:03:10.780
And then,
46
00:03:11.100 --> 00:03:14.960
and he also added a attestation signature signature,
47
00:03:15.420 --> 00:03:15.920
PSPT,
48
00:03:16.700 --> 00:03:19.520
in a in a proprietary field, which is kinda cool.
49
00:03:20.284 --> 00:03:22.064
And then there is a few bug fixes,
50
00:03:22.685 --> 00:03:24.305
parsing a non fields in PSPT,
51
00:03:25.325 --> 00:03:27.504
share single address over NFC,
52
00:03:28.090 --> 00:03:30.829
and oh, this one was interesting. So
53
00:03:31.290 --> 00:03:32.510
if you had used
54
00:03:33.290 --> 00:03:34.750
all the trick pins,
55
00:03:35.315 --> 00:03:41.015
we actually re turn over one of the slots on the secure elements, you could actually get yourself locked out.
56
00:03:42.595 --> 00:03:43.895
So but that's fixed.
57
00:03:45.420 --> 00:04:03.590
58
00:04:04.210 --> 00:04:09.855
59
00:04:10.955 --> 00:04:27.175
of the time folks just forget their PIN. Right? And then they reach out to support, and this is before even this this feature. It's like, hey, you know, can you guys help me get into my cold card? I, you know, I can't log in. I'm like, what's kind of the whole point? If you if you don't know your PIN you can't get in.
60
00:04:27.955 --> 00:04:30.375
And then they could run through the 13
61
00:04:31.635 --> 00:04:33.895
fails and and then it's it's bad.
62
00:04:34.530 --> 00:04:41.430
So yeah. So so that's it. We we hope to release this one next week. There might be one more feature coming that's why it was not released.
63
00:04:42.475 --> 00:04:46.575
64
00:04:47.195 --> 00:05:04.544
65
00:05:05.164 --> 00:05:08.384
really I I I don't understand where this guy found the time
66
00:05:09.085 --> 00:05:12.280
to to add as many trick pins as he did,
67
00:05:12.580 --> 00:05:28.795
68
00:05:29.160 --> 00:05:31.660
69
00:05:32.440 --> 00:05:37.420
There's a lot of, you know, we always say that if you're gonna really test the the trick pins
70
00:05:38.485 --> 00:05:41.145
or the break me pin, you might need to have an extra one.
71
00:05:43.444 --> 00:05:46.270
Anyways, so so yeah. So that's that's fixed.
72
00:05:46.750 --> 00:05:49.970
Oh and it's a we have a software fix for older bootloaders
73
00:05:50.509 --> 00:05:54.050
and then there is a new bootloader coming into new production that fixes that
74
00:05:54.669 --> 00:05:55.409
deep inside.
75
00:05:56.884 --> 00:05:58.104
Alright. Corelightning.
76
00:06:00.324 --> 00:06:00.824
0.12.0.
77
00:06:02.405 --> 00:06:03.944
Web 8 in it.
78
00:06:04.310 --> 00:06:06.730
So I don't know too much about core lightning.
79
00:06:07.430 --> 00:06:09.290
It is in c which is
80
00:06:10.230 --> 00:06:11.210
a nice thing.
81
00:06:12.044 --> 00:06:16.225
But now they keep track of where your Satoshis are in real time
82
00:06:16.604 --> 00:06:19.345
on lightning as historically being a bit of a challenge.
83
00:06:20.580 --> 00:06:21.800
Rusty has been
84
00:06:22.500 --> 00:06:26.920
direct to node plugin has been rewritten in C, well that's always nice.
85
00:06:28.525 --> 00:06:30.865
Emergency recover, a long requested feature,
86
00:06:31.725 --> 00:06:35.425
originally pioneered by LNG team with some marketing text here and commits.
87
00:06:36.820 --> 00:06:38.600
Static channel backups.
88
00:06:39.540 --> 00:06:40.280
That's nice.
89
00:06:41.139 --> 00:06:43.400
Added 0Conf and 0
90
00:06:43.845 --> 00:06:47.705
serve, m one architecture support. Okay. Cool. So you can use it on new Macs.
91
00:06:48.245 --> 00:06:51.465
Do you guys have any comments about core lightning or
92
00:06:51.780 --> 00:06:53.320
anything related to that update?
93
00:06:59.140 --> 00:07:00.760
I guess, I guess not.
94
00:07:01.074 --> 00:07:05.895
95
00:07:06.914 --> 00:07:09.270
96
00:07:09.890 --> 00:07:10.390
lightning.com?
97
00:07:13.090 --> 00:07:16.950
98
00:07:17.330 --> 00:07:18.310
they have Windows.
99
00:07:19.475 --> 00:07:23.495
C lightning does not have Windows support. So that's that's the,
100
00:07:24.195 --> 00:07:26.855
you know, terrible reason why I've only ever used LND.
101
00:07:27.440 --> 00:07:29.220
102
00:07:29.920 --> 00:07:36.025
Yeah. Exactly. So he's he's stuck on Windows. I use the He uses Windows XP. The original 2009
103
00:07:36.325 --> 00:07:37.785
104
00:07:38.485 --> 00:07:39.545
along with LND.
105
00:07:40.405 --> 00:07:40.905
106
00:07:41.845 --> 00:07:48.639
I assume Pierre uses Windows because of his accounting background and all the accounting software of Macs are absolutely atrocious.
107
00:07:49.574 --> 00:07:52.074
108
00:07:52.615 --> 00:07:58.450
Microsoft Excel cannot have c sharp plug ins on Mac OS. So,
109
00:07:58.930 --> 00:08:01.510
somebody, you know, write a letter to Satya.
110
00:08:02.770 --> 00:08:05.090
111
00:08:05.965 --> 00:08:07.745
bookkeeping stuff with lightning
112
00:08:08.125 --> 00:08:09.264
as your, residency
113
00:08:09.805 --> 00:08:10.305
project.
114
00:08:10.764 --> 00:08:15.585
115
00:08:16.190 --> 00:08:18.210
that communicates with your LND node
116
00:08:18.590 --> 00:08:20.530
and populates your Excel spreadsheet
117
00:08:21.150 --> 00:08:23.010
with all of the LND data.
118
00:08:23.515 --> 00:08:27.615
And it also allows you to pay invoices from within Excel.
119
00:08:27.995 --> 00:08:38.710
And so that way for business users who, you know, they might have, like, a list of a 1,000 invoices they need to pay for whatever reason, they could just, you know, pay it from the comfort of their spreadsheet.
120
00:08:39.225 --> 00:08:41.485
121
00:08:42.585 --> 00:08:43.565
Excel security
122
00:08:44.425 --> 00:08:45.245
on the Windows
123
00:08:46.190 --> 00:08:47.330
talking to the node.
124
00:08:48.750 --> 00:08:50.370
125
00:08:53.070 --> 00:09:03.045
Yeah. Get chat meme. Yeah. I I also have an Excel plugin that connects to a cold card. Oh, shit. No. No. No. I'm kidding. No. Cold card says no.
126
00:09:03.420 --> 00:09:06.079
127
00:09:06.620 --> 00:09:07.440
128
00:09:10.274 --> 00:09:27.430
129
00:09:27.730 --> 00:09:33.675
don't do that. You know, be be more secure than that. Yes. Don't put your lights life savings on lightning, period.
130
00:09:34.055 --> 00:09:35.274
131
00:09:35.894 --> 00:09:36.714
Yeah. MetaMask
132
00:09:37.339 --> 00:09:43.040
133
00:09:43.660 --> 00:09:47.084
134
00:09:47.464 --> 00:09:50.285
135
00:09:50.745 --> 00:09:51.485
136
00:09:52.320 --> 00:09:53.839
137
00:09:54.480 --> 00:09:56.740
Pierre ended up in proprietary software.
138
00:10:00.595 --> 00:10:07.975
139
00:10:08.450 --> 00:10:11.430
140
00:10:12.529 --> 00:10:13.510
141
00:10:15.785 --> 00:10:19.165
142
00:10:19.705 --> 00:10:20.025
but,
143
00:10:20.745 --> 00:10:26.420
144
00:10:26.800 --> 00:10:28.340
that actually added Bitcoin,
145
00:10:30.080 --> 00:10:35.345
capabilities to their system by, like, 5, 7 years ago. It was way back then,
146
00:10:36.204 --> 00:10:40.225
just so you could because, you know, Bitcoin, if you're gonna have like
147
00:10:41.779 --> 00:10:42.279
decimals,
148
00:10:43.620 --> 00:10:48.440
it's a lot of decimals. Right? And none of this accounting software could handle it.
149
00:10:48.820 --> 00:10:49.800
150
00:10:50.215 --> 00:10:50.955
That's right.
151
00:10:51.495 --> 00:10:55.515
152
00:10:55.895 --> 00:11:00.120
I think you should just do binary. It can do ones and zeros right on the screen and problem resolved.
153
00:11:00.839 --> 00:11:05.420
154
00:11:06.200 --> 00:11:07.020
to Bitcoin?
155
00:11:08.045 --> 00:11:09.745
156
00:11:10.445 --> 00:11:22.170
back in the day, most software was not, like, very virtualized from the actual sort of logic of the programs and, like, modern sort of stacks for software and languages,
157
00:11:23.510 --> 00:11:24.010
abstract,
158
00:11:24.904 --> 00:11:25.404
enough
159
00:11:26.024 --> 00:11:29.564
of the actual stuff you're trying to do from
160
00:11:30.425 --> 00:11:31.884
how the software is made,
161
00:11:32.360 --> 00:11:35.660
you know, so you can protect your integers and all that stuff.
162
00:11:36.040 --> 00:11:46.045
Yeah. No. I I think I think I think, engineering for software is is greatly improved in that sense, But also became shit because everything should be embedded. But that's a whole different story.
163
00:11:46.585 --> 00:11:53.440
164
00:11:54.700 --> 00:11:56.399
Yep. Help all these dinosaurs,
165
00:11:57.740 --> 00:11:58.240
upgrade.
166
00:11:58.705 --> 00:12:03.125
167
00:12:03.425 --> 00:12:08.350
accounting software. And it's funny because at Quaintite, we also have our custom accounting,
168
00:12:09.130 --> 00:12:15.390
software for the store that then plugs into the, you know, it has to interface with QuickBooks that accountants like to use.
169
00:12:15.945 --> 00:12:23.805
But, yeah, like once you have your own, like, accounting needs, especially with Bitcoin, you kinda like you don't want to use the old way of doing accounting.
170
00:12:24.185 --> 00:12:30.910
You really want to sort of like have your Bitcoin accounting and then you sort of transfer everything into USD denominated
171
00:12:31.290 --> 00:12:33.390
because that's really what the government cares about.
172
00:12:34.445 --> 00:12:34.945
Anyways.
173
00:12:36.205 --> 00:12:37.105
Yep. So,
174
00:12:37.965 --> 00:12:42.145
making accounting cool again. That's Bitcoin for you. Bitcoin fixes everything.
175
00:12:43.500 --> 00:12:45.920
Alright. Next, Block Clock 1.2.0
176
00:12:47.900 --> 00:12:50.320
was released yesterday. It's a small release.
177
00:12:51.015 --> 00:12:52.155
Now the micro,
178
00:12:52.695 --> 00:12:58.395
it's the same binary for both which is kinda cool. So we now support the Block Lock Micro,
179
00:13:00.180 --> 00:13:00.680
and,
180
00:13:01.300 --> 00:13:04.040
and, there is a new version for the mini.
181
00:13:04.980 --> 00:13:07.880
182
00:13:08.345 --> 00:13:11.485
183
00:13:14.105 --> 00:13:16.925
So yeah. And, you you don't need to update,
184
00:13:17.400 --> 00:13:20.300
your Block Lock Mini. This update is kind of optional,
185
00:13:20.600 --> 00:13:23.580
not much for it. It just wanted to consolidate to a single
186
00:13:23.960 --> 00:13:26.540
binary so there is less stuff to be reviewed.
187
00:13:27.565 --> 00:13:30.465
188
00:13:31.805 --> 00:13:35.905
189
00:13:36.660 --> 00:13:37.480
version 1.2.1.12.0.
190
00:13:42.019 --> 00:13:43.079
They added faucet
191
00:13:43.380 --> 00:13:43.880
xfun,
192
00:13:44.740 --> 00:13:45.240
extension.
193
00:13:45.865 --> 00:13:46.605
Oh, that's
194
00:13:47.145 --> 00:13:51.725
Stefan. And, DevTools adding full Python access via JavaScript for developers.
195
00:13:52.265 --> 00:13:55.700
So I guess you can automate things now. That just sounds
196
00:13:56.080 --> 00:13:58.100
horrifying. Yes. It it does. I got chills.
197
00:13:58.959 --> 00:14:00.820
Python through JavaScript. Yay.
198
00:14:03.115 --> 00:14:04.655
199
00:14:06.315 --> 00:14:07.775
200
00:14:09.915 --> 00:14:10.415
Amazing.
201
00:14:11.330 --> 00:14:13.589
Do you guys remember that elect,
202
00:14:13.890 --> 00:14:17.990
the the the Chrome of 0 day vulnerability that happened recently?
203
00:14:18.975 --> 00:14:27.555
A lot of I don't know about Spectre, but a lot of this this, the UI on this multi platform systems is essentially Chrome
204
00:14:28.430 --> 00:14:29.410
wrapped, right?
205
00:14:29.790 --> 00:14:42.204
So technically all this software, if they're using whatever, if it is Chrome and that version could have been vulnerable to this. They call it Electron, right? Yes. So money poof and it's gone.
206
00:14:42.745 --> 00:14:45.699
207
00:14:46.399 --> 00:15:04.510
to make an cross platform without using Electron. Is that how it's pronounced? I don't know. Q t, cute. I I've never I've only ever read it. So I don't know how it's pronounced. This is the first time I heard that. I'll call it cute going forward. I kinda dig it. So, yeah, I don't QT is great. The problem with QT is that
208
00:15:05.370 --> 00:15:06.510
209
00:15:07.380 --> 00:15:07.745
because
210
00:15:08.305 --> 00:15:11.365
the way they're trying to leverage the system for UI,
211
00:15:11.985 --> 00:15:12.705
they have this,
212
00:15:13.265 --> 00:15:16.885
relative spacing for things. It's like a relative unit for UI.
213
00:15:17.889 --> 00:15:19.750
It's very, very hard
214
00:15:20.290 --> 00:15:23.750
215
00:15:24.449 --> 00:15:38.380
my thing was, like, I just gotta keep it as simple as possible because if I add anything, it's just gonna be a total mess to deal with. That's right. Have you guys used Kivy? I always wanted to find we we've been trying to find a Kivy person. Kivy is essentially
216
00:15:39.000 --> 00:15:41.180
217
00:15:42.295 --> 00:15:43.755
wrapper. It was really nice.
218
00:15:44.295 --> 00:15:53.620
And like unit Unity, you sort of like just it's like, you know, like a a pixel world. Right? So you actually draw the stuff which means a lot more work too.
219
00:15:54.240 --> 00:15:56.705
220
00:15:57.825 --> 00:16:01.685
221
00:16:02.865 --> 00:16:10.279
222
00:16:11.060 --> 00:16:14.600
223
00:16:15.060 --> 00:16:15.880
Please upgrade.
224
00:16:17.855 --> 00:16:21.235
Spector is great. It really is. And it's the first one
225
00:16:21.695 --> 00:16:22.755
they did a proper
226
00:16:23.470 --> 00:16:25.010
wrapper for Bitcoin Core,
227
00:16:25.390 --> 00:16:27.810
on the same desktop, which is really nice.
228
00:16:28.510 --> 00:16:29.970
Alright. Join market.
229
00:16:30.565 --> 00:16:34.105
The one and only true coinjoin implementation.
230
00:16:34.805 --> 00:16:40.790
Actually, I've heard that no other coinjoin implementations actually exist. So it's version 0.9.7.
231
00:16:42.530 --> 00:16:43.510
So they improved,
232
00:16:44.210 --> 00:16:47.665
so the Tumblr algorithm fix and cycling, this is an audible,
233
00:16:48.204 --> 00:16:48.704
networking
234
00:16:49.245 --> 00:16:54.865
no, reworking of the Tumblr algorithm mostly motivated by finding an error which was causing failure
235
00:16:55.380 --> 00:16:57.080
for people that tried
236
00:16:57.780 --> 00:17:02.680
to use more than default numbers mixed up. Anyways, long explanation here.
237
00:17:03.705 --> 00:17:05.005
Disallowing UTXOs
238
00:17:05.545 --> 00:17:06.925
with confirmed spans,
239
00:17:08.185 --> 00:17:09.565
new script to calculate
240
00:17:09.945 --> 00:17:13.005
Fidelity Bond Values. Fidelity Bonds are really cool.
241
00:17:13.690 --> 00:17:15.390
New display of available balances.
242
00:17:16.970 --> 00:17:18.670
RPC API updates.
243
00:17:19.050 --> 00:17:22.430
They added a schedule status and session endpoint.
244
00:17:23.515 --> 00:17:24.335
Tor updates.
245
00:17:24.955 --> 00:17:29.775
QT changes now allow access to the XPub information in the QT interface.
246
00:17:31.200 --> 00:17:31.700
Installation,
247
00:17:32.080 --> 00:17:33.700
the installation now will automatically
248
00:17:35.760 --> 00:17:40.385
check release GPG signatures for libsodium. Oh, that's nice and Tor.
249
00:17:41.105 --> 00:17:42.165
So that's cool.
250
00:17:43.505 --> 00:17:47.045
Everybody should try join markets if they want to coin joint
251
00:17:48.145 --> 00:17:48.885
over Tor.
252
00:17:50.940 --> 00:17:51.919
NPN package,
253
00:17:53.260 --> 00:17:59.040
TypeScript for seedxor. Oh yeah. So somebody did created an implementation for seedxor
254
00:18:00.255 --> 00:18:01.475
in, TypeScript.
255
00:18:02.335 --> 00:18:02.835
So,
256
00:18:03.615 --> 00:18:07.315
that means you could probably now very easily integrate CDXR
257
00:18:07.775 --> 00:18:08.435
on your,
258
00:18:09.390 --> 00:18:10.370
like, React JS
259
00:18:11.390 --> 00:18:14.049
app or any sort of JavaScript based,
260
00:18:14.350 --> 00:18:16.210
wallet. Do you guys use SeedXor?
261
00:18:17.035 --> 00:18:19.455
262
00:18:20.075 --> 00:18:22.255
263
00:18:23.115 --> 00:18:24.895
tools available to Bitcoiners.
264
00:18:25.400 --> 00:18:29.740
So much easier than multisig. You get a lot of benefits that are similar.
265
00:18:30.440 --> 00:18:32.285
266
00:18:32.845 --> 00:18:34.945
if you're not ready for multisig yet,
267
00:18:35.645 --> 00:18:38.385
you know, this greatly greatly derisks
268
00:18:38.765 --> 00:18:40.065
your single sig
269
00:18:40.960 --> 00:18:41.779
seed backup.
270
00:18:43.519 --> 00:18:55.034
And this kind of encryption can it it it's nearly impossible to sort of like have a backdoor because you're just like soaring 2 values together. And you can recover without a computer, with paper.
271
00:18:55.640 --> 00:18:58.860
272
00:19:00.440 --> 00:19:02.540
like, the the original seed still
273
00:19:02.914 --> 00:19:07.335
as a backdrop somewhere. I mean So there is there is still that that issue.
274
00:19:07.794 --> 00:19:08.695
275
00:19:09.075 --> 00:19:16.720
So I like to say that when I'm, like, suggesting to people in, say, a podcast or whatever just because I don't know where they are at with knowledge.
276
00:19:17.420 --> 00:19:31.429
But in this pod, it's a little different. I mean, most of the people who who get through this list normally already know some of this stuff. Right. So, you know, if you have high availability, say for example, you already have a few micro SD backups and, you know, so you have
277
00:19:32.049 --> 00:19:37.495
some means of of recovery in case you lose a part, I I think you're you're more safe,
278
00:19:37.955 --> 00:19:44.775
279
00:19:45.460 --> 00:19:55.925
saying, you know, use a ledger or a treasure or something for ease. I say, just get a cold card. And then when I onboard them onto the cold card, I tell them to keep a micro SD backup and then 2 pieces of steel,
280
00:19:56.465 --> 00:19:58.485
one of each part of the seed XOR.
281
00:19:58.785 --> 00:20:03.684
Yep. And then you just put them in 2 different places. And then for 99% of people, I feel like
282
00:20:04.340 --> 00:20:13.535
283
00:20:14.575 --> 00:20:15.555
you're pretty safe,
284
00:20:16.095 --> 00:20:22.435
especially if you have 2 of those. And then if you have a house fire, you go find your 2 metal backups. Right? Like it's it's
285
00:20:23.330 --> 00:20:32.665
the the problem with the seed, especially if they don't have a passphrase is that, you know, somebody's gonna end up seeing that at some point even accidentally. Right? Or
286
00:20:33.125 --> 00:20:35.385
like a wife finds the seed
287
00:20:35.685 --> 00:20:41.480
the seed plate on the floor somewhere in the house, takes a picture and sends a text message. Honey, is this yours?
288
00:20:43.720 --> 00:20:45.179
And then poof, money gone.
289
00:20:47.080 --> 00:20:50.540
And, yeah. We we're gonna we're we're working on
290
00:20:50.885 --> 00:20:54.585
trying to add, 12, 12 word support as well for CDXR.
291
00:20:56.005 --> 00:20:57.785
Like, unfortunately, a lot of
292
00:20:58.500 --> 00:21:00.840
newcomers and whatever, they don't feel as
293
00:21:01.300 --> 00:21:03.240
as willing to work through 24
294
00:21:03.700 --> 00:21:06.440
holes, like, to punch 24 times 4.
295
00:21:06.804 --> 00:21:08.505
It's a lot of punching in that also,
296
00:21:09.365 --> 00:21:11.625
people have asked. We were trying to make it happen.
297
00:21:12.005 --> 00:21:13.945
298
00:21:14.630 --> 00:21:16.730
like, a meditative practice. Yes.
299
00:21:17.990 --> 00:21:19.049
300
00:21:19.909 --> 00:21:24.044
If you don't have some of these in your desk, you know, you're not a real Bitcoiner.
301
00:21:24.905 --> 00:21:27.245
302
00:21:29.470 --> 00:21:33.250
you know, the, the raspberry pie debates that people are having about nodes.
303
00:21:33.630 --> 00:21:39.015
It's like, for me, I just don't want it because I, I, I have not seen a beautiful raspberry pie setup.
304
00:21:39.415 --> 00:21:43.835
So even if it works, it's just like, you know, my node is something that is important
305
00:21:44.135 --> 00:21:47.435
and I think it should be treated with that sort of like sacredness.
306
00:21:48.659 --> 00:21:49.480
307
00:21:50.179 --> 00:21:51.720
raspberry pies are a shit coin.
308
00:21:52.179 --> 00:21:53.720
Hey. Imagine paying $200
309
00:21:54.100 --> 00:21:54.840
for that
310
00:21:55.460 --> 00:21:58.865
piece of crap that is completely closed source from Broadcon.
311
00:21:59.645 --> 00:22:04.125
312
00:22:05.520 --> 00:22:09.540
some firmware you can throw on it. I feel like I saw a headline for that the other day.
313
00:22:11.040 --> 00:22:14.420
314
00:22:14.785 --> 00:22:15.525
a way
315
00:22:15.905 --> 00:22:16.405
around,
316
00:22:16.945 --> 00:22:19.045
their crap. Like, that that's like a
317
00:22:19.585 --> 00:22:25.419
a a true true, like, bad actor in the hardware space, man. Those guys are are just brutal.
318
00:22:25.960 --> 00:22:28.139
319
00:22:29.000 --> 00:22:29.820
I think you've
320
00:22:30.600 --> 00:22:35.735
kind of been against it. But there is that method of creating a 2 of 3 seed XOR.
321
00:22:36.035 --> 00:22:43.760
Yes. And, I went through the process of doing it just to cause I wanted to see that magic. Because it it uses some weird set theory,
322
00:22:44.380 --> 00:22:49.945
to be able to construct this thing, and it worked. And it was really kinda magical thing to
323
00:22:50.405 --> 00:22:52.745
to work through it. You know, it took some time, but
324
00:22:53.045 --> 00:22:56.240
the idea that you could do that 2 of 3 by hand,
325
00:22:57.180 --> 00:23:01.520
was was very, very cool. And it really just shows the power of
326
00:23:01.820 --> 00:23:04.160
even these very, very basic
327
00:23:04.475 --> 00:23:05.294
crypto primitives.
328
00:23:05.595 --> 00:23:17.110
In fact, it's the most basic crypt crypto primitives that do the best job because it's literally just XOR, which is what, you know, like, a one time pad has always been, which is, you know, the perfect security,
329
00:23:18.210 --> 00:23:31.174
330
00:23:32.200 --> 00:23:33.340
completely interceptible
331
00:23:33.720 --> 00:23:40.620
comms. Right? They used to have vinyl with the full key, and they would pay play the vinyl on both sides,
332
00:23:41.225 --> 00:23:45.645
you know, like, to get the the messaging and encrypted across. It's it's just pretty cool.
333
00:23:46.025 --> 00:23:52.890
334
00:23:53.590 --> 00:23:59.850
335
00:24:03.415 --> 00:24:05.355
So yeah. So that's that's really cool.
336
00:24:06.135 --> 00:24:08.235
You know, I doubt that we're gonna support that
337
00:24:08.700 --> 00:24:11.040
that multi multi sig, that, multipart,
338
00:24:11.660 --> 00:24:17.440
CDXor just because it's the complexity increase and everything else. Just use multi sig if you get into that level.
339
00:24:17.764 --> 00:24:20.184
340
00:24:20.485 --> 00:24:31.280
341
00:24:31.900 --> 00:24:34.925
342
00:24:35.545 --> 00:24:36.825
and standardizing it? Or
343
00:24:37.785 --> 00:24:39.405
344
00:24:41.530 --> 00:24:47.870
It should exist somewhere, like, you know, properly annotated and stuff. I like to see more wallets, like, supported natively.
345
00:24:48.330 --> 00:24:49.070
346
00:24:49.450 --> 00:24:49.950
347
00:24:50.465 --> 00:24:52.965
Yeah. I mean, I I am a I'm a true,
348
00:24:53.585 --> 00:24:54.885
Shamir secret hater.
349
00:24:55.665 --> 00:24:58.165
I think, I think it's, too much complexity
350
00:24:58.539 --> 00:25:02.559
to when you get to that complexity and it's all custom solutions, you should just use multisig.
351
00:25:03.500 --> 00:25:09.945
352
00:25:10.645 --> 00:25:11.545
you can choose
353
00:25:12.085 --> 00:25:14.665
12 words, 18 words, 24 words.
354
00:25:15.620 --> 00:25:18.440
Are those are all are those all different wallets?
355
00:25:19.460 --> 00:25:19.960
356
00:25:20.740 --> 00:25:27.184
357
00:25:27.804 --> 00:25:29.505
358
00:25:30.125 --> 00:25:34.465
359
00:25:34.950 --> 00:25:37.850
No. Different wallet. Okay. That's what I thought.
360
00:25:38.309 --> 00:25:41.770
361
00:25:42.134 --> 00:25:45.514
And then for each index, you can have one of each type of export.
362
00:25:45.815 --> 00:25:48.075
Gotcha. And they will be all different secrets.
363
00:25:49.095 --> 00:25:51.514
Anyways, for anyone, interested in Seedexor,
364
00:25:52.040 --> 00:25:52.940
check out CDXR.com.
365
00:25:54.440 --> 00:25:55.980
There is a domain for it.
366
00:25:56.920 --> 00:25:57.420
Okay.
367
00:25:57.720 --> 00:25:58.220
Robosats,
368
00:25:59.080 --> 00:26:01.340
now available as an app on Embro.
369
00:26:02.054 --> 00:26:09.115
Does anyone here use, Robosats? It's a pretty cool project. I I am not super familiar with it, but I keep on hearing interesting things about it.
370
00:26:09.894 --> 00:26:15.100
371
00:26:16.440 --> 00:26:19.100
372
00:26:19.495 --> 00:26:21.115
373
00:26:21.655 --> 00:26:23.595
Gift cards for sats over lightning.
374
00:26:24.375 --> 00:26:26.235
375
00:26:26.950 --> 00:26:33.850
376
00:26:34.505 --> 00:26:36.765
377
00:26:37.304 --> 00:26:44.270
378
00:26:45.210 --> 00:26:50.890
No. I use it in Amazon. People like the Amazon gift cards. I don't know. It's because then they can sell to somebody else,
379
00:26:51.335 --> 00:26:53.435
380
00:26:54.615 --> 00:26:56.235
Probably more than the US dollar.
381
00:26:57.655 --> 00:27:01.850
382
00:27:02.230 --> 00:27:04.810
383
00:27:05.270 --> 00:27:09.530
384
00:27:09.894 --> 00:27:18.809
on the exchange rate per dollar unit on the card. Well, if you keep keep holding the gift card, you're gonna lose that money too. But there is that too. I mean,
385
00:27:19.990 --> 00:27:24.250
Ledger adding Mini Script soon, so that's cool. It's nice to see Ledger
386
00:27:25.085 --> 00:27:26.705
because I've been bantering them,
387
00:27:27.085 --> 00:27:40.610
privately for for years. First about the node thing and then about supporting PSPT, which they added both. And now, the mini the mini script stuff is is kinda cool that they're getting there. We don't support that yet. We do support output descriptors
388
00:27:41.070 --> 00:27:41.890
on codecard,
389
00:27:42.544 --> 00:27:48.485
but we don't support mini scripts yet just because there's no market demand yet, and it's a lot of work. So
390
00:27:48.945 --> 00:27:50.565
but it's just nice to see
391
00:27:51.040 --> 00:27:52.340
players of that size
392
00:27:53.120 --> 00:27:56.260
sort of really pushing Bitcoin stuff instead of the Shecoin stuff.
393
00:27:57.040 --> 00:27:59.380
394
00:27:59.975 --> 00:28:05.035
I don't know. Because I assume that that would also have to be added for you guys to to handle. Right?
395
00:28:05.655 --> 00:28:09.195
No. No. No. Are you guys could you guys use just the Rust version?
396
00:28:10.020 --> 00:28:11.240
397
00:28:11.940 --> 00:28:14.600
we would just write because it's just output descriptors.
398
00:28:17.115 --> 00:28:22.815
Right? It's just a more complex version of it because output descriptors were not complete.
399
00:28:24.955 --> 00:28:26.300
So, so yeah.
400
00:28:27.020 --> 00:28:33.680
So one cool thing because I was trying to to think right, because, you know, hardware wallets don't are not wallets. Right? They're just signing devices.
401
00:28:34.220 --> 00:28:34.720
So
402
00:28:35.655 --> 00:28:36.955
they don't really use
403
00:28:37.575 --> 00:28:46.320
the descriptors themselves. Right? They're just exporting it. So I was trying to think why would you add mini scripts to because you can just do the output descriptor version of that.
404
00:28:46.940 --> 00:28:47.680
But then
405
00:28:48.540 --> 00:28:51.440
one cool thing is that you could then then the Hadoop
406
00:28:51.924 --> 00:28:52.825
can be aware
407
00:28:53.125 --> 00:28:53.625
of
408
00:28:54.005 --> 00:28:57.465
the of the addresses, right, to double check that you own the addresses
409
00:28:59.550 --> 00:28:59.950
before,
410
00:29:00.350 --> 00:29:03.170
before you you let us sign. So it goes,
411
00:29:03.870 --> 00:29:06.290
don't sign it. You don't own this change address,
412
00:29:08.274 --> 00:29:11.575
which is, that's one attack vector there.
413
00:29:13.394 --> 00:29:14.855
414
00:29:15.235 --> 00:29:15.735
415
00:29:16.500 --> 00:29:20.040
Trezor and Wasabi joined forces to make Bitcoin more private.
416
00:29:20.660 --> 00:29:27.554
I'm a little biased on this one, but, I have I have I have opinions. Why why don't we, do you guys have opinions about,
417
00:29:28.415 --> 00:29:30.755
WhatsApp integration inside Ledger Suite?
418
00:29:31.215 --> 00:29:37.220
419
00:29:37.780 --> 00:29:39.480
wrestle some Jimmy's somewhere.
420
00:29:40.815 --> 00:29:41.795
421
00:29:42.335 --> 00:29:46.115
I I think I mean, aside from the coin joint implementation war,
422
00:29:46.575 --> 00:29:49.795
the I I I'm not sure how I feel about a a
423
00:29:50.480 --> 00:29:53.140
a nonphysically secure device over USB,
424
00:29:55.360 --> 00:29:57.380
doing this live on the Internet.
425
00:29:57.760 --> 00:29:58.900
Somehow it just
426
00:29:59.375 --> 00:30:00.995
it just makes me feel iffy.
427
00:30:01.695 --> 00:30:02.995
But it's cool to see.
428
00:30:03.535 --> 00:30:04.035
429
00:30:05.294 --> 00:30:08.434
Yeah. I noticed, we we skipped a thing about fulcrum,
430
00:30:09.440 --> 00:30:14.580
being added to Bitcoin binary. And if I remember correctly, it's not there's there's not a proof yet,
431
00:30:15.600 --> 00:30:16.659
but it's on there.
432
00:30:17.014 --> 00:30:17.514
And,
433
00:30:17.975 --> 00:30:22.315
I I've I've recently given Fulcom a try, and, I was impressed.
434
00:30:22.855 --> 00:30:25.930
My my problems with it are merely that, like,
435
00:30:26.490 --> 00:30:30.270
the the devs, I guess, they're a little more agnostic to,
436
00:30:31.050 --> 00:30:32.270
particular coins.
437
00:30:32.650 --> 00:30:33.710
438
00:30:34.255 --> 00:30:42.595
Yeah. The big blockers make the best Electrum implementations because they need to handle more data. Yeah. They have a lot more data to handle, so they thank you.
439
00:30:42.940 --> 00:30:48.000
440
00:30:48.300 --> 00:30:50.480
everyone else was, more performant.
441
00:30:51.020 --> 00:30:51.840
442
00:30:52.554 --> 00:30:54.575
443
00:30:54.875 --> 00:31:00.470
the best the most efficient Electrum implementation was Electromax, which was also big blockers. That's right.
444
00:31:01.190 --> 00:31:01.690
445
00:31:02.150 --> 00:31:05.530
And, on Bitcoin binary, I almost forgot. So
446
00:31:06.710 --> 00:31:09.929
for people that don't know, bitcoin binary dot org
447
00:31:10.575 --> 00:31:12.674
is a place where you can submit,
448
00:31:13.615 --> 00:31:15.315
your own proof of
449
00:31:15.775 --> 00:31:17.395
reproducible build for projects,
450
00:31:18.190 --> 00:31:23.250
but we also built a a bot there that builds on video and then tweets the video
451
00:31:24.269 --> 00:31:27.865
of building that that project and Fulcrum does build.
452
00:31:28.325 --> 00:31:31.625
I mean, I haven't reviewed their project myself, but the
453
00:31:32.485 --> 00:31:40.760
the the build does build and checks. So that's kinda cool. So, if anyone has any projects that are reproducibly built,
454
00:31:41.220 --> 00:31:43.915
we we take pull requests and we would
455
00:31:44.315 --> 00:31:46.255
be more than happy to list it
456
00:31:46.875 --> 00:31:48.735
and, and build for everybody.
457
00:31:49.835 --> 00:31:55.050
458
00:31:56.150 --> 00:31:57.130
hit that mark?
459
00:31:57.590 --> 00:32:04.134
Because, like, if I just made a video, it's like, I could just I could write a script that goes through the whole build thing and then prints out the
460
00:32:04.755 --> 00:32:06.855
shawesome that people are looking for.
461
00:32:07.235 --> 00:32:13.230
So so this is this is the beauty of of, reproducible builds. Right? It's about a web of trust.
462
00:32:13.769 --> 00:32:14.269
463
00:32:15.304 --> 00:32:17.085
people are trusting that we
464
00:32:17.705 --> 00:32:18.924
are running the
465
00:32:19.225 --> 00:32:22.284
the the GitHub code that we have there on the GitHub actions
466
00:32:22.825 --> 00:32:23.485
to build
467
00:32:23.899 --> 00:32:34.525
fulcrum in the way that we claim to build. Right? Can you take that at face value? Probably not. But we are doing this if somebody submits their own and hosts their own video on YouTube,
468
00:32:34.825 --> 00:32:36.045
right now it's 2,
469
00:32:36.585 --> 00:32:40.125
now you have Fulcrum making their claim on their website, that's 3,
470
00:32:40.560 --> 00:32:43.060
Right? And maybe you double check. I mean,
471
00:32:43.520 --> 00:32:45.460
you know, like the efforts to
472
00:32:46.240 --> 00:32:46.980
to coerce
473
00:32:47.655 --> 00:32:48.635
all these people,
474
00:32:49.655 --> 00:32:51.435
you know, because of one extension,
475
00:32:52.135 --> 00:32:55.195
it's kinda funny, right, but it becomes kinda pointless. So
476
00:32:55.730 --> 00:32:57.509
that's the idea. It's just about raising
477
00:32:58.210 --> 00:33:02.389
that cost of attack so high that it becomes just silly for you to try to,
478
00:33:02.775 --> 00:33:05.355
you know, break into GitHub, change our,
479
00:33:06.054 --> 00:33:08.395
our code without us seeing it on GitHub,
480
00:33:08.934 --> 00:33:11.595
right, and and running it and, you know,
481
00:33:12.679 --> 00:33:17.960
so so yeah. It's just if more people do it, you just gain that web of trust,
482
00:33:18.360 --> 00:33:19.500
exponential safety.
483
00:33:20.575 --> 00:33:34.450
484
00:33:34.910 --> 00:33:39.225
think for some reason that I have, something valuable to add. And so
485
00:33:39.605 --> 00:33:42.985
they would they would say, oh, okay. Well, he is getting the same,
486
00:33:44.245 --> 00:33:46.664
shot value as me, and I kinda like that guy.
487
00:33:47.280 --> 00:33:54.820
And these other people that I like too that I I think they are good at handling Bitcoin software. They're coming to the same shots too.
488
00:33:55.385 --> 00:33:58.925
They would all have to be colluding or diluting each other,
489
00:33:59.945 --> 00:34:07.790
to have come to the same SHOS value unless that was the real one. That's correct. And it's very similar to to PGP's
490
00:34:08.090 --> 00:34:10.350
491
00:34:10.970 --> 00:34:11.950
in person ideally.
492
00:34:12.454 --> 00:34:17.434
So so this is very similar, right, like you're essentially making GitHub commit, right, which is a point in history
493
00:34:18.055 --> 00:34:21.035
that it's stuck in a Merkle tree in a blockchain
494
00:34:23.050 --> 00:34:27.630
and, you're essentially claiming that he did what he did. Right? So there is a reputation
495
00:34:28.994 --> 00:34:29.734
component to
496
00:34:30.035 --> 00:34:31.974
it, and then there is essentially
497
00:34:32.275 --> 00:34:37.815
a a proof set. Right? So with more proofs in a set that that sort of claim the same thing.
498
00:34:38.200 --> 00:34:42.460
499
00:34:42.760 --> 00:34:43.260
hardcore.
500
00:34:43.960 --> 00:34:48.595
I think that does bring up, like, a a kind of broader thing about cryptography is like,
501
00:34:49.135 --> 00:34:52.275
in in a lot of cryptography, it's not that the
502
00:34:52.735 --> 00:34:55.235
the math is in and of itself
503
00:34:56.529 --> 00:34:57.029
meaningful.
504
00:34:57.650 --> 00:34:59.589
It's it's being able to create,
505
00:35:01.410 --> 00:35:04.230
pieces of data that are socially useful.
506
00:35:05.585 --> 00:35:06.885
507
00:35:07.185 --> 00:35:07.685
Right?
508
00:35:08.465 --> 00:35:09.845
And provable interdependence.
509
00:35:10.305 --> 00:35:10.805
It's
510
00:35:11.425 --> 00:35:15.790
it's it's it's amazing how, like, a very simple non dramatic
511
00:35:16.650 --> 00:35:21.390
version of software testing. Right? So essentially, like, we we don't do the negative.
512
00:35:21.744 --> 00:35:30.565
Right? I don't wanna get into sort of spats of projects and stuff. If they build, then great. Then we list. If they don't build, then they're not listed. Right?
513
00:35:31.549 --> 00:35:32.369
So like
514
00:35:33.309 --> 00:35:44.545
essentially you just take your inference from saying, hey, this project's built, therefore I'm gonna use these. We don't have to like get into drama or shit on other projects or anything. It's just,
515
00:35:44.845 --> 00:35:46.625
you know, you build or don't build.
516
00:35:47.400 --> 00:35:52.460
I I like this this mold a lot better because there is other sites out there that sort of review,
517
00:35:53.079 --> 00:35:55.819
bitcoin projects and then they end up in this griefed
518
00:35:56.315 --> 00:36:00.495
sort of like problem where they don't have necessarily the budget
519
00:36:02.155 --> 00:36:03.935
to do things but then they essentially
520
00:36:04.920 --> 00:36:11.340
grieved projects saying hey, if you don't give me money I'm not gonna change, I'm not gonna spend the time to change
521
00:36:11.765 --> 00:36:14.745
the fact that I was not able to build. It creates this terrible,
522
00:36:15.525 --> 00:36:16.905
terrible incentive set
523
00:36:17.285 --> 00:36:19.065
for for the project. It's
524
00:36:19.369 --> 00:36:27.310
it's horrific. And I wanted to solve that problem because it was pissing me off that just incompetent people couldn't build my projects where everybody else could.
525
00:36:27.745 --> 00:36:32.885
And I figure a lot of people felt the same way. So, hey, let's expand that pie and do that.
526
00:36:33.185 --> 00:36:34.965
I I'm calling this open security,
527
00:36:35.640 --> 00:36:36.140
and
528
00:36:36.599 --> 00:36:40.619
we have another project coming that's essentially a watchtower for,
529
00:36:41.160 --> 00:36:42.299
PGP signatures.
530
00:36:43.559 --> 00:36:44.539
Sorry, like
531
00:36:45.495 --> 00:36:46.395
signed binaries
532
00:36:46.695 --> 00:36:54.075
on Bitcoin projects. So we're gonna we're still sort of it's a side project so it keeps on being bumped, but we kinda got halfway there
533
00:36:54.440 --> 00:36:56.300
where, we're gonna be watching
534
00:36:57.000 --> 00:37:01.020
all the Bitcoin binaries, like Bitcoin project binaries on their sites,
535
00:37:01.825 --> 00:37:06.725
right, to see if it changes. And if it changes, does it if it matches
536
00:37:07.185 --> 00:37:09.445
the signature of the of the
537
00:37:11.460 --> 00:37:12.359
of the maintainer.
538
00:37:13.700 --> 00:37:15.400
And if it doesn't, we go like,
539
00:37:15.859 --> 00:37:19.960
you know, like computer. It's like, it doesn't match. Don't download. Don't download.
540
00:37:20.485 --> 00:37:22.345
Or go check or whatever. Right?
541
00:37:22.645 --> 00:37:25.145
I think these very tiny little things are so helpful.
542
00:37:26.565 --> 00:37:28.585
543
00:37:29.300 --> 00:37:30.980
There's always a side project. It's,
544
00:37:31.540 --> 00:37:32.840
I don't know. It's impressive.
545
00:37:33.300 --> 00:37:38.520
Yeah. I I I love it. You're you're building, like, a whole, you know, Bitcoin security empire.
546
00:37:40.285 --> 00:37:43.825
Bitcoins. That's funny. Yeah. Full stack, like,
547
00:37:44.445 --> 00:37:45.185
it's fantastic.
548
00:37:46.250 --> 00:37:49.070
549
00:37:49.450 --> 00:37:51.390
550
00:37:51.930 --> 00:37:54.270
551
00:37:54.890 --> 00:37:55.390
has
552
00:37:56.075 --> 00:37:57.295
one, entry
553
00:37:57.835 --> 00:38:00.494
for a commit, so I am not reading it.
554
00:38:01.515 --> 00:38:03.775
They have a new version. It stays at that.
555
00:38:04.930 --> 00:38:06.150
Okay. Zeus.
556
00:38:06.690 --> 00:38:08.310
Zeus version 0.6.6.
557
00:38:11.010 --> 00:38:13.030
New feature, reproducible builds.
558
00:38:13.685 --> 00:38:14.185
Yay.
559
00:38:14.485 --> 00:38:19.145
Guess where it's gonna end up? On bitcoin binary dot org. Do you guys use Zeus?
560
00:38:20.565 --> 00:38:21.465
561
00:38:22.130 --> 00:38:23.590
562
00:38:24.530 --> 00:38:26.630
563
00:38:27.330 --> 00:38:27.910
up here?
564
00:38:28.370 --> 00:38:29.350
565
00:38:29.835 --> 00:38:34.174
566
00:38:34.555 --> 00:38:35.934
as, like, a spending wallet?
567
00:38:36.234 --> 00:38:37.615
568
00:38:38.609 --> 00:38:39.670
It it just works.
569
00:38:40.369 --> 00:38:44.630
570
00:38:44.930 --> 00:38:47.815
571
00:38:48.275 --> 00:38:49.895
lightning bandwagon too.
572
00:38:50.355 --> 00:39:11.510
573
00:39:12.450 --> 00:39:20.115
and I use it primarily to like, when I'm drinking with Bitcorners to show them how cool it is that the sats just constantly coming into the node.
574
00:39:20.815 --> 00:39:22.915
But the UI is fantastic now.
575
00:39:24.655 --> 00:39:25.155
576
00:39:26.090 --> 00:39:30.990
let me just find here for Nunchuk. I have a small update here, but that's not a release.
577
00:39:33.370 --> 00:39:35.310
So they implemented BIP 21.
578
00:39:37.035 --> 00:39:39.135
Let me see if I can find their releases.
579
00:39:45.380 --> 00:39:47.720
I can't remember where they are. Well, anyways,
580
00:39:48.180 --> 00:39:51.560
so they implemented BIP 31 21. I think there is no
581
00:39:52.180 --> 00:39:56.705
recent software release yet, so wait for the next show to hear more about Nunchuk.
582
00:39:57.965 --> 00:39:59.185
Bisc version
583
00:39:59.485 --> 00:39:59.985
1.9.5.
584
00:40:01.760 --> 00:40:06.420
The server release introduced a new p two p status indicator as Bitcoin Core
585
00:40:06.880 --> 00:40:08.180
version 23 compatibility
586
00:40:09.405 --> 00:40:11.905
and makes bug fixes and minor improvements.
587
00:40:14.125 --> 00:40:18.305
So is Bisq still big? I haven't looked into Bisq in a while.
588
00:40:20.990 --> 00:40:32.204
589
00:40:32.505 --> 00:40:34.045
But I I feel like it's
590
00:40:34.480 --> 00:40:36.420
very rarely someone's first choice.
591
00:40:37.200 --> 00:40:38.660
592
00:40:39.119 --> 00:40:39.619
exchanges
593
00:40:40.000 --> 00:40:42.580
are are kinda like very high friction. Right?
594
00:40:43.125 --> 00:40:50.825
595
00:40:51.960 --> 00:40:53.660
for convenience and better UX,
596
00:40:54.359 --> 00:40:59.580
people are gonna choose that first. But if they get shut down, then Bisq still exists.
597
00:41:00.440 --> 00:41:00.940
598
00:41:01.785 --> 00:41:03.645
Fountain podcast version
599
00:41:04.905 --> 00:41:05.405
0.4.8.
600
00:41:07.945 --> 00:41:09.405
Hot and fountain discover
601
00:41:09.865 --> 00:41:10.365
discoverability,
602
00:41:11.250 --> 00:41:11.990
more discoverability,
603
00:41:13.090 --> 00:41:16.470
faster boosts, faster time stamping, time stamp clips,
604
00:41:17.170 --> 00:41:18.550
and ticked away your referrals.
605
00:41:19.404 --> 00:41:23.984
Yeah. So fountain just, like, the the app was a bit sort of chugging
606
00:41:24.365 --> 00:41:28.545
a bit. It was clunky. Yeah. It's yeah. It seems to be getting better.
607
00:41:29.530 --> 00:41:32.430
608
00:41:33.130 --> 00:41:37.310
it it's it seems so obvious, but it it is a big change because,
609
00:41:37.645 --> 00:41:45.185
you know, usually with, like, Apple Podcasts, like, you have the top charts. Right? And the podcasters are obsessed with the top charts, and it's just a completely
610
00:41:45.920 --> 00:41:49.620
closed system. No one really knows how the top charts work.
611
00:41:50.880 --> 00:41:56.345
The top charts that Fountain implemented is straight up how many sats has that episode received,
612
00:41:57.765 --> 00:42:01.224
which can still be gained like a podcast. You can send sats themselves,
613
00:42:02.005 --> 00:42:04.265
with sock puppet accounts or whatever, but
614
00:42:04.840 --> 00:42:10.860
it it seems like a a massive step up improvement in terms of, like, okay. Here's actual value that's determining
615
00:42:11.240 --> 00:42:16.615
616
00:42:16.995 --> 00:42:18.535
the episodes of this show.
617
00:42:18.995 --> 00:42:19.450
I actually I
618
00:42:28.445 --> 00:42:32.065
I just I just don't I I fail to see how podcast 2.0,
619
00:42:33.805 --> 00:42:35.665
takes over. I I'm a fan of ads.
620
00:42:36.039 --> 00:42:38.779
Put the ads in. I hate them. I skip them.
621
00:42:39.079 --> 00:42:45.259
Everybody wins. You know? It's like a lump sum for the producer, and and I don't think we're gonna go away from ads anytime soon.
622
00:42:45.655 --> 00:42:46.155
But,
623
00:42:46.855 --> 00:42:47.175
but,
624
00:42:47.655 --> 00:43:00.470
the fun though of knowing that there's people who like your show and sort of, like, wants to, like, sort of send you some sats to let you know that you liked it It's really cool. It's like getting a gift. Right? It's like somebody sends you a bottle of whiskey or something when you do something nice for them.
625
00:43:00.770 --> 00:43:01.590
That I love.
626
00:43:02.055 --> 00:43:16.300
627
00:43:16.920 --> 00:43:21.180
I mean, the issues are that their business model is is their ad partners.
628
00:43:21.674 --> 00:43:29.135
Right? So if you're starting a new podcast, the fact that you have the ability to get direct funding from your audience with with minimal
629
00:43:29.674 --> 00:43:30.174
middlemen
630
00:43:31.700 --> 00:43:38.359
is a massive step improvement, and it's just, like, no very few people use lightning right now. Right? So it's it's gonna take some time.
631
00:43:39.035 --> 00:43:43.455
But I could see a world in 5 years, 6 years where some new person comes out with a podcast
632
00:43:43.915 --> 00:43:46.015
from some random place in the world.
633
00:43:46.400 --> 00:43:52.900
Maybe they have a low cost of living and they're able to just immediately start receiving funds directly from their audience. That's empowering.
634
00:43:53.675 --> 00:43:57.695
635
00:43:58.474 --> 00:44:03.830
you know, they can have a podcast that from from a place where they have capital controls
636
00:44:04.290 --> 00:44:04.790
and
637
00:44:05.170 --> 00:44:06.070
and do well.
638
00:44:06.930 --> 00:44:10.470
639
00:44:12.275 --> 00:44:12.775
micropayments
640
00:44:13.075 --> 00:44:18.755
models. I I know someone was on Marty's podcast arguing that, you know, maybe Nick Zaba was wrong about,
641
00:44:19.474 --> 00:44:21.060
mental accounting costs
642
00:44:22.260 --> 00:44:23.320
with, micropayments.
643
00:44:23.940 --> 00:44:25.720
But then the sort of solutions
644
00:44:26.580 --> 00:44:27.560
that were being,
645
00:44:28.180 --> 00:44:39.224
put forward, how it like, it gets overcome, We're really just kind of validating Nexavo by saying that people would move towards a subscription model where you say, okay. Well, I'm I will give up to this amount,
646
00:44:39.850 --> 00:44:49.245
and let the computer just send according to that. And it's like, you might as well just pay the, you know, I don't even know what Netflix cost per month now, but they have their monthly cost.
647
00:44:49.885 --> 00:44:54.145
648
00:44:54.445 --> 00:44:55.185
with Bitcoin
649
00:44:55.805 --> 00:44:57.825
because Bitcoin is push not pull.
650
00:44:58.500 --> 00:45:03.480
And if there is one thing we know about customers is that unless you take it without their permission every month,
651
00:45:03.780 --> 00:45:05.480
they're not gonna give it to you.
652
00:45:06.105 --> 00:45:09.725
653
00:45:10.025 --> 00:45:10.845
to continually
654
00:45:11.625 --> 00:45:14.105
give them value as opposed to I mean, I
655
00:45:14.985 --> 00:45:15.485
because
656
00:45:15.900 --> 00:45:18.319
how how many people yeah. I mean, there's there's also, like,
657
00:45:18.619 --> 00:45:19.599
gym gyms
658
00:45:19.900 --> 00:45:30.145
are notorious for basically doing this. They get you they get you hooked, and then you never go to the gym again after January is up. And you still you still pay, which is why you should always use a disposable,
659
00:45:31.005 --> 00:45:33.585
card for things like that just in for anything
660
00:45:34.000 --> 00:45:36.900
something like that you should stick with. But, like, anything that
661
00:45:37.440 --> 00:45:39.839
you don't know for sure if you're gonna stick with,
662
00:45:40.240 --> 00:45:43.780
because these people can also then be crooks with it where it's like,
663
00:45:44.465 --> 00:45:48.245
you know, even after you say, I no longer want to be a part of this gym,
664
00:45:48.945 --> 00:46:08.875
there's a big problem with, companies like that still pulling money. So on the other hand, if you have a subscription model, but you have to actually say, yes, I want to give this person $5 this month. Like, you know, imagine imagine an app where it's your monthly bills and it lists all the stuff and it has some stats about it's like Approve. Approve. Approve. Approve. Approve.
665
00:46:09.627 --> 00:46:10.580
To 20
666
00:46:11.040 --> 00:46:11.540
hours
667
00:46:11.840 --> 00:46:12.080
of,
668
00:46:12.720 --> 00:46:13.620
Bitcoin review,
669
00:46:14.720 --> 00:46:16.100
which is only 1 episode,
670
00:46:16.400 --> 00:46:27.945
but you listen to 20 hours. Are you willing to give $5 again? And you just go down the list of the different stuff that you subscribe to, and it kinda gives you those stats and you say yes or no. I would imagine that
671
00:46:28.390 --> 00:46:29.510
you'd get way more,
672
00:46:29.990 --> 00:46:33.850
value out of the the content. And I would it would send a good,
673
00:46:34.870 --> 00:46:36.410
you know, signals to creators
674
00:46:36.835 --> 00:46:39.575
to continually improve and and all of that.
675
00:46:40.835 --> 00:46:49.950
So I think we're we're the sort of podcast this is me. I have no experience. I have not set sets. I have not received sets for, like, for for podcasts or anything.
676
00:46:51.690 --> 00:46:52.190
What
677
00:46:52.730 --> 00:46:53.790
what I think
678
00:46:54.505 --> 00:46:56.125
is valuable about it
679
00:46:56.425 --> 00:47:03.645
probably in my own head is it's a good sort of onboarding mechanism. It's like, hey. I'm gonna check out this podcast.
680
00:47:04.630 --> 00:47:10.970
I'll give it, you know, however, you know, 2¢ per per minute. I don't know what the going rate is.
681
00:47:11.674 --> 00:47:14.974
But I'll I'll give it a little bit of money just to to be nice.
682
00:47:15.515 --> 00:47:24.770
And I wanna check it out. And then once you've done that, you can see, okay. How much did I actually value this thing? Okay. I'm gonna start giving it this amount per month. So it's like a way to, like,
683
00:47:25.150 --> 00:47:27.490
onboard you onto a subscription model.
684
00:47:28.045 --> 00:47:34.065
685
00:47:34.685 --> 00:47:35.665
686
00:47:35.965 --> 00:47:36.465
Yeah.
687
00:47:36.970 --> 00:47:42.510
Podcast apps too. In instead of all this, you know, podcast apps could do a better job of
688
00:47:42.810 --> 00:47:45.335
figuring out ad blocking. Like, use
689
00:47:45.875 --> 00:47:48.935
AI to figure out where the ad is so that you can,
690
00:47:49.395 --> 00:47:52.135
I I've seen this in a few podcasts
691
00:47:52.670 --> 00:47:56.450
in I guess, I use Overcast? I think it's a fantastic app.
692
00:47:58.590 --> 00:48:04.835
And I've seen some podcasts have chapters and it actually cut off where the ad is. And you could just,
693
00:48:05.295 --> 00:48:10.755
it would automatically skip to where the ad is over. So I could imagine you could build AI
694
00:48:11.220 --> 00:48:13.480
that somehow, you know, recognizes this,
695
00:48:14.580 --> 00:48:17.080
and and disabled to to skip over.
696
00:48:17.460 --> 00:48:21.185
697
00:48:22.445 --> 00:48:23.985
essentially as a sponsor,
698
00:48:25.645 --> 00:48:26.865
I give a budget,
699
00:48:27.220 --> 00:48:27.720
say,
700
00:48:28.260 --> 00:48:31.320
to Apple Podcasts. Right? And then Apple Podcasts
701
00:48:32.020 --> 00:48:32.520
finds
702
00:48:32.820 --> 00:48:35.800
the best audiences for my ad dollars,
703
00:48:36.265 --> 00:48:42.845
right, and somehow, I don't know, gets the creators I don't know. Well, so Fountain has something like that where
704
00:48:44.030 --> 00:48:50.450
705
00:48:51.070 --> 00:48:58.935
706
00:48:59.810 --> 00:49:16.405
You know, go out there and try different stuff. And some things will stick, some won't, and maybe you tweak it and maybe find a nice market fit for something new. The other thing that, like, Bittstein kind of triggered in my head is is that so, like, my favorite podcast app is antennapod, completely false.
707
00:49:16.830 --> 00:49:19.170
708
00:49:19.470 --> 00:49:21.810
donate their time to open source work.
709
00:49:23.070 --> 00:49:25.944
If they're trying to integrate podcasting 2.0,
710
00:49:26.325 --> 00:49:32.424
if they integrate podcasting 2.0, they actually get a cut of all the stream sets Right. On their app. So all of a sudden,
711
00:49:32.930 --> 00:49:33.750
there's a business model
712
00:49:34.130 --> 00:49:37.990
for podcast app creators that isn't, you know, harvest user data
713
00:49:38.850 --> 00:49:40.310
and and surveil them.
714
00:49:41.015 --> 00:49:44.075
715
00:49:44.535 --> 00:49:45.035
is
716
00:49:45.575 --> 00:49:52.780
they have ads for a free version, or you can pay them $10 a year to not have the ads. That's what I love about Spotify.
717
00:49:53.800 --> 00:50:01.205
Yeah. And, I mean, you always have to just trust what people are saying on the back end because you you can't see what people are running on the back end. But,
718
00:50:01.825 --> 00:50:05.765
I I assume given the guy I I forget his name, but the guy that makes it, he,
719
00:50:06.225 --> 00:50:07.185
he's the guy that made,
720
00:50:08.100 --> 00:50:11.800
was it Instapaper? Like, the original what Instapaper is? Right.
721
00:50:12.180 --> 00:50:15.220
So he he he cares about, you know, kind of,
722
00:50:16.180 --> 00:50:17.320
privacy stuff.
723
00:50:18.164 --> 00:50:19.224
And for that,
724
00:50:20.005 --> 00:50:22.345
somewhere in the the terms, it said how,
725
00:50:22.805 --> 00:50:33.970
there's only very specific data that goes to the advertisers, which is how many people saw this and how many people clicked on it. Stuff like that. Where none of it is, like, actually using your information.
726
00:50:35.345 --> 00:50:39.525
And, it's just it's a very slick app. So, I mean, if if they implemented,
727
00:50:40.385 --> 00:50:45.480
lightning 2.0 in it, I'd probably, you know, just give it a shot just to to have fun with it.
728
00:50:46.040 --> 00:50:50.220
But I'm also just excited to see, like like you guys are saying, that people are trying this.
729
00:50:50.920 --> 00:50:51.820
And I think
730
00:50:52.215 --> 00:51:01.115
Adam Curry is right about just the power of RSS. I think RSS has been greatly underrated, and there's a reason Google killed it.
731
00:51:01.530 --> 00:51:10.510
And they got rid of, Google Reader and pushed all of, like, the the amp and all that stuff. It's a it's a very powerful medium. And I think it does create
732
00:51:11.375 --> 00:51:13.715
just you you could have a whole market for indexers,
733
00:51:14.415 --> 00:51:18.835
and RSS could be, you know, used for all sorts of different applications
734
00:51:19.220 --> 00:51:23.640
which we already see. I I subscribe to a lot of YouTube channels, not through YouTube because,
735
00:51:24.260 --> 00:51:32.365
I don't wanna be, like, logged into YouTube all the time. But I could there's a way to do it through RSS so I can get all the YouTube videos I want. Adam's indexer gets paid
736
00:51:32.745 --> 00:51:39.470
737
00:51:39.850 --> 00:51:41.390
738
00:51:42.035 --> 00:51:46.775
where people essentially mix match from other feeds, so they recurate
739
00:51:47.235 --> 00:51:48.615
episodes of podcasts.
740
00:51:48.995 --> 00:51:50.855
Mhmm. And then that resyndication,
741
00:51:52.180 --> 00:51:55.400
there is some, like, revenue split there or something.
742
00:51:55.700 --> 00:51:57.240
Because I would pay,
743
00:51:57.940 --> 00:52:04.325
like, a buck to have a feed of, like, multiple podcast episodes on a specific topic.
744
00:52:05.345 --> 00:52:15.420
Like, because there is, like, the wealth of knowledge out there in podcast is insane. Right? But I, you know, I don't necessarily wanna subscribe to a specific pod and and so I'd love to have, like, resyndication
745
00:52:16.280 --> 00:52:17.020
per topic.
746
00:52:17.405 --> 00:52:20.945
And it could be sort of automated too, all kinds of stuff people can do,
747
00:52:21.245 --> 00:52:27.570
especially with machine learning and just sort of trying to to get the topics and stuff and and just charge a buck and and and pay the podcasters
748
00:52:27.950 --> 00:52:29.090
for that syndication,
749
00:52:29.390 --> 00:52:30.130
the resyndication.
750
00:52:31.070 --> 00:52:32.770
I think that would be really cool.
751
00:52:33.765 --> 00:52:38.265
752
00:52:38.645 --> 00:52:43.520
or Patreon or some of these other paywalls. And it's like, they'll do something like,
753
00:52:44.319 --> 00:52:46.980
get get they'll do, like, half an episode free.
754
00:52:47.839 --> 00:52:55.805
And then if you want the whole thing, you know, go go subscribe. It's It's like, I don't wanna pay the whole, you know, monthly thing for this one episode I wanna hear.
755
00:52:56.185 --> 00:52:59.964
I haven't yet been sold on, you know, being being a pay pig for,
756
00:53:00.660 --> 00:53:02.520
your your whole operation here.
757
00:53:03.059 --> 00:53:07.319
So it would also be nice, you know, if more of these places just had a way to, like,
758
00:53:07.725 --> 00:53:09.505
pay for 1 episode or,
759
00:53:10.205 --> 00:53:15.425
have lightning 2 point o in a sense of, you know, hey, I wanna listen up to this amount
760
00:53:15.760 --> 00:53:17.220
to see where it is. Maybe
761
00:53:17.520 --> 00:53:20.819
maybe, I want 30 minutes more of this episode.
762
00:53:21.440 --> 00:53:25.835
It's all kinds of stuff that people could come up with and just the the fact that people are working on this,
763
00:53:26.935 --> 00:53:30.315
they'll find they'll find what works. And I think it's
764
00:53:30.660 --> 00:53:33.300
it's very bullish for just kind of the future of,
765
00:53:33.780 --> 00:53:35.880
766
00:53:36.340 --> 00:53:41.685
767
00:53:41.985 --> 00:53:42.485
768
00:53:42.785 --> 00:53:43.685
Alright, guys.
769
00:53:44.385 --> 00:53:44.885
So,
770
00:53:45.185 --> 00:53:47.445
the list of software is done.
771
00:53:47.890 --> 00:53:52.070
Now we're going to the 2nd part of the show. The noteworthy list,
772
00:53:52.850 --> 00:53:56.950
is essentially, like, projects and updates and other things that
773
00:53:58.365 --> 00:53:59.105
are interested
774
00:53:59.724 --> 00:54:00.545
for people
775
00:54:00.845 --> 00:54:04.670
who care about Bitcoin to know about but are not necessarily software updates.
776
00:54:05.710 --> 00:54:10.770
So there is this BIP bounty, tax deductible bug bounties for Bitcoin.
777
00:54:11.309 --> 00:54:13.730
I am a fan of anything tax deductible,
778
00:54:14.535 --> 00:54:15.035
especially,
779
00:54:15.494 --> 00:54:19.115
as a business because then he makes spending money on things that
780
00:54:19.415 --> 00:54:22.315
that matter be a way for the state to get less,
781
00:54:22.730 --> 00:54:24.490
782
00:54:25.050 --> 00:54:30.350
sorry. The accounts gotta step in here. What I I I I never understand this of
783
00:54:32.045 --> 00:54:33.025
Bitcoin companies
784
00:54:34.285 --> 00:54:35.984
needing to have
785
00:54:36.365 --> 00:54:38.385
Bitcoin expenses be tax deductible.
786
00:54:38.685 --> 00:54:40.305
They're already tax deductible.
787
00:54:40.809 --> 00:54:46.190
You they're they're part they're business expense. Business expenses are tax deductible. I don't understand
788
00:54:46.970 --> 00:54:47.470
why
789
00:54:47.825 --> 00:54:48.885
you need to have
790
00:54:49.425 --> 00:54:50.965
okay. This is a 100%
791
00:54:51.345 --> 00:54:54.005
tax deductible as a tech as a business expense,
792
00:54:54.385 --> 00:54:55.525
but I also
793
00:54:55.960 --> 00:54:57.579
would like this other category
794
00:54:58.039 --> 00:55:00.619
where it would also be a 100% tax deductible.
795
00:55:01.240 --> 00:55:05.745
It's the same outcome. You don't pay taxes. Like, I don't So the problem is,
796
00:55:06.225 --> 00:55:07.365
797
00:55:08.145 --> 00:55:08.885
like ours,
798
00:55:10.305 --> 00:55:11.365
you know, some,
799
00:55:11.825 --> 00:55:14.885
like a lot of types of business expenses are not
800
00:55:15.190 --> 00:55:20.170
expensable. Like What? Yeah. So so there are things that you can't like, for example,
801
00:55:21.589 --> 00:55:22.810
you know, like a donation,
802
00:55:23.349 --> 00:55:24.810
it's not a business expense
803
00:55:26.105 --> 00:55:26.605
Unless
804
00:55:27.065 --> 00:55:44.204
Why are you calling it a donation then? Just don't call it a donation. Call it a consulting fee. Well, see, this is the problem. Right? A lot of the times the people receiving the donations are not understanding that the way the world works. So they will make sure that the invoice says donation, Well, now you can't exactly.
805
00:55:44.505 --> 00:55:45.005
So
806
00:55:45.305 --> 00:55:50.444
so it's that's why it's important. It's important because people don't know how to do taxes.
807
00:55:50.890 --> 00:55:53.070
Right? They don't know how to journal things.
808
00:55:53.530 --> 00:55:54.030
So
809
00:55:54.730 --> 00:55:55.230
having
810
00:55:55.530 --> 00:55:59.150
this premade mechanisms that are already packaged correctly
811
00:55:59.735 --> 00:56:07.275
812
00:56:07.970 --> 00:56:15.484
813
00:56:15.945 --> 00:56:18.765
deductible Oh, okay. As a business expense.
814
00:56:19.224 --> 00:56:20.045
Same here.
815
00:56:20.425 --> 00:56:24.125
816
00:56:25.210 --> 00:56:36.735
817
00:56:37.195 --> 00:56:38.575
and deducting it a 100%.
818
00:56:38.955 --> 00:56:42.175
819
00:56:43.000 --> 00:56:44.619
820
00:56:45.160 --> 00:56:53.825
Or if you had people who could just, like, you know, set up an LLC and be like, hey, pay me this fee, and it's not a donation. So it's tax deductible.
821
00:56:57.245 --> 00:57:03.569
822
00:57:06.190 --> 00:57:09.410
823
00:57:10.405 --> 00:57:15.305
this is germ it's good to see. This is Jeremy Rubin's project. It seems like he's primarily
824
00:57:15.685 --> 00:57:18.345
he spun this up, for his Op CTV
825
00:57:18.724 --> 00:57:19.224
bounties.
826
00:57:19.760 --> 00:57:26.819
827
00:57:27.195 --> 00:57:29.615
to do OPC TV without changing Bitcoin.
828
00:57:30.315 --> 00:57:32.175
That that that is bullish.
829
00:57:32.875 --> 00:57:35.055
It's it's like we should not change
830
00:57:35.710 --> 00:57:37.569
Bitcoin for anyone's interest,
831
00:57:38.190 --> 00:57:41.809
unless it's in everybody's interest kind of thing. So
832
00:57:42.705 --> 00:57:47.765
I don't know. I I just find it really cool that they're sort of like looking and they're finding ways of doing what they wanna do,
833
00:57:48.305 --> 00:57:54.330
hopefully without any Bitcoin change, and then they don't need permission. Right? I mean, nobody needs permission in Bitcoin unless they want everybody to change.
834
00:57:54.950 --> 00:58:00.170
835
00:58:00.535 --> 00:58:01.755
836
00:58:02.215 --> 00:58:05.275
They're trying to figure out how to do this stuff using, I think, Taproot,
837
00:58:05.575 --> 00:58:06.075
multisig
838
00:58:06.775 --> 00:58:08.955
Interesting. If I remember right. Yeah.
839
00:58:09.335 --> 00:58:13.710
840
00:58:14.170 --> 00:58:14.910
What happened?
841
00:58:15.210 --> 00:58:19.710
842
00:58:20.155 --> 00:58:23.855
the the the pictures and is a carrot that lives inside Bitcoin
843
00:58:24.555 --> 00:58:27.055
and it produces a lot of methane
844
00:58:27.515 --> 00:58:28.655
and carbon dioxide
845
00:58:29.350 --> 00:58:30.970
and it's gonna boil the oceans.
846
00:58:31.590 --> 00:58:33.930
So that's why nobody should eat carrots anymore.
847
00:58:34.390 --> 00:58:37.050
848
00:58:37.475 --> 00:58:43.895
trying to, like, dunk on Taproot. Like, oh, we've had all this all this innovation and all you guys have come up with is Taproot.
849
00:58:44.970 --> 00:58:45.470
850
00:58:46.170 --> 00:58:48.030
they are gonna have a fun time,
851
00:58:48.490 --> 00:58:49.309
not withdrawing.
852
00:58:51.665 --> 00:58:57.445
853
00:58:57.745 --> 00:59:09.825
You can just create the most complex, interesting ways to withdraw any way that you can imagine withdrawing funds we can come up with with the tap root, and they can't do it at all. If they have, ultrasound
854
00:59:10.285 --> 00:59:10.785
855
00:59:11.245 --> 00:59:13.185
we have infinite withdraw money.
856
00:59:14.045 --> 00:59:20.410
857
00:59:20.950 --> 00:59:24.490
many years ago that got just completely reversed by the entire blockchain.
858
00:59:25.164 --> 00:59:26.464
And the community rallied
859
00:59:26.765 --> 00:59:32.305
860
00:59:34.119 --> 00:59:38.220
Alright. So Fedmint grant season. A new grantee, Josh Kitman,
861
00:59:38.680 --> 00:59:40.299
is the 1st grantee of Fedmint,
862
00:59:40.920 --> 00:59:43.915
is working with mustache enthusiast, Odell.
863
00:59:44.375 --> 00:59:45.755
Oh, you're mentioned here,
864
00:59:46.055 --> 00:59:51.890
Matt. Has called most bullish man I'm wearing both my mustache and my hat. Okay. He's working on an MVP
865
00:59:52.190 --> 00:59:52.930
for Fedbit.
866
00:59:53.790 --> 00:59:58.609
867
00:59:59.605 --> 01:00:01.305
868
01:00:01.605 --> 01:00:06.105
firm on this holds firm on decision not to freeze Tornado Cash Addresses
869
01:00:07.430 --> 01:00:07.930
awaiting,
870
01:00:08.630 --> 01:00:09.530
law enforcement
871
01:00:10.710 --> 01:00:11.210
instructions.
872
01:00:11.830 --> 01:00:17.675
That's that's interesting. I mean, listen. Anything that can be capturable will be capturable will be captured,
873
01:00:18.775 --> 01:00:27.500
but it is nice to see companies, at least fighting back or pretending to fight back a little bit. It's always, I don't know. It's a feel good thing more than a useful thing.
874
01:00:29.400 --> 01:00:35.855
875
01:00:37.355 --> 01:00:50.599
Yep. That that's true, actually. Maybe that's what they're doing, just buying people time. This blog post specifically, I think it was in response to there was, like, a Wall Street Journal or New York Times or Bloomberg hit piece on Tether not freezing tornado cash.
876
01:00:51.934 --> 01:00:57.474
So they released this blog post and said, well, we got no notice to freeze, so we're not freezing anything until we got notice.
877
01:00:57.775 --> 01:01:02.170
878
01:01:02.809 --> 01:01:04.029
gold thief and impartiality.
879
01:01:04.970 --> 01:01:05.690
What else?
880
01:01:06.010 --> 01:01:07.549
New York Digital Investment
881
01:01:07.985 --> 01:01:12.805
Group announces lightning accelerator project called In Wolf's oh, yeah. So that's
882
01:01:13.265 --> 01:01:14.405
a that's a Russ
883
01:01:15.510 --> 01:01:17.450
Ross Ross Stevens, thing.
884
01:01:17.830 --> 01:01:27.595
885
01:01:28.375 --> 01:01:33.840
886
01:01:34.860 --> 01:01:38.560
887
01:01:39.015 --> 01:01:41.835
888
01:01:42.455 --> 01:01:43.595
889
01:01:45.495 --> 01:01:48.030
890
01:01:48.330 --> 01:01:49.230
roaming around.
891
01:01:50.090 --> 01:01:51.790
892
01:01:52.170 --> 01:01:52.670
Tajdreja
893
01:01:53.585 --> 01:01:54.484
joining LightSpark.
894
01:01:55.424 --> 01:02:01.345
I mean, this is big because, I mean, I have respect for him, and I just didn't expect much from LightSpark. So
895
01:02:02.460 --> 01:02:03.279
896
01:02:03.980 --> 01:02:05.119
897
01:02:05.900 --> 01:02:06.880
David Marcus,
898
01:02:07.180 --> 01:02:07.680
the
899
01:02:08.380 --> 01:02:15.884
prominent shit coiner that was running Facebook shit coin has left and made it he's making light lightning startup that I originally thought was
900
01:02:16.265 --> 01:02:27.630
901
01:02:27.945 --> 01:02:34.025
902
01:02:34.585 --> 01:02:41.440
903
01:02:41.820 --> 01:02:47.815
But he also he did have dot ETH. I think that's the strongest argument for why he's a shitcoiner. Yes.
904
01:02:48.135 --> 01:02:49.835
But I think he also
905
01:02:50.214 --> 01:02:51.595
is an early Bitcoin
906
01:02:52.200 --> 01:02:56.220
booster. He was there, like, I think, 2013. He started filling his bag,
907
01:02:56.680 --> 01:02:57.180
and,
908
01:02:58.119 --> 01:03:01.339
I think that he learned a lot from his experience at Facebook.
909
01:03:02.105 --> 01:03:03.805
My my four d chess,
910
01:03:04.425 --> 01:03:07.565
thought here with, his company, LightSpark, is that,
911
01:03:08.025 --> 01:03:10.845
so I think Mark Zuckerberg is also a closet Bitcoiner.
912
01:03:11.490 --> 01:03:14.950
And they were like, okay. We we can't launch our own SharePoint.
913
01:03:15.570 --> 01:03:20.710
So what we're gonna do is you're gonna start this company. You're gonna create lightning infrastructure,
914
01:03:21.105 --> 01:03:24.724
and then Facebook will acquire it. Yes. You'll get rich, and we'll get lightning,
915
01:03:25.105 --> 01:03:27.525
and the regulators won't have time to do anything.
916
01:03:27.825 --> 01:03:29.765
917
01:03:30.260 --> 01:03:32.440
you get to see Pierre become a shitcoin apologist.
918
01:03:33.300 --> 01:03:34.520
919
01:03:35.220 --> 01:03:36.360
920
01:03:36.900 --> 01:03:40.974
that smart, powerful, well capitalized people don't understand
921
01:03:41.434 --> 01:03:45.934
Bitcoin if they're sort of, like, working on technology. Right? Like, the Zuckerberg
922
01:03:46.234 --> 01:03:46.974
of sorts.
923
01:03:47.420 --> 01:03:48.240
They get
924
01:03:48.700 --> 01:03:55.600
it very much. They listen. They would love to have their own capture version of things too because then they get to print the money,
925
01:03:56.095 --> 01:03:56.914
but they also learn
926
01:03:57.295 --> 01:04:04.115
very fast that they will get captured. I mean, Libra was immediately killed because that actually posed a threat to the US
927
01:04:06.299 --> 01:04:09.519
fed. Right? I mean, they they could have had their currency
928
01:04:09.980 --> 01:04:23.234
available to, what, 2,000,000,000 people now or whatever it is on on Facebook these days on day 1. Like, press a button and boom, they are the new money issuer. Right? So I I I think they get it. I think they're gonna try to milk
929
01:04:23.960 --> 01:04:25.820
captured things as far as they can
930
01:04:26.200 --> 01:04:27.500
to stack more sats.
931
01:04:28.119 --> 01:04:34.845
But, but yeah. And this guy, like, he's been sort of only talking about Bitcoin and and sort of, like, trying to be polite
932
01:04:35.145 --> 01:04:38.525
about, like, I don't think other coins are
933
01:04:38.825 --> 01:04:41.010
very safe or non capturable
934
01:04:41.550 --> 01:04:43.570
kind of, like, rhetoric. Right?
935
01:04:43.950 --> 01:04:47.410
Bitcoin is very good at this kind of thing.
936
01:04:48.110 --> 01:04:49.170
He's very careful.
937
01:04:49.775 --> 01:04:51.615
938
01:04:52.015 --> 01:04:55.954
cocktail parties to go to. You know, he wants to Yeah. Be friendly.
939
01:04:56.540 --> 01:05:00.000
940
01:05:00.380 --> 01:05:01.520
you know, also consider
941
01:05:02.700 --> 01:05:07.045
you have to wonder first of all, I I do think that he's a big corner to some level,
942
01:05:07.905 --> 01:05:14.485
to some degree. But you also have to consider why they would be learning the importance of this and Bitcoin specifically,
943
01:05:15.089 --> 01:05:24.375
and why there is that pushback about like, there's obviously the the the the drive to want to have your own capturable thing, but also not be capturable
944
01:05:24.675 --> 01:05:25.175
by
945
01:05:25.635 --> 01:05:26.375
other people.
946
01:05:26.915 --> 01:05:29.415
And you you have to wonder what goes through,
947
01:05:30.355 --> 01:05:30.855
Zuck's
948
01:05:31.155 --> 01:05:31.655
mind
949
01:05:32.160 --> 01:05:37.060
as, you know, the the state tries to further and further encroach on his
950
01:05:37.520 --> 01:05:41.060
capacity to manage Facebook as he plea pleases.
951
01:05:41.595 --> 01:05:46.895
952
01:05:47.195 --> 01:05:51.375
Yes. Totally. And it's fair. I mean, he did create his own universe. Right?
953
01:05:52.220 --> 01:05:53.599
I mean, it's his rules.
954
01:05:54.380 --> 01:06:05.595
955
01:06:05.895 --> 01:06:11.619
I'm sure he's the one who wants to be the one, deciding what to censor and what not to censor. And so,
956
01:06:12.339 --> 01:06:12.920
you know,
957
01:06:13.619 --> 01:06:17.079
for for someone in this situation, it might be, you know,
958
01:06:18.204 --> 01:06:18.704
capturable
959
01:06:19.005 --> 01:06:24.145
for thee, but not for me as as like a working thing. And to Pierre's,
960
01:06:24.765 --> 01:06:31.900
shitcoin, Apologism. There is there there is an element. I mean, I think over time, everyone's going to be a Bitcoiner eventually.
961
01:06:32.599 --> 01:06:33.339
And so
962
01:06:33.800 --> 01:06:35.500
we will have to develop,
963
01:06:36.215 --> 01:06:37.675
means of forgiveness,
964
01:06:38.375 --> 01:06:42.235
so that we can get people properly integrated back into,
965
01:06:42.695 --> 01:06:43.755
civilized society.
966
01:06:44.450 --> 01:06:53.269
Okay. So I I agree with you, but I I'm not saying that about David Marcus in particular. I'm just saying, broadly speaking, like, David does seem like a pretty good guy.
967
01:06:53.845 --> 01:06:56.085
In the future, there's gonna be people that,
968
01:06:56.565 --> 01:07:02.985
people have way more skepticism about than David Marcus. You know? You know, the the original way of people
969
01:07:03.320 --> 01:07:05.580
970
01:07:05.880 --> 01:07:08.300
either proof of burn or proof of sold.
971
01:07:08.760 --> 01:07:11.980
You know, my my dear friend, Tina Cash
972
01:07:12.575 --> 01:07:15.714
has, has done his his cycle of repentance.
973
01:07:16.734 --> 01:07:22.035
And, you know, it's, we we we've all lost Sats along the way, some more than others.
974
01:07:22.849 --> 01:07:26.230
975
01:07:26.530 --> 01:07:29.270
were you a shit corner before becoming a Maxi?
976
01:07:29.595 --> 01:07:31.135
And I think it was, like, 60%
977
01:07:31.435 --> 01:07:32.255
said yes.
978
01:07:32.635 --> 01:07:34.575
And so I think clearly,
979
01:07:35.115 --> 01:07:35.615
empirically,
980
01:07:35.915 --> 01:07:37.535
we already have a mechanism
981
01:07:37.915 --> 01:07:38.415
for,
982
01:07:38.740 --> 01:07:39.560
you know, repentance
983
01:07:39.940 --> 01:07:41.880
and for you coming back into the fold.
984
01:07:42.180 --> 01:07:53.165
All you gotta do is just be humble. That's all you gotta do. We're not asking you to write a long medium post about how you've seen the light. Like, just just become a bit harder. Like, we're we're not,
985
01:07:53.480 --> 01:07:59.420
986
01:08:00.200 --> 01:08:01.100
Bitcoin toxic,
987
01:08:01.800 --> 01:08:05.145
starter pack. I was very disappointed with the lack of,
988
01:08:05.705 --> 01:08:08.125
radios and stuff, so I figured I I,
989
01:08:08.905 --> 01:08:11.225
I go make one. I I heard that,
990
01:08:11.860 --> 01:08:25.195
991
01:08:25.815 --> 01:08:28.635
992
01:08:30.100 --> 01:08:45.045
the maximalist attack, but can we not own the fundamentalist attack? Can we just let this one die? No. No. No. I love that one. I just I'd I don't want us I don't want a bunch of plebs, like, running around saying I'm a Bitcoin fundamentalist. Like, I just do not want it to happen.
993
01:08:46.310 --> 01:08:50.410
994
01:08:50.870 --> 01:08:51.370
it's,
995
01:08:51.910 --> 01:09:10.360
996
01:09:10.935 --> 01:09:13.275
997
01:09:13.655 --> 01:09:15.675
concerns. Right? So terrorist
998
01:09:16.855 --> 01:09:18.315
regulations around terrorism
999
01:09:18.615 --> 01:09:22.900
are are very restrictive. It's already designated. You know, they they're very
1000
01:09:23.280 --> 01:09:24.020
anti terrorist.
1001
01:09:24.640 --> 01:09:25.140
Fundamentalist,
1002
01:09:25.840 --> 01:09:33.665
at least here in the US You're founded by it. Yeah. That's not that's that's, you know, tax deductible. Again, like, that's, you know, fantastic,
1003
01:09:34.685 --> 01:09:35.745
framing. So
1004
01:09:36.890 --> 01:09:46.705
not only is it great from a tax perspective, but it's also like we've been we've been hearing people tell us, stop looking at the price, focus on the fundamentals.
1005
01:09:47.165 --> 01:09:53.739
Fundamentals are what matter. Okay. We're fundamentalists. And then everyone gets upset. So I I don't know what to say. I am a fundamentalist
1006
01:09:54.280 --> 01:09:54.780
1007
01:09:55.400 --> 01:10:00.040
1008
01:10:00.845 --> 01:10:03.585
it's a it's a it's a word that's gonna be coming up.
1009
01:10:03.965 --> 01:10:05.985
1010
01:10:06.285 --> 01:10:14.320
by now you'd think that the people who call us names would understand that, like, we really, really don't care if anything we embrace
1011
01:10:15.020 --> 01:10:16.000
the new nomenclature.
1012
01:10:17.335 --> 01:10:21.035
We love the semantics of a in group, out group.
1013
01:10:21.495 --> 01:10:22.635
It it just strengthens,
1014
01:10:23.255 --> 01:10:24.500
Bitcoiners. Like,
1015
01:10:25.060 --> 01:10:32.200
maybe they should see that their attacks only makes us stronger. It's, I don't know. I think by now they would have learned but they clearly don't.
1016
01:10:33.195 --> 01:10:37.775
1017
01:10:38.235 --> 01:10:43.150
1018
01:10:43.610 --> 01:10:45.230
I hear blocks in my head.
1019
01:10:46.330 --> 01:10:49.230
1020
01:10:49.825 --> 01:10:53.525
1021
01:10:53.985 --> 01:10:56.305
So you can get a beep in the house for a while. Make it,
1022
01:10:56.865 --> 01:10:58.485
1023
01:10:59.450 --> 01:11:01.790
what's the call? The the the the Muslims,
1024
01:11:02.250 --> 01:11:09.445
like, they they do the great Yes. Song, the call to prayer. It should be Yes. Something of of that sort. And a 144
1025
01:11:09.905 --> 01:11:10.805
times a day,
1026
01:11:11.345 --> 01:11:12.325
you you
1027
01:11:13.105 --> 01:11:23.360
1028
01:11:24.835 --> 01:11:25.415
Boom. That's
1029
01:11:26.275 --> 01:11:26.855
it. Alright.
1030
01:11:27.955 --> 01:11:29.255
No bullshit Bitcoin,
1031
01:11:30.035 --> 01:11:34.215
on Twitter and on Telegram. I wanted to give a shout out because
1032
01:11:35.230 --> 01:11:37.650
this guy group of people
1033
01:11:38.110 --> 01:11:41.970
put out some really, really awesome high signal Bitcoin information.
1034
01:11:42.835 --> 01:11:46.055
They have a new website and and they put all the stuff there.
1035
01:11:46.435 --> 01:11:49.015
I just hope that they add the direct link to the
1036
01:11:49.475 --> 01:11:50.215
actual source
1037
01:11:50.550 --> 01:11:52.970
as a second tweet to their tweet or something.
1038
01:11:53.350 --> 01:12:02.554
But, anyways, it's just it's nice to have, like, high signal Bitcoin information without the ultra pumpage. The pumpage is nice too, but, you know,
1039
01:12:02.935 --> 01:12:03.835
different channel.
1040
01:12:04.295 --> 01:12:09.355
So, yeah, I wanted to put that out there because sometimes I find new stuff for us, through them.
1041
01:12:10.679 --> 01:12:11.320
1042
01:12:11.880 --> 01:12:16.460
with the new website, they added a bunch of, like, separate RSS feeds so you can pick.
1043
01:12:17.000 --> 01:12:22.135
Nice. We were talking about RSS feed maximalism earlier, so I thought it was worth mentioning.
1044
01:12:22.435 --> 01:12:26.375
1045
01:12:26.810 --> 01:12:28.190
Explorer for mempool.space.
1046
01:12:29.530 --> 01:12:33.630
It is in everything that they do absolutely gorgeous visually,
1047
01:12:34.525 --> 01:12:34.925
and,
1048
01:12:35.325 --> 01:12:45.010
you can really see how, Lightning is mostly on Amazon and on Google and and on Microsoft, which is fine. Different model. I think it's FUD.
1049
01:12:45.550 --> 01:12:48.050
1050
01:12:48.430 --> 01:12:48.930
the,
1051
01:12:51.905 --> 01:12:52.485
it doesn't
1052
01:12:53.264 --> 01:12:56.324
and and, you know, I'm not speaking about any particular
1053
01:12:56.625 --> 01:12:58.645
node on the network or anything, but
1054
01:12:59.050 --> 01:13:00.590
there are people who use
1055
01:13:00.970 --> 01:13:01.470
proxies
1056
01:13:02.010 --> 01:13:04.110
where the proxies on AWS
1057
01:13:04.490 --> 01:13:06.990
and the node is on physical hardware.
1058
01:13:07.515 --> 01:13:08.255
And so,
1059
01:13:09.195 --> 01:13:17.409
like, I we should be educating people about, hey. You know, cloud, not great. But also, like, if you if it's a $100,000
1060
01:13:18.429 --> 01:13:22.769
on the cloud Who cares? And you've got, you know, a kajillion,
1061
01:13:23.070 --> 01:13:26.495
you know, dollars worth of Bitcoin on your cold keys cold card
1062
01:13:27.295 --> 01:13:28.915
that are cold keys,
1063
01:13:30.015 --> 01:13:30.515
then
1064
01:13:31.055 --> 01:13:32.035
who who cares?
1065
01:13:32.975 --> 01:13:38.880
But the other part too is that, like, the whole premise of Lightning is that you can shut down 50%,
1066
01:13:39.420 --> 01:13:41.520
80%, 99% of the network.
1067
01:13:41.900 --> 01:13:42.780
Right? And,
1068
01:13:43.994 --> 01:13:44.974
nobody cares.
1069
01:13:45.275 --> 01:13:51.935
It shouldn't matter. Right? It it's trust minimized. So somebody can force close the channel to you, and it's okay.
1070
01:13:52.270 --> 01:13:54.930
1071
01:13:55.870 --> 01:13:57.969
Yeah. That that's pretty cool.
1072
01:13:58.590 --> 01:14:09.965
So and and Vodafone as well, which is private entity. It's not hosting solution for everybody. So, the only way this changes is if AWS or Google Cloud become unreliable
1073
01:14:10.989 --> 01:14:14.769
1074
01:14:15.070 --> 01:14:19.570
why why try to make things more robust when they're not?
1075
01:14:20.105 --> 01:14:29.650
This isn't like an area in my mind where I want lightning people to be focused on this. No. I want lightning people to be focused on increasing payment reliability.
1076
01:14:30.270 --> 01:14:33.150
Like, that's the bigger UX problem than,
1077
01:14:33.855 --> 01:14:39.155
are we on AWS or not? And it just seems completely misguided to me. But but, Pierre,
1078
01:14:39.614 --> 01:14:45.180
1079
01:14:45.560 --> 01:14:57.755
1080
01:14:58.215 --> 01:15:00.155
But, anyway, I'll get off my soapbox.
1081
01:15:00.630 --> 01:15:09.530
1082
01:15:10.014 --> 01:15:12.275
an already existing Blockchain Explorer.
1083
01:15:12.895 --> 01:15:14.994
So the coolest part to me is that
1084
01:15:15.295 --> 01:15:23.739
you can click on a Lightning node, and then it also shows you the on chain transactions for the open and closes. And you can basically switch between on chain
1085
01:15:24.360 --> 01:15:28.115
and layer 2. So it it, like, dynamically goes between the 2,
1086
01:15:28.735 --> 01:15:30.435
which becomes extremely useful,
1087
01:15:30.895 --> 01:15:34.880
1088
01:15:35.840 --> 01:15:49.735
You know, like like, you got even the nerdy look, which I love as well, but then you got this, like, ultra amazing, high information, well designed sites. Like, it's just nice because then media can show this instead of that gold coin for Bitcoin.
1089
01:15:50.595 --> 01:15:56.599
1090
01:15:57.079 --> 01:16:02.139
1091
01:16:02.565 --> 01:16:13.840
Every time I see that I don't know if you know exactly what picture I'm talking about. I know exactly It's a money money money 2020 or whatever. I think it was before it. No. It was it has to be at least, like, 2016 or 2017.
1092
01:16:14.460 --> 01:16:17.260
1093
01:16:17.865 --> 01:16:20.125
either Amsterdam or the Atlanta one.
1094
01:16:20.425 --> 01:16:25.220
1095
01:16:26.180 --> 01:16:30.920
1096
01:16:31.300 --> 01:16:32.040
oh, man.
1097
01:16:32.340 --> 01:16:33.160
That's funny.
1098
01:16:33.565 --> 01:16:39.105
1099
01:16:40.445 --> 01:16:49.790
Ledger announced that all Best Buy stores in America are selling Ledger hardware wallets. What are your thoughts on that? Oh, I was actually going to add that to the list, and I forgot.
1100
01:16:50.405 --> 01:16:52.665
1101
01:16:53.205 --> 01:16:55.705
I mean, like, it is crazy to think
1102
01:16:56.485 --> 01:17:03.680
that, like, you know, only 10 years later because remember, right, back in the day you couldn't go buy a modem 10 years into the Internet anywhere.
1103
01:17:04.140 --> 01:17:06.720
You had to go specialize stores and stuff. So
1104
01:17:07.655 --> 01:17:08.875
I I think this is
1105
01:17:09.495 --> 01:17:12.955
this is a huge, huge deal. You're gonna have
1106
01:17:13.255 --> 01:17:17.090
like a cheap wallet that's, like, physically reasonably physically secure,
1107
01:17:17.789 --> 01:17:20.289
and people can properly get exposed to shit coins.
1108
01:17:22.590 --> 01:17:23.409
On, like,
1109
01:17:23.745 --> 01:17:25.925
any store that you can go and buy with cash.
1110
01:17:26.705 --> 01:17:30.645
1111
01:17:31.025 --> 01:17:44.585
1112
01:17:45.445 --> 01:17:49.145
1113
01:17:49.510 --> 01:17:51.050
1114
01:17:51.830 --> 01:17:56.730
you know, like, probably different firmware and different slightly different case looks so that you can differentiate,
1115
01:17:57.110 --> 01:18:01.275
what came directly from us. Mhmm. Plus we have more projects coming. So
1116
01:18:01.735 --> 01:18:03.115
1117
01:18:03.495 --> 01:18:10.100
another cool thing to to build on that is the fact that you have all these people who can now just buy this. And, you know,
1118
01:18:10.480 --> 01:18:18.715
Odell, you probably have more experience than, well, NVK. The 2 of you certainly have more experience than me actually onboarding people,
1119
01:18:19.495 --> 01:18:23.960
into these wallets and working with seed phrases and all of that is probably
1120
01:18:24.660 --> 01:18:38.875
one of the more difficult things to get across when it comes to, you know, security and just in general. So the fact that just random people can go to the store, pick up one of these things. And in order to turn it on, like, you have to start engaging with the seed phrase.
1121
01:18:39.500 --> 01:18:41.600
A lot of people are probably gonna get burned, unfortunately,
1122
01:18:42.060 --> 01:18:43.600
but that's part of how it works.
1123
01:18:43.980 --> 01:18:48.025
1124
01:18:53.545 --> 01:19:07.305
initialize them with a seed. I'll put them in shrink-wrap, which takes like a second, and I'll just go and replace them at the store with, like, one of those shoplifting bags, you know, the with the foil around. It it looked like it was behind one of the, like, locked glass things,
1125
01:19:07.925 --> 01:19:15.740
1126
01:19:16.200 --> 01:19:18.460
knew it's like, oh, this is something we need to
1127
01:19:19.165 --> 01:19:27.105
protect a little bit more. Although, given the crypto nature, that alone might tell them enough. It's like, hey, this is actually one of the things that needs to be more protected.
1128
01:19:27.760 --> 01:19:29.699
1129
01:19:30.000 --> 01:19:31.940
1130
01:19:32.719 --> 01:19:33.219
1131
01:19:34.239 --> 01:19:39.565
I I it's still great. I mean, like, you know, we can, you know, I can, I can go and sort of, like,
1132
01:19:40.025 --> 01:19:40.525
intellectually
1133
01:19:41.385 --> 01:19:42.365
bait about,
1134
01:19:43.305 --> 01:19:58.285
like, attacks on this? But, like, at the end of the day, it's just more people getting exposed to self custody, and and that's a huge win. And more exposure in general. Like, it just it's totally normalized. It's like crypto. I'm sorry to use that phrase, but, like, it it is Ledger.
1135
01:19:58.825 --> 01:20:00.925
1136
01:20:01.705 --> 01:20:02.205
like,
1137
01:20:03.160 --> 01:20:07.500
crazy fringe thing. It's like you literally just go to Best Buy and pick up a wallet.
1138
01:20:08.280 --> 01:20:12.140