May 19, 2021

CD22: the lightning network with @fiatjaf and @evankaloudis

CD22: the lightning network with @fiatjaf and @evankaloudis
Citadel Dispatch
CD22: the lightning network with @fiatjaf and @evankaloudis

EPISODE: 0.2.2

BLOCK: 684116

PRICE: 2311 sats per dollar

TOPICS: lightning network


@fiatjaf: https://twitter.com/fiatjaf

@evankaloudis: https://twitter.com/evankaloudis


streamed live every tuesday:

https://citadeldispatch.com


twitch: https://twitch.tv/citadeldispatch​

bitcointv: https://bitcointv.com/video-channels/citadeldispatch/videos

podcast: https://anchor.fm/citadeldispatch​

telegram: https://t.me/citadeldispatch​


support the show: https://tippin.me/@odell

stream sats to the show: https://www.fountain.fm/

join the chat: http://citadel.chat/

00:00 - Bitcoin price volatility

00:26 - Predictions for Bitcoin price range

01:31 - Institutional adoption of Bitcoin

05:42 - Bitcoin race car initiative

12:25 - Bitcoin price drop and Elon Musk's influence

15:56 - Bullish outlook on Lightning Network

47:13 - Trade-offs in the Lightning Network

48:06 - Adoption of Liquid and Lightning

50:31 - Integration of Lightning Network in Games

01:31:09 - Issues with the current market maker system

01:32:08 - The need for a separate Oracle in gambling

01:33:24 - The demand for frictionless Bitcoin gambling

02:11:49 - Attacks on Ethereum Classic

02:12:14 - Cracking lower hash rate chains

02:13:28 - Nostra - a decentralized broadcasting cloud

WEBVTT

NOTE
Transcription provided by Podhome.fm
Created: 3/17/2024 8:02:33 PM
Duration: 9973.081
Channels: 1

1
00:00:00.000 --> 00:00:01.220
Back to just talking about,

2
00:00:01.760 --> 00:00:05.220
where Bitcoin is. Because when you remember when it ran up to 14,000

3
00:00:06.319 --> 00:00:14.125
and then pulled back to about 9,000? You said, yeah. No. That got a little bit out. I wish I'd sold some. At 14 Yeah. You copped to that. You got in trouble.

4
00:00:14.559 --> 00:00:21.779
The stackers all wrote in. Novogratz says, you know, paper hands or whatever the heck they're called. Alright. Now you're you've got the 62.

5
00:00:22.755 --> 00:00:23.974
Now we're at 45.

6
00:00:25.234 --> 00:00:48.950
What are your hands feeling like? Are they paper? Are they how come you're not doing the same thing? Why aren't you saying, you know what? I've made 10 times my money. Why don't I get out and then stack when it comes down back down to 20? So you must not think it's going back to 20. I I think 40 should hold. You know, I think we're gonna be at a 40 to 55 range for a while. We'll consolidate, and then we'll have another leg up. And I say that not just by guessing. We see institutions

7
00:00:49.410 --> 00:00:52.070
moving in, and it takes them a while. Right?

8
00:00:52.770 --> 00:00:54.790
UBS, Goldman Sachs, JPMorgan,

9
00:00:55.170 --> 00:00:57.955
almost every bank is on their way into their wealth channels.

10
00:00:58.355 --> 00:01:05.550
They're not there yet. They're getting set up. They're getting their funds ready. And so you think about just Morgan Stanley for a second. Right?

11
00:01:05.930 --> 00:01:10.110
With 2013, 14, I think I was, like, the lone Wall Street guy screaming about Bitcoin.

12
00:01:10.650 --> 00:01:12.510
Morgan Stanley just trained 4,000

13
00:01:12.970 --> 00:01:14.030
financial advisors

14
00:01:14.375 --> 00:01:18.634
to sell Bitcoin. And so we're gonna have these armies of newly

15
00:01:19.095 --> 00:01:19.595
anointed

16
00:01:20.134 --> 00:01:20.634
prophesizers,

17
00:01:21.095 --> 00:01:25.740
salesmen, who have learned the the technology, have learned why it's important in your portfolio,

18
00:01:26.119 --> 00:01:31.475
all going out to the bulk of wealth in America, 50 to 80 year olds, and I think that's gonna have an impact.

19
00:01:31.955 --> 00:01:36.854
It doesn't have a overnight. You would you would stack at 40. You would start I would stack at 40.

20
00:02:16.490 --> 00:02:18.270
Happy Bitcoin Tuesday, freaks.

21
00:02:18.650 --> 00:02:22.030
It's your boy, Odell, here for another Citadel dispatch.

22
00:02:22.754 --> 00:02:25.815
Last time we did one of these, last Bitcoin Tuesday,

23
00:02:27.955 --> 00:02:29.815
we were we were up a humble

24
00:02:30.599 --> 00:02:33.180
13 and a half $1,000 from where we are today.

25
00:02:33.640 --> 00:02:34.860
It's been a 24%

26
00:02:35.319 --> 00:02:35.819
decrease

27
00:02:36.120 --> 00:02:41.205
week over week since last Bitcoin Tuesday. Hope you guys are all huddling in there, and,

28
00:02:42.005 --> 00:02:47.660
you didn't get to let your ego get to you too much, and you you weren't leveraged, and and you didn't get blown the fuck out.

29
00:02:48.540 --> 00:02:53.600
Because if that's the case, then you're in Stackers Paradise right now, accumulating some cheap sets.

30
00:02:54.380 --> 00:02:59.345
Citadel dispatch, the interactive live show about Bitcoin distributed systems privacy and open source software

31
00:02:59.645 --> 00:03:01.105
coming to you every Tuesday.

32
00:03:01.485 --> 00:03:02.625
This is our 22nd

33
00:03:02.925 --> 00:03:03.425
episode.

34
00:03:03.885 --> 00:03:05.260
Very excited about it.

35
00:03:06.299 --> 00:03:08.400
To those coming in through our audio streams,

36
00:03:09.340 --> 00:03:11.200
what there are 2 podcast feeds.

37
00:03:11.579 --> 00:03:14.959
That was our boy, Joe Kernan, on CNBC talking with Novogratz,

38
00:03:16.364 --> 00:03:17.825
about stacking the dip

39
00:03:18.205 --> 00:03:19.185
and about weekends.

40
00:03:19.724 --> 00:03:28.490
Novo is a bit of a shit corner, no doubt, but, it's always good to see that kind of talk on mainstream media. It's pretty funny how it is permeated everywhere.

41
00:03:30.355 --> 00:03:37.255
As always, I just wanna do a big shout out to the rider die freaks that are here in the live chat and that have supported the show.

42
00:03:38.920 --> 00:03:41.580
Couldn't do without you guys. You guys are what it's about.

43
00:03:42.840 --> 00:03:48.425
You really make, Bitcoin Tuesdays really special to me. So so thank you to all you guys, especially

44
00:03:48.725 --> 00:03:51.225
if you're coming in through the podcasting 2 point o.

45
00:03:52.405 --> 00:03:56.860
The streaming stats is really fucking cool. We're gonna talk about that a little bit on the show,

46
00:03:58.600 --> 00:04:02.220
but if you haven't checked that Breeze app, like, the the the Breeze app is

47
00:04:02.605 --> 00:04:08.465
is you really see the future there. You can really see the future of of being able to stream value directly to content creators,

48
00:04:09.770 --> 00:04:12.990
rather than this ad model that is just, like, proliferated everywhere.

49
00:04:13.450 --> 00:04:15.390
So, definitely check that out if you haven't.

50
00:04:15.770 --> 00:04:18.830
I also wanna do a big shout out to our boy, Jack Mahler's

51
00:04:19.375 --> 00:04:20.195
living legend.

52
00:04:20.975 --> 00:04:25.395
He set up the Indy race car. We're gonna have a Bitcoin race car, car number 21,

53
00:04:26.255 --> 00:04:28.275
at the Indy 500 this weekend.

54
00:04:28.880 --> 00:04:30.320
Oh, yeah. He,

55
00:04:30.800 --> 00:04:31.300
completely

56
00:04:31.759 --> 00:04:38.015
turned down any actual strike branding on the race car, So it's going to be completely Bitcoin branded,

57
00:04:39.275 --> 00:04:42.255
and they're accepting donations that will go to open source development.

58
00:04:42.930 --> 00:04:47.349
So it's a really fantastic initiative. We had, I think, Michael Sailor pledged $250,000

59
00:04:48.129 --> 00:04:49.030
the other day,

60
00:04:50.129 --> 00:04:51.509
today earlier today.

61
00:04:51.905 --> 00:04:53.125
So pressure all,

62
00:04:53.665 --> 00:04:54.325
your businesses

63
00:04:54.785 --> 00:05:04.039
in the Bitcoin community to to step up to the plate and support open source development in probably the most baller fucking way possible, which is with a really fast fucking race car,

64
00:05:04.340 --> 00:05:05.479
in front of a 144,000

65
00:05:06.100 --> 00:05:07.080
people in Indianapolis.

66
00:05:08.419 --> 00:05:08.919
And

67
00:05:09.365 --> 00:05:13.465
I've been supporting it as well. You can support it at strike dot me slash racing.

68
00:05:14.324 --> 00:05:16.985
Any any donations that come in through the lnurl,

69
00:05:18.280 --> 00:05:22.700
QR code on the bottom left hand of the screen, if you're watching the video stream throughout this stream,

70
00:05:23.160 --> 00:05:24.540
will be split 5050

71
00:05:24.920 --> 00:05:27.660
with the with the race car. So,

72
00:05:28.264 --> 00:05:29.645
just trying to do my part

73
00:05:30.025 --> 00:05:36.240
to help this initiative. It's a really fucking great initiative, and it really aligns well with the work we've been doing at opensats dotorgandalsobitcoindevilist.com.

74
00:05:38.300 --> 00:05:40.000
So I'm really excited about that.

75
00:05:42.300 --> 00:05:46.025
With all that said, this is Citadel dispatch 22.

76
00:05:47.044 --> 00:05:48.985
We have Evan Kaludis returning

77
00:05:49.285 --> 00:05:51.225
for his 5th show.

78
00:05:51.759 --> 00:05:52.340
Oh, man.

79
00:05:52.800 --> 00:05:54.819
What's up, Briggs? Glad to be back.

80
00:05:55.120 --> 00:06:06.384
One of our resident lightning junkies, so it was important that he was here for the show. Last last week, if if you missed it, you should go and check it out, but there was a very deep dive into lightning privacy,

81
00:06:07.405 --> 00:06:13.540
with our boy Anthony and Open Arms. So we're gonna do the same fucking thing again. It's gonna be another really deep fucking show,

82
00:06:14.640 --> 00:06:20.485
on lightning and and just continue that path, And and we're fortunate enough to have Fiat Jaffe here with us who,

83
00:06:21.185 --> 00:06:23.445
is someone I've admired a lot on the Internet,

84
00:06:23.985 --> 00:06:28.470
but I never heard his voice till today, so it's really exciting to have him on the show. What's up, Fiat, Jeff?

85
00:06:29.010 --> 00:06:30.070
Hey. What's up?

86
00:06:31.730 --> 00:06:35.670
Very for inviting me. Yeah. Very prolific lightning developer.

87
00:06:36.155 --> 00:06:42.335
So really excited. The other thing that I wanted to mention before we jump into this is that I've been updating Citadel dispatch.com,

88
00:06:45.449 --> 00:06:51.470
and now all of the episodes are up there with embedded videos and searchable transcripts. I

89
00:06:52.224 --> 00:06:58.724
have continued my trend of just losing money doing this show, so I put another 1,000,000 sats into automated

90
00:06:59.025 --> 00:07:05.240
AI transcripts, which to be quite honest, aren't that good, but it's pretty fucking cool that you can search through all of the episodes.

91
00:07:06.020 --> 00:07:12.015
And I'm going to be going through those and trying to edit them and refine them because they have, like, these tools that I could do that for. But in the meantime,

92
00:07:13.035 --> 00:07:16.495
all 22 episodes of dispatch are easily searchable on dispatch.com,

93
00:07:17.035 --> 00:07:17.410
so

94
00:07:17.890 --> 00:07:18.870
pretty fucking cool.

95
00:07:20.690 --> 00:07:28.815
So with all that said, I mean, I I guess, you know, let's let's you know, people pretend that they're in it for the tech, but we gotta talk about what's on everyone's mind.

96
00:07:29.275 --> 00:07:34.140
Is Bitcoin dead? Are we going to 0? Is it all over? And why did Elon fuck us?

97
00:07:36.380 --> 00:07:38.960
That's a loaded question. Well, Matt, right to it.

98
00:07:40.220 --> 00:07:42.240
Yeah, man. It's been a really crazy week.

99
00:07:42.775 --> 00:07:47.275
You know, I I know a lot of hodlers are having their net worth fluctuate.

100
00:07:48.455 --> 00:07:53.350
A lot of people without faith just selling and letting go of their whole bags.

101
00:07:55.330 --> 00:08:00.870
You know, it's a little overblown, to be honest. And, you know, of course, mister Musk isn't helping

102
00:08:01.205 --> 00:08:03.865
with his bullshit, but, at the same time,

103
00:08:04.165 --> 00:08:05.145
just kind of,

104
00:08:05.525 --> 00:08:06.025
drawbacks

105
00:08:06.565 --> 00:08:07.065
or,

106
00:08:07.605 --> 00:08:11.040
you know, sort of par for the course. Look to 2017

107
00:08:11.420 --> 00:08:13.600
even. What we we drew back, like,

108
00:08:13.900 --> 00:08:16.560
4 or 5 times like this, 30% plus.

109
00:08:18.125 --> 00:08:26.384
And, I think people also need to take into account that taxes were due past couple weeks. Right? So there's gonna always be a lot of people

110
00:08:26.990 --> 00:08:32.270
just offloading their bags just to pay the bills, especially if there's, you know, traders in,

111
00:08:33.230 --> 00:08:42.865
this field. What so you think, like, people are panic selling their Bitcoin, like, the day before tax day when they realize how much taxes they owe? I I think there's a lot of people that don't plan in advance.

112
00:08:43.165 --> 00:08:44.120
That's for sure.

113
00:08:45.400 --> 00:08:46.940
But, you know, it's also not,

114
00:08:48.839 --> 00:08:56.055
we also can't neglect, you know, all the rhetoric and and the post from Elon this week. Of course, that shook a lot of people out. You know?

115
00:08:56.675 --> 00:08:57.555
It's hard to deny,

116
00:08:58.810 --> 00:09:02.990
how much we pumped when Tesla said they were adding to their books.

117
00:09:03.690 --> 00:09:05.630
So that's obviously a factor too.

118
00:09:06.965 --> 00:09:14.585
But I think we are like, the the the the fall of the price is not that big. I don't know because I'm not following that much. So

119
00:09:14.970 --> 00:09:19.310
but but if if it if you were at 5,000 and you drop to 4,000,

120
00:09:19.850 --> 00:09:21.149
it wouldn't be a

121
00:09:22.305 --> 00:09:24.964
very large dip. Right? So

122
00:09:26.305 --> 00:09:29.125
this what happened now wasn't isn't that big.

123
00:09:30.300 --> 00:09:32.640
And Elon Elon put us on a new level,

124
00:09:33.020 --> 00:09:37.100
and we we didn't drop drop from that from that level yet. So

125
00:09:37.955 --> 00:09:40.995
Yeah. I mean, I I think, you know, people love to put,

126
00:09:41.555 --> 00:09:49.560
and I kind of set you guys up with the question. I just think it's funny that I just got all these people reaching out to me, like, texting me, like, like, what the fuck is Elon doing? Like, what a fucking asshole,

127
00:09:50.420 --> 00:09:56.760
what a douchebag. It was like I I said to a friend, it was almost like their best they found out their best friend, like, slept with their fiance.

128
00:09:57.205 --> 00:10:12.410
You know? Like, they were, like, so betrayed. I'm like, guys, like, what the fuck did you expect? Like, he's never been a stable person. Like like, who who who thought, like It's not even just that he's not a stable person. It's, like, who the fuck is this guy? Like, think about it. Like, Tesla

129
00:10:12.790 --> 00:10:17.265
doesn't make money off their cars. Right? He has one of the poorest run,

130
00:10:17.805 --> 00:10:19.885
alternative energy companies, right, in,

131
00:10:20.605 --> 00:10:22.100
whatever, his panel company.

132
00:10:22.579 --> 00:10:26.839
And SpaceX is is a darling for government subsidies as well. Right?

133
00:10:29.305 --> 00:10:32.765
These are the kind of people that are gonna suffer the most

134
00:10:34.025 --> 00:10:34.765
post hyperbitcoinization.

135
00:10:37.339 --> 00:10:39.040
So it it should leave,

136
00:10:39.740 --> 00:10:42.960
it should be a surprise that that an individual like this

137
00:10:43.339 --> 00:10:45.120
is working to forward Bitcoin

138
00:10:45.835 --> 00:10:51.535
and, you know, trying to hold on to that sweet, sweet subsidy for as long as he can.

139
00:10:52.715 --> 00:10:55.990
But I just wanted to just add here. I mean, if you look at

140
00:10:57.010 --> 00:10:59.190
in in in bull markets,

141
00:11:00.529 --> 00:11:04.070
and bear markets, people just like trying to find explanations for price drops.

142
00:11:04.875 --> 00:11:10.415
But this is a thing that is just natural. It is gonna happen. Bitcoin is a truly scarce asset,

143
00:11:11.435 --> 00:11:17.570
and as a result, as it's going through its adoption phase, you tend to have these, you know, rapid increases

144
00:11:18.270 --> 00:11:19.250
and then decreases,

145
00:11:19.685 --> 00:11:24.824
you know, where it's just trying to find its support level. It's like there's no way for it to really go up,

146
00:11:25.605 --> 00:11:33.510
in a smooth fashion because it's just, like, almost like pure chaos. And I so I have a chart on the on the screen for the people on the on the video streams,

147
00:11:34.050 --> 00:11:52.440
from Glassnode from Glassnode's weekly, report. And as you can see on this thing, like, we had massive draw downs last in 2017 too. Like, people after the fact will pretend, you know, staying humble and stacking stats was the easy mood mode, and that anyone could have huddled and that we were all fucking lucky.

148
00:11:53.375 --> 00:11:56.515
But there was a lot of shit your pants stumps that happened,

149
00:11:56.975 --> 00:11:57.714
in 2017.

150
00:11:58.495 --> 00:12:06.720
Mhmm. And there's gonna be a lot more that happened this time, and it's just that now we're at such a higher number. You know? A 23% drop is $14,000.

151
00:12:09.165 --> 00:12:11.584
Like, that's not nothing. Right? Like, that's absolute

152
00:12:11.885 --> 00:12:12.365
terms,

153
00:12:12.765 --> 00:12:14.625
I could see it scaring more people.

154
00:12:18.720 --> 00:12:26.135
So that was our our daily Bitcoin price talk, and now we can jump into the tech that everyone cares about. Yeah. Fuck Elon.

155
00:12:27.795 --> 00:12:36.500
Yeah. I mean, the the moral of the story is that Elon is wanted to make sure that the whole world knows that he's still short Bitcoin. So But but it it should be a lesson. Like, we shouldn't simp for

156
00:12:37.040 --> 00:12:37.860
any billionaires,

157
00:12:38.480 --> 00:12:39.459
you know, none the

158
00:12:40.240 --> 00:12:44.265
no. We shouldn't send for any billionaires, and definitely don't send for any cantillionaires

159
00:12:44.645 --> 00:12:49.625
that are, you know, just just drunk off of the government spigot.

160
00:12:50.329 --> 00:12:54.089
We have full time Bitcoin in, in the comments. He's our resident,

161
00:12:55.130 --> 00:12:57.870
Tesla freak. He's obsessed with Tesla, so

162
00:12:59.145 --> 00:13:02.365
he he wants everyone to know to fuck Elon, but not fuck SpaceX.

163
00:13:05.545 --> 00:13:11.790
I don't know why he's making that distinction. I mean, I'm I'm kinda excited for Starlink. I think Starlink could be very useful to us.

164
00:13:14.170 --> 00:13:19.085
I would never get a Tesla period though because it's, like, a horrible fucking car for privacy. And,

165
00:13:19.565 --> 00:13:30.220
don't get me started on that. And, like and you have, like you just automatic imagine automatic updates to a car car, like, the thing is, like, going, like, 80 miles an hour and just getting automatic updates.

166
00:13:31.800 --> 00:13:33.175
Scare the shit out of me.

167
00:13:33.815 --> 00:13:34.875
I hope one day

168
00:13:35.255 --> 00:13:46.460
bad on the oil pipeline. Like, what if you get ransomware on your car? What if you're not driving it? What if your wife and kids are driving it? The best excuse if you're late to a meeting, you know, my car got ransomware ed.

169
00:13:48.200 --> 00:13:54.605
The I hope that that some rich Bitcoin or at some point in the future creates, like, a luxury private car company,

170
00:13:55.065 --> 00:14:07.030
you know, that has no computer in it. It's just, like, got a, you know, regular combustion engine in it, and just put this a nice car that's privacy focused. That would be the ideal for me. Because, like, right now, I feel like I have to buy a 20 year old car,

171
00:14:07.875 --> 00:14:12.214
if I don't want a computer in it. Or at least a hardening service, you know, like,

172
00:14:12.834 --> 00:14:23.960
drop my Tesla off and, like, chop that up. Like, let me get a couple of, firewalls in there, you know, some ways of verifying what's going on there, and, you know, cut off the core function from the web.

173
00:14:25.025 --> 00:14:26.965
I'm told that updates aren't automatic.

174
00:14:28.625 --> 00:14:36.010
So live corrections are the best part of the show or one of the best parts of the show. Okay. So For now, they're not automatic. So they For now.

175
00:14:36.550 --> 00:14:45.085
Yeah. I mean, they're not automatic. Right? But it's closed source, and no one's verifying it before they click the update button. So who the fuck? It doesn't really matter. If you press the accelerator,

176
00:14:45.625 --> 00:14:47.565
it updates. It's it's your constant.

177
00:14:53.660 --> 00:14:54.480
Yeah. So,

178
00:14:55.339 --> 00:14:58.800
that was a very important Bitcoin discussion. I'm really glad we had it.

179
00:14:59.885 --> 00:15:02.625
And I think let's just, you know so this this

180
00:15:03.084 --> 00:15:04.705
dispatch is all about dispatch

181
00:15:05.644 --> 00:15:08.785
is all about actionable Bitcoin discussions. So the idea is,

182
00:15:10.529 --> 00:15:13.269
I want us to focus on things that Bitcoiners can actually,

183
00:15:13.889 --> 00:15:18.745
you know, use in their day to day basis more so than, big picture things. But,

184
00:15:19.365 --> 00:15:20.905
since I have you, I'd I,

185
00:15:22.085 --> 00:15:23.545
you know, I I

186
00:15:24.005 --> 00:15:25.305
I think we'll

187
00:15:27.230 --> 00:15:31.810
ignore that aspect just for the beginning here, and I'm kind of curious, big picture.

188
00:15:32.350 --> 00:15:36.130
You've been, you know, really focused on lightning development specifically.

189
00:15:38.225 --> 00:15:39.045
Are you

190
00:15:39.905 --> 00:15:48.880
you know, the 2 year, 3 year outlook for lightning, are you bullish on it? Are you bearish on it? You know, what is your what are your thoughts there? Should should Bitcoiners,

191
00:15:50.060 --> 00:15:55.025
Bitcoiners seem to be very hyped about lightning right now. Is that is that hype properly placed, or is it mis

192
00:15:56.225 --> 00:16:05.420
placed? I think it's it's properly placed, but I'm not sure for the the same reasons. I I I I bullish I'm bullish on lightning, but

193
00:16:06.040 --> 00:16:11.175
I'm I'm bullish on more like a a network and less like a trustless

194
00:16:11.635 --> 00:16:13.975
pure payments through channels thing. Like,

195
00:16:15.635 --> 00:16:21.860
I think I think Bitcoin will have other forms of transferring there there there will be more other forms of transferring Bitcoin,

196
00:16:22.400 --> 00:16:24.500
and I think Lightning is the

197
00:16:25.520 --> 00:16:31.825
is the the the base for should be the base for all these like, if someone comes up with another protocol,

198
00:16:32.205 --> 00:16:34.625
we should integrate integrate it into Lightning,

199
00:16:35.360 --> 00:16:35.860
and

200
00:16:36.400 --> 00:16:39.620
Lightning will be this this network that connects everything,

201
00:16:40.080 --> 00:16:42.340
including custodial services and

202
00:16:43.264 --> 00:16:43.764
other

203
00:16:44.464 --> 00:16:44.964
stuff.

204
00:16:45.665 --> 00:16:48.004
So I'm I'm bullish on it because of that.

205
00:16:48.704 --> 00:16:49.904
Yeah. I mean, I think,

206
00:16:50.990 --> 00:16:54.529
I I I think we tend to be on the same page there from what you just said.

207
00:16:55.550 --> 00:16:57.170
You know, one interesting aspect,

208
00:16:58.325 --> 00:17:03.865
is that a lot of light and you just mentioned it, the word custodial. I mean, a lot of developers,

209
00:17:05.350 --> 00:17:07.930
frown on anything custodial related.

210
00:17:08.950 --> 00:17:11.370
But I feel like you've kind of leaned into it.

211
00:17:12.955 --> 00:17:17.055
Do you want to, like, do in a lot of ways, I feel like lightning

212
00:17:17.675 --> 00:17:20.815
I don't wanna put words in your mouth, but I, like, I feel like lightning

213
00:17:22.149 --> 00:17:25.690
really works well as, like, interoperable custodial wallets.

214
00:17:26.230 --> 00:17:30.005
This idea where you can have, like, a bunch of little custodial wallets with

215
00:17:30.405 --> 00:17:34.105
varied trust models, and they can all interact with each other in an open way.

216
00:17:34.565 --> 00:17:35.065
Yeah.

217
00:17:36.485 --> 00:17:39.865
Yeah. Yeah. That that's what I think too, like, since a long time.

218
00:17:40.390 --> 00:17:48.730
When people I I people use it to say, like they still say, like, if you if you're going if you're going to use a custodial wallet, better use PayPal.

219
00:17:49.355 --> 00:17:53.695
But this this argument is stupid because PayPal is not using Bitcoin.

220
00:17:54.075 --> 00:18:03.460
And then they say, oh, so use Coinbase. But Coinbase is a closed thing. You're you're stuck inside there, and they they own you if you're there. But if you're using a a custodial

221
00:18:04.555 --> 00:18:06.255
service that's interactive lightning,

222
00:18:06.555 --> 00:18:10.815
then it's open. And then anyone can join other custodial service. Like, competition,

223
00:18:12.050 --> 00:18:13.670
makes things better. Like,

224
00:18:14.050 --> 00:18:18.390
we don't have to have trustless everything. We we need the trustless option,

225
00:18:18.770 --> 00:18:20.630
but the the market,

226
00:18:21.505 --> 00:18:23.365
the free market of of services

227
00:18:24.065 --> 00:18:26.164
still works very well for most things.

228
00:18:26.784 --> 00:18:28.804
So also for money transferring.

229
00:18:29.419 --> 00:18:30.080
So do

230
00:18:30.380 --> 00:18:31.679
you think,

231
00:18:32.380 --> 00:18:37.039
do you think the average user should be using their own Lightning node when they interact with Lightning?

232
00:18:39.465 --> 00:18:42.845
Well, I think they should for now if they are willing to

233
00:18:43.145 --> 00:18:43.304
to

234
00:18:44.240 --> 00:18:51.860
if they they want to understand it, they they must run a a node to to see it go it happening and so on. But I I don't think most people

235
00:18:52.545 --> 00:18:55.365
are up for this. Like, they they don't care.

236
00:18:57.505 --> 00:18:59.320
And and so I think

237
00:19:00.279 --> 00:19:05.580
the people that care and the people that understand should strive to create an an environment

238
00:19:06.200 --> 00:19:10.245
in which the people that don't care don't get trapped inside Coinbase.

239
00:19:10.625 --> 00:19:12.404
They can get trapped inside

240
00:19:12.784 --> 00:19:13.924
a a more open

241
00:19:14.225 --> 00:19:14.725
thing.

242
00:19:15.664 --> 00:19:16.725
Does that make sense?

243
00:19:17.220 --> 00:19:21.320
Well, I mean, let's talk about so so right now, I have this lnurl

244
00:19:21.700 --> 00:19:23.160
on the bottom left hand corner,

245
00:19:24.020 --> 00:19:25.799
and it uses your LNTX

246
00:19:26.260 --> 00:19:27.554
bot, which

247
00:19:28.014 --> 00:19:29.875
is a Telegram bot, but

248
00:19:30.414 --> 00:19:35.154
I feel like it does that doesn't go far enough. It it's it's a full fledged lightning wallet

249
00:19:35.870 --> 00:19:41.570
that runs inside of the Telegram app, which is already installed by, well, I don't know, like, a couple billion people probably.

250
00:19:44.054 --> 00:19:48.715
And it's got tons and tons of features in it, including this static donation

251
00:19:49.015 --> 00:19:57.300
QR code that allows anyone to just scan it whether it's during the show or later, and it goes it goes right to my wallet. Now that wallet is custodial though,

