1
00:00:00,000 --> 00:00:28,320
Hello, and we're back. And we're back.

2
00:00:28,320 --> 00:00:32,639
There was some problem there. Sorry about that. Can you hear me now?

3
00:00:32,639 --> 00:00:41,200
Yes, now I can hear you. I don't know what it would be.

4
00:00:41,200 --> 00:00:47,279
Yeah, we were talking about Zcash and Monero. It seems like Zcash has some very smart people

5
00:00:47,279 --> 00:00:53,080
there and Monero has a strong community. It would be great if the whole privacy community

6
00:00:53,080 --> 00:01:00,480
in the blockchain world could come together on one project. Maybe the Zcash sidechain

7
00:01:00,480 --> 00:01:05,160
would be that project. It would have the best of all worlds. What do you think about that

8
00:01:05,160 --> 00:01:06,160
idea?

9
00:01:06,160 --> 00:01:18,120
Yes, so my personal take is that, yeah, sure, this Zcash stuff is very interesting. And

10
00:01:18,120 --> 00:01:31,639
I think full membership on all set with this non-trusted setup kind of stuff is very, very

11
00:01:31,639 --> 00:01:40,239
interesting. But I personally think that we should keep as much off-chain as possible.

12
00:01:40,239 --> 00:01:46,480
So I very much like these approaches where we are optimistically trying to keep the state

13
00:01:46,480 --> 00:01:56,199
of some blockchains that are highly replicated and easily surveilled. So that is why I'm

14
00:01:56,199 --> 00:02:02,919
more interested in the Bitcoin clone sidechains, where you just add more cheaper Bitcoin block

15
00:02:02,919 --> 00:02:11,240
space and you have the same contractual capability and you can do stuff like the Ark layer 2

16
00:02:11,240 --> 00:02:21,039
Lightning on top of them. I am more interested in that. Maybe I'm a bit of a boomer about

17
00:02:21,039 --> 00:02:26,600
Bitcoin, but I kind of like the approach it takes. I'm more interested in it. I'm more

18
00:02:26,600 --> 00:02:33,839
intrigued by it than altcoins and what they are trying differently. But I'm not against

19
00:02:34,240 --> 00:02:45,399
them pursuing these alternative approaches. They should feel free to do so. And that's kind of how I

20
00:02:45,399 --> 00:02:53,679
see it and why I'm saying I'm more interested in Thunder and stuff like that. Because they're just

21
00:02:54,240 --> 00:03:05,240
more sensible to me to be very, very economic with block space. And it's good if it's there. It's

22
00:03:05,240 --> 00:03:11,720
good if it's there when you really need it, when you have to settle disputes. But optimistically,

23
00:03:11,720 --> 00:03:17,839
we can keep a lot of the stuff off-chain. And I kind of like that line of approach.

24
00:03:23,839 --> 00:03:33,360
Welcome, Paul. Paul is joining the stage. Hi, Paul. We were chatting about Zcash and privacy

25
00:03:33,360 --> 00:03:34,080
drivechains.

26
00:03:37,320 --> 00:03:40,559
Oh, cool. Great. Happy Monday, everyone.

27
00:03:42,479 --> 00:03:43,119
Hello.

28
00:03:47,399 --> 00:03:52,759
I saw you're a posted Bitcoin dev. I hope you get an answer. I think it's quite likely that you are

29
00:03:53,559 --> 00:04:02,880
correct. Because it's the type of thing that probably no one... Well, you know, just like, the

30
00:04:02,880 --> 00:04:07,880
more time I spend in Bitcoin, the more you realize that no one actually reads anything. That's all

31
00:04:07,880 --> 00:04:11,960
just Twitter-based scholarship.

32
00:04:12,960 --> 00:04:22,079
Right. It would be very nice if someone like, you know, AG Towns or someone like that would, you

33
00:04:22,079 --> 00:04:29,160
know, give me a thumbs up. Like, yeah, you are on to something. It's probably right. That would

34
00:04:29,160 --> 00:04:37,760
help. But I think I'm probably right. I have spent some time on it. I have managed to discuss it

35
00:04:38,679 --> 00:04:49,359
with Jeremy Rubin. And he also said stuff that makes me think I am right about this. And it's kind

36
00:04:49,359 --> 00:04:55,880
of funny because, you know, everyone was talking about it, like it's a fact that you can implement

37
00:04:55,880 --> 00:05:06,720
Ark with APO. And everyone just took it, you know, someone somewhere once said that APO can emulate

38
00:05:06,720 --> 00:05:13,279
CTV and everyone just took that as cash money and run with it. And it turns out it's not exactly

39
00:05:13,279 --> 00:05:13,559
true.

40
00:05:23,559 --> 00:05:30,880
So yes, Zcash is... I think Zcash is a good example because it's something that... It's a situation

41
00:05:30,880 --> 00:05:38,519
where there's a lot of R&D done in an altcoin, but it has many other wacky distracting features such as

42
00:05:38,519 --> 00:05:47,320
having the attacks. It's also something where people will say... Sometimes people will say, well, we

43
00:05:47,320 --> 00:05:55,079
will scale in some way. And I say, well, it's not just about scale. It's about also privacy. I mean, I

44
00:05:55,079 --> 00:05:59,640
would also hope, I don't know if this is true, but I would hope that people would look to the Zcash

45
00:05:59,640 --> 00:06:07,640
thing and they would say, well, it's very difficult to be pro-privacy in this industry. And so anyone

46
00:06:07,640 --> 00:06:15,239
who is pro-privacy is... That is like a signal that they are very legit. But who knows?

47
00:06:17,359 --> 00:06:24,440
We were talking about how did Monero actually manage to attract a stronger network effect, seemingly?

48
00:06:24,679 --> 00:06:32,920
Like they have a more devoted crowd, a stronger crowd. They are more popular in the darknet markets

49
00:06:32,920 --> 00:06:38,600
and among the more rebel types, you know, the more further state types.

50
00:06:47,799 --> 00:06:51,000
I mean, all I'm saying is that I was in the industry for a really long time.

51
00:06:51,880 --> 00:06:58,040
Ricardo, who is not the creator... A lot of people think he's the creator of Monero, but that's not true.

52
00:06:58,839 --> 00:07:04,839
But a lot of people... He went on Bitcoin Uncensored, which almost everyone else refused to do.

53
00:07:06,359 --> 00:07:12,279
And they grilled him, but he basically said, well, what are we supposed to do if we want this thing?

54
00:07:12,279 --> 00:07:17,160
What are we going to do, wait for sidechains? And they were like, yes. And he's like, well,

55
00:07:17,239 --> 00:07:20,920
it's like, call me back when there are sidechains, which is honestly,

56
00:07:20,920 --> 00:07:23,720
you know, was the right decision because that was back in 2015.

57
00:07:25,799 --> 00:07:30,600
So I think they started this thing and it was actually going nowhere for a really long time, but

58
00:07:32,279 --> 00:07:37,480
Ricardo, he did do a lot of different things. For example, they banned discussion of the price,

59
00:07:38,600 --> 00:07:44,359
which I think was key because by doing that, they kicked out all the people who were there for

60
00:07:44,359 --> 00:07:51,320
the wrong reasons. And that is how they at least got this one use case shipped of like, what you

61
00:07:51,320 --> 00:07:57,720
might call private something. And then I think it was just kind of a little bit of a self-reinforcing

62
00:07:57,720 --> 00:08:04,359
circle after that, because everyone else was just pumping things. And they said, any discussion of

63
00:08:04,359 --> 00:08:08,600
the price is like you get banned from the subreddit, you're banned from everything. And then they had

64
00:08:08,600 --> 00:08:12,200
like, they had that joke, you know, don't buy Monero. You remember that joke? Like, and they did

65
00:08:12,200 --> 00:08:17,720
the Bitcoin sign guy. It's the same joke, but I would honestly, they were so clever about it that

66
00:08:17,720 --> 00:08:23,239
I would fall for it every time. And they photoshopped it so that someone photoshopped it from buy Bitcoin

67
00:08:23,239 --> 00:08:28,119
to buy Litecoin. And everyone was like, this is so stupid. We hate this person. And then the Monero

68
00:08:28,119 --> 00:08:31,559
people replied to that. And you're like, oh, no, it's going to be Monero. And then it's like,

69
00:08:32,200 --> 00:08:37,640
Ricardo's face on the Bitcoin sign guy's head. And then it's don't buy Monero. And then you're like,

70
00:08:38,280 --> 00:08:42,679
ah, get me every time. So I think.

71
00:08:45,559 --> 00:08:49,400
As I remember, and I could be wrong, but this is how I remember it.

72
00:08:50,359 --> 00:08:55,960
As you said, Monero was really not going anywhere. They had a very hardcore crowd, but

73
00:08:56,760 --> 00:09:06,280
they had no real life adoption or any. The speculators were kept at arm's length.

74
00:09:07,880 --> 00:09:12,359
And then when it turned out that Bitcoin is not going to have, you know,

75
00:09:13,880 --> 00:09:20,039
significant block size increase or not going to go down apart with additional block size increases

76
00:09:20,039 --> 00:09:27,479
in the future, that's when Monero started to go up. A lot of people were suddenly looking for

77
00:09:27,479 --> 00:09:33,559
alternatives when that became clear. And that's when Monero started to go. And

78
00:09:33,559 --> 00:09:41,960
the moment they listed it from major exchanges, that whole momentum seemingly got just killed,

79
00:09:41,960 --> 00:09:48,840
obliterated. And they had basically skipped an entire cycle where it didn't really appreciate

80
00:09:49,640 --> 00:09:58,840
compared to Bitcoin. It was in a long stat field or something. At least this is how I remember that

81
00:09:58,840 --> 00:10:07,000
this just shows that basically a lot of the price action was probably still from speculators,

82
00:10:07,000 --> 00:10:12,760
no matter what they tried. So people are going to speculate on everything. That's just human nature.

83
00:10:12,840 --> 00:10:20,280
So that's how we live. Yeah. Another question talking about alternatives. Can some of you

84
00:10:20,280 --> 00:10:28,359
guys give some comments on these three coins? First, just the new, you know, the upgrade of

85
00:10:28,359 --> 00:10:35,400
Litecoin with MumbleBimble, for example, and then on Secret Network and ROSE, because they both

86
00:10:36,039 --> 00:10:43,559
all three are also related to, you know, putting security and anonymity in the transactions. Thanks.

87
00:10:46,520 --> 00:10:52,520
Oh, I've never heard of those last two, I think. But Litecoin certainly added MumbleWimble

88
00:10:52,520 --> 00:10:57,320
extension blocks. One of the weird things about that is there's just so many actually

89
00:10:57,320 --> 00:11:02,840
interesting facets of that, but I don't know if we have time for them all. But, you know,

90
00:11:02,840 --> 00:11:07,400
one is that people say like Litecoin is a staging ground for Bitcoin because SegWit was activated

91
00:11:07,400 --> 00:11:13,559
there first, but I don't actually agree with that. I think it's just there was no real opposition to

92
00:11:13,559 --> 00:11:20,760
SegWit, so doing it on Litecoin was kind of meaningless. But yeah, there was this MumbleWimble

93
00:11:20,760 --> 00:11:26,280
project and it's actually debatable whether or not MumbleWimble adds privacy because an adversary

