WEBVTT

00:00:00.960 --> 00:00:07.760
Welcome to the Crazy Wisdom podcast. I've got Paul Sztorc here, and he is the CEO at
LayerTwo Labs.

00:00:07.760 --> 00:00:13.920
Welcome to the show. Hey, thanks for having me. So there's a bunch of different
places we could

00:00:13.920 --> 00:00:19.520
go. Let's start with Zcash. What is the relationship between Bitcoin and Zcash?

00:00:20.720 --> 00:00:28.880
Well, currently, unfortunately, there's not enough of a relationship. So Zcash is a
variant of the

00:00:28.880 --> 00:00:34.400
blockchain design where the sender, the receiver, and the amounts are all hidden.
They're all not

00:00:34.400 --> 00:00:41.360
obvious. But in the Bitcoin blockchain, you can see at least the unique key pair,
the public key

00:00:41.360 --> 00:00:46.800
of the sender and the receiver, and you know how much was sent in a given
transaction. So it's not

00:00:46.800 --> 00:00:53.600
as private as people would have liked, and that's why Zcash was invented as an
alternative. One of

00:00:53.600 --> 00:01:00.720
the many projects that we work on at LayerTwo Labs is taking that same privacy
technology and

00:01:00.720 --> 00:01:07.440
putting it as an optional LayerTwo on Bitcoin so that you can move the coins from L1
to this L2,

00:01:07.440 --> 00:01:12.080
and over there, you have the same experience that users of the Zcash altcoin have.

00:01:13.200 --> 00:01:20.800
Very cool. So it's a LayerTwo. You're building LayerTwo as an easy mechanism for
transferring

00:01:21.440 --> 00:01:23.120
Bitcoin to Zcash? Did I get that right?

00:01:23.680 --> 00:01:29.920
Not quite. Zcash is like you have to separate the technology stack of Zcash and the
code

00:01:29.920 --> 00:01:38.400
from the altcoin. It's made its own project. Zcash is its own project, and they have
their own

00:01:38.400 --> 00:01:46.320
altcoin that's separate from the 21 million BTC. And we try to reuse a similar idea,
the ZK

00:01:47.280 --> 00:01:53.520
snark or this zero-knowledge cryptography, and we make it so that you can take your
Bitcoin and put

00:01:53.520 --> 00:01:59.520
it in a new zone, and in this new zone, it has the same attributes that the Zcash
altcoin would

00:01:59.520 --> 00:02:04.000
have with its software, but this is only with Bitcoin. So it's the same 21 million
Bitcoin,

00:02:04.000 --> 00:02:13.200
but the Zcash feature. Okay, got it. So this is not related. So it's more having to
do with ZK

00:02:13.200 --> 00:02:21.280
proofs. Yeah, it's more about bringing the features from altcoin to Bitcoin, but not

00:02:21.280 --> 00:02:25.760
bringing the altcoin. And so the idea is you have 21 million Bitcoin, but we'd have
whatever

00:02:25.760 --> 00:02:30.720
features you want. You have Ethereum, smart contracts, you have Zcash, privacy,
etc., etc.

00:02:30.720 --> 00:02:36.480
You could have different block sizes or different, you could write the blockchain in
a different

00:02:36.480 --> 00:02:41.600
language. So Bitcoin Core isn't C++, but you could just have, the L2 could be
whatever you like.

00:02:42.560 --> 00:02:46.320
So how does it work to have it? I have heard in the past, I haven't looked into it
very deeply,

00:02:46.320 --> 00:02:52.480
but I've heard that L2, layer twos on Bitcoin have been slow and haven't worked that
well.

00:02:53.280 --> 00:02:58.000
Is that accurate? What are some other, is Rootstock a layer two?

00:02:58.000 --> 00:03:02.080
Yes, but you're in good company if you're confused about Rootstock, because that's
what

00:03:02.080 --> 00:03:06.480
everyone is. And even I, sometimes I'm like, what are they doing over there? And
they did all this

00:03:06.480 --> 00:03:11.680
fundraising back in 2015. There's a huge amount of money and it's like, what, I
don't know what's

00:03:11.680 --> 00:03:17.760
exactly going on over there. And another reason is that we built our own, it was
kind of a little

00:03:17.760 --> 00:03:23.760
bit of a toy, but we basically forked Geth, the Ethereum full node, and we made it
into a Bitcoin

00:03:23.760 --> 00:03:30.640
L2 as a kind of demo. And we did that like in 20, maybe 2023. And this only took
like maybe

00:03:30.640 --> 00:03:34.800
a month or two. But that was supposed to be Ethereum, excuse me, that was supposed
to be

00:03:34.800 --> 00:03:40.800
Rootstock's project was Ethereum on Bitcoin. But then we were doing it in like two
months and

00:03:40.800 --> 00:03:46.320
it's been 10 years. So I don't know. No one knows. I mean, I like, the Rootstock
people are great.

00:03:46.320 --> 00:03:55.600
I love Sergio and Diego and they're very neat. But it is confusing. I don't mean to
criticize

00:03:55.600 --> 00:04:00.320
them, but I think that they definitely could do a better idea of saying, this is
what we want to

00:04:00.320 --> 00:04:06.000
make and here it is, because we've been working on it for 10 years. So I agree with
you that a lot of

00:04:06.000 --> 00:04:14.400
the L2s aren't good. And in fact, I created this company and I created all this work
because I

00:04:14.400 --> 00:04:18.800
looked around and I thought that all this is terrible and it could be much better.
So I think

00:04:18.800 --> 00:04:23.360
they are not very good. And unfortunately, I think it's a very difficult thing to
convey without

00:04:23.360 --> 00:04:27.520
someone running the software themselves and seeing for themselves like exactly what
happened.

00:04:27.520 --> 00:04:32.320
There's also another difficulty in explaining it, which is that there's like a lot
of people

00:04:32.320 --> 00:04:39.200
just lying out there to get more favorable attention or deals or whatever,

00:04:39.200 --> 00:04:45.600
or they want to launch something. So there's not a lot of incentive, to be honest.
And it's

00:04:45.600 --> 00:04:51.040
also just kind of confusing, like every technical thing. It's very easy to just
paper something over

00:04:51.120 --> 00:04:57.760
and say, oh, it works as a demo. It works on our website or something like that.

00:04:57.760 --> 00:05:03.840
It's very hard to actually prove something out in the battle-tested arena where it's
going to be

00:05:03.840 --> 00:05:10.560
attacked by maybe hackers or come under some kind of stress that would require
decentralization.

00:05:10.560 --> 00:05:15.920
So for something to be battle-tested is really, really hard and it's very easy for
imitators to

00:05:16.880 --> 00:05:22.800
steal the valor or however you might call it. So it's very hard to explain. And
unfortunately,

00:05:22.800 --> 00:05:27.120
I think it's going to be like .com or something where there's like tons of scams and
then at the

00:05:27.120 --> 00:05:32.080
end, there will be a few people left standing. I'm a little bit pessimistic on
explaining it

00:05:32.080 --> 00:05:37.360
to people, having tried to do this for 10 years, explain why these L2s aren't very
good,

00:05:37.360 --> 00:05:44.080
why they probably have no future, what we should do instead. And I've had some
success with that,

00:05:44.080 --> 00:05:50.000
but not enough to move the whole Bitcoin culture to where I think it should be.

00:05:50.000 --> 00:05:55.120
So I think it's going to take a little while. Yeah, well, and so what you said about
a bunch

00:05:55.120 --> 00:06:01.440
of scams and sort of like it all blowing up, I told some podcast guests in the past,

00:06:01.440 --> 00:06:06.160
I told them that that's going to happen, right? There's going to be a Great
Depression-like event

00:06:06.160 --> 00:06:13.360
for crypto. And they're like, that was 2022. That was FBF. That was like a crypto
winter,

00:06:13.360 --> 00:06:17.120
basically, where it all destroyed, right? FTX, yeah.

00:06:17.120 --> 00:06:20.560
Well, that was an example. Yeah, I think we definitely go through cycles of

00:06:21.360 --> 00:06:29.920
optimism and then unfair pessimism. But this is a common pattern also, which is
that, for example,

00:06:32.160 --> 00:06:36.720
so for example, with Theranos, there was this scam blood company that maybe people
are familiar

00:06:36.720 --> 00:06:43.600
with. But when that comes out, it's so-called sucks the air out of the room. In
other words,

00:06:43.600 --> 00:06:48.080
if you wanted to start a blood company at the time, it would not be possible because
everyone

00:06:48.080 --> 00:06:50.960
would say, well, how are you going to compete with Theranos? Theranos is this great,
great,

00:06:50.960 --> 00:06:57.520
great company. So when there's the delusional optimism, it's bad for all the good
ideas.

00:06:58.320 --> 00:07:02.080
And then when Theranos collapses, now how are you going to start a blood company
now? Because

00:07:02.080 --> 00:07:09.360
everyone's going to be very wary and skeptical. Most people are not, unfortunately,
it pains me

00:07:09.360 --> 00:07:17.200
to say this, I wish it weren't the case, but most people are very superficial and
they only see the

00:07:17.200 --> 00:07:23.360
cosmetic surface and they just think blood company bad or whatever. So this has
happened in Bitcoin,

00:07:23.360 --> 00:07:30.640
where the L2s of Lightning doesn't work very well. The other L2s are kind of not
real with the

00:07:31.200 --> 00:07:37.520
extent of talking about liquid or even like fetament. These are like cheating by
just

00:07:38.160 --> 00:07:42.960
masking multi-sig as L2. This has also happened in Ethereum, where it's just
multi-sig. A multi-sig

00:07:42.960 --> 00:07:46.800
where a bunch of strangers or even one person who has all the key, because you have
no idea how they

00:07:46.800 --> 00:07:51.680
do the multi-sig ceremony. One person can just take all the money immediately. So
this led to

00:07:51.680 --> 00:07:59.520
the so-called custodial L2s, which is again, that is just like kind of saying like a
dry ocean or

00:07:59.520 --> 00:08:06.320
something. But this is just a language game that people have played to keep the
grift going. And

00:08:06.320 --> 00:08:10.560
so it's going to be very difficult to untangle all the nonsense, but there you go.

00:08:10.560 --> 00:08:13.360
Yeah. Well, I mean, and that's just not within crypto as well. That's the

00:08:14.000 --> 00:08:17.840
strangest thing about the state of the world over the past few years is that

00:08:20.160 --> 00:08:24.240
I come from Silicon Valley and I come from a Silicon Valley. I was born and raised
there.

00:08:24.240 --> 00:08:28.960
And a lot of the people that I grew up with are really involved with that early wave

00:08:29.520 --> 00:08:35.680
and during that time, none of the, I mean, there was BS like Oracle, Oracle famous,

00:08:35.680 --> 00:08:40.640
maybe not so famously, but in 2001, Larry Ellison did what he's doing today, which
is basically

00:08:40.640 --> 00:08:45.440
making up numbers about how they're going to have $300 billion in contracts over the
next years with

00:08:45.440 --> 00:08:51.680
open AI. Sam Altman's also pretty good at that. So, you know, like there have been
hucksters before

00:08:51.680 --> 00:08:56.880
and I'm not calling Sam Altman a huckster, like Oracle that in 2001, he did actually
make up

00:08:56.880 --> 00:09:03.920
numbers. So like there are people who essentially oversell and then either

00:09:03.920 --> 00:09:08.160
deliver or under deliver, but it doesn't matter at that time because they've already
got the

00:09:08.160 --> 00:09:15.360
attention and all you really need to get is their attention. So that existed in the
Bay Area,

00:09:15.360 --> 00:09:21.760
but then it wasn't like fully into it. And then starting with the social media
companies,

00:09:21.760 --> 00:09:28.080
particularly Facebook, I mean, Facebook is just like the guy was buying VPNs to spy
on users.