252
00:19:58.480 --> 00:20:07.525
and, I mean, correct me if I'm wrong. The main reason it it's custodial is because it makes it way easier for you to implement those features. Right? In, like, a UX friendly way.

253
00:20:08.970 --> 00:20:15.235
Well, the the actual way it's custodial is because I didn't know how to do it, like, differently when I did it.

254
00:20:16.195 --> 00:20:21.174
But, yeah, if if it wasn't custodial, it would require people to run software

255
00:20:21.795 --> 00:20:25.015
and connect to the bot, and no one would do it. So

256
00:20:26.820 --> 00:20:30.840
But let's talk about the risk. Right? The risk is that you run away with my money,

257
00:20:32.580 --> 00:20:33.960
and or that

258
00:20:34.445 --> 00:20:37.745
there's there's some kind of pressure and you have to require KYC.

259
00:20:38.365 --> 00:20:38.865
So

260
00:20:39.325 --> 00:20:40.705
both of those get mitigated

261
00:20:42.100 --> 00:20:52.135
if you just use it with less amount of money. Right? I mean, that's basically the argument. Right? It's like if if you if you run away if you if you decide to do an exit scam on this wallet,

262
00:20:52.515 --> 00:20:57.575
you know, I'll lose 50 or $60 or whatever, and I'll just call it a day and call it even.

263
00:20:58.570 --> 00:20:59.390
Yeah. Yeah.

264
00:20:59.770 --> 00:21:00.990
I think I think

265
00:21:01.690 --> 00:21:02.750
yeah. I think that's

266
00:21:03.130 --> 00:21:03.630
exact.

267
00:21:04.970 --> 00:21:07.390
For this for this custodial wallets,

268
00:21:07.955 --> 00:21:11.335
you should put low money on it. It's all fine.

269
00:21:12.115 --> 00:21:18.590
It's it's just weird. People running nodes to to you you start a full lightning node and open channels just

270
00:21:19.050 --> 00:21:19.870
to transact

271
00:21:20.170 --> 00:21:23.685
$5 on it. It's not it's not good investment.

272
00:21:24.225 --> 00:21:28.565
And it's weird because, like, you know, we go deep into the weeds on this show. I mean, dispatch

273
00:21:29.025 --> 00:21:31.845
freaks are you know, I think they're

274
00:21:32.300 --> 00:21:33.120
they're very enthusiastic

275
00:21:33.660 --> 00:21:36.960
about Bitcoin. They're very focused on Bitcoin, on best practices.

276
00:21:37.900 --> 00:21:40.160
Most of them are probably using their own nodes.

277
00:21:41.345 --> 00:21:49.125
But then you have, like, wake up calls where, you know, I had Keydominer and MBK on the show. You know, they're both highly technical people,

278
00:21:50.710 --> 00:22:01.475
very educated Bitcoiners, and they both admitted you know, Keydomen who runs a lightning service, they both admitted that their favorite wallet to use was Wallet of Satoshi, which is a custodian mobile wallet.

279
00:22:02.255 --> 00:22:06.435
So I feel like there's this massive disconnect between, like, the geeks in the space

280
00:22:07.070 --> 00:22:13.970
and reality. Right? And no one really discusses it, so I kinda like that. I think dispatch should be able to bridge that gap.

281
00:22:16.615 --> 00:22:23.530
Yeah. I I just I I there there's definitely a role here for custodial wallets, and to say otherwise is just ignoring the reality. Right?

282
00:22:24.570 --> 00:22:27.870
Yeah. Yeah. Yeah. But I think when if you're talking about,

283
00:22:28.490 --> 00:22:29.390
building bridges,

284
00:22:29.850 --> 00:22:30.750
I think 11

285
00:22:31.565 --> 00:22:34.544
the biggest problem with Custodial is the privacy,

286
00:22:35.404 --> 00:22:37.424
not that someone will steal,

287
00:22:37.804 --> 00:22:41.550
$10 for a new for new like, the the privacy is much worse because

288
00:22:42.510 --> 00:22:45.010
I can't see all transactions from everybody

289
00:22:45.390 --> 00:22:47.810
on LNTX, but and that's bad.

290
00:22:48.430 --> 00:22:51.010
But the the solution to this is that the,

291
00:22:51.665 --> 00:22:54.965
hosted hosted channels thing. Have you ever heard about that?

292
00:22:55.425 --> 00:22:56.725
Well, let's talk about that.

293
00:22:58.730 --> 00:23:00.270
Yeah. The hosted channels is

294
00:23:01.450 --> 00:23:02.990
is a protocol that

295
00:23:03.770 --> 00:23:05.230
uses the same lightning

296
00:23:06.215 --> 00:23:08.475
base, like, the the same communication channels,

297
00:23:08.935 --> 00:23:09.435
and

298
00:23:10.215 --> 00:23:13.915
you you you just do something similar to to Lightning.

299
00:23:15.029 --> 00:23:22.409
It's it's a channel with amounts and so on and balances, but you the the the client doesn't doesn't

300
00:23:23.235 --> 00:23:26.294
control the money. The money stays on the on the host side.

301
00:23:26.755 --> 00:23:34.919
So it's a it's a custodial service, but it's fully private because the the host doesn't know what where you're sending the payments to and

302
00:23:35.539 --> 00:23:36.039
basically

303
00:23:36.740 --> 00:23:49.815
Now this is currently implemented on BLW on Android. Is that right? Yeah. It's currently implemented on BLW. And the server side, there's a, it's it's running on a clear for for Intel, which is my pseudonym.

304
00:23:50.195 --> 00:23:50.855
Just kidding.

305
00:23:53.700 --> 00:23:56.360
And now and now Antl is making a new wallet

306
00:23:56.660 --> 00:23:59.240
that's much better, much cleaner, I think,

307
00:23:59.665 --> 00:24:02.405
and with the with the Immorton library.

308
00:24:03.025 --> 00:24:05.285
And releasing a plug in to

309
00:24:05.665 --> 00:24:14.310
for anyone to run it run the the the server side on their a clear note easily. So there there could be a a bunch of different custodians

310
00:24:15.410 --> 00:24:16.870
hosting these these channels.

311
00:24:18.274 --> 00:24:21.575
And also, I'm I'm planning on finishing, like,

312
00:24:21.875 --> 00:24:31.970
getting my work done and making a plug in for c lightning tool to support this. If I find that 15 that that that extra hour in the day, I will do it.

313
00:24:35.785 --> 00:24:39.005
Yes. I think that BLW is a pretty interesting model.

314
00:24:39.865 --> 00:24:41.965
So, you know, you have those hosted channels

315
00:24:43.309 --> 00:24:44.769
that are indeed custodial,

316
00:24:45.710 --> 00:24:46.210
but,

317
00:24:46.669 --> 00:24:53.184
for more pressing stuff or, you know, when you can't find a route, you're able to have your own channel opened up,

318
00:24:54.605 --> 00:25:07.070
you know, to make those connections that are you know, those payments that are more private and to the branch you wanna make. And you can have a wallet with different channels different hosted channels to different hosts. Like and

319
00:25:07.485 --> 00:25:07.804
you don't

320
00:25:08.445 --> 00:25:15.904
your money doesn't sit all in one place. And you'll then then you send NPP payments splitting over these different

321
00:25:16.350 --> 00:25:16.850
hosted

322
00:25:17.309 --> 00:25:21.090
channels. It's very private. It's very, very, like, very private.

323
00:25:21.470 --> 00:25:21.970
And

324
00:25:22.750 --> 00:25:25.295
I think it's I think it's a very good model,

325
00:25:25.674 --> 00:25:27.455
and no one's talking about it.

326
00:25:28.155 --> 00:25:37.880
Yeah. It's it's definitely underrated and has a lot of interesting qualities to it. And, yeah, I think it's only gonna get more interesting as we have more providers like this that offer hosted channels

327
00:25:38.260 --> 00:25:38.659
as,

328
00:25:39.220 --> 00:25:41.794
you know, more different wallet implementations,

329
00:25:43.054 --> 00:25:44.274
have support for it.

330
00:25:44.654 --> 00:25:46.434
And furthermore, down the line,

331
00:25:46.815 --> 00:25:52.350
as far as, like, protocol stuff goes, is routing is split up and sees a whole bunch of innovations,

332
00:25:53.690 --> 00:25:55.630
then things start getting really interesting.

333
00:25:55.985 --> 00:26:00.725
So the simple summary of the hosted the hosted channel's trade off is

334
00:26:01.184 --> 00:26:01.924
they can't

335
00:26:02.465 --> 00:26:07.900
they you you you you don't have custodial privacy, but they can still steal your funds. Right?

336
00:26:08.600 --> 00:26:09.100
Yeah.

337
00:26:09.480 --> 00:26:09.980
Mhmm.

338
00:26:11.365 --> 00:26:15.385
Actually, I think you should call them credit channels. I I don't understand why

339
00:26:15.845 --> 00:26:19.385
custodial is bad, but credit is good on the on the mainstream,

340
00:26:19.685 --> 00:26:20.090
like

341
00:26:20.970 --> 00:26:21.549
a finance

342
00:26:21.850 --> 00:26:22.350
world.

343
00:26:23.690 --> 00:26:27.450
Credit is okay. You don't pay taxes for credit, but you

344
00:26:27.995 --> 00:26:30.815
the government goes against you. You should do custodian stuff.

345
00:26:32.395 --> 00:26:39.409
But, so so you we when we when we have you know, there's there there's it's an interesting nuance here. Right? Because

346
00:26:40.190 --> 00:26:40.929
you have

347
00:26:42.110 --> 00:26:44.450
a privacy concern with your custodian,

348
00:26:45.105 --> 00:26:47.205
I mean, if we're not talking hosted channels,

349
00:26:47.745 --> 00:26:48.245
but

350
00:26:48.945 --> 00:26:50.565
in a lot of ways, you get

351
00:26:50.865 --> 00:26:59.900
better external privacy if that custodian is a trusted source. If that that custodian is not working against you if the custodian is working against you, you have, obviously, you have worse privacy.

352
00:27:00.665 --> 00:27:03.485
But if the custodian is attempting to protect your privacy,

353
00:27:04.265 --> 00:27:11.410
then you have in in a lot of situations, you might have better privacy. Like, one of the things I think is interesting about Bitcoin On

354
00:27:11.710 --> 00:27:19.845
Chain is, historically, we've had a ton of custodial wallets, and they've all, like, failed. So people have moved, you know, to pretty much the default is noncustodial.

355
00:27:20.145 --> 00:27:22.485
Right? Like, it's a it's it's a very rare day

356
00:27:23.025 --> 00:27:32.960
where you have, like, a mobile wallet that has custodial on chain. We still have that in lightning, and, you know, we have 61 and 2 in the comments. I think one of the main concerns I have with something like Wallet or Satoshi

357
00:27:33.445 --> 00:27:36.985
or Blue Wallet is it's not very clear that it's a custodial wallet.

358
00:27:37.765 --> 00:27:44.840
Yeah. What the risks are and what the trade offs are. But we've seen on chain, like, people have moved to pretty much self custody by default.

359
00:27:45.700 --> 00:27:51.000
And as a result, all of a sudden on chain privacy techniques are more important. Right? Because if you're,

360
00:27:52.075 --> 00:28:00.175
and I already I I see people realizing this even if they don't admit it when they, like, try and pay me from strike or cash app because they don't want me to,

361
00:28:01.639 --> 00:28:06.779
you know, see what their balances are. So they they rely on the custodian to protect their privacy for them,

362
00:28:07.480 --> 00:28:09.179
which I just think is just an interesting

363
00:28:11.345 --> 00:28:16.404
it's an interesting thing that happened that no one really talks about is that was this move from from custodial

364
00:28:17.080 --> 00:28:21.020
dominating to non custodial and and the impact it had on on chain privacy?

365
00:28:23.799 --> 00:28:27.174
Yeah. Yeah. I I was not following the Bitcoin space

366
00:28:27.475 --> 00:28:27.875
at the

367
00:28:28.515 --> 00:28:29.495
at this period

368
00:28:30.035 --> 00:28:32.775
when people use it. We still do on chain wallets.

369
00:28:33.280 --> 00:28:35.440
So I don't really know it. This thing about,

370
00:28:35.760 --> 00:28:43.415
not show sharing your balances is, like, to the peep to the person you're paying, this is not talking about very much, like, in this

371
00:28:43.715 --> 00:28:45.495
every time someone talks about privacy,

372
00:28:46.915 --> 00:28:52.990
no one talks about this or maybe I'm missing it. The joint market has a good solution to it. You can pay someone

373
00:28:53.290 --> 00:28:57.310
while doing a coin join with the exact amount, so it fixes that.

374
00:28:59.125 --> 00:29:00.025
But yes.

375
00:29:00.565 --> 00:29:03.465
Yeah. But with LightningAid, it's it's much more

376
00:29:03.845 --> 00:29:06.585
it's much harder to to move to a no custodial

377
00:29:07.500 --> 00:29:08.000
setup.

378
00:29:08.460 --> 00:29:12.240
So So what do you what do you think keep smaller amounts.

379
00:29:12.700 --> 00:29:23.605
I mean, the the big thing I think with non custodial Lightning is channel management. There's this concept of channel management. I think it kinda goes hand in hand with how hard it is to conceptualize UTXO management to begin with,

380
00:29:24.120 --> 00:29:26.940
in coin control. Like, this is something that we're always

381
00:29:29.000 --> 00:29:31.500
harping on and very focused on in this space,

382
00:29:33.585 --> 00:29:34.085
but

383
00:29:35.024 --> 00:29:36.005
it it it's

384
00:29:36.385 --> 00:29:44.919
UTXO management is, like, a very hard thing for people to grasp, and as a result, I feel like lightning channel management is also has this this

385
00:29:45.220 --> 00:29:45.620
this,

386
00:29:46.179 --> 00:29:48.765
speed bump. It's a hurdle to try and understand it.

387
00:29:49.325 --> 00:29:56.625
And that's kind of where the custodial wallets come into play. Before I get there, 6102 is saying it was always dominated by non custodial wallets.

388
00:29:57.000 --> 00:30:00.380
I mean, I would push back there. What I'm suggesting is, you know, stuff like

389
00:30:00.680 --> 00:30:04.460
like Silk Road, for instance, was a completely custodial product,

390
00:30:05.185 --> 00:30:08.885
that had a built in mixer, and and the users of Silk Road,

391
00:30:09.425 --> 00:30:12.885
were relying on that custodial privacy to provide them privacy.

392
00:30:15.070 --> 00:30:15.570
But

393
00:30:16.190 --> 00:30:21.809
so so I'm talking about from that angle or or any of the exchanges that were non KYC, stuff like BTCE

394
00:30:22.535 --> 00:30:24.635
that existed for the longest fucking time,

395
00:30:25.415 --> 00:30:31.755
or MintPal or Cripsy or whatever. I don't know. All the fucking shit coin casinos that that had no KYC.

396
00:30:32.780 --> 00:30:35.360
Those are all custodial wallets. But, anyway, I'm getting derailed.

397
00:30:35.900 --> 00:30:40.160
Fiat, Jeff, I'm curious. So so we're talking about UTXO management, channel

398
00:30:40.460 --> 00:30:40.960
management.

399
00:30:43.155 --> 00:30:45.815
One thing we've talked about a lot in this show is

400
00:30:46.275 --> 00:30:48.215
the uncle Jim model. This idea

401
00:30:48.820 --> 00:30:53.080
where you have, like, a friend or family member, in this case, his his name's uncle Jim,

402
00:30:54.179 --> 00:30:56.519
and he runs the node for the family.

403
00:30:57.725 --> 00:31:03.025
And he has, like, you know, 25 or 30 people that he's custodial on top of,

404
00:31:03.405 --> 00:31:06.210
that he you know, he's their he's their Bitcoin friend or Bitcoin uncle.

405
00:31:10.130 --> 00:31:18.664
Samura implement this with their QR code pairing with the node, but that's obviously not lightning, and we've seen BlueWallet implement it recently,

406
00:31:20.485 --> 00:31:23.785
on the lightning side. So BlueWallet defaults to custodial,

407
00:31:24.790 --> 00:31:29.850
but it it runs on LND hub. So if you run LND hub on your Raspberry Blitz or your Umbrel,

408
00:31:30.230 --> 00:31:31.850
or I think my note as well,

409
00:31:33.175 --> 00:31:35.035
you can then be the uncle Jim,

410
00:31:35.415 --> 00:31:36.635
and you can have,

411
00:31:38.055 --> 00:31:40.795
you can have friends or family connect to you, and they don't have to deal with any channel management or anything. You deal

412
00:31:41.530 --> 00:31:43.710
you know, trade off wise, or

413
00:31:44.690 --> 00:31:45.190
is

414
00:31:46.170 --> 00:31:52.605
that something that you think is just a complete waste of time? You know, trade off wise, or is that something that you think is just a complete waste of time?

415
00:31:53.145 --> 00:32:00.310
Yeah. No. I think that's that's a good thing good thing for the future and for now. Yeah. I see it happening. I see people on the LNB's

416
00:32:00.610 --> 00:32:05.030
Telegram chat asking about how to set up the LND Hub plug in

417
00:32:05.335 --> 00:32:07.595
so they can host for friends and family.

418
00:32:08.054 --> 00:32:08.554
And,

419
00:32:09.095 --> 00:32:14.794
yeah, I I since a long time ago, I I I thought about this too, and I think it's a good model.

420
00:32:15.220 --> 00:32:16.520
I think the the

421
00:32:17.220 --> 00:32:24.040
the model for with with hosted channels, anyone being able to to run their own hosted channel server,

422
00:32:24.785 --> 00:32:28.725
that's good too for this this specific case to the oncogene

423
00:32:29.025 --> 00:32:30.280
stuff. So

424
00:32:30.785 --> 00:32:31.605
yeah. Yeah.

425
00:32:32.270 --> 00:32:34.450
I think this is the way the way future

426
00:32:34.910 --> 00:32:35.650
is this.

427
00:32:36.830 --> 00:32:43.035
This and other other scene other things that the the good thing about Lightning is this. You can have the Uncle g model. You can have the completely

428
00:32:44.215 --> 00:32:50.075
running your own stuff model. You can have the big exchange bank model, everything together.

429
00:32:50.650 --> 00:32:51.950
And also people running

430
00:32:52.250 --> 00:32:54.430
lightning on lightning on some liquid

431
00:32:55.050 --> 00:32:56.830
and other side chains.

432
00:33:00.535 --> 00:33:04.715
What are your thoughts here, Evan? I mean, you're the lead maintainer of a completely noncustodial,

433
00:33:05.175 --> 00:33:06.315
non uncle Jim.

434
00:33:08.020 --> 00:33:09.240
User own node wallet?

435
00:33:11.460 --> 00:33:12.440
Yes. So

436
00:33:14.105 --> 00:33:15.645
I really do want to support

437
00:33:15.945 --> 00:33:19.885
uncle g model. Right? LND does have support for the uncle g

438
00:33:20.265 --> 00:33:20.765
model.

439
00:33:22.140 --> 00:33:24.400
So we have support for LND hub.

440
00:33:25.660 --> 00:33:26.320
You can

441
00:33:26.620 --> 00:33:29.260
download Zeus and use that if you want.

442
00:33:29.660 --> 00:33:35.905
We auto generate the blue wall in lnd hub server, but we encourage everyone to,

443
00:33:37.245 --> 00:33:43.010
you know, if possible, find an uncle Jim to connect to and use their

444
00:33:43.310 --> 00:33:54.295
note. In fact, we're doing some work right now. We have some work in right now to fix the connection for LD Hubs that are behind Tor. So, like, let's say you use an Umbrel, and that's on Tor by default.

445
00:33:55.315 --> 00:33:58.935
The next release of Zeus is gonna make sure that that's all ironed out.

446
00:33:59.640 --> 00:34:01.580
And, if you're an uncle Jim

447
00:34:01.880 --> 00:34:05.820
and you've got a node that's running on Tor, you're running that LND Hub blue

448
00:34:06.440 --> 00:34:07.980
wallet server service

449
00:34:08.440 --> 00:34:09.340
behind Tor,

450
00:34:10.345 --> 00:34:13.485
Zeus is gonna be able to accommodate people using that. So,

451
00:34:14.185 --> 00:34:15.405
I I think that

452
00:34:15.865 --> 00:34:18.940
there's some limitations with what you can do with LND hub.

453
00:34:19.980 --> 00:34:22.000
Obviously, you're not gonna get the fully featured

454
00:34:22.380 --> 00:34:26.319
set of features like key send or channel management

455
00:34:26.859 --> 00:34:27.680
or messaging

456
00:34:28.335 --> 00:34:32.835
of that stuff. But to onboard people onto the Lightning Network, it's a great solution.

457
00:34:33.215 --> 00:34:34.515
And if we want

458
00:34:35.890 --> 00:34:40.550
this to be viable and and for this to be more common and,

459
00:34:41.250 --> 00:34:42.710
you know, for for real

460
00:34:44.615 --> 00:34:48.235
commercial solutions, like, with big corporations running stuff,

461
00:34:49.255 --> 00:34:50.875
to not be the the default.

462
00:34:51.990 --> 00:34:54.250
You know? Freaks have to go out there

463
00:34:54.950 --> 00:34:58.570
and run it themselves and and try to onboard their friends and family.

464
00:34:59.225 --> 00:35:03.725
Let's make this the way that people experience Lightning Network for the first time.

465
00:35:05.225 --> 00:35:06.445
There's so much more,

466
00:35:10.480 --> 00:35:21.145
you know, it's so much easier to go to your friend, your buddy, your uncle Jim than to, you know, file a support ticket at this big corporation that you hope is inevitably gonna be looked at

467
00:35:21.845 --> 00:35:23.145
and, you know,

468
00:35:23.685 --> 00:35:24.185
centralizing

469
00:35:24.645 --> 00:35:28.970
risk. You you you don't want these big honeypots of people's info

470
00:35:29.510 --> 00:35:33.530
to, you know, keep growing and collecting people's data and,

471
00:35:33.990 --> 00:35:34.570
you know,

472
00:35:35.325 --> 00:35:38.225
be there to be subpoenaed by federal government.

473
00:35:39.325 --> 00:35:39.885
But are we

474
00:35:40.845 --> 00:35:44.145
like, I I see I see why it's ideal.

475
00:35:44.930 --> 00:35:48.869
I mean, look. Bitcoin doesn't have a support department or marketing department.

476
00:35:50.210 --> 00:35:56.155
A show like this, you know, we can hit thousands of users, but thousands of people, but, like, it can't scale to,

477
00:35:56.695 --> 00:35:58.875
you know, educating 1,000,000 or 1,000,000,000.

478
00:35:59.815 --> 00:36:01.660
The only way it really scales if

479
00:36:01.980 --> 00:36:05.359
was, like, each of each of the freaks, you know, goes and

480
00:36:05.900 --> 00:36:12.775
and, you know, helps 10 of their friends and family, and and they have tons of 10 of their friends and family. And then that's how I, like, see it scaling.

481
00:36:13.235 --> 00:36:15.095
But, like, are we biased? Like

482
00:36:15.715 --> 00:36:16.215
like,

483
00:36:16.590 --> 00:36:18.770
I wasn't around you know, I'm a youngin'.

484
00:36:19.070 --> 00:36:21.310
I wasn't around during, you know,

485
00:36:22.110 --> 00:36:25.490
when com computers and the Internet were starting to become a thing.

486
00:36:27.474 --> 00:36:34.214
But, like, some of the old timers that have been around, they told me, you know, like, this was the model that they were talking about back in the day.

487
00:36:34.550 --> 00:36:36.250
Like, the Internet was gonna be,

488
00:36:36.950 --> 00:36:41.610
you know, your your uncle Jim was gonna run the mainframe computer in, like, his garage,

489
00:36:42.150 --> 00:36:49.155
and everyone was gonna connect to it. And instead, what happened was economies of scale just centralized it all into,

490
00:36:49.535 --> 00:36:51.235
you know, Google, Apple, Microsoft,

491
00:36:51.535 --> 00:36:52.035
Amazon,

492
00:36:53.380 --> 00:36:59.720
Twitter, Twitch. Right? Like, it it centralized it all into these these giant clouds these cloud services.

493
00:37:00.365 --> 00:37:05.425
But that trend is just being bucked now. Like, home computing is becoming so

494
00:37:05.805 --> 00:37:08.065
practical and so much cheaper. And

495
00:37:08.445 --> 00:37:11.800
you know what it really is? It's like people realize the terrors of

496
00:37:12.180 --> 00:37:22.395
what can go wrong when you trust these centralized entities with your data. Like, the average person is starting to, you know, come to terms with the amount of control that Google and Apple

497
00:37:22.855 --> 00:37:25.035
and Microsoft, etcetera, all have.

498
00:37:25.655 --> 00:37:26.155
And,

499
00:37:26.940 --> 00:37:29.280
you know, now now that we have these solutions,

500
00:37:31.420 --> 00:37:32.480
in, you know,

501
00:37:32.860 --> 00:37:33.360
cheap

502
00:37:33.820 --> 00:37:36.240
hardware and and free open source software,

503
00:37:36.655 --> 00:37:42.515
Like, people are starting to explore. I mean, it's it's not gonna be your your grandma that sets one of these off.

504
00:37:43.690 --> 00:37:47.390
But, you know, for the people who are willing to do their own research and

505
00:37:48.010 --> 00:37:49.869
figure out how all these things work,

506
00:37:50.329 --> 00:37:52.510
it's it's more practical than ever.

507
00:37:53.295 --> 00:38:03.310
And, you know, it's it's it's not inherently by the default design of the Internet that that these things would happen and become centralized. It's like a hub and spoke model. You know? Like like, the Internet's

508
00:38:04.410 --> 00:38:09.310
built to route around these traffic jams. And to be sort of centralized entities are

509
00:38:10.165 --> 00:38:11.385
sort of anomalous.

510
00:38:12.485 --> 00:38:15.145
And, you know, hopefully, the the move

511
00:38:15.525 --> 00:38:17.225
the movement keeps running, and,

512
00:38:17.530 --> 00:38:20.190
you know, people take things into their own hands.

513
00:38:20.570 --> 00:38:24.190
And, you know, we we need to try to make sure in the Bitcoin community

514
00:38:24.650 --> 00:38:26.510
that we don't get to that centralized,

515
00:38:26.810 --> 00:38:27.310
really

516
00:38:29.035 --> 00:38:31.695
highly centralized model. Like, we wanna try to avoid that

517
00:38:32.155 --> 00:38:33.775
instead of having to undo it.

518
00:38:34.235 --> 00:38:36.790
I think, like, the Internet has survived

519
00:38:37.170 --> 00:38:39.430
in in the sense that you can still

520
00:38:40.050 --> 00:38:43.990
go to the Unfolding or run your own stuff model today.

521
00:38:44.345 --> 00:38:44.845
Uh-huh.

522
00:38:45.465 --> 00:38:51.085
And even if the the majority of people are are using the centralized service, and they they can they can migrate

523
00:38:51.385 --> 00:38:52.925
off now like they're doing.

524
00:38:55.100 --> 00:39:03.745
And so if if you can do that on Bitcoin and Lightning, I think we're safe. Like, as long as it's possible to to to jump

525
00:39:04.205 --> 00:39:11.799
off, we're fine. The the bad thing would be if the centralized big providers just made themselves incompatible with everything else, and

526
00:39:12.500 --> 00:39:14.039
then they trapped everybody.

527
00:39:14.660 --> 00:39:16.839
But if it if that doesn't happen,

528
00:39:17.535 --> 00:39:18.915
it's still okay.

529
00:39:20.494 --> 00:39:20.994
Yeah.

530
00:39:21.775 --> 00:39:24.994
I saw I saw a question on the chat, but it it vanished.

531
00:39:25.760 --> 00:39:26.660
Someone asking

532
00:39:27.360 --> 00:39:32.820
if if you're if you're not liable for hosting the the funds of your friends and family.

533
00:39:33.494 --> 00:39:38.635
I think I think I don't know if you are liable or not. I don't know the the laws, but I think this question is

534
00:39:39.015 --> 00:39:44.119
is I see it happening everywhere. Like, everybody's too afraid of being liable to to stuff.

535
00:39:44.900 --> 00:39:51.785
I'm not sure that's the correct mentality. I think we shouldn't like, if if everybody if if a ton of people are running nodes and

536
00:39:52.644 --> 00:39:56.744
for for their friends and family, the government won't be able to track everybody.

537
00:39:57.119 --> 00:39:57.280
So

538
00:39:57.920 --> 00:40:10.925
This is total cock mentality. I'm sorry to butt in, but, like, if you're gonna have the government have to dictate every private relationship you have, then you've already lost the plot. You know? Like, we're we're trying to build a world of voluntary interaction.

539
00:40:11.545 --> 00:40:19.650
If you can't make it up, you don't wanna take on that risk and help advance this technology and make life easier for your friends and family because of legal liability,

540
00:40:20.465 --> 00:40:22.325
yeah, you're already cooked. I'm sorry.

541
00:40:23.505 --> 00:40:27.045
Yeah. Yeah. That's what I wanted to say, but not in these words.

542
00:40:30.000 --> 00:40:35.060
So that's it. We have to step up and and take some risk, I think, for the benefit of everybody.

543
00:40:36.435 --> 00:40:39.495
And if more the more people do do it, the best.