94
00:11:26,280 --> 00:11:31,400
can just log everything. And then the key feature of MumbleWimble is that the transaction cut

95
00:11:31,400 --> 00:11:38,679
through can be deleted. You could delete it, but if everyone is listening

96
00:11:39,559 --> 00:11:46,520
on the network, then it's too late. So yeah, I don't know. I think a lot of the privacy claims are

97
00:11:47,320 --> 00:11:51,479
just like any other claim where it's a buzzword that people use.

98
00:11:52,440 --> 00:12:03,000
Thank you. The other two coins, one is especially ROSE, and this is really about privacy

99
00:12:03,799 --> 00:12:09,640
in these transactions. It's based on Cosmos, basically. You guys have never heard of that?

100
00:12:11,239 --> 00:12:15,159
No. Okay. There's lots of things to hear of.

101
00:12:16,039 --> 00:12:22,119
No problem. Hey, this is part of why BIP300 is so important, believe it or not. It's because

102
00:12:23,080 --> 00:12:30,520
the idea that everyone should have to hear about and then be justified to. You invent something,

103
00:12:30,520 --> 00:12:34,119
you have to explain it to everyone, you have to convince everyone that it's a good idea.

104
00:12:34,840 --> 00:12:39,159
That's really not very viable, and nothing else in the world works that way. When it does work

105
00:12:39,159 --> 00:12:43,559
that way, you have something where the king has to decide everything, or you have a dictator

106
00:12:43,719 --> 00:12:50,599
everything, or you have a dictatorship. That doesn't really ever work. What if you wanted

107
00:12:50,599 --> 00:12:56,760
to open a new restaurant, and you had to first go to the leader of the biggest restaurant in town,

108
00:12:56,760 --> 00:13:01,960
which would be, of course, this weird Soviet soup kitchen place that everyone is getting their food,

109
00:13:03,400 --> 00:13:10,280
and you go to them and you would say, excuse me, person, I want to open Subway sandwiches.

110
00:13:11,239 --> 00:13:15,080
You have to explain everything to them, and you say, oh, it'll be like this, it'll be like that.

111
00:13:16,840 --> 00:13:21,799
That world sucks compared to a world where someone can just launch a thing. I think that

112
00:13:21,799 --> 00:13:27,799
this is good. The ideal situation is that so much new stuff is being invented that

113
00:13:28,520 --> 00:13:33,640
almost no one has heard of anything. We've heard of basically zero percent.

114
00:13:34,280 --> 00:13:42,919
20,000 is the number of altcoins right now, or something like that. I think I have maybe

115
00:13:42,919 --> 00:13:50,359
have an idea about a dozen of them, what they do, and that's it. I'm not really interested in

116
00:13:50,359 --> 00:14:00,039
anything, just Bitcoin stuff mainly. Very, very little time spent on maybe privacy coins and

117
00:14:00,200 --> 00:14:09,239
nothing else. Even there, I just basically know something about Zcash and Monero, but that's it.

118
00:14:11,000 --> 00:14:15,640
Another very interesting is Holochain. I don't know if you guys have heard about that.

119
00:14:17,960 --> 00:14:24,919
They're really pioneering towards peer-to-peer, basically. It's a total 100 percent decentralized

120
00:14:24,919 --> 00:14:32,520
network, which is also working as a storage layer. Maybe have a look at that as well.

121
00:14:32,520 --> 00:14:37,000
I don't know anything about that, but I do know a little bit about the three. I think

122
00:14:37,000 --> 00:14:45,640
the idea is a good idea. The storage concept, like the Filecoin SIA storage type concept,

123
00:14:45,640 --> 00:14:50,039
I think is a cool idea because people have extra hard drive space. You're not using your

124
00:14:50,679 --> 00:14:56,280
internet. It's 3 a.m. when you're asleep, you're not using your internet connection. I don't know

125
00:14:56,280 --> 00:15:01,000
which version, which design will prevail, but I actually have always thought that that idea

126
00:15:01,000 --> 00:15:07,479
was pretty decent. Exactly what is happening, if you think about the major cloud providers like

127
00:15:07,479 --> 00:15:12,919
Google, Amazon, Microsoft, this is exactly what they're doing. But this is somehow, as well,

128
00:15:13,400 --> 00:15:20,760
dictatorship. Somehow, the prominent powers in the market who really control your whole data,

129
00:15:20,760 --> 00:15:26,760
because if you run all your jobs into a data center, into cloud, for example,

130
00:15:26,760 --> 00:15:31,400
eventually, these companies have access to it, whether you like it or not. It's just the truth.

131
00:15:32,200 --> 00:15:38,760
How do you really go about creating those environments where you're sure that they are

132
00:15:38,760 --> 00:15:47,000
GDPR compliant, that they are private? That's the beauty of these networks, probably, I think.

133
00:15:47,880 --> 00:15:53,239
Yeah, if you go to Amazon or whatever, they're going to guarantee not to lose your data. But

134
00:15:53,239 --> 00:15:58,599
what does that really mean? They're just going to split it up into 10 different encrypted pieces

135
00:15:59,960 --> 00:16:04,919
and put it in 10 different data centers. But you could also do that.

136
00:16:09,159 --> 00:16:13,000
Yeah, of course they do. Yeah, I agree. That's what I'm saying. I'm saying it's the same thing.

137
00:16:13,000 --> 00:16:20,599
So why be a middleman? Software eats the world, right? So why let them do that?

138
00:16:20,599 --> 00:16:25,239
And cloud computing becomes more important? Yeah, who wants them to have access to all of your

139
00:16:26,679 --> 00:16:34,280
photos and the emails you send to all the people, all your miscreants?

140
00:16:35,239 --> 00:16:42,359
Yeah, so I'm not even interested in cloud storage that is not client-side encrypted.

141
00:16:42,359 --> 00:16:48,760
The sad thing is that the whole power and a lot of the utility that cloud computing can give you

142
00:16:49,320 --> 00:16:56,359
is just not really working with encrypted data. So the whole thing that they are trying to sell

143
00:16:56,359 --> 00:17:03,000
us UX and stuff is just it gets completely disabled with client-side encryption. You can

144
00:17:03,320 --> 00:17:09,880
only manipulate and interpret the data on the clients. And that means you can't actually use

145
00:17:09,880 --> 00:17:14,599
the computers in the cloud. At least right now, this is where we are technologically.

146
00:17:14,599 --> 00:17:22,199
Maybe in the future, someone will invent a way where you can just create a completely bongo

147
00:17:22,199 --> 00:17:29,719
encrypted virtual architecture of yourself that nobody can decipher. And you can compile

148
00:17:29,719 --> 00:17:34,520
applications that run on this. And anyone that looks at the memory, they just see encrypted

149
00:17:34,520 --> 00:17:38,439
shit. But it's actually a tooling complete computer. Maybe we will get there someday.

150
00:17:38,439 --> 00:17:44,760
And you can have private cloud computing, you know, maybe. But right now, it's absolutely

151
00:17:44,760 --> 00:17:55,880
horrible. And I want none of that. Paul, when you reflect on the potential

152
00:17:55,959 --> 00:18:03,479
for drivechain to absorb the privacy coin community to Bitcoin, what do you think will

153
00:18:03,479 --> 00:18:09,880
be some of the interesting facets of that transition? If the privacy communities of

154
00:18:09,880 --> 00:18:17,479
Zcash and Monero and others were to completely move to the Zcash drivechain on Bitcoin,

155
00:18:17,479 --> 00:18:19,079
what would that look like, do you think?

156
00:18:26,839 --> 00:18:33,000
Well, I think, to be honest with you, I think it might take a little while. People would have

157
00:18:33,000 --> 00:18:39,560
to grow comfortable with this. But I think it would be driven. In general, my view of the side

158
00:18:39,560 --> 00:18:48,599
chains conquering the world is that people see no future in the altcoin. So I think right now,

159
00:18:50,119 --> 00:18:57,959
everyone who, if you work on Ethereum, or if you work on whatever, or if you live in that world,

160
00:18:57,959 --> 00:19:02,839
you kind of are imagining the possibility of flippening or, or at least carving out some

161
00:19:02,839 --> 00:19:09,239
kind of niche. But with sidechains, the niche is just not going to be there, really.

162
00:19:10,359 --> 00:19:15,560
Maybe there'll be some kind of weird niche, super proof of stake niche or something. But

163
00:19:16,839 --> 00:19:21,400
in general, the idea is that like, they lose hope. And so I would, the idea is that

164
00:19:22,839 --> 00:19:27,239
out of, eventually, people would see, you know, like the writing on the wall with Monero. And

165
00:19:27,239 --> 00:19:31,880
they said, listen, we are very good. We did the right thing by making this technology.

166
00:19:32,359 --> 00:19:37,160
We did the right thing by caring about privacy. But just this is the future. The future is just

167
00:19:37,160 --> 00:19:43,079
one coin with lots of different blockchains, lots of different software. And I think

168
00:19:45,160 --> 00:19:49,640
that is, you know, that would be like that. So then I think it would probably, I mean,

169
00:19:49,640 --> 00:19:55,719
I'm not sure, but privacy has a weird feature where sometimes it's like,

170
00:19:56,485 --> 00:20:02,485
very subversive things get it first, or very kind of shameful things get it first.

171
00:20:02,485 --> 00:20:07,205
And so it's not like a big, it's not a lot of fanfare when it switches over.

172
00:20:07,205 --> 00:20:13,444
But I would think that in general, people would want to really have it vetted, too,

173
00:20:13,444 --> 00:20:20,885
because you just imagine someone who really cares about privacy, they probably have a big stake in the outcome of whatever they're trying to do.

174
00:20:21,444 --> 00:20:33,284
So that could probably be like three major reasons why someone is, you know, becoming very privacy focused.

175
00:20:33,284 --> 00:20:39,845
The first is pretty obvious. I mean, if they are doing illegal stuff, then they want their privacy.

176
00:20:39,845 --> 00:20:48,885
So criminals probably love physical cash. I would imagine that they just absolutely love physical cash.

177
00:20:49,845 --> 00:20:55,045
But where they can't use physical cash, they want something, you know, very private.

178
00:20:55,045 --> 00:21:00,565
But and of course, the other part is people want to be ungovernable.

179
00:21:00,565 --> 00:21:06,885
So of course, the government wants to control people, but people don't want the government to control them.

180
00:21:06,885 --> 00:21:11,285
And again, of course, criminals also don't want the government to control them.

181
00:21:11,285 --> 00:21:13,205
But there are a lot of people who are not criminals.

182
00:21:13,205 --> 00:21:16,324
They just simply don't want the government to control them.

183
00:21:16,324 --> 00:21:18,165
They want to be ungovernable.

184
00:21:18,165 --> 00:21:28,565
And of course, the line blurs a little bit because these people basically cherry pick the laws that they are, you know, observing or keeping themselves.

185
00:21:28,565 --> 00:21:36,645
So they could be in a strict sense considered criminals because they won't, you know, uphold the laws that they find unjust.

186
00:21:36,645 --> 00:21:42,084
They don't agree with that. They pick and choose based on their own moral imperatives.

187
00:21:42,885 --> 00:21:48,805
And if you really want to be very lenient, then criminals are basically just doing exactly this.

188
00:21:48,805 --> 00:21:52,245
So the line kind of can blur in some cases.