00:09:28.080 --> 00:09:32.720
There's so many things that that guy has done that are clearly outside the bounds of
what

00:09:32.720 --> 00:09:37.200
Western culture promotes in its values and what Silicon Valley used to promote. And
so that

00:09:37.200 --> 00:09:42.240
created this whole giant narcissism bubble that just kept on going. And then crypto
came into it

00:09:42.240 --> 00:09:48.320
and crypto tied money to it. But there is a value, like there is a huge value in
Bitcoin. I think

00:09:48.880 --> 00:09:55.440
there's value in Ethereum. I think there's value in Chainlink. I like those
companies and this is

00:09:55.440 --> 00:10:02.320
not investment advice, but so there is something real to it. But the process you
mentioned,

00:10:02.320 --> 00:10:08.160
which is really real as well, and that leads to a sort of media technology question
because

00:10:09.360 --> 00:10:15.200
what created those in the 2010, from 2010 to 2020, you had all of a sudden social
media

00:10:15.200 --> 00:10:20.720
mixing with the TV. So the TV could broadcast to hundreds of million people and then
it mixed with

00:10:20.720 --> 00:10:24.800
social media so that hundreds of million people could be directed to these social
networks.

00:10:24.800 --> 00:10:32.960
The TV no longer works. A recent podcast guest heard what I just said here now and
was like,

00:10:32.960 --> 00:10:37.200
yeah, it's true. It is breaking down, but at least like one to two billion people,

00:10:37.200 --> 00:10:41.280
maybe a lot more than that, know that Donald Trump is president. So we don't all
have

00:10:41.280 --> 00:10:46.880
synchronous attention all at the same time, but we definitely are breaking down to
the sense that

00:10:46.880 --> 00:10:52.800
the TV can mediate that in such a reliable way that you could have a hundred million
people

00:10:52.800 --> 00:10:57.760
watching the Seinfeld episodes. So that long rant was basically to say that I think
what you're

00:10:57.760 --> 00:11:02.880
talking about is going away and that people are like, I think there's going to be a
lot of builders.

00:11:02.880 --> 00:11:08.160
There already are a lot of builders out there building these things and they'll get
the attention

00:11:08.160 --> 00:11:12.240
that they need when it comes. What do you think? Do you think I'm on to something
there?

00:11:12.240 --> 00:11:19.760
Do you disagree? I do think that eventually, I do think that on a long enough time
frame,

00:11:19.760 --> 00:11:25.360
the frauds are all found out. So maybe they drag a lot of good people down with them
or

00:11:25.360 --> 00:11:31.120
innocent victims. Also, I think that's also common, but I do think you can't really
get away with it

00:11:31.120 --> 00:11:40.320
forever. I do think that it's easy, like your example, before the election, it's
very difficult

00:11:40.320 --> 00:11:46.400
to tell who's going to win or even who's currently in the lead and everyone's got an
opinion. And

00:11:46.400 --> 00:11:53.360
then over time, it sort of becomes clearer. Even on election day, it could be a
photo finish.

00:11:54.000 --> 00:11:58.800
And then even a few days afterwards, it might not be totally clear, but then over
time,

00:11:58.800 --> 00:12:04.400
it becomes extremely clear and people just give up on anyone who tried to push a
conspiracy

00:12:04.400 --> 00:12:09.520
theory saying that that's actually Kamala in a wig or in a suit or something.

00:12:09.520 --> 00:12:15.280
They just give up on that. So that shifts out of the Overton window. So I think
that's true.

00:12:16.080 --> 00:12:24.240
I think we do want to do everything we can to bring the truth forward in time. We
don't

00:12:24.560 --> 00:12:28.400
want to stall progress. I think that would be

00:12:32.160 --> 00:12:34.640
sad because there would be needless suffering for no reason.

00:12:36.320 --> 00:12:39.600
Well, that gets into the take about the information age because everything we just

00:12:39.600 --> 00:12:44.640
talked about, we're in the information age now. The industrial age, while still
relevant,

00:12:44.640 --> 00:12:49.200
is sort of not as relevant as the information age. And I think that process is
basically going

00:12:49.200 --> 00:12:55.200
to reveal a lot of things because now anybody with the LLMs can go and find out
information.

00:12:56.320 --> 00:13:00.880
And whether it's true information is really interesting. Are you a believer in the

00:13:01.920 --> 00:13:06.800
Bitcoin sound money? When we have sound money, all of our political structures can
get better

00:13:06.800 --> 00:13:11.600
because we actually have something that is tied to truth in the sense of accounting,

00:13:11.600 --> 00:13:16.240
like a good accounting system where money is valuable again. Do you buy into that?

00:13:17.040 --> 00:13:23.680
I think it is an improvement. I don't think it's the end of the road at all.

00:13:24.320 --> 00:13:32.000
I do think it's a huge problem. No one has any explanation for the fiscal trajectory
of the

00:13:32.000 --> 00:13:36.480
federal government in the United States or really in all these other governments. So

00:13:36.480 --> 00:13:40.320
every federal government is just going to spend as much as they possibly can.

00:13:40.720 --> 00:13:46.640
And the model is not, I think it's a mistake to look at it like a household where
you earn a

00:13:46.640 --> 00:13:53.360
certain amount and then you have a credit card or whatever. That is a mistake. The
politicians

00:13:53.360 --> 00:13:59.200
spend the money and then the recipients get the money. And who pays for it are
taxpayers in the

00:13:59.200 --> 00:14:04.000
future. It's a completely different group. And then even the bondholders, we go into
debt,

00:14:04.000 --> 00:14:08.880
the bondholders get a bond, they get the risk-free asset that no one will ever
default on,

00:14:08.880 --> 00:14:13.920
they get a yield. Who pays the bondholders? Future taxpayers, people who might not
even

00:14:13.920 --> 00:14:19.600
be able to vote yet. And so that is not the right model. Milton Friedman had a great

00:14:20.560 --> 00:14:24.080
thought experiment where he said, imagine hypothetically there's like a magic

00:14:24.800 --> 00:14:29.920
rich uncle or something who dies and he has whatever it is in the bank, $30
trillion,

00:14:30.720 --> 00:14:36.320
and this is enough to pay down the national debt to zero and pay off everything and
bring us back

00:14:36.320 --> 00:14:43.040
to zero. His thought experiment is what would happen the next day? The politicians
would spend

00:14:43.040 --> 00:14:47.440
the full amount back. It would be like a graph down and then it would be like a
little thing,

00:14:47.440 --> 00:14:52.080
it would tap up and then it would go all the way back to the trend line down. It
would go all the

00:14:52.080 --> 00:14:59.120
way back. They would spend the $30 trillion on some excuse. And so the model is not
a household.

00:14:59.120 --> 00:15:05.280
The model is pushing the envelope and saying, we can get money out of this system
until something

00:15:05.280 --> 00:15:16.240
breaks. And it's going to break in a horrible way. Whether you had Bitcoin or not,
it will break.

00:15:16.240 --> 00:15:20.800
But if you had Bitcoin, it would probably break earlier because they'd need to
actually come up

00:15:20.800 --> 00:15:24.480
with Bitcoin to actually pay. You can't just keep going into debt and then have the
Fed

00:15:25.200 --> 00:15:29.600
service the debt with inflation. If there were laws, if this is the thing about
crypto that's

00:15:29.600 --> 00:15:34.400
so interesting, because if there were laws that tied Bitcoin to the treasury, if the
treasury

00:15:34.400 --> 00:15:40.800
had to account... I think the ideal Bitcoin scenario is that all the federal
workers,

00:15:40.800 --> 00:15:45.280
like people who work in the army and the post office or whatever, they would be paid
because

00:15:45.280 --> 00:15:50.960
Bitcoin has taken over. So now they know and in theory, they're running a full note
or they have

00:15:50.960 --> 00:15:56.240
a wallet that access full note, because that's what everyone does in theory. And so
now the

00:15:56.240 --> 00:16:02.480
federal government needs to obtain, in order to pay them, it needs to tax.
Interesting.

00:16:02.480 --> 00:16:07.680
And it can maybe pay them with IOUs and say, I'll pay you next year. But then those
IOUs are

00:16:07.680 --> 00:16:11.920
bonds and they can have, people could trade those. You know what I mean? So someone
could say,

00:16:11.920 --> 00:16:16.080
listen, I know that the federal government's saying I'm going to get $60,000 next
year,

00:16:16.080 --> 00:16:21.280
but I don't believe them. I'll sell you this 60,000 years, $60,000 payable to the
bearer

00:16:21.280 --> 00:16:27.120
or 6,000 BTC or whatever. And I'll sell you it for 30,000 or for 40,000. So there's
immediately

00:16:27.200 --> 00:16:33.520
a bond price and there's immediately market feedback for going into debt too much.

00:16:34.800 --> 00:16:40.960
So really interesting points. Are you worried at all about the derivatives,

00:16:40.960 --> 00:16:47.920
the fact that there are now treasury companies who entire stock strategy is to buy a
bunch of

00:16:47.920 --> 00:16:51.840
Bitcoin and then have their stock be worth more because the expected increase in
value?

00:16:52.080 --> 00:16:54.320
I agree with this and I don't know. But the thing is,

00:16:56.960 --> 00:17:00.720
I hated Snapchat when it comes to this. Just because I hate something doesn't mean
it's not

00:17:00.720 --> 00:17:07.600
good. We need the world, Silicon Valley, we need the optimists to get their say. But
yeah,

00:17:07.600 --> 00:17:12.080
I don't get this idea at all. So I have background in economics and in business and
other things.

00:17:12.080 --> 00:17:15.760
And so to me, it makes absolutely no sense whatsoever. I mean, the whole point of
the

00:17:15.760 --> 00:17:18.800
company is the company is supposed to have some kind of comparative advantage.

00:17:18.800 --> 00:17:23.760
It has to take these inputs and turn them into outputs that are worth reliably much
more to

00:17:23.760 --> 00:17:29.600
cover all the overhead and to give the investors a return on the capital employed
for the business.

00:17:29.600 --> 00:17:37.040
This is all like business school 101, finance 101 stuff. It's also finance 101 or
maybe 102

00:17:37.040 --> 00:17:43.760
or something. But you should not invest in a company that is going to buy Google
stock or

00:17:43.760 --> 00:17:49.440
something. You should just buy the Google stock. This is nothing against Google
specifically. I'm

00:17:49.440 --> 00:17:55.200
just saying you don't need an intermediary. You don't need a pointless middleman.
Middlemen are

00:17:55.200 --> 00:18:00.000
very good and middlemen make the world go round. But you don't want any pointless
middleman,

00:18:00.000 --> 00:18:03.840
really. Why am I buying Google? In other words, you don't want to buy a company that
says,

00:18:03.840 --> 00:18:12.080
we will buy copper. We will buy wheat. Just buy the wheat. What are they doing?

00:18:12.880 --> 00:18:17.680
And in this case, I think it's very disturbing because the companies could get
hacked. There

00:18:17.680 --> 00:18:22.800
could be a regulatory change. They could just be an inside job and someone could
steal the Bitcoin

00:18:22.800 --> 00:18:28.560
and say, we got hacked. And then this thing with the MNAV, this idea of the NAV. The
NAV is

00:18:28.560 --> 00:18:33.680
something like the company has a million dollars worth of Bitcoin. It's currently
worth a million.

00:18:34.320 --> 00:18:41.120
But then that would be the NAV equal to one. But like for many of these companies,
the

00:18:41.920 --> 00:18:48.800
stock, the company is worth somehow is trading at higher than the, so the company is
trading at

00:18:48.800 --> 00:18:53.120
2 million. It doesn't do anything, but it has $1 million worth of Bitcoin. But why
wouldn't

00:18:53.120 --> 00:18:58.320
the whole company be worth 1 million? So wouldn't you short the company and buy
Bitcoin? And this