544
00:40:40.355 --> 00:40:44.455
There was also a question that finished about how Lightning or Liquid

545
00:40:45.490 --> 00:40:47.750
would work with Lightning or Main Bitcoin.

546
00:40:48.690 --> 00:40:52.150
And the the the answer is just that you just need bridges

547
00:40:52.575 --> 00:40:53.075
And,

548
00:40:54.175 --> 00:40:56.675
like like, the nodes that are on liquid,

549
00:40:57.214 --> 00:40:59.395
they must understand how to use the bridge.

550
00:40:59.775 --> 00:41:04.280
And the nodes that are on on the on the main chain side, they can

551
00:41:05.780 --> 00:41:10.280
the liquid node can use the route hints route hints on the invoice to

552
00:41:10.820 --> 00:41:11.320
to

553
00:41:12.025 --> 00:41:17.405
point them to the bridge, and then the bridge knows what to do to send the pass the the payment

554
00:41:18.025 --> 00:41:19.245
to the liquid node,

555
00:41:19.839 --> 00:41:21.540
if that that makes sense.

556
00:41:22.319 --> 00:41:23.380
I have a prototype

557
00:41:24.400 --> 00:41:27.859
for that, but it needs a ton of improvement to be actually usable.

558
00:41:28.255 --> 00:41:28.994
But it works.

559
00:41:29.775 --> 00:41:30.835
I think it works.

560
00:41:33.375 --> 00:41:42.370
I feel like you have I feel like you have a bunch of, like, little projects you're not telling us, Jeff. I feel like Yeah. Your hands are everywhere. Like yeah. I feel like your engine is revving, like,

561
00:41:42.830 --> 00:41:44.210
all the way all day.

562
00:41:45.165 --> 00:41:47.665
Like, it feels like you're a workhorse, man.

563
00:41:47.965 --> 00:41:48.465
I'm

564
00:41:48.845 --> 00:41:53.905
impressed by, like, all the little pods you've got your hands in and all the contributions you've made.

565
00:41:56.190 --> 00:41:56.690
Yeah.

566
00:41:56.990 --> 00:41:57.490
Yeah.

567
00:41:57.869 --> 00:42:00.450
I wish they were finished and working and

568
00:42:01.365 --> 00:42:06.105
there were more people helping maybe or maybe making them better than me.

569
00:42:06.805 --> 00:42:10.500
But I I can't finish most of the things I have. I I I tried.

570
00:42:11.060 --> 00:42:13.320
I mean, I just wanna jump back real quick.

571
00:42:13.860 --> 00:42:19.160
I mean, I I think there is, you know, definitely real liability and and depending on your jurisdiction.

572
00:42:20.685 --> 00:42:26.785
And I think but mostly that works to our advantage. Right? And I I I guess I kind of asked a,

573
00:42:30.380 --> 00:42:37.904
you know, I asked kind of a leading question when I asked if it's gonna centralize, and I think what happens is, like, the one thing we have going to our advantage

574
00:42:38.285 --> 00:42:43.505
is these financial regulations mean that, you know, the centralized corporate services,

575
00:42:44.125 --> 00:42:47.440
because of liability, are gonna have oppressive KYC.

576
00:42:48.700 --> 00:42:51.440
They're gonna have, you know, information retention

577
00:42:52.060 --> 00:42:54.720
and and poor privacy. So because of that,

578
00:42:55.714 --> 00:43:02.214
there's actually a major friction point to using these centralized services over using either your own node or,

579
00:43:02.930 --> 00:43:06.230
I see in the comments, we they don't like uncle Jim. They want aunt Jam.

580
00:43:07.890 --> 00:43:11.510
If, you know, using your uncle Jim node, you don't have that that friction.

581
00:43:11.925 --> 00:43:20.505
So they're they're I unlike the Internet, you know, something like with with, like, Gmail, for instance. Right? It's, like, centralized email. Right? It's, like, completely.

582
00:43:21.310 --> 00:43:26.770
If you talk to, like, an original email nerd, like, Gmail completely lost the plot and isn't real email.

583
00:43:27.310 --> 00:43:46.799
But people love it. Right? And it's because that trade off isn't very clear that they're reading your email and they're providing you a service because they're just reading through every single thing you do and just collecting information on you. But if you sign up for a centralized service and they're, like, upload your passport, prick your finger and give us your blood, give us your Social Security number, like, the firstborn

584
00:43:47.180 --> 00:43:47.680
child,

585
00:43:48.365 --> 00:43:54.385
like, then, you know, you might look for a different option. You're gonna be like, that that's that's a heavy price to pay.

586
00:43:54.685 --> 00:43:57.345
So we kind of have that you know, while that's

587
00:44:07.255 --> 00:44:09.115
It'll also help to our advantage,

588
00:44:09.734 --> 00:44:11.035
the fact that,

589
00:44:12.295 --> 00:44:16.250
that that they you know, the big players will have to ball with those regulations. Right?

590
00:44:18.010 --> 00:44:20.350
Yeah. It's it's definitely something working in our favor.

591
00:44:21.089 --> 00:44:23.390
The Yeah. But the person was asking about

592
00:44:23.705 --> 00:44:29.565
the the Right. Uncle Jim lawyers, the the Uncle Jim liability. I think Uncle Jim shouldn't worry about that.

593
00:44:30.345 --> 00:44:41.140
Yeah. I mean, if I was a lawyer, I would say to worry about it. But in practice, you know, if you're doing it for, like, your 10 family members or something, like, except for the, you know, the most authoritative governments, you'll probably be fine.

594
00:44:42.400 --> 00:44:46.715
So I kinda derailed the conversation a little bit. We were, like, dipping our toes into liquid.

595
00:44:48.375 --> 00:44:52.155
Do you think, like, liquid is a reasonable project, or do you think, like, it's

596
00:44:53.770 --> 00:44:54.829
it's it's unnecessary

597
00:44:56.089 --> 00:44:57.470
because of lightning existing?

598
00:44:58.569 --> 00:44:59.789
Oh, I think it's reasonable.

599
00:45:00.645 --> 00:45:03.464
I like I like I think custodial stuff is reasonable

600
00:45:03.765 --> 00:45:05.865
as I said before. And, like,

601
00:45:06.805 --> 00:45:09.704
we we should strive to get better custodian models,

602
00:45:10.400 --> 00:45:13.859
and liquid is a good custodian model. It's a custodian that

603
00:45:14.480 --> 00:45:16.180
it's very private and,

604
00:45:16.880 --> 00:45:19.220
actually, not very private if you're trying to

605
00:45:19.655 --> 00:45:21.195
to back out. But

606
00:45:21.815 --> 00:45:30.200
and it's reasonably safe. Right? The the apparently, they have good good safety for the keys. So it's it's better than a bank,

607
00:45:31.780 --> 00:45:37.295
and it's open. You don't have to to KOC to use it. Only only if you want to peg out, but

608
00:45:37.775 --> 00:45:39.555
that's not not always necessary.

609
00:45:41.295 --> 00:45:51.599
Yeah. Because you can just do a swap, really. You don't need to do a formal peg out. Yeah. That's what I think. The the the obsession over the peg out is a little bit ridiculous because the only thing that you you really have,

610
00:45:53.464 --> 00:45:54.285
you know,

611
00:45:54.744 --> 00:45:54.905
trust minimized,

612
00:45:56.425 --> 00:45:59.244
in and out with is lightning. Before lightning existed,

613
00:46:01.289 --> 00:46:03.549
you know, this idea that we had a trust minimized

614
00:46:03.849 --> 00:46:09.950
way of pegging in is is is revolutionary on its side on itself. And then, you know, swaps,

615
00:46:10.585 --> 00:46:13.725
you know, especially if we get atomic swaps. But even if you get

616
00:46:14.105 --> 00:46:18.605
I mean, we already have them. We have the custodial swaps. Right? Like, the shape shift type of things.

617
00:46:19.480 --> 00:46:23.020
And that's what people have been using with altcoins for however long.

618
00:46:24.040 --> 00:46:29.805
It's relatively trust minimized. I mean, obviously, they can run off with your money in the interim while the while the trade's happening.

619
00:46:30.505 --> 00:46:36.125
We had Adam back on the show the other day. He made an interesting point. Like, even if we have if we have centralized atomic swaps,

620
00:46:37.539 --> 00:46:45.400
that improves the trust model slightly further because, yes, it's a centralized point of failure, but they can't steal your money. The swap only happens if they're giving you the

621
00:46:45.940 --> 00:46:46.680
the equivalent.

622
00:46:49.525 --> 00:46:52.585
So, like, it's almost like a misnomer saying, like, we need permissionless

623
00:46:53.045 --> 00:46:56.985
peg outs on on liquid. We just need, like, a healthy swap market. Right?

624
00:47:00.280 --> 00:47:01.580
Yeah. The yeah.

625
00:47:01.880 --> 00:47:08.555
I mean, if if the peg outs are someone will have to to do the the bag outs on the normal way. Like,

626
00:47:09.415 --> 00:47:14.155
or at least that that guarantee has to be there that there will be a bag out. Adam

627
00:47:14.470 --> 00:47:21.050
Adam made a interesting point. Right? And there was a trade off made, and the trade off was if, you know, they get you get

628
00:47:22.585 --> 00:47:25.085
way better external security for the system

629
00:47:25.385 --> 00:47:28.525
if you make it so PEG outs only go to approved ex pubs,

630
00:47:28.825 --> 00:47:30.444
which is the federation members.

631
00:47:31.200 --> 00:47:33.619
So it's, like, it's a very clear trade off they made.

632
00:47:33.920 --> 00:47:49.369
And I I'm not, you know, I'm not sure I'm I'm not gonna be the one who says that the better trade off is that they should be able to peg out to any fucking address, because who wants who wants the chance that you could have, you know, 10,000 Bitcoin just get drained from the whole system at once

633
00:47:49.750 --> 00:47:51.130
or whatever. I'm being alarmist.

634
00:47:52.070 --> 00:47:57.875
But Yeah. Yeah. I I didn't know that. I didn't know that the that was a decision based on on security.

635
00:47:58.175 --> 00:47:58.835
So yeah.

636
00:47:59.535 --> 00:48:03.955
Yeah. We did a 3 hour banger with Adam back on the show, which was a very special episode.

637
00:48:04.415 --> 00:48:05.075
Yeah. Great.

638
00:48:06.120 --> 00:48:20.585
Where we do no one talks about liquid. That's why I like to talk about it more. No one uses it. I mean, if you go to, like That's the main thing. More services have to adopt it, really. And, you know, if you take a look at their blockchain and see how many transact on. It's a ghost town. I mean,

639
00:48:20.885 --> 00:48:25.859
not to say that it doesn't have some real merits and could be really useful. It's just, definitely

640
00:48:26.560 --> 00:48:34.020
not where we need it right now. And, you know, you could say the same thing about lightning. Lightning needs a lot more adoption for Yeah. But not at not

641
00:48:35.244 --> 00:48:42.145
not the same level. Yeah. Not the same level. People are using Lightning more actively, but they could both use bump.

642
00:48:45.690 --> 00:48:46.190
Yeah.

643
00:48:47.130 --> 00:48:48.750
No one talks about RSK.

644
00:48:50.009 --> 00:48:51.789
Did you have an opinion on RSK?

645
00:48:53.395 --> 00:48:54.135
Yeah. No.

646
00:48:54.515 --> 00:48:56.695
I think the same about Liquid. Like,

647
00:48:56.995 --> 00:48:57.735
I think it's

648
00:48:58.035 --> 00:48:59.655
better than a bank, so

649
00:49:00.355 --> 00:49:02.695
that's good. I I'm not sure about the

650
00:49:03.300 --> 00:49:11.400
Ethereum like smart contract. I'm not sure they're very useful. But It has a it it has a shitcoin. It has a shitcoin, though. Liquid doesn't have the shitcoin.

651
00:49:12.205 --> 00:49:13.585
Yeah. There's also that.

652
00:49:14.365 --> 00:49:16.685
You could generate your own shitcoins on,

653
00:49:17.645 --> 00:49:26.750
like, liquid, when when are we gonna do the Citadel dispatch coin? You know what I mean? This is this is liquid this is liquid on that pool space right now.

654
00:49:27.530 --> 00:49:31.585
Like, the blocks do happen quicker, so you have to give them that. Like, like 2 transactions

655
00:49:31.965 --> 00:49:32.705
per block.

656
00:49:33.005 --> 00:49:34.385
Fucking ghost tab.

657
00:49:34.845 --> 00:49:35.345
Man.

658
00:49:38.320 --> 00:49:42.480
Well, that's pretty crazy. That is just said. Let's see what happens if,

659
00:49:43.119 --> 00:49:48.205
you know, once this gets integrated with it all the way and and see how that pans out.

660
00:49:48.585 --> 00:49:56.460
That could go a long way. But I think it's also gonna take some of the other centralized exchanges to be running it for things to really take off.

661
00:49:58.280 --> 00:50:03.195
Yeah. I mean, we had fee spike, and still pretty much no one used it. I don't know. We'll see. I I I think

662
00:50:03.815 --> 00:50:12.950
I think it's, it's a lot more user friendly for for a new user because they don't have the channel management. I think that's the main thing it does going for it. I don't get the whole trader thing,

663
00:50:14.610 --> 00:50:18.505
because I I think the trader thing can get solved with private lightning channels. But,

664
00:50:20.825 --> 00:50:23.164
Yeah. I digress. I'm just, so

665
00:50:24.505 --> 00:50:28.880
so, Fiat, Jeff, you started working with, our friends over at Zebedee,

666
00:50:29.660 --> 00:50:31.440
when from in December. Right?

667
00:50:31.980 --> 00:50:32.480
Yeah.

668
00:50:33.180 --> 00:50:37.984
So we had to the freaks that that remember, we had Andre Neves on the show,

669
00:50:39.325 --> 00:50:41.345
CEO and cofounder of Zebedee

670
00:50:42.445 --> 00:50:44.625
4 episodes ago or 5 episodes ago.

671
00:50:47.330 --> 00:50:51.910
So the the the focus over there is is putting stats and lightning into games.

672
00:50:53.954 --> 00:50:54.454
Yeah.

673
00:50:55.234 --> 00:50:58.595
Do you wanna dive into that experience at all? Like, what do do you think

674
00:51:01.320 --> 00:51:14.955
is it as natural of a fit as we think it is? Like, are are is that is that do you think it's safe to say that most Zoomers are gonna start using Sats in video games before they use them anywhere else? Oh, I I don't know. I don't understand the Zoomers.

675
00:51:18.190 --> 00:51:20.369
I don't play with games very much also,

676
00:51:20.910 --> 00:51:23.810
but I think that's that that has potential, and

677
00:51:24.165 --> 00:51:24.665
I

678
00:51:25.205 --> 00:51:26.665
don't think it's as easy.

679
00:51:27.205 --> 00:51:32.025
I I I've heard you say before, like, that you just wanna lose sets to some

680
00:51:33.079 --> 00:51:37.320
some Asian guy that kills you. But I'm not sure that the incentives

681
00:51:38.280 --> 00:51:40.135
the incentives are that perfect.

682
00:51:40.595 --> 00:51:45.895
The the the the sets change the the incentives. So you have to you have to change the game a little, like, to

683
00:51:46.275 --> 00:51:46.775
accommodate.

684
00:51:47.460 --> 00:51:51.300
Like poker is a a good game with that could be played with sets because

685
00:51:52.020 --> 00:51:53.560
with money of any kind

686
00:51:54.099 --> 00:51:57.675
because the the the money is inside the game. It's not just

687
00:51:58.055 --> 00:51:59.675
the the winner takes all.

688
00:52:01.975 --> 00:52:09.080
Like, the the bluffing and putting putting money on the table, that's a part of the game. And I think putting sets inside games

689
00:52:09.380 --> 00:52:16.875
has to be done in that way too. Like, the the the first version of the Infuze CS GO thing, it was just the winner takes more sets.

690
00:52:17.335 --> 00:52:25.730
But then we added that coin. I don't know if you saw it, but when you when you kill someone, they left the sets in the form of a coin in the map. So that changed the incentives

691
00:52:26.109 --> 00:52:37.355
because if you go rushing to to pick up the coins, you expose yourself. And so that kind of changes in the game. I think that that's what makes Yeah. I love that. It's like,

692
00:52:37.815 --> 00:52:43.035
if you play Call of Duty, it's like kill confirmed. Like, you gotta pick up the tags left behind.

693
00:52:43.920 --> 00:52:45.220
Otherwise, it doesn't count.

694
00:52:46.000 --> 00:52:47.140
So But, yeah,

695
00:52:47.440 --> 00:52:53.060
really awesome to see you guys think of new game modes and and rolling them out. I need to play that one personally.

696
00:52:55.165 --> 00:52:56.705
Yeah. But I'm I'm hopeful.

697
00:52:57.405 --> 00:52:59.665
I I don't see very much the

698
00:53:00.125 --> 00:53:01.670
customer side of it. But

699
00:53:02.549 --> 00:53:03.369
Well, the consumers

700
00:53:03.670 --> 00:53:13.215
I mean, look. You said you're not a gamer. The consumers right now, like, these guys these people spend so much money on gaming already. It's like you automatically are losing money in gaming.

701
00:53:13.835 --> 00:53:18.655
It's just if you add if you add stats rewards, then you might make money as well.

702
00:53:19.119 --> 00:53:21.700
Like, there might be, like, a a way to make money.

703
00:53:23.599 --> 00:53:27.380
And and, I mean, the example that I always say, I mean, you brought it up, poker,

704
00:53:27.914 --> 00:53:30.815
is, like, fucking poker without money sucks.

705
00:53:31.355 --> 00:53:37.819
Like, I will not sit down to play poker for 4 hours without money now. I'm an adult. Okay? That's something that we did you did as children.

706
00:53:38.359 --> 00:53:44.380
Now that you're an adult, you wanna play you wanna play with cash. Otherwise, it's not it's not fun. And I think

707
00:53:44.875 --> 00:53:46.575
once you start having good games

708
00:53:47.115 --> 00:53:49.135
that have this, like, built in natively,

709
00:53:50.555 --> 00:53:54.335
where, you know, if you spend 2 hours, you have real money on the line,

710
00:53:55.339 --> 00:53:59.180
it's just gonna kinda ruin all the games that don't have it. It's just like, why would you

711
00:54:00.460 --> 00:54:02.400
there'll still be, like, a place for

712
00:54:02.715 --> 00:54:04.575
the single player epic games,

713
00:54:05.435 --> 00:54:10.735
where, you know, you just wanna, like, lose yourself for 5 hours, 6 hours, and escape reality,

714
00:54:11.130 --> 00:54:15.390
and there'll be no money in those. But, when it comes to the competitive shit,

715
00:54:16.010 --> 00:54:21.755
you know, people are gonna wanna I'm gonna wanna play I wanna play the game that I have skin in the game or actually have

716
00:54:22.055 --> 00:54:23.355
have stats on the line.

717
00:54:25.895 --> 00:54:38.704
Yeah. No. The the pro the problem is that if you're not the best player in the world, then you're gonna face the best player because they wanna take your sets. And then the game won't be fun because you wanna play with your level. That issue. Your level.

718
00:54:39.404 --> 00:54:54.005
Do they So, like, so, like, Fortnite is a perfect example. So Fortnite in the beginning, you would just get, like look. I'm not you know, the best gamers in the world are 14 years old, and they, like, their fingers just twitch organically with whatever they're doing.

719
00:54:54.465 --> 00:54:56.065
They don't even think when they play.

720
00:54:56.785 --> 00:55:11.555
So, like, in the beginning of Fortnite, we just used to get our asses kicked. And then they they added a system, you know, where, like, there's, like, a ranking system, like, a reputation system. Right? And and you'd now I can actually win because they only put me with the shitty players. Mhmm. Mhmm.

721
00:55:11.855 --> 00:55:16.755
So, like, that's I don't think that's like, that's just good game mechanics. Right? Like, that's not,

722
00:55:17.570 --> 00:55:23.830
like, period. Even if there's no sats on the line, if you just play a game where you just die instantly all the time, like, that's not a fun game.

723
00:55:25.015 --> 00:55:29.914
Yeah. Yeah. But the the problem is that peep most people want to play with people that are on their level,

724
00:55:30.295 --> 00:55:31.515
so the game is interesting.

725
00:55:31.870 --> 00:55:36.610
The the best player doesn't don't want to play with the worst player because it won't be found.

726
00:55:37.230 --> 00:55:45.095
But if they they want they're playing to get the money, then they want play with the worst player possible, so they get the the sets from that that guy.

727
00:55:45.635 --> 00:55:47.655
So there's there's an, conflicting

728
00:55:48.115 --> 00:55:54.090
incentive there that must be solved. But once you solve that, the games do become more interesting, I think.

729
00:55:55.670 --> 00:56:01.665
And, I mean, the other thing that you guys are dealing with on the fly and something we talked about on the on the show with Andre,

730
00:56:04.525 --> 00:56:06.225
is this idea,

731
00:56:09.329 --> 00:56:14.790
you know, is the is the user friendly nature of the wallet. Right? You guys have opted for a custodial wallet over there.

732
00:56:16.965 --> 00:56:20.905
Is this something you battle with? Like, I assume you guys would prefer to move to a noncustodial

733
00:56:21.285 --> 00:56:22.425
if possible. Right?

734
00:56:24.325 --> 00:56:25.385
I'm not sure.

735
00:56:26.789 --> 00:56:30.010
Yeah. I would prefer to move to a hosted channel model,

736
00:56:31.510 --> 00:56:37.215
but but I I don't know. The the people that play, I have the I'm not sure, but I have the impression that

737
00:56:38.075 --> 00:56:46.880
they want to be, like, the guy who just cares about playing games or whatever, forever kind. It's hard for that same person to be interested in running

738
00:56:47.420 --> 00:56:47.920
channels

739
00:56:48.539 --> 00:56:49.680
and so on. So

740
00:56:50.859 --> 00:56:54.904
maybe Black Personal will move to another wallet that has that capability.

741
00:56:55.365 --> 00:57:02.025
But for all the for the Zoomers that don't don't care about anything, they they should use the the so the wallet.

742
00:57:04.540 --> 00:57:09.760
It it shouldn't matter, though, because, like, you can just use whatever wallet to pay the invoices again. Yeah. That Right?

743
00:57:10.335 --> 00:57:17.154
Yeah. That that's the that's the the thing. What what's the only requirement? Like, you gotta do, l and u or l pay to get paid out

744
00:57:17.660 --> 00:57:18.640
For withdraw.

745
00:57:19.339 --> 00:57:21.819
Yeah. Yeah. Yeah. Okay. Because it still means

746
00:57:22.140 --> 00:57:25.265
you're still sitting on a custodial wall till you withdraw. Yeah.

747
00:57:26.684 --> 00:57:33.904
Yeah. The I mean, the main issue of a custodial wall is is KYC regs. You know? It's the same thing we were talking about, that friction.

748
00:57:34.204 --> 00:57:34.704
And,

749
00:57:35.150 --> 00:57:43.890
you know, Zebedee has, like they have different limits. They have different levels for what level of KYC you do. Mhmm. So lower amounts, it's not, like, horrible.

750
00:57:46.085 --> 00:57:49.705
But, I mean, I think, ultimately, the goal's gotta be to move to a noncustodial

751
00:57:50.085 --> 00:57:55.369
thing so that you can open it up to more users. I mean, we had Sputnik on the same show,

752
00:57:55.750 --> 00:57:58.250
and he has Bitcoin Bounty Hunt, and he was like,

753
00:57:59.190 --> 00:58:12.800
you you know, he made his game like a proper BitCorner originally. And, like, every if when you installed it, it installed a full lightning node on your computer. Jeez. And, like, he had bottleneck issues real quick. And and the other thing is

754
00:58:13.100 --> 00:58:18.545
is in a high fee environment. Right? Like, if you have to open a channel for someone, you're hitting the chain.

755
00:58:19.165 --> 00:58:20.045
Right? That could be,

756
00:58:20.845 --> 00:58:22.224
you know, if if

757
00:58:22.765 --> 00:58:29.310
if block space if but the block space is not gonna increase, I I'd be very surprised if, you know, we have block size increase.

758
00:58:30.089 --> 00:58:33.710
So if that's the case, you know, we could be looking at a $100, a $150

759
00:58:35.195 --> 00:58:39.355
main you know, on chain transaction fees to open a channel. Like, how could you ever have,

760
00:58:41.115 --> 00:58:44.460
anything under that amount has gotta be custodial. Otherwise, you're just

761
00:58:45.420 --> 00:58:46.320
burning money.

762
00:58:46.700 --> 00:58:47.520
Yeah. Absolutely.

763
00:58:48.140 --> 00:58:53.775
Yeah. Yeah. Yeah. I mean, to be sovereign, to have your own channels, there's a cost to it. And,

764
00:58:54.335 --> 00:59:00.595
that's that's one of the bigger problems here. It's like that and and the convenience of, you know, not having to manage your channels.

765
00:59:03.220 --> 00:59:09.000
These channels are so fragile. They close for you should touch them, they close, and then you lose a ton of money.

766
00:59:10.704 --> 00:59:17.525
These things worry me. There's a lot of things that I feel like are just hidden because developers are just eating the cost right now to build

767
00:59:18.120 --> 00:59:20.220
to, like, build out the user base. Right?

768
00:59:20.680 --> 00:59:25.020
Like, Moon Wallet is a perfect example. Like, Moon Wallet's UX is fucking fantastic.

769
00:59:26.005 --> 00:59:34.025
But, like, I don't know how they're doing it without just burning a shit ton of money. They they are. I mean, they I think they're spending a lot of money for user acquisition costs,

770
00:59:34.510 --> 00:59:35.330
And I think

771
00:59:35.630 --> 00:59:40.050
that the mix of, you know, these user these companies figuring out, like,

772
00:59:41.070 --> 00:59:44.585
their flows and how much they want to spend for this user acquisition

773
00:59:45.365 --> 00:59:46.505
versus also,

774
00:59:47.045 --> 00:59:51.560
you know, dealing with the custodial wallets and, you know, dealing with potential

775
00:59:51.940 --> 00:59:52.440
impending,

776
00:59:53.780 --> 00:59:54.680
you know, regulations

777
00:59:54.980 --> 00:59:56.200
and risk there. Like,

778
00:59:57.695 --> 00:59:59.315
a whole bunch of the wallets

779
00:59:59.695 --> 01:00:04.515
that we know and use today might not look the same in even, say, a year's time.

780
01:00:06.730 --> 01:00:10.590
Well, when when the Bitcoin Hyperbit connection happen,

781
01:00:10.970 --> 01:00:12.510
all these issues will vanish.

782
01:00:12.905 --> 01:00:15.885
So we just have to survive until that point.

783
01:00:17.545 --> 01:00:26.120
Yeah. That's true. At least, we're seeing a lot of innovation and, you know, not even 3 months ago, I don't think people were using Mona's mantra. It it wasn't really talked about.

784
01:00:26.580 --> 01:00:30.520
So things are moving really rapidly as far as these custodial and

785
01:00:31.155 --> 01:00:33.255
semi, in quotes, semi custodial

786
01:00:33.555 --> 01:00:34.535
wallets are going.

787
01:00:35.155 --> 01:00:37.734
So, I think there's still a lot of room for experimentation,

788
01:00:38.035 --> 01:00:39.655
and that that's what's happening.

789
01:00:40.470 --> 01:00:45.910
But, you know, don't don't expect things to stay the same or even for your favorite wallet to stick around,

790
01:00:46.550 --> 01:00:57.484
in, say, 2 years. But just to be clear here, that's when we say Moon Wallet, we mean m u u n. Yep. Hopefully, they will change their name so I don't have to fucking say how to spell it every time. But,

791
01:00:59.690 --> 01:01:05.070
what is Moon Moon Wallet with an o? Is there the Yeah. There's a custodial.

792
01:01:05.610 --> 01:01:07.715
Yeah. Yeah. Custodial. Right?

793
01:01:09.235 --> 01:01:11.415
Yeah. I think so. I haven't used their product.

794
01:01:15.635 --> 01:01:16.375
Have you,

795
01:01:17.500 --> 01:01:21.120
yeah. Yeah. So, yeah, I I agree. This this is, like, a heavy competitive

796
01:01:21.500 --> 01:01:25.440
market right now for lightning wallets, and and most of them will probably not survive.

797
01:01:27.805 --> 01:01:31.585
But it should be interesting to see how the whole high fee environment works,

798
01:01:32.445 --> 01:01:36.590
with lightning because I feel like it hasn't really been stress tested under that environment yet.

799
01:01:37.950 --> 01:01:38.030
The

800
01:01:39.550 --> 01:01:44.990
and, like, it barely did, like, 2 weeks ago or 3 weeks ago, but I feel like people just stopped doing things. They

801
01:01:54.740 --> 01:01:55.720
talking about

802
01:01:56.180 --> 01:02:01.240
how, ranking systems suck because we're talking about video game ranking systems, and it reminded me

803
01:02:02.875 --> 01:02:03.375
because,

804
01:02:04.715 --> 01:02:09.455
you know, Lightning Labs released this new tool that can let you explore your boss score

805
01:02:09.994 --> 01:02:10.815
last week,

806
01:02:11.820 --> 01:02:17.200
and it's still closed. I it's not open. Like, we don't know how they classify things.