189
00:21:52,965 --> 00:21:55,124
But yeah, people want to be ungovernable.

190
00:21:55,124 --> 00:22:08,805
And that is the part where I have some doubt about, because you can absolutely imagine that if Bitcoin keeps valuing and, you know, the cost to create a new altcoin or to clone an altcoin is basically zero.

191
00:22:09,764 --> 00:22:15,365
And the potential upside to sell your stuff when you get it early and cheap is huge.

192
00:22:15,365 --> 00:22:27,524
And there is an entire industry built on this that tries to, you know, hype up obscure new shitcoins and just dump them and move on and create the next.

193
00:22:28,164 --> 00:22:31,285
So people will eventually grow tired of this.

194
00:22:31,445 --> 00:22:45,205
And we can foresee that as a lot of Bitcoin maximalists have been created by this simple phenomenon that, you know, holding altcoins is just very, very drug prone experience.

195
00:22:46,085 --> 00:22:59,285
And we can foresee that people would prefer, you know, holding one thing from one monetary layer that actually keeps appreciating.

196
00:23:00,244 --> 00:23:04,884
And they would just stop this experimentation.

197
00:23:04,884 --> 00:23:12,404
There is this line of reasoning that I think most sidechain advocates follow, that this makes sense.

198
00:23:13,044 --> 00:23:26,645
But the ungovernable part is actually like that's a counterforce, I think, because when you put everything, you know, when you put everything on one horse and that horse gets its leg broken,

199
00:23:27,365 --> 00:23:29,365
then you all lose.

200
00:23:29,365 --> 00:23:42,964
And so basically, a lot of people, I think, in Monero, the way they talk about Bitcoin and what Bitcoin is doing and where it's heading and stuff like that,

201
00:23:43,764 --> 00:23:53,925
it tells me that they deeply mistrust how, you know, how ungovernable Bitcoin will be in the future.

202
00:23:54,005 --> 00:23:58,005
So they simply don't agree with that Bitcoin will be ungovernable.

203
00:23:58,005 --> 00:24:18,405
And that's why they will be reluctant, you know, to subservient their consensus to Bitcoin, because that basically in their head is just giving up power to the man, to the state, if you like, giving up power and decreasing the ungovernability.

204
00:24:18,805 --> 00:24:26,324
So there is this line that first, I think, Bitcoin needs to prove that it can indeed remain ungovernable.

205
00:24:26,324 --> 00:24:44,965
And only then will a lot of these hardcore people, you know, consider actually using a sidechain instead of, you know, a consensus where they have more independence and more of this magical power of will and imagination,

206
00:24:44,965 --> 00:24:49,604
where no matter how an attacker comes at them, they can just change the rule, right?

207
00:24:49,604 --> 00:24:55,525
So it's almost like a giant monster is coming for you, but you can just wish it away.

208
00:24:56,884 --> 00:25:02,245
This is kind of how these software projects work if the community can reach consensus.

209
00:25:02,245 --> 00:25:06,965
And the larger the community, the larger, the less this works well.

210
00:25:07,685 --> 00:25:22,645
And this is a reason for, you know, that works against this theory that everyone will just immediately prefer a Bitcoin sidechain that does the same technologically, I think.

211
00:25:25,125 --> 00:25:26,724
So, Paul, what do you think about that?

212
00:25:26,724 --> 00:25:38,645
Do you think that something like Drivechain will inevitably be adopted by a coin that has a robust community and then that coin would swallow up all of the others?

213
00:25:39,284 --> 00:25:48,965
Or do you think the social issues that Moon Settler described would inhibit that total victory by one network effect?

214
00:25:48,965 --> 00:26:07,205
Well, I think what he was saying was that people are buying Monero because they rightly perceived in 2016 as partly as a result of the scaling war.

215
00:26:07,525 --> 00:26:17,844
They kind of thought, well, not only is, you know, there's a difference between having everything figured out and being on the path to world domination.

216
00:26:17,844 --> 00:26:25,044
But if there's a significant split internally, then that means that either one side is wrong or perhaps both sides are wrong.

217
00:26:25,685 --> 00:26:30,965
Because there's apparently enough criticism internally of each side to mount this huge split.

218
00:26:31,685 --> 00:26:43,125
And I think that the split is... that triggered people to say, well, you know, if someone ever actually figures this out, we'll come back.

219
00:26:43,125 --> 00:26:45,844
But right now, they have not figured it out.

220
00:26:50,485 --> 00:26:57,525
Yeah, sure. But then the rhetoric actually evolved if you look at, you know, the talking points.

221
00:26:57,525 --> 00:27:08,564
So a lot of the things that they are saying are not just... of course, the baseline criticism is that Bitcoin is too traceable.

222
00:27:08,564 --> 00:27:22,485
And therefore, since Bitcoin is too traceable, it will naturally become permissioned for the end users, even if they can't actually squeeze the miners, if they can't stronger the miners into compliance.

223
00:27:22,724 --> 00:27:27,525
But they actually, on the other hand, are that convinced that that will come.

224
00:27:27,525 --> 00:27:44,645
Like, Bitcoiners are generally pretty confident in that no state will be able to, you know, just whip the miners into compliance and force censorship, black or white listing or whatever,

225
00:27:45,365 --> 00:27:48,564
travel rule enforcement on the miners.

226
00:27:50,085 --> 00:27:55,844
That is a general view in the Bitcoin community that that is just not going to happen.

227
00:27:56,405 --> 00:28:04,164
On the other hand, I'm pretty sure that most of the Monero people are just taking it, you know, as a fact that this will happen.

228
00:28:04,485 --> 00:28:18,245
And they think that their consensus mechanism is actually more robust and more superior against this kind of government overreach or strong arming techniques.

229
00:28:18,245 --> 00:28:31,204
So that's another way to put more concretely that what I was talking about, that they actually want, you know, they actually want to be ungovernable.

230
00:28:31,204 --> 00:28:35,365
And there are more facets to that than just on-chain privacy.

231
00:28:36,245 --> 00:28:46,565
There are actually, it's a multifaceted issue, and they have become very indoctrinated and very practiced in preaching their points.

232
00:28:46,565 --> 00:29:15,365
And basically, I think even if Bitcoin adopted on layer one ring signatures and confidential transactions as an option, even then a lot of these hardcore Monero people would find the excuses not to, you know, abandon their own network and come back to Bitcoin.

233
00:29:15,844 --> 00:29:21,765
But to continue as they have been doing and basically compete with Bitcoin everywhere they can.

234
00:29:22,644 --> 00:29:25,365
That is how I kind of perceive their attitude.

235
00:29:46,325 --> 00:29:49,685
All right. Very well said.

236
00:29:51,204 --> 00:29:52,644
This is Drivechain Twitter Spaces.

237
00:29:52,644 --> 00:30:15,925
We meet every Monday and Friday to talk about how sidechains can revolutionize innovation on Bitcoin, bringing all of the technology of altcoins to Bitcoin sidechains, potentially eliminating all of the enthusiasm that exists for altcoins, bringing their users economic activity to Bitcoin instead, strengthening Bitcoin.

238
00:30:23,604 --> 00:30:37,524
Yeah, one more thing I would like to mention, I don't know, did we talk about, you know, a little bit about ARK and the limitations last time?

239
00:30:37,524 --> 00:30:39,044
I don't remember.

240
00:30:39,044 --> 00:30:40,084
Yeah, we did.

241
00:30:40,084 --> 00:30:46,964
A lot of you in particular are interested in the dust limit for stuff coming back.

242
00:30:47,925 --> 00:30:54,325
I was wondering if anyone would ever calculate the exact size of the ARK redemption transaction in bytes.

243
00:30:54,325 --> 00:31:14,325
That's certainly something that people want to know to see what multiple that is of a normal transaction, which is if a normal fee rate is $5, then how much does it cost to, you know, like in the uncooperative clothes, uncooperative clothes.

244
00:31:14,404 --> 00:31:18,325
We should have started a clothing line that makes shirts and hats, uncooperative clothes.

245
00:31:21,445 --> 00:31:29,125
So I just saw a lot of people recently, you know, having the doubts expressed along these lines.

246
00:31:29,125 --> 00:31:33,765
So so mainly the liquidity criticism was very loud.

247
00:31:33,765 --> 00:31:41,524
So people were trying to figure out how much liquidity is going to have to be available in access for the service provider.

248
00:31:41,524 --> 00:31:44,485
That was something that people ran away with.

249
00:31:44,485 --> 00:32:01,044
And the other stuff was this, how can you actually say that it is non-custodial when you may not be able to economically enforce your property rights on chain because you are below the dust limit.

250
00:32:01,604 --> 00:32:06,805
So everyone has a different idea about how much Bitcoin on-chain fees will be.

251
00:32:07,844 --> 00:32:14,164
Roughly, we have now about 10 million active Bitcoiners, I believe, at tops.

252
00:32:14,164 --> 00:32:16,164
I don't know how much the exact amount is.

253
00:32:16,805 --> 00:32:24,164
Somewhere probably between 5 and 10 million people who actually hold UTXOs and do lightning stuff.

254
00:32:26,164 --> 00:32:29,604
And most of that is, you know, inert and core storage.

255
00:32:30,565 --> 00:32:34,084
And with this, we have the blocks absolutely full.

256
00:32:34,805 --> 00:32:36,404
Huge backlog is present.

257
00:32:37,524 --> 00:32:48,084
So in a future where hundreds of millions of people want to have access to the Bitcoin network and want to have self-custody,

258
00:32:48,084 --> 00:32:53,365
I don't think we can talk about $5 fees for transactions or $50.

259
00:32:53,365 --> 00:32:55,685
That just doesn't seem realistic to me.

260
00:32:56,325 --> 00:33:08,404
I'm thinking more along the lines of thousands of dollars for a transaction on-chain or maybe tens of thousands if Bitcoin really gets adopted and appreciates in the future.

261
00:33:09,284 --> 00:33:18,084
So this whole thing about, you know, having to, not only you are splitting up.

262
00:33:18,084 --> 00:33:27,044
So let's say you hold $50,000 on Bitcoin and the on-chain fees are just $5,000, $10,000 on average.

263
00:33:27,844 --> 00:33:34,005
And you are actually splitting up that $50,000 to like 10 virtual UTXOs.

264
00:33:34,005 --> 00:33:40,885
And each of them takes multiple transactions to push on-chain, like let's say three on average.

265
00:33:41,844 --> 00:33:47,445
So when you are in a situation like that, you are just going to burn all your money trying to do that.

266
00:33:47,445 --> 00:33:49,685
That is pretty obvious to me.

267
00:33:51,685 --> 00:33:57,925
And that is why I think we are not completely done yet figuring this thing out.

268
00:33:57,925 --> 00:34:05,765
Of course, I can't actually predict what fees people will pay, how much demand will be there for the Bitcoin box space.

269
00:34:06,485 --> 00:34:30,964
We can only speculate on, if someone is a bullish Bitcoin or a Bitcoin maximalist, then he probably imagines that Bitcoin is going to gain prestige and going to gain dominance and going to gain demand for the block space and grow the user base.

270
00:34:31,604 --> 00:34:39,044
And I think we are already pushing the limits of what Bitcoin can actually do, how many people Bitcoin can house.