00:18:58.320 --> 00:19:02.160
is exactly what people have pointed out. And this is what a couple of people did.
You can go back

00:19:02.160 --> 00:19:09.600
and read. I even tweeted about it. There was someone who had been long Bitcoin in
the real

00:19:09.600 --> 00:19:16.560
spot market, and then they shorted MicroStrategy. I can only assume that trade must
have done well,

00:19:16.560 --> 00:19:21.600
because that was like a few months ago. And even though Bitcoin has gone down a
little,

00:19:21.600 --> 00:19:25.840
I think MicroStrategy has gone down more. I'm not sure. Check, always check the
math,

00:19:25.840 --> 00:19:30.240
you know, for yourself. But there was a guy who famously said that he would do this.
And he said,

00:19:30.240 --> 00:19:34.160
this has nothing to do with Bitcoin. He says, I'm actually going long Bitcoin in the
trade.

00:19:34.160 --> 00:19:38.240
This is basic financial engineering also. This is, again, maybe not finance 101,

00:19:38.240 --> 00:19:42.320
but this is certainly derivatives 101, if you ever took such a class as I have.

00:19:44.480 --> 00:19:49.680
This is like we combine several different things to get whatever you want. So like
an example would

00:19:49.680 --> 00:19:53.440
be you're in an airplane and you hear someone from Boeing, and then they go to the
bathroom

00:19:53.440 --> 00:19:57.200
and take a phone call. And you can't tell what the call is about, but you know that

00:19:57.280 --> 00:20:04.720
they really worked up about something. Well, you could buy like call options out of
the money and

00:20:04.720 --> 00:20:12.640
put options so that the stock moves a lot in either direction, you make money. So
all this stuff is...

00:20:14.160 --> 00:20:18.480
So again, and there's even more to it than that. The treasury companies,

00:20:18.480 --> 00:20:23.280
like if you just buy Bitcoin yourself, you are kind of in the situation where

00:20:24.000 --> 00:20:31.920
no one knows that you own the coin. I mean, it does depend on your own government
situation,

00:20:31.920 --> 00:20:36.160
your tax jurisdiction you're in, and what kind of other information you have and how
you bought

00:20:36.160 --> 00:20:43.680
the coins. But there's a sense in which like... So for example, if you pay down
debt, it's like

00:20:43.680 --> 00:20:48.320
a tax-free, risk-free reward. So if you're in debt and you have credit card debt and
it's 10%,

00:20:49.280 --> 00:20:55.360
you're getting charged on the debt. If you pay that down, it's like you got an
immediate tax-free,

00:20:55.360 --> 00:21:01.040
risk-free 10% return. If you get an actual return in the real stock market, you have
to sell,

00:21:01.040 --> 00:21:06.240
you have to realize the gain, you have to pay capital gains tax, you have to report
all this.

00:21:06.240 --> 00:21:09.840
It's uncertain that you will... You don't know that you're going to get the 10%.

00:21:10.640 --> 00:21:17.200
So if you buy the Bitcoin yourself, it's kind of like you have a tax-free... The
upside is sort of

00:21:17.200 --> 00:21:23.920
tax-free because it's in cyberspace and it kind of depends. And you can
strategically

00:21:25.280 --> 00:21:31.600
manage the tax consequences of that purchase. Whereas if you buy it in the
corporation world,

00:21:32.320 --> 00:21:37.360
there's like now tons and tons and tons of maybe fees, taxes, who knows.

00:21:38.640 --> 00:21:44.880
And you don't know how that... So I don't understand at all why the Bitcoin treasury

00:21:44.880 --> 00:21:53.360
companies exist. But who knows? I want to go into the technical details of what
you're doing

00:21:53.360 --> 00:21:57.600
specifically with ZK Proofs because that stuff is interesting. It's not totally in
my wheelhouse yet

00:21:57.600 --> 00:22:02.800
and I want it to be. But before we go there, I want to talk about what about a
normal company

00:22:02.800 --> 00:22:09.440
like Tesla buying Bitcoin as a treasury, as their financial hedge against their
currencies and stuff

00:22:09.440 --> 00:22:13.600
like that. Do you think that makes sense? Any thoughts there? I do. I think it could
make sense.

00:22:13.920 --> 00:22:19.040
It does cut against what I said before where I said you shouldn't buy... What Tesla
should always

00:22:19.040 --> 00:22:23.760
do is what their owners kind of want them to do. And so you shouldn't invest in
Tesla if they're

00:22:23.760 --> 00:22:29.920
just going to buy Bitcoin. However, there could be a good reason, which is like if
you're worried

00:22:29.920 --> 00:22:35.280
about having legal trouble and being sued and having some random judge somewhere tie
up all

00:22:35.280 --> 00:22:40.720
of the assets of the company in cash. If you're worried about that, now you've got
some Bitcoin.

00:22:40.720 --> 00:22:46.720
So now they can't. And now you can hire lawyers and you can have the appeals process
go on and on

00:22:46.720 --> 00:22:52.560
forever. And so you may need it as a kind of like... It's kind of like having a
backup generator

00:22:53.520 --> 00:22:59.440
at your house. And so in that way, it might actually serve a legitimate business
purpose.

00:22:59.440 --> 00:23:04.160
And I think that it could make sense. That's really cool. The other thought that I
have for

00:23:04.160 --> 00:23:08.800
the treasury... Not the treasury companies, the normal companies who have products
and services

00:23:08.800 --> 00:23:14.560
that they order, that they provide outside of that, is that it's essentially like
any company

00:23:14.560 --> 00:23:21.520
at a certain size turns into a finance company. So if they have cash like Google or
all these

00:23:21.520 --> 00:23:27.840
other companies, they maintain large cash balances in order to have cash, not like
what you said,

00:23:27.840 --> 00:23:34.000
but to go and buy acquisition if they need to or prepare for the future. And so
there's...

00:23:34.720 --> 00:23:40.400
Cash, although many companies do, which is interesting, such as Apple. But there's
also

00:23:40.400 --> 00:23:46.640
the idea of the commercial paper market or even other money market type things where

00:23:48.400 --> 00:23:54.400
a company like Walmart may have no cash. This is a hypothetical example, but they
may have no...

00:23:54.400 --> 00:23:57.040
But then they need to make payroll. They could borrow money for like

00:23:57.520 --> 00:24:03.680
two or three days, a very short term loan. So you're right that the CFOs of these
companies

00:24:03.680 --> 00:24:10.560
will do financial magic to get away with whatever cash balance they choose is
something that they

00:24:10.560 --> 00:24:14.880
think will make them the most money. So some people have a lot of cash, others have
less.

00:24:14.880 --> 00:24:19.200
I think with Apple, I may be totally wrong about this and this information may be
outdated,

00:24:19.200 --> 00:24:23.840
but I think they have like tons of cash overseas and they don't want to bring it
back because it

00:24:24.800 --> 00:24:29.360
will pay taxes. So whatever the situation is, they will manage it in a way to...

00:24:30.720 --> 00:24:33.920
I think Apple is waiting for like a... They're just going to buy their time

00:24:34.560 --> 00:24:38.240
and wait for the right government to be elected to give them like a one-time

00:24:38.240 --> 00:24:40.560
exemption to move the money back. I heard something like that.

00:24:40.560 --> 00:24:47.200
Oh, interesting. I just recently heard about something. It's in relation to Uruguay,

00:24:47.200 --> 00:24:51.680
but Uruguay is only reacting to an international thing that I believe is probably
coming from the

00:24:51.680 --> 00:24:56.880
U.S. which is the U.S. is trying to get rid of the loopholes which I believe exist
in Ireland.

00:24:56.880 --> 00:25:00.160
And what you just mentioned is just like all these different places,

00:25:00.160 --> 00:25:02.240
like the whole international system is totally crazy.

00:25:02.381 --> 00:25:29.381
And so there's the U.S. government and the international order are attempting to
maintain a 15% corporate tax on all of the different companies in the world, which
is so crazy given what we're talking about, the TV dying and social media, it all
seems like everything is going to get decentralized, including human attention. And
it feels like all these sort of... It really feels at the moment like the, in my
personal opinion, that the forces of nature are trying to get rid of the loopholes.

00:25:29.381 --> 00:25:41.381
The forces of tyranny are winning. I actually think that they're losing. But it's
like when somebody starts to lose control, they get really crazy and they start to
do crazy things.

00:25:41.381 --> 00:25:52.381
If you want to talk about it, we can definitely talk about that. Or we can move into
the technical like ZK proofs. So if you wanted to respond to that, the last thing I
said, we can do that.

00:25:53.381 --> 00:26:13.381
I think there was a famous book, The Sovereign Individual, is that what it was
called? I think. And it was about like how the internet is going to change
everyone's relationship with their government and flip it around so that previously
you're a hostage and you can be farmed up for cash.

00:26:14.381 --> 00:26:30.381
But in the future, which is now the present, I suppose, you would be able to just
change countries on a whim and move your money on a whim. And so then they would
have to compete to retain it, be more like businesses. And the countries would have
to say, come here, we will offer you such and such.

00:26:31.381 --> 00:26:41.381
We'll offer you zero percent tax. We'll offer you these laws. And they thought that
that would be a good idea. And I think I agree basically with what the book had to
say.

00:26:42.381 --> 00:27:00.381
I think there's some nuance to it. I got to go back and read that book because I've
now heard it cited so many times. The thing about the United States, though, is I
think the large empires or former empires like China and Russia are going to clamp
down on their borders.

00:27:00.381 --> 00:27:21.381
But maybe Russia wants people to move there probably because they now lack a lot of
people. So it might just be the United States. But I definitely noticed that the
United States seems to getting their border much stronger. And I guess they're
trying to attract with the $5 million visa program. But yeah, it's an interesting
question.

00:27:22.381 --> 00:27:37.381
It's a prediction of the book, The Sovereign Individual. It says there will be
various excuses to close the borders and keep the high value taxpayers in. And they
even say – they say there will be like a pandemic fearmongering and they say all
this stuff, fearmongering about immigration.

00:27:38.381 --> 00:27:53.381
It's a very long book but it does predict a lot of things. I'm not saying that that
was what happened. But it does speak to a certain number of things are tilted in the
direction of maintaining the old relationship between the taxpayer and the
government.

00:27:54.381 --> 00:28:13.381
And they'll want to lean on anything that is – that touches that legitimate or fake.
They'll just say, well, this is wishful thinking. They want a pandemic where we have
to close all the airports and no one can get out. I think Russia is in a demographic
collapse and they – I'm not sure anything can fix.

00:28:14.381 --> 00:28:40.381
They'll need lots of people to come in. Who's going to go in when you're
conscripting people and sending them in wars and things? I don't know. Who's going
to want to go over there? That's the issue with – of course, the dictatorship has
many advantages but it just has a few crucial disadvantages which is just like
people just take one look at that and they just think, well, it seems like a risk to
me so I just won't go there. And that ends up being worth a lot I think.

00:28:40.381 --> 00:28:43.381
So crazy. It's such an interesting time to be alive.

00:29:10.381 --> 00:29:30.381
So you can see the keys in Bitcoin and you can see the amount transferred in
Bitcoin. And then so you've got a zero-knowledge proof and the zero-knowledge proof
allows the same thing but it allows – or no, sorry. It allows – yeah, well, actually
it was probably a good time to hand it over to you. What does the ZK proof allow two
people to do?

00:29:31.381 --> 00:29:42.381
Well, in Zcash, first of all, everyone can reuse the same address because as I've
said, the transactions don't – they don't peg – each transaction is not pegged to
any address.

00:29:43.381 --> 00:30:01.381
So you just have one address. It's very long but it says whatever and then you can
just post it publicly and show all your friends. They can then send money to you but
no one will know that the money is coming to you or from them because you can reuse
the same address because the addresses are not connected to the transactions. So
that is a big difference.