807
01:02:17.740 --> 01:02:20.485
And I, like, tweeted at them in, like, all caps,

808
01:02:21.605 --> 01:02:23.145
because I have, like, 250

809
01:02:23.445 --> 01:02:27.650
peers on that note. And they were, like, 0 of 250 are good peers.

810
01:02:28.369 --> 01:02:33.510
And I was like, you never fuck it. You talk shit about my peers like this, and I'll never forget it.

811
01:02:34.130 --> 01:02:41.005
And and my boss score, like, moved up, like, a 100 points or 200 points after that, and I've got, like, 7 good peers now.

812
01:02:41.705 --> 01:02:43.405
So what you're telling us

813
01:02:43.865 --> 01:02:47.830
is that Oz is the wizard behind the green curtain, and he's just

814
01:02:48.370 --> 01:02:49.910
changing things as he wants.

815
01:02:51.090 --> 01:02:55.325
Yeah. We we need to get buzz on the show. We have too many questions.

816
01:02:55.704 --> 01:02:58.615
If this score if this score is the name of a person.

817
01:02:59.120 --> 01:03:01.940
We we need to try to get as many tips out of him as possible.

818
01:03:03.680 --> 01:03:09.165
If this score has the name of a person, you assume that person is manually requesting that ranking.

819
01:03:11.065 --> 01:03:16.285
But, technically, it stands for balance of satoshis. It has nothing to do with his name. That's just a coincidence.

820
01:03:17.039 --> 01:03:20.660
I think it stands for his name too, but he made balance of Satoshis.

821
01:03:21.200 --> 01:03:27.515
No. I'm aware. It's it's a running joke in here. I think one of the reasons my boss score was bad was because we proposed an Odell score.

822
01:03:29.895 --> 01:03:32.155
Yeah. Competing score. That's minus 500.

823
01:03:34.740 --> 01:03:36.680
Yeah. I think you should do it.

824
01:03:38.500 --> 01:03:40.180
But, yeah, I mean, I think we need

825
01:03:41.455 --> 01:03:44.595
like, so what are you what are your thoughts on, like, reputation systems,

826
01:03:45.455 --> 01:03:49.395
for lightning notes? Like, this is this this is something that's essential. Right?

827
01:03:51.060 --> 01:03:51.560
Yeah.

828
01:03:52.100 --> 01:03:59.845
I I like reputation systems. I just don't know how to do them. It's always very hard. Like, a a global ranking is is not

829
01:04:00.805 --> 01:04:02.505
maybe for lightning nodes, it's good.

830
01:04:04.405 --> 01:04:05.325
But the

831
01:04:05.785 --> 01:04:07.145
generally, like, the the

832
01:04:07.650 --> 01:04:08.950
graph of reputation,

833
01:04:09.490 --> 01:04:14.070
I think it works better, but also much harder to build for the stuff.

834
01:04:14.735 --> 01:04:17.635
For Lightning nodes, I the thing I I like about

835
01:04:18.175 --> 01:04:22.355
the thing I wanted to see is, like, if a peer is closing channels

836
01:04:23.000 --> 01:04:23.500
because

837
01:04:23.880 --> 01:04:24.700
I hate that.

838
01:04:25.160 --> 01:04:25.660
And

839
01:04:26.280 --> 01:04:27.000
also failing

840
01:04:27.640 --> 01:04:32.825
I don't know what they what they measure that, but they probably don't measure if the peer is closing channels because

841
01:04:34.585 --> 01:04:42.605
I don't know. You you can't know if why a a channel was closed in unless you're watching the logs and understanding all the internals.

842
01:04:43.310 --> 01:04:45.650
So I think that's information is not public.

843
01:04:46.830 --> 01:04:47.970
Yeah. I don't know.

844
01:04:48.350 --> 01:04:50.815
Yeah. It's tricky right now. There's just so many different metrics,

845
01:04:51.295 --> 01:04:53.954
out there, and it's hard to weigh them versus each other.

846
01:04:54.734 --> 01:04:55.555
I think it's,

847
01:04:56.255 --> 01:05:02.830
you know, that that's pretty much why the metrics for BOS aren't public. I think they're still getting ironed out.

848
01:05:04.090 --> 01:05:07.215
You know, even a heavy router like BOS is still trying to figure out

849
01:05:07.695 --> 01:05:08.435
which metrics

850
01:05:09.375 --> 01:05:18.599
together or on their own are most valuable and should be weighted the most. And, yes, it's gonna take a good amount of time more. We're we're gonna need more routing on the network.

851
01:05:19.460 --> 01:05:25.045
And, you know, what what may be a good peer for one person might not necessarily be a good peer for another.

852
01:05:25.505 --> 01:05:28.405
I think a lot of that really depends on

853
01:05:29.345 --> 01:05:33.525
what your flows and the flows of your users are are really looking like.

854
01:05:33.830 --> 01:05:38.490
You know? Like, you wanna make sure that your liquidity is accommodating to the flows that your users

855
01:05:39.110 --> 01:05:41.290
are going through on a regular basis

856
01:05:41.775 --> 01:05:43.155
more so than anything else.

857
01:05:47.055 --> 01:05:47.555
Yeah.

858
01:05:49.150 --> 01:05:52.130
So I have the tweet I pulled the tweet up just because it's fucking hilarious.

859
01:05:55.550 --> 01:05:55.870
The

860
01:05:56.415 --> 01:06:02.575
I mean, I you you mentioned something that was interesting there, Fiat, Jeff. I mean, like, right now, like, it's so

861
01:06:03.375 --> 01:06:04.675
we don't even know,

862
01:06:08.829 --> 01:06:12.609
like, it's so experimental. Like, you can't really like, I have

863
01:06:13.069 --> 01:06:16.235
I have, at least on l and d, like, I'll just have

864
01:06:16.615 --> 01:06:19.755
channels just get closed that I didn't close,

865
01:06:20.295 --> 01:06:21.275
that were just,

866
01:06:22.020 --> 01:06:22.760
you know,

867
01:06:23.460 --> 01:06:25.000
they they they just closed themselves.

868
01:06:25.860 --> 01:06:29.560
And I don't believe that they I at first, I didn't believe they closed themselves,

869
01:06:31.815 --> 01:06:32.315
except

870
01:06:32.855 --> 01:06:39.434
I saw, like, a couple channels closed that, like, were with people that, like, I really trusted, and they, like, swore to me that they didn't close the channel.

871
01:06:40.295 --> 01:06:43.440
Yep. So, like, there's, like, phantom closes happening.

872
01:06:44.859 --> 01:06:48.960
A tour, like, should be Especially when you have that tour only?

873
01:06:49.295 --> 01:06:53.555
Yeah. I I think a lot of people have a lot of issues with that, getting bad circuits.

874
01:06:54.095 --> 01:06:55.395
So this is a screenshot

875
01:06:55.695 --> 01:06:59.900
this is a screenshot from last week, May 11th. Right? And here's the screenshot from today.

876
01:07:02.680 --> 01:07:07.100
How do you jump up so much? Like, I'm green. I'm good. I'm not unstable anymore.

877
01:07:09.285 --> 01:07:12.905
Oh my god. The buzz slider, man. Pretty fucking funny, man.

878
01:07:13.285 --> 01:07:16.825
And they they have way I have way more peers than 176, but whatever.

879
01:07:17.690 --> 01:07:21.390
Yeah. The Tor thing is interesting. Right? Because, like, if you're talking about

880
01:07:24.375 --> 01:07:30.315
if you're talking about sovereign lightning nodes, right, like, they should be running Tor only. But if you're gonna talk about uptime,

881
01:07:33.410 --> 01:07:39.109
you know, obviously, you'd be better off if you're running in, like, Amazon's main server farm in Clearnet.

882
01:07:40.565 --> 01:07:44.345
Yeah. I I just see them as 2 different classes of nodes. It's like you're either,

883
01:07:44.964 --> 01:07:48.184
you know, really into the routing and you're willing to

884
01:07:48.740 --> 01:07:51.000
make yourself public facing on Clearnet

885
01:07:51.700 --> 01:07:56.040
or you're more so catering yourself towards personal use and privacy.

886
01:07:56.815 --> 01:07:57.295
And,

887
01:07:57.775 --> 01:08:03.555
Yeah. I I think they're very much different, and they come with their own unique set of challenges. And,

888
01:08:04.059 --> 01:08:06.319
you know, they're not gonna perform the same,

889
01:08:06.700 --> 01:08:09.280
under the same conditions just because of that network,

890
01:08:09.740 --> 01:08:10.240
alone.

891
01:08:14.744 --> 01:08:15.565
Fucking hilarious.

892
01:08:17.545 --> 01:08:18.045
So,

893
01:08:19.000 --> 01:08:24.380
so last week, I accidentally or maybe 2 weeks ago, I accidentally said that you were,

894
01:08:25.480 --> 01:08:26.300
the maintainer

895
01:08:26.679 --> 01:08:29.865
of Fiat Jaffe. I said you were the maintainer of this Immortan,

896
01:08:30.765 --> 01:08:32.185
I guess, lightning implementation,

897
01:08:33.525 --> 01:08:34.505
which you aren't.

898
01:08:35.090 --> 01:08:44.285
But do you wanna talk about it? Like, you're one of the I I you're the one who brought it to my attention. So Do we know for sure, though? I mean, Fiat Jaff is a NIM. Okay?

899
01:08:44.685 --> 01:08:45.185
So,

900
01:08:45.485 --> 01:08:47.105
like, who's to say for sure?

901
01:08:48.525 --> 01:08:49.025
Well,

902
01:08:49.645 --> 01:08:52.625
I would I would love to be the author of this, but, I'm not.

903
01:08:56.110 --> 01:09:03.325
And, well, I can't I can't speak. You you should try to get Anton here on the show on the show, but he he won't give interviews to anyone, I think.

904
01:09:05.165 --> 01:09:06.385
So I'm I'm trying my best.

905
01:09:07.325 --> 01:09:08.865
The the idea is that,

906
01:09:09.485 --> 01:09:12.225
like, the POW was a was a

907
01:09:12.610 --> 01:09:15.910
custom implementation tool. People say it was based on a clear,

908
01:09:16.450 --> 01:09:17.670
like, open on Saturday

909
01:09:18.210 --> 01:09:19.110
last week, but,

910
01:09:19.570 --> 01:09:20.895
it it isn't really.

911
01:09:21.375 --> 01:09:29.955
It it he just took the the cryptographic functions and encoding functions from a clear, but all the the logic, the lightning logic is is custom.

912
01:09:30.330 --> 01:09:32.590
And he's doing it again on Immorton.

913
01:09:34.250 --> 01:09:35.390
Basically, he says,

914
01:09:36.250 --> 01:09:44.285
Immorton has 2 difference, 2 key differences from from the BOW. 1 is that it has hosted channels, like, in a more prominent

915
01:09:44.905 --> 01:09:45.405
space.

916
01:09:46.265 --> 01:09:46.765
And

917
01:09:47.400 --> 01:09:52.380
the hosted channels on on BLW, like, the v one hosted channels, they were just

918
01:09:53.080 --> 01:09:53.820
on the

919
01:09:54.255 --> 01:09:55.554
on the edges of

920
01:09:55.934 --> 01:09:59.875
you you you only have a hosted channel between your BOW and a nuclear server.

921
01:10:00.655 --> 01:10:08.500
And with Martin, he created a parallel network of hosted channels that can route payments. So you can have,

922
01:10:08.960 --> 01:10:09.780
2 Eclairs

923
01:10:10.080 --> 01:10:11.780
and a hosting channel between them,

924
01:10:12.365 --> 01:10:14.705
and they can sit in the middle of a route,

925
01:10:15.085 --> 01:10:17.265
and you can initiate a a payment

926
01:10:17.645 --> 01:10:19.665
from your Immorton based wallet

927
01:10:19.965 --> 01:10:25.480
that passes through that hosted channel. You can't advertise that channel on the on the global

928
01:10:25.780 --> 01:10:27.960
channel lightning channel graph because,

929
01:10:29.220 --> 01:10:29.960
it requires

930
01:10:30.340 --> 01:10:36.075
the the the the protocol requires you to have an on chain utic so for that. But he made a

931
01:10:37.015 --> 01:10:41.340
separate gossip mechanism for to announce these channels, and, the Immorta wallet

932
01:10:42.280 --> 01:10:49.180
understands that. And also the eclair hosted channels plug in understand that. So they they know about the channel. Once you know that

933
01:10:56.645 --> 01:11:00.300
thing, Like, he's very he loves trampoline routing now.

934
01:11:02.599 --> 01:11:04.139
And using trampoline routing,

935
01:11:05.304 --> 01:11:06.684
one one note can

936
01:11:07.385 --> 01:11:12.764
outsource. Like, they can they can route a payment through your immortal mobile wallet.

937
01:11:13.090 --> 01:11:15.349
So if your if your mobile wallet is online,

938
01:11:16.690 --> 01:11:18.150
you'll connect to a node,

939
01:11:19.090 --> 01:11:22.389
and the node if the node understands that trampoline thing,

940
01:11:23.125 --> 01:11:25.304
they can route the payment through through you

941
01:11:25.605 --> 01:11:26.665
to another place,

942
01:11:27.125 --> 01:11:32.105
like, using another channel you your mobile wallet has. So it's good for the beer

943
01:11:32.540 --> 01:11:33.040
that

944
01:11:33.500 --> 01:11:39.760
they if it it can be like a hosted channel or a normal channel between the the immortal node and the

945
01:11:40.105 --> 01:11:40.605
server.

946
01:11:41.705 --> 01:11:47.085
It's good for the peer that the sets don't get stuck in that channel because on a normal,

947
01:11:47.785 --> 01:11:49.325
on a normal mobile wallet,

948
01:11:50.090 --> 01:11:52.670
if someone opens a channel to that wallet or

949
01:11:53.210 --> 01:12:00.475
the the wallet opens a channel to to that to that note, the sets, they they're stuck there. Like, between your Breeze Wallet and the Breeze

950
01:12:02.295 --> 01:12:06.395
server, there's a channel, and the Breeze server has sets on that channel,

951
01:12:06.900 --> 01:12:13.560
but they can't get the sets out unless they close the channel. So they they're there. But if using this this technique,

952
01:12:14.020 --> 01:12:15.639
you can send a payment

953
01:12:16.525 --> 01:12:22.705
from the server to the wallet and then to elsewhere. So you can clean up your your sets from that channel.

954
01:12:23.244 --> 01:12:24.784
Anyway, I hope that's clear.

955
01:12:25.550 --> 01:12:27.570
So that these 2 big improvements.

956
01:12:27.950 --> 01:12:29.970
Also also the ability to

957
01:12:30.510 --> 01:12:32.690
I'm not sure this is doable right now.

958
01:12:33.150 --> 01:12:34.130
Actually, it is.

959
01:12:34.625 --> 01:12:36.965
Like, the ability to the ability to

960
01:12:38.625 --> 01:12:43.125
send a payment that passes through a private channel and then goes on,

961
01:12:43.650 --> 01:12:45.510
that breaks the the heuristic,

962
01:12:46.770 --> 01:12:53.025
that's like a private channel is always the end of the payment because you don't know maybe now that payment will still go on.

963
01:12:53.824 --> 01:13:00.405
So it's good for privacy, very good for privacy. Drake's one of the big problems of Lightning privacy that Anthony

964
01:13:01.470 --> 01:13:02.290
talked about.

965
01:13:02.830 --> 01:13:03.730
Well, I mean,

966
01:13:04.590 --> 01:13:05.470
to break it down

967
01:13:06.990 --> 01:13:08.290
so so,

968
01:13:08.675 --> 01:13:10.535
basically, all of our Lightning implementations

969
01:13:11.235 --> 01:13:13.495
so far have been focused on,

970
01:13:15.395 --> 01:13:19.250
full node users, This idea that you use your own node, and it's almost like

971
01:13:20.270 --> 01:13:33.275
after the fact, after like, a second tier of user is the user who's gonna be a light user, and, you know, we'll make these different trade offs to to make that possible for them to use it without their own node. While Immortan seems like

972
01:13:34.370 --> 01:13:39.030
just an acceptance that not every user is gonna use their own node, so there should be a

973
01:13:39.490 --> 01:13:47.405
implementation that's focused on on light users, users that aren't using their own node. Right? Like, from the ground up, it should be focused on that and those trade offs.

974
01:13:48.329 --> 01:13:52.590
I wouldn't say that users that use your own node, but, like, the lightning

975
01:13:53.369 --> 01:14:03.505
implementation are focused on servers, I think. Right. Those nodes are online all the time. And then they they they realized you could have Lightning note wallets on on phones.

976
01:14:04.680 --> 01:14:07.980
But I think, like, BOW lets you use your own Bitcoin node.

977
01:14:09.000 --> 01:14:14.875
By default, it doesn't, but you can point to your own Bitcoin node. Maybe Mortem will too.

978
01:14:15.735 --> 01:14:21.040
So, yeah, you can still use your your own node, but it's focused on the the lite mobile

979
01:14:22.060 --> 01:14:22.560
wallet.

980
01:14:25.905 --> 01:14:26.405
So,

981
01:14:29.744 --> 01:14:33.045
Evan, you you have any comments here before we move on from a modem?

982
01:14:34.730 --> 01:14:48.275
No. I'm just really looking forward to it coming out and people being able to mess around with it. So definitely something I would explore and then wanna play around with. I know a lot of people wanna get some white client wallet rolling.

983
01:14:49.700 --> 01:14:53.080
It's exciting. It might be a really good solution alongside,

984
01:14:53.700 --> 01:14:56.920
you know, rolling your own L and D or messing with rust lightning.

985
01:14:58.055 --> 01:15:02.875
Yeah. We we'd really love to play around with it. I mean, it's interesting. Right? Because, like,

986
01:15:05.610 --> 01:15:10.430
I mean, there's, like, roles to play for all these things. I mean, I run I I run 2 247

987
01:15:11.450 --> 01:15:13.950
Lightning nodes. I use Zeus to connect to them.

988
01:15:14.765 --> 01:15:23.680
But at the end of the day, like, if I'm gonna accept a quick payment or something, like, I I prefer to use Moon. Like, it's just it's just cleaner. I like that it's just all built in. You know?

989
01:15:24.480 --> 01:15:31.060
And I feel like there's something to be said there about something like a Morden if if you have something that's literally designed for,

990
01:15:34.065 --> 01:15:42.165
basically, mobile users. Right? And then then I don't have to deal with, you know, my tour circuit working or any of that shit, and I can I can leave the heavy lifting

991
01:15:42.530 --> 01:15:45.110
for those notes at a different time if I want?

992
01:15:46.370 --> 01:15:51.430
Yeah. I mean, it's perfectly normal to have different, you know, risk profiles for different kinds of payments.

993
01:15:51.915 --> 01:15:56.575
You know what I mean? If I'm just trying to accept a cool $10, $20 at the bar from a friend,

994
01:15:57.035 --> 01:16:03.680
you know, there's nothing wrong with throwing that on a custodial wall. Right. I'm not gonna use my fucking routing node to fucking accept that payment. Like, that's ridiculous.

995
01:16:04.060 --> 01:16:09.760
And I'm gonna dox my public key to him, you know, at the same time. Yeah. Yeah. Yeah. Anyone that he shares it with by accident.

996
01:16:10.264 --> 01:16:13.724
Yeah. And, you know, things are constantly changing. It's gonna be easier

997
01:16:14.025 --> 01:16:22.889
with these new routing types to get receiver privacy, but, you know, things are are sort of hairy right now. So it's

998
01:16:23.190 --> 01:16:27.290
completely to normal to be using different wallets for different function.

999
01:16:28.185 --> 01:16:32.285
Do you think do you think lnbig is evil? And the fact that lnbig is sponsoring

1000
01:16:32.825 --> 01:16:34.605
Morten makes it evil too.

1001
01:16:36.610 --> 01:16:39.190
Oh, Ellen Bigg, not yeah. Ellen Bigg. Right?

1002
01:16:39.650 --> 01:16:40.150
Yeah.

1003
01:16:40.770 --> 01:16:46.230
I mean, I think it doesn't make him Morten evil, but it also doesn't make Ellen Bigg not evil.

1004
01:16:47.635 --> 01:16:49.095
Why do you think it's evil?

1005
01:16:49.795 --> 01:16:56.420
I mean, I'm not saying that Ellen Big is evil, but I'm saying that we should be skeptic like, I feel like there's a lot of Bitcoin promoters,

1006
01:16:57.040 --> 01:17:00.560
you know, on on Twitter and stuff. Like, look. I don't know if you guys can see,

1007
01:17:01.200 --> 01:17:06.344
on the top left hand corner, we can see, like, all the how many freaks are tuning in through the live,

1008
01:17:07.605 --> 01:17:08.344
live streams.

1009
01:17:08.804 --> 01:17:12.824
It shows the total number of freaks. I'm not sure if they show that to you. Do they show that to you?

1010
01:17:13.790 --> 01:17:16.130
I don't see it. Well, anyway,

1011
01:17:17.150 --> 01:17:20.450
when we were talking about Elon and the price and shit,

1012
01:17:20.805 --> 01:17:27.385
we were fucking 10 x where we are right now. Right? Like, when you get when you get, like, an hour and a half into, like, a technical conversation,

1013
01:17:28.805 --> 01:17:33.660
you only have the ride or dies left. And and and the hidden secret with Bitcoin

1014
01:17:34.600 --> 01:17:37.340
is, you know, if you if you care about engagement,

1015
01:17:38.025 --> 01:17:45.165
the two things that that work for you are either heavy fear or which doesn't even work as well, but the real thing that works

1016
01:17:45.545 --> 01:17:47.630
is just heavy bullishness. You just

1017
01:17:47.949 --> 01:17:55.969
you put bullishness on everything, which is why, like, this is a technical show, but I constantly reiterate in that Bitcoin is designed to pump forever. Right? Because you gotta tow the line.

1018
01:17:57.934 --> 01:18:01.715
But so so the issue is the the issue that you see is,

1019
01:18:03.215 --> 01:18:05.474
you see people ignore these things

1020
01:18:06.030 --> 01:18:08.050
that, you know, bingo, nuance

1021
01:18:08.590 --> 01:18:20.025
that that, you know, we should be critical of and we should be concerned about. And the big thing for me for a while and still is is that Ellen Big has, like, half the public capacity of the network.

1022
01:18:20.350 --> 01:18:21.810
It's a little bit less now,

1023
01:18:23.390 --> 01:18:33.255
and everyone just glosses that over when they're set talking about public capacity numbers. Right? And if you mix it with Ellen Big and then you do, like, the top 3 regulated KYC services

1024
01:18:33.875 --> 01:18:37.975
that are on lightning, right, then you're, like, 75% of the network's public capacity

1025
01:18:38.870 --> 01:18:45.910
are these, you know, the small group of of institutions, and we have no idea who LN Big is. So it could very well be

1026
01:18:46.615 --> 01:18:57.340
you know, I've heard people speculate and I really don't have any desire to speculate, but I've heard people speculate it's like a a rich Russian Bitcoiner who just wants to see the lightning network grow and is throwing a bunch of money in.

1027
01:18:57.960 --> 01:19:02.540
I respect that. That would be awesome. You know? I mean, I I'm not, you know,

1028
01:19:03.080 --> 01:19:13.244
I don't have his kind of money, and I'm not Russian, but I did similar with our stacking stats note. I just threw a shit ton of money into it, to just try and jump start the whole thing and encourage people to,

1029
01:19:13.600 --> 01:19:15.699
you know, experiment with these kind of things.

1030
01:19:16.239 --> 01:19:19.460
But at the end of the day, whoever this unknown entity is is running,

1031
01:19:19.920 --> 01:19:20.580
you know,

1032
01:19:21.034 --> 01:19:29.480
tens, like, 50 nodes all in from the same, like, server farm that's, like, in Langley, Virginia, like, right next to where the CIA's base is.

1033
01:19:30.920 --> 01:19:36.855
And and, like, there's only, like, 3 of us that call it out that's that ever fucking talk about it. No one talks about it.

1034
01:19:38.695 --> 01:19:40.715
So what you're saying is operate

1035
01:19:41.015 --> 01:19:42.875
as if Ellen Big is

1036
01:19:43.495 --> 01:19:43.995
CIA?

1037
01:19:44.810 --> 01:19:46.750
Or something, you know, something malicious.

1038
01:19:47.210 --> 01:19:55.265
I think I think you should I mean, not saying one way or the other for sure, but, yeah, why not make that presumption and stay on the the cautious

1039
01:19:55.805 --> 01:19:59.105
side? Like, when a morn comes out, we gotta review that code. Come on.

1040
01:20:01.325 --> 01:20:02.730
Yeah. And, like, the the

1041
01:20:03.030 --> 01:20:08.570
the analogy that I brought up in the the past is, like, tour is funded by 3 letter agencies. Right?

1042
01:20:09.555 --> 01:20:16.135
So it doesn't mean that, you know, Tor is inherently bad, but it doesn't make the 3 letter agencies any better for funding it.

1043
01:20:17.560 --> 01:20:20.220
I mean, they benefit off the anonymity

1044
01:20:20.920 --> 01:20:23.980
and the the anonymity set that it creates.

1045
01:20:24.360 --> 01:20:24.860
So

1046
01:20:26.485 --> 01:20:32.105
it makes sense. It doesn't really devalue it really if you could verify what it actually does, but,

1047
01:20:32.780 --> 01:20:36.560
you know Well, it does it does put into question it makes you think, like,

1048
01:20:37.020 --> 01:20:44.055
it makes a lot of sense that Tor is not, you know, designed for an environment where the US government is adversarial towards it.

1049
01:20:44.755 --> 01:20:48.215
Right? And, like, there there was never designed that way. And

1050
01:20:48.860 --> 01:20:53.599
I don't think it's a coincidence that, you know, the money behind it happens to be the US government. Right?

1051
01:20:54.300 --> 01:20:59.265
I mean, listen, well, we know the flaws in Tor. You know, anyone could set up these these

1052
01:21:00.365 --> 01:21:01.905
these output nodes. Right?

1053
01:21:03.645 --> 01:21:06.465
You know, that they could be just pound overnight. Right?

1054
01:21:06.845 --> 01:21:11.350
But we go do mostly, it it serves our purposes really well.

1055
01:21:12.050 --> 01:21:14.630
Well, anyway, that's my little rant on Ellen Bigg.

1056
01:21:16.735 --> 01:21:19.395
And we had Anthony in the comments defending them.

1057
01:21:20.015 --> 01:21:23.535
We should be more concerned about all the random nodes than Ellen Bigg. I've

1058
01:21:24.495 --> 01:21:24.995
why?

1059
01:21:27.350 --> 01:21:36.330
Yeah. I don't know. I'm very naive of these things. Like, it it looks like a Russian guy with money that wants to help Lightning, and I believe that

1060
01:21:36.935 --> 01:21:41.275
because I'm very naive. I also believe Satoshi Nakamoto is a young Japanese boy.

1061
01:21:44.855 --> 01:21:45.675
So that's

1062
01:21:47.460 --> 01:21:50.039
my imagination is it. It's very

1063
01:21:51.940 --> 01:21:52.440
Yeah.

1064
01:21:53.875 --> 01:21:55.255
Young Japanese boy.

1065
01:21:56.434 --> 01:21:58.775
I'm, I'm on board with that theory.

1066
01:21:59.715 --> 01:22:00.215
At

1067
01:22:01.155 --> 01:22:03.380
least we know, Ellen, but it's hard to

1068
01:22:18.605 --> 01:22:19.745
They're talking about Alan.

1069
01:22:20.500 --> 01:22:24.600
Yeah. Langley is just fucking with us. Yeah. You're coming in and out a little bit.

1070
01:22:27.355 --> 01:22:30.255
Yeah. It's it's absolutely because of talking about Allan Vic.

1071
01:22:30.875 --> 01:22:31.375
But,

1072
01:22:32.395 --> 01:22:35.375
yeah, I mean, as far as, like, connecting to a random node,

1073
01:22:36.390 --> 01:22:39.370
you know, can you hear me now? No. There we go.

1074
01:22:40.150 --> 01:22:41.050
Yeah. You're back.

1075
01:22:41.429 --> 01:22:42.650
I think. Apologies.

1076
01:22:43.245 --> 01:22:48.465
Yeah. We were disconnected. I was disconnected for a little while there, so I apologize to the freaks if if it was disjointing.

1077
01:22:49.885 --> 01:22:52.225
You on the satellite Internet this week, Matt?

1078
01:22:53.010 --> 01:22:54.550
Actually, don't answer that too.

1079
01:22:56.370 --> 01:23:01.750
We started talking about it again, and we used the Langley keyword, and then all of a sudden, everything just starts going down.

1080
01:23:02.985 --> 01:23:03.485
Yeah.

1081
01:23:04.665 --> 01:23:05.725
Or for the course.

1082
01:23:06.905 --> 01:23:10.284
If you keep disconnecting you, we won't invite you next week.

1083
01:23:10.679 --> 01:23:14.300
Yeah. Next time we got it, we'll invite some guests on. Don't worry, Matt.

1084
01:23:15.239 --> 01:23:16.619
We'll appreciate that.