271
00:34:39,044 --> 00:34:45,204
So we are probably at peak self-sovereign adoption if nothing changes.

272
00:34:46,565 --> 00:34:59,365
And this is where sidechains need to be part of the discussion because they kind of give you the ability to arbitrarily expand the available block space.

273
00:34:59,365 --> 00:35:04,164
But also without increasing the global burden for everyone.

274
00:35:04,164 --> 00:35:14,164
And this partitioning effect is a huge thing and can totally change the game as we know it currently.

275
00:35:18,565 --> 00:35:22,964
My personal view is that the fees on layer one will actually be low.

276
00:35:24,404 --> 00:35:28,724
The average fee won't be low because there will be these BIP301 accounting transactions.

277
00:35:28,805 --> 00:35:38,164
There will be like 10 or 12 of those that pay enormous fee, so the average will be high, but almost no one will pay the average.

278
00:35:38,164 --> 00:35:46,005
The median fee will be low because I just don't see people being willing to actually pay a high fee.

279
00:35:46,005 --> 00:35:49,765
When the fees go up, people complain and they try to batch or they try to do whatever.

280
00:35:49,765 --> 00:35:58,005
They'll try to wriggle out of the fee, including by going custodial, which is like the bar tab batching type idea.

281
00:35:58,885 --> 00:36:11,044
But I do think that still the problem of high fees is relevant to ARK because there can be a kind of bank run where everything's operating normally and no one is doing the uncooperative close.

282
00:36:11,844 --> 00:36:17,284
And then a couple people do it and this causes a congestion to increase.

283
00:36:18,565 --> 00:36:24,325
And then there's a problem because you have to do it within four weeks, right?

284
00:36:24,404 --> 00:36:28,964
So some people think, well, just to be safe, I'll close.

285
00:36:30,245 --> 00:36:33,685
And then when you do that, the fees go up even more.

286
00:36:33,685 --> 00:36:36,565
And then more stuff is near the dust limit.

287
00:36:36,565 --> 00:36:42,885
So people say it can trigger this big cascade of people trying to settle.

288
00:36:43,925 --> 00:36:53,044
And of course, lightning can make it all worse because as we discussed, when nodes disagree on the fee rate on lightning, then they will force close.

289
00:36:53,044 --> 00:36:55,125
So that can add to the chaos.

290
00:36:55,925 --> 00:37:03,765
And ARK has this special property that is allergic to malleability, transaction ID malleability.

291
00:37:03,765 --> 00:37:06,005
It really depends on not being malleable.

292
00:37:06,005 --> 00:37:15,045
That means basically in layman terms that you cannot fee bump these ARK settlement transaction tree stuff.

293
00:37:15,045 --> 00:37:17,365
So you can't fee bump the connectors.

294
00:37:17,365 --> 00:37:21,604
You can't fee bump the VTX.

295
00:37:21,604 --> 00:37:24,964
So as you try to push them on chain.

296
00:37:26,084 --> 00:37:31,285
And you can't fee bump how you want to continue from that.

297
00:37:31,285 --> 00:37:35,444
Maybe if you have something more complex done with the ASP.

298
00:37:36,165 --> 00:37:42,165
So either the ASP locks in a lot in advance, tries to guess what is the fee rate going to be,

299
00:37:42,165 --> 00:37:45,444
like multiplies that with two and locks that in two.

300
00:37:45,525 --> 00:37:55,285
But then he can seriously get hurt if someone is, as you said, for fun or whatever reason just unrolling these transactions that will cost a lot.

301
00:37:55,924 --> 00:38:05,204
So ideally, you would want the person that is pushing these transactions on chain to pay the fee for it because you want to keep people cooperating.

302
00:38:05,204 --> 00:38:10,165
But in case of ARK, because of this four week sweep, it's not so clear cut.

303
00:38:10,165 --> 00:38:18,165
Because we don't want a situation where anyone can just cause the other harm without him being harmed.

304
00:38:18,165 --> 00:38:22,165
We want everyone to get hurt when cooperation stops.

305
00:38:22,165 --> 00:38:30,324
But it's very hard to do it well in advance, lock these things in weeks in advance when you can't predict the fee rate.

306
00:38:30,885 --> 00:38:37,765
So that seems to be a key thing to ARK, to fine tune it and to make it work optimally,

307
00:38:38,485 --> 00:38:46,724
even in the best assumptions and circumstances, is to have a good estimate what the fee rate the next day will be,

308
00:38:46,724 --> 00:38:49,765
and the next week and two weeks after.

309
00:38:49,765 --> 00:38:53,604
If you can't do that, there will be a lot of problems probably.

310
00:38:54,324 --> 00:38:58,485
With the low value VTXs, the high value VTXs will probably be fine.

311
00:38:59,204 --> 00:39:02,564
Medium Satoshi VTXs hopefully will be completely fine.

312
00:39:07,365 --> 00:39:17,444
Paul, is the Thunder scaling sidechain in any way a fundamental necessity for the survival for Bitcoin more than other kinds of sidechains?

313
00:39:17,444 --> 00:39:28,005
Or would you say that Thunder is just one example of the many ways that Bitcoin mainchain doesn't offer all of the features that some people would want,

314
00:39:28,005 --> 00:39:31,444
and therefore we need a sidechain to meet those people's demands?

315
00:39:34,324 --> 00:39:40,084
Well, I think that actually it is, because I think at the end of the day, the system...

316
00:39:41,125 --> 00:39:45,525
Like, what people are doing today with Bitcoin is they're saying something like...

317
00:39:47,684 --> 00:39:56,005
It's like we're designing a radio, and they're saying right now the radio can only do 8 kilobytes per second.

318
00:39:57,749 --> 00:40:10,749
Or something like that. And they're saying, well, we're going to keep improving it, and we'll get it up to 200 kilobytes a second, and then we'll get it up to 205 kilobytes.

319
00:40:11,749 --> 00:40:20,749
But I kind of don't see it that way. I think we already have Venmo, we already have WeChat Pay, we already have all this stuff, Zelle, whatever, PayPal.

320
00:40:21,749 --> 00:40:26,749
So the network effects of money are so strong that once something wins, it'll be very hard to dislodge it.

321
00:40:28,749 --> 00:40:36,749
There'll be people who talk about the immaculate conception of Bitcoin, but for whatever wins, it'll be impossible to dislodge, like the QWERTY keyboard.

322
00:40:37,749 --> 00:40:57,749
It just can't be dislodged. So basically, whoever gets to the largest scale first without dying will just win. Everything else will just be pets.com, and we'll be gone.

323
00:40:58,749 --> 00:41:13,749
So I think that the idea of whether or not you can scale to all 8 billion people on the planet Earth is something that we should be a little bit more, I don't know if the word is compromising on or something, but because of the scaling war, people just kind of refuse to be open-minded.

324
00:41:14,749 --> 00:41:21,749
At least concerned, right? So even if you don't want to say compromise, we should be more concerned about this.

325
00:41:22,749 --> 00:41:31,749
And the idea should be more like, we can get 8 billion people with custodial, how do we improve on that?

326
00:41:32,749 --> 00:41:49,749
So it should go the other way. It shouldn't be like the radio gets this far. We should say, okay, right now we can get 8 billion people with custodial, how do we improve on custodial while still keeping 8 billion people in the network?

327
00:41:50,749 --> 00:42:02,749
And so it should go the opposite direction, really. So that's kind of what I think. I think like, okay, when you write to the Bitcoin.dev mailing list, it should be, here's how I get 8 billion people, and then here's what I sacrifice.

328
00:42:03,749 --> 00:42:09,749
And whoever sacrifices the least should win. But it should be flipped, the question, I think.

329
00:42:10,749 --> 00:42:22,749
Yeah, but also, there is some weird psychosis going on in Bitcoin circles, I believe.

330
00:42:22,749 --> 00:42:34,749
So the way that people want to handle future changes, especially consensus forks, is somehow completely deranged.

331
00:42:35,749 --> 00:42:46,749
Somehow, there is a misconception of the risks with changes to Bitcoin Core codebase that involve the consensus.

332
00:42:46,749 --> 00:42:55,749
And people don't understand that those changes get the most eyes on. Those changes are the hardest, the most vetted.

333
00:42:56,749 --> 00:43:05,749
So if anyone wants to slip in some nasty into Bitcoin Core, he will definitely not do a consensus fork. He will definitely not flag it as a consensus fork.

334
00:43:06,749 --> 00:43:10,749
I can't quite hear him now. Oh, he's back. Yes, now we can hear you.

335
00:43:11,749 --> 00:43:12,749
I hear him just fine.

336
00:43:13,749 --> 00:43:14,749
Thank you.

337
00:43:14,749 --> 00:43:20,749
All right, so I think people are too afraid of consensus changes.

338
00:43:21,749 --> 00:43:29,749
And they are very, very comfortable with the 10,000 pull requests that get merged into core every year.

339
00:43:30,749 --> 00:43:35,749
The Bitcoin codebase is getting completely reworked. People are changing almost every...

340
00:43:39,749 --> 00:43:41,749
All right, please continue.

341
00:43:45,749 --> 00:44:01,749
So I see this weird detachment or this weird psychosis where people are very afraid to change a single line of consensus code.

342
00:44:01,749 --> 00:44:14,749
Even though, like I said, that will almost surely get all the core developers to really seriously look at that code and discuss it to death and run tests on it endlessly.

343
00:44:15,749 --> 00:44:23,749
And all the additional code changes that very well could actually result in forks because that's just the nature of Bitcoin.

344
00:44:24,749 --> 00:44:31,749
Replacing the database under Bitcoin can result in a hard forecast or anything like that.

345
00:44:32,749 --> 00:44:38,749
And so a lot of things get changed in Bitcoin. A lot of the code gets changed, but nobody cares about that.

346
00:44:39,749 --> 00:44:43,749
Everybody only cares about the stuff that people call forks.

347
00:44:44,749 --> 00:45:00,749
And there seems to be some notion that something sinister could be slipped into Bitcoin with a fork and we should be very vigilant and fight against any such change.

348
00:45:01,749 --> 00:45:07,749
And I actually don't understand where these people are getting these weird ideas. This is completely deranged.

349
00:45:07,749 --> 00:45:17,749
And we have this situation and we are a bit stuck because as Bitcoin is right now, it's completely unscalable.

350
00:45:18,749 --> 00:45:24,749
So this is a fact. So Bitcoin is completely unscalable as it is. It can only be scaled through custody.

351
00:45:25,749 --> 00:45:34,749
And it's almost certainly guaranteeable that if you scale through custody, then this 21 million Bitcoin limit is just not going to hold in the future.

352
00:45:34,749 --> 00:45:43,749
I think history just proves that the entire world will be hungry for Bitcoin and the liquidity and they will just find ways to work around it.

353
00:45:44,749 --> 00:45:57,749
And if people can't insist on final settlement because it just doesn't work, then there is just no way in hell that we can hang on to that limit.

354
00:45:58,749 --> 00:46:07,749
I didn't quite follow that last point about there being a relationship, in your view, between the supply of Bitcoin and its scalability.

355
00:46:08,749 --> 00:46:17,749
Isn't the argument in favor of tail issuance mainly focused on security budget, low fees, not on scaling?

356
00:46:17,749 --> 00:46:27,749
I think this has nothing to do with tail emission or the security budget. Think about it this way.