00:30:02.381 --> 00:30:07.381
How does the transaction – how does the money get – or has value transact?

00:30:08.381 --> 00:30:21.381
Well, okay. I'm not – first of all, I'm not an expert on the actual ZK proof
technology and it's very arcane but I can explain a little bit about the type of way
that it works. It might work.

00:30:22.381 --> 00:30:46.381
So there is an idea of – so the SNARK or the NA, like – well, let me give you an
example of like how it would be – so like there's one classic example where you're
on – there's like a cave that has like a circle and you want to get out and someone
like a monster or something follows you into there and you've got to go left or
right.

00:30:47.381 --> 00:30:56.381
If you go left and they meet you, then they'll eat you or something. But if you go
the other way, then you get out.

00:30:57.381 --> 00:31:08.381
And so the question is if you tested the person a million times and they got out
every time, then that would show that they know which way the monster is heading.

00:31:09.381 --> 00:31:14.381
The monster is headed left or right and you know – you evade them every time or what
have you.

00:31:15.381 --> 00:31:17.381
I probably butchered that but that's like a classic example.

00:31:18.381 --> 00:31:24.381
So that's sort of interactive in the sense of you have tested them over and over
again and you see they pass every time.

00:31:25.381 --> 00:31:31.381
So I don't know how and they – most critically, this is the zero knowledge part,
which is it's not justified.

00:31:32.381 --> 00:31:34.381
I'm not telling you how I get out of the cave every time.

00:31:35.381 --> 00:31:37.381
I'm not telling you how.

00:31:38.381 --> 00:31:40.381
But we all know that I can.

00:31:41.381 --> 00:31:42.381
So somehow I'm doing it.

00:31:43.381 --> 00:31:44.381
Interesting. OK.

00:31:44.381 --> 00:31:50.381
So that's a way of making the argument that I know something without anyone really
kind of explaining.

00:31:51.381 --> 00:31:53.381
It's just to have this repeated test.

00:31:54.381 --> 00:31:56.381
So that may shed some light on it.

00:31:57.381 --> 00:32:05.381
This has been described as moon math before and even when – what was that guy's
name?

00:32:06.381 --> 00:32:10.381
Zuko Wilcox, the creator of Zcatch.

00:32:10.381 --> 00:32:13.381
He first would give talks about this and he would say I have absolutely no idea how
any of this works.

00:32:14.381 --> 00:32:16.381
He had like math on the slides and he'd say no one knows how this works.

00:32:17.381 --> 00:32:18.381
This was like in 2015 or something.

00:32:19.381 --> 00:32:21.381
So I'm hesitant to try to explain how to render it.

00:32:22.381 --> 00:32:29.381
But the thing is there's a – because – partially because of Zcatch, there is a large
– and because of Ethereum.

00:32:30.381 --> 00:32:37.381
There's a large research community around this and they have built software
libraries and we have just taken the Zcatch one piece.

00:32:37.381 --> 00:32:42.381
There's a huge stack, but they have like a Zk-SNARK library now.

00:32:43.381 --> 00:32:45.381
And that's just open source online.

00:32:46.381 --> 00:32:52.381
So it is not – I don't know how fruitful it would be to try to explain.

00:32:53.381 --> 00:32:56.381
But we could continue to try or we could –

00:32:57.381 --> 00:32:58.381
No, no, no.

00:32:59.381 --> 00:33:02.381
I've got a specific question because I only asked that question because I wasn't
familiar with it.

00:33:02.381 --> 00:33:04.381
And that actually answered a lot of questions.

00:33:05.381 --> 00:33:12.381
Why it's been so hard for me to figure out Zk-proofs is because there's moon math
involved and I'm going to definitely steal that terminology.

00:33:13.381 --> 00:33:19.381
So what was that tiny piece that you got from all the Zk-proofs and attached to
Bitcoin?

00:33:20.381 --> 00:33:21.381
What's the relationship to Bitcoin?

00:33:22.381 --> 00:33:25.381
Well, OK, that's a different question.

00:33:25.381 --> 00:33:32.381
But they have – Zcatch has produced different like phases and they named them after
plants.

00:33:33.381 --> 00:33:36.381
Like one was like sapling and one was like sprout.

00:33:37.381 --> 00:33:38.381
One was like orchard.

00:33:39.381 --> 00:33:40.381
So there's like the latest version.

00:33:41.381 --> 00:33:51.381
Now to have the Zcatch altcoin function, they actually need this kind of like
turnstile thing where the money will leave the old zone and go into the new zone.

00:33:51.381 --> 00:33:54.381
And they made numerous improvements over the years.

00:33:55.381 --> 00:34:00.381
So for example, on the old Zcatch, you could not run the software on a phone.

00:34:01.381 --> 00:34:03.381
It was too resource intensive.

00:34:04.381 --> 00:34:05.381
Wow.

00:34:05.381 --> 00:34:07.381
And also you had to have a trusted setup with a few people.

00:34:08.381 --> 00:34:14.381
So if they all colluded, they could break the privacy.

00:34:15.381 --> 00:34:17.381
But you needed everyone to collude.

00:34:17.381 --> 00:34:25.381
So as long as one person like destroys – this was called a toxic – I think it was
called toxic waste or something like that was the nickname for it.

00:34:26.381 --> 00:34:27.381
Everyone had to like do this thing.

00:34:28.381 --> 00:34:34.381
Like a group of people did this and they had to delete what they had on their
computer.

00:34:35.381 --> 00:34:37.381
As long as at least one person did that, it would work.

00:34:38.381 --> 00:34:40.381
Now this was then upgraded to like something like 80 people.

00:34:40.381 --> 00:34:41.381
And then they have a new version.

00:34:42.381 --> 00:34:52.381
This is this thing called Halo 2, which did not require the trusted setup or at
least did something that was like so feasible that it's no longer a relevant issue.

00:34:53.381 --> 00:34:55.381
So this is all in their orchard crate.

00:34:56.381 --> 00:34:57.381
They have like a rust crate.

00:34:58.381 --> 00:34:59.381
I'm not sure how familiar you are with rust crates.

00:35:00.381 --> 00:35:01.381
But rust puts everything in these crates.

00:35:02.381 --> 00:35:03.381
And so they have a rust crate for that.

00:35:03.381 --> 00:35:13.381
Is that like a – what is it when you go – oh man, how could I forget?

00:35:14.381 --> 00:35:15.381
Docker. Is it like a Docker container for rust?

00:35:16.381 --> 00:35:17.381
Well, a little bit.

00:35:18.381 --> 00:35:20.381
Of course, it is kind of like a dependency in a way.

00:35:21.381 --> 00:35:27.381
And just merely the crate is not enough because it's not enough to have – that
doesn't equal like a wallet or a node or whatever.

00:35:28.381 --> 00:35:30.381
But this is like the crypto library that does the moon math.

00:35:31.381 --> 00:35:32.381
So it's like moon math in and out.

00:35:33.381 --> 00:35:34.381
So I took that part.

00:35:35.381 --> 00:35:40.381
Connecting things to Bitcoin is a different matter, which is my other area, which is
the sidechain or the Drivechain.

00:35:41.381 --> 00:35:42.381
It was Bitcoin 300.

00:35:43.381 --> 00:35:47.381
It's something I've been into for a long time about what is the right way if you
don't like what Bitcoin Core is doing.

00:35:48.381 --> 00:35:54.381
If you think the block time should be faster or the block size should be bigger or
that there should be smart contracts or something else.

00:35:54.381 --> 00:36:03.381
How do you have like a competing piece of software where you have real Bitcoin on
there and in a way that actually works?

00:36:04.381 --> 00:36:16.381
Where you have this infinite freedom, the open source kind of freedom, but you also
are not weighing everyone else down on Bitcoin Core with all of your weird ideas,
which may be terrible ideas.

00:36:16.381 --> 00:36:21.381
So that was an old concept that I became obsessed with in 2015.

00:36:22.381 --> 00:36:24.381
And that is what became the Drivechain idea.

00:36:25.381 --> 00:36:29.381
What is sometimes today called the sidechain, although that word has also been
abused.

00:36:30.381 --> 00:36:32.381
And now I think that word has basically no meaning.

00:36:33.381 --> 00:36:34.381
So it's a Drivechain.

00:36:35.381 --> 00:36:36.381
A Drivechain is what you're calling it.

00:36:38.381 --> 00:36:41.381
At LayerTwo Labs, we have like a few of these type of things.

00:36:42.381 --> 00:36:43.381
And that's really interesting.

00:36:43.381 --> 00:36:45.381
I haven't picked this up since, when was that?

00:36:46.381 --> 00:36:48.381
It was in 2018 when there was a block size war.

00:36:49.381 --> 00:36:50.381
When was the block size war?

00:36:51.381 --> 00:36:56.381
Well, I would say it kind of ended around 2017, although arguably continued for
another year as Bitcoin Cash.

00:36:57.381 --> 00:37:07.381
August 1st was the launch of Bitcoin Cash and then November of 2017 was the
abandonment of SegWit2x, which caused the split.

00:37:08.381 --> 00:37:12.381
And then you could arguably say that they kind of still fought it out for another
year.

00:37:13.381 --> 00:37:14.381
Got it.

00:37:15.381 --> 00:37:26.381
But Bitcoin Cash never really overtook BTC in terms of recognizability, adoption,
whatever.

00:37:27.381 --> 00:37:36.381
So that would be – that's the short version is that that was the finally being
ousted and going into like altcoin kind of status.

00:37:36.381 --> 00:37:48.381
Really, the block size war raged from maybe at least – I mean, definitely in 2015,
it got very big with Mike Hearn and Bitcoin XT and the scaling Bitcoin conferences.

00:37:49.381 --> 00:37:51.381
It's kind of always in the background a little bit.

00:37:52.381 --> 00:37:56.381
Well, let's talk about that because you're essentially – you want to create a
Drivechain.

00:37:57.381 --> 00:38:05.381
And this Drivechain will allow people to essentially transact with privacy off of
Bitcoin, which is really interesting.

00:38:06.381 --> 00:38:09.381
Can you talk more about that, how the privacy will work?

00:38:10.381 --> 00:38:13.381
I have one, this Zcash related L2.

00:38:14.381 --> 00:38:15.381
It's sometimes called Zside.

00:38:16.381 --> 00:38:17.381
Zside, OK, cool.

00:38:18.381 --> 00:38:19.381
It's a sidechain.

00:38:20.381 --> 00:38:22.381
But then I have a separate one called – you can just keep doing this all day.

00:38:23.381 --> 00:38:26.381
And I have a separate one that I call Thunder as a kind of lightning joke.

00:38:27.381 --> 00:38:34.381
And that one, if you had – I have like a plan to have like 14 geographically
distributed.

00:38:35.381 --> 00:38:40.381
So you have like one for like North America, one for like Western Europe, one for
like Southeast Asia.

00:38:41.381 --> 00:38:48.381
And if you had like 14 of these, you could have – with the software we currently
have, it would be able to process every transaction on earth.

00:38:48.381 --> 00:39:02.381
And I recently had like a contest to improve the performance and try – test 960
megabyte blocks and see how to improve the performance, which was – I think it was a
big success.

00:39:03.381 --> 00:39:12.381
And anyone can go online now and look at the – we had like the benchmark script used
to test the software and it will generate – it takes like an hour.

00:39:12.381 --> 00:39:26.381
But it will generate a huge number of transactions as if it will like kind of load
this huge buffer of transactions as if there were trillions of transactions per
year, roughly 9 trillion transactions per year at a certain rate.

00:39:27.381 --> 00:39:33.381
And then it will connect like 10 blocks of that and it will time with the stopwatch
and you can see how long that takes.

00:39:34.381 --> 00:39:36.381
And it does – it takes – it's reasonably fast.

00:39:37.381 --> 00:39:39.381
It's only a few minutes or so.