1085
01:23:18.925 --> 01:23:28.545
Yeah. So, I mean, I I just want more conversation about Ellen Big. I just the the, you know, whatever. I'm not I'm not trying to be conspiratorily here, but I I just think, you know, if

1086
01:23:29.119 --> 01:23:36.500
you gotta discount you gotta at least discount the public capacity that's provided by LNB because it's all provided by a single entity. Right? So

1087
01:23:40.405 --> 01:23:40.905
let's

1088
01:23:41.445 --> 01:23:50.150
stay on the note of random nodes, though. And Anthony makes a pretty good point in that you sorta have to trust all your counterparties

1089
01:23:50.450 --> 01:23:51.670
on lightning. Right?

1090
01:23:52.290 --> 01:23:55.990
You're trusting them to not close your channel at an inconvenient time.

1091
01:23:56.325 --> 01:24:00.105
But, also, if you're routing payments through them and they're your first hop out,

1092
01:24:01.285 --> 01:24:02.344
they're gonna know,

1093
01:24:02.805 --> 01:24:05.310
you know, that's coming from you and

1094
01:24:05.929 --> 01:24:20.955
where it's going next. Right? So you're trusting them in that regard. Yeah. But they don't they don't know if you're the one originating that payment. No. No. They know that you're just passing something along. Yeah. But still, it adds up. If you end up using a route multiple times,

1095
01:24:21.920 --> 01:24:25.139
they can start, you know, creating a profile on you of some sort.

1096
01:24:26.159 --> 01:24:26.980
So while,

1097
01:24:28.159 --> 01:24:29.139
you have some

1098
01:24:29.465 --> 01:24:37.325
guarantees and that, you know, it's not necessarily coming from you, you could be another hop in the net. They could start still start making some assumptions about you.

1099
01:24:39.980 --> 01:24:44.000
So for the most part, I'd say on land, it's better to have counterparties that you trust.

1100
01:24:49.425 --> 01:24:49.925
Yeah.

1101
01:24:50.784 --> 01:24:53.685
Yeah. From multiple reasons, I think.

1102
01:24:55.870 --> 01:24:57.890
I mean, it's a little bit weird. Right? Because,

1103
01:24:58.430 --> 01:25:05.785
I mean, we were so I I feel like we were sold that it was, you know, that wasn't the case. Right? It was just it was, like, poor

1104
01:25:06.805 --> 01:25:07.945
expectation management.

1105
01:25:08.645 --> 01:25:10.825
I I think, like, big words like,

1106
01:25:11.285 --> 01:25:13.545
like, trustless in nature got

1107
01:25:14.590 --> 01:25:15.250
and whatnot.

1108
01:25:15.950 --> 01:25:20.690
And, also, things getting learned on the fly as we have this new experimental network

1109
01:25:21.265 --> 01:25:23.525
that really only been around, what, 3 years now.

1110
01:25:24.304 --> 01:25:28.245
We're still learning things, you know, every day, really, like new

1111
01:25:28.625 --> 01:25:29.870
Yes. And it's like,

1112
01:25:30.350 --> 01:25:35.650
hell, even Anthony's deep dive on privacy. Like, no one's really done that till since, you know, last week.

1113
01:25:36.110 --> 01:25:38.610
You know, this is a really nascent network, and

1114
01:25:39.645 --> 01:25:42.465
I wouldn't blame that part really much as, like,

1115
01:25:42.844 --> 01:25:46.704
you know, bad marketing or, like, fraudulent marketing like other product

1116
01:25:47.099 --> 01:25:52.239
products in the space have, but more so not really knowing all the constraints of it out the gate.

1117
01:25:54.195 --> 01:25:58.775
Touch touch dryer tells a story. I I heard him saying this on some podcast

1118
01:25:59.315 --> 01:25:59.815
that

1119
01:26:00.515 --> 01:26:05.740
like, touch dryer and Joseph Phung, I think, the the guys that invented the Light Net Network.

1120
01:26:06.360 --> 01:26:06.860
Uh-huh.

1121
01:26:07.720 --> 01:26:16.125
Yep. Desiree, like, he he he tells something like that. Joseph was very excited in saying that. I think he even says that in the original presentation,

1122
01:26:16.745 --> 01:26:18.845
the from 2,000 and 15,

1123
01:26:19.305 --> 01:26:22.285
that lightning network will allow us to route,

1124
01:26:22.719 --> 01:26:27.060
like, dozens of millions of, I don't know, a very large number and

1125
01:26:28.159 --> 01:26:31.860
made all that hype about it while while Tej was very

1126
01:26:32.495 --> 01:26:39.875
cultures and didn't he says he didn't really believe it was going to be such a such a powerful thing.

1127
01:26:40.310 --> 01:26:42.570
And then Josephine went to material.

1128
01:26:43.510 --> 01:26:44.250
So that's

1129
01:26:44.790 --> 01:26:47.050
common, like, expected behavior.

1130
01:26:47.665 --> 01:26:50.805
Yeah. I mean, we have NVK on the show a lot, and he's you know,

1131
01:26:51.185 --> 01:26:53.585
he makes an interesting point. I mean, I I don't know if it's

1132
01:26:55.260 --> 01:26:55.920
it's just

1133
01:26:56.300 --> 01:26:58.719
a lot of aspects of of the lightning ecosystem

1134
01:26:59.020 --> 01:27:01.039
feel a little bit shit coiny, you know,

1135
01:27:02.135 --> 01:27:04.695
or, like, less adversarial. It's it doesn't,

1136
01:27:05.175 --> 01:27:06.955
and that's not to degrade the

1137
01:27:07.575 --> 01:27:10.875
the devs who work on it all the time. I mean, I have so much respect,

1138
01:27:11.970 --> 01:27:16.710
for all the devs that are are contributing to lightning projects and making it more robust.

1139
01:27:18.610 --> 01:27:22.845
But it does it it's like the portion of Bitcoin that's, like, less adversarial. Right?

1140
01:27:23.385 --> 01:27:25.405
It's like our it's like our fun

1141
01:27:27.000 --> 01:27:37.035
sandbox where you can do all these different things and kinda you you know, hashtag reckless. Right? Like, imagine if, like, Bitcoin core devs were like, oh, run Bitcoin core, you know, hashtag reckless.

1142
01:27:37.575 --> 01:27:42.155
Like, that would be ridiculous. Like, leave all your funds in the hot wallet. You know what I mean?

1143
01:27:42.610 --> 01:27:51.910
But, no. I mean, listen. It's it's supposed to be your checking account. Right? This is their funds that you wanna be able to move at a moment's notice.

1144
01:27:52.515 --> 01:27:58.055
And, there's a trade off in the security model to accommodate for that. Yeah? Right. So

1145
01:27:58.915 --> 01:28:01.335
it's definitely not where you wanna have

1146
01:28:02.139 --> 01:28:08.835
the majority of your savings on. Right? You know, it's just like what you're trying to to move in your month or whatever

1147
01:28:10.114 --> 01:28:15.495
Until the next time you have to rebalance or or open new channel channels. You know?

1148
01:28:17.555 --> 01:28:18.055
Right.

1149
01:28:20.570 --> 01:28:26.110
Okay. So, I mean, on to the next topic. While we have you here, Fia, Jeff, you have this project

1150
01:28:26.765 --> 01:28:28.525
that I'm gonna butcher the name,

1151
01:28:30.525 --> 01:28:31.025
antetilineum?

1152
01:28:32.284 --> 01:28:32.784
Antilium?

1153
01:28:34.045 --> 01:28:34.545
Atlinium.

1154
01:28:35.380 --> 01:28:35.880
Atlinium.

1155
01:28:36.740 --> 01:28:42.805
Horrible name, dude. It's a really bad name. So you wanna talk to the freaks about what it is and why they should care?

1156
01:28:44.325 --> 01:28:46.345
I'm not sure they should care. I the

1157
01:28:48.725 --> 01:28:50.425
the the idea of smart contracts,

1158
01:28:51.845 --> 01:28:52.610
it it's

1159
01:28:53.090 --> 01:28:55.670
was on my mind for a long time, and

1160
01:28:56.530 --> 01:29:00.869
I I realized that they they could be useful, like, as a programmable

1161
01:29:02.305 --> 01:29:02.805
escrow,

1162
01:29:03.425 --> 01:29:03.925
like,

1163
01:29:04.305 --> 01:29:10.645
they could you put money in there and something happens, and people can trust that. They don't have to

1164
01:29:10.980 --> 01:29:13.080
trust absolutely, but they can trust

1165
01:29:13.620 --> 01:29:18.725
that the person there's not a person interested in, like, that can steal from that

1166
01:29:19.285 --> 01:29:21.225
from that contract, that escrow.

1167
01:29:22.565 --> 01:29:23.865
So I made this,

1168
01:29:24.565 --> 01:29:26.345
this explanation was terrible.

1169
01:29:27.489 --> 01:29:29.030
But the idea is that you can

1170
01:29:30.050 --> 01:29:39.905
it's like Ethereum, but on Ethereum, you have an escrow that is the the Ethereum network and the the nodes and the validation and the miners and so on. In this case, it's the same, but

1171
01:29:40.365 --> 01:29:41.825
this grow is a server

1172
01:29:42.205 --> 01:29:43.105
that I run.

1173
01:29:43.760 --> 01:29:48.020
And other people can post their their contracts there. Like, they write

1174
01:29:48.720 --> 01:29:52.260
some lines of code, and then they have a smart escrow

1175
01:29:52.895 --> 01:29:56.195
that they can use for other things. And someone

1176
01:29:56.575 --> 01:30:02.630
using that doesn't have to trust the person who wrote the code. They only have to trust me in this case,

1177
01:30:04.610 --> 01:30:13.215
and that's it. So it's like a it's it's I mean, it's a flex on Ethereum. You're saying we can do what what you do, and you as long as you add this trusted third party.

1178
01:30:13.915 --> 01:30:21.130
But but because this trusted third party it's like the uncle Jim model. Right? Like, the trusted third party can have competition. There's a bunch of different providers.

1179
01:30:21.670 --> 01:30:22.570
You know, ideally,

1180
01:30:23.430 --> 01:30:25.130
there aren't, but if there were,

1181
01:30:25.670 --> 01:30:29.755
then you could get away with that trust model more. Is that the that's the argument basically. Right?

1182
01:30:30.295 --> 01:30:31.595
The the the argument

1183
01:30:32.055 --> 01:30:33.275
is is like

1184
01:30:33.815 --> 01:30:36.075
separating the the person who that

1185
01:30:36.730 --> 01:30:37.949
ensures you that,

1186
01:30:38.489 --> 01:30:46.575
like, guarantees your money, like, holds your money and guarantees that some code will be run. Separating that from the person who wrote the code.

1187
01:30:47.515 --> 01:30:49.855
Right. And then and to me, I mean,

1188
01:30:50.555 --> 01:30:51.935
the simple use case

1189
01:30:53.120 --> 01:30:56.260
is is this prediction market betting use case.

1190
01:30:57.040 --> 01:31:00.980
Yeah. I've I've been trying to make a ton of small apps to showcase it.

1191
01:31:01.535 --> 01:31:02.035
Yeah.

1192
01:31:03.295 --> 01:31:03.795
Yeah.

1193
01:31:04.175 --> 01:31:09.155
That one makes the most sense to me. There's a lot of there should be a lot of demand there. Why is no one using it?

1194
01:31:09.940 --> 01:31:12.119
I don't think it's very good. Like, the incentives

1195
01:31:12.659 --> 01:31:18.199
are not very good. You you I had to make another one that uses a different calculation for the

1196
01:31:18.755 --> 01:31:20.135
for the market, like

1197
01:31:20.835 --> 01:31:21.335
because

1198
01:31:21.715 --> 01:31:25.095
otherwise, you you pay you you can't buy a lot of shares.

1199
01:31:25.875 --> 01:31:27.080
Otherwise, you pay up

1200
01:31:27.560 --> 01:31:29.980
the the the probability will go sky

1201
01:31:30.440 --> 01:31:40.455
high. So you have to buy 1, buy a few shares and tell someone else to buy the others, but it still works like that way. Like, it's it has a market is market,

1202
01:31:41.074 --> 01:31:42.935
automated market maker thing

1203
01:31:43.715 --> 01:31:44.215
that,

1204
01:31:44.860 --> 01:31:45.360
like,

1205
01:31:47.260 --> 01:31:47.760
just

1206
01:31:48.139 --> 01:31:50.239
you don't need another book for that.

1207
01:31:50.540 --> 01:31:54.755
So it's good in that way. But on the other hand, it's not very optimized for

1208
01:31:55.775 --> 01:32:00.195
large volumes. And also the idea that the person who created the the contract

1209
01:32:01.219 --> 01:32:03.320
resolves it is not ideal.

1210
01:32:04.340 --> 01:32:05.640
Like, the person who

1211
01:32:06.739 --> 01:32:12.375
there should definitely be another way. Yeah. The discrete log contract guys are trying to solve that, right,

1212
01:32:12.755 --> 01:32:16.070
where the Oracle is a separate person, doesn't know what the bets are.

1213
01:32:16.949 --> 01:32:18.570
But I I do feel like,

1214
01:32:19.909 --> 01:32:22.550
I mean, when I got into Bitcoin, my first use case

1215
01:32:23.110 --> 01:32:24.165
I mean, I think,

1216
01:32:24.565 --> 01:32:35.420
you know, the obvious use case was was gambling. Right? I mean, you had Satoshi Dice, but you also had we had Black Tuesday in America where they basically just, like, cut off all the online betting sites.

1217
01:32:37.400 --> 01:32:43.685
And, yeah, like, it's, you know, online betting now in the United States has become, you know, more legal, and you have the

1218
01:32:44.385 --> 01:32:48.325
you know, you have Portnoy playing in it with Penn Gaming, and you have DraftKings,

1219
01:32:49.130 --> 01:32:51.869
and, you know, you you have Yahoo, you have all these different

1220
01:32:52.329 --> 01:32:54.750
regulated services that offer online betting.

1221
01:32:55.290 --> 01:32:55.790
But,

1222
01:32:58.485 --> 01:33:02.665
to me, there's this massive demand for, you know, no k y c, frictionless

1223
01:33:03.525 --> 01:33:04.585
Bitcoin gambling,

1224
01:33:05.150 --> 01:33:09.810
whether that's, you know we can call it gambling or we can call it prediction markets. It's the same shit.

1225
01:33:11.710 --> 01:33:12.210
And

1226
01:33:13.345 --> 01:33:18.565
it's like everyone's just trying to reinvent the wheel almost. You know? It's like I've I've been in the space for

1227
01:33:19.105 --> 01:33:20.165
8 plus years,

1228
01:33:22.430 --> 01:33:25.970
and everyone's trying to overcomplicate it. Like, I just need, like,

1229
01:33:26.750 --> 01:33:29.090
a a relatively simple liquid site

1230
01:33:29.705 --> 01:33:37.965
that's not not like liquid Bitcoin, like, a site that has enough volume. Right? That that I don't care if it's centralized. You know? Let me just bet with lightning,

1231
01:33:38.490 --> 01:33:40.110
get in and out of my bets easily,

1232
01:33:40.810 --> 01:33:42.910
call it a day. Like, I don't you know?

1233
01:33:43.290 --> 01:33:47.710
What do you wanna bet on? Like sports or Well, the big one in America

1234
01:33:48.055 --> 01:33:49.835
the big one in America is Americans

1235
01:33:50.135 --> 01:33:53.595
aren't legally allowed to gamble on elections. So,

1236
01:33:54.935 --> 01:33:59.590
all those regulated services I just mentioned simply cannot have any election bets.

1237
01:34:00.050 --> 01:34:03.190
Right? So we had this major election come and go,

1238
01:34:03.570 --> 01:34:08.815
and there was, like, nobody was offering it. Like, the Ethereum guys have, like, this super complicated augur.

1239
01:34:09.195 --> 01:34:16.060
You know, the DLC guys are talking about DLCs left and right, discreet log contracts, but you couldn't there was no easy way to bet on it.

1240
01:34:17.420 --> 01:34:21.440
That was a failure in my mind. Right? Like, that's that's ridiculous that it's 2021.

1241
01:34:22.540 --> 01:34:29.865
So there there's 2 problems there. One is the the order book thing. The the liquidity is important, as you said, but it's very hard to get.

1242
01:34:30.325 --> 01:34:33.305
And and if you do the order book thing,

1243
01:34:34.190 --> 01:34:35.090
it's impossible

1244
01:34:35.550 --> 01:34:43.675
because no one's going to put orders on the site without liquidity. And when someone one joins the site, they don't find any orders, so so empty.

1245
01:34:43.975 --> 01:34:44.475
So

1246
01:34:44.935 --> 01:34:53.890
it's very hard to to get going. So the automated market makes a thing. It it solves that part, but I think no one has used it on the wild.

1247
01:34:54.510 --> 01:34:56.050
It's, I copied

1248
01:34:56.350 --> 01:34:58.050
the the code from the Hivemind

1249
01:34:58.670 --> 01:34:59.170
project.

1250
01:35:00.295 --> 01:35:02.235
And the other problem is that the law

1251
01:35:02.695 --> 01:35:04.075
rate. You you could have

1252
01:35:04.535 --> 01:35:05.035
yeah.

1253
01:35:05.735 --> 01:35:09.520
When when this this market start to getting to get interesting,

1254
01:35:10.619 --> 01:35:12.320
they always they always fail.

1255
01:35:12.699 --> 01:35:18.764
They always like, the government always shut them down. And you could do if you watch the the post tours,

1256
01:35:19.385 --> 01:35:20.525
presentation on Hivemind,

1257
01:35:22.344 --> 01:35:26.390
you can do a ton of interesting things with this with this betting market.

1258
01:35:27.090 --> 01:35:33.110
And you can do conditional betting, and you you can, like, extract a lot of knowledge from the society,

1259
01:35:34.415 --> 01:35:37.075
from from these markets using these markets.

1260
01:35:37.775 --> 01:35:42.990
But the problem is that the law will always be against it. So you need a system like Bitcoin,

1261
01:35:43.690 --> 01:35:44.910
I think, for this.

1262
01:35:45.450 --> 01:35:47.390
I think a system that is very

1263
01:35:48.810 --> 01:35:49.950
censorship resistant.

1264
01:35:51.495 --> 01:35:57.515
So, yeah, we don't predict on market. Predict on market is a toy, like, to showcase the the

1265
01:35:58.570 --> 01:36:00.730
the algorithm the the the the

1266
01:36:02.570 --> 01:36:05.310
sorry. The automated market maker algorithm

1267
01:36:06.655 --> 01:36:11.635
to show that it works even with, like, very few users, you can still buy shares.

1268
01:36:12.015 --> 01:36:15.720
You don't depend on someone else going on the site at the same time and

1269
01:36:16.360 --> 01:36:18.300
staying there, something like that.

1270
01:36:19.560 --> 01:36:25.180
But the other part, the censorship resistant part is very important. That's why I I wanted to see your hive mind working.

1271
01:36:25.864 --> 01:36:27.385
And, like, I mean, like, a Bitcoin

1272
01:36:28.264 --> 01:36:30.125
I it'd be who me to mention,

1273
01:36:31.784 --> 01:36:32.764
you know, economics

1274
01:36:33.145 --> 01:36:33.625
geek,

1275
01:36:34.344 --> 01:36:35.165
Nick Carter,

1276
01:36:35.530 --> 01:36:42.490
our boy Nick Carter, like, he thinks, like, prediction markets would be awesome for corn futures because corn futures, I guess, are illegal, and we we like

1277
01:36:43.610 --> 01:36:50.975
he he thinks that'd be a fun use for prediction markets. But prediction markets are really fucking cool, this idea that you can gamble on an outcome because

1278
01:36:51.515 --> 01:36:55.055
it goes back to the video games that we were talking about with the video games.

1279
01:36:55.700 --> 01:36:59.800
You have stats on the line. You actually have skin in the game. So those predictions,

1280
01:37:00.900 --> 01:37:02.680
the way those betting markets go

1281
01:37:03.235 --> 01:37:03.735
should

1282
01:37:04.195 --> 01:37:05.415
be way more likely,

1283
01:37:06.195 --> 01:37:07.415
outcome wise

1284
01:37:07.955 --> 01:37:15.260
than if you if you have, like, a centralized polling provider or something like that. And a perfect example in Bitcoin land right now

1285
01:37:15.800 --> 01:37:16.540
is, like,

1286
01:37:16.920 --> 01:37:21.980
where the fuck is our betting markets on on whether or not when Taproot's gonna get activated?

1287
01:37:22.775 --> 01:37:30.155
Right? Like, that should be when I start this show or when I do rabbit hole recap on Thursday and I'm talking about how likely it is for Taproot

1288
01:37:30.600 --> 01:37:47.680
to get activated. It shouldn't be based on some engagement account on Twitter that's saying, oh, 90% of mining pools are are saying it's activated. It should be on a very liquid betting site that says, you know, 10,000 Bitcoin are saying that, you know, Taprid is gonna be activated in the next month and a half,

1289
01:37:49.680 --> 01:37:53.700
and we don't have that. It's crazy that we don't have that. I am not saying

1290
01:37:54.560 --> 01:38:02.364
I deserve shit because I'm not gonna build that. I don't I don't want to have that liability on me, but some NIM some enterprising NIM somewhere

1291
01:38:03.065 --> 01:38:04.765
in the Seychelles or some shit

1292
01:38:05.160 --> 01:38:08.380
should have, like, the the this that service should be available.

1293
01:38:09.800 --> 01:38:15.225
It's it's gonna come. I mean, thing things are just so early as far as that stuff goes right now. Like like, DLCs

1294
01:38:15.925 --> 01:38:18.505
are really just rolling now, and I think

1295
01:38:18.885 --> 01:38:21.545
we're gonna see a lot more services using them,

1296
01:38:21.940 --> 01:38:22.600
you know,

1297
01:38:23.300 --> 01:38:24.920
in in the next year even.

1298
01:38:25.540 --> 01:38:26.280
And furthermore,

1299
01:38:26.659 --> 01:38:30.040
we don't even have DLCs on lightning yet. We we need to get Taproot activated,

1300
01:38:30.500 --> 01:38:31.000
and

1301
01:38:31.415 --> 01:38:35.035
that's gonna be a game changer in itself. So a lot of people,

1302
01:38:35.655 --> 01:38:41.850
you know, probably have an idea of of what they want their infrastructure to look like, and it's just not technically possible yet,

1303
01:38:42.550 --> 01:38:44.570
with the state of the blockchain right now.

1304
01:38:47.885 --> 01:38:56.380
We got, some guys in the comments mentioning Stacks, which is formerly Blockstack, which is formally something else, I think. This is terrible shitcoin.

1305
01:38:57.159 --> 01:39:00.060
This is terrible terrible. They lie. They're liars.

1306
01:39:01.400 --> 01:39:09.135
Let's hear this. Let's hear this. I wanna hear your opinion on it. Yeah. I wanna hear the rundown. Oh, I I don't know very much about Stack, but I know that Blockstack

1307
01:39:09.594 --> 01:39:13.855
has been lying since they were created. Like, they make a ton of marketing about

1308
01:39:14.290 --> 01:39:16.630
doing something something blockchain, something

1309
01:39:17.170 --> 01:39:21.110
decentralized, something like they don't explain what they're doing, and no one cares. No one looks.

1310
01:39:23.255 --> 01:39:27.515
When when you go look inside the the blocks, I think they have decentralized

1311
01:39:27.895 --> 01:39:35.870
apps. It was all fake because the apps were just running in a cloud server that you could host yourself. Like, is this a normal app?

1312
01:39:36.650 --> 01:39:40.715
You can't host apps normally. And then you store the data on a decentralized

1313
01:39:41.095 --> 01:39:46.635
network that's just a server that you can run, but everybody run their the server that they offered

1314
01:39:46.935 --> 01:39:47.595
by default.

1315
01:39:48.490 --> 01:39:52.590
And then they they buy a ton of Bitcoiners with this they they they give

1316
01:39:52.890 --> 01:39:55.710
money for Bitcoiners to build apps that integrated

1317
01:39:56.010 --> 01:39:56.830
block stack.

1318
01:39:57.435 --> 01:40:02.495
And oh, I don't know. It's it's so terrible. And then they made this tax thing that's a shitcoin.

1319
01:40:03.115 --> 01:40:07.300
And they say they say it's based on Bitcoin, but it's it's not

1320
01:40:07.840 --> 01:40:15.685
okay. I don't know. I don't know the details about Stack, but I know it's not based on Bitcoin. It's not a side chain. And they say it is, so

1321
01:40:16.545 --> 01:40:25.060
starts with a lie. And they have a they have a regulated shitcoin that's attached to it that they were they're they got legal permission to dump on retail.

1322
01:40:25.520 --> 01:40:39.235
I remember everyone was super proud of them. There was, like, all the congratulations were going out on Bitcoin Twitter. I was like, guys, like, can we not congratulate someone for getting regulatory approval to to dump a shit coin on retail? And then I got a lot of shit for that, and here we are.

1323
01:40:40.450 --> 01:40:45.350
I haven't looked at that chart lately, but I assume it's pretty just trending to 0 with everything else.

1324
01:40:46.985 --> 01:40:50.445
No. I mean, this is my same concern with RSK. Right? Like, RSK

1325
01:40:51.385 --> 01:40:59.490
has got, like, shitcoin vibes all over it. It's got the fucking token. You know? I don't know what to believe there. Would you agree, Fiat, Jeff? Like, how is that different than RSK?

1326
01:41:00.990 --> 01:41:02.050
RSK is a

1327
01:41:02.830 --> 01:41:07.755
a a real side chain if you if you consider the Federated peg side

1328
01:41:08.055 --> 01:41:11.275
chain. So you can really move Bitcoins there

1329
01:41:12.055 --> 01:41:13.355
and transact Bitcoins

1330
01:41:13.900 --> 01:41:16.880
and move them move them back, features their their model.

1331
01:41:17.500 --> 01:41:20.080
So if it's What's the token for?

1332
01:41:21.395 --> 01:41:28.855
I I don't know the the story about the token, but you can ignore the token. It's like another token inside. If you could ignore the token, it's almost worse.

1333
01:41:30.580 --> 01:41:32.100
I'm not sure. Like, the token

1334
01:41:32.900 --> 01:41:36.120
I I we need to Stacks token for?

1335
01:41:37.060 --> 01:41:39.960
You can't move Bitcoin to the Stacks blockchain,

1336
01:41:40.945 --> 01:41:42.885
and you can't move the Bitcoins back.

1337
01:41:44.225 --> 01:41:50.770
But you can do it on RSK. That's the purpose of RSK. The token was like a money grab thing to finance

1338
01:41:51.389 --> 01:41:53.730
the the stuff. I don't know. I don't like the token.

1339
01:41:54.429 --> 01:42:02.344
But I'm saying it's different it's different projects. Like, one is trying to be a side chain even if they have a shady token. The other is just a shitcoin

1340
01:42:03.045 --> 01:42:04.985
that markets itself will rely.

1341
01:42:05.640 --> 01:42:11.020
A governance token. They both they both sound like shitcoins to me. What did you have an opinion on Urbit?

1342
01:42:12.905 --> 01:42:14.125
Well, I'd have you.

1343
01:42:17.545 --> 01:42:20.204
I liked Urbit when I first read about it.

1344
01:42:20.520 --> 01:42:28.460
That's my opinion. But it also has a shitcoin. It's like my barometer is, like, if these things have shitcoins attached to them, it's just like it's probably garbage.

1345
01:42:28.855 --> 01:42:32.715
They didn't have a shitcoin in the beginning. It was just that weird talk about

1346
01:42:33.335 --> 01:42:35.835
planets and shit Those are the shitcoins.

1347
01:42:36.230 --> 01:42:41.050
They have their NFT shit coins, like planets, universes, stars. They're all trainable.

1348
01:42:41.670 --> 01:42:52.785
Yeah. I know I know they are now, but in the beginning, when I was reading it, there was no mention of shit coins. And then when they got traction, they said, oh, we decided to do these things that are properties

1349
01:42:53.165 --> 01:43:00.180
on the network, and we need a net a blockchain to do it, and they've decided to do it on Ethereum, and then we launch this token.

1350
01:43:01.255 --> 01:43:01.755
Yeah.

1351
01:43:02.135 --> 01:43:04.795
But they're switching to Bitcoin, but it still has the

1352
01:43:05.895 --> 01:43:18.140
Well Like, that's what people don't realize. Like, I like, my issue with shit tokens isn't that they're on Ethereum. It's like they're like, oh, if we put the shit token on liquid, then the Bitcoiners will like it. Like, I still don't like your shit token.

1353
01:43:18.585 --> 01:43:22.365
But don't don't you think there is some form of digital assets that

1354
01:43:22.825 --> 01:43:24.605
can exist besides Bitcoin?

1355
01:43:27.250 --> 01:43:33.030
I mean, that's a $1,000,000 question. The one that we tolerate on this show is the BISTDAO token. Like, is that a shitcoin?

1356
01:43:33.489 --> 01:43:33.989
Yes.

1357
01:43:34.345 --> 01:43:35.165
Yeah. Sort

1358
01:43:36.985 --> 01:43:42.925
of. I think it is a shitcoin. I mean, like, how how deep in the weeds do we wanna go defining shitcoins here?

1359
01:43:43.460 --> 01:43:47.480
Well, my my thing is that if the token represents something real.