357
00:46:28,749 --> 00:46:41,749
If everyone in the world, all the 8 billion people are basically having a custodial relationship with someone and never seeing or operating with on-chain Bitcoin ever,

358
00:46:41,749 --> 00:46:48,749
not even with Lightning directly, they are all having custodial wallets and only the banks use Lightning to settle.

359
00:46:49,749 --> 00:46:51,749
Banks and financial institutions settle on Lightning with each other.

360
00:46:52,749 --> 00:46:56,749
In a world like that, all the Bitcoin is basically just paper Bitcoin.

361
00:46:57,749 --> 00:47:08,749
And there is nothing stopping anyone from issuing the same Bitcoin to hundreds of people and lending out their real Bitcoin for years or whatever.

362
00:47:08,749 --> 00:47:16,749
And basically the same thing that happened to gold, the same system can easily be replicated on Bitcoin.

363
00:47:17,749 --> 00:47:24,749
And people have been talking about this, by the way, so I don't know how long, but this discussion was very hot since 2015 at least.

364
00:47:25,749 --> 00:47:30,749
And it was a very important aspect, I think, of the Skizm and the Bcash fork.

365
00:47:31,749 --> 00:47:40,749
That many people were convinced that if we do not scale Bitcoin on the main chain, at least to some degree,

366
00:47:41,749 --> 00:47:46,749
then the end result will inevitably be a huge fractional reserve scam.

367
00:47:47,749 --> 00:47:52,749
And we are just going to replicate the previous failings in history with it.

368
00:47:52,749 --> 00:47:54,749
And I find this argument very compelling.

369
00:47:55,749 --> 00:47:59,749
I don't know any reason why this shouldn't happen, because expense is expense.

370
00:48:00,749 --> 00:48:04,749
People are saying gold is expensive to settle and hard to move.

371
00:48:05,749 --> 00:48:08,749
Yeah, if Bitcoin is expensive to settle and hard to move, it's the same thing.

372
00:48:11,749 --> 00:48:18,749
Yeah, he's talking about, Henry, what you would use as your Bitcoin wallet in the future.

373
00:48:19,749 --> 00:48:22,749
It wouldn't be a full node, it would just be pointing to the custodial thing.

374
00:48:23,749 --> 00:48:27,749
So what if they updated it and they just said, you don't own any Bitcoin anymore.

375
00:48:28,749 --> 00:48:31,749
Or you own twice as much. They'd just make it up.

376
00:48:32,749 --> 00:48:35,749
And there would be no one in the world who could just say…

377
00:48:36,749 --> 00:48:39,749
The people who run a Bitcoin full node would be able to say, oh, that's not true.

378
00:48:40,749 --> 00:48:44,749
But actually those people would be a tiny minority and no one would care about them at all.

379
00:48:45,749 --> 00:48:51,749
I mean, the people that run the Bitcoin nodes would have no idea how much Bitcoin is credited to people worldwide.

380
00:48:52,749 --> 00:48:54,749
They would have no idea. They could have suspicions about it.

381
00:48:55,749 --> 00:49:01,749
Everyone could have a general feeling about it, that there is just too much Bitcoin denominated liquidity available in the world.

382
00:49:02,749 --> 00:49:05,749
But no one could actually verify anything.

383
00:49:06,749 --> 00:49:14,749
Any financial institution can just make numbers up about their reserves or whatever, or not even tell anyone.

384
00:49:15,749 --> 00:49:18,749
I mean, I don't know what cash reserves my bank holds.

385
00:49:19,749 --> 00:49:21,749
I don't know. If I ask them, they won't tell me.

386
00:49:22,749 --> 00:49:24,749
I have no idea what is their financial situation.

387
00:49:25,749 --> 00:49:29,749
Probably they report balance sheets to some state authority or something.

388
00:49:30,749 --> 00:49:32,749
But I have no clue what their situation is.

389
00:49:33,749 --> 00:49:39,749
Yeah, it's interesting that in the scaling war there was actually one of the disputed points was…

390
00:49:40,749 --> 00:49:46,749
One thing that people both hit on was they said, how can we maximize the quantity of full nodes?

391
00:49:47,749 --> 00:49:56,749
And the small block side said, if the node is too expensive, it's already really hard to do initial block download.

392
00:49:57,749 --> 00:49:59,749
Running a node is really inconvenient.

393
00:49:59,749 --> 00:50:01,749
We don't want the blocks to get bigger.

394
00:50:02,749 --> 00:50:05,749
Every week there's a thousand new blocks.

395
00:50:06,749 --> 00:50:14,749
So even if the block size is only 8 megabytes, that's 8 gigabytes every week piling on.

396
00:50:15,749 --> 00:50:17,749
You have to stop the bleeding, so to speak.

397
00:50:18,749 --> 00:50:20,749
But then the other side, I remember they're on the large block side.

398
00:50:21,749 --> 00:50:23,749
They said, well listen, Bitcoin right now is really small.

399
00:50:24,749 --> 00:50:25,749
We only have a few people in Bitcoin.

400
00:50:26,749 --> 00:50:33,749
We need to go to the whole world and then maybe a much smaller percentage of people will be running nodes.

401
00:50:34,749 --> 00:50:36,749
But we'll be big.

402
00:50:37,749 --> 00:50:40,749
We'll be a big hit and then lots of people will be involved.

403
00:50:41,749 --> 00:50:43,749
They'll have all their money in it and they will run nodes.

404
00:50:44,749 --> 00:50:47,749
And then the quantity of nodes will actually go up if the block size is greater.

405
00:50:48,749 --> 00:50:53,749
So it's an intriguing case where both sides actually agreed on a metric.

406
00:50:53,749 --> 00:50:58,749
There was so much disagreement, but it's just interesting that in this case there was kind of an agreement.

407
00:50:59,749 --> 00:51:04,749
Where there was like, we both actually want this number to be its highest value.

408
00:51:05,749 --> 00:51:08,749
But then it was kind of like, yeah, who knows?

409
00:51:09,749 --> 00:51:10,749
It would have been interesting.

410
00:51:11,749 --> 00:51:18,749
So what do you think about these recent developments on U3XO and 0SYNC4?

411
00:51:19,749 --> 00:51:21,749
Have you been keeping tabs on that?

412
00:51:22,749 --> 00:51:26,749
Well, yeah, so people really like this ZK-SNARK stuff.

413
00:51:27,749 --> 00:51:28,749
And I have always hated it, honestly.

414
00:51:29,749 --> 00:51:30,749
I've been suspicious of it.

415
00:51:31,749 --> 00:51:34,749
Partly because it was clear that everyone is just BSing and no one actually knows how it works.

416
00:51:35,749 --> 00:51:39,749
But until recently, now I think recently, the last five years has changed a lot.

417
00:51:40,749 --> 00:51:45,749
So it went from being completely untenable to me to being kind of okay.

418
00:51:46,749 --> 00:51:51,749
I actually, ZK proofs do not solve data availability in the slightest.

419
00:51:52,749 --> 00:51:56,749
And so I wrote this thing about fraud proofs that I think is way better.

420
00:51:57,749 --> 00:52:00,749
Because fraud proofs actually can solve data availability.

421
00:52:01,749 --> 00:52:06,749
You can create a type of payment in like a lightning channel or in some other thing.

422
00:52:07,749 --> 00:52:11,749
Some kind of non-thing that is not involving the full node.

423
00:52:12,749 --> 00:52:16,749
Yeah, it triggers if some part of the block is empty.

424
00:52:17,749 --> 00:52:18,749
And then you can see what the market price of that is.

425
00:52:19,749 --> 00:52:22,749
And then you'll know if the market price of that is very low, like 0%.

426
00:52:23,749 --> 00:52:25,749
Then you know that the block is there somewhere.

427
00:52:26,749 --> 00:52:32,749
Yeah, so 0SYNC, the interesting thing about 0SYNC is it does not directly affect consensus.

428
00:52:33,749 --> 00:52:36,749
It is not a ZK-SNARK or anything.

429
00:52:37,749 --> 00:52:46,749
It just, they are basically trying to zero-knowledge prove the computational correctness of verifying Bitcoin,

430
00:52:47,749 --> 00:52:49,749
you know, validating the entire blockchain.

431
00:52:50,749 --> 00:52:54,749
And they figured out ways how this can be composed, how this can be parallelized,

432
00:52:55,749 --> 00:53:01,749
how individuals, you know, chipping in their hash power voluntarily, node runners,

433
00:53:01,749 --> 00:53:06,749
how could they just validate parts of blocks and this can be aggregated,

434
00:53:07,749 --> 00:53:10,749
because the aggregation itself is a computation, you know.

435
00:53:11,749 --> 00:53:20,749
So they figured out how you can do trees that are, you know, zero-knowledge provable sort of,

436
00:53:21,749 --> 00:53:23,749
and how you can aggregate zero-knowledge proofs.

437
00:53:24,749 --> 00:53:28,749
And this means, this kind of means that if you accept that this thing works,

438
00:53:28,749 --> 00:53:36,749
this ZK magic thing works, at least with reasonable assurances or within reasonable assurances,

439
00:53:37,749 --> 00:53:45,749
then basically the whole argument about Bitcoin blockchain bloat over long term just becomes completely mute,

440
00:53:46,749 --> 00:53:55,749
because you can basically sync up in the future where these proofs are available

441
00:53:55,749 --> 00:54:00,749
and then you can verify them on your client and it can sync up to the chain state

442
00:54:01,749 --> 00:54:03,749
without even downloading the entire chain state.

443
00:54:04,749 --> 00:54:12,749
You would know that this Merkle forest root is actually belonging to a valid chain state for that block height.

444
00:54:13,749 --> 00:54:15,749
It would know that the proof of work is correct.

445
00:54:16,749 --> 00:54:20,749
It would know everything, every calculation has been done in theory.

446
00:54:21,749 --> 00:54:22,749
I don't know if this is really working.

447
00:54:22,749 --> 00:54:25,749
By the way, I'm just assuming that they are not bullshitting us.

448
00:54:26,749 --> 00:54:32,749
So you would be able to verify this eight kilobyte or something zero-knowledge proof

449
00:54:33,749 --> 00:54:40,749
and then you could just assume a UTXO forest or some other UTXO aggregation.

450
00:54:41,749 --> 00:54:46,749
Some people said that UTXO is not perfect because you cannot prove,

451
00:54:46,749 --> 00:54:56,749
you cannot prove that when someone tells you that some UTXOs that you are interested in are included,

452
00:54:57,749 --> 00:54:59,749
they can't prove that the opposite.

453
00:55:00,749 --> 00:55:05,749
So they can't prove you that these are only the UTXOs that you own and there are no others.

454
00:55:06,749 --> 00:55:10,749
So I don't know what is the name of that, but the point is there will be some structure

455
00:55:11,749 --> 00:55:15,749
and you will only need to hold the roots and you will be able to run a full node from that

456
00:55:16,749 --> 00:55:22,749
and you will be able to come online every few weeks and just get started with a new zero-knowledge proof

457
00:55:23,749 --> 00:55:28,749
that some people prepared and basically the whole idea that people will keep terabytes or exabytes

458
00:55:29,749 --> 00:55:34,749
or I don't know how much data on their full node, it just seems silly, like implausible.

