April 21, 2022
Miles Suter, RockstarDev, and Lisa Neigut at Bitcoin Commons on March 18th 2022
I sat down with Miles Suter, Rockstardev, and Lisa Neigut on March 18th 2022 at the Bitcoin Takeover event held at Bitcoin Commons in Austin during SXSW to discuss lightning development and the three main lightning implementations: LND, CLN, and LDK.
Video: https://bitcointv.com/w/1jRpeX7VrQkzRcoqha6yso
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:10 - Development in Bitcoin being slow compared to the mantra of move fast and break things
00:21 - Building applications on top of Bitcoin in a permissionless way on the Lightning Network
02:23 - The multi-implementation approach in developing Lightning Network
WEBVTT
NOTE
Transcription provided by Podhome.fm
Created: 3/17/2024 4:25:23 PM
Duration: 1719.406
Channels: 1
1
00:00:10.455 --> 00:00:12.955
People will talk about how development in Bitcoin is slow,
2
00:00:13.495 --> 00:00:14.555
and that we,
3
00:00:15.410 --> 00:00:20.630
you know, it's it's really opposite to the mantra of move fast and bake break things, but it's also,
4
00:00:21.010 --> 00:00:21.510
permissionless.
5
00:00:21.890 --> 00:00:23.830
And and these three people
6
00:00:24.155 --> 00:00:29.295
are all building applications on top of Bitcoin in a permissionless way each on the Lightning Network. So,
7
00:00:29.595 --> 00:00:32.895
we've got Lisa Niget. Lisa is a c lightning protocol engineer
8
00:00:33.210 --> 00:00:34.030
at Blockstream.
9
00:00:34.730 --> 00:00:40.990
Before she was a back end engineer at Square or Block, formerly known as Square. And she's also,
10
00:00:41.690 --> 00:00:42.350
the chief
11
00:00:42.655 --> 00:00:44.915
explaining officer, I believe at
12
00:00:45.535 --> 00:00:50.595
the best education Bitcoin education company in the world called, base 58. And,
13
00:00:51.380 --> 00:00:57.540
Lisa is a graduate of the University of Texas here in Austin, and it's really special. Lisa's just down the road,
14
00:00:58.485 --> 00:01:06.505
in Houston. And, and thank you so much for, for coming up here to Austin to, to share what you're building on lightning today. We've got rockstar dev,
15
00:01:06.990 --> 00:01:08.530
otherwise known as uncle,
16
00:01:08.990 --> 00:01:10.049
to many of you,
17
00:01:10.829 --> 00:01:11.329
rockstar,
18
00:01:11.789 --> 00:01:14.530
in addition to being a core contributor to,
19
00:01:14.835 --> 00:01:17.015
BTC pay server, which is an open source,
20
00:01:17.635 --> 00:01:18.775
payments processor,
21
00:01:19.315 --> 00:01:24.115
is also the VP of engineering at strike. So Jack Mallers was up here before talking about,
22
00:01:24.820 --> 00:01:26.120
global monetary interoperability.
23
00:01:26.900 --> 00:01:33.400
Rockstar, we're talking about more, what they're actually, actively developing at strike and how they think about developing on top of lightning.
24
00:01:33.775 --> 00:01:35.475
And then we've also got Miles Suter,
25
00:01:36.015 --> 00:01:36.515
who
26
00:01:36.895 --> 00:01:45.679
is a product lead on the Bitcoin side at, the Cash App, which is a subsidiary of block or formerly known as Square. It's still just not,
27
00:01:45.979 --> 00:01:50.975
it's going to get there. Okay. It's going to get there. He's also a contributor, spiral BC BTC,
28
00:01:52.335 --> 00:01:52.835
and,
29
00:01:54.015 --> 00:01:54.915
cash app recently,
30
00:01:55.615 --> 00:01:56.115
launched,
31
00:01:56.735 --> 00:01:59.600
the ability for their users to access lightning. So,
32
00:02:00.880 --> 00:02:04.900
this will be, you know, a great talk about one of, one of the ways that,
33
00:02:05.600 --> 00:02:08.420
a lot of people are working to, to build and scale Bitcoin
34
00:02:08.825 --> 00:02:11.644
and help make it easier to move Bitcoin around the world.
35
00:02:12.025 --> 00:02:16.125
So with that, I'll bring you guys up and, and Matt O'Dell will lead the discussion.
36
00:02:23.040 --> 00:02:26.135
So one of our mics is gone. At least you wanna stay here.
37
00:02:27.095 --> 00:02:29.595
Matt. Oh, yeah. You over here. Matt, you're there.
38
00:02:31.095 --> 00:02:34.155
Mic. I should use that mic. Under his feet though. Is it mic?
39
00:02:39.390 --> 00:02:42.770
We good on mics? We're good on mics. We're good on mics? We're good on mics. We're good on mics? We're good on mics? We're good on mics? We're good on mics. Okay. Awesome. Yeah.
40
00:02:43.870 --> 00:02:44.370
So
41
00:02:44.905 --> 00:02:46.265
we're very fortunate to have,
42
00:02:48.425 --> 00:02:50.665
all these great people up here with us,
43
00:02:50.985 --> 00:02:53.485
today to talk about lightning and the future of lightning.
44
00:02:55.810 --> 00:02:58.210
What's really interesting, and Parker kind of,
45
00:02:58.930 --> 00:02:59.990
touched on it,
46
00:03:00.370 --> 00:03:00.870
is
47
00:03:01.625 --> 00:03:05.724
on when when when we're talking about Bitcoin, when we're talking about on chain Bitcoin, the protocol,
48
00:03:06.584 --> 00:03:09.084
right now it's dominated by a single implementation.
49
00:03:10.350 --> 00:03:11.330
But with lightning,
50
00:03:11.790 --> 00:03:20.835
we started with a multi implementation approach. And the idea is that you have multiple different teams that are working on lightning and that they're all cross compatible with each other.
51
00:03:21.295 --> 00:03:24.115
So we have Lisa here. She's working on sea lightning.
52
00:03:24.415 --> 00:03:26.410
We have rock star who,
53
00:03:27.030 --> 00:03:29.690
at strike they're building on, LND.
54
00:03:30.230 --> 00:03:32.330
And then we have miles at cash app,
55
00:03:32.870 --> 00:03:34.490
who they're working on LDK,
56
00:03:35.595 --> 00:03:36.095
which,
57
00:03:36.555 --> 00:03:43.695
their open source team, Spiral, is taking the lead on that, and they've integrated that into Cash App. So we have
58
00:03:45.120 --> 00:03:48.659
3 3 of the implementations. I think there what are there? 6 implementations
59
00:03:49.040 --> 00:03:49.540
now?
60
00:03:51.605 --> 00:03:58.025
It's always changing now. Yeah. Yeah. Maybe even less than that. Four major. Yeah. I would say. Majors. Yeah.
61
00:03:59.364 --> 00:03:59.864
So
62
00:04:00.830 --> 00:04:03.150
recently there's been a lot of drama with,
63
00:04:03.550 --> 00:04:05.250
cross implementation work.
64
00:04:05.550 --> 00:04:08.050
Are we going to talk about that or is that too juicy?
65
00:04:09.625 --> 00:04:17.005
How do you guys, how do you guys feel about that? Do you think like, is, is a multi implementation world of lightning actually going to
66
00:04:17.380 --> 00:04:27.855
come to fruition, or is it going to just be dominated by a single implementation? No. This is a question for Rockstar. Right? Let's jump right in. Well Let's go. Yeah. Yeah. Most disagreeable topic.
67
00:04:29.355 --> 00:04:36.070
My view, especially when it comes to lightning is, yeah, it's it's it's a good thing, man. It's a good thing especially because,
68
00:04:37.330 --> 00:04:38.470
when it comes to
69
00:04:39.330 --> 00:04:49.785
base blockchain and Bitcoin Core, you do not want a lot of disagreement. You want consensus. You want building slow. But when it comes to Lightning and what Lightning enables us,
70
00:04:50.725 --> 00:04:52.185
you want teams
71
00:04:52.630 --> 00:04:54.650
pushing the envelope, pushing the
72
00:04:55.030 --> 00:05:06.055
the spec, which is what you see now with Bolt 12 and lnurl. I mean, lnurl to me, I I'm a huge fan of Fiat Jeff, and, what he did with lnurl
73
00:05:06.675 --> 00:05:10.134
pushed the spec. Right? It opened up new use cases,
74
00:05:11.600 --> 00:05:12.580
new opportunities.
75
00:05:14.320 --> 00:05:22.795
You know, you can do things that you couldn't do before. So for me, the more implementations we have and the the more market
76
00:05:25.370 --> 00:05:29.710
gets to decide, yeah, what wins in the long term, like, I'm all for that. Yeah.
77
00:05:33.194 --> 00:05:35.854
Yeah. I, I tend to agree as well.
78
00:05:38.074 --> 00:05:45.160
I think that there you get different things out of, the different implementations. And when we started LBK, we really wanted to create
79
00:05:45.540 --> 00:05:48.680
an implementation that's much more modular, much more customizable,
80
00:05:49.585 --> 00:05:50.085
and,
81
00:05:50.545 --> 00:05:51.025
one that's
82
00:05:51.585 --> 00:06:08.245
doesn't have, like, a a a VC backed company behind it. So, I mean, I wish all the implementations well, and everybody's driving it forward in its own way. But we thought it was really important to have one that didn't have to, like, find a way to make money. It could just be sponsored for free
83
00:06:08.545 --> 00:06:11.185
at blocks. So that was kind of a core part,
84
00:06:12.705 --> 00:06:14.705
of why we kicked off,
85
00:06:15.105 --> 00:06:15.605
LDK
86
00:06:16.330 --> 00:06:20.990
and, also that it's written in Rust. It seems to be the hot thing on the streets these days.
87
00:06:22.170 --> 00:06:22.990
But, yeah,
88
00:06:23.415 --> 00:06:36.680
Cash App was the first implementation to use it, and it's still quite it's still quite new. We had Matt Corral flushing it out and filling out some of the gaps as we're building out our product and doing it kinda hand in hand, which was a really, really cool experience.
89
00:06:37.139 --> 00:06:37.879
We started
90
00:06:38.605 --> 00:06:40.225
Spiral, known as Square Crypto,
91
00:06:40.605 --> 00:06:43.265
over 2 years ago with no expectation of
92
00:06:43.725 --> 00:06:45.025
collaboration or,
93
00:06:46.180 --> 00:06:50.120
like, using them. The we spun it up just so they could benefit the entire ecosystem.
94
00:06:50.740 --> 00:06:56.405
But as we started to look into Lightning, as they were getting closer to being able to ship something to production,
95
00:06:56.785 --> 00:06:58.805
the timing really aligned nicely.
96
00:06:59.105 --> 00:07:00.805
And so just having that expertise
97
00:07:02.440 --> 00:07:05.900
and being able to lean on them and work as a team in the same Slack channel,
98
00:07:06.759 --> 00:07:09.340
theoretically in the same building if we weren't all remote,
99
00:07:10.345 --> 00:07:13.544
like, yeah, it was it was a really, really cool thing to see. And I think,
100
00:07:14.185 --> 00:07:17.085
that cross pollination is something we're really excited about at Ploc.
101
00:07:18.050 --> 00:07:22.630
Yeah. And as someone so I've been involved in the lightning spec process since late 2018,
102
00:07:23.250 --> 00:07:25.805
which is, like, starting to become a while now.
103
00:07:26.365 --> 00:07:30.865
I have to say that, like, having Matt Corallo and the rest of the spiral team become
104
00:07:31.324 --> 00:07:35.270
more involved in the spec process over the last couple of years has been a huge,
105
00:07:36.050 --> 00:07:42.550
benefit, I think, to the spec and to the things that we focus on adding and improving in the lightning network. So,
106
00:07:43.215 --> 00:07:45.715
I think, Matt, like, your your first,
107
00:07:46.495 --> 00:07:52.870
I think your question was, like, do the inner does it in our operation, does it work? And I think the reality is that, yeah, it does work.
108
00:07:53.250 --> 00:08:08.085
Right? There are, like, a couple different lightning implementations and they do all, for the most part, play well together. You can run them. You can open channels between them. And so, I think that, like, if you wanna just kinda, like, you know, draw between them. And so, I think that, like, if you wanna just kinda, like, you know, draw a line in the sand and say, did it work? Was it successful?
109
00:08:09.180 --> 00:08:15.340
I think, like, yes. I think it was very successful. And we have, like, a bunch of big companies now that are able to,
110
00:08:16.380 --> 00:08:17.280
that are sponsoring
111
00:08:18.134 --> 00:08:21.435
and really growing, I think, practices of engineers
112
00:08:21.974 --> 00:08:28.320
that have deep experience in exactly how lightning works and are, like, distributed. Right? They have different sources of funding.
113
00:08:28.940 --> 00:08:30.400
They kinda have different mandates
114
00:08:30.860 --> 00:08:31.680
as organizations
115
00:08:32.060 --> 00:08:33.600
around what they're focused on.
116
00:08:34.425 --> 00:08:44.440
Like, one thing that I feel like I've seen come out of the spiral team, especially through Matt's, like, leadership there is, a real focus on, like, what is the lightning experience look like on the mobile
117
00:08:44.740 --> 00:08:46.280
on mobile apps. Right? So,
118
00:08:46.820 --> 00:08:54.445
kinda like, what is the light client lightning experience and, like, the spiral team. And also to be fair, the ASIN, the Claire team, they're based out of France.
119
00:08:55.165 --> 00:08:57.505
They don't get as much representation in American,
120
00:08:58.285 --> 00:09:07.850
bit coin situations because they are located in Europe. But, they have also, along with Spiral, really been pushing forward the mobile use case and what we need to add to the protocol,
121
00:09:08.845 --> 00:09:15.600
across the board to make it more possible for mobile users to use. So yeah. I think there's, you know, I think it's a distributed protocol
122
00:09:23.355 --> 00:09:25.695
2 crypto project that exists in entire space.
123
00:09:26.475 --> 00:09:42.985
And it it is that, because we tried to do the spec process and we put a lot of time, energy, and effort across a bunch of different teams to, like, spin up different implementations, etcetera. So yeah. I I I think it's been a success so far. Yeah. I mean, I I apologize a little bit for just coming off swinging.
124
00:09:44.485 --> 00:09:48.985
Let's go. I'm kind of can you explain what that spec process looks like,
125
00:09:49.800 --> 00:10:01.935
Lisa? This is me. Yeah. Yes. I can explain what the process the process looks like. So the general idea so for those of you who aren't familiar with Spark processes, and I would assume most of us are not. I wasn't until I started working on Lightning.
126
00:10:02.315 --> 00:10:05.455
The whole idea between behind having a specification.
127
00:10:05.835 --> 00:10:12.560
So I like the way I like to describe it is there's, like, kind of, like, almost, like, tiers of, like, difficulty in open source software.
128
00:10:13.579 --> 00:10:24.865
Tier 1 is, like, you write some software, and then you open source it. So writing software and, like, having a working thing is really difficult, and shipping that is, like, I think its own level of, like, a difficult thing.
129
00:10:26.090 --> 00:10:34.464
Thing about a spec, I would say, is kinda one level more difficult. And that you're not just writing software, you're also writing a whole set of instructions
130
00:10:34.765 --> 00:10:35.825
about how to
131
00:10:36.365 --> 00:10:39.904
reimplement that software you just wrote. So it's, like, very detailed
132
00:10:40.820 --> 00:10:45.399
instructions about how to recreate the thing that you've just written and published.
133
00:10:45.779 --> 00:10:56.274
But you do it in a group setting, so it's not just you alone writing code. You talk to a bunch of others. So you write you can write, like, a you write the instructions kinda by yourself or whatever, but then you send it to a committee
134
00:10:56.654 --> 00:10:57.555
of other people.
135
00:10:57.940 --> 00:11:02.280
And you have to convince one of them to also go through these, like, written instructions
136
00:11:02.660 --> 00:11:07.000
and reimplement what you've done on their own, probably, in a different language,
137
00:11:07.824 --> 00:11:10.165
from the written instructions that you've written down.
138
00:11:10.625 --> 00:11:16.805
And then, you take the 2 different software open most, you know, these are all open source softwares, so it's multiple open source projects.
139
00:11:17.480 --> 00:11:20.300
You take these 2. You point them at each other, and, like, okay. Do they interoperate?
140
00:11:21.160 --> 00:11:26.154
And if it does work, then once that's happened, once both teams have successfully implemented
141
00:11:26.535 --> 00:11:36.130
this, like, written down from the written down description of the spec of, like, the process the software should follow, etcetera. Once you've got 2 teams in lightning, so there's, like, 4 implementations.
142
00:11:37.070 --> 00:11:49.355
The current process is once you have 2 teams that have implemented just, like, written down instruction set, the other side's verified, hey, it looks good. We've gone through bit of a review process both on the code as well as, like, the written instruction set. Right? Like, in English.
143
00:11:50.350 --> 00:12:05.805
At that point, we say, okay. This back is, like, considered part of the protocol. So it's like I would say it's, like, much more rigorous than just writing code and shipping it and getting building traction and getting users, etcetera. Like, you you have to do all that on top of this, but there's also this sort of rigorous,
144
00:12:06.580 --> 00:12:10.520
peer review, peer process that spec stuff for lightning goes through.
145
00:12:11.540 --> 00:12:13.080
Yeah. And, 4 implementations
146
00:12:13.860 --> 00:12:15.720
are l and d, c lightning,
147
00:12:16.165 --> 00:12:28.920
eclair, and then now LDK. Right? Right. Eclair was what we were talking about earlier, async. Yeah. Async. Yeah. Because for me, when we talk about specs, maybe that's where your first question comes in. They're like, are we at the point where
148
00:12:29.300 --> 00:12:37.545
the consensus on a spec level in advance is possible? And I I would say, yeah, we're getting there where it like like it won't be possible.
149
00:12:38.645 --> 00:12:39.145
But
150
00:12:39.765 --> 00:12:40.825
What does that mean?
151
00:12:41.180 --> 00:12:43.760
It means that you will start having
152
00:12:44.140 --> 00:12:48.240
features implemented that if they get mainstream adoptions,
153
00:12:48.620 --> 00:12:49.120
then
154
00:12:49.765 --> 00:12:50.505
other implementations
155
00:12:50.965 --> 00:12:51.705
will add
156
00:12:52.805 --> 00:12:56.425
it instead of first agreeing on spec and then implementing.
157
00:12:58.370 --> 00:12:59.750
So but but for me,
158
00:13:00.290 --> 00:13:02.550
that's a natural process that you see
159
00:13:03.970 --> 00:13:20.800
in in any anything that becomes popular. And lightning now I mean, there there were there was this meme, what, like, 2 years ago, lightning doesn't exist, whatnot. Like, lightning nowadays is not processing. Like, it it's getting to the point where it's, like, 100 of 1,000,000 of dollars are settled across lightning.
160
00:13:21.325 --> 00:13:22.945
Like it is in in production.
161
00:13:24.045 --> 00:13:24.865
So just
162
00:13:25.645 --> 00:13:26.785
the whole ecosystem,
163
00:13:27.085 --> 00:13:32.640
the product is maturing, and we are getting to that point where, like you had browser wars. So
164
00:13:33.020 --> 00:13:35.440
I don't think we'll have wars with different implementations,
165
00:13:35.900 --> 00:13:38.480
but I do see the system. Not yet at least. No.
166
00:13:39.625 --> 00:13:44.285
I see the system maturing, and then we will have other protocols. Like, I know now CoinJoin,
167
00:13:45.545 --> 00:13:51.980
CoinJoin is picking up those wars, but there is also, like, a coin pool protocol as a as a
168
00:13:52.680 --> 00:13:56.140
spec is out. It's a proposal. So to me, the more
169
00:13:57.115 --> 00:14:02.815
alternative layer 2 protocols we have, the the the better, and then some of the drama will move there. And,
170
00:14:03.195 --> 00:14:04.735
yeah, the system will mature.
171
00:14:05.830 --> 00:14:17.615
In addition to, like, spec, spec compatibility, I think I think there's an under kind of served area here in terms of product compatibility as well. Building on Bitcoin is hard just in and of itself. Building on lightning's
172
00:14:17.995 --> 00:14:19.615
even harder just because of the complexity,
173
00:14:20.555 --> 00:14:26.230
involved in the the safety like, the the need to be utmost secure throughout that whole process.
174
00:14:26.690 --> 00:14:34.335
That said, there's there's just basic wallet compatibility stuff for everybody building wallets right now that needs to get needs to get this act together. And, hopefully,
175
00:14:34.735 --> 00:14:36.355
I've I've put together a matrix
176
00:14:36.815 --> 00:14:41.315
of, like, which wallets can send to other wallets, who defaults to 0 amount invoices,
177
00:14:41.615 --> 00:14:54.425
who can't send to 0 amount invoices. And there's it's just a real big mess. And it feels like if all of us wallets could talk to each other and kinda get on the same page and work a little bit more in unison, that could add a lot more cohesion to the ecosystem.
178
00:14:54.805 --> 00:14:57.865
And so that's just kind of like a basic thing on a product level before
179
00:14:58.165 --> 00:14:59.845
diving into even some of these deeper,
180
00:15:00.245 --> 00:15:01.300
spec level things.
181
00:15:02.339 --> 00:15:06.360
Hey. Let's do it right now, man. What it is? Like, BIP 21 with lightning
182
00:15:06.820 --> 00:15:10.875
query string? Like I I'm all about BIP 21. So let's,
183
00:15:11.435 --> 00:15:16.255
more to come there. You wanna explain BIP 21 to the audience? So BIP 21 essentially
184
00:15:17.035 --> 00:15:18.569
lets you create it.
185
00:15:19.190 --> 00:15:21.910
You can have a one shared QR code with,
186
00:15:22.310 --> 00:15:28.275
combining an on chain and a lightning invoice. Essentially, it looks like a lightning invoice, but it has a fallback to an on chain,
187
00:15:29.055 --> 00:15:32.595
wall address in there. I think that moving towards the standard,
188
00:15:33.615 --> 00:15:35.715
will do a lot for just, like, increasing,
189
00:15:36.960 --> 00:16:01.270
user adoption and making normies not have to think, like, am I sending on chain? Am I sending on lightning? Is lightning bitcoin? Like, what the hell is even going on here? And so if you have one QR code, if I scan with a lightning only wallet okay. Cool. I'll I'll take the fastest cheapest option. I'll use lightning. If I scan with a on chain only wallet, okay, I don't recognize that that lightning QR code, I'll fall back on that on chain address, send it on chain.
190
00:16:02.530 --> 00:16:05.665
And so in your bank account, you might
191
00:16:06.125 --> 00:16:20.585
it's like your debit account. You might move funds in there via a variety of different ways. And you don't really care. Like, is this an ACH? Is this, like, over the wire? You just see money in, money out. And I think as a community, I think the north star we should be working towards
192
00:16:21.365 --> 00:16:23.145
is, just moving Bitcoin.
193
00:16:23.524 --> 00:16:28.760
And, hopefully, as we scale and as we get more users, we're using the faster, cheaper, more efficient layers.
194
00:16:29.220 --> 00:16:35.240
But if we're going to onboard a 1,000,000,000 people, I think we need to make it really simpler like, much, much simpler. And, ultimately,
195
00:16:35.694 --> 00:16:42.355
hope hopefully, in due time, I think, we can abstract away, like, the need to call out Lightning at all. It's just moving Bitcoin.
196
00:16:44.829 --> 00:16:58.470
Yeah. Because I did bit 21 with Lightning inquiry string and BTC based server. Like, I coded that. But I know, Lisa, if we are agreeing here, then I need to get that in strike. You know? So what's your opinion on that one?
197
00:16:58.790 --> 00:17:02.170
I'm a be honest. This is the first time hearing about BIP 21
198
00:17:02.949 --> 00:17:04.890
With lightning. With lightning. Yes.
199
00:17:05.975 --> 00:17:12.475
My understanding is that lightning invoices, you can add a fallback address on chain. So sounds like I mean,
200
00:17:12.909 --> 00:17:16.289
from my knowledge of the current invoicing system on lightning,
201
00:17:17.149 --> 00:17:33.590
seems like we're probably running to an issue there where existing Bitcoin wallets can't parse lightning invoices is a problem. Right? So the data that you want is that use case was considered when they wrote the lightning spec. But the problem is that the wallet implementers
202
00:17:34.770 --> 00:17:42.155
do not offer a way to parse that data, so they have invented another spec called BIP 20 1 that they were getting
203
00:17:42.615 --> 00:17:46.235
wallet people to implement. BIP 21 is is like the oldest
204
00:17:46.540 --> 00:17:58.865
standard, then it's backwards compatible. But it's what you're saying is when, bolt bolt 11 was done, there was fallback address for on chain address. Mhmm. Like, this is the other way way around, and it's, like, the most backwards compatible.
205
00:17:59.565 --> 00:18:00.065
So
206
00:18:01.085 --> 00:18:06.065
there is this now conversation, like, okay. What is unified QR code? And are we
207
00:18:06.710 --> 00:18:15.370
in agreement on feature set that it offers? Because when when we are talking about bolt 12 now, there is, like, a refund option and so on and so forth.
208
00:18:16.435 --> 00:18:20.215
So I don't know. I need to see if I'm going with Miles, bit 21
209
00:18:20.595 --> 00:18:30.990
lightning, or I'm going full back. Yes. It's I mean, obviously, there's gotta be a lot of community discussion here and make sure all the wallets are compatible. My understanding is that there's a number of, like, Coinbase
210
00:18:31.655 --> 00:18:32.795
withdrawing from Coinbase
211
00:18:33.095 --> 00:18:35.995
to a unified QR code will will break because
212
00:18:36.295 --> 00:18:39.515
they haven't implemented that correctly. But it should just be a small
213
00:18:39.910 --> 00:18:41.430
small change for a lot of these,
214
00:18:41.910 --> 00:19:01.700
consumer wallets to get bit 21 working properly. Does Coinbase support withdrawal with Lightning? No. Okay. No. I see. I see. Okay. So there's, like, no chance that they would understand, like, the bolt 11 thing either. It's interesting. I mean, I think I think what you guys are highlighting is that I think there's a lot of work still to be done in the wallet space. I don't think
215
00:19:02.400 --> 00:19:05.475
I don't think that, like, as an industry, we've quite figured out exactly
216
00:19:12.595 --> 00:19:18.540
Like, some of the most exciting stuff yet to be built is, like, this, like, interop and, like, getting the experience exactly
217
00:19:18.920 --> 00:19:20.780
hammered out at the wallet level. And,
218
00:19:21.575 --> 00:19:38.145
I think, you know, I work on the spec layer, which is just some extent, like, a few layers beneath the wallet stuff. And I think having a lack of, like, a centralized, like, at least forum for specs on all that stuff, I think you can definitely tell through kind of all the, I wouldn't call it confusion, but,
219
00:19:39.105 --> 00:19:43.525
all of the competing, like, specs little, like, suggestions of how to move forward.
220
00:19:44.510 --> 00:19:50.770
The fact that there's not, like, a consortium kinda like a consortium might be I don't know if that's a good word or a bad word.
221
00:19:51.150 --> 00:20:06.570
But, like, you know, at least, like, the wind lightning started as a protocol. Like, there were we were everyone was there together writing the spec together and agreed that that's what they were working towards as a group. Whereas, I think on the wallet side, there hasn't been kinda that, like, cohesive
222
00:20:07.445 --> 00:20:09.385
clarity of, like, exactly what
223
00:20:09.765 --> 00:20:14.184
it should look like. Does that make sense? And, like, you're trying to figure that out. I don't think anyone has, like, the right answer.
224
00:20:14.725 --> 00:20:26.965
But it is a little bit like that x kcd thing where you had a problem with, like, the previous specs. You made a new one. So there were 14 ways to do it. Now there's, like, 15 sort of thing. And I I do think we see that happening a lot on the wallet side.
225
00:20:27.445 --> 00:20:35.784
Yeah. That's that's why I'm thankful to people like Parker who organized these events to get these conversations started because while we are transferring
226
00:20:36.159 --> 00:20:40.500
100 of 1,000,000 of dollars across Lightning, there is still work to be done. So
227
00:20:42.559 --> 00:20:54.125
I do wanna I I was talking about how hard it was to work on lightning a second ago, but I do wanna just, like, give a huge shout out to everybody working on this, especially Jeff from spiral. I just saw you over there. I didn't mean to leave you earlier.
228
00:20:55.040 --> 00:21:05.345
But, like, 2 I remember 2 or 3 years ago at this point maybe, we're doing the lightning torch and trying to, like, stand up a node and get it all to work. And, man, it was just, like, show
229
00:21:05.985 --> 00:21:09.685
liquidity? Yeah. It's, like, what what is inbound liquidity? Are you kidding me?
230
00:21:10.065 --> 00:21:10.725
And so
231
00:21:11.105 --> 00:21:13.765
seeing the slow but but steady progress
232
00:21:14.290 --> 00:21:15.110
and seeing this
233
00:21:15.970 --> 00:21:19.910
starting at the start of 2021, I think, but really progressing even more recently,
234
00:21:20.530 --> 00:21:23.190
it's just gotten so much more usable, so much more reliable,
235
00:21:23.755 --> 00:21:31.295
and it's a big testament to all the people working super hard on it. I remember I was sending a payment to Miles, and I guess it was early 2019,
236
00:21:31.950 --> 00:21:46.754
and we were trying to figure out lightning. And I sent him the 1st payment. It didn't work. Then we, like, did some channel management stuff, and then I sent him the 2nd payment. It worked. We're like, yes, we got it. Then I went to send them the 3rd payment and we ran out of liquidity and it didn't work. We're like, what the hell is going on here?
237
00:21:47.934 --> 00:21:49.875
It does feel like it's been a long time.
238
00:21:50.600 --> 00:21:50.919
And,
239
00:21:51.480 --> 00:21:53.820
and the whole space has, has moved forward tremendously.
240
00:21:55.159 --> 00:22:05.325
So I mean, with the bib 21 thing specifically, since it just got brought up, I mean, at the end of the day, you're talking about the wallets on the receiving side, being able to display this new QR code,
241
00:22:05.945 --> 00:22:14.540
but it can also be solved on the opposite side with the sender. I mean, we see a moon wallet with 2 use taking the initiative there. I mean, you scan either side and it works
242
00:22:14.920 --> 00:22:15.900
at what point,
243
00:22:16.335 --> 00:22:21.155
at what point does it just become tech debt to say, like, I need to support copay wallet
244
00:22:21.615 --> 00:22:27.720
or, you know, some wallet that no one's used in 5 years because know, it doesn't know what a lightning invoices.
245
00:22:28.500 --> 00:22:35.080
Is that, like, is that an actual thing that Bitcoiners should be thinking about? Or are we are we supposed to support, you know, every
246
00:22:36.125 --> 00:22:37.825
every wallet under the sun?
247
00:22:39.645 --> 00:22:42.705
Whenever co pay is mentioned, like, I I, like,
248
00:22:43.560 --> 00:22:50.700
congrats to BitPay for for taking, like, the wallet that was most advanced and running it into ground. Like, what is it? 0 innovation.
249
00:22:51.320 --> 00:22:51.820
Yeah.
250
00:22:53.075 --> 00:22:55.815
I think it will be a natural process.
251
00:22:56.115 --> 00:22:56.934
Like, it's
252
00:22:57.955 --> 00:23:00.455
you can only plan so much in advance,
253
00:23:00.820 --> 00:23:01.320
and
254
00:23:01.860 --> 00:23:03.880
that's what I what Lisa was saying.
255
00:23:05.300 --> 00:23:10.520
Whole lightning spec, the the work done there was amazing. It was like all all the,
256
00:23:10.885 --> 00:23:11.545
you know,
257
00:23:12.565 --> 00:23:15.225
what it what what does Bolt stand for? It's like improvement.
258
00:23:16.885 --> 00:23:20.505
Base is a lightning technology. Base is a lightning. There we go.
259
00:23:20.889 --> 00:23:28.269
And Now we got the basics down. Yeah. Basics. No. You need to get it out. Listen, man. I'm VP of engineering now. I'm not into small details.
260
00:23:28.649 --> 00:23:29.549
But it's like
261
00:23:30.585 --> 00:23:42.020
all those improvements, like, they were agreed upon, and then it was like hard work of implementing it. And now we are there. I don't expect that we are going to have another chance to, like, all, like, duke it out. But
262
00:23:42.320 --> 00:23:48.605
that shouldn't we shouldn't look at that as a big problem. It's just okay. Let it go and grow organically and
263
00:23:50.025 --> 00:23:50.845
let it happen.
264
00:23:52.730 --> 00:23:56.270
Yeah. I think there's oh, man. I forgot what I was gonna say. Sorry.
265
00:23:57.210 --> 00:23:58.750
No. I I got you with Bolt.
266
00:24:00.615 --> 00:24:11.429
So correct me if I'm wrong, but on the Bolt 21 piece, I believe it's, like, every wallet should support this. Just some don't. And it's a very quick, easy change to support it. But as you're saying, it's,
267
00:24:11.809 --> 00:24:19.554
like, the most the most possible backwards compatible. Is Bip 21 the one that Bipay was trying to push forward? They got a bunch of
268
00:24:19.895 --> 00:24:20.955
oh, that was 70?
269
00:24:21.975 --> 00:24:23.035
70. 71. Right?
270
00:24:25.370 --> 00:24:37.605
Oh, so sorry. I remember what I wanted to say. The yeah. So, I mean, I think I think going back to, like, spec process in the bit 21 conversation and, like, clearly, this bit thing, bit 21 is a massive improvement to user experience
271
00:24:37.905 --> 00:24:42.005
and that, like, Miles was saying, it sort of helps abstract away, like, the,
272
00:24:42.850 --> 00:24:49.110
implementation details of how you're moving Bitcoin around, which I think is definitely, like, a very worthy goal to get to from a user perspective.
273
00:24:49.890 --> 00:24:51.885
But, you know, like, all of these processes,
274
00:24:52.425 --> 00:24:55.165
like, every spec is only as good as, like, the participation
275
00:24:55.545 --> 00:25:12.995
you get into it. Right? And so, I mean, that's good for lightning as well. Like, we really need, like, everyone who's who wants to adhere to the the spec process. Like, we need you need, like, everyone, like, in the community participating. Right? So there's, like, a little bit of, like, you know, people have to, like, opt in to participation.
276
00:25:13.295 --> 00:25:25.350
And when people stop participating in the process for whatever reason, maybe they're busy. Maybe they've got, like, you know, business reasons. They're, like, more pressing, like, material concerns of where they're spending their dev time, etcetera.
277
00:25:25.765 --> 00:25:29.945
Maybe they've got some competing reason why they don't wanna make it happen, whatever. But,
278
00:25:30.565 --> 00:25:36.670
you know, really, it's like everyone chipping in and participating and get excited about, like, the possibility of interoperation
279
00:25:37.130 --> 00:25:41.070
that really moves, like, all this, like, entire, you know, network forward.
280
00:25:42.115 --> 00:25:45.255
Yeah. And I I always now when I'm speaking, I say to
281
00:25:45.635 --> 00:25:55.550
prospective developers that want to get more involved. Like, maybe it's what Lisa is saying, this problem, that problem, but maybe you are already doing good work and it's just not
282
00:25:56.090 --> 00:25:59.525
publicized well enough. So if there are such people in audience,
283
00:25:59.905 --> 00:26:01.605
yeah, talking about you, man,
284
00:26:01.905 --> 00:26:02.405
like,
285
00:26:02.865 --> 00:26:09.050
reach out after this talk and let let's see how to work together because, yeah, this is open source. Let's, yeah, let's collaborate.
286
00:26:09.590 --> 00:26:14.330
And and I wanna extend the invitation far beyond just engineers as well. A lot of this
287
00:26:15.905 --> 00:26:20.725
envisioned ideal user experience discussion is happening in the Bitcoin design community.
288
00:26:21.345 --> 00:26:33.190
And, like, we if you're a designer, hop on in there and share your input. If you're just a normal user, hop on in there and share your input and help us kinda come to consensus. You don't have to be an engineer to have an opinion.
289
00:26:34.164 --> 00:26:36.825
There's all sorts of stakeholders in this environment,
290
00:26:37.684 --> 00:26:40.664
and certain people have strengths in certain areas.
291
00:26:41.100 --> 00:26:43.360
These these 2 are deep in the engineering scene.
292
00:26:44.139 --> 00:26:44.639
I
293
00:26:45.980 --> 00:26:49.679
I don't know what my strengths are exactly, but, compared to them. But,
294
00:26:50.605 --> 00:27:00.510
but, like, there's a there's a million ways to contribute. And maybe you're just maybe you just send the 100 lightning payments every day. But as a result of that, you know all the wallets, you know where the incompatibilities
295
00:27:00.810 --> 00:27:09.304
are, and you can help drive something forward that maybe then that somebody else picks up and, ultimately gets all the different wallets and the different implementations
296
00:27:09.605 --> 00:27:13.065
aligned and just build a a much better global lightning experience.
297
00:27:14.005 --> 00:27:20.730
I I mean, this has been a great conversation, guys. We're almost out of time. I figure we'll wrap up with final thoughts. Rockstar, final thoughts.
298
00:27:23.695 --> 00:27:27.715
Just glad to be with all of you here and that we're, you know,
299
00:27:28.335 --> 00:27:35.990
participating in building history. Like, when we look back on this event in a year or 2, it will be like it happened here. Some,
300
00:27:37.250 --> 00:27:39.909
agreements were made here. Somewhat had a
301
00:27:40.210 --> 00:27:40.710
moment.
302
00:27:41.644 --> 00:27:45.585
So just looking forward to this journey with you. Let's go. Marty,
303
00:27:46.044 --> 00:27:49.300
we will win. Thanks, rock star. Lisa, final thoughts.
304
00:27:49.700 --> 00:27:58.520
Okay. So I think Lightning is awesome. I think Lightning has a lot of potential to really prove itself as being, like, the true heart of the Web 3 movement in terms of decentralization
305
00:27:59.285 --> 00:28:00.505
and, like, self sovereignty.
306
00:28:01.045 --> 00:28:20.255
And I'm really excited about it. Also gonna take 2 seconds to show the fact that base 58, my Bitcoin transaction protocol class, just open registration for our next class. So if you are really interested in finding out more, getting involved in how the Bitcoin protocol works, we do a 6 weeks class, and we'd really love to have you in our class. So check out our website at base58.info.
307
00:28:21.434 --> 00:28:24.495
Thanks, Lisa. Really appreciate your work with Base 58.
308
00:28:25.200 --> 00:28:28.340
Miles, final thoughts. Prometheans versus Malthusians.
309
00:28:28.880 --> 00:28:29.780
Don't forget it.
310
00:28:30.160 --> 00:28:30.980
Thanks, guys.
NOTE
Transcription provided by Podhome.fm
Created: 3/17/2024 4:25:23 PM
Duration: 1719.406
Channels: 1
1
00:00:10.455 --> 00:00:12.955
2
00:00:13.495 --> 00:00:14.555
and that we,
3
00:00:15.410 --> 00:00:20.630
you know, it's it's really opposite to the mantra of move fast and bake break things, but it's also,
4
00:00:21.010 --> 00:00:21.510
permissionless.
5
00:00:21.890 --> 00:00:23.830
And and these three people
6
00:00:24.155 --> 00:00:29.295
are all building applications on top of Bitcoin in a permissionless way each on the Lightning Network. So,
7
00:00:29.595 --> 00:00:32.895
we've got Lisa Niget. Lisa is a c lightning protocol engineer
8
00:00:33.210 --> 00:00:34.030
at Blockstream.
9
00:00:34.730 --> 00:00:40.990
Before she was a back end engineer at Square or Block, formerly known as Square. And she's also,
10
00:00:41.690 --> 00:00:42.350
the chief
11
00:00:42.655 --> 00:00:44.915
explaining officer, I believe at
12
00:00:45.535 --> 00:00:50.595
the best education Bitcoin education company in the world called, base 58. And,
13
00:00:51.380 --> 00:00:57.540
Lisa is a graduate of the University of Texas here in Austin, and it's really special. Lisa's just down the road,
14
00:00:58.485 --> 00:01:06.505
in Houston. And, and thank you so much for, for coming up here to Austin to, to share what you're building on lightning today. We've got rockstar dev,
15
00:01:06.990 --> 00:01:08.530
otherwise known as uncle,
16
00:01:08.990 --> 00:01:10.049
to many of you,
17
00:01:10.829 --> 00:01:11.329
rockstar,
18
00:01:11.789 --> 00:01:14.530
in addition to being a core contributor to,
19
00:01:14.835 --> 00:01:17.015
BTC pay server, which is an open source,
20
00:01:17.635 --> 00:01:18.775
payments processor,
21
00:01:19.315 --> 00:01:24.115
is also the VP of engineering at strike. So Jack Mallers was up here before talking about,
22
00:01:24.820 --> 00:01:26.120
global monetary interoperability.
23
00:01:26.900 --> 00:01:33.400
Rockstar, we're talking about more, what they're actually, actively developing at strike and how they think about developing on top of lightning.
24
00:01:33.775 --> 00:01:35.475
And then we've also got Miles Suter,
25
00:01:36.015 --> 00:01:36.515
who
26
00:01:36.895 --> 00:01:45.679
is a product lead on the Bitcoin side at, the Cash App, which is a subsidiary of block or formerly known as Square. It's still just not,
27
00:01:45.979 --> 00:01:50.975
it's going to get there. Okay. It's going to get there. He's also a contributor, spiral BC BTC,
28
00:01:52.335 --> 00:01:52.835
and,
29
00:01:54.015 --> 00:01:54.915
cash app recently,
30
00:01:55.615 --> 00:01:56.115
launched,
31
00:01:56.735 --> 00:01:59.600
the ability for their users to access lightning. So,
32
00:02:00.880 --> 00:02:04.900
this will be, you know, a great talk about one of, one of the ways that,
33
00:02:05.600 --> 00:02:08.420
a lot of people are working to, to build and scale Bitcoin
34
00:02:08.825 --> 00:02:11.644
and help make it easier to move Bitcoin around the world.
35
00:02:12.025 --> 00:02:16.125
So with that, I'll bring you guys up and, and Matt O'Dell will lead the discussion.
36
00:02:23.040 --> 00:02:26.135
So one of our mics is gone. At least you wanna stay here.
37
00:02:27.095 --> 00:02:29.595
Matt. Oh, yeah. You over here. Matt, you're there.
38
00:02:31.095 --> 00:02:34.155
39
00:02:39.390 --> 00:02:42.770
40
00:02:43.870 --> 00:02:44.370
So
41
00:02:44.905 --> 00:02:46.265
we're very fortunate to have,
42
00:02:48.425 --> 00:02:50.665
all these great people up here with us,
43
00:02:50.985 --> 00:02:53.485
today to talk about lightning and the future of lightning.
44
00:02:55.810 --> 00:02:58.210
What's really interesting, and Parker kind of,
45
00:02:58.930 --> 00:02:59.990
touched on it,
46
00:03:00.370 --> 00:03:00.870
is
47
00:03:01.625 --> 00:03:05.724
on when when when we're talking about Bitcoin, when we're talking about on chain Bitcoin, the protocol,
48
00:03:06.584 --> 00:03:09.084
right now it's dominated by a single implementation.
49
00:03:10.350 --> 00:03:11.330
But with lightning,
50
00:03:11.790 --> 00:03:20.835
we started with a multi implementation approach. And the idea is that you have multiple different teams that are working on lightning and that they're all cross compatible with each other.
51
00:03:21.295 --> 00:03:24.115
So we have Lisa here. She's working on sea lightning.
52
00:03:24.415 --> 00:03:26.410
We have rock star who,
53
00:03:27.030 --> 00:03:29.690
at strike they're building on, LND.
54
00:03:30.230 --> 00:03:32.330
And then we have miles at cash app,
55
00:03:32.870 --> 00:03:34.490
who they're working on LDK,
56
00:03:35.595 --> 00:03:36.095
which,
57
00:03:36.555 --> 00:03:43.695
their open source team, Spiral, is taking the lead on that, and they've integrated that into Cash App. So we have
58
00:03:45.120 --> 00:03:48.659
3 3 of the implementations. I think there what are there? 6 implementations
59
00:03:49.040 --> 00:03:49.540
now?
60
00:03:51.605 --> 00:03:58.025
61
00:03:59.364 --> 00:03:59.864
62
00:04:00.830 --> 00:04:03.150
recently there's been a lot of drama with,
63
00:04:03.550 --> 00:04:05.250
cross implementation work.
64
00:04:05.550 --> 00:04:08.050
Are we going to talk about that or is that too juicy?
65
00:04:09.625 --> 00:04:17.005
How do you guys, how do you guys feel about that? Do you think like, is, is a multi implementation world of lightning actually going to
66
00:04:17.380 --> 00:04:27.855
come to fruition, or is it going to just be dominated by a single implementation? No. This is a question for Rockstar. Right? Let's jump right in. Well Let's go. Yeah. Yeah. Most disagreeable topic.
67
00:04:29.355 --> 00:04:36.070
68
00:04:37.330 --> 00:04:38.470
when it comes to
69
00:04:39.330 --> 00:04:49.785
base blockchain and Bitcoin Core, you do not want a lot of disagreement. You want consensus. You want building slow. But when it comes to Lightning and what Lightning enables us,
70
00:04:50.725 --> 00:04:52.185
you want teams
71
00:04:52.630 --> 00:04:54.650
pushing the envelope, pushing the
72
00:04:55.030 --> 00:05:06.055
the spec, which is what you see now with Bolt 12 and lnurl. I mean, lnurl to me, I I'm a huge fan of Fiat Jeff, and, what he did with lnurl
73
00:05:06.675 --> 00:05:10.134
pushed the spec. Right? It opened up new use cases,
74
00:05:11.600 --> 00:05:12.580
new opportunities.
75
00:05:14.320 --> 00:05:22.795
You know, you can do things that you couldn't do before. So for me, the more implementations we have and the the more market
76
00:05:25.370 --> 00:05:29.710
gets to decide, yeah, what wins in the long term, like, I'm all for that. Yeah.
77
00:05:33.194 --> 00:05:35.854
78
00:05:38.074 --> 00:05:45.160
I think that there you get different things out of, the different implementations. And when we started LBK, we really wanted to create
79
00:05:45.540 --> 00:05:48.680
an implementation that's much more modular, much more customizable,
80
00:05:49.585 --> 00:05:50.085
and,
81
00:05:50.545 --> 00:05:51.025
one that's
82
00:05:51.585 --> 00:06:08.245
doesn't have, like, a a a VC backed company behind it. So, I mean, I wish all the implementations well, and everybody's driving it forward in its own way. But we thought it was really important to have one that didn't have to, like, find a way to make money. It could just be sponsored for free
83
00:06:08.545 --> 00:06:11.185
at blocks. So that was kind of a core part,
84
00:06:12.705 --> 00:06:14.705
of why we kicked off,
85
00:06:15.105 --> 00:06:15.605
LDK
86
00:06:16.330 --> 00:06:20.990
and, also that it's written in Rust. It seems to be the hot thing on the streets these days.
87
00:06:22.170 --> 00:06:22.990
But, yeah,
88
00:06:23.415 --> 00:06:36.680
Cash App was the first implementation to use it, and it's still quite it's still quite new. We had Matt Corral flushing it out and filling out some of the gaps as we're building out our product and doing it kinda hand in hand, which was a really, really cool experience.
89
00:06:37.139 --> 00:06:37.879
We started
90
00:06:38.605 --> 00:06:40.225
Spiral, known as Square Crypto,
91
00:06:40.605 --> 00:06:43.265
over 2 years ago with no expectation of
92
00:06:43.725 --> 00:06:45.025
collaboration or,
93
00:06:46.180 --> 00:06:50.120
like, using them. The we spun it up just so they could benefit the entire ecosystem.
94
00:06:50.740 --> 00:06:56.405
But as we started to look into Lightning, as they were getting closer to being able to ship something to production,
95
00:06:56.785 --> 00:06:58.805
the timing really aligned nicely.
96
00:06:59.105 --> 00:07:00.805
And so just having that expertise
97
00:07:02.440 --> 00:07:05.900
and being able to lean on them and work as a team in the same Slack channel,
98
00:07:06.759 --> 00:07:09.340
theoretically in the same building if we weren't all remote,
99
00:07:10.345 --> 00:07:13.544
like, yeah, it was it was a really, really cool thing to see. And I think,
100
00:07:14.185 --> 00:07:17.085
that cross pollination is something we're really excited about at Ploc.
101
00:07:18.050 --> 00:07:22.630
102
00:07:23.250 --> 00:07:25.805
which is, like, starting to become a while now.
103
00:07:26.365 --> 00:07:30.865
I have to say that, like, having Matt Corallo and the rest of the spiral team become
104
00:07:31.324 --> 00:07:35.270
more involved in the spec process over the last couple of years has been a huge,
105
00:07:36.050 --> 00:07:42.550
benefit, I think, to the spec and to the things that we focus on adding and improving in the lightning network. So,
106
00:07:43.215 --> 00:07:45.715
I think, Matt, like, your your first,
107
00:07:46.495 --> 00:07:52.870
I think your question was, like, do the inner does it in our operation, does it work? And I think the reality is that, yeah, it does work.
108
00:07:53.250 --> 00:08:08.085
Right? There are, like, a couple different lightning implementations and they do all, for the most part, play well together. You can run them. You can open channels between them. And so, I think that, like, if you wanna just kinda, like, you know, draw between them. And so, I think that, like, if you wanna just kinda, like, you know, draw a line in the sand and say, did it work? Was it successful?
109
00:08:09.180 --> 00:08:15.340
I think, like, yes. I think it was very successful. And we have, like, a bunch of big companies now that are able to,
110
00:08:16.380 --> 00:08:17.280
that are sponsoring
111
00:08:18.134 --> 00:08:21.435
and really growing, I think, practices of engineers
112
00:08:21.974 --> 00:08:28.320
that have deep experience in exactly how lightning works and are, like, distributed. Right? They have different sources of funding.
113
00:08:28.940 --> 00:08:30.400
They kinda have different mandates
114
00:08:30.860 --> 00:08:31.680
as organizations
115
00:08:32.060 --> 00:08:33.600
around what they're focused on.
116
00:08:34.425 --> 00:08:44.440
Like, one thing that I feel like I've seen come out of the spiral team, especially through Matt's, like, leadership there is, a real focus on, like, what is the lightning experience look like on the mobile
117
00:08:44.740 --> 00:08:46.280
on mobile apps. Right? So,
118
00:08:46.820 --> 00:08:54.445
kinda like, what is the light client lightning experience and, like, the spiral team. And also to be fair, the ASIN, the Claire team, they're based out of France.
119
00:08:55.165 --> 00:08:57.505
They don't get as much representation in American,
120
00:08:58.285 --> 00:09:07.850
bit coin situations because they are located in Europe. But, they have also, along with Spiral, really been pushing forward the mobile use case and what we need to add to the protocol,
121
00:09:08.845 --> 00:09:15.600
across the board to make it more possible for mobile users to use. So yeah. I think there's, you know, I think it's a distributed protocol
122
00:09:23.355 --> 00:09:25.695
2 crypto project that exists in entire space.
123
00:09:26.475 --> 00:09:42.985
And it it is that, because we tried to do the spec process and we put a lot of time, energy, and effort across a bunch of different teams to, like, spin up different implementations, etcetera. So yeah. I I I think it's been a success so far. Yeah. I mean, I I apologize a little bit for just coming off swinging.
124
00:09:44.485 --> 00:09:48.985
125
00:09:49.800 --> 00:10:01.935
126
00:10:02.315 --> 00:10:05.455
The whole idea between behind having a specification.
127
00:10:05.835 --> 00:10:12.560
So I like the way I like to describe it is there's, like, kind of, like, almost, like, tiers of, like, difficulty in open source software.
128
00:10:13.579 --> 00:10:24.865
Tier 1 is, like, you write some software, and then you open source it. So writing software and, like, having a working thing is really difficult, and shipping that is, like, I think its own level of, like, a difficult thing.
129
00:10:26.090 --> 00:10:34.464
Thing about a spec, I would say, is kinda one level more difficult. And that you're not just writing software, you're also writing a whole set of instructions
130
00:10:34.765 --> 00:10:35.825
about how to
131
00:10:36.365 --> 00:10:39.904
reimplement that software you just wrote. So it's, like, very detailed
132
00:10:40.820 --> 00:10:45.399
instructions about how to recreate the thing that you've just written and published.
133
00:10:45.779 --> 00:10:56.274
But you do it in a group setting, so it's not just you alone writing code. You talk to a bunch of others. So you write you can write, like, a you write the instructions kinda by yourself or whatever, but then you send it to a committee
134
00:10:56.654 --> 00:10:57.555
of other people.
135
00:10:57.940 --> 00:11:02.280
And you have to convince one of them to also go through these, like, written instructions
136
00:11:02.660 --> 00:11:07.000
and reimplement what you've done on their own, probably, in a different language,
137
00:11:07.824 --> 00:11:10.165
from the written instructions that you've written down.
138
00:11:10.625 --> 00:11:16.805
And then, you take the 2 different software open most, you know, these are all open source softwares, so it's multiple open source projects.
139
00:11:17.480 --> 00:11:20.300
You take these 2. You point them at each other, and, like, okay. Do they interoperate?
140
00:11:21.160 --> 00:11:26.154
And if it does work, then once that's happened, once both teams have successfully implemented
141
00:11:26.535 --> 00:11:36.130
this, like, written down from the written down description of the spec of, like, the process the software should follow, etcetera. Once you've got 2 teams in lightning, so there's, like, 4 implementations.
142
00:11:37.070 --> 00:11:49.355
The current process is once you have 2 teams that have implemented just, like, written down instruction set, the other side's verified, hey, it looks good. We've gone through bit of a review process both on the code as well as, like, the written instruction set. Right? Like, in English.
143
00:11:50.350 --> 00:12:05.805
At that point, we say, okay. This back is, like, considered part of the protocol. So it's like I would say it's, like, much more rigorous than just writing code and shipping it and getting building traction and getting users, etcetera. Like, you you have to do all that on top of this, but there's also this sort of rigorous,
144
00:12:06.580 --> 00:12:10.520
peer review, peer process that spec stuff for lightning goes through.
145
00:12:11.540 --> 00:12:13.080
146
00:12:13.860 --> 00:12:15.720
are l and d, c lightning,
147
00:12:16.165 --> 00:12:28.920
eclair, and then now LDK. Right? Right. Eclair was what we were talking about earlier, async. Yeah. Async. Yeah. Because for me, when we talk about specs, maybe that's where your first question comes in. They're like, are we at the point where
148
00:12:29.300 --> 00:12:37.545
the consensus on a spec level in advance is possible? And I I would say, yeah, we're getting there where it like like it won't be possible.
149
00:12:38.645 --> 00:12:39.145
But
150
00:12:39.765 --> 00:12:40.825
What does that mean?
151
00:12:41.180 --> 00:12:43.760
It means that you will start having
152
00:12:44.140 --> 00:12:48.240
features implemented that if they get mainstream adoptions,
153
00:12:48.620 --> 00:12:49.120
then
154
00:12:49.765 --> 00:12:50.505
other implementations
155
00:12:50.965 --> 00:12:51.705
will add
156
00:12:52.805 --> 00:12:56.425
it instead of first agreeing on spec and then implementing.
157
00:12:58.370 --> 00:12:59.750
So but but for me,
158
00:13:00.290 --> 00:13:02.550
that's a natural process that you see
159
00:13:03.970 --> 00:13:20.800
in in any anything that becomes popular. And lightning now I mean, there there were there was this meme, what, like, 2 years ago, lightning doesn't exist, whatnot. Like, lightning nowadays is not processing. Like, it it's getting to the point where it's, like, 100 of 1,000,000 of dollars are settled across lightning.
160
00:13:21.325 --> 00:13:22.945
Like it is in in production.
161
00:13:24.045 --> 00:13:24.865
So just
162
00:13:25.645 --> 00:13:26.785
the whole ecosystem,
163
00:13:27.085 --> 00:13:32.640
the product is maturing, and we are getting to that point where, like you had browser wars. So
164
00:13:33.020 --> 00:13:35.440
I don't think we'll have wars with different implementations,
165
00:13:35.900 --> 00:13:38.480
but I do see the system. Not yet at least. No.
166
00:13:39.625 --> 00:13:44.285
I see the system maturing, and then we will have other protocols. Like, I know now CoinJoin,
167
00:13:45.545 --> 00:13:51.980
CoinJoin is picking up those wars, but there is also, like, a coin pool protocol as a as a
168
00:13:52.680 --> 00:13:56.140
spec is out. It's a proposal. So to me, the more
169
00:13:57.115 --> 00:14:02.815
alternative layer 2 protocols we have, the the the better, and then some of the drama will move there. And,
170
00:14:03.195 --> 00:14:04.735
yeah, the system will mature.
171
00:14:05.830 --> 00:14:17.615
172
00:14:17.995 --> 00:14:19.615
even harder just because of the complexity,
173
00:14:20.555 --> 00:14:26.230
involved in the the safety like, the the need to be utmost secure throughout that whole process.
174
00:14:26.690 --> 00:14:34.335
That said, there's there's just basic wallet compatibility stuff for everybody building wallets right now that needs to get needs to get this act together. And, hopefully,
175
00:14:34.735 --> 00:14:36.355
I've I've put together a matrix
176
00:14:36.815 --> 00:14:41.315
of, like, which wallets can send to other wallets, who defaults to 0 amount invoices,
177
00:14:41.615 --> 00:14:54.425
who can't send to 0 amount invoices. And there's it's just a real big mess. And it feels like if all of us wallets could talk to each other and kinda get on the same page and work a little bit more in unison, that could add a lot more cohesion to the ecosystem.
178
00:14:54.805 --> 00:14:57.865
And so that's just kind of like a basic thing on a product level before
179
00:14:58.165 --> 00:14:59.845
diving into even some of these deeper,
180
00:15:00.245 --> 00:15:01.300
spec level things.
181
00:15:02.339 --> 00:15:06.360
182
00:15:06.820 --> 00:15:10.875
183
00:15:11.435 --> 00:15:16.255
more to come there. You wanna explain BIP 21 to the audience? So BIP 21 essentially
184
00:15:17.035 --> 00:15:18.569
lets you create it.
185
00:15:19.190 --> 00:15:21.910
You can have a one shared QR code with,
186
00:15:22.310 --> 00:15:28.275
combining an on chain and a lightning invoice. Essentially, it looks like a lightning invoice, but it has a fallback to an on chain,
187
00:15:29.055 --> 00:15:32.595
wall address in there. I think that moving towards the standard,
188
00:15:33.615 --> 00:15:35.715
will do a lot for just, like, increasing,
189
00:15:36.960 --> 00:16:01.270
user adoption and making normies not have to think, like, am I sending on chain? Am I sending on lightning? Is lightning bitcoin? Like, what the hell is even going on here? And so if you have one QR code, if I scan with a lightning only wallet okay. Cool. I'll I'll take the fastest cheapest option. I'll use lightning. If I scan with a on chain only wallet, okay, I don't recognize that that lightning QR code, I'll fall back on that on chain address, send it on chain.
190
00:16:02.530 --> 00:16:05.665
And so in your bank account, you might
191
00:16:06.125 --> 00:16:20.585
it's like your debit account. You might move funds in there via a variety of different ways. And you don't really care. Like, is this an ACH? Is this, like, over the wire? You just see money in, money out. And I think as a community, I think the north star we should be working towards
192
00:16:21.365 --> 00:16:23.145
is, just moving Bitcoin.
193
00:16:23.524 --> 00:16:28.760
And, hopefully, as we scale and as we get more users, we're using the faster, cheaper, more efficient layers.
194
00:16:29.220 --> 00:16:35.240
But if we're going to onboard a 1,000,000,000 people, I think we need to make it really simpler like, much, much simpler. And, ultimately,
195
00:16:35.694 --> 00:16:42.355
hope hopefully, in due time, I think, we can abstract away, like, the need to call out Lightning at all. It's just moving Bitcoin.
196
00:16:44.829 --> 00:16:58.470
197
00:16:58.790 --> 00:17:02.170
198
00:17:02.949 --> 00:17:04.890
With lightning. With lightning. Yes.
199
00:17:05.975 --> 00:17:12.475
My understanding is that lightning invoices, you can add a fallback address on chain. So sounds like I mean,
200
00:17:12.909 --> 00:17:16.289
from my knowledge of the current invoicing system on lightning,
201
00:17:17.149 --> 00:17:33.590
seems like we're probably running to an issue there where existing Bitcoin wallets can't parse lightning invoices is a problem. Right? So the data that you want is that use case was considered when they wrote the lightning spec. But the problem is that the wallet implementers
202
00:17:34.770 --> 00:17:42.155
do not offer a way to parse that data, so they have invented another spec called BIP 20 1 that they were getting
203
00:17:42.615 --> 00:17:46.235
204
00:17:46.540 --> 00:17:58.865
standard, then it's backwards compatible. But it's what you're saying is when, bolt bolt 11 was done, there was fallback address for on chain address. Mhmm. Like, this is the other way way around, and it's, like, the most backwards compatible.
205
00:17:59.565 --> 00:18:00.065
So
206
00:18:01.085 --> 00:18:06.065
there is this now conversation, like, okay. What is unified QR code? And are we
207
00:18:06.710 --> 00:18:15.370
in agreement on feature set that it offers? Because when when we are talking about bolt 12 now, there is, like, a refund option and so on and so forth.
208
00:18:16.435 --> 00:18:20.215
So I don't know. I need to see if I'm going with Miles, bit 21
209
00:18:20.595 --> 00:18:30.990
210
00:18:31.655 --> 00:18:32.795
withdrawing from Coinbase
211
00:18:33.095 --> 00:18:35.995
to a unified QR code will will break because
212
00:18:36.295 --> 00:18:39.515
they haven't implemented that correctly. But it should just be a small
213
00:18:39.910 --> 00:18:41.430
small change for a lot of these,
214
00:18:41.910 --> 00:19:01.700
215
00:19:02.400 --> 00:19:05.475
I don't think that, like, as an industry, we've quite figured out exactly
216
00:19:12.595 --> 00:19:18.540
Like, some of the most exciting stuff yet to be built is, like, this, like, interop and, like, getting the experience exactly
217
00:19:18.920 --> 00:19:20.780
hammered out at the wallet level. And,
218
00:19:21.575 --> 00:19:38.145
I think, you know, I work on the spec layer, which is just some extent, like, a few layers beneath the wallet stuff. And I think having a lack of, like, a centralized, like, at least forum for specs on all that stuff, I think you can definitely tell through kind of all the, I wouldn't call it confusion, but,
219
00:19:39.105 --> 00:19:43.525
all of the competing, like, specs little, like, suggestions of how to move forward.
220
00:19:44.510 --> 00:19:50.770
The fact that there's not, like, a consortium kinda like a consortium might be I don't know if that's a good word or a bad word.
221
00:19:51.150 --> 00:20:06.570
But, like, you know, at least, like, the wind lightning started as a protocol. Like, there were we were everyone was there together writing the spec together and agreed that that's what they were working towards as a group. Whereas, I think on the wallet side, there hasn't been kinda that, like, cohesive
222
00:20:07.445 --> 00:20:09.385
clarity of, like, exactly what
223
00:20:09.765 --> 00:20:14.184
it should look like. Does that make sense? And, like, you're trying to figure that out. I don't think anyone has, like, the right answer.
224
00:20:14.725 --> 00:20:26.965
But it is a little bit like that x kcd thing where you had a problem with, like, the previous specs. You made a new one. So there were 14 ways to do it. Now there's, like, 15 sort of thing. And I I do think we see that happening a lot on the wallet side.
225
00:20:27.445 --> 00:20:35.784
226
00:20:36.159 --> 00:20:40.500
100 of 1,000,000 of dollars across Lightning, there is still work to be done. So
227
00:20:42.559 --> 00:20:54.125
228
00:20:55.040 --> 00:21:05.345
But, like, 2 I remember 2 or 3 years ago at this point maybe, we're doing the lightning torch and trying to, like, stand up a node and get it all to work. And, man, it was just, like, show
229
00:21:05.985 --> 00:21:09.685
liquidity? Yeah. It's, like, what what is inbound liquidity? Are you kidding me?
230
00:21:10.065 --> 00:21:10.725
And so
231
00:21:11.105 --> 00:21:13.765
seeing the slow but but steady progress
232
00:21:14.290 --> 00:21:15.110
and seeing this
233
00:21:15.970 --> 00:21:19.910
starting at the start of 2021, I think, but really progressing even more recently,
234
00:21:20.530 --> 00:21:23.190
it's just gotten so much more usable, so much more reliable,
235
00:21:23.755 --> 00:21:31.295
236
00:21:31.950 --> 00:21:46.754
and we were trying to figure out lightning. And I sent him the 1st payment. It didn't work. Then we, like, did some channel management stuff, and then I sent him the 2nd payment. It worked. We're like, yes, we got it. Then I went to send them the 3rd payment and we ran out of liquidity and it didn't work. We're like, what the hell is going on here?
237
00:21:47.934 --> 00:21:49.875
It does feel like it's been a long time.
238
00:21:50.600 --> 00:21:50.919
And,
239
00:21:51.480 --> 00:21:53.820
and the whole space has, has moved forward tremendously.
240
00:21:55.159 --> 00:22:05.325
So I mean, with the bib 21 thing specifically, since it just got brought up, I mean, at the end of the day, you're talking about the wallets on the receiving side, being able to display this new QR code,
241
00:22:05.945 --> 00:22:14.540
but it can also be solved on the opposite side with the sender. I mean, we see a moon wallet with 2 use taking the initiative there. I mean, you scan either side and it works
242
00:22:14.920 --> 00:22:15.900
at what point,
243
00:22:16.335 --> 00:22:21.155
at what point does it just become tech debt to say, like, I need to support copay wallet
244
00:22:21.615 --> 00:22:27.720
or, you know, some wallet that no one's used in 5 years because know, it doesn't know what a lightning invoices.
245
00:22:28.500 --> 00:22:35.080
Is that, like, is that an actual thing that Bitcoiners should be thinking about? Or are we are we supposed to support, you know, every
246
00:22:36.125 --> 00:22:37.825
every wallet under the sun?
247
00:22:39.645 --> 00:22:42.705
248
00:22:43.560 --> 00:22:50.700
congrats to BitPay for for taking, like, the wallet that was most advanced and running it into ground. Like, what is it? 0 innovation.
249
00:22:51.320 --> 00:22:51.820
Yeah.
250
00:22:53.075 --> 00:22:55.815
I think it will be a natural process.
251
00:22:56.115 --> 00:22:56.934
Like, it's
252
00:22:57.955 --> 00:23:00.455
you can only plan so much in advance,
253
00:23:00.820 --> 00:23:01.320
and
254
00:23:01.860 --> 00:23:03.880
that's what I what Lisa was saying.
255
00:23:05.300 --> 00:23:10.520
Whole lightning spec, the the work done there was amazing. It was like all all the,
256
00:23:10.885 --> 00:23:11.545
you know,
257
00:23:12.565 --> 00:23:15.225
what it what what does Bolt stand for? It's like improvement.
258
00:23:16.885 --> 00:23:20.505
Base is a lightning technology. Base is a lightning. There we go.
259
00:23:20.889 --> 00:23:28.269
And Now we got the basics down. Yeah. Basics. No. You need to get it out. Listen, man. I'm VP of engineering now. I'm not into small details.
260
00:23:28.649 --> 00:23:29.549
But it's like
261
00:23:30.585 --> 00:23:42.020
all those improvements, like, they were agreed upon, and then it was like hard work of implementing it. And now we are there. I don't expect that we are going to have another chance to, like, all, like, duke it out. But
262
00:23:42.320 --> 00:23:48.605
that shouldn't we shouldn't look at that as a big problem. It's just okay. Let it go and grow organically and
263
00:23:50.025 --> 00:23:50.845
let it happen.
264
00:23:52.730 --> 00:23:56.270
265
00:23:57.210 --> 00:23:58.750
266
00:24:00.615 --> 00:24:11.429
267
00:24:11.809 --> 00:24:19.554
268
00:24:19.895 --> 00:24:20.955
oh, that was 70?
269
00:24:21.975 --> 00:24:23.035
70. 71. Right?
270
00:24:25.370 --> 00:24:37.605
271
00:24:37.905 --> 00:24:42.005
and that, like, Miles was saying, it sort of helps abstract away, like, the,
272
00:24:42.850 --> 00:24:49.110
implementation details of how you're moving Bitcoin around, which I think is definitely, like, a very worthy goal to get to from a user perspective.
273
00:24:49.890 --> 00:24:51.885
But, you know, like, all of these processes,
274
00:24:52.425 --> 00:24:55.165
like, every spec is only as good as, like, the participation
275
00:24:55.545 --> 00:25:12.995
you get into it. Right? And so, I mean, that's good for lightning as well. Like, we really need, like, everyone who's who wants to adhere to the the spec process. Like, we need you need, like, everyone, like, in the community participating. Right? So there's, like, a little bit of, like, you know, people have to, like, opt in to participation.
276
00:25:13.295 --> 00:25:25.350
And when people stop participating in the process for whatever reason, maybe they're busy. Maybe they've got, like, you know, business reasons. They're, like, more pressing, like, material concerns of where they're spending their dev time, etcetera.
277
00:25:25.765 --> 00:25:29.945
Maybe they've got some competing reason why they don't wanna make it happen, whatever. But,
278
00:25:30.565 --> 00:25:36.670
you know, really, it's like everyone chipping in and participating and get excited about, like, the possibility of interoperation
279
00:25:37.130 --> 00:25:41.070
that really moves, like, all this, like, entire, you know, network forward.
280
00:25:42.115 --> 00:25:45.255
281
00:25:45.635 --> 00:25:55.550
prospective developers that want to get more involved. Like, maybe it's what Lisa is saying, this problem, that problem, but maybe you are already doing good work and it's just not
282
00:25:56.090 --> 00:25:59.525
publicized well enough. So if there are such people in audience,
283
00:25:59.905 --> 00:26:01.605
yeah, talking about you, man,
284
00:26:01.905 --> 00:26:02.405
like,
285
00:26:02.865 --> 00:26:09.050
reach out after this talk and let let's see how to work together because, yeah, this is open source. Let's, yeah, let's collaborate.
286
00:26:09.590 --> 00:26:14.330
287
00:26:15.905 --> 00:26:20.725
envisioned ideal user experience discussion is happening in the Bitcoin design community.
288
00:26:21.345 --> 00:26:33.190
And, like, we if you're a designer, hop on in there and share your input. If you're just a normal user, hop on in there and share your input and help us kinda come to consensus. You don't have to be an engineer to have an opinion.
289
00:26:34.164 --> 00:26:36.825
There's all sorts of stakeholders in this environment,
290
00:26:37.684 --> 00:26:40.664
and certain people have strengths in certain areas.
291
00:26:41.100 --> 00:26:43.360
These these 2 are deep in the engineering scene.
292
00:26:44.139 --> 00:26:44.639
I
293
00:26:45.980 --> 00:26:49.679
I don't know what my strengths are exactly, but, compared to them. But,
294
00:26:50.605 --> 00:27:00.510
but, like, there's a there's a million ways to contribute. And maybe you're just maybe you just send the 100 lightning payments every day. But as a result of that, you know all the wallets, you know where the incompatibilities
295
00:27:00.810 --> 00:27:09.304
are, and you can help drive something forward that maybe then that somebody else picks up and, ultimately gets all the different wallets and the different implementations
296
00:27:09.605 --> 00:27:13.065
aligned and just build a a much better global lightning experience.
297
00:27:14.005 --> 00:27:20.730
298
00:27:23.695 --> 00:27:27.715
299
00:27:28.335 --> 00:27:35.990
participating in building history. Like, when we look back on this event in a year or 2, it will be like it happened here. Some,
300
00:27:37.250 --> 00:27:39.909
agreements were made here. Somewhat had a
301
00:27:40.210 --> 00:27:40.710
moment.
302
00:27:41.644 --> 00:27:45.585
So just looking forward to this journey with you. Let's go. Marty,
303
00:27:46.044 --> 00:27:49.300
304
00:27:49.700 --> 00:27:58.520
305
00:27:59.285 --> 00:28:00.505
and, like, self sovereignty.
306
00:28:01.045 --> 00:28:20.255
And I'm really excited about it. Also gonna take 2 seconds to show the fact that base 58, my Bitcoin transaction protocol class, just open registration for our next class. So if you are really interested in finding out more, getting involved in how the Bitcoin protocol works, we do a 6 weeks class, and we'd really love to have you in our class. So check out our website at base58.info.
307
00:28:21.434 --> 00:28:24.495
308
00:28:25.200 --> 00:28:28.340
Miles, final thoughts. Prometheans versus Malthusians.
309
00:28:28.880 --> 00:28:29.780
Don't forget it.
310
00:28:30.160 --> 00:28:30.980
Thanks, guys.