00:39:39.381 --> 00:39:42.381
So actually it's – and it's 10-minute blocks.

00:39:43.381 --> 00:39:45.381
So as long as it's less than 10 minutes, then you're in business.

00:39:46.381 --> 00:39:49.381
And this is like on normal – pretty normal hardware.

00:39:50.381 --> 00:39:52.381
This is just on like the GitHub runner thing.

00:39:53.381 --> 00:39:55.381
So that's my plan to scale Bitcoin.

00:39:56.381 --> 00:40:05.381
And we again are testing it at planetary scale right now, which is something that I
really don't think anyone has done or even would even dream of trying to do.

00:40:05.381 --> 00:40:14.381
With Lightning, they realize – at least by now on a subconscious level, they realize
that you can't onboard people to Lightning without an L1 transaction.

00:40:15.381 --> 00:40:17.381
So it's a complete dead end for scaling.

00:40:18.381 --> 00:40:19.381
But everyone is just dancing around this.

00:40:20.381 --> 00:40:28.381
So I got to go into that one because that – somebody tried to send me a Lightning
thing and it did not work.

00:40:29.381 --> 00:40:31.381
And it sounds – it seems like it's dead.

00:40:31.381 --> 00:40:32.381
It's custodial.

00:40:33.381 --> 00:40:34.381
It doesn't use Bitcoin network or the Lightning network.

00:40:35.381 --> 00:40:36.381
It's just an – it's like an app that updates.

00:40:37.381 --> 00:40:38.381
You have a third party.

00:40:39.381 --> 00:40:40.381
On their app and it's all fake.

00:40:41.381 --> 00:40:42.381
And that's all travesty.

00:40:43.381 --> 00:40:45.381
So can you go into that specific thing that you mentioned?

00:40:46.381 --> 00:40:47.381
I mean there's a bunch of things I want to go back to.

00:40:48.381 --> 00:40:49.381
One is the 960 megabyte block.

00:40:50.381 --> 00:40:57.381
But before we go into that, I want to go into Lightning, which is why is – why is
Lightning failing basically?

00:40:58.381 --> 00:41:01.381
Well, it's like a good attempt.

00:41:02.381 --> 00:41:06.381
But part – it has just fundamentally is incapable of doing the job.

00:41:07.381 --> 00:41:17.381
So Lightning was this idea that was just like six degrees of separation like Kevin
Bacon type idea where if you want to pay someone, maybe you don't know them
personally.

00:41:18.381 --> 00:41:20.381
But you probably know someone who knows someone that they know or something.

00:41:21.381 --> 00:41:22.381
You build this route.

00:41:22.381 --> 00:41:31.381
So the idea is we'd already have all these channels open with people and that we
could reuse on L2 with the channels we would send – not on L1.

00:41:32.381 --> 00:41:35.381
And on L2, we would be able to have a path and we would be able to send them.

00:41:36.381 --> 00:41:39.381
So the problem is opening a channel requires one L1 transaction.

00:41:40.381 --> 00:41:41.381
And so there's not enough space for that even.

00:41:42.381 --> 00:41:50.381
Even in a hypothetical world where we all only need one transaction ever in our
lives on Bitcoin L1, there's not enough space.

00:41:50.381 --> 00:41:55.381
It would take like something like six or seven years to onboard everyone, which is
too long.

00:41:56.381 --> 00:41:57.381
But the bigger issue –

00:41:58.381 --> 00:41:59.381
So the block size?

00:42:00.381 --> 00:42:01.381
Yeah, the channels don't last that long.

00:42:02.381 --> 00:42:05.381
You have to refresh them because of liquidity issues and of course people need more
than one channel.

00:42:06.381 --> 00:42:15.381
And in fact, when Lightning works now, it often uses this thing called the submarine
swap, which again, these are all fancy terms for just saying that Lightning is
broken but without admitting that out loud.

00:42:15.381 --> 00:42:22.381
So the submarine swap is a one L1 transaction made by one of the two parties to
reset the liquidity.

00:42:23.381 --> 00:42:27.381
So it's like you use Lightning but they use one L1 transaction is required each
time.

00:42:28.381 --> 00:42:29.381
So the Lightning part is kind of superfluous.

00:42:30.381 --> 00:42:33.381
So the block size war was lost basically.

00:42:34.381 --> 00:42:35.381
That's what you're trying to say.

00:42:36.381 --> 00:42:42.381
I actually was a small blocker and I still am and I'm in favor of shrinking block
size because we can have the L2 that has the unlimited block size.

00:42:42.381 --> 00:42:45.381
So I always thought it doesn't matter what the L1 block size can be very small.

00:42:46.381 --> 00:42:56.381
But the issue is that the L1 – well, the block size war led to a situation where the
large blockers said we need to increase the block size.

00:42:57.381 --> 00:43:05.381
They lost and this discredited them and it discredited anything related to like
block size or blockchain design.

00:43:06.381 --> 00:43:11.381
And it discredited – also the miners took their side so it discredited anything
related to like mining or collecting L1 transaction fees.

00:43:12.381 --> 00:43:14.381
So this was like a 10-year setback I think.

00:43:15.381 --> 00:43:22.381
And then meanwhile the people who won, their answer to what are we going to do
because the block size does not scale Bitcoin.

00:43:23.381 --> 00:43:24.381
The L1 blocks are too small.

00:43:25.381 --> 00:43:26.381
So what do we do?

00:43:27.381 --> 00:43:30.381
Their answer was we'll scale in layers and specifically we'll scale with the
Lightning network.

00:43:31.381 --> 00:43:38.381
So this led everyone to put all of their attention on Lightning which has been a
huge – Lightning is basically the Theranos of Bitcoin unfortunately.

00:43:39.381 --> 00:43:44.381
But it has distracted everyone and it has pulled everyone away from what they should
have been doing the whole time.

00:43:45.381 --> 00:43:46.381
But now people are realizing that.

00:43:47.381 --> 00:43:49.381
But now there's been like two 10-year setbacks.

00:43:50.381 --> 00:43:53.381
Now people are starting to come back.

00:43:54.381 --> 00:43:55.381
It's so interesting.

00:43:56.381 --> 00:43:57.381
Only a few people too.

00:43:58.381 --> 00:44:02.381
But this started this like Bitcoin Season 2 and like the push for Covenants and like
ARK and stuff like that.

00:44:03.381 --> 00:44:09.381
These are people – again, this is all just a way of admitting that Lightning doesn't
work without saying that out loud.

00:44:10.381 --> 00:44:12.381
You get invited to the right parties.

00:44:13.381 --> 00:44:14.381
It's very common.

00:44:15.381 --> 00:44:16.381
And Bitcoin is a bit of a religion.

00:44:17.381 --> 00:44:18.381
I'm just a supporter of that religion.

00:44:19.381 --> 00:44:20.381
So it is very common.

00:44:21.381 --> 00:44:22.381
And they call it Covenant 2 which is really funny.

00:44:23.381 --> 00:44:28.381
Yeah, it's kind of pretentious and like aloof weird term that is not very
accessible.

00:44:29.381 --> 00:44:31.381
It's not just like where are the Anglo-Saxon words?

00:44:32.381 --> 00:44:35.381
Like backhoe or whatever, wifebeater.

00:44:36.381 --> 00:44:38.381
Where are the clear words that just say what you mean?

00:44:39.381 --> 00:44:40.381
They're nowhere to be found.

00:44:41.381 --> 00:44:44.381
But this is the problem with Lightning also is that it's very technical.

00:44:45.381 --> 00:44:46.381
You can get the VCs.

00:44:47.381 --> 00:44:50.381
If you pronounce the right words, the VCs have no idea what's going on.

00:44:51.381 --> 00:44:52.381
So they will just invest.

00:44:53.381 --> 00:44:55.381
And so that's why it is – unfortunately, yeah.

00:44:56.381 --> 00:44:58.381
That's part of why it's a setback because it's self-reinforcing.

00:44:59.381 --> 00:45:00.381
Yeah, no.

00:45:01.381 --> 00:45:05.381
It's so strange and it's absurd and it's funny like a lot of things are now.

00:45:06.381 --> 00:45:11.381
But you're optimistic because you're building this thing that is going to change.

00:45:12.381 --> 00:45:18.381
It's quite hard to be pessimistic when first of all, Bitcoin has done like 100,000x
ROI.

00:45:19.381 --> 00:45:21.381
So Bitcoin has succeeded enormously.

00:45:22.381 --> 00:45:23.381
Everyone hated it.

00:45:24.381 --> 00:45:26.381
All the years I've known about Bitcoin, everyone was hating it.

00:45:26.381 --> 00:45:27.381
It was awkward to talk about.

00:45:28.381 --> 00:45:32.381
You couldn't even talk about it with like your friends and family because it was
just so stigmatizing.

00:45:33.381 --> 00:45:35.381
And you seemed like you were getting scammed the whole time.

00:45:36.381 --> 00:45:37.381
But yet it prevailed and crushed everyone.

00:45:38.381 --> 00:45:40.381
It became a voting block issue.

00:45:41.381 --> 00:45:45.381
It made everyone wealthy and powerful and interesting.

00:45:46.381 --> 00:45:50.381
And the other thing is I had the Drivechain idea back in 2015.

00:45:50.381 --> 00:45:55.381
So the whole time I've known that it's possible to make Bitcoin scale to the whole
planet.

00:45:56.381 --> 00:46:02.381
And it's possible to have Bitcoin transactions that do the same smart contracts at
the same EVM as Ethereum.

00:46:03.381 --> 00:46:04.381
And it's the same privacy as Zcash.

00:46:05.381 --> 00:46:06.381
So I always knew that that was possible in theory.

00:46:07.381 --> 00:46:08.381
Because of the block size.

00:46:09.381 --> 00:46:15.381
And then eventually like in late 2022, I started this company because I just was
tired of waiting for this to happen.

00:46:16.381 --> 00:46:17.381
So I was like, I'll just have to do it myself.

00:46:17.381 --> 00:46:21.381
It's still a lot of what I have to say is misunderstood by a lot of people.

00:46:22.381 --> 00:46:27.381
So but what is the – because you said you were a small block size.

00:46:28.381 --> 00:46:29.381
What is the –

00:46:30.381 --> 00:46:31.381
Right, I'm on L1.

00:46:32.381 --> 00:46:33.381
But then 960 is L2.

00:46:34.381 --> 00:46:37.381
So this ignores the night and day difference between L1 and L2, which is the
all-important night and day difference.

00:46:38.381 --> 00:46:39.381
The L2s are optional.

00:46:40.381 --> 00:46:45.381
If they fail for any reason, if they get attacked, if they have a bug and they
crash,

00:46:45.381 --> 00:46:50.381
if the government says running the L2 software will get you shot in the head and
killed, it doesn't matter.

00:46:51.381 --> 00:46:53.381
That can just fail or it can just even be on pause.

00:46:54.381 --> 00:46:55.381
It can just be – we can just bide our time.

00:46:56.381 --> 00:46:57.381
It's like the Mott and Bailey type thing.

00:46:58.381 --> 00:47:00.381
If that fails for any reason, it doesn't make any difference.

00:47:01.381 --> 00:47:10.381
The L1, if the L1 is mandatory for everyone to run in order for the miners to get
paid, in order for the blocks to flow, in order for proof of work to happen, the L1
is mandatory for everyone.

00:47:10.381 --> 00:47:19.381
And really if you think about it, the way I have structured it, it's like the L1 is
mandatory and then if you want to run the L2, you need the L1 plus the L2.

00:47:20.381 --> 00:47:23.381
So every L2 node needs the L1 node, but the reverse is not the case.

00:47:24.381 --> 00:47:26.381
So what we're saying is it's kind of like a la carte.

00:47:27.381 --> 00:47:33.381
How much do you want everyone to have to pay in terms of the cost of running the
full nodes?