459
00:55:35,749 --> 00:55:38,749
I think initial block download will be gone in like a decade.

460
00:55:39,749 --> 00:55:44,749
So like 99.9% of the people interacting with Bitcoin will not do IBD.

461
00:55:44,749 --> 00:55:46,749
I am pretty convinced of this.

462
00:55:47,749 --> 00:55:53,749
And this makes the entire argument in the block size world like insanely, insanely silly to me.

463
00:55:54,749 --> 00:56:02,749
Well, it's interesting that you say that because that type of argument is exactly why I think the ZK proof stuff is a terrible idea.

464
00:56:03,749 --> 00:56:06,749
I mean because, but let me kind of unpack it a little bit.

465
00:56:07,749 --> 00:56:09,749
Because what I have to say is actually kind of nuanced.

466
00:56:10,749 --> 00:56:13,749
But the first thing to point out is we already have that basically.

467
00:56:14,749 --> 00:56:16,749
It's called SPV. Now it doesn't necessarily work.

468
00:56:17,749 --> 00:56:25,749
But there's like, what would you say like, there's a saying that goes when you have a hammer,

469
00:56:26,749 --> 00:56:28,749
when you're holding a hammer, every problem looks like a nail.

470
00:56:29,749 --> 00:56:33,749
You know what I mean? And it's like you're holding a hammer and you have these ZK proofs

471
00:56:34,749 --> 00:56:35,749
and they think, oh, what can we use these for?

472
00:56:36,749 --> 00:56:37,749
Okay, we'll prove the chain state.

473
00:56:38,749 --> 00:56:40,749
But there's never really been a real like dispute.

474
00:56:40,749 --> 00:56:44,749
You know, like there's never really an actual dispute like about.

475
00:56:45,749 --> 00:56:49,749
Now, I'm not saying that we should just, you know, we should just give up or whatever.

476
00:56:50,749 --> 00:56:55,749
Like, but what I'm saying is SPV already can do like in 2009, we already only get the headers.

477
00:56:56,749 --> 00:57:00,749
SPV does not actually prove correctness.

478
00:57:01,749 --> 00:57:09,749
So SPV only proves that a certain amount of work was put into the creation of a Merkle tree

479
00:57:10,749 --> 00:57:16,749
and in that Merkle tree, a transaction that you deem valid and to you is included.

480
00:57:17,749 --> 00:57:19,749
So that is the only thing it can actually prove.

481
00:57:20,749 --> 00:57:23,749
It cannot prove that there was not more Bitcoin minted in the Coinbase

482
00:57:24,749 --> 00:57:29,749
than what you would, you know, find acceptable somewhere along the line or some other.

483
00:57:30,749 --> 00:57:31,749
There was not a malicious spend.

484
00:57:32,749 --> 00:57:33,749
It can prove none of these things.

485
00:57:34,749 --> 00:57:38,749
But ZK proves in theory, if you can really like ZK prove these computations

486
00:57:39,749 --> 00:57:42,749
and the aggregations are also reasonable.

487
00:57:43,749 --> 00:57:44,749
But why do I say that anyway?

488
00:57:45,749 --> 00:57:48,749
Because imagine what would it be like if you broke a rule?

489
00:57:51,749 --> 00:57:52,749
You know what I mean?

490
00:57:53,749 --> 00:57:54,749
Like it doesn't prove that all the rules have been followed.

491
00:57:55,749 --> 00:57:58,749
But imagine what if you broke a rule in the world where we only have SPV?

492
00:57:59,749 --> 00:58:02,749
Well, it has to be the case that like the entire network is fooled.

493
00:58:03,749 --> 00:58:04,749
Yeah.

494
00:58:05,749 --> 00:58:06,749
Right?

495
00:58:07,749 --> 00:58:14,749
I mean, it has to be that the majority of the hash power at least is colluding with that

496
00:58:15,749 --> 00:58:22,749
or has been fooled because SPV really relies on that.

497
00:58:22,749 --> 00:58:31,749
The majority of the hash power, the heaviest chain is not incentivized in fraud.

498
00:58:32,749 --> 00:58:33,749
They are somehow kept honest.

499
00:58:34,749 --> 00:58:40,749
So when someone with some insignificant amount like $10 that he receives in Bitcoin

500
00:58:41,749 --> 00:58:47,749
would use SPV, he relies on that, you know, Coinbase and Binance and Michael Saylor

501
00:58:47,749 --> 00:58:53,749
and every big author is running their full nodes and they are not taking any bullshit.

502
00:58:54,749 --> 00:58:55,749
They are enforcing the rules.

503
00:58:56,749 --> 00:59:07,749
What ZeroSync does is it says, okay, we remove the risk that the miners can collude

504
00:59:08,749 --> 00:59:12,749
with everyone against full nodes.

505
00:59:13,749 --> 00:59:17,749
Now, that's exactly what the fraud proofs thing that I described does.

506
00:59:18,749 --> 00:59:19,749
Yeah.

507
00:59:21,749 --> 00:59:24,749
Fraud proofs, again, are like, to me, very simple.

508
00:59:25,749 --> 00:59:29,749
Whereas ZK-SNARK thing does not work with data availability

509
00:59:30,749 --> 00:59:33,749
and it uses all this complicated stuff that no one can understand.

510
00:59:34,749 --> 00:59:36,749
Yeah, it's interesting.

511
00:59:37,749 --> 00:59:44,749
I think there could be like a sensible way to use this.

512
00:59:45,749 --> 00:59:47,749
I believe that we can have.

513
00:59:49,896 --> 00:59:54,296
Data availability, roll up data availability does not need to be forever.

514
00:59:54,296 --> 01:00:00,696
It's not like the actual ledger updates, you know, it doesn't have to be available forever.

515
01:00:01,336 --> 01:00:04,696
Even that may not be need to be available forever.

516
01:00:04,696 --> 01:00:06,455
But let's say we want to keep.

517
01:00:06,455 --> 01:00:07,896
But you understand what I'm saying.

518
01:00:07,896 --> 01:00:13,656
It's already, in 2010, it was already possible to mostly do what you describe as this thing

519
01:00:14,455 --> 01:00:17,576
that would end like the block size debate and everything

520
01:00:18,056 --> 01:00:20,455
where you just have your 80 byte headers.

521
01:00:20,455 --> 01:00:24,936
You have the proof of work chain, which is 4.4 megabytes per year, which is nothing.

522
01:00:26,456 --> 01:00:28,376
You get the whole, you get completely to the end.

523
01:00:29,815 --> 01:00:32,776
You have a Merkle tree that proves that you're included in the thing,

524
01:00:32,776 --> 01:00:36,296
and then you have UTXO commitments of whatever kind of which

525
01:00:37,736 --> 01:00:41,815
one type of UTXO commitment, which I think is probably the best one,

526
01:00:41,815 --> 01:00:43,815
because I think, you know, Ted is probably a genius.

527
01:00:44,456 --> 01:00:45,335
I agree.

528
01:00:45,335 --> 01:00:51,815
If you want to go with UTXO commitments, I would say that we commit to a UTXO route

529
01:00:51,815 --> 01:00:58,696
because it's just more useful, more options are available to people and more flexibility

530
01:00:58,696 --> 01:01:03,495
how it is used and what is getting verified and deferred, verified and whatever.

531
01:01:04,056 --> 01:01:07,095
So, yeah, a lot of people say that

532
01:01:07,976 --> 01:01:14,455
zero-sync proving these trees is actually better than commitments,

533
01:01:14,455 --> 01:01:15,896
consensus-enforced commitments.

534
01:01:15,896 --> 01:01:19,815
There is one problem with, you know, consensus-enforced commitments,

535
01:01:20,616 --> 01:01:24,135
and that is that it is computationally intensive.

536
01:01:25,095 --> 01:01:31,896
So, let's say if you want to, if you want, if you have to put into a valid block,

537
01:01:31,976 --> 01:01:44,696
into a valid Bitcoin block, you have to put the last UTXO, last change state in this UTXO,

538
01:01:44,696 --> 01:01:50,855
you know, tree format, the hash commitment to that for it to be valid.

539
01:01:51,415 --> 01:01:52,696
That will be very useful.

540
01:01:52,696 --> 01:01:54,936
That will be very useful to end users.

541
01:01:54,936 --> 01:01:59,655
But what it will do to miners is they would have to spend a lot of time

542
01:01:59,655 --> 01:02:03,175
when they receive a block to actually, you know,

543
01:02:03,175 --> 01:02:10,935
create the new updated state of the UTXO tree and get the new route commitment.

544
01:02:11,575 --> 01:02:15,735
And they can't really just start working on the block until they do that.

545
01:02:16,696 --> 01:02:24,696
So, you introduce something here where a lot of problems can come

546
01:02:24,696 --> 01:02:29,095
with, you know, the bloating of the UTXO set.

547
01:02:29,095 --> 01:02:32,696
In the future, if someone really starts to spam the UTXO set,

548
01:02:32,696 --> 01:02:37,175
and we are starting to keep some of it not in memory on statistical terms,

549
01:02:37,175 --> 01:02:43,015
and this update can take a lot of time if someone strategically picks

550
01:02:43,015 --> 01:02:46,216
inclusion of new transactions and stuff like that.

551
01:02:46,216 --> 01:02:50,616
So, if it involves IOP operations and not just in memory,

552
01:02:50,616 --> 01:02:53,416
then especially it's going to be expensive.

553
01:02:53,416 --> 01:02:57,575
And you can actually, maybe in extreme circumstances,

554
01:02:57,575 --> 01:03:03,015
deny miners' ability to work on a new block for minutes after receiving a block.

555
01:03:03,015 --> 01:03:08,295
And that gives the one that assembled that block like a huge advantage,

556
01:03:08,295 --> 01:03:10,856
actually, because he can immediately start working on it.

557
01:03:10,856 --> 01:03:15,655
He knows exactly what he has done, even before he found, you know, his work.

558
01:03:15,655 --> 01:03:20,056
And this whole thing is not so clear-cut in my mind,

559
01:03:20,216 --> 01:03:29,416
how we could do this, you know, without screwing up the way Bitcoin mining works.

560
01:03:36,535 --> 01:03:42,455
So, again, the fraud-proof idea that I can link...

561
01:03:42,455 --> 01:03:43,735
I can post a link if you like.

562
01:03:43,735 --> 01:03:47,416
I just replied to, because I don't know if I can...

563
01:03:47,815 --> 01:03:55,575
I just replied to Robin Linus, who is doing a ZKP sidechains now, fake shirt.

564
01:03:56,375 --> 01:03:58,375
I don't know how to send it into the thing.

565
01:03:58,375 --> 01:03:59,896
I can copy it in here.

566
01:04:00,535 --> 01:04:02,056
I don't know if I can move it in.

567
01:04:02,056 --> 01:04:03,095
Can I do the thing?

568
01:04:04,295 --> 01:04:08,295
I think you have to press share on the tweet

569
01:04:08,295 --> 01:04:11,096
and then select that you share it with this piece, something like that.

570
01:04:11,096 --> 01:04:14,536
Yeah, you want to put a tweet in the nest, you go to the tweet,

571
01:04:15,496 --> 01:04:19,896
and at the bottom right of the tweet, you click that arrow that's pointing upwards.