1360
01:43:48.420 --> 01:43:56.655
Oh, total shitcoin. I mean, like, if it's like a tangible thing in the real world, like, oh, this asset's pegged to What about Tether? Is Tether a shitcoin?

1361
01:43:58.554 --> 01:44:00.415
Yeah. Tether, I think it's not a shitcoin.

1362
01:44:01.110 --> 01:44:02.650
Why is Tether not a shitcoin?

1363
01:44:04.710 --> 01:44:09.290
Because it's an IOU. Like, it's not not a shitcoin. It's a proper IOU.

1364
01:44:10.405 --> 01:44:10.905
Yeah.

1365
01:44:12.645 --> 01:44:15.145
I I think that there's some assets that

1366
01:44:15.605 --> 01:44:18.264
maybe you can own that aren't money

1367
01:44:18.680 --> 01:44:21.660
that you can transfer, but, I'm not sure about the

1368
01:44:22.120 --> 01:44:23.340
concrete examples.

1369
01:44:23.880 --> 01:44:25.180
Is gold a shitcoin? Governance

1370
01:44:25.880 --> 01:44:30.875
tokens are not are always shitcoin. Come on. Gold's totally a shitcoin. Is yeah. Is gold a shitcoin?

1371
01:44:32.695 --> 01:44:33.994
You put that on the screen.

1372
01:44:36.570 --> 01:44:43.835
This used to be a reoccurring segment on the show. The like, after, like, 10 episodes, everyone just agreed it was a shitcoin, so I stopped asking the question, but it

1373
01:44:44.395 --> 01:44:45.375
it did fit.

1374
01:44:47.114 --> 01:44:49.055
What do you think? Do you think gold's a shitcoin?

1375
01:44:53.679 --> 01:44:54.179
No.

1376
01:44:56.159 --> 01:44:57.060
I think no.

1377
01:44:57.520 --> 01:45:00.820
It depends on what your definition of a shitcoin is. Right? Yeah.

1378
01:45:02.095 --> 01:45:09.475
Yep. Yep. So if gold's not a shitcoin, then I I think I would agree that Tether is not a shitcoin, or, like, a Tether gold, right, wouldn't be a shitcoin.

1379
01:45:10.050 --> 01:45:13.270
If you don't think gold like, if if the asset that is backing

1380
01:45:13.810 --> 01:45:19.110
whatever, you know, you're, like, you're relying on a trusted third party. It's an IOU, but maybe it's not a shitcoin.

1381
01:45:19.925 --> 01:45:21.785
But I think gold's a shitcoin, so

1382
01:45:22.085 --> 01:45:23.625
the IOU is also shitcoin.

1383
01:45:24.805 --> 01:45:31.370
Yeah. But there are there's also some assets, digital assets. I think maybe their bit example is not that bad.

1384
01:45:32.070 --> 01:45:34.810
If you if the shitcoins are the ships and planets,

1385
01:45:35.864 --> 01:45:42.844
they are they are properties, like, they're digital properties in the on the they're closed network that you can join by buying a ship.

1386
01:45:44.470 --> 01:45:49.690
Digital real estate? Digital real estate. Yeah. Maybe these are these aren't shitcoin. But

1387
01:45:50.150 --> 01:45:51.805
That's what shitcoiners say.

1388
01:45:52.285 --> 01:45:58.065
Yeah. Yeah. Was it wasn't there a whole shitcoin just based on make believe land, digital space?

1389
01:45:58.525 --> 01:46:01.790
Oh, yeah. Barry Silberts neck deep in it. What was it called?

1390
01:46:02.270 --> 01:46:05.010
Man. There's just too many to keep track of at this point, honestly.

1391
01:46:06.270 --> 01:46:10.050
Yeah. But I think the thing has to resist before you sell them. Decentraland.

1392
01:46:11.074 --> 01:46:11.574
Decentraland.

1393
01:46:11.875 --> 01:46:14.215
That's it. I hate that I know that.

1394
01:46:15.795 --> 01:46:18.135
There's gonna be, like, a game show one day.

1395
01:46:18.490 --> 01:46:20.270
Who knows their shitcoin?

1396
01:46:21.130 --> 01:46:22.270
Name that shitcoin.

1397
01:46:22.730 --> 01:46:23.630
Yeah. Yeah.

1398
01:46:24.010 --> 01:46:32.905
Yeah. I did for a future segment. We'll see. Well, there was a there was a shitcoin that used multiple mining algorithms to supposedly make it more decentralized, but

1399
01:46:33.740 --> 01:46:37.120
a malicious individual figured out that all you had to do is compromise a single,

1400
01:46:37.580 --> 01:46:41.440
algorithm to compromise the whole system. What was the name of that Chickcoin?

1401
01:46:45.265 --> 01:46:46.165
I don't know.

1402
01:46:47.185 --> 01:46:50.245
And I I thought we were playing a game show, so I just went for it.

1403
01:46:51.510 --> 01:46:54.650
I think it was Verge. Right? Dogecoin dark or whatever.

1404
01:46:55.270 --> 01:46:55.770
Yeah.

1405
01:46:56.870 --> 01:47:00.810
Yeah. But, anyway, that that's another show that we won't do our Shitcoin

1406
01:47:02.695 --> 01:47:04.235
our Shitcoin trivia show.

1407
01:47:04.935 --> 01:47:07.355
So one one thing about Shitcoins is, like,

1408
01:47:08.760 --> 01:47:12.699
the Uniswap example on Ethereum. I don't know if you know about this.

1409
01:47:13.480 --> 01:47:18.235
Probably, you know. But there's the Uniswap thing that doesn't have a token,

1410
01:47:18.614 --> 01:47:22.155
and it's kinda useful thing in the context of Ethereum.

1411
01:47:23.094 --> 01:47:26.074
And then they launched another version that has a shitcoin.

1412
01:47:26.940 --> 01:47:36.475
I think that's the definition. Like, you don't need that. You had it working without the shitcoin, and then you launch itself that is a point, and you invented some some crap that shitcoin does.

1413
01:47:36.775 --> 01:47:41.355
I I love that. That issue. Yeah. But you realize what happened. Right? It was a competitor.

1414
01:47:41.655 --> 01:47:45.275
It was a competing product released it with a shitcoin that

1415
01:47:45.640 --> 01:47:47.580
that made you money if you used it.

1416
01:47:48.120 --> 01:48:00.575
The pancake swap or something? No. It was sushi swap. Sushi. I fuck I fucking hate that I know this. It was SushiSwap, and then they were taking all the volume from Uniswap, so then Uniswap added their own token because they didn't want the volume to get taken.

1417
01:48:01.035 --> 01:48:01.775
And then

1418
01:48:02.090 --> 01:48:02.590
c

1419
01:48:03.130 --> 01:48:08.430
z Binance c z fucking just completely cloned the whole Ethereum chain

1420
01:48:08.810 --> 01:48:13.355
and made it super centralized with 3 second blocks, and he called it Binance Smart Chain.

1421
01:48:13.975 --> 01:48:15.835
And on that, he created

1422
01:48:16.295 --> 01:48:16.795
PancakeSwap,

1423
01:48:17.175 --> 01:48:26.940
which is a direct copy of Uniswap and SushiSwap, but is on Binance Smart Chain. So that's that's what's going on in Bitcoin land right now. What what CZ did was he saw

1424
01:48:27.560 --> 01:48:29.260
Atlenium. He's like, wow.

1425
01:48:29.865 --> 01:48:43.630
How awesome could a project be if you centralize it? But And he pretty much copied it. But he had good branding instead of Atlaneum. Yeah. You know, I knew it was Chase sounds so much better. Atlenium is better because you can talk to the external

1426
01:48:44.090 --> 01:48:54.005
world. Like, on Ethereum, you can't. But on on a cleanium, you can you can make HTTP calls to other sites and fetch data. So the Oracle problem is solved.

1427
01:48:54.500 --> 01:48:56.600
You you just have to trust the server.

1428
01:48:58.100 --> 01:48:59.160
So it's not solved?

1429
01:49:00.660 --> 01:49:04.875
Yeah. It's not solved. I mean, that's the main issue of the Oracle problem. Right? It's like a trusted third party.

1430
01:49:05.655 --> 01:49:07.835
Yeah. But you're already trusting the entire

1431
01:49:08.790 --> 01:49:09.290
Atlenium

1432
01:49:09.670 --> 01:49:10.170
structure.

1433
01:49:10.710 --> 01:49:11.210
So

1434
01:49:12.790 --> 01:49:27.090
Okay. So Lightning Junkie is pretty upset with us for talking about shitcoins. I just wanted just one more thing. Just really just really quickly. Like, this BSC thing is hilarious. Like, this is something that a lot of us have theorized for a while, and Binance finally did it.

1435
01:49:27.870 --> 01:49:30.610
It's just that if if you start centralizing

1436
01:49:30.910 --> 01:49:32.690
to try and reduce fees and friction,

1437
01:49:33.205 --> 01:49:38.344
someone else is gonna come that centralizes further, and you're just gonna it's a race to the bottom. You're just gonna have to compete.

1438
01:49:38.804 --> 01:49:45.659
And, Bitcoiners don't talk about it a lot with the BSC thing, but it's like their b cash, but it's actually being done by a,

1439
01:49:46.280 --> 01:49:52.535
you know, a a player who's actually very sophisticated in the market, Binance, you know, one of the, probably the most,

1440
01:49:53.635 --> 01:49:55.495
popular exchange by volume.

1441
01:49:57.155 --> 01:50:05.000
I mean, who knows how much volume is real, but but he's, like, actually executing on this shit, and he uses the same fucking addresses. Right? Like, we we had,

1442
01:50:06.100 --> 01:50:20.090
it's literally the same exact address format. If you look at a BSC address, it looks exactly like an Ethereum address. You can't tell the difference. It's it's an it's exactly the same address. You can switch between even as a setting, you can switch MetaMask that just switches to his chain.

1443
01:50:20.969 --> 01:50:31.835
And, like, now we have Portnoy Portnoy. I'm not gonna say the name of the shitcoin, but Portnoy is still the bottom of the battle of shitcoin. Guess what chain it's on? It's on BSC. It's not on Ethereum. So they've played themselves,

1444
01:50:32.295 --> 01:50:34.395
and it's it's just pretty fucking hilarious,

1445
01:50:35.095 --> 01:50:36.555
case study to watch unfold.

1446
01:50:37.520 --> 01:50:38.580
Yeah. That's awesome.

1447
01:50:40.000 --> 01:50:44.900
So Lightning Junkies wants us to talk about any pre vout l 2 channel factories.

1448
01:50:47.665 --> 01:50:55.845
Do you guys have strong opinions on them? I mean, they're I think we need we need additional soft fork, to enable that. Right?

1449
01:50:56.670 --> 01:51:00.690
Yeah. I I think so. Any printout is BIP 118, I think.

1450
01:51:01.710 --> 01:51:05.875
And l two builds upon that. I'm not entirely sure.

1451
01:51:06.735 --> 01:51:08.355
Then channel factories,

1452
01:51:09.534 --> 01:51:10.995
I I don't know too well.

1453
01:51:11.760 --> 01:51:14.020
I bet Jeff could speak to a lot of this stuff

1454
01:51:14.719 --> 01:51:16.179
better than I could, actually.

1455
01:51:17.920 --> 01:51:18.159
So

1456
01:51:18.875 --> 01:51:21.614
yeah. That's the best soft fork and much better than Taproot,

1457
01:51:21.995 --> 01:51:23.455
much more useful than Taproot.

1458
01:51:24.795 --> 01:51:36.265
We should have this and not Taproot. If you if you maybe you can have both. Yeah. Probably. You need both. So could you explain what it is in a nutshell to someone who may not know and hasn't been following?

1459
01:51:38.245 --> 01:51:40.025
So the basic idea is that

1460
01:51:40.885 --> 01:51:43.065
you can create a Bitcoin transaction

1461
01:51:44.010 --> 01:51:46.590
that does doesn't reference a previous output.

1462
01:51:47.210 --> 01:51:50.590
And then later, after the transaction was already signed and okay,

1463
01:51:50.985 --> 01:51:53.244
you assign it to a previous output.

1464
01:51:54.105 --> 01:51:56.684
And this enables l two, which is

1465
01:51:58.344 --> 01:52:00.445
a much better way to have lightning channels

1466
01:52:01.130 --> 01:52:06.830
that you can just keep updating the state and deleting the the previous states because you you can always

1467
01:52:07.665 --> 01:52:11.445
you always have a transaction that's pre signed by your peer,

1468
01:52:11.985 --> 01:52:20.110
and you you can attach it to any previous state of that channel. So if your peer tries to cheat you, you can attach the the newest version

1469
01:52:20.730 --> 01:52:23.695
of the channel to that, and then you're okay.

1470
01:52:24.715 --> 01:52:25.215
So

1471
01:52:25.515 --> 01:52:28.735
you don't have to keep track of all the previous states. Like,

1472
01:52:29.275 --> 01:52:31.455
currently, you you keep track of a penalty

1473
01:52:31.915 --> 01:52:34.190
key for all the previous states.

1474
01:52:35.290 --> 01:52:36.350
So it's very cumbersome

1475
01:52:36.970 --> 01:52:37.790
and very complex

1476
01:52:38.170 --> 01:52:38.670
design.

1477
01:52:40.425 --> 01:52:42.205
Yeah. Very, very complex to implement.

1478
01:52:42.585 --> 01:52:46.845
And we feel l two is much simpler. So you can have more complex

1479
01:52:47.420 --> 01:52:56.080
stuff on top of L2 that you can have today, like this channel factors that they're just channels with more than 1 peer. They they call them, like

1480
01:52:56.965 --> 01:52:57.405
Okay.

1481
01:52:57.845 --> 01:52:58.985
Multi party channels.

1482
01:52:59.525 --> 01:53:03.785
And then is you can have a channel with a bunch of peers, and these and you make

1483
01:53:04.330 --> 01:53:07.390
virtual channels between these peers inside this

1484
01:53:08.490 --> 01:53:10.190
this this multiparty channel.

1485
01:53:11.255 --> 01:53:16.455
And then if 1 of these like, if 2 of these peers want to exit, they can exit to the change

1486
01:53:17.255 --> 01:53:18.270
they can leave their

1487
01:53:18.750 --> 01:53:21.650
their the multiparty channel with their own channel,

1488
01:53:22.030 --> 01:53:24.930
and they then it becomes a standalone channel. Anyway,

1489
01:53:25.445 --> 01:53:29.625
it's it's better. It's it's better for backups. It's better for

1490
01:53:30.885 --> 01:53:32.985
watchtowers. You can actually have watchtowers

1491
01:53:33.580 --> 01:53:37.600
because in the current model, it's too cumbersome and expensive to have watchtowers.

1492
01:53:38.060 --> 01:53:40.640
But if any per watt l 2, you can.

1493
01:53:42.135 --> 01:53:42.635
Yeah.

1494
01:53:44.215 --> 01:53:45.755
And other things, I don't remember.

1495
01:53:47.175 --> 01:53:49.914
Unwanted channel closes are gonna decrease too

1496
01:53:50.215 --> 01:53:50.715
as,

1497
01:53:52.320 --> 01:53:54.260
you know, you you could pop in another input.

1498
01:53:54.800 --> 01:53:55.540
Yeah. Yeah.

1499
01:53:56.480 --> 01:53:59.620
One of the cause of channel close today is fee negotiation.

1500
01:54:00.225 --> 01:54:05.045
Like, when you created the commitment transaction that you need when you want to force close a channel,

1501
01:54:05.665 --> 01:54:07.525
the peers have to agree on a fee.

1502
01:54:08.640 --> 01:54:09.140
And,

1503
01:54:09.840 --> 01:54:14.340
like, they have to agree on a fee that will be filed in the future. So it's complicated.

1504
01:54:15.255 --> 01:54:23.594
And when the negotiation doesn't doesn't match, like, one peer wants a higher fee and you want a smaller fee, then they could the channel they they close the channel.

1505
01:54:24.080 --> 01:54:25.300
So that's very bad.

1506
01:54:26.320 --> 01:54:29.300
But with any pre vouch, you can you can always

1507
01:54:31.120 --> 01:54:37.304
pay for the fee at the time you're you're committing the you're you're closing the channel through

1508
01:54:38.804 --> 01:54:40.585
child pays for parent things.

1509
01:54:41.045 --> 01:54:42.344
So I think it's better.

1510
01:54:43.400 --> 01:54:43.900
And

1511
01:54:44.519 --> 01:54:48.860
what else? So you you you remove that step from the from the problem.

1512
01:54:52.535 --> 01:54:53.035
Yeah.

1513
01:54:53.495 --> 01:55:00.235
Also, in prelaunch is very good because it enables space chains. Watch the video from Ruben Swanson on space chains.

1514
01:55:03.130 --> 01:55:04.590
I watched that for a

1515
01:55:05.770 --> 01:55:07.550
why should I care about space chains?

1516
01:55:09.355 --> 01:55:11.695
Well, there are some things as I said,

1517
01:55:12.635 --> 01:55:14.895
that maybe you want a blockchain for,

1518
01:55:15.595 --> 01:55:16.335
but you'd,

1519
01:55:16.890 --> 01:55:18.190
like, in 2013,

1520
01:55:18.570 --> 01:55:24.190
people were talking about block things you can do in in the blockchain. Most of them are shit, but some of them

1521
01:55:24.570 --> 01:55:33.840
were not that bad. But the problem is that to have a blockchain, you need a way to to mine the chain. And to mine the chain, you need the shitcoin. So

1522
01:55:34.300 --> 01:55:36.160
no short no blockchain is

1523
01:55:36.780 --> 01:55:43.405
is good because they all have shitcoins. But with the space chains, you can have a a blockchain without a Shitcoin

1524
01:55:43.945 --> 01:55:46.204
that merge minds with Bitcoin transparently.

1525
01:55:48.184 --> 01:55:54.039
So that's it. So you can have one one of the examples actually, the the one example I have is

1526
01:55:54.340 --> 01:55:54.840
DNS

1527
01:55:55.460 --> 01:55:55.960
because

1528
01:55:56.579 --> 01:55:59.960
we're in the real world now, we are all owned by the

1529
01:56:00.265 --> 01:56:04.925
ICANN people that are vampires. I don't know who they are, but It's a unique.

1530
01:56:05.864 --> 01:56:06.605
Yeah. Probably.

1531
01:56:07.310 --> 01:56:07.810
So

1532
01:56:08.270 --> 01:56:10.050
we need an exit from ICANN.

1533
01:56:11.390 --> 01:56:16.995
And a blockchain, I think it's the best way. And it's good that now with Spacechains, we can have a

1534
01:56:17.955 --> 01:56:20.615
a blockchain for names that isn't a shitcoin.

1535
01:56:24.300 --> 01:56:25.680
Well, that sounds pretty cool.

1536
01:56:28.380 --> 01:56:28.700
I,

1537
01:56:29.980 --> 01:56:31.360
I wonder, like, how much

1538
01:56:33.205 --> 01:56:39.685
like, I feel like it's hard to for us to grasp what the future looks like. You know? You have all these moving parts. I mean, so much of it is

1539
01:56:42.310 --> 01:56:45.930
I mean, it's overwhelming to me, and I spend so much time trying to

1540
01:56:46.310 --> 01:56:47.290
understand it.

1541
01:56:48.790 --> 01:56:50.170
I wonder, you know,

1542
01:56:50.495 --> 01:56:57.715
how much I'm missing when I'm thinking about, you know, what it'll look like in 5 years, what what will the future look in 5 years. I mean, the other big thing I'm

1543
01:56:58.790 --> 01:57:09.265
pretty excited about is state change, which I don't think requires any kind of soft fork, period. Oh. It just has an interesting trust model that it requires, in Braveout too.

1544
01:57:09.645 --> 01:57:21.760
Oh, it does? Yeah. But the the there's the the this version the commerce block is making. Yeah. That one doesn't require. Right? Yeah. That doesn't require. But the with and prevail, they're they're better. They're much better.

1545
01:57:22.460 --> 01:57:24.320
Without without it,

1546
01:57:24.875 --> 01:57:26.735
the the trade off is that

1547
01:57:27.515 --> 01:57:28.015
is

1548
01:57:28.635 --> 01:57:36.579
you're you're you're trusting that the state chain provider and your counterparty aren't colluding. As long as they don't collude, you're good, though.

1549
01:57:37.280 --> 01:57:39.139
No. That's with Right. And prevault.

1550
01:57:39.599 --> 01:57:41.219
Yeah. That's with and prevault.

1551
01:57:41.599 --> 01:57:47.954
Oh. Without entry vault, I think the only difference that they expire, you you use, time locks.

1552
01:57:48.335 --> 01:57:51.235
So your state chain thing expires.

1553
01:57:51.970 --> 01:57:57.990
You have to go to go to the chain from wire to wire. Which is obviously not ideal in a high fee environment.

1554
01:57:58.530 --> 01:57:59.030
Yeah.

1555
01:58:00.045 --> 01:58:01.425
But still the the

1556
01:58:01.885 --> 01:58:04.225
on the other side, like, on on the real

1557
01:58:04.605 --> 01:58:05.745
state change vision,

1558
01:58:06.340 --> 01:58:09.560
you still have to trust the the the counterparty that's

1559
01:58:10.100 --> 01:58:10.760
the entity.

1560
01:58:12.180 --> 01:58:17.785
But the entity can be blind, so it's it's kinda better. They don't have to know about the

1561
01:58:18.425 --> 01:58:22.685
they they only have to sign stuff. They don't have to know they are the

1562
01:58:23.360 --> 01:58:28.500
federation that's custodian. They're they're not actually custodian thing. They're just signing stuff.

1563
01:58:31.485 --> 01:58:35.025
Got it. So do you guys think we're gonna get Taproot by the end of the year?

1564
01:58:35.805 --> 01:58:36.305
Yes.

1565
01:58:36.685 --> 01:58:37.185
Definitely.

1566
01:58:38.190 --> 01:58:40.849
Probably in the next activation period, it'll lock in.

1567
01:58:41.309 --> 01:58:44.610
I mean Yes. I mean The big miners are gonna fuck around.

1568
01:58:45.395 --> 01:58:51.895
There's there's gonna be some fucking around, Matt, but there's gonna be a limit to how much, like, these guys can push the envelope.

1569
01:58:52.490 --> 01:59:01.070
So, Evan, we don't have we don't have the prediction market I want. So, like, do you wanna put money on the line that that the next activation period doesn't,

1570
01:59:01.895 --> 01:59:03.594
we don't get we don't get Taproot?

1571
01:59:06.614 --> 01:59:11.434
Yeah. Let's let's have a friendly wager. What do you say? How much is a friendly wager?

1572
01:59:12.040 --> 01:59:14.460
I don't know. Put at least a 100,000 sats down.

1573
01:59:15.080 --> 01:59:17.980
That's it? Well, let's do, let's do 500,000

1574
01:59:18.360 --> 01:59:18.860
sats.

1575
01:59:20.505 --> 01:59:21.005
500,000

1576
01:59:21.385 --> 01:59:23.885
sats. We have 3. Let's do it.

1577
01:59:24.585 --> 01:59:27.244
Okay. So if if Taproot if Taproot,

1578
01:59:28.900 --> 01:59:33.000
passes the threshold I guess it technically doesn't activate. Right? But if it passes the threshold

1579
01:59:33.540 --> 01:59:34.280
of 90%

1580
01:59:34.980 --> 01:59:37.000
over the next difficulty adjustment,

1581
01:59:37.475 --> 01:59:38.695
then I owe you 500,000

1582
01:59:39.075 --> 01:59:41.815
sats. And if it doesn't, you owe me 500,000 sats.

1583
01:59:42.195 --> 01:59:42.855
I I

1584
01:59:43.315 --> 01:59:51.740
am I'm a 100% in. Let's do it. Okay. Deal. It locks in, but it doesn't activate. Right? If that's that's the proper terminology. Yeah. Yeah. So it's gonna activate

1585
01:59:52.120 --> 01:59:53.180
in November.

1586
01:59:53.575 --> 01:59:57.835
Right. So yeah. But it will lock in. Lock in. Yeah. Yeah. Yeah. So lock in,

1587
01:59:58.375 --> 01:59:58.875
and

1588
01:59:59.495 --> 02:00:01.595
I'm betting that we'll have a lock in

1589
02:00:01.970 --> 02:00:09.910
during the 3rd activation period. Which is the next one. Right? You're not gonna get it for me. Currently on the second one. Each activation period is 2 weeks,

1590
02:00:10.585 --> 02:00:11.085
$2,016.

1591
02:00:12.345 --> 02:00:16.125
So yeah. Awesome. Yeah. I think I think this one, we we already,

1592
02:00:16.745 --> 02:00:20.330
yeah, we already overshot it. We got 11% of the blocks are red.

1593
02:00:21.370 --> 02:00:25.470
And, you know, we also things are a little hairy because not all the miners

1594
02:00:26.490 --> 02:00:27.870
are signaling consistently.

1595
02:00:28.250 --> 02:00:29.070
So btc.com

1596
02:00:30.335 --> 02:00:30.835
is,

1597
02:00:31.215 --> 02:00:32.435
straggler right now.

1598
02:00:32.975 --> 02:00:35.395
And, without them, we're at 85%.

1599
02:00:35.855 --> 02:00:37.715
But with them, we're at, like, 94%

1600
02:00:38.815 --> 02:00:39.555
or so.

1601
02:00:40.410 --> 02:00:40.910
So,

1602
02:00:42.570 --> 02:00:44.670
hey, that's not to say other people won't,

1603
02:00:45.690 --> 02:00:52.245
start messing around with 2 claim technical difficulties, say, oh, we're morally opposed to Taproot. Who knows?

1604
02:00:53.025 --> 02:00:55.045
I don't think it's gonna be super straightforward,

1605
02:00:55.345 --> 02:00:58.510
but I think that the majority will prevail.

1606
02:00:59.050 --> 02:01:00.030
I think, ironically,

1607
02:01:01.050 --> 02:01:04.510
or maybe it's not ironic. I think, like, the recent dump in price

1608
02:01:05.285 --> 02:01:21.210
helps taproot activation because, like, if the miners are, you know if if the if the price is just pumping and the miners just feel like they're baller as fuck, then I feel like they're more likely to fuck around. Yeah. But, like, the miners are feeling super poor right now. They, you know, their their net worth just went down by 23%.

1609
02:01:23.365 --> 02:01:26.105
So they they might be less likely to to fuck around.

1610
02:01:26.725 --> 02:01:35.369
Yeah. Yeah. I could see that. That's definitely a factor. But I think it's Yeah. Same thing to assume is they're gonna fuck around with us. They're gonna do someone's gonna do something,

1611
02:01:35.670 --> 02:01:38.650
and it it's it's gonna be shortsighted.

1612
02:01:39.095 --> 02:01:39.595
But,

1613
02:01:40.615 --> 02:01:47.595
let's see how it pans out. Let's see how it pans out. We're we're still not exactly on the money right there with the rate we wanna be.

1614
02:01:48.610 --> 02:01:51.910
But, you know, the numbers are looking good. If if our stragglers,

1615
02:01:52.450 --> 02:01:53.110
we've already

1616
02:01:53.650 --> 02:01:58.605
The real question is if Elon supports Taproot or not. I mean, that's that's basically

1617
02:01:59.705 --> 02:02:01.805
that that's how these decisions get decided.

1618
02:02:02.650 --> 02:02:09.310
Yeah. They they phone them up. Elon gets on the phone. He calls up Ellen Big. He's like, yo, Ellen Big was going out.

1619
02:02:10.554 --> 02:02:15.375
What do you know? Should we know that Ellen Bigg? Ellen Bigg should signal.

1620
02:02:15.914 --> 02:02:20.570
Do we have do do we have their opinion on it? We don't know how they feel.

1621
02:02:21.010 --> 02:02:25.110
Have them on the show. I mean, I guess all lightning people are very pro Taproot,

1622
02:02:25.810 --> 02:02:26.870
rightfully so.

1623
02:02:27.875 --> 02:02:33.815
Yeah. I mean No one really has a good argument against Taproot at this point. All our fighting has been about that activated.

1624
02:02:34.515 --> 02:02:35.015
Yeah.

1625
02:02:36.619 --> 02:02:39.420
Ellen Bigg is AXA Insurance. We got he's out of the

1626
02:02:40.619 --> 02:02:45.760
I trust him because he said something earlier that I a 100% agree with, which is the Chrysler building is a shitcoin.

1627
02:02:48.035 --> 02:02:54.455
Okay. So if we get Taproot, so do we think any prove out is is when do we think that's gonna happen?

1628
02:02:55.409 --> 02:02:57.670
Next year. Yeah. Hopefully, 2022.

1629
02:02:58.770 --> 02:02:59.270
Yeah.

1630
02:03:00.210 --> 02:03:02.869
And I'm I'm better yet. On ln.

1631
02:03:05.085 --> 02:03:08.204
So let's see. That's gonna change up a whole bunch of stuff. I mean

1632
02:03:09.164 --> 02:03:11.105
I think everybody loves any.

1633
02:03:12.050 --> 02:03:15.730
No one's against it. And if the program creation does well

1634
02:03:18.370 --> 02:03:27.665
and the code is much simpler. The code changes. I think I think, has a branch that's on a Bitcoin cord that already does it in it's small