00:47:34.381 --> 00:47:35.381
So does that make sense?

00:47:35.381 --> 00:47:42.381
So you can see why at first you want the first pass to be as low as possible because
you don't want to exclude anyone from the first zone.

00:47:43.381 --> 00:47:49.381
Then when you want to staple more stuff on, you can grow it to whatever you think is
the right size.

00:47:50.381 --> 00:47:55.381
And then maybe there will only be a few nodes, but it won't matter because you're
pushing the envelope.

00:47:56.381 --> 00:47:59.381
This is explicitly we've switched from something that everyone must do.

00:48:00.381 --> 00:48:01.381
It's kind of like a pacemaker.

00:48:02.381 --> 00:48:03.381
You don't want it to be very adventurous.

00:48:04.381 --> 00:48:05.381
You want it to be very simple.

00:48:06.381 --> 00:48:07.381
You want it to be very reliable.

00:48:08.381 --> 00:48:11.381
You don't want the pacemaker to have Bluetooth or something, right?

00:48:12.381 --> 00:48:15.381
But the L2s are a completely different thing.

00:48:16.381 --> 00:48:17.381
They're optional.

00:48:18.381 --> 00:48:19.381
So now we have them of all shapes and sizes.

00:48:20.381 --> 00:48:23.381
So we have the Zcache one, we have Thunder, we have a few more.

00:48:24.381 --> 00:48:25.381
Oh, got it.

00:48:26.381 --> 00:48:31.381
So you're making multiple L2s because you're just thinking about it from an adoption
standpoint.

00:48:31.381 --> 00:48:32.381
If it gets adopted.

00:48:37.381 --> 00:48:40.381
An L2, let me explain what I think an L2 is.

00:48:41.381 --> 00:48:42.381
And then you can help me figure it out.

00:48:43.381 --> 00:48:45.381
An L2 is basically something.

00:48:46.381 --> 00:48:49.381
So you got an L1 that is computing blocks.

00:48:50.381 --> 00:48:55.381
The miners use their computation power to basically do a cryptographic puzzle.

00:48:56.381 --> 00:48:58.381
And then they get rewarded with that cryptographic puzzle.

00:48:58.381 --> 00:49:01.381
And that's to mine one Bitcoin block.

00:49:02.381 --> 00:49:07.381
The L2, what is the relationship between that and the L1?

00:49:08.381 --> 00:49:09.381
The L2 and the L1 in that scenario?

00:49:10.381 --> 00:49:13.381
Well, I think we have to sort nodes from miners.

00:49:14.381 --> 00:49:21.381
The nodes are doing the CPU work of assembling the transactions into a block.

00:49:22.381 --> 00:49:24.381
And checking each block, storing each block on your computer.

00:49:25.381 --> 00:49:27.381
So this is the so-called data availability problem.

00:49:29.381 --> 00:49:31.381
So the blockchain is stored by the nodes.

00:49:32.381 --> 00:49:38.381
And the miners, it's actually the miners are their own kind of similar to the L2, L1
relationship.

00:49:39.381 --> 00:49:42.381
You need to run a node in order to mine or you need to talk to one.

00:49:43.381 --> 00:49:46.381
You need to have someone, someone out there has to give you information if you're a
miner.

00:49:47.381 --> 00:49:49.381
The miner is like a customer of the node.

00:49:50.381 --> 00:49:52.381
It's a little bit backwards than the way a lot of people think about it.

00:49:52.381 --> 00:49:58.381
So if you're mining, you either need a node yourself or you need someone's node
somewhere.

00:49:59.381 --> 00:50:00.381
You need to let them borrow it.

00:50:01.381 --> 00:50:02.381
Got it, got it.

00:50:03.381 --> 00:50:03.973
Everyone who gets paid.

00:50:03.973 --> 00:50:30.973
If you run a store and you accept Bitcoin, or if you're a laborer, and your boss
pays you in Bitcoin, the node is what tells you whether or not you have been paid.
There are various hacks and, and cheats and things. But that's really the purpose of
the node. This is another thing that very, very few people understand. This is the
part of the whole knots versus core controversy is based on misunderstanding this as
well, which is what's the point of the node. The point of the node is to validate
incoming transactions.

00:50:30.973 --> 00:50:44.973
So if you, if you aren't, if you don't own a store and you're selling stuff for
Bitcoin, or you're not a, you don't own like a graphic design consultancy, and
you're being paid in Bitcoin, then the node isn't doing that much for you.

00:50:44.973 --> 00:50:57.973
You could maybe say it's archiving the blockchain. But we don't really need that as
much as people think so. Whereas if you're something like Coinbase, or you're Kraken
or whatever, people are sending you Bitcoin all the time.

00:50:58.973 --> 00:51:16.973
So their node is really important. Not only do they run one node, but they run
multiple old, they're probably running Bitcoin 0.12 and 13 and 14. They run them
all. And if anything weird happens, they have like a giant button that they press
that probably halts the whole, this is how I assume it works.

00:51:16.973 --> 00:51:39.973
But I've talked to people in the industry. And I know that it does work or something
like that. So those people are critically relying on the nodes. And then other
people just kind of think, well, I'm running my node to this, they think this is
like some kind of American Idol text to you want to win situation, which it is not.
But that's fine. Also that people are, I'm glad I'm happy that people are excited
about something or whatever.

00:51:40.973 --> 00:51:59.973
So the node, to review what I was talking about, the miners need a node, in part
because the miners are getting paid by their pool or they find a block and the block
is going to pay them three Bitcoin or it used to be 50 Bitcoin. So obviously in the
past, if you were mining, you wanted the node because you wanted to see if you hit
the block or not, which is the only real way to know.

00:51:59.973 --> 00:52:16.973
So these are all people have money coming in. And so the nodes do this part. The
miners are just grinding SHA-256. They grind this SHA-256d, double SHA-256. And they
try to get the hash of the blocks header to be very, very low.

00:52:16.973 --> 00:52:38.973
Because the hash is a giant integer. And so they say it has to start with a certain
number of leading zeros. That's like a computer science term, because what they're
thinking of is the memory of the computer, which is ones and zeros. So they're
thinking of those zeros, they're thinking 0, 0, 0, 0, 0. But a regular person would
just say each block header, basically, the hash is basically a number. It's a huge
number.

00:52:39.973 --> 00:53:01.973
But it's a number chosen between 0 and like 2 to the 256. Which is basically, I
think I used to be able to do this a little bit better. But I think it's something
like 16 to the 64th. Is that right? It's 2 to the 256. You can change it around,
maybe off by one or two. But that 10 to the 80th is the number of atoms in the
universe.

00:53:02.973 --> 00:53:19.973
So if you see 1664, of course, it's not, but I'm just saying like, this is like the
biggest number. You know, it's like really, really big. So you're picking a big
number and the difficulty adjustment is saying it's only valid if it is in a very
narrow set.

00:53:20.973 --> 00:53:42.973
So if the first bit starts, you think about the first bit is 0 or 1. If you say we
only want the numbers in the first half, we're going 0 to 2 to the 256, the max. If
you say you've got to make it halfway, at least, that's like saying we'll give up
half the hashes and the number has to start with at least one zero.

00:53:43.973 --> 00:53:46.973
There's this thing called Indianness, but I don't want to confuse.

00:53:46.973 --> 00:53:47.973
Indianness?

00:53:48.973 --> 00:53:59.973
You have this huge timeline or this huge space, and half of them are in the top
half. That's the first zero. And then 25% of them start with two zeros in a way.

00:54:00.973 --> 00:54:18.973
So when people say this about solving the puzzle, and must start with a certain
number of zeros, they mean the more and more zeros eventually in the top eighth, top
164th, and in fact, we've really crunched it way down, where it's a tiny, tiny, tiny
percentage, because there's 256 numbers that could either be 0 or 1.

00:54:19.973 --> 00:54:37.973
And so for you to even get to something like 16, or I mean, I think 2 to the 10th is
like 1024 or something, so you're already throwing away 99.9% of the blocks, even
when you're just starting with 10 zeros.

00:54:37.973 --> 00:54:40.973
But now at this point, we're starting with huge amounts.

00:54:40.973 --> 00:54:44.973
So that's what the miners do. I don't know if that was too weird.

00:54:44.973 --> 00:54:57.973
No, no, no. This is all interesting, because the way I learn is I get an abstract
concept, and then that abstract concept, the more I go into it, the more I realize
that it doesn't accurately reflect reality.

00:54:57.973 --> 00:55:03.973
And so that number that you were describing, that really long number, I got that
that's the puzzle.

00:55:03.973 --> 00:55:05.973
That is the hash effect.

00:55:05.973 --> 00:55:10.973
So when you go on a block explorer and you click on a block, that's what that is.

00:55:10.973 --> 00:55:24.973
You can go on right now and look, and you'll see not only does it start with zeros
in the sense of the bits in the computer's memory, but when you have eight of those
in a row, it ends up being a zero when they put it in hex anyway.

00:55:24.973 --> 00:55:32.973
So you'll see it actually, the real one has lots of real zeros that it starts with
also, because it just has so many zeros.

00:55:33.973 --> 00:55:34.973
And the miners are competing.

00:55:34.973 --> 00:55:47.973
I may have a double or triple check. It depends on how, because people do the hex,
they do two hex characters, and that's 256. So it's actually two zeros, but I don't
want to like, this is not the type of thing you should just say glibly on a podcast.

00:55:47.973 --> 00:55:58.973
Everyone can look up like exact details of it all, but what I'm saying is the, when
you look at the block, it will print it out in hex, it will not print it out in
binary, like a big string of ones and zeros.

00:55:58.973 --> 00:55:59.973
Got it.

00:56:00.973 --> 00:56:11.973
That's why I remember that joke from Silicon Valley, the show, and like the first
episode where he does his multiplication tables in hex, he says like five times F.

00:56:11.973 --> 00:56:26.973
And he says it's like it's 75 or something, he just makes the, he just made that up,
but the point is, there's, hex is like counting to 16 and if you count to 16 twice
you get to 256, and so two zeros and I don't know, this is probably boring people at
this point.

00:56:27.973 --> 00:56:31.973
The joke, look up the joke of what's, I think it's what's five times F is the joke.

00:56:31.973 --> 00:56:32.973
So.

00:56:32.973 --> 00:56:35.973
He just made that up, Ehrlich Bachman, the cowboy actor.

00:56:35.973 --> 00:56:36.973
So.

00:56:36.973 --> 00:56:37.973
But it's funny anyway.

00:56:37.973 --> 00:56:43.973
So what are the miners competing to do in that thing that you just said?

00:56:43.973 --> 00:56:49.973
They are, what they do is they have a, the block is changing all the time, first of
all, because new transactions are coming in.

00:56:49.973 --> 00:56:50.973
Yeah.

00:56:50.973 --> 00:56:51.973
The transactions change the Merkle tree.

00:56:51.973 --> 00:56:52.973
Yeah.

00:56:52.973 --> 00:56:55.973
Okay, Merkle tree, I got to go study that.

00:56:55.973 --> 00:56:56.973
I'm sorry.

00:56:56.973 --> 00:57:00.973
No, no, I was just saying I got to, can you hear me now?

00:57:00.973 --> 00:57:01.973
Yes.

00:57:01.973 --> 00:57:03.973
Yeah, I was just saying I got to study the Merkle tree.

00:57:03.973 --> 00:57:04.973
So can you go back to that part where.

00:57:04.973 --> 00:57:08.973
Your audio did like something weird, I think maybe like hit the microphone or
something.

00:57:08.973 --> 00:57:10.973
So it just sounded weird to me for a second.

00:57:10.973 --> 00:57:11.973
Okay.

00:57:11.973 --> 00:57:14.973
So the one thing is that what is a Bitcoin block?

