April 14, 2022
Andrew Poelstra at Bitcoin Commons on March 18th 2022
I sat down with Andrew Poelstra on March 18th 2022 at the Bitcoin Takeover event held at Bitcoin Commons in Austin during SXSW to discuss his open source work.
Video: https://bitcointv.com/w/vmwWJVfFEL7vxY47EGtdLz
support the show: https://citadeldispatch.com/contribute
twitch: https://twitch.tv/citadeldispatch
bitcointv: https://bitcointv.com/video-channels/citadeldispatch/videos
podcast: https://www.podpage.com/citadeldispatch
telegram: https://t.me/citadeldispatch
stream sats to the show: https://www.fountain.fm/
join the chat: https://matrix.to/#/#citadel:bitcoin.kyoto
00:12 - Understanding the type of work Andrew does and its importance to the Bitcoin network
01:02 - Andrew's experience in the open source space and his introduction to Bitcoin
08:31 - Andrew's involvement in Bitcoin Core and the challenges of working on consensus code
15:26 - Andrew's role as the director of research at Blockstream and the growth of Bitcoin research
18:18 - The significance of open source development in the Bitcoin space and the ability to be well paid and respected
WEBVTT
NOTE
Transcription provided by Podhome.fm
Created: 3/17/2024 4:25:35 PM
Duration: 1514.031
Channels: 1
1
00:00:12.855 --> 00:00:13.355
Understanding
2
00:00:13.735 --> 00:00:16.074
of the type of work that Andrew does,
3
00:00:16.650 --> 00:00:17.630
and his team
4
00:00:17.930 --> 00:00:29.605
is really critical to advancing the Bitcoin network. And it's at a layer that, that a lot of us don't get to look through into every day. So we really appreciate Andrew being here today. And thank you, Matt, for leading this talk.
5
00:00:40.620 --> 00:00:41.760
Yeah. Let's do that.
6
00:00:46.895 --> 00:00:47.875
Thank you, Parker.
7
00:00:50.170 --> 00:00:55.789
Yeah. So I'll just echo, what Parker said. We're very lucky to have Andrew joining us here.
8
00:00:57.945 --> 00:01:01.725
If we let him run, most of us will not understand what he's talking about.
9
00:01:02.265 --> 00:01:05.325
So we will try and bring it back, and keep it
10
00:01:06.479 --> 00:01:06.979
accessible.
11
00:01:08.719 --> 00:01:10.820
I guess a good place to start is
12
00:01:11.679 --> 00:01:15.675
how how long have you, been working in the open source space for?
13
00:01:16.075 --> 00:01:17.675
So in the open source space,
14
00:01:18.155 --> 00:01:20.015
beyond Bitcoin, I've been doing,
15
00:01:20.475 --> 00:01:22.690
I think, public open source work since I was
16
00:01:23.250 --> 00:01:23.750
12,
17
00:01:24.130 --> 00:01:25.030
11, or 12,
18
00:01:25.490 --> 00:01:26.950
so about 20 years.
19
00:01:28.050 --> 00:01:28.550
Originally,
20
00:01:29.570 --> 00:01:31.085
like, the first public open source
21
00:01:31.565 --> 00:01:36.945
tool that I worked on was something called PCB, which is what it sound like. It's a printed circuit board editor.
22
00:01:37.485 --> 00:01:39.000
It was part of the the
23
00:01:39.480 --> 00:01:40.860
GEDA, which is a GNU
24
00:01:41.560 --> 00:01:42.700
Electronic Design
25
00:01:43.400 --> 00:01:44.780
Apps, something like that.
26
00:01:45.240 --> 00:01:55.765
And I spent a summer working on just improving the UI, changing their units from, I think, 1 100th of a millimeter to nanometers so you could do more precise things when you're working in metric and things like that.
27
00:01:56.660 --> 00:01:59.960
And before that, I've been doing some, like, my own kind of hobby projects,
28
00:02:00.260 --> 00:02:03.480
but back then, I didn't have, like, an Internet connection at home,
29
00:02:03.925 --> 00:02:14.189
at least not all the time. I think when my parents weren't on the phone, then I could connect to the Internet. So it wasn't so easy wasn't so easy to be doing open source stuff. I got into Bitcoin, though. That's kind of a
30
00:02:14.489 --> 00:02:17.150
continuation of that. In late 2011,
31
00:02:17.450 --> 00:02:24.805
somebody on slashdot, maybe this was kind of the very end of slash dot, I think, was to kind of pump me into the Bitcoin space. Somebody was posting something
32
00:02:25.825 --> 00:02:26.325
wrong
33
00:02:27.060 --> 00:02:27.960
about Bitcoin,
34
00:02:28.260 --> 00:02:47.290
and I don't remember what it was. I think at the time, there was a meme that the way the Bitcoin worked, right, is that you would grind. You would find these these hashes, right, that was mining with, and then you would trade the hash values somehow. Right? You would, like, I don't know, put them in a secret envelope. And I don't know. I mean, it didn't make sense. Right? So I followed the slash daughter who who was making this claim to bitcoin.org
35
00:02:47.670 --> 00:02:54.825
to try to understand how all these idiots trading cashes thought that they were going to make some sort of financial system out of it.
36
00:02:55.205 --> 00:02:55.705
And
37
00:02:56.005 --> 00:02:57.065
as it turned out,
38
00:02:57.445 --> 00:03:00.185
their, Bitcoin does not work by people trading hashes.
39
00:03:00.700 --> 00:03:01.520
And from bitcoin.org,
40
00:03:01.820 --> 00:03:03.680
I I wound up, on IRC,
41
00:03:04.300 --> 00:03:09.360
and I was able to meet I was very fortunate to show up on IRC at this time in late 2011, early 2012.
42
00:03:09.725 --> 00:03:11.745
At that time, Mt. Gox was in full swing.
43
00:03:12.045 --> 00:03:14.465
I think the price had just crashed from $30
44
00:03:14.845 --> 00:03:15.985
down to, like, 15.
45
00:03:16.605 --> 00:03:18.945
So it was a steal. Right? I could get in at half price.
46
00:03:19.280 --> 00:03:19.780
And,
47
00:03:20.160 --> 00:03:22.980
no. No. Of course. It it continued down to, like, 2 or 3.
48
00:03:24.560 --> 00:03:26.740
And then it was going to 0, so I sold everything.
49
00:03:27.245 --> 00:03:29.425
No. Not quite. Not quite, but close.
50
00:03:29.805 --> 00:03:30.305
So
51
00:03:31.325 --> 00:03:40.400
I was very fortunate at that time. It was very early days. Sort of the only way that you could get into Bitcoin was something like that. There were sort of 2 big ways that I was familiar with.
52
00:03:40.700 --> 00:03:48.215
Maybe 3. But, I mean, the the big ways were either you were a developer, like a cryptographer or a hobbyist or somebody who thought it was just a neat technical system,
53
00:03:48.675 --> 00:03:51.415
or you had heard of the Silk Road and it was a way to buy drugs,
54
00:03:51.760 --> 00:03:54.500
basically, is what you'd come in. And then there were
55
00:03:54.880 --> 00:04:01.385
I guess, the third way was the Ron Paul people, the kind of libertarian, like, hard money kind of set of people. But at that
56
00:04:01.765 --> 00:04:11.130
time, it was difficult to sell Bitcoin to a lot of the the hard money people, to the Mises Institute, for example, famously did did had a very negative view of Bitcoin.
57
00:04:11.830 --> 00:04:19.585
And this came from sort of an intuition that if something's on a computer, then it can't be hard money. Right? Like like, computer money is the opposite of hard money.
58
00:04:20.065 --> 00:04:27.205
And a theme that we've seen throughout this day, right, is that for the most part, in everything except for Bitcoin, that intuition is true.
59
00:04:27.600 --> 00:04:32.100
As we move our ordinary money onto computers, we're finding we're exposing ourselves to censorship
60
00:04:32.640 --> 00:04:36.895
and, and things of that nature. But with Bitcoin, you don't, which is very surprising,
61
00:04:38.715 --> 00:04:42.175
and, like, it's not obvious that that should even be possible.
62
00:04:42.635 --> 00:04:43.135
Right?
63
00:04:43.460 --> 00:04:49.080
Because as silly as this idea was that Bitcoin was trading hash values, which is what people were saying back then,
64
00:04:50.099 --> 00:04:54.265
there have been a lot of good memes about Bitcoin, but that one was one of the oldest and and funnier ones.
65
00:04:55.045 --> 00:05:14.805
It's difficult to think, like, how else could it work. Right? And now I think we we've as a as a community, we've started to develop some more intuition about how digital signatures work and the notion of signing transactions and transactions having inputs and outputs and so on, but it very quickly becomes very technical still. And this idea that you could have money that somehow is on a computer,
66
00:05:15.185 --> 00:05:19.685
and you spend the money by creating data and transmitting it over public networks
67
00:05:20.389 --> 00:05:32.324
that are, like, not only being wiretapped at every possible opportunity, but in the end, the data goes on to a public blockchain, which is then replicated 10th of 1000th times across the world and would be stored until long after everyone in this room is dead.
68
00:05:32.945 --> 00:05:39.310
It's surprising that you could transfer money that way, that somebody couldn't just download the blockchain and just copy all your coins off and and run laughing.
69
00:05:40.090 --> 00:05:40.590
And
70
00:05:41.130 --> 00:05:44.190
so moving back to to the open source world, I I showed up on IRC.
71
00:05:44.675 --> 00:05:54.289
At the time, everybody on IRC, actually, still everybody on IRC, is kind of a crazy, like, gray beard developer kind of type. And the Bitcoin community was fairly small,
72
00:05:54.750 --> 00:05:56.689
and everybody was very welcoming.
73
00:05:57.949 --> 00:06:05.745
And, at that time in my life, I I was, again very fortunate in the timing. I was transitioning into graduate school. I was actually moving here to Austin,
74
00:06:06.205 --> 00:06:08.785
to start a math PhD program here at UT,
75
00:06:09.485 --> 00:06:09.985
and
76
00:06:10.990 --> 00:06:11.650
the first
77
00:06:12.270 --> 00:06:20.645
couple years of a math PhD program, I would say, are probably the easiest thing that anybody could possibly do. It was just like a free ride. It was great.
78
00:06:20.945 --> 00:06:22.245
They, they gave me $20,000
79
00:06:22.625 --> 00:06:28.720
a year to just move to Austin and party all the time. And all I had to do was, like, write some tests every 3 or 4
80
00:06:29.020 --> 00:06:36.700
months. And, and that's cool. And then, you know, eventually, they say, like, you know, you should get a supervisor. You should have a thesis topic and all this stuff. And at that point, I left. But they,
81
00:06:37.675 --> 00:06:45.215
at the time, it was just like it was great. I I had very little responsibility. I had nobody no deadlines, no anything. And
82
00:06:45.910 --> 00:06:47.530
at that time, I showed up on IRC,
83
00:06:48.070 --> 00:06:57.535
and there were people like Greg Maxwell there and Peter Wula and Matt Corallo, who are all still still around, by the way, although they're they're some of them are less public than they have been in the past.
84
00:06:57.915 --> 00:06:58.415
And
85
00:06:59.675 --> 00:07:05.050
they said, hey. There's this thing called the eprint archive, which is a place where cryptographers post
86
00:07:05.430 --> 00:07:37.650
their papers that they're working on prior to going through the peer review and being published and stuff. And I said, hey, Andrew. Let me try reading these papers and try to understand this this Bitcoin stuff where we have this ECDSA signature scheme, and there's this other scheme called Schnorr that we think might be better for various reasons. Maybe we can investigate that kind of thing. And it's funny here to be be talking about this in 2022, and I guess, like, 7 or 8 later, we 7 or 8 years later, we finally did get Schnorr into Bitcoin. But we were talking about it back then. We were talking about Snarks, back then. There was a paper in late 2013 called Snarks for c,
87
00:07:37.950 --> 00:07:39.410
by, like, 8 different
88
00:07:39.950 --> 00:07:44.105
authors. Probably the most famous one in this movie, Eli Ben Sousen, who's the CEO of Starquare.
89
00:07:44.805 --> 00:07:45.305
And
90
00:07:45.925 --> 00:07:48.345
it was a small community of people who
91
00:07:48.720 --> 00:07:54.260
were doing open source development, who were reading open access literature, cryptographic literature,
92
00:07:54.639 --> 00:07:57.460
and the idea to me that you could just download,
93
00:07:58.065 --> 00:08:03.125
like, the things that academics were doing, and you could see what was happening in this intellectual development
94
00:08:04.385 --> 00:08:04.885
of
95
00:08:05.870 --> 00:08:07.810
of the system of the whole field of cryptography
96
00:08:08.190 --> 00:08:14.414
was very exciting and eye opening. Right? Like, you don't need academic access to get access to the eprint archive. You don't need to be a cryptographer
97
00:08:14.715 --> 00:08:15.854
to read these papers.
98
00:08:16.955 --> 00:08:24.610
There is some some sort of basic math literacy you need, but you can get that from the Internet as well. You don't need to go through a system. There's no no gates that
99
00:08:25.310 --> 00:08:34.485
you're being kept out of. There is if you want credentials perhaps, but that's not what you needed to do Bitcoin. You didn't need any credentials. You still don't need any credentials.
100
00:08:34.785 --> 00:08:38.165
It's very much an open access system where as long as you can be, you know,
101
00:08:38.660 --> 00:08:45.735
kinda kinda reasonably sociable and and get along with people, and not show up and start fights and and fool around on Twitter all day,
102
00:08:46.214 --> 00:08:54.635
then you can get stuff done. Right? People will recognize that that you know what you're talking about or don't, and they're very helpful. They're very friendly. They'll they'll help you to ramp up.
103
00:08:55.240 --> 00:08:55.900
And so
104
00:08:56.280 --> 00:09:08.895
I showed up in the Bitcoin world. I had a bit of math experience, a bit of crypto experience. Like, I I was sort of primed to be working on this kind of stuff and a fair bit of open source experience at that time. I'd done a lot of public development and public projects.
105
00:09:09.275 --> 00:09:16.170
I was familiar with the process of, like, writing code and asking people to read it and and going through iterations and review.
106
00:09:16.550 --> 00:09:21.314
And people saying mean things to you and people asking me to rewrite things that you'd put weeks of,
107
00:09:21.855 --> 00:09:23.394
your blood and sweat into.
108
00:09:24.014 --> 00:09:24.514
And
109
00:09:25.134 --> 00:09:27.394
so I was okay with that. And
110
00:09:28.540 --> 00:09:30.320
from there, there was sort of a natural
111
00:09:30.699 --> 00:09:36.639
a natural thing. I would I would suggest that Bitcoin, especially Bitcoin Core, is not the friendliest of open source projects,
112
00:09:37.415 --> 00:09:44.795
to join. It's very high friction because Bitcoin Core has consensus code in it. Right? Like, it's really and then consensus code for now, like, a multi $100,000,000,000
113
00:09:45.495 --> 00:09:45.995
system
114
00:09:46.620 --> 00:09:48.560
is really kind of mind blowing.
115
00:09:48.940 --> 00:09:51.760
But at the time, it was a much smaller system, first of all,
116
00:09:52.220 --> 00:09:52.720
and
117
00:09:53.315 --> 00:09:54.855
we didn't understand consensus
118
00:09:55.315 --> 00:09:57.815
as well as we do now. There's an interesting,
119
00:09:58.355 --> 00:10:05.029
historical tidbit. If you look for the word soft fork on Bitcoin talk, you'll find that the first use of that term,
120
00:10:05.570 --> 00:10:07.430
I believe, dates to 2012
121
00:10:08.610 --> 00:10:09.350
or so,
122
00:10:09.650 --> 00:10:12.230
around the same time that the idea of mining pools
123
00:10:12.995 --> 00:10:23.710
showed up, and other things that we take for granted, like, very old thing. But, actually, Bitcoin had been going for several years. There were big exchanges running. And at the time as a community, we didn't understand the notion of
124
00:10:24.570 --> 00:10:28.095
hard forks and soft forks and how consensus worked and and things like that.
125
00:10:28.495 --> 00:10:34.754
It was a very, very, early Wild West day. Like, even even for Bitcoin, like, this was a Wild West. This was pretty crazy.
126
00:10:35.855 --> 00:10:36.355
And,
127
00:10:37.340 --> 00:10:45.440
secondly, as much as Bitcoin Core is in at the time, it was just called Bitcoin. It was a very controversial name change for for reasons I'm not going to go into.
128
00:10:47.885 --> 00:10:50.144
I gravitated more towards the crypto side of things
129
00:10:50.685 --> 00:10:51.185
and
130
00:10:52.685 --> 00:10:53.665
the cryptography
131
00:10:54.450 --> 00:10:59.190
behind Bitcoin is actually done in a separate software library called Libsec p 256k1.
132
00:11:00.450 --> 00:11:09.005
And I remember Greg Maxwell, who at the time was just like the god of Bitcoin. And and to this day, actually, if there's one person in the world who's responsible for Bitcoin existing and surviving,
133
00:11:09.600 --> 00:11:12.100
and thriving the way that it has, it will be Greg Maxwell.
134
00:11:13.280 --> 00:11:17.620
I was talking to him on IRC because he's he's actually pretty easy to talk to on IRC,
135
00:11:18.160 --> 00:11:18.660
and
136
00:11:19.165 --> 00:11:22.705
he suggested that I work on an arm assembly
137
00:11:23.405 --> 00:11:35.420
implementation of some crypto algorithm. Right? Some, like, very obscure technical thing. And I was kinda shocked that Greg Maxwell would think that I could do something like that. Right? Like, it's just, like, I was kinda very flattered. And and even though I wasn't,
138
00:11:35.895 --> 00:11:48.150
I had a little bit of experience doing stuff like that. It was with arm assembly and crypto and stuff. I thought, wow. Like, I should go do that. And so I spent some time trying to do it. And in in the end, I didn't actually succeed at that. To this day, I have not touched the arm assembly code in the.
139
00:11:48.610 --> 00:11:54.115
But by doing that, I learned about how the library worked. I learned that who the different developers were. I learned how to interact with them.
140
00:11:55.475 --> 00:12:01.255
And between that and my reading of stuff on the eprint archive, I was then able to become a cryptog, a contributor
141
00:12:01.640 --> 00:12:04.300
to the Libsakp library, which does all of the crypto.
142
00:12:04.920 --> 00:12:05.420
And,
143
00:12:05.960 --> 00:12:12.685
eventually, I became a maintainer, actually, for several years. I was one of the persons, who had merge access to to that library.
144
00:12:14.905 --> 00:12:18.285
And I remember when this first happened, I was very scared.
145
00:12:18.800 --> 00:12:20.980
Bitcoin at the time had a market cap, maybe $1,000,000,000
146
00:12:21.680 --> 00:12:24.020
around this time, I think, maybe maybe 2 or $3,000,000,000,
147
00:12:25.280 --> 00:12:26.740
and the cryptography
148
00:12:27.755 --> 00:12:43.670
underlying it, everything in Bitcoin is cryptography somehow, but there's a core of it that's, like, is, like, hard cryptography. It's it's, like, pure cryptography. I I don't know what the right word is, but it's the signatures. Right? It's the stuff that deals with secret keys and with public keys where if those keys are leaked or lost or something,
149
00:12:44.035 --> 00:12:46.855
then all the money is gone forever.
150
00:12:47.714 --> 00:12:48.214
And
151
00:12:49.555 --> 00:12:57.950
there are ways there are very subtle ways that you can lose key material. Whenever you have computers working with secret key material, that's a very dangerous and fragile situation. It's it's really incredible
152
00:12:58.330 --> 00:13:13.930
that cryptography works at all. Right? Because you have all these public networks. You have these public logs. You have everything. Everything can be seen. So how can you take a secret key? You put this into some sort of computer system. It takes that secret key and does something with it, and it outputs
153
00:13:14.470 --> 00:13:23.595
something that looks, you know, random, but somehow derived from that key in a way that you can verify, because you can verify the signatures and stuff. But somehow, it doesn't reveal anything about the key,
154
00:13:24.055 --> 00:13:47.420
and there is a lot of, like it really is dancing a fine line. The way that it works, right, is the computer needs to generate a second ephemeral key, and then it turns out that if you mix 2 uniformly random things together, the output will be uniformly random. Sorry. If you mix a uniformly random thing and anything else together, the result will be uniformly random. So, there's a sense in which you can erase data by mixing it with uniform randomness, and that's what happens as part of the signature process.
155
00:13:48.120 --> 00:13:53.605
But if you mess up and you don't use quite uniform enough randomness, right, if you use, like, too many one bits or whatever,
156
00:13:54.144 --> 00:14:00.564
then it's not uniform, and you don't erase all the secret key data, and then your keys get leaked. And, in fact, this has happened on the real network.
157
00:14:01.120 --> 00:14:09.595
So I was working on the library that was used in Bitcoin Core or Bitcoin at the time, and this was the most popularly used library. On the verification side,
158
00:14:09.975 --> 00:14:15.835
it is, like, the by far the most popular. It's it's the library that's in the reference implementation, right, on the reference Bitcoin node.
159
00:14:16.350 --> 00:14:25.410
And this library is actually used inside of a lot of hardware wallets. It's used in all of the major Ethereum node implementation that's used in wallets for that. It's used in, like,
160
00:14:25.954 --> 00:14:29.975
all over the place, even in non cryptocurrency application. It's a very widely used library.
161
00:14:30.675 --> 00:14:31.175
And
162
00:14:31.555 --> 00:14:34.055
if the code that I was writing or reviewing
163
00:14:34.430 --> 00:14:40.930
or merging was somehow wrong, then there was potentially 1,000,000,000 of dollars that could just go away.
164
00:14:41.585 --> 00:14:50.645
And at the time, I was, you know, in my early twenties. I was, like, screwing around, like, doing some sort of immigration scam, with the UT here so that I could fool around and, you know, play the piano
165
00:14:50.980 --> 00:14:52.440
and drink beer all the time.
166
00:14:52.899 --> 00:14:55.399
And I had this multibillion dollar system
167
00:14:55.779 --> 00:14:57.080
that somehow depended
168
00:14:57.779 --> 00:15:00.520
you know, I I think there were safeguards in retrospect.
169
00:15:00.964 --> 00:15:05.545
But, certainly, it felt at the time like it depended on me not doing anything too reckless.
170
00:15:06.404 --> 00:15:06.904
And
171
00:15:07.899 --> 00:15:20.855
this is a very strange experience. It was a very strange phenomenon, really, like, at the time. And and now Bitcoin is much bigger, and there are many more stakeholders. And and in many ways, it's not the wild west, and there really are safeguards. Right? At this point, like, I actually
172
00:15:21.235 --> 00:15:26.055
probably couldn't screw up the system even if I tried. But at the time, maybe I could've.
173
00:15:26.620 --> 00:15:30.320
And the idea that I could do that despite not being
174
00:15:31.019 --> 00:15:31.519
credentialed
175
00:15:31.820 --> 00:15:33.040
in any real way,
176
00:15:33.420 --> 00:15:39.685
I was just a student who, you know, in the the professional world, certainly in software development and and in cryptography.
177
00:15:41.105 --> 00:15:45.125
Being a student is not a good thing. Right? People are very distrustful of students writing
178
00:15:45.790 --> 00:15:47.650
cryptography code, with good reason.
179
00:15:48.190 --> 00:15:50.529
It was cool that I could just walk in and sort of do that.
180
00:15:51.070 --> 00:15:57.954
And so that was that was probably 2013, 2014, and I I continue to to ride that out pretty much to this day.
181
00:15:59.615 --> 00:16:00.274
In 2014,
182
00:16:00.654 --> 00:16:02.915
there was a company called Blockstream that started.
183
00:16:03.540 --> 00:16:12.095
And they're they're reasonably well known, certainly on the technical side of things. A lot of people have heard of Blockstream and outside of the the technical sphere or maybe not as well known, but
184
00:16:12.635 --> 00:16:18.415
they were at the time in late 2014 and and a project by a bunch of people basically on IRC.
185
00:16:19.019 --> 00:16:24.000
We had a couple, like, VCU, like, California people. I don't know where they came from, and they're not they're not there anymore,
186
00:16:25.019 --> 00:16:33.205
who showed up and kinda facilitate a thing that would buy us flights and and do all sorts of cool stuff. But what it felt like to me and what it was really was me and a bunch of people in IRC
187
00:16:33.985 --> 00:16:38.000
who were able somehow to form a company around all this experimental
188
00:16:38.379 --> 00:16:39.600
kind of crypto stuff
189
00:16:40.139 --> 00:16:43.839
that we were doing basically in our spare time for fun.
190
00:16:44.485 --> 00:16:59.975
And for me, it meant that I could stay in Austin where I no longer had to be going. Like, I I had a student visa at the time with UT, and that was really why I was still in that PhD program. And I was able to drop that and switch to a work visa and stay in Austin, and that was cool. But it was also cool that we were making money,
191
00:17:00.375 --> 00:17:02.315
or at least raising money doing,
192
00:17:03.575 --> 00:17:05.195
cryptography, doing, like, experimental
193
00:17:05.895 --> 00:17:06.395
doing
194
00:17:06.960 --> 00:17:08.420
experimental, like, novel
195
00:17:09.040 --> 00:17:15.825
cryptocurrency research. Like, cryptocurrency research wasn't even really a thing at that time outside of outside of us and a couple other similar groups.
196
00:17:16.544 --> 00:17:17.284
And so
197
00:17:17.664 --> 00:17:20.705
I've continued basically in in that vein over the last,
198
00:17:21.985 --> 00:17:28.120
6 or 8 years pretty much since Blockchain has been formed. At this point, I I I am the director of research at Blocks, and I run a team of researchers.
199
00:17:28.580 --> 00:17:42.390
For a little while, we were kind of the only team, in town, but now there are many, which is super cool to see. Chainco Labs also funds a lot of Bitcoin development, and they they partially fund the Bitcoin OpTech newsletter and and also the outreach associated to that.
200
00:17:43.190 --> 00:17:48.650
There's Brink, which is a company, Mike Schmidt, who who lives here in Austin, although he's he's not here. He lives outside Austin.
201
00:17:49.190 --> 00:17:52.455
No. I shouldn't point in what direction, but, you know, he's around.
202
00:17:52.995 --> 00:17:53.495
And,
203
00:17:55.154 --> 00:18:03.120
and there's this block, of course, which was Square Crypto until recently. Right? There's there's all these different groups who are doing Bitcoin research as well as
204
00:18:03.500 --> 00:18:05.600
stakeholders, you know, exchanges and stuff.
205
00:18:06.059 --> 00:18:10.960
Funding research, like paying for core developers to work and and contributing to this open source world.
206
00:18:11.585 --> 00:18:12.085
And
207
00:18:13.265 --> 00:18:14.165
this is a fascinating
208
00:18:15.265 --> 00:18:20.165
thing to see as aside from just the fascination in Bitcoin itself. From the open source perspective,
209
00:18:20.860 --> 00:18:33.095
there's been forever open source has been around forever. It's been around in some form or other probably since the seventies. I think it sort of came in as an idea. And before that, actually, everything was, like nobody even thought about trying to monetize source code.
210
00:18:33.635 --> 00:18:37.815
And then when people did open source, it was right there to say, well, you know, maybe we could do that without
211
00:18:38.610 --> 00:18:44.790
trapping people and trying to control access to information and, like, somehow forming a censorship based monetization model.
212
00:18:45.330 --> 00:18:57.140
So open source has been around forever, and open source led to to many things that we know and love. Right? The Linux operating system, which is used in in half the phones that are out there as well as 80% of all the servers and stuff out there.
213
00:18:57.680 --> 00:19:05.875
And all over the Internet. Right? The the decoders that show you JPEGs and GIFs and the original web browsers and and actually all current web browsers are all open source.
214
00:19:06.595 --> 00:19:12.455
It's just everywhere, and historically, there was no way to monetize this. There was this this horrible phenomenon where
215
00:19:12.990 --> 00:19:15.010
people would invent groundbreaking
216
00:19:15.310 --> 00:19:21.890
critical things, as you have an xkcd about this. People who would write code that would then become, like, a foundational
217
00:19:22.284 --> 00:19:23.265
critical component
218
00:19:24.044 --> 00:19:26.465
of the infrastructure of the modern world,
219
00:19:26.845 --> 00:19:29.904
and they would be basically begging for donations on the Internet,
220
00:19:30.330 --> 00:19:32.510
Or they will be making, like, $40,000
221
00:19:33.049 --> 00:19:41.965
a year because some random software company was willing to hire them in the in the, like, whatever part of Oklahoma that they lived in and stuff like that. And and they were doing, like, really
222
00:19:42.345 --> 00:19:47.485
critical stuff that's leading to trillion of dollars of wealth creation in other parts of the industry, but they personally
223
00:19:47.865 --> 00:19:49.245
don't see a dime of that.
224
00:19:49.570 --> 00:19:50.950
And in the Bitcoin space,
225
00:19:51.330 --> 00:19:52.390
we are very fortunate
226
00:19:52.770 --> 00:19:56.870
in that there is a lot of money kind of by definition in the Bitcoin space,
227
00:19:57.330 --> 00:19:57.830
and
228
00:19:58.875 --> 00:20:03.375
more broadly geopolitically there's a lot of money in cryptography. There's a lot of money in computer security,
229
00:20:04.235 --> 00:20:07.695
and it's possible to get a very high paying job doing bitcoin
230
00:20:08.340 --> 00:20:27.520
development. And if you were here around in the the very early days of Bitcoin as well, it's also possible to make a nontrivial amount of money by just owning some Bitcoin and holding on to it. Although I should I should maybe clarify because there's a meme out there. One of the many, many ideas that people have about Bitcoin is that all the OG developers have just, like, 1,000,000,000 of dollars or whatever.
231
00:20:28.059 --> 00:20:28.559
And
232
00:20:29.260 --> 00:20:39.075
this is actually not true for a couple of reasons. And I'm obviously that's I have a very self serving motivation in saying this to everybody, but it is legitimately a a falsehood that,
233
00:20:39.935 --> 00:20:45.409
Bitcoin OGs all have tremendous piles of money. One reason is that they, like many people,
234
00:20:46.029 --> 00:20:53.784
after buying Bitcoin and seeing it go up 10 x, right, from 15¢ to a buck 50, just like fold it all and said like, all right, you know, I I can buy a car now.
235
00:20:54.485 --> 00:20:58.264
Another reason is though at the time, it seemed like a really experimental
236
00:20:58.644 --> 00:21:06.940
kind of sketchy system that was going to fall over any day, and it really did for a very long time, like, longer than than anyone would expect. I would say personally
237
00:21:07.644 --> 00:21:09.105
that it was maybe, like,
238
00:21:09.644 --> 00:21:10.784
2016 or 2017
239
00:21:11.085 --> 00:21:14.625
before I thought that maybe the system could could maybe keep a phone,
240
00:21:15.100 --> 00:21:24.000
that there wasn't going to be some break and shot to where, like, the mining incentives would turn out not to work or, you know, who knows? Maybe the crypto would be broken in some way or maybe just, like, network systems.
241
00:21:24.505 --> 00:21:27.645
Maybe it couldn't handle partitioning or maybe there'd be a fork or
242
00:21:29.225 --> 00:21:30.445
or whatever. And
243
00:21:31.280 --> 00:21:36.740
and so the people who are closest to the system really building it had a much clearer idea of the fragility of the system
244
00:21:37.040 --> 00:21:45.865
and the inherent fragility of cryptography of of how narrow a dance all of this code was doing to work with secret key data to do meaningful things.
245
00:21:46.280 --> 00:21:52.140
And so the people who were building the system and working on it the hardest were probably the most suspicious of it,
246
00:21:52.680 --> 00:21:55.895
beyond the people who would, like, look at it once and walk away, of course.
247
00:21:56.455 --> 00:21:59.975
And then finally, like, as a more general thing, it's good not to, to,
248
00:22:01.175 --> 00:22:08.690
to invest too heavily in something that your career already invests in. Right? We we learned that from Enron, but as a general thing. Right? That just your your personal
249
00:22:08.990 --> 00:22:11.490
what you're good at is a self, a form of investment.
250
00:22:12.115 --> 00:22:12.615
So
251
00:22:12.995 --> 00:22:14.135
by diverse the diversification
252
00:22:15.395 --> 00:22:28.290
mandates that you probably shouldn't have all your actual money is something that your career also depends on because that way, you know, you you while you have some protection against 1 or both of those sorry. You have some protection against one of those, not both going away.
253
00:22:28.695 --> 00:22:31.515
And, and if instead you put all your chips where
254
00:22:32.054 --> 00:22:32.534
where,
255
00:22:33.095 --> 00:22:36.715
where your employment prospects are, you know, that's that's a very risky thing to do.
256
00:22:37.210 --> 00:22:41.210
So, so for that reason, I mean, a few people did get very rich, and I'm not gonna say who,
257
00:22:41.530 --> 00:22:42.429
but, you know,
258
00:22:43.049 --> 00:22:51.924
a few people did. But for the most part, developers in the Bitcoin space were not able to just, like, buy 10,000 coins back when they were worth 50¢ and and have held on to them today.
259
00:22:52.225 --> 00:22:53.684
But what we were able to do
260
00:22:54.019 --> 00:22:57.799
is form an industry, a thriving industry with a lot of economic
261
00:22:58.179 --> 00:23:02.760
activity happening in it where it's possible as an open source developer
262
00:23:03.684 --> 00:23:09.865
to be well paid and well respected. And that's a very novel thing in the history of open source and in the history of development,
263
00:23:10.404 --> 00:23:19.059
and it's a very precious thing. Like and and I again, obviously, this is very self serving. It's precious that I get paid so much, isn't it? But what I mean is,
264
00:23:19.695 --> 00:23:27.430
historically, open source I guess, I I haven't I realized I haven't defined open source, but it's the idea that that you can publish code and anybody can show up and contribute
265
00:23:29.910 --> 00:23:30.570
to it. Right? And that the code is public. You can vet it. You can verify it.
266
00:23:31.270 --> 00:23:36.250
If you think there's something suspicious about it, you can read it and and assure yourself that there's not, and there is.
267
00:23:36.625 --> 00:23:42.485
If you want to contribute to it, if it's broken, you can fix it. You can submit changes. People will take it, and, you know, everybody can share.
268
00:23:42.865 --> 00:23:43.365
And,
269
00:23:44.130 --> 00:23:46.630
historically, there hasn't been any model to
270
00:23:48.370 --> 00:23:50.310
to make that sustainable economically
271
00:23:50.690 --> 00:23:57.325
other than charity, basically. So, for example, the Linux operating system for a long time, basically, like, IBM was paying a couple developers to do it.
272
00:23:57.865 --> 00:24:02.880
And now there are, you know, probably a couple dozen companies like IBM paying Linux kernel developers.
273
00:24:03.260 --> 00:24:13.445
But they're doing it because, you know, with 1 or 2 employees on, like, a, you know, 100000 person payroll. So So it's fine. It's not very much money, and their business does kinda depend on Linux continuing, but it's just sort of a
274
00:24:14.065 --> 00:24:15.045
charitable thing.
275
00:24:15.640 --> 00:24:28.295
And that works for Linux because Linux is huge and important, but it doesn't work for a lot of smaller projects that wind up being done by individuals in their spare time. So now it's personal charity. Right? It's people just doing a lot of these projects out of a labor of love,
276
00:24:28.835 --> 00:24:33.929
and it's very cool that for something like Bitcoin, which for a lot of us was a labor of love,
277
00:24:34.630 --> 00:24:36.070
we're able to be paid for that. And then,
278
00:24:37.429 --> 00:24:40.970
we're able to do it in a financially sustainable way. So
279
00:24:41.735 --> 00:24:42.315
so that's
280
00:24:42.695 --> 00:24:43.674
it's pretty cool.
281
00:24:44.695 --> 00:24:46.554
I mean, dude, you fucking killed it.
282
00:24:48.534 --> 00:24:50.780
You have 2 minutes left. It's 2
283
00:24:54.040 --> 00:24:54.620
minutes left.
284
00:24:59.655 --> 00:25:04.635
Cool. So I I think I'll seed my last 2 minutes, then if it's really 2 minutes. So thank you all for listening.
NOTE
Transcription provided by Podhome.fm
Created: 3/17/2024 4:25:35 PM
Duration: 1514.031
Channels: 1
1
00:00:12.855 --> 00:00:13.355
2
00:00:13.735 --> 00:00:16.074
of the type of work that Andrew does,
3
00:00:16.650 --> 00:00:17.630
and his team
4
00:00:17.930 --> 00:00:29.605
is really critical to advancing the Bitcoin network. And it's at a layer that, that a lot of us don't get to look through into every day. So we really appreciate Andrew being here today. And thank you, Matt, for leading this talk.
5
00:00:40.620 --> 00:00:41.760
6
00:00:46.895 --> 00:00:47.875
7
00:00:50.170 --> 00:00:55.789
Yeah. So I'll just echo, what Parker said. We're very lucky to have Andrew joining us here.
8
00:00:57.945 --> 00:01:01.725
If we let him run, most of us will not understand what he's talking about.
9
00:01:02.265 --> 00:01:05.325
So we will try and bring it back, and keep it
10
00:01:06.479 --> 00:01:06.979
accessible.
11
00:01:08.719 --> 00:01:10.820
I guess a good place to start is
12
00:01:11.679 --> 00:01:15.675
how how long have you, been working in the open source space for?
13
00:01:16.075 --> 00:01:17.675
14
00:01:18.155 --> 00:01:20.015
beyond Bitcoin, I've been doing,
15
00:01:20.475 --> 00:01:22.690
I think, public open source work since I was
16
00:01:23.250 --> 00:01:23.750
12,
17
00:01:24.130 --> 00:01:25.030
11, or 12,
18
00:01:25.490 --> 00:01:26.950
so about 20 years.
19
00:01:28.050 --> 00:01:28.550
Originally,
20
00:01:29.570 --> 00:01:31.085
like, the first public open source
21
00:01:31.565 --> 00:01:36.945
tool that I worked on was something called PCB, which is what it sound like. It's a printed circuit board editor.
22
00:01:37.485 --> 00:01:39.000
It was part of the the
23
00:01:39.480 --> 00:01:40.860
GEDA, which is a GNU
24
00:01:41.560 --> 00:01:42.700
Electronic Design
25
00:01:43.400 --> 00:01:44.780
Apps, something like that.
26
00:01:45.240 --> 00:01:55.765
And I spent a summer working on just improving the UI, changing their units from, I think, 1 100th of a millimeter to nanometers so you could do more precise things when you're working in metric and things like that.
27
00:01:56.660 --> 00:01:59.960
And before that, I've been doing some, like, my own kind of hobby projects,
28
00:02:00.260 --> 00:02:03.480
but back then, I didn't have, like, an Internet connection at home,
29
00:02:03.925 --> 00:02:14.189
at least not all the time. I think when my parents weren't on the phone, then I could connect to the Internet. So it wasn't so easy wasn't so easy to be doing open source stuff. I got into Bitcoin, though. That's kind of a
30
00:02:14.489 --> 00:02:17.150
continuation of that. In late 2011,
31
00:02:17.450 --> 00:02:24.805
somebody on slashdot, maybe this was kind of the very end of slash dot, I think, was to kind of pump me into the Bitcoin space. Somebody was posting something
32
00:02:25.825 --> 00:02:26.325
wrong
33
00:02:27.060 --> 00:02:27.960
about Bitcoin,
34
00:02:28.260 --> 00:02:47.290
and I don't remember what it was. I think at the time, there was a meme that the way the Bitcoin worked, right, is that you would grind. You would find these these hashes, right, that was mining with, and then you would trade the hash values somehow. Right? You would, like, I don't know, put them in a secret envelope. And I don't know. I mean, it didn't make sense. Right? So I followed the slash daughter who who was making this claim to bitcoin.org
35
00:02:47.670 --> 00:02:54.825
to try to understand how all these idiots trading cashes thought that they were going to make some sort of financial system out of it.
36
00:02:55.205 --> 00:02:55.705
And
37
00:02:56.005 --> 00:02:57.065
as it turned out,
38
00:02:57.445 --> 00:03:00.185
their, Bitcoin does not work by people trading hashes.
39
00:03:00.700 --> 00:03:01.520
And from bitcoin.org,
40
00:03:01.820 --> 00:03:03.680
I I wound up, on IRC,
41
00:03:04.300 --> 00:03:09.360
and I was able to meet I was very fortunate to show up on IRC at this time in late 2011, early 2012.
42
00:03:09.725 --> 00:03:11.745
At that time, Mt. Gox was in full swing.
43
00:03:12.045 --> 00:03:14.465
I think the price had just crashed from $30
44
00:03:14.845 --> 00:03:15.985
down to, like, 15.
45
00:03:16.605 --> 00:03:18.945
So it was a steal. Right? I could get in at half price.
46
00:03:19.280 --> 00:03:19.780
And,
47
00:03:20.160 --> 00:03:22.980
no. No. Of course. It it continued down to, like, 2 or 3.
48
00:03:24.560 --> 00:03:26.740
And then it was going to 0, so I sold everything.
49
00:03:27.245 --> 00:03:29.425
No. Not quite. Not quite, but close.
50
00:03:29.805 --> 00:03:30.305
So
51
00:03:31.325 --> 00:03:40.400
I was very fortunate at that time. It was very early days. Sort of the only way that you could get into Bitcoin was something like that. There were sort of 2 big ways that I was familiar with.
52
00:03:40.700 --> 00:03:48.215
Maybe 3. But, I mean, the the big ways were either you were a developer, like a cryptographer or a hobbyist or somebody who thought it was just a neat technical system,
53
00:03:48.675 --> 00:03:51.415
or you had heard of the Silk Road and it was a way to buy drugs,
54
00:03:51.760 --> 00:03:54.500
basically, is what you'd come in. And then there were
55
00:03:54.880 --> 00:04:01.385
I guess, the third way was the Ron Paul people, the kind of libertarian, like, hard money kind of set of people. But at that
56
00:04:01.765 --> 00:04:11.130
time, it was difficult to sell Bitcoin to a lot of the the hard money people, to the Mises Institute, for example, famously did did had a very negative view of Bitcoin.
57
00:04:11.830 --> 00:04:19.585
And this came from sort of an intuition that if something's on a computer, then it can't be hard money. Right? Like like, computer money is the opposite of hard money.
58
00:04:20.065 --> 00:04:27.205
And a theme that we've seen throughout this day, right, is that for the most part, in everything except for Bitcoin, that intuition is true.
59
00:04:27.600 --> 00:04:32.100
As we move our ordinary money onto computers, we're finding we're exposing ourselves to censorship
60
00:04:32.640 --> 00:04:36.895
and, and things of that nature. But with Bitcoin, you don't, which is very surprising,
61
00:04:38.715 --> 00:04:42.175
and, like, it's not obvious that that should even be possible.
62
00:04:42.635 --> 00:04:43.135
Right?
63
00:04:43.460 --> 00:04:49.080
Because as silly as this idea was that Bitcoin was trading hash values, which is what people were saying back then,
64
00:04:50.099 --> 00:04:54.265
there have been a lot of good memes about Bitcoin, but that one was one of the oldest and and funnier ones.
65
00:04:55.045 --> 00:05:14.805
It's difficult to think, like, how else could it work. Right? And now I think we we've as a as a community, we've started to develop some more intuition about how digital signatures work and the notion of signing transactions and transactions having inputs and outputs and so on, but it very quickly becomes very technical still. And this idea that you could have money that somehow is on a computer,
66
00:05:15.185 --> 00:05:19.685
and you spend the money by creating data and transmitting it over public networks
67
00:05:20.389 --> 00:05:32.324
that are, like, not only being wiretapped at every possible opportunity, but in the end, the data goes on to a public blockchain, which is then replicated 10th of 1000th times across the world and would be stored until long after everyone in this room is dead.
68
00:05:32.945 --> 00:05:39.310
It's surprising that you could transfer money that way, that somebody couldn't just download the blockchain and just copy all your coins off and and run laughing.
69
00:05:40.090 --> 00:05:40.590
And
70
00:05:41.130 --> 00:05:44.190
so moving back to to the open source world, I I showed up on IRC.
71
00:05:44.675 --> 00:05:54.289
At the time, everybody on IRC, actually, still everybody on IRC, is kind of a crazy, like, gray beard developer kind of type. And the Bitcoin community was fairly small,
72
00:05:54.750 --> 00:05:56.689
and everybody was very welcoming.
73
00:05:57.949 --> 00:06:05.745
And, at that time in my life, I I was, again very fortunate in the timing. I was transitioning into graduate school. I was actually moving here to Austin,
74
00:06:06.205 --> 00:06:08.785
to start a math PhD program here at UT,
75
00:06:09.485 --> 00:06:09.985
and
76
00:06:10.990 --> 00:06:11.650
the first
77
00:06:12.270 --> 00:06:20.645
couple years of a math PhD program, I would say, are probably the easiest thing that anybody could possibly do. It was just like a free ride. It was great.
78
00:06:20.945 --> 00:06:22.245
They, they gave me $20,000
79
00:06:22.625 --> 00:06:28.720
a year to just move to Austin and party all the time. And all I had to do was, like, write some tests every 3 or 4
80
00:06:29.020 --> 00:06:36.700
months. And, and that's cool. And then, you know, eventually, they say, like, you know, you should get a supervisor. You should have a thesis topic and all this stuff. And at that point, I left. But they,
81
00:06:37.675 --> 00:06:45.215
at the time, it was just like it was great. I I had very little responsibility. I had nobody no deadlines, no anything. And
82
00:06:45.910 --> 00:06:47.530
at that time, I showed up on IRC,
83
00:06:48.070 --> 00:06:57.535
and there were people like Greg Maxwell there and Peter Wula and Matt Corallo, who are all still still around, by the way, although they're they're some of them are less public than they have been in the past.
84
00:06:57.915 --> 00:06:58.415
And
85
00:06:59.675 --> 00:07:05.050
they said, hey. There's this thing called the eprint archive, which is a place where cryptographers post
86
00:07:05.430 --> 00:07:37.650
their papers that they're working on prior to going through the peer review and being published and stuff. And I said, hey, Andrew. Let me try reading these papers and try to understand this this Bitcoin stuff where we have this ECDSA signature scheme, and there's this other scheme called Schnorr that we think might be better for various reasons. Maybe we can investigate that kind of thing. And it's funny here to be be talking about this in 2022, and I guess, like, 7 or 8 later, we 7 or 8 years later, we finally did get Schnorr into Bitcoin. But we were talking about it back then. We were talking about Snarks, back then. There was a paper in late 2013 called Snarks for c,
87
00:07:37.950 --> 00:07:39.410
by, like, 8 different
88
00:07:39.950 --> 00:07:44.105
authors. Probably the most famous one in this movie, Eli Ben Sousen, who's the CEO of Starquare.
89
00:07:44.805 --> 00:07:45.305
And
90
00:07:45.925 --> 00:07:48.345
it was a small community of people who
91
00:07:48.720 --> 00:07:54.260
were doing open source development, who were reading open access literature, cryptographic literature,
92
00:07:54.639 --> 00:07:57.460
and the idea to me that you could just download,
93
00:07:58.065 --> 00:08:03.125
like, the things that academics were doing, and you could see what was happening in this intellectual development
94
00:08:04.385 --> 00:08:04.885
of
95
00:08:05.870 --> 00:08:07.810
of the system of the whole field of cryptography
96
00:08:08.190 --> 00:08:14.414
was very exciting and eye opening. Right? Like, you don't need academic access to get access to the eprint archive. You don't need to be a cryptographer
97
00:08:14.715 --> 00:08:15.854
to read these papers.
98
00:08:16.955 --> 00:08:24.610
There is some some sort of basic math literacy you need, but you can get that from the Internet as well. You don't need to go through a system. There's no no gates that
99
00:08:25.310 --> 00:08:34.485
you're being kept out of. There is if you want credentials perhaps, but that's not what you needed to do Bitcoin. You didn't need any credentials. You still don't need any credentials.
100
00:08:34.785 --> 00:08:38.165
It's very much an open access system where as long as you can be, you know,
101
00:08:38.660 --> 00:08:45.735
kinda kinda reasonably sociable and and get along with people, and not show up and start fights and and fool around on Twitter all day,
102
00:08:46.214 --> 00:08:54.635
then you can get stuff done. Right? People will recognize that that you know what you're talking about or don't, and they're very helpful. They're very friendly. They'll they'll help you to ramp up.
103
00:08:55.240 --> 00:08:55.900
And so
104
00:08:56.280 --> 00:09:08.895
I showed up in the Bitcoin world. I had a bit of math experience, a bit of crypto experience. Like, I I was sort of primed to be working on this kind of stuff and a fair bit of open source experience at that time. I'd done a lot of public development and public projects.
105
00:09:09.275 --> 00:09:16.170
I was familiar with the process of, like, writing code and asking people to read it and and going through iterations and review.
106
00:09:16.550 --> 00:09:21.314
And people saying mean things to you and people asking me to rewrite things that you'd put weeks of,
107
00:09:21.855 --> 00:09:23.394
your blood and sweat into.
108
00:09:24.014 --> 00:09:24.514
And
109
00:09:25.134 --> 00:09:27.394
so I was okay with that. And
110
00:09:28.540 --> 00:09:30.320
from there, there was sort of a natural
111
00:09:30.699 --> 00:09:36.639
a natural thing. I would I would suggest that Bitcoin, especially Bitcoin Core, is not the friendliest of open source projects,
112
00:09:37.415 --> 00:09:44.795
to join. It's very high friction because Bitcoin Core has consensus code in it. Right? Like, it's really and then consensus code for now, like, a multi $100,000,000,000
113
00:09:45.495 --> 00:09:45.995
system
114
00:09:46.620 --> 00:09:48.560
is really kind of mind blowing.
115
00:09:48.940 --> 00:09:51.760
But at the time, it was a much smaller system, first of all,
116
00:09:52.220 --> 00:09:52.720
and
117
00:09:53.315 --> 00:09:54.855
we didn't understand consensus
118
00:09:55.315 --> 00:09:57.815
as well as we do now. There's an interesting,
119
00:09:58.355 --> 00:10:05.029
historical tidbit. If you look for the word soft fork on Bitcoin talk, you'll find that the first use of that term,
120
00:10:05.570 --> 00:10:07.430
I believe, dates to 2012
121
00:10:08.610 --> 00:10:09.350
or so,
122
00:10:09.650 --> 00:10:12.230
around the same time that the idea of mining pools
123
00:10:12.995 --> 00:10:23.710
showed up, and other things that we take for granted, like, very old thing. But, actually, Bitcoin had been going for several years. There were big exchanges running. And at the time as a community, we didn't understand the notion of
124
00:10:24.570 --> 00:10:28.095
hard forks and soft forks and how consensus worked and and things like that.
125
00:10:28.495 --> 00:10:34.754
It was a very, very, early Wild West day. Like, even even for Bitcoin, like, this was a Wild West. This was pretty crazy.
126
00:10:35.855 --> 00:10:36.355
And,
127
00:10:37.340 --> 00:10:45.440
secondly, as much as Bitcoin Core is in at the time, it was just called Bitcoin. It was a very controversial name change for for reasons I'm not going to go into.
128
00:10:47.885 --> 00:10:50.144
I gravitated more towards the crypto side of things
129
00:10:50.685 --> 00:10:51.185
and
130
00:10:52.685 --> 00:10:53.665
the cryptography
131
00:10:54.450 --> 00:10:59.190
behind Bitcoin is actually done in a separate software library called Libsec p 256k1.
132
00:11:00.450 --> 00:11:09.005
And I remember Greg Maxwell, who at the time was just like the god of Bitcoin. And and to this day, actually, if there's one person in the world who's responsible for Bitcoin existing and surviving,
133
00:11:09.600 --> 00:11:12.100
and thriving the way that it has, it will be Greg Maxwell.
134
00:11:13.280 --> 00:11:17.620
I was talking to him on IRC because he's he's actually pretty easy to talk to on IRC,
135
00:11:18.160 --> 00:11:18.660
and
136
00:11:19.165 --> 00:11:22.705
he suggested that I work on an arm assembly
137
00:11:23.405 --> 00:11:35.420
implementation of some crypto algorithm. Right? Some, like, very obscure technical thing. And I was kinda shocked that Greg Maxwell would think that I could do something like that. Right? Like, it's just, like, I was kinda very flattered. And and even though I wasn't,
138
00:11:35.895 --> 00:11:48.150
I had a little bit of experience doing stuff like that. It was with arm assembly and crypto and stuff. I thought, wow. Like, I should go do that. And so I spent some time trying to do it. And in in the end, I didn't actually succeed at that. To this day, I have not touched the arm assembly code in the.
139
00:11:48.610 --> 00:11:54.115
But by doing that, I learned about how the library worked. I learned that who the different developers were. I learned how to interact with them.
140
00:11:55.475 --> 00:12:01.255
And between that and my reading of stuff on the eprint archive, I was then able to become a cryptog, a contributor
141
00:12:01.640 --> 00:12:04.300
to the Libsakp library, which does all of the crypto.
142
00:12:04.920 --> 00:12:05.420
And,
143
00:12:05.960 --> 00:12:12.685
eventually, I became a maintainer, actually, for several years. I was one of the persons, who had merge access to to that library.
144
00:12:14.905 --> 00:12:18.285
And I remember when this first happened, I was very scared.
145
00:12:18.800 --> 00:12:20.980
Bitcoin at the time had a market cap, maybe $1,000,000,000
146
00:12:21.680 --> 00:12:24.020
around this time, I think, maybe maybe 2 or $3,000,000,000,
147
00:12:25.280 --> 00:12:26.740
and the cryptography
148
00:12:27.755 --> 00:12:43.670
underlying it, everything in Bitcoin is cryptography somehow, but there's a core of it that's, like, is, like, hard cryptography. It's it's, like, pure cryptography. I I don't know what the right word is, but it's the signatures. Right? It's the stuff that deals with secret keys and with public keys where if those keys are leaked or lost or something,
149
00:12:44.035 --> 00:12:46.855
then all the money is gone forever.
150
00:12:47.714 --> 00:12:48.214
And
151
00:12:49.555 --> 00:12:57.950
there are ways there are very subtle ways that you can lose key material. Whenever you have computers working with secret key material, that's a very dangerous and fragile situation. It's it's really incredible
152
00:12:58.330 --> 00:13:13.930
that cryptography works at all. Right? Because you have all these public networks. You have these public logs. You have everything. Everything can be seen. So how can you take a secret key? You put this into some sort of computer system. It takes that secret key and does something with it, and it outputs
153
00:13:14.470 --> 00:13:23.595
something that looks, you know, random, but somehow derived from that key in a way that you can verify, because you can verify the signatures and stuff. But somehow, it doesn't reveal anything about the key,
154
00:13:24.055 --> 00:13:47.420
and there is a lot of, like it really is dancing a fine line. The way that it works, right, is the computer needs to generate a second ephemeral key, and then it turns out that if you mix 2 uniformly random things together, the output will be uniformly random. Sorry. If you mix a uniformly random thing and anything else together, the result will be uniformly random. So, there's a sense in which you can erase data by mixing it with uniform randomness, and that's what happens as part of the signature process.
155
00:13:48.120 --> 00:13:53.605
But if you mess up and you don't use quite uniform enough randomness, right, if you use, like, too many one bits or whatever,
156
00:13:54.144 --> 00:14:00.564
then it's not uniform, and you don't erase all the secret key data, and then your keys get leaked. And, in fact, this has happened on the real network.
157
00:14:01.120 --> 00:14:09.595
So I was working on the library that was used in Bitcoin Core or Bitcoin at the time, and this was the most popularly used library. On the verification side,
158
00:14:09.975 --> 00:14:15.835
it is, like, the by far the most popular. It's it's the library that's in the reference implementation, right, on the reference Bitcoin node.
159
00:14:16.350 --> 00:14:25.410
And this library is actually used inside of a lot of hardware wallets. It's used in all of the major Ethereum node implementation that's used in wallets for that. It's used in, like,
160
00:14:25.954 --> 00:14:29.975
all over the place, even in non cryptocurrency application. It's a very widely used library.
161
00:14:30.675 --> 00:14:31.175
And
162
00:14:31.555 --> 00:14:34.055
if the code that I was writing or reviewing
163
00:14:34.430 --> 00:14:40.930
or merging was somehow wrong, then there was potentially 1,000,000,000 of dollars that could just go away.
164
00:14:41.585 --> 00:14:50.645
And at the time, I was, you know, in my early twenties. I was, like, screwing around, like, doing some sort of immigration scam, with the UT here so that I could fool around and, you know, play the piano
165
00:14:50.980 --> 00:14:52.440
and drink beer all the time.
166
00:14:52.899 --> 00:14:55.399
And I had this multibillion dollar system
167
00:14:55.779 --> 00:14:57.080
that somehow depended
168
00:14:57.779 --> 00:15:00.520
you know, I I think there were safeguards in retrospect.
169
00:15:00.964 --> 00:15:05.545
But, certainly, it felt at the time like it depended on me not doing anything too reckless.
170
00:15:06.404 --> 00:15:06.904
And
171
00:15:07.899 --> 00:15:20.855
this is a very strange experience. It was a very strange phenomenon, really, like, at the time. And and now Bitcoin is much bigger, and there are many more stakeholders. And and in many ways, it's not the wild west, and there really are safeguards. Right? At this point, like, I actually
172
00:15:21.235 --> 00:15:26.055
probably couldn't screw up the system even if I tried. But at the time, maybe I could've.
173
00:15:26.620 --> 00:15:30.320
And the idea that I could do that despite not being
174
00:15:31.019 --> 00:15:31.519
credentialed
175
00:15:31.820 --> 00:15:33.040
in any real way,
176
00:15:33.420 --> 00:15:39.685
I was just a student who, you know, in the the professional world, certainly in software development and and in cryptography.
177
00:15:41.105 --> 00:15:45.125
Being a student is not a good thing. Right? People are very distrustful of students writing
178
00:15:45.790 --> 00:15:47.650
cryptography code, with good reason.
179
00:15:48.190 --> 00:15:50.529
It was cool that I could just walk in and sort of do that.
180
00:15:51.070 --> 00:15:57.954
And so that was that was probably 2013, 2014, and I I continue to to ride that out pretty much to this day.
181
00:15:59.615 --> 00:16:00.274
In 2014,
182
00:16:00.654 --> 00:16:02.915
there was a company called Blockstream that started.
183
00:16:03.540 --> 00:16:12.095
And they're they're reasonably well known, certainly on the technical side of things. A lot of people have heard of Blockstream and outside of the the technical sphere or maybe not as well known, but
184
00:16:12.635 --> 00:16:18.415
they were at the time in late 2014 and and a project by a bunch of people basically on IRC.
185
00:16:19.019 --> 00:16:24.000
We had a couple, like, VCU, like, California people. I don't know where they came from, and they're not they're not there anymore,
186
00:16:25.019 --> 00:16:33.205
who showed up and kinda facilitate a thing that would buy us flights and and do all sorts of cool stuff. But what it felt like to me and what it was really was me and a bunch of people in IRC
187
00:16:33.985 --> 00:16:38.000
who were able somehow to form a company around all this experimental
188
00:16:38.379 --> 00:16:39.600
kind of crypto stuff
189
00:16:40.139 --> 00:16:43.839
that we were doing basically in our spare time for fun.
190
00:16:44.485 --> 00:16:59.975
And for me, it meant that I could stay in Austin where I no longer had to be going. Like, I I had a student visa at the time with UT, and that was really why I was still in that PhD program. And I was able to drop that and switch to a work visa and stay in Austin, and that was cool. But it was also cool that we were making money,
191
00:17:00.375 --> 00:17:02.315
or at least raising money doing,
192
00:17:03.575 --> 00:17:05.195
cryptography, doing, like, experimental
193
00:17:05.895 --> 00:17:06.395
doing
194
00:17:06.960 --> 00:17:08.420
experimental, like, novel
195
00:17:09.040 --> 00:17:15.825
cryptocurrency research. Like, cryptocurrency research wasn't even really a thing at that time outside of outside of us and a couple other similar groups.
196
00:17:16.544 --> 00:17:17.284
And so
197
00:17:17.664 --> 00:17:20.705
I've continued basically in in that vein over the last,
198
00:17:21.985 --> 00:17:28.120
6 or 8 years pretty much since Blockchain has been formed. At this point, I I I am the director of research at Blocks, and I run a team of researchers.
199
00:17:28.580 --> 00:17:42.390
For a little while, we were kind of the only team, in town, but now there are many, which is super cool to see. Chainco Labs also funds a lot of Bitcoin development, and they they partially fund the Bitcoin OpTech newsletter and and also the outreach associated to that.
200
00:17:43.190 --> 00:17:48.650
There's Brink, which is a company, Mike Schmidt, who who lives here in Austin, although he's he's not here. He lives outside Austin.
201
00:17:49.190 --> 00:17:52.455
No. I shouldn't point in what direction, but, you know, he's around.
202
00:17:52.995 --> 00:17:53.495
And,
203
00:17:55.154 --> 00:18:03.120
and there's this block, of course, which was Square Crypto until recently. Right? There's there's all these different groups who are doing Bitcoin research as well as
204
00:18:03.500 --> 00:18:05.600
stakeholders, you know, exchanges and stuff.
205
00:18:06.059 --> 00:18:10.960
Funding research, like paying for core developers to work and and contributing to this open source world.
206
00:18:11.585 --> 00:18:12.085
And
207
00:18:13.265 --> 00:18:14.165
this is a fascinating
208
00:18:15.265 --> 00:18:20.165
thing to see as aside from just the fascination in Bitcoin itself. From the open source perspective,
209
00:18:20.860 --> 00:18:33.095
there's been forever open source has been around forever. It's been around in some form or other probably since the seventies. I think it sort of came in as an idea. And before that, actually, everything was, like nobody even thought about trying to monetize source code.
210
00:18:33.635 --> 00:18:37.815
And then when people did open source, it was right there to say, well, you know, maybe we could do that without
211
00:18:38.610 --> 00:18:44.790
trapping people and trying to control access to information and, like, somehow forming a censorship based monetization model.
212
00:18:45.330 --> 00:18:57.140
So open source has been around forever, and open source led to to many things that we know and love. Right? The Linux operating system, which is used in in half the phones that are out there as well as 80% of all the servers and stuff out there.
213
00:18:57.680 --> 00:19:05.875
And all over the Internet. Right? The the decoders that show you JPEGs and GIFs and the original web browsers and and actually all current web browsers are all open source.
214
00:19:06.595 --> 00:19:12.455
It's just everywhere, and historically, there was no way to monetize this. There was this this horrible phenomenon where
215
00:19:12.990 --> 00:19:15.010
people would invent groundbreaking
216
00:19:15.310 --> 00:19:21.890
critical things, as you have an xkcd about this. People who would write code that would then become, like, a foundational
217
00:19:22.284 --> 00:19:23.265
critical component
218
00:19:24.044 --> 00:19:26.465
of the infrastructure of the modern world,
219
00:19:26.845 --> 00:19:29.904
and they would be basically begging for donations on the Internet,
220
00:19:30.330 --> 00:19:32.510
Or they will be making, like, $40,000
221
00:19:33.049 --> 00:19:41.965
a year because some random software company was willing to hire them in the in the, like, whatever part of Oklahoma that they lived in and stuff like that. And and they were doing, like, really
222
00:19:42.345 --> 00:19:47.485
critical stuff that's leading to trillion of dollars of wealth creation in other parts of the industry, but they personally
223
00:19:47.865 --> 00:19:49.245
don't see a dime of that.
224
00:19:49.570 --> 00:19:50.950
And in the Bitcoin space,
225
00:19:51.330 --> 00:19:52.390
we are very fortunate
226
00:19:52.770 --> 00:19:56.870
in that there is a lot of money kind of by definition in the Bitcoin space,
227
00:19:57.330 --> 00:19:57.830
and
228
00:19:58.875 --> 00:20:03.375
more broadly geopolitically there's a lot of money in cryptography. There's a lot of money in computer security,
229
00:20:04.235 --> 00:20:07.695
and it's possible to get a very high paying job doing bitcoin
230
00:20:08.340 --> 00:20:27.520
development. And if you were here around in the the very early days of Bitcoin as well, it's also possible to make a nontrivial amount of money by just owning some Bitcoin and holding on to it. Although I should I should maybe clarify because there's a meme out there. One of the many, many ideas that people have about Bitcoin is that all the OG developers have just, like, 1,000,000,000 of dollars or whatever.
231
00:20:28.059 --> 00:20:28.559
And
232
00:20:29.260 --> 00:20:39.075
this is actually not true for a couple of reasons. And I'm obviously that's I have a very self serving motivation in saying this to everybody, but it is legitimately a a falsehood that,
233
00:20:39.935 --> 00:20:45.409
Bitcoin OGs all have tremendous piles of money. One reason is that they, like many people,
234
00:20:46.029 --> 00:20:53.784
after buying Bitcoin and seeing it go up 10 x, right, from 15¢ to a buck 50, just like fold it all and said like, all right, you know, I I can buy a car now.
235
00:20:54.485 --> 00:20:58.264
Another reason is though at the time, it seemed like a really experimental
236
00:20:58.644 --> 00:21:06.940
kind of sketchy system that was going to fall over any day, and it really did for a very long time, like, longer than than anyone would expect. I would say personally
237
00:21:07.644 --> 00:21:09.105
that it was maybe, like,
238
00:21:09.644 --> 00:21:10.784
2016 or 2017
239
00:21:11.085 --> 00:21:14.625
before I thought that maybe the system could could maybe keep a phone,
240
00:21:15.100 --> 00:21:24.000
that there wasn't going to be some break and shot to where, like, the mining incentives would turn out not to work or, you know, who knows? Maybe the crypto would be broken in some way or maybe just, like, network systems.
241
00:21:24.505 --> 00:21:27.645
Maybe it couldn't handle partitioning or maybe there'd be a fork or
242
00:21:29.225 --> 00:21:30.445
or whatever. And
243
00:21:31.280 --> 00:21:36.740
and so the people who are closest to the system really building it had a much clearer idea of the fragility of the system
244
00:21:37.040 --> 00:21:45.865
and the inherent fragility of cryptography of of how narrow a dance all of this code was doing to work with secret key data to do meaningful things.
245
00:21:46.280 --> 00:21:52.140
And so the people who were building the system and working on it the hardest were probably the most suspicious of it,
246
00:21:52.680 --> 00:21:55.895
beyond the people who would, like, look at it once and walk away, of course.
247
00:21:56.455 --> 00:21:59.975
And then finally, like, as a more general thing, it's good not to, to,
248
00:22:01.175 --> 00:22:08.690
to invest too heavily in something that your career already invests in. Right? We we learned that from Enron, but as a general thing. Right? That just your your personal
249
00:22:08.990 --> 00:22:11.490
what you're good at is a self, a form of investment.
250
00:22:12.115 --> 00:22:12.615
So
251
00:22:12.995 --> 00:22:14.135
by diverse the diversification
252
00:22:15.395 --> 00:22:28.290
mandates that you probably shouldn't have all your actual money is something that your career also depends on because that way, you know, you you while you have some protection against 1 or both of those sorry. You have some protection against one of those, not both going away.
253
00:22:28.695 --> 00:22:31.515
And, and if instead you put all your chips where
254
00:22:32.054 --> 00:22:32.534
where,
255
00:22:33.095 --> 00:22:36.715
where your employment prospects are, you know, that's that's a very risky thing to do.
256
00:22:37.210 --> 00:22:41.210
So, so for that reason, I mean, a few people did get very rich, and I'm not gonna say who,
257
00:22:41.530 --> 00:22:42.429
but, you know,
258
00:22:43.049 --> 00:22:51.924
a few people did. But for the most part, developers in the Bitcoin space were not able to just, like, buy 10,000 coins back when they were worth 50¢ and and have held on to them today.
259
00:22:52.225 --> 00:22:53.684
But what we were able to do
260
00:22:54.019 --> 00:22:57.799
is form an industry, a thriving industry with a lot of economic
261
00:22:58.179 --> 00:23:02.760
activity happening in it where it's possible as an open source developer
262
00:23:03.684 --> 00:23:09.865
to be well paid and well respected. And that's a very novel thing in the history of open source and in the history of development,
263
00:23:10.404 --> 00:23:19.059
and it's a very precious thing. Like and and I again, obviously, this is very self serving. It's precious that I get paid so much, isn't it? But what I mean is,
264
00:23:19.695 --> 00:23:27.430
historically, open source I guess, I I haven't I realized I haven't defined open source, but it's the idea that that you can publish code and anybody can show up and contribute
265
00:23:29.910 --> 00:23:30.570
266
00:23:31.270 --> 00:23:36.250
267
00:23:36.625 --> 00:23:42.485
If you want to contribute to it, if it's broken, you can fix it. You can submit changes. People will take it, and, you know, everybody can share.
268
00:23:42.865 --> 00:23:43.365
And,
269
00:23:44.130 --> 00:23:46.630
historically, there hasn't been any model to
270
00:23:48.370 --> 00:23:50.310
to make that sustainable economically
271
00:23:50.690 --> 00:23:57.325
other than charity, basically. So, for example, the Linux operating system for a long time, basically, like, IBM was paying a couple developers to do it.
272
00:23:57.865 --> 00:24:02.880
And now there are, you know, probably a couple dozen companies like IBM paying Linux kernel developers.
273
00:24:03.260 --> 00:24:13.445
But they're doing it because, you know, with 1 or 2 employees on, like, a, you know, 100000 person payroll. So So it's fine. It's not very much money, and their business does kinda depend on Linux continuing, but it's just sort of a
274
00:24:14.065 --> 00:24:15.045
charitable thing.
275
00:24:15.640 --> 00:24:28.295
And that works for Linux because Linux is huge and important, but it doesn't work for a lot of smaller projects that wind up being done by individuals in their spare time. So now it's personal charity. Right? It's people just doing a lot of these projects out of a labor of love,
276
00:24:28.835 --> 00:24:33.929
and it's very cool that for something like Bitcoin, which for a lot of us was a labor of love,
277
00:24:34.630 --> 00:24:36.070
we're able to be paid for that. And then,
278
00:24:37.429 --> 00:24:40.970
we're able to do it in a financially sustainable way. So
279
00:24:41.735 --> 00:24:42.315
so that's
280
00:24:42.695 --> 00:24:43.674
it's pretty cool.
281
00:24:44.695 --> 00:24:46.554
282
00:24:48.534 --> 00:24:50.780
You have 2 minutes left. It's 2
283
00:24:54.040 --> 00:24:54.620
284
00:24:59.655 --> 00:25:04.635
Cool. So I I think I'll seed my last 2 minutes, then if it's really 2 minutes. So thank you all for listening.