1635
02:03:28.224 --> 02:03:29.844
the small changes. So

1636
02:03:35.460 --> 02:03:37.239
Okay. Well, I mean, that's optimistic.

1637
02:03:37.540 --> 02:03:41.054
I'm, you know, I'm down with supporting that timeline. Do we think,

1638
02:03:41.535 --> 02:03:44.835
what about cross input signature aggregation? Is that ever gonna happen?

1639
02:03:45.295 --> 02:03:46.114
Oh, man.

1640
02:03:47.690 --> 02:03:52.350
That is such a loaded can of worms just because, like, we don't really have a great way to do it,

1641
02:03:53.290 --> 02:03:55.390
without doing a hard fork, I believe.

1642
02:03:55.690 --> 02:03:56.190
So,

1643
02:03:56.695 --> 02:04:00.315
you know, I mean, I I think it's something everyone would like to see.

1644
02:04:00.695 --> 02:04:04.155
I think, we'd be Wait. You can do it with a soft fork, can't you?

1645
02:04:07.330 --> 02:04:18.285
I'm I'm not a 100% sure. Someone in the comment If you can't do it without a hard fork, then we're fucked. I thought I thought you could do it this often. Biggest thing right now that it would require a hard fork,

1646
02:04:19.945 --> 02:04:22.205
the the way that the signatures are

1647
02:04:22.980 --> 02:04:23.480
are

1648
02:04:23.940 --> 02:04:28.040
read. So Yeah. Needs to come up with a really great way to tackle that,

1649
02:04:28.420 --> 02:04:29.640
and then maybe

1650
02:04:30.180 --> 02:04:38.985
we'll have it. I I don't know. You know? A lot of people are also posturing like, oh, it's not gonna happen. There's too many corporate interests. It would have provided for too much privacy.

1651
02:04:39.480 --> 02:04:47.099
And I don't think that's that's really the case. I think if we found the clean way to do it, I I think it would definitely get activated. But

1652
02:04:47.405 --> 02:04:51.105
like I said, there's there's not a great way to do it right now.

1653
02:04:52.605 --> 02:05:02.050
Yeah. I don't know very much about that. I I heard these things like that. No one has solved it. Like, no one has found a way. But I think, like, after end,

1654
02:05:03.535 --> 02:05:08.755
we start to squeeze Bitcoin very much to to put more things on it.

1655
02:05:09.055 --> 02:05:12.035
And I I know I don't know if it will work like that.

1656
02:05:12.540 --> 02:05:14.800
But I I I'm hopeful that

1657
02:05:15.180 --> 02:05:19.200
people will like drivechains, the drive the hash a scroll idea.

1658
02:05:19.555 --> 02:05:26.775
And then we can move these things to side chains that are very But the drive change minimize it. The drive change need any preVAP?

1659
02:05:28.130 --> 02:05:28.850
No. But,

1660
02:05:29.410 --> 02:05:35.265
no. The drive change is 2 parts, like the merge mining, blind merge mining, and the Hash AD s Pro.

1661
02:05:35.745 --> 02:05:37.445
And we can do the blind Dave?

1662
02:05:39.425 --> 02:05:40.645
Yes. I think it is.

1663
02:05:41.025 --> 02:05:47.670
The merge mining, we can do with any profile. Like, that's how the space change work. And then we only need the HashHatro s pro.

1664
02:05:48.450 --> 02:05:52.230
That's so that's BIP 300. Right? All the stuff with the merge mining?

1665
02:05:52.725 --> 02:05:54.025
Or is that just hash,

1666
02:05:54.965 --> 02:06:01.465
hash rate? Hash rate. Yeah. That's 300. Yeah. Why why is it not safe? I don't I don't know.

1667
02:06:01.980 --> 02:06:06.140
I don't know. I just like, why doesn't everyone merge mine? Like, what what what

1668
02:06:07.340 --> 02:06:11.495
I I've been hearing about drive change for such a long time. I just, like, assume it's vaporware.

1669
02:06:13.155 --> 02:06:13.655
Yeah.

1670
02:06:14.035 --> 02:06:15.235
I don't know. It's kinda

1671
02:06:16.195 --> 02:06:18.855
Like, did you realize what happened with Dogecoin and Litecoin?

1672
02:06:19.330 --> 02:06:20.710
We're back to the shit coins.

1673
02:06:21.170 --> 02:06:21.670
Dogecoin

1674
02:06:22.770 --> 02:06:24.150
is worth more than Litecoin,

1675
02:06:24.770 --> 02:06:28.150
but it's merge mined with Litecoin. Like, I feel like that broke something,

1676
02:06:28.665 --> 02:06:40.010
but I don't know what it broke. But I feel, like, there's gotta be an incentive that's broken there. Like, it they're Litecoin miners that are supposed to mine Dogecoin on the side, and now they're Dogecoin miners that are also mining Litecoin. Right?

1677
02:06:42.389 --> 02:06:49.945
Yeah. Yeah. I think the incentives are weird, especially when it's, like, explicit merge money, not blind.

1678
02:06:50.565 --> 02:06:51.065
And

1679
02:06:51.925 --> 02:06:53.864
and also when there are 2 different shitcoins

1680
02:06:54.650 --> 02:06:57.870
in the in the case of drive chain or you you wouldn't have,

1681
02:06:58.330 --> 02:07:00.030
the sheep. You wouldn't have a sheep coin.

1682
02:07:00.410 --> 02:07:01.710
Yeah. And

1683
02:07:02.695 --> 02:07:06.475
there's there's an argument that it's I think most people don't

1684
02:07:07.095 --> 02:07:10.795
try to merge mine because it's not worth doing. Like, the the miners

1685
02:07:11.230 --> 02:07:13.570
don't want to to run a node on

1686
02:07:13.949 --> 02:07:15.730
a stupid shitcoin thing.

1687
02:07:16.830 --> 02:07:19.489
Just like they're mining Bitcoin. You don't want to plug

1688
02:07:19.825 --> 02:07:28.325
a terrible software that will crash everything into their their many rigs. I think this was happening, like, the when Namecoin is merged with Bitcoin,

1689
02:07:29.040 --> 02:07:35.735
and Namecoin used it to crash miners' notes. But but what about, like, something like BCash? Like, are they just

1690
02:07:36.695 --> 02:07:42.554
are they just idiots, or, like, why why is why didn't they choose the merge mind route rather than,

1691
02:07:43.175 --> 02:07:44.795
you know, like, their 10 block

1692
02:07:45.390 --> 02:07:50.210
checkpoint thing with the minority hash rate of the same hash rate of the same algo.

1693
02:07:50.670 --> 02:07:52.210
Like, why didn't they merge mine?

1694
02:07:55.365 --> 02:08:04.070
I think they're idiots. What's this? Ethash? Yeah. Yeah. Yeah. That is the answer. I mean, they're definitely idiots, but I'm curious if that's why they're they're not merge mining or

1695
02:08:04.930 --> 02:08:06.790
if they're just they're you know,

1696
02:08:07.090 --> 02:08:22.300
that would be even dumber. It'd be even dumber if they if they merge mine than if they do what they're currently doing. Like, I don't even see people offer that as an option. Like, no one talks about that in p cash flow or no one talked about now it's worthless or whatever. Okay. No one really talked about it.

1697
02:08:22.920 --> 02:08:25.500
No. I think the problem is that the miners wouldn't

1698
02:08:26.120 --> 02:08:31.485
want to run these softwares. But if it's blind merge mining, like like the space change model,

1699
02:08:31.865 --> 02:08:37.770
then the miners don't have to know about it. You just merge mine by publishing transactions, normal Bitcoin transactions, and the miners just

1700
02:08:38.650 --> 02:08:47.755
use this. So Like how does that work, the merge mining? So, like, let's say I'm a Litecoin miner. Right? And, you know, Dogecoin's piggybacking on it.

1701
02:08:48.715 --> 02:08:55.375
And I'm like, listen. I don't care about Dogecoin. I don't wanna do this extra computation. I don't care about the extra reward I'm gonna get.

1702
02:08:55.730 --> 02:09:05.085
So when I mine my blocks, do does Doge not get a block mined and effectively Dogecoin users have to wait until a miner comes and mines a block that

1703
02:09:05.725 --> 02:09:06.945
does include Dogecoin?

1704
02:09:08.925 --> 02:09:18.670
Yeah. I think it is. That's that's the way it is. RSK is blind is merge mining with Bitcoin, so the miners have to run RSK nodes. And

1705
02:09:19.130 --> 02:09:22.614
I think 70% are doing it. You you can look at the

1706
02:09:23.395 --> 02:09:44.735
the Coinbase of the blocks. Most of the they don't have an RSK block thing or an operator. Yeah. But, like, what does that mean? Like, is that secure, or is that bullshit? Is that, like, a bullshit number when when Sergio comes out and he's, like, 70 like, he's, like, we have we have one of the most hash rates out of any chain, you know, besides Bitcoin. We have 70% of Bitcoin hash rate is is merge mining

1707
02:09:45.130 --> 02:09:46.830
RSK. Like, is that just bullshit?

1708
02:09:47.770 --> 02:09:50.670
I think it's partly bullshit, but it's also partly good.

1709
02:09:52.305 --> 02:09:54.645
It's bullshit because it's not the same security

1710
02:09:54.945 --> 02:09:55.925
model of Bitcoin,

1711
02:09:57.345 --> 02:09:59.445
but it's also a good way of doing.

1712
02:09:59.860 --> 02:10:02.040
You you need some time stamping thing

1713
02:10:02.340 --> 02:10:07.240
on your chain, and the the best way to do it is just to use the Bitcoin chain.

1714
02:10:08.185 --> 02:10:17.085
But on the other hand, it's not secure in the sense that you can't it's hard to roll back. It's it's easier to roll back RSK than it is to roll back Bitcoin.

1715
02:10:18.160 --> 02:10:21.940
It's it's got a property of that. Like, if you attack,

1716
02:10:22.320 --> 02:10:23.700
let's say, Litecoin or

1717
02:10:24.160 --> 02:10:34.145
Rootstock, whatever, you or you you attack the main chain that all the merge mining is piggybacking on. You can also hack or 51% attack,

1718
02:10:34.780 --> 02:10:36.620
you know, the sub trends. So, like, if you

1719
02:10:37.500 --> 02:10:41.920
Do I have to that's a given. That's a given. But, I mean, that it basically incentivizes

1720
02:10:42.380 --> 02:10:45.725
it it further monetizes an attack on the main chain. But

1721
02:10:46.185 --> 02:10:51.565
but, like, I'm trying to struggle with I'm struggling with the idea of this, like, 70% merge mined with Bitcoin.

1722
02:10:52.230 --> 02:10:54.090
Like, does that make it more secure

1723
02:10:54.870 --> 02:10:56.010
than a independent

1724
02:10:57.030 --> 02:11:01.370
chain that has a different POW, like, like Ethereum, you know,

1725
02:11:02.055 --> 02:11:05.595
that has a different algorithm, but it's POW, separate POW,

1726
02:11:06.615 --> 02:11:09.420
less hash rate that 70% of Bitcoin's hash rate.

1727
02:11:09.980 --> 02:11:18.560
Is probably more secure than I mean, there's other elements to it. Right? But proof of work wise, it's probably more secure than this merge mind RSK shit.

1728
02:11:21.545 --> 02:11:26.990
Yeah. That's hard to control. It's so weird because we, like, talk about all these theoreticals. Right? And then it's like,

1729
02:11:28.110 --> 02:11:39.164
you know, like, central super centralized, like, Binance chain doesn't get attacked or anything. You know? It's like we have, like, these super central Dogecoin. Right? Like, there's, like, 3 people running Dogecoin nodes. Right? Like, no one is

1730
02:11:39.545 --> 02:11:45.085
they they keep all their Dogecoin on Robinhood or whatever, and no one actually attacks it. So, like, until, like, people, like, actually

1731
02:11:45.950 --> 02:11:53.490
until, like, these chains actually get attacked, it's all just kind of theoretical bullshit. But they many of many of the those who were attacked, like,

1732
02:11:53.855 --> 02:11:57.875
Ethereum Classic was attacked many times. Yeah. Ethereum Classic got fucking wrecked.

1733
02:11:59.535 --> 02:12:10.059
Yes. Well, you know, like, a lot of them merged out. It's really about the lowest hanging fruit in a lot of these situations. You know what I mean? Like, the the coins that are easiest to crack

1734
02:12:10.665 --> 02:12:14.125
on certain hash rates. I mean, certain algorithms are gonna get cracked first.

1735
02:12:14.505 --> 02:12:21.360
You know? Why not? If you're building up this capacity to do it, like Right. Like those lower hash rate chains are sort of like,

1736
02:12:23.260 --> 02:12:24.719
canaries in the coal mine.

1737
02:12:25.020 --> 02:12:26.960
Yeah. I mean so maybe I'm just being

1738
02:12:28.505 --> 02:12:37.405
skeptical for skeptical's sake. But for whatever reason, my gut just, like, every time I see this merge mine shit, I just don't trust it and just seems wrong to me, but I can't put my finger on it.

1739
02:12:39.590 --> 02:12:41.369
So how does it work then

1740
02:12:41.670 --> 02:12:45.610
in, say, a drive chain. Right? Like, if there's no block subsidy

1741
02:12:46.375 --> 02:12:48.235
for it because you're not making a shitcoin,

1742
02:12:48.695 --> 02:12:57.290
like, how how does that work? Well, we pay fees, and then the the sidechain miner uses those fees to pay for block space on the main chain.

1743
02:12:57.990 --> 02:12:58.490
Gotcha.

1744
02:12:59.910 --> 02:13:02.570
So that's the the security model. I think it's

1745
02:13:03.055 --> 02:13:06.995
I'm not sure, but it's I think it's safe to say it's based on the money

1746
02:13:08.175 --> 02:13:16.260
spent. It's just a cleaner way to do it. You spend money and you secure the chain. You don't have to buy poor proof of work stuff, ASICs,

1747
02:13:17.040 --> 02:13:18.260
and video cards

1748
02:13:18.800 --> 02:13:23.505
and start mining things. And you just reuse Bitcoin, and you pay money for it.

1749
02:13:26.284 --> 02:13:29.185
Gotcha. Okay. That makes sense. Fair enough.

1750
02:13:30.510 --> 02:13:33.570
So, I mean, before we close this up, I mean, I wanted to talk about,

1751
02:13:34.670 --> 02:13:37.010
I guess you're, like, working on this, like, distributed,

1752
02:13:37.685 --> 02:13:42.744
like, broadcasting cloud, like a distributed Twitter. I think you're calling it Nostra.

1753
02:13:44.244 --> 02:13:46.170
Yeah. Did I pronounce it right?

1754
02:13:46.890 --> 02:13:50.670
Yeah. I'm not sure. I I don't think about how to pronounce Phoenix. Clearly.

1755
02:13:55.795 --> 02:14:01.495
Yeah. Like, how do you say if you have Jeff? Are we saying that right? He doesn't even know. Yeah. He sure Does it matter?

1756
02:14:02.660 --> 02:14:04.200
Doesn't matter. Doesn't matter.

1757
02:14:06.020 --> 02:14:07.480
So what is this? Nostra.

1758
02:14:08.340 --> 02:14:09.240
Oh, that's

1759
02:14:09.860 --> 02:14:10.180
a way

1760
02:14:10.915 --> 02:14:13.094
the best way I could find to to

1761
02:14:15.315 --> 02:14:16.935
stop the censorship stuff

1762
02:14:17.315 --> 02:14:18.215
on the Internet

1763
02:14:19.690 --> 02:14:20.190
and,

1764
02:14:20.650 --> 02:14:22.030
like, Twitter censorship.

1765
02:14:23.370 --> 02:14:26.830
But then it I realized it could be used for more stuff, and

1766
02:14:27.875 --> 02:14:28.195
it's

1767
02:14:29.075 --> 02:14:30.615
I'm not sure how to explain it.

1768
02:14:31.555 --> 02:14:34.055
It's a it's a it's a decentralized

1769
02:14:34.675 --> 02:14:38.760
thing, but it's not peer to peer. You have servers, and you connect to the servers,

1770
02:14:39.139 --> 02:14:41.239
and you send your stuff to these servers.

1771
02:14:41.620 --> 02:14:47.595
And someone else can listen to this stuff. Like, the server will send to them. And you can use multiple servers,

1772
02:14:48.455 --> 02:14:48.955
and

1773
02:14:49.415 --> 02:14:55.800
you're always safe because there will always be some server that even like, the idea is that the servers will block you,

1774
02:14:56.500 --> 02:15:02.120
but you you can use another server. But you you want your identity, like, it's not like Mastodon.

1775
02:15:03.225 --> 02:15:03.885
The server

1776
02:15:04.505 --> 02:15:06.925
knows it it knows it owns your identity.

1777
02:15:07.225 --> 02:15:09.324
So if the server blocks you, you're screwed.

1778
02:15:10.425 --> 02:15:10.925
And

1779
02:15:12.230 --> 02:15:13.050
but With Mastodon,

1780
02:15:14.150 --> 02:15:16.090
the server owns your identity too. Right?

1781
02:15:16.710 --> 02:15:19.615
Yeah. That's what I'm saying. Sorry. Right.

1782
02:15:20.075 --> 02:15:26.895
Mastodon, the server owns your identity. On those server, you won't because it's a a Oh. A key pair.

1783
02:15:27.590 --> 02:15:29.770
And then you just use the server to publish

1784
02:15:30.389 --> 02:15:39.335
stuff. And this the the server blocks you you have other servers that you're also publishing to, and you can also start your own server and people can follow you in any server

1785
02:15:39.954 --> 02:15:49.190
as long as they know your your public key. Or you can use some kind of DNS stuff to give that public key a readable name.

1786
02:15:50.125 --> 02:15:55.744
So it's like a federated Twitter where you control your identity because it's a public private key pair?

1787
02:15:56.045 --> 02:16:02.950
Yeah. Basically that. And, like, it's it's a small change, or, like, this is the that's the essential change between that and

1788
02:16:03.490 --> 02:16:04.630
NoSIR and

1789
02:16:05.075 --> 02:16:05.575
Mastodon.

1790
02:16:06.435 --> 02:16:12.935
But you you you get a ton of cool things with this change. Like, the fact that it becomes like a a

1791
02:16:13.760 --> 02:16:17.380
network for enemies in the sense that you can have multiple servers,

1792
02:16:17.840 --> 02:16:19.620
and we we call them relays.

1793
02:16:20.375 --> 02:16:34.560
But each can have its own policy. 1 can do k o k o s c, and the other can just ban certain topics, and the other can be free, and the other can charge. One can store your stuff for you. The other can just relay it and delete it.

1794
02:16:35.260 --> 02:16:39.040
And you it's a very flexible model. And since you since

1795
02:16:39.506 --> 02:16:42.806
and there's there's a way to pay for these things because your

1796
02:16:43.346 --> 02:16:47.660
your you have a relationship with your server, and you know that server.

1797
02:16:48.040 --> 02:16:58.285
And then that server can charge you for extra things or the basic service of relaying your things. So you can use that to pass more things than just

1798
02:16:58.985 --> 02:16:59.885
Twitter messages.

1799
02:17:01.065 --> 02:17:05.350
I think it works. And, theoretically, that could be, like, your lightning public key too

1800
02:17:06.450 --> 02:17:14.405
if we're just gonna Yeah. Right? Yeah. It could be. I made it, like, because I was very feeling very fancy. I made the public key in the protocol to be

1801
02:17:15.265 --> 02:17:17.445
tap root keys, like the the

1802
02:17:17.905 --> 02:17:18.405
342

1803
02:17:19.186 --> 02:17:20.711
keys. Very cocky.

1804
02:17:23.011 --> 02:17:26.551
Yeah. Because I I thought, oh, maybe someone wants to do some

1805
02:17:27.226 --> 02:17:31.805
weird cryptographic stuff with these keys, but, yeah, it doesn't make much difference.

1806
02:17:32.905 --> 02:17:40.270
The the new points that yeah. That's the main negative of Mastodon. Right? So, like, to the freaks I don't know, Mastodon's like a federated version of Twitter,

1807
02:17:41.689 --> 02:17:45.825
but that has competition among the servers, which are, you know, the different federations.

1808
02:17:46.845 --> 02:17:49.025
I think instances are what they call them.

1809
02:17:51.380 --> 02:17:54.600
But what happens is because you don't own your identity,

1810
02:17:56.899 --> 02:18:02.525
you know, there's still a lot of friction if if if whatever server you're using decides to fuck you

1811
02:18:02.985 --> 02:18:08.125
or, you know, get very censorship happy. It's it's hard to move your social graph,

1812
02:18:08.739 --> 02:18:11.160
your followers and your following or whatever,

1813
02:18:11.699 --> 02:18:12.199
to,

1814
02:18:12.819 --> 02:18:18.165
you know, a way, to mitigate that kind of thing. It there's there's a heavy friction layer there. Right?

1815
02:18:18.565 --> 02:18:22.585
Yeah. Yeah. They have a way to export, but it assumes the server is cooperative.

1816
02:18:23.605 --> 02:18:30.640
Right. The server will the whole purpose. In fact. Yeah. So if you're kicked off, like, there's no way of moving the team. Yeah.

1817
02:18:31.500 --> 02:18:34.985
And that they they also have this this narrative that

1818
02:18:35.386 --> 02:18:43.565
each instance has its own identity. Like, you have an instance for some kind of people and then another for other kind of people. But in the end,

1819
02:18:44.820 --> 02:18:45.320
like,

1820
02:18:45.700 --> 02:18:53.640
if if I join a server that only allows talking about football, and then I I start following people from other servers,

1821
02:18:53.985 --> 02:18:59.765
The football server, we will have to fetch all these posts from the these other servers that are not

1822
02:19:00.465 --> 02:19:02.485
their their its main interest,

1823
02:19:02.800 --> 02:19:06.420
and then it becomes a I think it doesn't scale very much.

1824
02:19:06.880 --> 02:19:11.405
It only scales if there's some big servers, and I don't know. I'm

1825
02:19:11.785 --> 02:19:12.444
not sure.

1826
02:19:12.905 --> 02:19:16.444
But I I don't think the incentives are aligned. I don't know how it's working

1827
02:19:16.905 --> 02:19:21.260
to this day, but seems to be working. But the the the main problem is this, of the identity.

1828
02:19:25.285 --> 02:19:34.186
I dig it. I like that concept. I mean, that was the main thing that was pushing me away. And to be honest, like, the freak say, like, why don't I use masks? I'm more like, fuck social media.

1829
02:19:35.240 --> 02:19:39.340
Like, I just you know, I'm gonna use Twitter till I get banned and then

1830
02:19:39.960 --> 02:19:40.460
sayonara.

1831
02:19:42.716 --> 02:19:46.096
You know, I use I like the private group chats. I I think it's

1832
02:19:46.636 --> 02:19:50.600
a it's a healthier it's a healthier way to stay in touch with people and have

1833
02:19:51.159 --> 02:19:52.060
real discussions.

1834
02:19:53.720 --> 02:19:57.100
Obviously, I think dispatch is a great format for real discussion as well.

1835
02:20:00.425 --> 02:20:02.604
Yes. So, I mean, I think this has been a great conversation.

1836
02:20:04.024 --> 02:20:04.524
Oh,

1837
02:20:04.825 --> 02:20:10.080
this is one thing I wanna talk about, l and URL. So we have the we have the QR code on the bottom left.

1838
02:20:13.261 --> 02:20:14.721
I saw you, like,

1839
02:20:15.075 --> 02:20:16.855
talking shit about the lnurl

1840
02:20:17.235 --> 02:20:17.735
maintainer.

1841
02:20:18.755 --> 02:20:19.415
Like, the,

1842
02:20:20.115 --> 02:20:24.400
you wanna talk about the maintainer now. Yeah. Or now you're the maintainer.

1843
02:20:25.660 --> 02:20:38.335
Hell, yeah. That's all you have to do. Listen up, kid. You have an open source project out there. You don't like the way things are being run. All you have to do is go talk shit on the maintainer, and it's gonna be yours now.

1844
02:20:38.830 --> 02:20:41.330
No. It's name Robson or something?

1845
02:20:42.430 --> 02:20:46.290
That that was not the maintainer. Like, that's just the guy who had the initial idea

1846
02:20:46.665 --> 02:20:47.405
for channels.

1847
02:20:48.265 --> 02:20:49.645
The the first idea was

1848
02:20:50.185 --> 02:20:52.444
with, like, getting a channel automatically

1849
02:20:52.825 --> 02:20:53.645
from us,

1850
02:20:54.024 --> 02:20:58.240
a peer from your mobile wallet. And then it was implemented by BOW.

1851
02:20:59.580 --> 02:21:04.561
And then Anton was the maintainer, but then he gave the repository to me. I think he

1852
02:21:05.965 --> 02:21:08.784
got didn't like it anymore. I don't know.

1853
02:21:09.564 --> 02:21:10.845
But the guy who invented it,

1854
02:21:12.610 --> 02:21:15.270
he thought he he he thought that

1855
02:21:16.130 --> 02:21:22.186
by encoding the like, this QR code, it has a bunch of garbage on

1856
02:21:22.645 --> 02:21:29.545
it, bunch of letters, and these letters are batched 32 encoded URLs, normal URLs.

1857
02:21:31.239 --> 02:21:32.540
And it could be just,

1858
02:21:33.319 --> 02:21:33.720
a normal

1859
02:21:34.439 --> 02:21:51.250
a plain URL instead of the batch 32 thing. But but the guy thought that the QR codes would be smaller if you encoded it in this batch 32 thing. Mhmm. But in fact, they aren't. Like, you could he could have checked this in one minute, but he didn't.

1860
02:21:51.630 --> 02:21:55.954
So now we're stuck with this protocol that we can't change now because it will break everything.

1861
02:21:56.255 --> 02:22:02.880
Oh, no. That would be easier if it was just a URL. It was just a Yeah. Plain text QR code URL. Right? Yes. Yes.

1862
02:22:04.800 --> 02:22:10.979
So we can't change it now? Why can't we change it now? Like, how are we on your end user? Man. Just put in a pull request. What's going on?

1863
02:22:12.165 --> 02:22:16.586
Yeah. I could just change the thing on the the protocol, and then that will just break everything.

1864
02:22:17.445 --> 02:22:24.590
There's not there's not many wallets that support it yet. Right? Are there? I mean, BLW supports it. Wallet and Satoshi supports

1865
02:22:25.210 --> 02:22:26.590
it. Zeus supports it.

1866
02:22:27.370 --> 02:22:28.695
Does Zeus support it?

1867
02:22:29.176 --> 02:22:33.195
Oh, yeah. Well, we support a bunch of them, and it's mostly yeah. Jeff's doing.

1868
02:22:33.815 --> 02:22:34.315
But,

1869
02:22:34.775 --> 02:22:38.590
we we don't support, what is it, channel or auth yet?

1870
02:22:39.070 --> 02:22:51.545
I'd really like to get auth in. I think auth is my favorite one. This is cheap. These things are all different. Like, they're separate. It's weird that they all have the same name. But Yeah. They're different concepts sort of Yeah. On top of Lightning.

1871
02:22:52.645 --> 02:22:54.984
But, yeah, they all have to be implemented separately.

1872
02:22:55.670 --> 02:23:06.285
But, yeah, auth is the idea that you can, you know, be connected on your to your node. Right? And then you were presented with a QR code on-site to log in. You scan it.

1873
02:23:07.785 --> 02:23:13.311
Your node talks to the web server, and, you get logged in. I think

1874
02:23:13.690 --> 02:23:17.150
that's really awesome way to get rid of passwords in a lot of places.

1875
02:23:17.690 --> 02:23:21.615
So, Jeff, my question is, what the hell do we have to do to get this working in Zeus?

1876
02:23:22.895 --> 02:23:23.395
Well,

1877
02:23:24.335 --> 02:23:26.915
I don't know. You have to look at what Breeze did,

1878
02:23:27.775 --> 02:23:30.275
because they they did something with the LND keys.

1879
02:23:31.610 --> 02:23:35.070
Yeah. You you just have to to use a a private key.

1880
02:23:36.250 --> 02:23:41.455
Where that does that private key comes from doesn't matter very much very much, but it's it's better

1881
02:23:42.075 --> 02:23:44.895
if you were reusing your Bitcoin seed key.

1882
02:23:46.075 --> 02:23:46.575
So

1883
02:23:46.955 --> 02:23:47.455
yeah.

1884
02:23:47.811 --> 02:23:55.030
Yeah. Gotcha. Last time I was looking at it, LND needed a fix, but, yeah, it seems like the Breeze guys has some sort of workaround.

1885
02:23:55.405 --> 02:23:57.905
Yeah. Yeah. There's a workaround. You you I think they

1886
02:23:58.605 --> 02:24:05.470
they LND has that sign message thing, and you can sign a message that's in the protocol, like, on the in the LNUR

1887
02:24:06.090 --> 02:24:10.990
of spec. Like, you sign a default message, and you use that signature because it's deterministic.

1888
02:24:11.450 --> 02:24:13.745
You use that as your LNUR

1889
02:24:15.005 --> 02:24:15.505
key.

1890
02:24:15.845 --> 02:24:16.345
So

1891
02:24:16.845 --> 02:24:22.705
Yeah. Yeah. That's just a way to generate the key from the LND node.