572
01:04:20,936 --> 01:04:26,536
And then from there, you select the very top option, which is the name of this spaces.

573
01:04:28,855 --> 01:04:29,496
I shared it.

574
01:04:30,135 --> 01:04:30,536
Perfect.

575
01:04:33,096 --> 01:04:37,015
And then I replied it to my fraud-proof thing.

576
01:04:37,575 --> 01:04:44,295
But so the fraud-proofs idea is exactly...

577
01:04:44,295 --> 01:04:49,415
To me, it's equal to zero knowledge proofs, except everyone can understand them,

578
01:04:49,975 --> 01:04:52,216
and they could be finished.

579
01:04:52,216 --> 01:04:56,216
They would have been finished in like whatever, 2016, if people really cared.

580
01:04:56,216 --> 01:05:01,015
But to me, people don't really care, because whatever we do in life...

581
01:05:02,855 --> 01:05:04,695
Think about if you were to buy a chicken sandwich.

582
01:05:05,415 --> 01:05:12,376
We don't really live in a world where you check every single thing about the chicken,

583
01:05:13,656 --> 01:05:18,056
you check everything about the sauce, you check everything about the bread,

584
01:05:19,015 --> 01:05:20,616
or else you're poisoned and die.

585
01:05:21,735 --> 01:05:24,216
It's just, you know, I understand how that's better.

586
01:05:24,216 --> 01:05:26,056
If we could audit everything, we should.

587
01:05:26,056 --> 01:05:26,616
I like that.

588
01:05:27,896 --> 01:05:31,255
I would like to be able to know everything about my chicken sandwich before I eat it.

589
01:05:32,216 --> 01:05:36,536
But I think, you know, how practical is it really?

590
01:05:36,536 --> 01:05:41,896
Because whatever thing is invented or theorized,

591
01:05:41,896 --> 01:05:44,776
like just the world, a layperson is not a specialist.

592
01:05:44,776 --> 01:05:47,015
So all the different people who are involved,

593
01:05:47,015 --> 01:05:52,135
consuming or producing this good or shipping it around, it's just this huge project.

594
01:05:52,936 --> 01:06:00,616
And so, basically, this seems to be like putting a whole lot of effort into...

595
01:06:00,616 --> 01:06:03,415
Like, compare the amount of effort put into this thing.

596
01:06:05,415 --> 01:06:08,056
It's just, it seems disproportionate.

597
01:06:08,056 --> 01:06:11,336
So what I'm getting at is, we put a lot of effort into making sure that

598
01:06:12,056 --> 01:06:17,175
miners don't cheat light clients via SPV mode.

599
01:06:17,975 --> 01:06:20,536
But that problem could be solved by just telling those people,

600
01:06:20,616 --> 01:06:23,175
just telling those people, hey, if you're worried about that,

601
01:06:23,175 --> 01:06:25,096
run a full node instead of a light client.

602
01:06:25,735 --> 01:06:28,776
So it's already a completely easy to solve problem.

603
01:06:29,336 --> 01:06:31,336
And if someone is providing you, if you have like a,

604
01:06:31,336 --> 01:06:34,855
with the equivalent of a lightning service provider or like a full node service provider,

605
01:06:35,496 --> 01:06:38,295
if you had that and they did the bad job, you could switch.

606
01:06:38,936 --> 01:06:41,575
You know, there could be like a subscription service.

607
01:06:41,575 --> 01:06:43,735
I'm not actually advocating for any of this.

608
01:06:43,735 --> 01:06:47,175
I'm just talking about how you ask about a thing.

609
01:06:47,735 --> 01:06:51,255
ZK-proof sync, ZK-proof magic, whatever.

610
01:06:51,255 --> 01:06:55,975
And the thing doesn't really improve on the existing world at all,

611
01:06:55,975 --> 01:06:58,695
because the existing world is already kind of shaped like that.

612
01:06:59,255 --> 01:07:02,376
And that thing isn't a real problem compared to like,

613
01:07:02,376 --> 01:07:05,255
how do we get more people using Bitcoin?

614
01:07:05,255 --> 01:07:10,936
How do we get more flexibility with Bitcoin upgrades?

615
01:07:10,936 --> 01:07:15,175
How do we, how do we make Bitcoin more conservative to prevent social attacks?

616
01:07:16,056 --> 01:07:19,496
Like there's a giant long list of things that are all way, way more important

617
01:07:19,496 --> 01:07:22,056
than if there are people cheating SPV mode,

618
01:07:22,056 --> 01:07:24,056
which already has like natural feedback loops.

619
01:07:24,056 --> 01:07:25,496
If people cheat with that, they would.

620
01:07:26,056 --> 01:07:29,816
So that's, this is kind of what bothers me about it is it does seem like

621
01:07:30,695 --> 01:07:34,536
that it's addressing a completely fake problem in my point of view.

622
01:07:34,536 --> 01:07:36,855
In a way that when people,

623
01:07:36,855 --> 01:07:38,936
the regular lay person is not going to be able to understand

624
01:07:38,936 --> 01:07:41,496
what these ZK-proofs do at all.

625
01:07:41,496 --> 01:07:44,936
The way they could at least understand what a hash is or what a signature is,

626
01:07:44,936 --> 01:07:47,816
a regular person would be able to understand that eventually.

627
01:07:50,855 --> 01:07:58,376
So the biggest problem that we still didn't really figure out with the SPV mode, right,

628
01:07:59,175 --> 01:08:00,376
is the privacy issue.

629
01:08:00,936 --> 01:08:07,816
So a lot of Lite clients, Lite wallets are just horrible for privacy.

630
01:08:07,975 --> 01:08:12,376
And even, even, you know, the, ironically,

631
01:08:12,376 --> 01:08:18,295
like the most hardcore parts of the Bitcoin privacy crowd, the Samurai crowd,

632
01:08:19,015 --> 01:08:25,815
if you, if you start a Samurai wallet, right, without, you know, doing anything else,

633
01:08:25,815 --> 01:08:27,495
you just download and start using it.

634
01:08:27,495 --> 01:08:30,615
You're basically giving them your, your ex-pubs.

635
01:08:30,615 --> 01:08:33,255
And, and I'm not even sure.

636
01:08:35,495 --> 01:08:36,856
That's a mistake. I agree.

637
01:08:36,856 --> 01:08:39,976
But I think the, the privacy thing, you know,

638
01:08:39,976 --> 01:08:45,336
you're referring to the fact that a Lite client must ask a full node for UTXOs, right?

639
01:08:45,976 --> 01:08:46,476
Yeah.

640
01:08:47,015 --> 01:08:50,216
But I think that's actually quite solvable.

641
01:08:50,216 --> 01:08:52,536
And in fact, lots of people introduced various things,

642
01:08:52,536 --> 01:08:55,656
remember like Neutrino and then like this little Bloom filter.

643
01:08:55,656 --> 01:08:57,656
And then I think UTXO is part of that too,

644
01:08:57,656 --> 01:09:03,736
because you just, you can set the software up to just ask like many, many decoy things,

645
01:09:03,736 --> 01:09:06,135
you know, just ask like 5,000 at random,

646
01:09:06,135 --> 01:09:07,575
including your real one.

647
01:09:08,296 --> 01:09:10,455
So I think that that is also like a solve.

648
01:09:10,455 --> 01:09:12,776
What we should really do is we should wait.

649
01:09:14,216 --> 01:09:16,375
I am torn because in part,

650
01:09:16,375 --> 01:09:19,656
I think people should just pursue technology for its own sake.

651
01:09:20,296 --> 01:09:24,695
But really, I do think that we should wait for the user to complain

652
01:09:24,695 --> 01:09:26,856
before we solve a problem.

653
01:09:26,856 --> 01:09:27,416
You know what I mean?

654
01:09:27,416 --> 01:09:29,336
So like the ZK thing, it's like, it's not,

655
01:09:30,296 --> 01:09:32,055
that shouldn't really be on people's radar.

656
01:09:32,055 --> 01:09:34,455
Like we have these other problems and then people say,

657
01:09:35,416 --> 01:09:41,336
we can make this towering Tesseract thing of enormous,

658
01:09:42,455 --> 01:09:44,695
like cutting edge technology.

659
01:09:44,695 --> 01:09:45,896
And people are like, what does it do?

660
01:09:45,896 --> 01:09:50,455
And they said, well, you no longer will be scammed on SPV mode.

661
01:09:50,455 --> 01:09:52,615
And it's like, well, that has never happened to anyone ever.

662
01:09:55,656 --> 01:09:56,156
Yeah.

663
01:09:57,336 --> 01:10:01,815
I kind of agree that probably the biggest pain point

664
01:10:01,815 --> 01:10:04,935
that people will start complaining about will be the fees.

665
01:10:05,656 --> 01:10:12,776
And the second is, seems to be this thing that,

666
01:10:13,656 --> 01:10:17,815
you know, people have with running their own Lightning wallet

667
01:10:17,815 --> 01:10:21,176
or doing some other cooperative stuff is,

668
01:10:22,135 --> 01:10:25,656
you know, how do they receive offline?

669
01:10:25,656 --> 01:10:30,216
So we completely bongored that part of Bitcoin

670
01:10:30,216 --> 01:10:33,336
where you could just, you know, share an address with someone

671
01:10:33,336 --> 01:10:37,575
and they can send that at your ledger, at their ledger.

672
01:10:37,575 --> 01:10:42,055
And you can just scan for it and receive it.

673
01:10:42,055 --> 01:10:45,096
And nothing really can go wrong.

674
01:10:45,096 --> 01:10:47,656
So it's not like if you don't claim it in two weeks,

675
01:10:47,656 --> 01:10:49,096
then it's really gone.

676
01:10:49,096 --> 01:10:51,815
If you don't look at it for a month, it will still be there.

677
01:10:52,375 --> 01:10:55,656
And these things just kind of changed.

678
01:10:56,615 --> 01:11:00,055
And we are assuming that people will be fine with it.

679
01:11:00,455 --> 01:11:02,536
I don't think people will be fine with it.

680
01:11:02,536 --> 01:11:04,695
And we already see that, you know,

681
01:11:04,695 --> 01:11:06,776
Wallet of Satoshi is hugely popular

682
01:11:06,776 --> 01:11:09,096
because it basically solves these problems.

683
01:11:09,096 --> 01:11:12,135
So people don't have to dig around with channel management.

684
01:11:12,135 --> 01:11:14,536
They don't need to incur on-chain fees.

685
01:11:15,176 --> 01:11:19,656
If they can, you know, buy Bitcoin on an exchange

686
01:11:19,656 --> 01:11:21,815
and just, you know, withdraw over Lightning,

687
01:11:21,815 --> 01:11:23,815
then they can withdraw to Wallet of Satoshi

688
01:11:23,815 --> 01:11:25,736
where they can receive offline.

689
01:11:25,736 --> 01:11:27,096
They can play with ZOPs.

690
01:11:27,096 --> 01:11:28,455
The fees are low.

691
01:11:28,455 --> 01:11:31,976
I imagine Wallet of Satoshi is especially low.

692
01:11:32,695 --> 01:11:35,255
And the whole thing is just convenient.

693
01:11:35,255 --> 01:11:39,495
And this seems like a huge pull for the users.

694
01:11:40,296 --> 01:11:43,495
And it doesn't seem to bother them