00:57:14.973 --> 00:57:22.973
And it's actually made of this thing called the header, which is only 80 bytes,
which is very small, which is extremely small.

00:57:22.973 --> 00:57:25.973
It's the header plus the vector of transactions.

00:57:25.973 --> 00:57:32.973
So it's very important to separate these two things to have a proper understanding
of what the miner does.

00:57:33.973 --> 00:57:45.973
And so the vector of transactions is hashed to this Merkle tree, which the result is
just this tiny little 32 byte thing, which is 64 characters long.

00:57:45.973 --> 00:57:48.973
And this goes into the header.

00:57:48.973 --> 00:57:57.973
The header only contains a very small number of things, four bytes for the version,
the hash of the previous block, the hash of the Merkle root.

00:57:57.973 --> 00:58:00.973
And you can see how this is laying it out in space.

00:58:00.973 --> 00:58:03.973
So like you have header, header, header, block 1, 2, 3, 4, 5.

00:58:03.973 --> 00:58:10.973
Then beneath the block, theoretically, you have like the vector of transactions and
you have like the Merkle tree, which is like a triangle.

00:58:10.973 --> 00:58:20.973
And so it's a version, previous block, hash Merkle roots, the timestamp, and this
thing called the nonce.

00:58:21.973 --> 00:58:24.973
And these are the only things in the header.

00:58:24.973 --> 00:58:34.973
And every time a single byte or even a single bit of the header changes, the hash of
the block will change.

00:58:34.973 --> 00:58:37.973
And that's the thing that has to be beneath the zeros.

00:58:37.973 --> 00:58:39.973
So I don't know. Maybe this will help.

00:58:39.973 --> 00:58:42.973
But you can imagine a bunch of hashes.

00:58:42.973 --> 00:58:45.973
You know, like what a hash is when I'm talking about a 32 byte hash.

00:58:46.973 --> 00:58:50.973
Imagine hash of block 1, 2, 3, 4, 5 just arrayed in a big line.

00:58:50.973 --> 00:58:53.973
Then beneath that, there's 32 byte hash.

00:58:53.973 --> 00:58:57.973
Beneath that would be like a little box, 80 bytes.

00:58:57.973 --> 00:58:58.973
And it contains all this stuff.

00:58:58.973 --> 00:59:01.973
One of the things it contains is the hash of the previous block.

00:59:01.973 --> 00:59:07.973
So it'll be, if you looked with your eyes diagonally, you would see the same little
thing.

00:59:07.973 --> 00:59:16.973
And then beneath each of those tiny little boxes, there's like a huge box that has
like a huge list of all the transactions that were in that block.

00:59:16.973 --> 00:59:19.973
So this is like a review 101.

00:59:19.973 --> 00:59:27.973
I'm like, well, maybe it's not 101, but I'm just saying this is funny because this
is older stuff.

00:59:27.973 --> 00:59:30.973
If I could still remember it all, but I think I can.

00:59:30.973 --> 00:59:36.973
And so the hash you want to be a very low number, low integer.

00:59:36.973 --> 00:59:40.973
The miners will scramble the nonce.

00:59:40.973 --> 00:59:43.973
They take the block and they increment the nonce.

00:59:43.973 --> 00:59:44.973
Nonce is even named.

00:59:44.973 --> 00:59:48.973
There's a number that is used only once, and that is the origin of its name.

00:59:48.973 --> 00:59:53.973
In fact, so when they do that, it switches the hash to something else.

00:59:53.973 --> 00:59:58.973
So they're kind of shuffling the deck each time to get a new card.

00:59:59.973 --> 01:00:06.973
From like it maybe said like Ace of Spades is like the lowest or something and like
whatever King of Diamonds is the highest.

01:00:06.973 --> 01:00:08.973
I'm just making this up.

01:00:08.973 --> 01:00:13.973
But if you named it one through 52, they're kind of shuffling the deck and drawing
the card.

01:00:13.973 --> 01:00:20.973
And if they don't hit, if they don't get close enough to the top, then it's not a
valid block.

01:00:20.973 --> 01:00:29.973
And so they're hoping to get very, very close, except instead of going from 0 to 52,
it's 0 to 256.

01:00:29.973 --> 01:00:31.973
That's enormous numbers.

01:00:31.973 --> 01:00:35.973
It's a fathomably large deck that is absolutely gargantuan.

01:00:35.973 --> 01:00:36.973
And that's what they do it millions of times.

01:00:36.973 --> 01:00:44.973
Now, in practice, they don't have to increment the nonce so often, although they do,
because the timestamp is also changing every second.

01:00:45.973 --> 01:00:50.973
And the Merkle tree is also changing as new transactions show up in the mempool and
are broadcast on the network.

01:00:50.973 --> 01:00:52.973
So actually everything is changing.

01:00:52.973 --> 01:00:53.973
All those things are changing.

01:00:53.973 --> 01:00:58.973
And in fact, in the Coinbase, the miners scramble this thing called the extra nonce,
and they do all kinds of other stuff, too.

01:00:58.973 --> 01:01:00.973
They also scramble the version bytes.

01:01:00.973 --> 01:01:05.973
They scramble everything to try to go as fast as possible.

01:01:05.973 --> 01:01:23.973
But this is just a different – this is completely different from the node thing
where they are using the CPU to basically make a trivial change to the block that
has nothing to do with the transactions in it and then SHA-256 again.

01:01:23.973 --> 01:01:26.973
So that is what all these ASICs and whatever are doing.

01:01:26.973 --> 01:01:28.973
They are doing that.

01:01:28.973 --> 01:01:36.973
They are doing a completely different thing, which is not really that complicated,
but they have to do it as many times as they possibly can as quickly as possible and
as cheaply as possible.

01:01:36.973 --> 01:01:38.973
And so that's what they are doing.

01:01:38.973 --> 01:01:40.973
That's what they're getting rewarded for?

01:01:40.973 --> 01:01:46.973
If they hit – when they change the block, eventually – the hash will change every
time, remember.

01:01:46.973 --> 01:01:52.973
So eventually, not anytime soon, but if they try – think about it like this way.

01:01:52.973 --> 01:01:57.973
If they try one hash a second, then the hash just sort of is what it is.

01:01:57.973 --> 01:02:10.973
But if they try two hashes a second, if they can make the block, calculate the hash,
then shift the block and calculate it again, probably one of those hashes will start
with a 1 and the other will start with a 0.

01:02:10.973 --> 01:02:15.973
Not necessarily really, but then imagine you can do four hashes at once.

01:02:15.973 --> 01:02:17.973
They're all random.

01:02:17.973 --> 01:02:19.973
The hashes are random and unpredictable.

01:02:20.973 --> 01:02:31.973
So if you can do four at once, probably you've got one that starts with 1, 1,
probably one that starts with 0, 1, probably one that starts with 1, 0, and then you
probably have one that starts with 0, 0.

01:02:31.973 --> 01:02:33.973
Now, of course, I'm just making this up.

01:02:33.973 --> 01:02:36.973
This is not like totally to be relied upon.

01:02:37.973 --> 01:02:47.973
But the point is if you do it more and more and more and more, eventually, you can
guarantee that within the first second you'll have one that starts with five or six
zeros.

01:02:47.973 --> 01:02:56.973
But then the goal is to do it so many times that you eventually – before any of the
other miners, you find one that has enough zeros to count.

01:02:56.973 --> 01:03:00.973
So they're all trying to cheat, but it's a virtuous cycle.

01:03:00.973 --> 01:03:02.973
Is that what I heard basically?

01:03:02.973 --> 01:03:03.973
It's like a race.

01:03:03.973 --> 01:03:05.973
It's like a 400-meter dash.

01:03:05.973 --> 01:03:06.973
Okay.

01:03:06.973 --> 01:03:08.973
So the faster you run, you're more likely to win.

01:03:08.973 --> 01:03:12.973
That's not quite the same because it's not – the 400-meter dash is like a
deterministic physics.

01:03:12.973 --> 01:03:14.973
Yeah, interesting.

01:03:14.973 --> 01:03:21.973
These things are – this is what's called memorylessness property in statistics.

01:03:21.973 --> 01:03:23.973
So the hash does not know.

01:03:23.973 --> 01:03:26.973
You can have two examples.

01:03:26.973 --> 01:03:30.973
So imagine trying to crack a safe, and the safe has just a dial.

01:03:30.973 --> 01:03:32.973
And if you get the dial right, the safe opens.

01:03:33.973 --> 01:03:35.973
It is numbered one through 1,000.

01:03:35.973 --> 01:03:38.973
You try one, and then it doesn't work.

01:03:38.973 --> 01:03:39.973
You pull the lever.

01:03:39.973 --> 01:03:40.973
You try number two.

01:03:40.973 --> 01:03:41.973
It doesn't work.

01:03:41.973 --> 01:03:42.973
Try number three.

01:03:42.973 --> 01:03:51.973
On average, it should take you about 500 tries because 500 is where you've crossed
the point of having tried half of the – you've tried one out of every two.

01:03:51.973 --> 01:03:52.973
Got it.

01:03:52.973 --> 01:03:54.973
On average, it should take you 500 tries.

01:03:54.973 --> 01:03:56.973
That is not how Bitcoin mining works at all.

01:03:56.973 --> 01:03:58.973
It works a different way.

01:03:58.973 --> 01:04:05.973
You have to imagine that there's a long hallway with an infinite number of safes
that are all identical.

01:04:05.973 --> 01:04:07.973
They're all set to random values.

01:04:07.973 --> 01:04:08.973
You don't know which they are.

01:04:08.973 --> 01:04:14.973
And you go up, and you spin the dial randomly, and then you pull – it lands on 37 or
something.

01:04:14.973 --> 01:04:20.973
You pull the lever, and if that doesn't work, you walk to the next safe, and then
you try again.

01:04:20.973 --> 01:04:22.973
That is what Bitcoin mining is like.

01:04:22.973 --> 01:04:26.973
So every single spin is the same.

01:04:26.973 --> 01:04:37.973
But if you can run down and you can just pull as many levers as you can, spin all
the dials, and pull the levers, you're likely to open – to finally hit and open one
of the safes.

01:04:37.973 --> 01:04:43.973
In this case, by the way, it should take you about 1,000 tries because you never
make any – you don't make any progress.

01:04:43.973 --> 01:04:46.973
So you're stuck at one out of 1,000 permanently.

01:04:47.973 --> 01:04:58.973
So you can see after – and the other thing is when you spin the first – in the
previous example where you only have one safe, the first try is one in 1,000.

01:04:58.973 --> 01:05:01.973
But immediately, your odds start to improve.

01:05:01.973 --> 01:05:06.973
And in fact, once you get to the 500th spin, it's more like one in 500.

01:05:06.973 --> 01:05:10.973
By the time you get down to the last two numbers, it's a 50-50.

01:05:10.973 --> 01:05:12.973
It's either going to be 9, 9, 8 or 9, 9, 9.

01:05:12.973 --> 01:05:14.973
Maybe you don't know which one it is.

01:05:14.973 --> 01:05:18.973
At some point, you might feel your luck is so bad, you might skip 9, 9, 8 and try 9,
9, 9.

01:05:18.973 --> 01:05:22.973
You might feel like an idiot for starting at zero or starting at one.

01:05:22.973 --> 01:05:25.973
But the point is now there's only two that it can be.

01:05:25.973 --> 01:05:28.973
So it's actually down to 50-50 at that point.

01:05:28.973 --> 01:05:36.973
And in fact, if you tried them all and there's only one left, then it's a 100%
chance, of course, that that one will be the one that opens the safe.

01:05:36.973 --> 01:05:42.973
This does not happen in the Bitcoin mining example, the memorylessness example where
you're walking down the hallway.

01:05:42.973 --> 01:05:45.973
No matter what, it's always a new thing.

01:05:45.973 --> 01:05:51.973
Even if you just had five that were seven in a row, the next one could be seven or
it could not.