1892
02:24:23.050 --> 02:24:29.869
And and you need a different key for each site too. Right? Yeah. Yeah. Then you take that key and you h mac it with

1893
02:24:30.405 --> 02:24:31.545
the website's

1894
02:24:33.285 --> 02:24:47.770
the domain. Domain name. Yes. The. Then you have a key for the website. But the idea is that you you only need the the the seed key from LND, and you can generate all the other keys. Yeah. Yeah. But this is a very old idea, like the the idea of ln URL.

1895
02:24:48.225 --> 02:24:51.524
There's a protocol called s q squirrel,

1896
02:24:52.064 --> 02:24:54.085
s q r l something

1897
02:24:54.545 --> 02:24:58.130
that did this exact same thing. Something you named it.

1898
02:25:01.410 --> 02:25:01.910
Sorry.

1899
02:25:03.170 --> 02:25:03.670
Okay.

1900
02:25:04.130 --> 02:25:05.350
And there's the

1901
02:25:06.290 --> 02:25:07.605
bit bit I.

1902
02:25:08.485 --> 02:25:16.266
What's what is called? Bit I Bit ID. I don't I don't know. Someone did a Bitcoin case. But this is true, and maybe there are others.

1903
02:25:17.350 --> 02:25:21.130
The the problem with them is that you can't manage the middle people.

1904
02:25:22.069 --> 02:25:22.810
You can

1905
02:25:23.955 --> 02:25:24.774
make the

1906
02:25:25.475 --> 02:25:31.495
a website can make you sign something that's actually valid for the other website, and then they steal your

1907
02:25:32.730 --> 02:25:33.710
your credentials.

1908
02:25:34.090 --> 02:25:34.570
But,

1909
02:25:34.971 --> 02:25:35.471
lnurloff

1910
02:25:37.210 --> 02:25:38.910
solves that by generosity,

1911
02:25:40.730 --> 02:25:41.230
by

1912
02:25:41.595 --> 02:25:42.654
making these keys

1913
02:25:43.034 --> 02:25:44.975
get they are different for each domain.

1914
02:25:46.635 --> 02:25:50.720
And in practice in practice, what the user is seeing is and I and I

1915
02:25:51.279 --> 02:25:53.700
I may or may not have tested this out with lnmarkets.com,

1916
02:25:54.800 --> 02:26:19.591
is that you can just, like, sign you could just you just open a lightning wallet that's compatible. I mean, Phoenix is the one that I tried it with. I did or I didn't try it with. And then you just scan the QR code, and it just automatically signs you in. And every time you wanna sign back in, you just scan the QR code. And it's as simple as that for the end user. Right? Yeah. Yep. Yeah. Rules. Rules w two. It doesn't it doesn't have to be a lightning wallet, actually. Could be any key.

1917
02:26:20.195 --> 02:26:34.320
Right. But I'm just saying I'm saying in in practice, this is what a Bitcoin user would see probably. Right? They probably would see a lightning one. The cool part is you already have the wallet. Right? And you're and, presumably, you're gonna be funding the service with that same wallet. Right? So you use lnurl

1918
02:26:34.780 --> 02:26:39.265
for withdrawals, and you use lightning for deposits, and you use lnurl off for

1919
02:26:42.225 --> 02:26:49.750
I guess you could use lnurl to pay as well, but you you can use the whole stack. What's interesting is ln markets is down, by the way, right now.

1920
02:26:50.210 --> 02:26:50.710
Amazon

1921
02:26:51.330 --> 02:26:52.470
Amazon CloudFront.

1922
02:26:53.676 --> 02:26:59.615
Oh, block for my country. It's because I oh, I see. My VPN is is in America right now.

1923
02:27:02.930 --> 02:27:03.670
It happens.

1924
02:27:04.050 --> 02:27:04.790
It happens.

1925
02:27:06.050 --> 02:27:09.430
VPNs don't exist, so, like, of course, the IP blocks work.

1926
02:27:09.970 --> 02:27:10.610
So the

1927
02:27:11.605 --> 02:27:15.145
so we we hit that. That was so I think Ellen URL to me,

1928
02:27:16.965 --> 02:27:20.425
you know, maybe I'm a little bit biased as a content creator, but

1929
02:27:21.600 --> 02:27:26.260
it's kind of to me, it's like this holy grail that we've been working for for a while where,

1930
02:27:29.335 --> 02:27:33.435
and I see this in in the work I do with activists who are trying to accept donations.

1931
02:27:33.814 --> 02:27:35.435
This idea that we could have,

1932
02:27:36.239 --> 02:27:37.220
like, a fixed

1933
02:27:37.760 --> 02:27:42.100
some kind of fixed text or fixed QR code that never changes,

1934
02:27:42.695 --> 02:27:46.155
that still allows you to accept donations in a relatively private way.

1935
02:27:47.255 --> 02:27:53.120
Because let's be honest. Like, if you're accepting donations, like, BTC pay server is way too heavy. Like, that's that's ridiculous.

1936
02:27:55.340 --> 02:28:04.135
So would you agree, Fio, Jeff, that, like, that's kind of our best path forward right now? Like, you know, stealth addresses, you know, aren't really happening on Bitcoin.

1937
02:28:06.354 --> 02:28:06.854
Yeah.

1938
02:28:07.180 --> 02:28:08.560
I think it's good for donations.

1939
02:28:08.939 --> 02:28:10.880
They're a new pay thing. But,

1940
02:28:12.859 --> 02:28:14.479
yeah, I think it's good for donations.

1941
02:28:15.105 --> 02:28:18.325
But my idea with it, initially, when I suggested

1942
02:28:18.945 --> 02:28:23.205
it, was, like, to make things in the physical world

1943
02:28:23.745 --> 02:28:24.485
with it.

1944
02:28:24.980 --> 02:28:33.160
Because on the on the website, if you're joining web open a website, the website can generate a, like, invoice, not a normal, like, an invoice

1945
02:28:33.625 --> 02:28:37.404
to you at any at any time. But in the in the in the streets,

1946
02:28:37.705 --> 02:28:48.449
like, you're and you're going you want to buy some food on the street, and the the seller can just have a single QR code there. And you scan it, and the the seller knows your bot

1947
02:28:49.015 --> 02:28:50.315
and that kind of thing.

1948
02:28:51.655 --> 02:28:54.715
There are many many niche niche use cases like this.

1949
02:28:56.215 --> 02:29:00.330
Yeah. But for for streams like this, like, you use this, it's good to

1950
02:29:01.529 --> 02:29:05.790
and the the it besides just making a payment, there's also

1951
02:29:06.936 --> 02:29:17.200
like, you can return stuff to the user so you can have some form of interactivity there. Like, the user receives a code on their wallet, and they use the code to open a door or something, Or

1952
02:29:17.660 --> 02:29:18.160
they

1953
02:29:18.620 --> 02:29:22.640
I don't know. If if you saw, like, there's there's videos from,

1954
02:29:23.100 --> 02:29:26.325
I forgot what the channel is, but that's BTC socialist

1955
02:29:26.705 --> 02:29:34.485
is in these videos. Right. And he puts a a QR code with a handler there. And if you scan and pay you a hand a 100 sets,

1956
02:29:34.811 --> 02:29:39.391
like, he gets slapped in the face by a Right. And he smoked bombs and stuff.

1957
02:29:40.730 --> 02:29:41.790
Yeah. Classic.

1958
02:29:42.971 --> 02:29:43.471
Yeah.

1959
02:29:44.436 --> 02:29:50.915
That's that's the visual that's the visual I had. And he's working on he's working on that with Ellen Bits, I think, like, to have,

1960
02:29:51.730 --> 02:29:56.950
I I guess that's it. He's the lead maintainer of that project to to create, like, basically a streamer school toolkit.

1961
02:29:57.730 --> 02:29:59.750
If you're a streamer and you want to

1962
02:30:01.176 --> 02:30:04.476
add the add these things, he's, like, making it so it works with,

1963
02:30:05.016 --> 02:30:05.516
OBS,

1964
02:30:06.615 --> 02:30:09.516
which is, like, a very common software that streamers use.

1965
02:30:11.080 --> 02:30:17.740
So, Fia, Jeff, I mean, one of the things that I really like about you is that you're super contrarian. I feel like you're always, like, mouthing off at people,

1966
02:30:18.655 --> 02:30:23.476
on Twitter, but but you do it from a, like, a builder's point of view. Like, I feel like you're also,

1967
02:30:24.176 --> 02:30:25.556
you know, like, you're building

1968
02:30:26.460 --> 02:30:29.841
you're building products that you know, projects that

1969
02:30:30.301 --> 02:30:33.665
that I feel like there's just, like, not that much focus on. Like, once again, like,

1970
02:30:34.545 --> 02:30:37.925
l l n t x bot, like, you think it's, like, this boring project,

1971
02:30:38.545 --> 02:30:46.460
but it's, like, a super useful thing that, like, I assume, you know, thousands of people are are it's probably one of the more popular lightning wallets.

1972
02:30:47.080 --> 02:30:50.061
No one's competing with you. Like, no one's even bothering to try.

1973
02:30:52.795 --> 02:30:56.335
What is like, before we leave here, like, what is

1974
02:30:56.636 --> 02:31:06.040
for the freaks, like, what is you know hit us with some contrarianism. Like, what what is a common fallacy that Bitcoiners powered all the time? What is something that frustrates you?

1975
02:31:06.694 --> 02:31:08.234
You know? Like, what like,

1976
02:31:11.255 --> 02:31:12.135
Yeah. Yeah. That's

1977
02:31:13.471 --> 02:31:20.051
well, the the last the latest one I've I've been thinking about is the the problem of lightning

1978
02:31:21.635 --> 02:31:22.135
HTLCs.

1979
02:31:23.475 --> 02:31:26.215
Like, there's this FUD from the caches.

1980
02:31:26.755 --> 02:31:28.440
I don't know if you remember, like,

1981
02:31:28.921 --> 02:31:31.740
some time ago. The guy is saying that, oh, HDLCs,

1982
02:31:32.841 --> 02:31:36.620
they they don't work for small payments because they are uneconomical,

1983
02:31:37.495 --> 02:31:44.235
and then everybody got mad at him. I just I forgot the name. Oh, it's Peter Rieseau, I think, was saying this.

1984
02:31:44.774 --> 02:31:52.949
But he's right, and everybody refused to acknowledge that, I think, or they acknowledge, but they say, oh, it's not a big problem. Because,

1985
02:31:55.010 --> 02:31:55.670
when you

1986
02:31:56.025 --> 02:31:56.766
when you

1987
02:31:57.305 --> 02:31:59.485
make a lightning payment, the HDLC,

1988
02:32:00.745 --> 02:32:04.445
it goes to like, you you create a virtual you create an output

1989
02:32:04.920 --> 02:32:05.739
for the HTLC

1990
02:32:06.040 --> 02:32:06.779
on your

1991
02:32:07.640 --> 02:32:08.779
commitment transaction.

1992
02:32:09.399 --> 02:32:11.100
And then if that HTLC

1993
02:32:11.640 --> 02:32:12.540
if the peer

1994
02:32:14.016 --> 02:32:15.235
fails you, like,

1995
02:32:15.615 --> 02:32:18.115
you have to close the channel and then redeem that HTLC.

1996
02:32:18.655 --> 02:32:21.955
Either the the receiver redeems it with a preimage

1997
02:32:22.311 --> 02:32:28.091
or the sender re redeems it after a time out. That's the the the the point.

1998
02:32:28.870 --> 02:32:29.370
And

1999
02:32:30.465 --> 02:32:33.846
for most well, like, if if the fees are, like, $5,

2000
02:32:34.865 --> 02:32:38.085
most lightning payments are below $5. And

2001
02:32:38.450 --> 02:32:39.190
when they're

2002
02:32:39.570 --> 02:32:40.390
over $5,

2003
02:32:41.970 --> 02:32:43.590
they get splitted by MPP,

2004
02:32:44.050 --> 02:32:47.030
and so they get below the the the threshold.

2005
02:32:47.985 --> 02:32:50.325
And then you don't create these these HDLCs

2006
02:32:50.785 --> 02:32:56.230
because they would be an economical to redeem on the chain. So they just don't exist,

2007
02:32:57.431 --> 02:33:03.770
and the the amounts go to the to the minor fees of that transaction if they that transaction ever gets published.

2008
02:33:05.395 --> 02:33:07.255
But the the node implementations,

2009
02:33:07.635 --> 02:33:09.016
they act like

2010
02:33:09.395 --> 02:33:12.056
like like if the HDLCs existed.

2011
02:33:12.595 --> 02:33:13.095
So

2012
02:33:13.471 --> 02:33:19.091
the HDLC doesn't exist. You can't redeem it, but your note says, oh, the other note isn't cooperating.

2013
02:33:19.631 --> 02:33:29.314
I'll close the channel to redeem the HDLC, and then it closes the channel. And then it the only day is realized there's no HDLC there, so it closed the channel for no reason.

2014
02:33:30.851 --> 02:33:33.351
So I've I've been talking to some people,

2015
02:33:33.891 --> 02:33:41.785
about this idea, and most of the people I'm talking to, they were they were like, oh, I think it's not so bad, but I think this is really bad.

2016
02:33:42.645 --> 02:33:43.145
Yeah.

2017
02:33:43.445 --> 02:33:47.145
That was a contrary, very complex, I think.

2018
02:33:48.900 --> 02:33:55.160
There there there's ways to improve this that I came up with, but other people may come up with better ways.

2019
02:33:55.795 --> 02:33:59.415
I mean, the main takeaway, right, is that, like, if if you do a transaction

2020
02:33:59.955 --> 02:34:02.295
on lightning that's under the dust limit

2021
02:34:03.020 --> 02:34:05.280
of whatever the dust limit is at any given time,

2022
02:34:06.140 --> 02:34:07.840
potentially dust limit in the future,

2023
02:34:09.180 --> 02:34:14.145
then all of a sudden, that's not a trust minimized payment anymore. Right? Because there's no way to actually settle it.

2024
02:34:14.765 --> 02:34:17.345
That's the that's the crux of the

2025
02:34:18.045 --> 02:34:18.545
issue.

2026
02:34:19.460 --> 02:34:25.880
Yeah. And then the the entire lightning protocol assumes that you get a preimage that's a proof of your payment.

2027
02:34:26.739 --> 02:34:35.645
Right. But you don't get that preimage if the channel if the if the like, in a normal HDLC, the ideal world in which everything is HDLCs,

2028
02:34:36.104 --> 02:34:37.085
you would get

2029
02:34:38.670 --> 02:34:40.931
that. Even if a channel failed in the middle,

2030
02:34:41.311 --> 02:34:47.715
the the the party would still see the preimage on the chain and pass the preimage back back until it gets to the to the sender.

2031
02:34:48.895 --> 02:34:51.395
But if these HDFCs don't exist,

2032
02:34:51.854 --> 02:34:56.595
there's no preimage. So you could have paid. The person could have received the payment,

2033
02:34:56.960 --> 02:34:58.820
but you never get a proof of payment.

2034
02:34:59.280 --> 02:35:00.820
I think this is serious because

2035
02:35:01.280 --> 02:35:07.155
Yeah. Yeah. It doesn't happen very often, I think. Or maybe it it does it, but we don't know.

2036
02:35:08.335 --> 02:35:15.551
But I think this is serious, and I think people should stop pretending it lightning is fully trustless, like and

2037
02:35:16.410 --> 02:35:18.990
face the fact that these payments aren't trustless,

2038
02:35:19.370 --> 02:35:25.305
and then do something about it instead of just assuming they are and closing the channels for no reason.

2039
02:35:29.471 --> 02:35:32.610
And what I feel like happens is, like, whenever you bring it up, like

2040
02:35:33.150 --> 02:35:38.690
like, there's there's just, like, a lot of hand waving. Like, oh, well, like, you should just pick trusted channel partners.

2041
02:35:39.295 --> 02:35:41.795
Yeah. But that doesn't Like, what are we doing here?

2042
02:35:42.814 --> 02:35:45.935
Yeah. But even if you have trusted channel partners, like, the it's

2043
02:35:46.640 --> 02:35:55.665
most of the times, it's not the fault of your channel partner. It's not the channel partner trying to cheat on you. It's just a fail a a bug or some other beer,

2044
02:35:57.005 --> 02:35:59.265
did something on on the on the web.

2045
02:35:59.645 --> 02:36:07.350
The confirmation not getting all the way back. Yeah. It's definitely a issue then. But if it would be much better, the protocol, if we

2046
02:36:07.650 --> 02:36:09.830
face this this fact and

2047
02:36:10.165 --> 02:36:12.585
realize it's not fully trustless, but

2048
02:36:13.125 --> 02:36:15.305
we can still use it and

2049
02:36:15.685 --> 02:36:17.465
stop closing channels for no reason.

2050
02:36:19.850 --> 02:36:24.270
Yeah. If you want trustless, then you use the main chain and and pay the fees as,

2051
02:36:25.285 --> 02:36:29.545
you know, as you have to because because you're using a a, you know,

2052
02:36:30.325 --> 02:36:32.105
a a very robust protocol.

2053
02:36:32.760 --> 02:36:35.819
And if you wanna if you wanna lighter trade off balance,

2054
02:36:36.359 --> 02:36:37.819
that is cheaper and faster,

2055
02:36:38.760 --> 02:36:41.659
that requires a little bit more trust, then you use Lightning. Right?

2056
02:36:43.185 --> 02:36:44.325
Yeah. Yeah.

2057
02:36:45.025 --> 02:36:46.645
And I think a a better model

2058
02:36:47.185 --> 02:36:49.525
for these that involves more trust

2059
02:36:50.450 --> 02:36:53.989
and maybe 3rd party arbiters to to prevent

2060
02:36:55.170 --> 02:36:55.670
abuses,

2061
02:36:56.210 --> 02:36:58.229
like, would scale better

2062
02:36:58.676 --> 02:37:00.615
and would allow for other kinds

2063
02:37:01.315 --> 02:37:03.976
of payment protocols to be integrated with

2064
02:37:04.355 --> 02:37:05.096
more easily.

2065
02:37:06.330 --> 02:37:09.310
I don't know. And, also, we would we could use p t

2066
02:37:09.690 --> 02:37:11.950
p p t lcs, like the the

2067
02:37:12.730 --> 02:37:13.790
DLC stuff

2068
02:37:14.386 --> 02:37:16.325
Today without without Taproot

2069
02:37:17.025 --> 02:37:19.285
because it wouldn't tap on the chain.

2070
02:37:20.545 --> 02:37:22.165
It would never go to the chain.

2071
02:37:26.070 --> 02:37:27.131
Without Taproot?

2072
02:37:27.750 --> 02:37:32.755
Yeah. Without Taproot. Would you wanna jump into that? I mean, I'm a little bit confused on what you just said there.

2073
02:37:33.475 --> 02:37:33.975
Yeah.

2074
02:37:34.915 --> 02:37:35.575
No. No.

2075
02:37:36.274 --> 02:37:37.415
Let's skip this.

2076
02:37:38.035 --> 02:37:41.335
Okay. Fair enough. That's what I love about Bitcoin. I feel like

2077
02:37:42.740 --> 02:37:46.040
we're all just different levels of confused, and we're just doing it together.

2078
02:37:47.061 --> 02:37:48.360
Yeah. I'm definitely confused.

2079
02:37:51.995 --> 02:37:53.615
I mean, this has been a great conversation.

2080
02:37:54.635 --> 02:38:00.734
I really appreciate you joining us. I mean, like, I I think I said this in the beginning. I don't know if we're on air yet, but this is

2081
02:38:03.351 --> 02:38:05.530
your your first English language podcast,

2082
02:38:06.150 --> 02:38:10.330
which is fucking awesome. I it's I'm very proud of the amount of

2083
02:38:12.335 --> 02:38:16.915
podcast virginities I've taken here on dispatch over the last, 22 episodes.

2084
02:38:18.255 --> 02:38:19.155
I think it's

2085
02:38:20.290 --> 02:38:29.591
it's just a it's it's it's just it's awesome. I I I I wanna do something different with dispatch. I don't wanna do more of the same. There's a lot of content out there for you freaks,

2086
02:38:31.875 --> 02:38:36.935
and I, you know, I wanted to do something unique and something something different that added value.

2087
02:38:38.194 --> 02:38:38.694
So

2088
02:38:39.210 --> 02:38:42.590
every day that I get to do that with dispatch is fucking awesome.

2089
02:38:43.770 --> 02:38:49.685
Yeah. We have John Fisher in the comments over my head. One of the other cool things is I one thing I've noticed with bit devs,

2090
02:38:50.705 --> 02:38:55.600
is, like, I feel like even if the over the head stuff is happening around you, you kinda just, like,

2091
02:38:56.080 --> 02:39:05.665
you absorb some of it, and you just keep doing it, and you'll just keep absorbing it. I only understood how Bitcoin based things work, like, after many years of not

2092
02:39:06.045 --> 02:39:10.545
thinking I I had understood what was wrong, and then I read something old.

2093
02:39:11.165 --> 02:39:14.721
And I didn't understand that it's not it was

2094
02:39:15.101 --> 02:39:16.961
terrible, but it's good in the end.

2095
02:39:17.421 --> 02:39:17.921
Exactly.

2096
02:39:18.860 --> 02:39:20.801
I'd like if you're not, you know,

2097
02:39:21.155 --> 02:39:38.880
if you're not confused, you're probably not pushing yourself hard enough, I think, is, like, a a relatively good rule of thumb. Yeah. Yeah. And don't pretend you, like, know something you don't. Like, it's such a deep rabbit hole with all these sub rabbit holes you can get sucked down to and you know? It's obviously impossible to keep track of it all.

2098
02:39:39.285 --> 02:39:40.585
So with all that said,

2099
02:39:41.365 --> 02:39:45.945
do you guys have any final topics that you wanna discuss before we wrap it up here?

2100
02:39:51.490 --> 02:39:53.351
I don't think so. Jeff, you got anything?

2101
02:39:54.210 --> 02:39:55.670
Oh, I've talked too much.

2102
02:39:57.354 --> 02:40:02.395
Not enough. You have not talked enough. It it's been an honor to have you here. You gotta come back on,

2103
02:40:02.955 --> 02:40:08.450
do some other issues. I'm sure Matt will pair you up with someone who pokes a little less fun at you. But I'm still

2104
02:40:09.150 --> 02:40:13.650
I'm still a little bit shocked you came on for you, Jeff, to be honest. I it's it's been an honor.

2105
02:40:15.245 --> 02:40:16.065
Good. Okay.

2106
02:40:16.845 --> 02:40:21.104
Well, I appreciate both of you guys. I appreciate the work you've done. I appreciate you coming on.

2107
02:40:21.405 --> 02:40:25.311
I encourage you to continue your work. I will do my best,

2108
02:40:26.170 --> 02:40:29.391
from my pedestal to support you guys and use your

2109
02:40:30.010 --> 02:40:30.510
projects

2110
02:40:30.970 --> 02:40:31.470
and

2111
02:40:32.285 --> 02:40:35.905
advocate for people to support and use them as well.

2112
02:40:37.484 --> 02:40:38.465
On that note,

2113
02:40:39.290 --> 02:40:40.830
if you're an open source contributor

2114
02:40:41.210 --> 02:40:42.590
and you're looking for funding,

2115
02:40:42.970 --> 02:40:44.990
consider submitting your project at opensats.org.

2116
02:40:45.850 --> 02:40:46.910
We're gonna be announcing

2117
02:40:47.755 --> 02:40:49.056
our first sets of grants

2118
02:40:49.516 --> 02:40:50.255
very soon,

2119
02:40:51.355 --> 02:40:55.375
probably at the conference. We'll see on June 4th, June 5th in Miami.

2120
02:40:58.020 --> 02:40:59.399
If you haven't already,

2121
02:40:59.779 --> 02:41:00.279
consider

2122
02:41:00.739 --> 02:41:02.520
donating to the

2123
02:41:03.540 --> 02:41:05.239
Bitcoin car at the Indy 500

2124
02:41:05.545 --> 02:41:10.025
that is being led by Jack Mahler's. He will not be driving it. Ed Carpenter will be driving it. But,

2125
02:41:11.465 --> 02:41:19.891
he he is leading the initiative, and all those funds are going to open source development, Bitcoin focused open source development. You can get that at strike.me/racing.

2126
02:41:21.806 --> 02:41:25.665
Also, as I said earlier in the show, any donations that came in through that lnurlqr

2127
02:41:26.445 --> 02:41:26.945
code,

2128
02:41:27.965 --> 02:41:30.865
during the length of the show will be split 5050

2129
02:41:31.870 --> 02:41:35.170
between me to recoup costs and, the IndyCar.

2130
02:41:36.350 --> 02:41:37.729
You should also pressure

2131
02:41:38.350 --> 02:41:39.810
every company in the space

2132
02:41:40.266 --> 02:41:43.806
and every person who likes to flex about how much Bitcoin they own on Twitter,

2133
02:41:44.506 --> 02:41:49.645
into donating here. It's a very baller initiative. We have a race car that will win the race.

2134
02:41:50.460 --> 02:41:57.120
It's a very flashy race car, and it's a good time to peer pressure your favorite influencer and corporation, so consider doing that.

2135
02:41:59.194 --> 02:42:01.935
Yeah. With all that said, I thank both of you guys.

2136
02:42:02.475 --> 02:42:04.015
Evan, I'll see you in Miami.

2137
02:42:04.715 --> 02:42:07.755
Fiat, Jeff, I hope to meet you one day in person and,

2138
02:42:08.410 --> 02:42:11.950
split a beer. Well, we could have our own beers, but but share beers.

2139
02:42:13.210 --> 02:42:14.350
And thank you both.

2140
02:42:16.010 --> 02:42:16.750
Thank you.

2141
02:42:17.175 --> 02:42:19.194
Yeah. Thanks again for having me again, Matt.

2142
02:42:20.534 --> 02:42:21.435
Cheers, freaks.

2143
02:42:33.505 --> 02:42:34.244
Good morning.

2144
02:42:39.104 --> 02:42:39.925
Good morning.

2145
02:42:44.740 --> 02:42:45.561
Good morning.

2146
02:42:50.345 --> 02:42:51.165
Good morning.

2147
02:42:56.904 --> 02:43:01.800
Wake up, mister West, mister West, mister Fresh, mister by himself, he's so impressed.

2148
02:43:02.260 --> 02:43:14.975
I mean, damn, did you even see the test? You got d's mom, The d's, Rosie Perez. And yes, barely passed. Any and every class looking at every f. Cheated on every test, I guess. This is my dissertation,

2149
02:43:15.275 --> 02:43:17.840
homie, this this basic. Welcome to graduation.

2150
02:43:18.700 --> 02:43:19.440
Good morning.

2151
02:43:24.355 --> 02:43:25.016
Good morning.

2152
02:43:30.035 --> 02:43:30.855
Good morning.

2153
02:43:35.619 --> 02:43:36.439
Good morning.

2154
02:43:41.355 --> 02:43:42.095
Good morning.

2155
02:43:42.395 --> 02:43:44.415
On this date, we've become legendary.

2156
02:43:44.875 --> 02:43:52.080
Everything we dreamed of. I'm like the fly Malcolm x by any genes necessary. Detroit red cleaned up

2157
02:43:52.460 --> 02:44:04.635
from the streets of the league, from an eighth to a key. But you graduate when you make it about it. Streets from the moments of pain. Look how far we done came. Hate to say and you change, now you're doing your thing. Good morning.

2158
02:44:09.440 --> 02:44:10.340
Good morning.

2159
02:44:15.225 --> 02:44:16.045
Good morning.

2160
02:44:20.825 --> 02:44:21.645
Good morning.

2161
02:44:26.480 --> 02:44:28.660
Good morning. Look at the valedictorian,

2162
02:44:29.520 --> 02:44:31.895
scared of the future while I hop in in delorean.

2163
02:44:32.435 --> 02:44:48.795
Scared to face the world, complacent career student. Some people graduate, but you're still stupid. They tell you read this, eat this. Don't look around, just peep this. Preachers, teachers, Jesus. Okay. Look up now. They done stole your street ness. After all of that, you received this.

2164
02:45:29.975 --> 02:45:35.370
Love you, freaks. Thank you for tuning in for another Bitcoin Tuesday. You guys make it all worth it.

2165
02:45:36.311 --> 02:45:38.170
Just a quick reminder that

2166
02:45:38.485 --> 02:45:42.025
CITIL Dispatch is available on all of your favorite podcast apps.

2167
02:45:42.806 --> 02:45:45.226
It makes me feel dirty, but consider subscribing

2168
02:45:45.690 --> 02:45:49.950
and giving a good review. It does go a long way. I do appreciate it.

2169
02:45:50.410 --> 02:45:57.465
I will see you on Thursday for rabbit hole recap. I'll see you next Tuesday for Citadel dispatch. I have about

2170
02:45:58.005 --> 02:45:58.505
20

2171
02:45:59.045 --> 02:46:03.305
dispatch first run hats left. If you want 1, hit me up

2172
02:46:03.841 --> 02:46:05.380
via Telegram or Keybase.

2173
02:46:06.000 --> 02:46:08.261
I love you all. Stay humble, stack sets.

2174
02:46:09.280 --> 02:46:11.540
200 k by conference day still in play.