695
01:11:43,495 --> 01:11:46,615
that the provider sees everything that they are doing,

696
01:11:46,615 --> 01:11:49,815
literally, and they are fully exposed

697
01:11:49,815 --> 01:11:51,176
and they are fully in custody

698
01:11:51,176 --> 01:11:54,135
because the UX is just so damn good for them.

699
01:11:54,375 --> 01:11:56,216
So, Moon Settler, you're concerned,

700
01:11:56,216 --> 01:11:57,336
if I understood correctly,

701
01:11:57,336 --> 01:12:00,455
about the possibility of high fees in the future,

702
01:12:00,455 --> 01:12:03,416
encouraging users to use custodial Bitcoin.

703
01:12:03,416 --> 01:12:04,536
Yeah.

704
01:12:04,536 --> 01:12:09,495
But it's interesting how the drivechain community,

705
01:12:10,135 --> 01:12:12,455
many people, for example, Paul, I think,

706
01:12:12,455 --> 01:12:15,656
you know, has a view that fees might stay low.

707
01:12:15,656 --> 01:12:17,815
So you and he might have different expectations

708
01:12:17,815 --> 01:12:21,096
about the future of fees on mainchain.

709
01:12:21,416 --> 01:12:25,495
Yeah, I don't say they will be high, necessarily.

710
01:12:25,495 --> 01:12:27,336
Ideally, in a high adoption feature,

711
01:12:27,336 --> 01:12:28,375
they should be high

712
01:12:28,375 --> 01:12:31,736
because it is a very, very limited resource.

713
01:12:31,736 --> 01:12:34,536
But it can also just be very unstable.

714
01:12:34,536 --> 01:12:39,656
Like, so it can be like one sub per view by one quarter

715
01:12:39,656 --> 01:12:43,976
and 9,000 sub per view by the next quarter

716
01:12:43,976 --> 01:12:46,375
when some mania hits or whatever.

717
01:12:46,375 --> 01:12:48,455
So, yeah, I don't know.

718
01:12:48,695 --> 01:12:50,776
When some mania hits or whatever.

719
01:12:50,776 --> 01:12:54,135
So it can just be very unstable and hard to plan for.

720
01:12:55,096 --> 01:13:00,216
I don't foresee low fees,

721
01:13:00,216 --> 01:13:02,455
really affordable low fees forever

722
01:13:02,455 --> 01:13:05,255
in a future where Bitcoin is valuable and adopted.

723
01:13:05,255 --> 01:13:06,455
I think that can only happen

724
01:13:06,455 --> 01:13:08,776
if it's completely marginalized and forgotten

725
01:13:08,776 --> 01:13:14,536
because this highly replicated block space alone has value.

726
01:13:14,536 --> 01:13:17,096
So we can see that people are figuring out

727
01:13:17,096 --> 01:13:18,055
what to do with it.

728
01:13:18,695 --> 01:13:21,736
There will very likely be a baseline demand for it.

729
01:13:22,536 --> 01:13:27,096
And I find it much more likely that, you know, the fees.

730
01:13:35,575 --> 01:13:40,216
Yeah, I think the fees will be higher on L1 than L2,

731
01:13:40,216 --> 01:13:42,135
but not that high

732
01:13:42,135 --> 01:13:47,575
because people will be able to do the efficient broadcast,

733
01:13:47,656 --> 01:13:50,296
efficient news thing in various other ways.

734
01:13:50,935 --> 01:13:53,176
They'll evolve to do them in the most space efficient way.

735
01:13:54,615 --> 01:13:57,495
And so even L1, it's just people don't want to pay.

736
01:13:57,495 --> 01:13:59,495
So I don't think, but yeah,

737
01:13:59,495 --> 01:14:02,615
I think L1 could definitely be unstable also.

738
01:14:02,615 --> 01:14:03,495
I think that's the case.

739
01:14:04,856 --> 01:14:07,176
Sorry, I can't speak anymore,

740
01:14:07,176 --> 01:14:11,336
but I will stay here maybe through an emoji or something,

741
01:14:11,336 --> 01:14:14,776
but I'm off from speaking.

742
01:14:14,776 --> 01:14:15,176
Okay.

743
01:14:15,176 --> 01:14:16,695
Thank you very much as always.

744
01:14:16,695 --> 01:14:18,695
Please come back again very soon, Moon Settler.

745
01:14:20,296 --> 01:14:21,255
Welcome to the stage.

746
01:14:21,255 --> 01:14:23,416
So I didn't understand.

747
01:14:23,416 --> 01:14:24,296
What's the topic?

748
01:14:26,856 --> 01:14:28,055
We're talking about drivechain.

749
01:14:28,055 --> 01:14:31,336
That's Bitcoin Improvement Proposal 300 and 301.

750
01:14:32,776 --> 01:14:33,495
That's our topic.

751
01:14:35,416 --> 01:14:36,856
Let's talk about the halving.

752
01:14:39,416 --> 01:14:39,815
All right.

753
01:14:39,815 --> 01:14:43,656
Well, the halving is coming in 2024,

754
01:14:43,656 --> 01:14:44,856
approximately in March.

755
01:14:45,815 --> 01:14:47,015
April, April.

756
01:14:47,656 --> 01:14:52,935
3.125 Bitcoin per block in Coinbase.

757
01:14:53,815 --> 01:14:58,375
And it'll be interesting to see if that,

758
01:14:59,176 --> 01:15:01,176
if the Bitcoin price has moved since then,

759
01:15:01,176 --> 01:15:04,296
or if the miner revenue will be approximately cut in half

760
01:15:04,296 --> 01:15:05,015
due to the halving.

761
01:15:10,935 --> 01:15:11,896
What do you think about it?

762
01:15:15,575 --> 01:15:16,536
Bitcoin law.

763
01:15:16,536 --> 01:15:17,815
What do you think about the halving?

764
01:15:18,695 --> 01:15:19,176
Bullish.

765
01:15:24,216 --> 01:15:27,176
One minute and I will respond.

766
01:15:27,176 --> 01:15:27,656
One minute.

767
01:15:27,656 --> 01:15:28,615
I'm a little bit busy.

768
01:15:29,176 --> 01:15:29,495
Okay.

769
01:15:30,695 --> 01:15:33,495
Well, it's not necessarily bullish

770
01:15:33,495 --> 01:15:37,096
because Bitcoin SV and Bitcoin Cash have the same halving.

771
01:15:38,296 --> 01:15:40,216
Every so many blocks, every four years,

772
01:15:40,935 --> 01:15:41,896
there's a halving there.

773
01:15:42,856 --> 01:15:46,776
And surely you're not also equally bullish on them.

774
01:15:46,776 --> 01:15:47,976
Yeah, that didn't work.

775
01:15:52,216 --> 01:15:53,495
Yeah, lots of things have those.

776
01:15:55,495 --> 01:15:56,055
Yeah.

777
01:15:56,055 --> 01:15:58,296
I mean, there's many things in the world are scarce,

778
01:15:58,296 --> 01:15:59,736
but do not command value.

779
01:16:02,856 --> 01:16:03,736
Like Ethereum.

780
01:16:06,856 --> 01:16:10,216
Well, Ethereum does command some value.

781
01:16:10,216 --> 01:16:10,776
Does it not?

782
01:16:11,495 --> 01:16:13,015
It commands half the value of Bitcoin.

783
01:16:14,695 --> 01:16:16,856
Yeah, but one day it can go up like,

784
01:16:17,815 --> 01:16:21,736
it can go like what happened to Terra Luna.

785
01:16:22,375 --> 01:16:24,935
It has infinite supply

786
01:16:25,736 --> 01:16:28,455
and it doesn't have a maximum supply like Bitcoin.

787
01:16:28,455 --> 01:16:29,736
It has 21 million.

788
01:16:30,615 --> 01:16:34,135
And there is no proof of work like Bitcoin.

789
01:16:34,856 --> 01:16:36,055
And other than that,

790
01:16:37,176 --> 01:16:38,055
other than that,

791
01:16:38,776 --> 01:16:44,856
I think Ethereum is just a shit coin.

792
01:16:45,736 --> 01:16:48,296
I think it's like Cardano.

793
01:16:48,296 --> 01:16:52,856
Cardano, I'm actually more bullish on Cardano than Ethereum,

794
01:16:52,856 --> 01:16:54,296
even though I'm a maximalist.

795
01:16:55,176 --> 01:16:55,576
All right.

796
01:16:55,576 --> 01:16:57,495
Thank you very much for your comments.

797
01:16:58,056 --> 01:17:00,056
And we appreciate you being here.

798
01:17:01,176 --> 01:17:04,615
It's great to have lots of people come on up.

799
01:17:04,615 --> 01:17:07,335
We welcome everyone else who might have a question.

800
01:17:07,335 --> 01:17:11,896
Join the stage and share your thought or your question if you have one.

801
01:17:11,896 --> 01:17:13,816
But you can also just share a comment.

802
01:17:13,816 --> 01:17:15,495
This is Drivechain Twitter Spaces.

803
01:17:15,495 --> 01:17:18,456
We meet every Monday and Friday to discuss

804
01:17:19,095 --> 01:17:22,696
how sidechains can tremendously strengthen Bitcoin

805
01:17:24,135 --> 01:17:28,056
and potentially enable Bitcoin to absorb all of the value,

806
01:17:28,056 --> 01:17:33,896
the users and technology of every altcoin, potentially.

807
01:17:34,215 --> 01:17:37,656
And it also has the potential to boost Bitcoin's fees

808
01:17:37,656 --> 01:17:42,135
so that Bitcoin miners can make many millions of dollars per day

809
01:17:42,135 --> 01:17:45,416
from transaction fees instead of the usual, which is...

810
01:17:45,416 --> 01:17:46,696
You're kind of cutting it out.

811
01:17:46,696 --> 01:17:49,495
I don't know if you have the best connection per se.

812
01:17:54,696 --> 01:17:57,495
But maybe that's fine.

813
01:17:58,296 --> 01:18:01,095
I'm not the host, but if anyone wants to come up,

814
01:18:05,095 --> 01:18:07,896
then raise your hand using the hand button.

815
01:18:10,696 --> 01:18:12,855
Yeah, if you'd like to come on up, raise your hand,

816
01:18:12,855 --> 01:18:17,095
and we'll let you up, ask a question, share a comment.

817
01:18:19,255 --> 01:18:20,056
Am I coming through now?

818
01:18:21,015 --> 01:18:23,416
Okay, well, maybe no one wants to talk about anything,

819
01:18:25,176 --> 01:18:27,335
in which case I have lots to do.

820
01:18:27,335 --> 01:18:28,375
All right, well, we could...

821
01:18:28,375 --> 01:18:29,816
Someone pick...

822
01:18:29,816 --> 01:18:32,615
We could adjourn until Monday, until Friday.

823
01:18:35,855 --> 01:18:38,055
Okay, well, maybe no one wants to talk about anything.

824
01:18:39,575 --> 01:18:41,975
In which case, I have lots to do.

825
01:18:41,975 --> 01:18:47,775
All right, well, we could adjourn until Friday.

826
01:18:48,434 --> 01:18:51,074
Speak again Friday.

827
01:18:51,915 --> 01:18:52,235
Sounds

828
01:18:54,936 --> 01:18:56,296
All right.