01:05:51.973 --> 01:05:52.973
You have no way of knowing.

01:05:52.973 --> 01:05:55.973
So it's always one in 1,000.

01:05:55.973 --> 01:06:01.973
Okay, so and then for the last five minutes or so, what is the – and you have an
appointment afterwards, I think, as well.

01:06:01.973 --> 01:06:03.973
And if you have to go, let me know.

01:06:03.973 --> 01:06:10.973
But what is the – how do the L2s fit into that, what you just described?

01:06:11.973 --> 01:06:12.973
That's important.

01:06:12.973 --> 01:06:13.973
So we separate nodes and miners.

01:06:13.973 --> 01:06:15.973
So we did like a long digression about miners.

01:06:15.973 --> 01:06:23.973
But the nodes are what process every transaction and store every transaction and
serve it back whenever you ask.

01:06:23.973 --> 01:06:31.973
So when a new person wants to sync a node, it's kind of like BitTorrent where they
download every season of Game of Thrones or something and someone is uploading.

01:06:31.973 --> 01:06:39.973
So this part is crucial because if no one does – if no one mines, then maybe there
won't be any block until someone starts mining again.

01:06:39.973 --> 01:06:46.973
But if no one provides the blockchain data, then no one knows if anything is a
double spend or not, or no one knows.

01:06:46.973 --> 01:06:48.973
This is the whole point of Satoshi's design.

01:06:48.973 --> 01:06:50.973
So no one can spend any money without the blockchain history.

01:06:50.973 --> 01:06:52.973
No one knows who has the coins.

01:06:52.973 --> 01:07:00.973
So for each – so the block size debate was kind of about this, which was like what
are we – what's the rule?

01:07:00.973 --> 01:07:02.973
Like how much are we all obligated?

01:07:02.973 --> 01:07:05.973
It's like you're kind of doing – you and a bunch of friends are going to go on a
trip.

01:07:05.973 --> 01:07:08.973
Like is it going to be – are we going to like Tahiti or something?

01:07:08.973 --> 01:07:10.973
Is it going to be – is it going to cost a fortune?

01:07:10.973 --> 01:07:15.973
But in which case the trip might be better, but everyone is going to have to pay
more money.

01:07:15.973 --> 01:07:23.973
Or are we just going to go to the local bar, in which case it's much easier.

01:07:23.973 --> 01:07:26.973
It's going to cost less, but it might not be as special.

01:07:26.973 --> 01:07:30.973
So the block size is kind of like what are we all – it's a collective issue.

01:07:30.973 --> 01:07:32.973
Like what are we all in for?

01:07:32.973 --> 01:07:40.973
The L2s, as I've said, the way the L2s work is it's sort of saying all of us are
agreed to go in for more stuff.

01:07:40.973 --> 01:07:47.973
We're saying we're going to go to the bar and then some of us, a small subset of us
are going to go to Tahiti

01:07:47.973 --> 01:07:49.973
or we're going to go to Disney World or whatever.

01:07:49.973 --> 01:07:52.973
Take your pick as to what a great vacation is.

01:07:52.973 --> 01:07:54.973
But that's the point.

01:07:55.973 --> 01:08:05.973
The question is – this makes it very easy to transact on L1 and send the coins from
L1 to L2 and transact on L2.

01:08:05.973 --> 01:08:09.973
But what it does not make easy is having the coins come back from L2 to L1.

01:08:09.973 --> 01:08:11.973
The question is how do we do that?

01:08:11.973 --> 01:08:16.973
That is the big sticking problem because remember some of the people are only on L1

01:08:16.973 --> 01:08:20.973
and they have no idea what happened on L2 and they don't want to know.

01:08:21.973 --> 01:08:26.973
Even if we force them to know, that would be bad because that's just forcing them to
go to Tahiti and they didn't want to go.

01:08:26.973 --> 01:08:30.973
So the question is what do we do about that?

01:08:30.973 --> 01:08:40.973
What I do is I bundle all of the withdrawal – the entire activity on the L2
including the withdrawal transactions over a period of months.

01:08:40.973 --> 01:08:47.973
The entirety of the outstanding activity, I bundle that into one transaction that
has one hash.

01:08:47.973 --> 01:08:53.973
And then I basically have the miners on L1 slowly, very slowly approve this hash.

01:08:53.973 --> 01:08:56.973
This is deliberately extremely slow for security reasons.

01:08:56.973 --> 01:08:58.973
It requires everyone to lie.

01:08:58.973 --> 01:09:10.973
It's a little bit like the cave thing, the ZK in a way, where it requires that if
you want to misstate anything that happened on the L2 ever,

01:09:10.973 --> 01:09:13.973
the whole trajectory and the withdrawal period.

01:09:14.973 --> 01:09:22.973
The hash will be different, and the miners will have to basically knowingly endorse
hash A does not equal what it should.

01:09:22.973 --> 01:09:26.973
It should be hash A equals hash A. It will equal something else that's completely
different.

01:09:26.973 --> 01:09:32.973
The point of that is to make it so that the miners are the ones who can basically
slowly approve the withdrawal.

01:09:32.973 --> 01:09:41.973
And the reason why this works is because of something else that was invented by
Satoshi in 2010 called merge mining.

01:09:42.973 --> 01:09:47.973
Where the L1 miners can collect fees from other blockchain networks for free.

01:09:47.973 --> 01:09:54.973
So they get all this cash for free, and we're doing essentially zero additional
work.

01:09:54.973 --> 01:09:57.973
It's so little that it might as well be zero.

01:09:57.973 --> 01:10:00.973
And this is more CPU work.

01:10:00.973 --> 01:10:01.973
This is not any of the hash.

01:10:01.973 --> 01:10:04.973
It's kind of like they open all the safes at once.

01:10:04.973 --> 01:10:07.973
Not only is there a long row of safes.

01:10:08.973 --> 01:10:12.973
So you may be familiar with a Namecoin, which was merge mined with Bitcoin ever
since 2011.

01:10:12.973 --> 01:10:16.973
And you may also be familiar with Dogecoin and Litecoin are merge mined.

01:10:19.973 --> 01:10:24.973
What you actually do under the hood is you actually run Namecoin software, and you
find a Namecoin block.

01:10:24.973 --> 01:10:28.973
But the Namecoin block is built so that part of it is a Bitcoin block.

01:10:28.973 --> 01:10:31.973
So you always find a Namecoin and a Bitcoin block at once.

01:10:31.973 --> 01:10:33.973
And you can do this to an unlimited degree.

01:10:33.973 --> 01:10:37.973
You can actually find blocks on all the L2s at once, like 5, 6, 7.

01:10:37.973 --> 01:10:44.973
And so the logic of this system is this, which is that miners will make a ton of
money from this system.

01:10:44.973 --> 01:10:49.973
A huge, like an enormous amount of money in revenue from this in return for doing
very little work.

01:10:49.973 --> 01:10:53.973
So they would not want to kill the goose that lays the golden egg.

01:10:53.973 --> 01:10:55.973
And that's why it would work.

01:10:55.973 --> 01:11:04.973
Another leg of the logic behind why this is the way it is, is that even if it's very
slow, the withdrawal coming back.

01:11:04.973 --> 01:11:06.973
First of all, the deposits are instant.

01:11:06.973 --> 01:11:09.973
But second of all, there's like a secondary market.

01:11:09.973 --> 01:11:14.973
So you can imagine an example where there's like a casino, and the casino you can
win.

01:11:14.973 --> 01:11:16.973
Some people – the casino is like the L2.

01:11:16.973 --> 01:11:21.973
And you can win and lose your money in different ways here at this casino.

01:11:22.973 --> 01:11:27.973
But then when you want to cash the chips out, that's like the withdrawal from the L2
back to the L1.

01:11:27.973 --> 01:11:32.973
And in my version, it's very, very, very slow and very secure.

01:11:32.973 --> 01:11:40.973
And so you go to like the counter and you've got your chips, and it's going to take
you maybe months to get the chips cashed out, which is like going back to L1.

01:11:40.973 --> 01:11:54.973
However, the reason why this is not a problem is because a secondary market will
develop where there's like a bunch of people in front of the exchange counter at the
casino.

01:11:54.973 --> 01:11:57.973
Like a bunch of people who are just like, listen, I will pay 99.

01:11:57.973 --> 01:11:59.973
I'll give you today.

01:11:59.973 --> 01:12:02.973
Immediately, I'll pay you 99 cents on the dollar.

01:12:02.973 --> 01:12:04.973
I'll buy you out, and then I'll walk.

01:12:04.973 --> 01:12:06.973
These people get like a little yield.

01:12:06.973 --> 01:12:08.973
They'll walk the coins slowly.

01:12:09.973 --> 01:12:13.973
And yield in Bitcoin or yield in the layer 2?

01:12:13.973 --> 01:12:15.973
Well, they would technically buy the L2 coin.

01:12:15.973 --> 01:12:21.973
So like let's say I had 100 coin on the L2, 100 Bitcoin on the L2.

01:12:21.973 --> 01:12:23.973
I swap it.

01:12:23.973 --> 01:12:25.973
I don't want to wait.

01:12:25.973 --> 01:12:33.973
So I go to the person who gives me 99 BTC on L1, and they take my L2 coin.

01:12:33.973 --> 01:12:37.973
Now, they're collecting all the L2 coins they have in a huge pile.

01:12:37.973 --> 01:12:40.973
Like whatever, like 100,000 L2 coin.

01:12:40.973 --> 01:12:47.973
When they walk it across slowly, it will be deleted from the L2, and then they'll
get 100,000 L1.

01:12:47.973 --> 01:12:56.973
So it's allowing equal exchange from the people who do participate in the L2 with
the L1, eventual.

01:12:56.973 --> 01:12:57.973
Right.

01:12:57.973 --> 01:13:04.973
What BIP300 actually does is it keeps track of all the coins that have been sent
from the L1 to the L2,

01:13:04.973 --> 01:13:08.973
and then it pays them to their new owners eventually after a very slow process.

01:13:08.973 --> 01:13:10.973
Okay.

01:13:10.973 --> 01:13:18.973
Well, I think I have reached my limit of understanding abstract concepts for today.

01:13:18.973 --> 01:13:25.973
But I would love to do another one in about three to six to nine months to
understand all the other stuff

01:13:25.973 --> 01:13:30.973
because I feel like with the same level of complexity of just following what
happened with Bitcoin,

01:13:30.973 --> 01:13:34.973
there's a lot of things we can cover, and I have a lot of questions about all those
other things.

01:13:34.973 --> 01:13:36.973
So I would love to do another one.

01:13:36.973 --> 01:13:38.973
Unless there's something else you want to share.

01:13:38.973 --> 01:13:44.973
On LayerTwoLabs.com slash download, you can download the software and play around with
it.

01:13:44.973 --> 01:13:45.973
There's play money.

01:13:45.973 --> 01:13:51.973
We have like a signet, and we are also testing with more realistic tests.

01:13:52.973 --> 01:13:55.973
It makes it much more look like the real Bitcoin network.

01:13:55.973 --> 01:13:59.973
So this is probably a different way to learn.

01:13:59.973 --> 01:14:03.973
You can try out the privacy sidechain and the Thunder sidechain.

01:14:03.973 --> 01:14:07.973
So, yeah, if you go to LayerTwoLabs.com slash download, you can try it out.

01:14:07.973 --> 01:14:11.973
It just says play money, so you won't lose any real Bitcoin or whatever like that.

01:14:11.973 --> 01:14:15.973
You can just try our test network and see the software for yourself,

01:14:15.973 --> 01:14:19.973
which is probably a better way to learn certain things.

01:14:21.973 --> 01:14:23.973
Cool. I'm going to try it.

01:14:23.973 --> 01:14:25.973
Thank you so much.

01:14:25.973 --> 01:14:26.973
Thank you.
