WEBVTT

00:00:00.049 --> 00:00:02.730
So I realized shortly after

00:00:02.930 --> 00:00:04.950
joining that it wasn't

00:00:04.990 --> 00:00:06.532
plugged in or in front of me.

00:00:06.871 --> 00:00:08.833
So there's that.

00:00:08.893 --> 00:00:10.833
It sounded like shit.

00:00:12.335 --> 00:00:13.816
Oh, fantastic.

00:00:14.535 --> 00:00:15.396
Well, it sounds better now.

00:00:15.656 --> 00:00:16.696
It sounded like shit before.

00:00:17.496 --> 00:00:17.736
Yeah.

00:00:17.757 --> 00:00:18.737
Cause it was my headphones.

00:00:20.618 --> 00:00:20.778
Huh?

00:00:21.899 --> 00:00:23.420
Which incidentally, uh,

00:00:23.460 --> 00:00:25.341
you don't appear to be wearing at all,

00:00:26.882 --> 00:00:28.582
which is unusual at this point though,

00:00:28.663 --> 00:00:29.202
which looks great.

00:00:32.969 --> 00:00:33.651
Who turned that on?

00:00:33.670 --> 00:00:38.234
Are you going to turn that off?

00:00:38.914 --> 00:00:39.234
Yeah,

00:00:39.255 --> 00:00:40.777
we seem to be having an evening of

00:00:40.817 --> 00:00:42.898
technical difficulties here.

00:00:44.018 --> 00:00:45.381
My mouse just disconnected,

00:00:45.540 --> 00:00:47.502
so there's that.

00:00:48.862 --> 00:00:50.384
At least you got your

00:00:50.445 --> 00:00:51.706
fucking microphone sorted, eh?

00:01:07.966 --> 00:01:13.390
Hello and welcome to Game of Nodes,

00:01:13.989 --> 00:01:15.311
weekly podcast from

00:01:15.551 --> 00:01:16.992
Independent Validator Teams.

00:01:18.712 --> 00:01:19.912
You keep buying them,

00:01:20.054 --> 00:01:23.695
we'll keep validating them since, wait,

00:01:23.736 --> 00:01:24.676
how many years are we doing this?

00:01:24.736 --> 00:01:27.177
I was about to say since 2021.

00:01:27.358 --> 00:01:30.338
I feel like it's coming on

00:01:30.519 --> 00:01:33.340
three years in March.

00:01:33.561 --> 00:01:35.861
I'd say we've all been a

00:01:35.902 --> 00:01:37.143
good three years in the whole

00:01:37.813 --> 00:01:40.555
When was your first mainnet, Schulze?

00:01:40.614 --> 00:01:41.614
Are you the first one that

00:01:41.635 --> 00:01:45.317
got up on a mainnet?

00:01:46.457 --> 00:01:47.819
For this business?

00:01:47.899 --> 00:01:48.840
Secret Network, which was in 2021.

00:01:49.079 --> 00:01:50.521
Yeah, yeah.

00:01:50.861 --> 00:01:53.281
So you were early 21.

00:01:53.501 --> 00:01:55.504
The rest of us plebs were late 21, right?

00:01:56.965 --> 00:01:57.245
Mid.

00:01:59.566 --> 00:02:01.766
Doge was my first, though, in 2014,

00:02:01.766 --> 00:02:04.009
if that helps at all.

00:02:04.069 --> 00:02:05.370
We all mined a couple of

00:02:05.409 --> 00:02:06.950
blocks of Doge on an old laptop.

00:02:06.971 --> 00:02:07.331
That doesn't...

00:02:09.125 --> 00:02:09.745
Does that count?

00:02:11.246 --> 00:02:12.127
I think it counts.

00:02:12.266 --> 00:02:12.587
Yeah.

00:02:13.668 --> 00:02:14.348
If you sold them,

00:02:14.408 --> 00:02:16.610
it counts because then you

00:02:16.651 --> 00:02:17.831
may or may not have been in profit.

00:02:20.054 --> 00:02:22.276
So somewhere on an old laptop,

00:02:22.295 --> 00:02:23.037
which probably is on these

00:02:23.056 --> 00:02:24.978
shelves behind me, one direction,

00:02:25.679 --> 00:02:26.199
that direction,

00:02:27.520 --> 00:02:29.021
there is a laptop with some Doge on it,

00:02:29.141 --> 00:02:29.801
presumably,

00:02:31.364 --> 00:02:33.185
which I've never checked back in on.

00:02:35.247 --> 00:02:36.228
Probably wasn't very many.

00:02:37.233 --> 00:02:38.813
I should check.

00:02:39.655 --> 00:02:42.257
If it even boosts Windows 7.

00:02:42.677 --> 00:02:44.818
It might be still mining, Doge.

00:02:46.401 --> 00:02:47.381
I don't think so.

00:02:48.002 --> 00:02:49.643
Here's how old that laptop is.

00:02:49.864 --> 00:02:52.286
It was a Sony VAIO laptop.

00:02:55.328 --> 00:02:56.508
Those are owned by what?

00:02:57.270 --> 00:02:58.510
Vizio now or something like that?

00:03:00.549 --> 00:03:01.109
Oh, it could be.

00:03:01.308 --> 00:03:01.549
Yeah.

00:03:02.189 --> 00:03:02.590
I don't know.

00:03:02.669 --> 00:03:04.431
But it was, it was, it was a laptop,

00:03:04.471 --> 00:03:05.031
you know, it was like,

00:03:05.070 --> 00:03:06.451
that was the Sony laptop

00:03:06.472 --> 00:03:09.092
brand for a while in the thoughts that,

00:03:10.152 --> 00:03:11.253
so probably didn't mind too

00:03:11.294 --> 00:03:12.373
many Dogecoin is what I'm saying.

00:03:12.394 --> 00:03:14.375
It was not a, it was not high end.

00:03:15.855 --> 00:03:18.076
They were, they were ultra premium.

00:03:18.137 --> 00:03:18.977
Like they cost a lot of

00:03:19.016 --> 00:03:20.157
fucking money back in the day.

00:03:20.677 --> 00:03:22.519
Yeah, they were, they were all right.

00:03:22.618 --> 00:03:23.278
They were all right, man.

00:03:25.080 --> 00:03:26.540
But I can't,

00:03:27.375 --> 00:03:27.594
Yeah.

00:03:27.655 --> 00:03:27.955
I mean,

00:03:28.436 --> 00:03:30.276
let's not get too deeply into

00:03:30.578 --> 00:03:31.657
phrase laptop history.

00:03:31.938 --> 00:03:33.099
I can't a hundred percent

00:03:33.139 --> 00:03:34.941
remember when I actually got it,

00:03:35.681 --> 00:03:37.682
how much it costs or what the specs were,

00:03:38.764 --> 00:03:39.564
but I remember it being

00:03:39.604 --> 00:03:40.786
better than what I had before,

00:03:41.086 --> 00:03:42.227
which was a cast off.

00:03:43.987 --> 00:03:45.088
Um, but you know, I,

00:03:45.348 --> 00:03:46.310
I equally don't remember it

00:03:46.330 --> 00:03:48.671
being like turbo mega, you know,

00:03:48.711 --> 00:03:49.431
it did still have,

00:03:49.472 --> 00:03:50.393
this was still in the days

00:03:50.432 --> 00:03:52.675
when it had CD drives had like, you know,

00:03:52.694 --> 00:03:53.596
the tray, you know,

00:03:53.616 --> 00:03:54.697
the laptop tray where the

00:03:54.717 --> 00:03:56.318
CD drive comes out the side.

00:03:58.757 --> 00:03:58.896
Well,

00:03:58.917 --> 00:03:59.776
there are a couple of different

00:03:59.836 --> 00:04:01.138
iterations that you had to

00:04:01.478 --> 00:04:02.858
start off with the plug-in ones, right?

00:04:02.877 --> 00:04:03.718
You had to carry it around

00:04:03.778 --> 00:04:04.639
separately and then they

00:04:04.658 --> 00:04:06.058
sort of built them in and then they,

00:04:07.139 --> 00:04:08.539
you know, I had a,

00:04:10.161 --> 00:04:11.920
one of my first MacBook Pros,

00:04:12.420 --> 00:04:14.681
I actually replaced the CD

00:04:15.842 --> 00:04:18.642
tray internally with like a

00:04:18.742 --> 00:04:20.004
caddy that holds an SSD.

00:04:21.576 --> 00:04:24.038
So it was like before

00:04:24.137 --> 00:04:26.338
MacBook pros shipped with SSDs,

00:04:26.379 --> 00:04:27.300
they had a spinner in them.

00:04:28.060 --> 00:04:29.261
So I took out the,

00:04:29.560 --> 00:04:31.242
the CD drive and put a

00:04:31.262 --> 00:04:33.444
little tray in there that holds an SSD.

00:04:33.483 --> 00:04:35.725
So I could have SSD on that

00:04:35.845 --> 00:04:37.867
side of port and then, um,

00:04:38.487 --> 00:04:41.749
use the other spinner just for more, uh,

00:04:43.209 --> 00:04:44.190
long-term storage stuff.

00:04:45.230 --> 00:04:46.750
Do you remember whenever

00:04:47.511 --> 00:04:50.492
SSDs came out and I used to

00:04:50.512 --> 00:04:52.552
show my friends how fast my laptop would,

00:04:52.713 --> 00:04:53.833
would spin up after that?

00:04:54.093 --> 00:04:55.372
Cause you know, before SSDs,

00:04:55.434 --> 00:04:57.134
it was like two minutes and

00:04:57.153 --> 00:04:58.194
then SSD brought it down to

00:04:58.233 --> 00:05:00.035
like 20 seconds.

00:05:00.055 --> 00:05:00.935
And then NVMe of course

00:05:00.975 --> 00:05:02.776
takes it a second and a half to spin up,

00:05:03.216 --> 00:05:04.437
but people would lose their

00:05:04.476 --> 00:05:05.536
mind whenever I'd show them like,

00:05:05.557 --> 00:05:05.896
hold on.

00:05:05.916 --> 00:05:06.216
All right,

00:05:06.237 --> 00:05:07.237
just stay here and wait for it

00:05:07.257 --> 00:05:07.557
to turn on.

00:05:07.577 --> 00:05:08.697
And they'd be like, I don't have coffee.

00:05:08.718 --> 00:05:10.459
Like, what do you want me to wait for?

00:05:10.478 --> 00:05:11.098
And then it would be on.

00:05:11.119 --> 00:05:12.579
And they'd be like, how,

00:05:12.838 --> 00:05:13.540
how did that happen?

00:05:13.600 --> 00:05:14.079
What did you do?

00:05:17.084 --> 00:05:24.069
I remember installing Mac OS,

00:05:24.089 --> 00:05:25.971
whatever it was at that time,

00:05:25.990 --> 00:05:26.851
whatever version it was.

00:05:27.732 --> 00:05:31.935
And the installation process

00:05:32.016 --> 00:05:35.278
was just amazingly fast.

00:05:36.920 --> 00:05:38.019
And I was just like,

00:05:39.120 --> 00:05:40.903
did I just step into a

00:05:40.942 --> 00:05:43.464
different technological era?

00:05:44.459 --> 00:05:44.720
Yes.

00:05:44.980 --> 00:05:45.521
Yes, I did.

00:05:46.641 --> 00:05:47.903
Rama's asking who's rocking

00:05:47.923 --> 00:05:48.802
the background noise.

00:05:48.862 --> 00:05:49.704
That would be me.

00:05:50.043 --> 00:05:52.865
My very courteous neighbors

00:05:53.166 --> 00:05:54.327
are constructing early in

00:05:54.367 --> 00:05:54.968
the morning again.

00:05:55.148 --> 00:05:55.528
Thank you.

00:05:56.488 --> 00:05:56.928
Beautiful.

00:05:57.290 --> 00:06:00.072
So I'll say who's running a circular saw.

00:06:00.512 --> 00:06:03.754
In fact, is a circular saw or something.

00:06:04.454 --> 00:06:07.737
I would say it could be a circular saw.

00:06:08.117 --> 00:06:09.399
It might actually be a planer.

00:06:10.952 --> 00:06:11.694
Somebody was telling me the

00:06:11.713 --> 00:06:14.435
other day that because

00:06:14.656 --> 00:06:16.177
there's been a lot more bike thefts,

00:06:16.257 --> 00:06:19.581
what with, you know, recession or, well,

00:06:19.661 --> 00:06:20.862
cost of living slash

00:06:21.081 --> 00:06:21.882
inflation or whatever.

00:06:23.785 --> 00:06:25.766
But apparently, so obviously angle grinder,

00:06:26.266 --> 00:06:27.829
your classic way for

00:06:27.869 --> 00:06:30.630
defeating an expensive bike lock.

00:06:32.353 --> 00:06:33.274
But apparently they're very,

00:06:33.713 --> 00:06:35.615
most angle grinder, is it,

00:06:36.612 --> 00:06:38.634
a blade technically the the

00:06:38.735 --> 00:06:40.516
disc part would you call

00:06:40.536 --> 00:06:41.757
that a grinding disc

00:06:42.257 --> 00:06:43.517
grinding disc thing

00:06:43.538 --> 00:06:45.459
apparently most of them are

00:06:45.519 --> 00:06:46.920
very susceptible to even a

00:06:47.040 --> 00:06:48.581
small amount of ceramic

00:06:48.600 --> 00:06:49.822
they don't like it very

00:06:49.901 --> 00:06:51.622
much and so if you have

00:06:51.682 --> 00:06:53.043
like um essentially just

00:06:53.084 --> 00:06:54.964
like really thin uh ceramic

00:06:55.024 --> 00:06:57.547
layer in like a laminated

00:06:57.646 --> 00:07:00.088
bike lock like a layer of I

00:07:00.108 --> 00:07:01.209
guess a layer of metal a

00:07:02.129 --> 00:07:03.250
plastic lamination a

00:07:03.670 --> 00:07:04.812
ceramic lamination and

00:07:05.622 --> 00:07:06.944
then a rubber outer layer

00:07:07.043 --> 00:07:08.326
apparently it could really

00:07:08.386 --> 00:07:09.867
really with an angle

00:07:09.887 --> 00:07:12.870
grinder um really okay

00:07:12.930 --> 00:07:13.850
citation needed on that

00:07:13.891 --> 00:07:15.012
yeah a friend of mine who's

00:07:15.672 --> 00:07:17.033
I feel like what was what

00:07:17.053 --> 00:07:18.475
their degree I feel like

00:07:18.514 --> 00:07:20.297
they were their degree 15

00:07:20.297 --> 00:07:21.057
years ago whatever was

00:07:21.117 --> 00:07:22.478
science so I kind of defer

00:07:22.519 --> 00:07:24.199
to them on on subjects of

00:07:24.240 --> 00:07:25.221
this they were like ah yes

00:07:25.401 --> 00:07:26.723
ceramic that's the thing

00:07:26.762 --> 00:07:28.944
you need in your your bike

00:07:28.964 --> 00:07:31.266
they they do have all different kinds of

00:07:31.829 --> 00:07:32.629
Like blades, though,

00:07:32.649 --> 00:07:34.091
you can get diamond blades,

00:07:34.130 --> 00:07:35.511
which would make short work

00:07:35.591 --> 00:07:37.312
of a ceramic item.

00:07:37.773 --> 00:07:38.333
Yeah, I mean,

00:07:38.353 --> 00:07:39.213
it kind of seemed like if you

00:07:39.233 --> 00:07:41.314
were very serious about nicking bikes,

00:07:41.375 --> 00:07:42.415
you'd probably just have

00:07:42.576 --> 00:07:43.697
whatever the most expensive

00:07:43.737 --> 00:07:45.398
blade is because you want

00:07:45.437 --> 00:07:47.238
to be pulling up your van,

00:07:47.658 --> 00:07:49.000
knocking through the bike lock,

00:07:49.600 --> 00:07:51.242
bike in the back of the van and off.

00:07:51.581 --> 00:07:51.922
Because, I mean,

00:07:51.942 --> 00:07:53.182
it's happening in the centre of a city,

00:07:53.262 --> 00:07:53.463
right?

00:07:53.523 --> 00:07:54.384
It's not like there aren't

00:07:54.803 --> 00:07:57.105
the odd plod around and whatnot.

00:07:57.786 --> 00:07:58.086
I mean,

00:07:58.125 --> 00:07:59.607
from the videos I've seen recently,

00:08:00.396 --> 00:08:01.177
don't look like anyone

00:08:01.216 --> 00:08:02.418
really gives a fuck anyway

00:08:02.478 --> 00:08:03.298
so you could probably spend

00:08:03.338 --> 00:08:04.259
a good half an hour if you

00:08:04.278 --> 00:08:07.382
needed to yeah I did have a

00:08:07.422 --> 00:08:08.963
friend actually who's uh

00:08:09.744 --> 00:08:10.845
whose dad was a machine

00:08:10.904 --> 00:08:13.247
shop um guy and he

00:08:13.406 --> 00:08:15.728
accidentally locked his or

00:08:16.288 --> 00:08:16.910
he had that thing where

00:08:16.949 --> 00:08:17.690
somebody else locks their

00:08:17.730 --> 00:08:21.293
bike to yours um and so he

00:08:21.334 --> 00:08:22.595
borrowed an angle grinder

00:08:23.744 --> 00:08:25.725
Took it on the bus into the

00:08:25.766 --> 00:08:28.990
city and then just angle

00:08:29.050 --> 00:08:31.211
grinded the lock off his own bike.

00:08:32.092 --> 00:08:34.054
And a policeman did come over and was like,

00:08:34.475 --> 00:08:36.697
um, what are you doing?

00:08:36.878 --> 00:08:38.438
And he's like, this is my bike.

00:08:38.479 --> 00:08:40.140
Somebody else has locked their bike to it.

00:08:41.602 --> 00:08:42.423
And they're like, hmm.

00:08:44.417 --> 00:08:45.977
You kind of seem like,

00:08:46.918 --> 00:08:48.821
you kind of don't seem like a Scali,

00:08:49.260 --> 00:08:49.981
and this doesn't look like

00:08:50.022 --> 00:08:51.143
a particularly expensive bike,

00:08:51.202 --> 00:08:53.024
and you seem very intent on this one bike,

00:08:53.043 --> 00:08:54.284
so we're going to let it slide.

00:08:55.285 --> 00:08:56.346
They just walked off.

00:08:56.366 --> 00:08:58.109
They were like, yeah, fair enough.

00:08:58.269 --> 00:08:59.289
We believe that's your bike.

00:08:59.549 --> 00:09:00.431
Off you go.

00:09:01.692 --> 00:09:04.073
Whatever happened to police on the beat?

00:09:04.734 --> 00:09:06.096
I was walking around this

00:09:06.135 --> 00:09:08.457
suburb the other day in Melbourne,

00:09:08.738 --> 00:09:10.658
and it occurred to me,

00:09:11.764 --> 00:09:14.586
that I haven't seen a cop in

00:09:14.647 --> 00:09:17.950
like years on the street

00:09:19.291 --> 00:09:20.331
budget and there is

00:09:20.792 --> 00:09:23.173
graffiti everywhere yeah

00:09:23.234 --> 00:09:24.254
like there's no one you

00:09:24.274 --> 00:09:25.657
know knocking heads when

00:09:25.697 --> 00:09:26.878
you're spraying on the side

00:09:26.898 --> 00:09:28.759
of buildings and there's

00:09:28.840 --> 00:09:29.840
there's some crazy stat in

00:09:29.880 --> 00:09:31.261
this country about how like

00:09:31.461 --> 00:09:32.503
burglaries and things are

00:09:32.523 --> 00:09:34.144
just they're just not even

00:09:34.304 --> 00:09:35.725
investigated anymore like

00:09:36.166 --> 00:09:37.187
the the police just

00:09:38.429 --> 00:09:39.490
don't have the capacity or

00:09:39.530 --> 00:09:40.150
can't be fucked.

00:09:40.410 --> 00:09:40.910
One of the two.

00:09:40.931 --> 00:09:42.312
I don't know if that's the

00:09:42.351 --> 00:09:43.111
same in Australia.

00:09:43.152 --> 00:09:44.072
I thought you guys were like

00:09:44.113 --> 00:09:45.133
pretty recession proof.

00:09:45.153 --> 00:09:47.754
So you still probably funded, you know,

00:09:47.793 --> 00:09:50.315
like investigating

00:09:50.375 --> 00:09:51.836
burglaries or some shit, but.

00:09:52.697 --> 00:09:54.277
Well, yeah,

00:09:54.336 --> 00:09:56.018
like you can call them and they do stuff,

00:09:56.138 --> 00:09:58.239
but yeah, I don't know.

00:09:58.259 --> 00:09:58.499
I just,

00:09:59.099 --> 00:10:00.440
I feel like they should be out on

00:10:00.460 --> 00:10:00.879
the street,

00:10:00.899 --> 00:10:03.942
just busting shit when people like,

00:10:04.101 --> 00:10:04.341
you know,

00:10:04.926 --> 00:10:05.525
Are you sure they're not

00:10:05.567 --> 00:10:06.947
walking around whacking

00:10:06.988 --> 00:10:07.947
people with the nightstick

00:10:08.028 --> 00:10:08.609
for doing shit?

00:10:09.009 --> 00:10:10.210
Are they not just like busy

00:10:10.269 --> 00:10:11.510
investigating financial

00:10:11.530 --> 00:10:12.471
crime on the blockchain?

00:10:14.533 --> 00:10:16.054
Oh, yeah.

00:10:16.235 --> 00:10:16.615
I mean,

00:10:17.796 --> 00:10:19.096
if you were to go down to the

00:10:19.596 --> 00:10:20.298
police station,

00:10:20.317 --> 00:10:24.280
I'm sure there is just a bunch of highly,

00:10:24.761 --> 00:10:26.363
highly skilled police with

00:10:26.442 --> 00:10:28.224
pocket protectors doing God's work.

00:10:28.965 --> 00:10:29.105
Yeah.

00:10:29.125 --> 00:10:30.745
I mean, they're not, they're not walking.

00:10:32.006 --> 00:10:33.528
They're not walking the boomer beat.

00:10:33.849 --> 00:10:34.009
No.

00:10:34.860 --> 00:10:36.582
They're walking the meta beat.

00:10:38.063 --> 00:10:39.384
Like, it kind of shits me, though,

00:10:39.404 --> 00:10:42.268
because there's just people

00:10:42.347 --> 00:10:45.149
out here with spray cans, you know,

00:10:45.470 --> 00:10:47.631
tagging, like,

00:10:48.673 --> 00:10:49.913
historic buildings and shit.

00:10:49.953 --> 00:10:50.835
It's just kind of annoying.

00:10:52.015 --> 00:10:53.677
Like, I don't want to see you fucking...

00:10:54.745 --> 00:10:56.225
I just don't want to see your life.

00:10:56.245 --> 00:10:57.466
These kids, these youths,

00:10:58.028 --> 00:11:00.269
they're spraying this paint

00:11:00.369 --> 00:11:02.530
from a can and they're

00:11:02.571 --> 00:11:03.951
riding these boards with

00:11:04.011 --> 00:11:06.333
wheels and playing this

00:11:06.413 --> 00:11:07.774
music by this band called

00:11:07.855 --> 00:11:09.855
Fu Manchu and it's all very annoying.

00:11:10.517 --> 00:11:11.437
They just keep saying

00:11:11.518 --> 00:11:15.019
radical and flipping the bird to the man.

00:11:15.039 --> 00:11:17.201
I might not mind if...

00:11:19.133 --> 00:11:20.452
what they were painting was

00:11:20.533 --> 00:11:22.653
like you know a banksy or

00:11:22.673 --> 00:11:24.215
something but they're just

00:11:24.315 --> 00:11:25.914
scribbling their name or

00:11:25.955 --> 00:11:27.575
something it's illegal

00:11:27.676 --> 00:11:28.696
we're gonna start somewhere

00:11:28.755 --> 00:11:29.456
now you know what you're

00:11:29.475 --> 00:11:31.096
missing a trick right you

00:11:31.136 --> 00:11:33.157
should be going up to them

00:11:33.197 --> 00:11:34.758
and saying like do you want

00:11:34.778 --> 00:11:36.738
to earn some real money and

00:11:36.778 --> 00:11:38.599
buy real money I mean coins

00:11:40.048 --> 00:11:40.908
How about you?

00:11:41.009 --> 00:11:43.091
Put my crayon everywhere.

00:11:43.270 --> 00:11:43.591
Yeah.

00:11:43.630 --> 00:11:44.691
Put fucking big balls

00:11:44.730 --> 00:11:46.231
blockchain up on this building.

00:11:46.491 --> 00:11:48.533
That historic building built

00:11:48.533 --> 00:11:49.514
230 years ago.

00:11:49.734 --> 00:11:51.053
All wood construction.

00:11:51.595 --> 00:11:54.076
Very susceptible to, you know,

00:11:54.196 --> 00:11:55.836
hard enamel spray paint.

00:11:56.917 --> 00:11:58.557
Get my logo up on that shit

00:11:58.597 --> 00:11:59.578
and damn the damage.

00:12:00.078 --> 00:12:01.759
I'll pay for it with shit coins.

00:12:01.820 --> 00:12:02.500
That's what I'll do.

00:12:02.899 --> 00:12:04.181
They come after me, the cops.

00:12:04.660 --> 00:12:06.241
I'll just say, put it on my tab.

00:12:08.072 --> 00:12:09.152
spread over that banksy

00:12:09.192 --> 00:12:10.873
right there yeah just spray

00:12:10.893 --> 00:12:12.212
straight over that banksy

00:12:12.232 --> 00:12:14.033
that's yesterday's news the

00:12:14.072 --> 00:12:15.793
future's now old man and

00:12:15.813 --> 00:12:16.714
the future's big balls

00:12:16.754 --> 00:12:20.215
blockchain dot com forward

00:12:20.235 --> 00:12:21.695
slash null dot php

00:12:23.115 --> 00:12:28.076
trademarked um there is

00:12:28.177 --> 00:12:29.576
like in in melbourne there

00:12:29.616 --> 00:12:31.417
is a lot of pretty good

00:12:31.456 --> 00:12:33.577
graffiti especially around the cities

00:12:36.041 --> 00:12:38.043
Like, I'm talking about graffiti art.

00:12:39.224 --> 00:12:42.125
There's a lot of good murals

00:12:42.186 --> 00:12:42.866
and stuff around.

00:12:43.788 --> 00:12:46.149
It's just these fucking tags.

00:12:48.490 --> 00:12:49.793
They're just utterly ridiculous.

00:12:50.413 --> 00:12:52.414
Welcome to Noel's Boomer Hour.

00:12:53.475 --> 00:12:54.416
Yeah, there's a really good one.

00:12:54.797 --> 00:12:56.217
I can't remember his name.

00:12:56.437 --> 00:12:58.139
But there's one, like, literally,

00:12:58.320 --> 00:13:00.400
we're close to the train station here.

00:13:01.182 --> 00:13:02.322
And just around the corner...

00:13:04.187 --> 00:13:05.008
Right by the pub,

00:13:05.508 --> 00:13:08.171
there was a really nice one

00:13:08.431 --> 00:13:10.613
of Kim Jong-un,

00:13:12.134 --> 00:13:15.177
but some other twat fucking

00:13:15.217 --> 00:13:16.499
come and sprayed over the top of it.

00:13:16.538 --> 00:13:19.100
So fuckers.

00:13:19.902 --> 00:13:20.962
I'm trying to find the artist.

00:13:20.982 --> 00:13:22.224
It's really good.

00:13:22.464 --> 00:13:23.524
He's got quite a lot of them

00:13:23.565 --> 00:13:24.485
around Melbourne and Sydney.

00:13:24.986 --> 00:13:26.347
If it's not an NFT, who cares?

00:13:26.408 --> 00:13:27.208
It won't live forever.

00:13:27.229 --> 00:13:28.129
It'll be forgotten.

00:13:29.423 --> 00:13:31.083
i think these are nfts as

00:13:31.124 --> 00:13:32.684
well the nfts are timeless

00:13:32.725 --> 00:13:34.166
now you know this all art

00:13:34.245 --> 00:13:35.525
is ephemeral except for

00:13:35.647 --> 00:13:37.047
nfts which are inherently

00:13:37.106 --> 00:13:38.148
timeless and therefore more

00:13:38.207 --> 00:13:40.568
valuable I i think these

00:13:40.688 --> 00:13:43.471
ones are like nft arised

00:13:44.110 --> 00:13:46.932
after a completion before

00:13:46.972 --> 00:13:47.932
they get sprayed over by

00:13:48.073 --> 00:13:50.674
are they are they sprayed

00:13:50.735 --> 00:13:52.035
over by the same artist so

00:13:52.076 --> 00:13:53.176
that only the nft

00:13:53.255 --> 00:13:54.557
representation can remain

00:13:54.576 --> 00:13:56.357
they come back and they

00:13:56.398 --> 00:13:57.458
burn it they're like

00:13:58.870 --> 00:14:00.172
at the physical artifacts.

00:14:01.072 --> 00:14:03.153
You know, like, you know,

00:14:03.173 --> 00:14:04.674
the bubble writing of the nineties,

00:14:04.975 --> 00:14:08.157
like the, the graffiti bubble writing.

00:14:08.177 --> 00:14:09.597
Yeah.

00:14:09.638 --> 00:14:10.239
It was, it was,

00:14:10.839 --> 00:14:13.360
it was bubble written over by like,

00:14:13.500 --> 00:14:15.863
I don't know, Jerry or something.

00:14:16.202 --> 00:14:17.604
Probably by the Zion guys.

00:14:17.683 --> 00:14:17.903
Right.

00:14:17.923 --> 00:14:21.466
I should just, I should put,

00:14:21.525 --> 00:14:23.388
should put this on like, you know,

00:14:23.868 --> 00:14:25.448
mobile mode and walk

00:14:25.489 --> 00:14:26.750
outside and give you a tour

00:14:26.789 --> 00:14:27.410
of the neighborhoods.

00:14:27.471 --> 00:14:27.910
Graffiti graffiti.

00:14:28.765 --> 00:14:31.567
my critiques on each hey you

00:14:31.606 --> 00:14:32.366
know we could do it we

00:14:32.407 --> 00:14:33.147
could do an outside

00:14:33.187 --> 00:14:35.888
broadcast van version null

00:14:35.947 --> 00:14:37.447
on the null null's

00:14:37.488 --> 00:14:39.188
walkabout not on the range

00:14:40.149 --> 00:14:41.409
the null ranger I don't

00:14:41.429 --> 00:14:42.470
know something like that

00:14:43.230 --> 00:14:45.091
null on the beat take out

00:14:45.150 --> 00:14:47.551
my nightstick yeah it could

00:14:47.571 --> 00:14:49.172
be like people might get

00:14:49.392 --> 00:14:50.192
people might get the wrong

00:14:50.231 --> 00:14:53.852
idea of that no no on the beat uh

00:14:56.296 --> 00:14:58.616
Yeah, they probably would get it.

00:14:58.636 --> 00:15:01.837
I was about to say, no,

00:15:02.077 --> 00:15:03.839
it does sound very strongly

00:15:03.899 --> 00:15:04.639
like masturbation.

00:15:05.038 --> 00:15:06.779
It sounds like masturbation, doesn't it?

00:15:09.200 --> 00:15:13.841
So anyway, what have you been up to?

00:15:13.861 --> 00:15:14.902
I was talking shortly before

00:15:14.942 --> 00:15:16.982
the show about what's

00:15:17.043 --> 00:15:19.283
occurring during this bull market.

00:15:19.303 --> 00:15:19.744
I have spent like...

00:15:23.702 --> 00:15:25.943
I've spent the last week re

00:15:26.244 --> 00:15:28.104
reconfiguring a bunch of, um,

00:15:28.264 --> 00:15:32.345
Ansible and moving just

00:15:32.664 --> 00:15:34.505
shit loads of nodes to new servers,

00:15:34.566 --> 00:15:38.126
because after a lot of my

00:15:38.167 --> 00:15:39.126
servers are sort of coming

00:15:39.226 --> 00:15:42.207
up on a year of use, um,

00:15:43.067 --> 00:15:44.067
from when I moved a lot of

00:15:44.107 --> 00:15:46.408
things after the last bull market to, um,

00:15:47.188 --> 00:15:50.029
more economical, uh, servers and.

00:15:51.070 --> 00:15:53.251
the hard drives are trashed

00:15:53.991 --> 00:15:57.215
so they are well over 100

00:15:57.215 --> 00:16:00.697
um utilization and I don't

00:16:00.738 --> 00:16:03.099
mean space I mean like you

00:16:03.119 --> 00:16:04.780
know the nand flashes wore

00:16:04.801 --> 00:16:08.744
the out so um yeah been

00:16:08.803 --> 00:16:11.145
finding new providers new

00:16:11.186 --> 00:16:12.927
servers trying to find all

00:16:12.966 --> 00:16:13.527
those 7950x 3ds hidden

00:16:13.547 --> 00:16:14.447
around the place and uh

00:16:18.668 --> 00:16:19.528
moving stuff around,

00:16:19.568 --> 00:16:20.889
testing out some new providers.

00:16:21.470 --> 00:16:23.530
I can tell you that Contabo

00:16:25.191 --> 00:16:27.111
do not have good hard drives.

00:16:29.472 --> 00:16:30.273
I just can't believe you

00:16:30.293 --> 00:16:31.232
went and tried them again.

00:16:31.373 --> 00:16:33.953
Like, what were you thinking?

00:16:35.075 --> 00:16:38.056
Well, they... So, it is hard to find...

00:16:40.631 --> 00:16:42.793
So I don't know how familiar

00:16:42.813 --> 00:16:43.654
our audience is,

00:16:43.754 --> 00:16:45.096
probably not familiar at all,

00:16:45.356 --> 00:16:47.479
with some of the

00:16:47.519 --> 00:16:49.360
requirements of these faster networks.

00:16:49.681 --> 00:16:50.861
They tend to perform better

00:16:51.062 --> 00:16:54.705
on faster threads than slow threads.

00:16:55.166 --> 00:16:56.567
So you can have shitloads of

00:16:56.667 --> 00:16:58.129
threads or CPUs,

00:16:58.889 --> 00:17:01.432
and it won't necessarily

00:17:02.273 --> 00:17:04.193
yield a good result if you have...

00:17:05.204 --> 00:17:06.786
fewer threads that are faster,

00:17:06.826 --> 00:17:09.586
you can get a better result

00:17:10.027 --> 00:17:12.468
in terms of missed blocks.

00:17:12.488 --> 00:17:16.130
So the hunt continues for fast CPUs.

00:17:16.890 --> 00:17:23.492
And unfortunately, around APAC,

00:17:24.333 --> 00:17:26.273
there's not a lot on offer

00:17:26.634 --> 00:17:28.974
in terms of Ryzen CPUs and stuff.

00:17:29.795 --> 00:17:31.536
And I just came across Contabo.

00:17:31.776 --> 00:17:32.115
They had a 7900X.

00:17:34.010 --> 00:17:36.853
with a couple of options for

00:17:36.932 --> 00:17:38.013
hard drive sizes.

00:17:39.054 --> 00:17:40.134
It should have been a pretty

00:17:40.154 --> 00:17:45.019
good indicator that they had.

00:17:45.038 --> 00:17:46.700
They were denominated in the thousands,

00:17:46.900 --> 00:17:51.863
not like 960, 1800.

00:17:51.863 --> 00:17:53.604
They were rounded off to the thousands,

00:17:54.105 --> 00:17:56.226
which generally tells you

00:17:56.246 --> 00:17:57.446
that it's a consumer drive,

00:17:57.547 --> 00:17:59.709
not a enterprise drive.

00:18:00.469 --> 00:18:01.829
So anyway, they had...

00:18:03.714 --> 00:18:04.875
Like the model has rounded

00:18:04.935 --> 00:18:05.715
off to the thousands or

00:18:05.736 --> 00:18:06.496
what are you saying there?

00:18:07.336 --> 00:18:08.837
The capacity when the

00:18:08.857 --> 00:18:10.939
capacity is rounded off to the thousands,

00:18:11.019 --> 00:18:13.140
it's usually a consumer drive, you know,

00:18:13.160 --> 00:18:14.701
nice and easy to digest.

00:18:15.421 --> 00:18:18.563
So instead of the actual 1.92 or whatever.

00:18:19.222 --> 00:18:20.044
Yeah, exactly.

00:18:20.183 --> 00:18:21.124
Or a thousand instead of

00:18:21.163 --> 00:18:24.665
nine 60 or 4,000 instead of three 82.

00:18:24.665 --> 00:18:26.307
So, you know, when they're,

00:18:26.586 --> 00:18:28.847
when they're on the, the real numbers,

00:18:29.067 --> 00:18:29.749
it's usually.

00:18:30.992 --> 00:18:31.773
most of the time an

00:18:31.794 --> 00:18:32.794
enterprise drive of some

00:18:32.814 --> 00:18:34.536
description not necessarily

00:18:34.596 --> 00:18:36.116
always a good one but you

00:18:36.156 --> 00:18:37.198
know I never thought about

00:18:37.238 --> 00:18:38.739
that because I've primarily

00:18:38.759 --> 00:18:39.940
been a cloud fucking weenie

00:18:39.980 --> 00:18:41.059
for the last few years and

00:18:41.079 --> 00:18:42.401
you just ask for how much

00:18:42.441 --> 00:18:43.821
space you want and you just

00:18:43.862 --> 00:18:47.865
go two two is what I want

00:18:48.326 --> 00:18:52.368
megabytes no terabytes is

00:18:52.429 --> 00:18:54.589
what I would like yes

00:18:56.121 --> 00:18:58.842
So here at Kingnodes,

00:18:58.862 --> 00:18:59.782
we've also been building

00:18:59.843 --> 00:19:00.663
our own shit lately,

00:19:00.702 --> 00:19:02.022
which has been a bit of an adventure.

00:19:02.723 --> 00:19:06.505
And man, you pay for good hard drives.

00:19:06.585 --> 00:19:08.465
Like it is not a trivial thing.

00:19:09.185 --> 00:19:10.666
You can stick a consumer one

00:19:10.707 --> 00:19:11.968
terabyte drive in there and

00:19:12.167 --> 00:19:13.448
get out of it for like, you know,

00:19:13.488 --> 00:19:14.067
a hundred bucks.

00:19:15.068 --> 00:19:17.289
Whereas if you stick like an

00:19:17.390 --> 00:19:19.590
enterprise one terabyte drive in there,

00:19:20.471 --> 00:19:21.431
you're several hundreds

00:19:21.510 --> 00:19:22.811
more for a good one.

00:19:23.347 --> 00:19:24.107
it all comes down to the

00:19:24.167 --> 00:19:25.268
right endurance like how

00:19:25.288 --> 00:19:26.348
many times you can rewrite

00:19:26.368 --> 00:19:27.989
the drive and how how low

00:19:28.009 --> 00:19:30.750
the latency is um we've

00:19:30.769 --> 00:19:31.410
struck a pretty good

00:19:31.450 --> 00:19:34.150
balance um for our archive

00:19:34.910 --> 00:19:36.270
nodes of what we use in

00:19:36.310 --> 00:19:38.471
those but the drives are

00:19:38.530 --> 00:19:40.832
expensive um but they can

00:19:40.852 --> 00:19:41.711
be rewritten a bunch of

00:19:41.731 --> 00:19:44.951
times so um I haven't found

00:19:44.991 --> 00:19:48.313
like any any large uh

00:19:49.212 --> 00:19:50.573
drives with like a right

00:19:50.613 --> 00:19:52.953
endurance of three or higher so

00:19:54.451 --> 00:19:56.932
hunt continues well I'm

00:19:56.972 --> 00:19:57.853
talking about you know

00:19:57.893 --> 00:19:58.534
drives where you're not

00:19:58.574 --> 00:20:00.334
dropping 10 grand on a 15

00:20:00.334 --> 00:20:01.474
terabyte drive or something

00:20:03.276 --> 00:20:05.977
that's a thing really oh

00:20:06.017 --> 00:20:07.336
yeah yeah there's some

00:20:07.517 --> 00:20:09.377
expensive drives out there

00:20:09.938 --> 00:20:12.019
the um the ones we use in

00:20:12.138 --> 00:20:17.020
our archives are about I'm

00:20:17.040 --> 00:20:19.281
gonna say 1300 us I think

00:20:19.942 --> 00:20:21.982
per drive for what capacity

00:20:23.243 --> 00:20:24.986
15.36 terabytes.

00:20:25.948 --> 00:20:26.167
Wow.

00:20:27.128 --> 00:20:27.348
Wow.

00:20:27.368 --> 00:20:28.510
Those are hardcore.

00:20:29.711 --> 00:20:30.752
Yeah.

00:20:31.374 --> 00:20:32.394
Our first machine we built

00:20:32.414 --> 00:20:37.320
has four of them in it with ZFS.

00:20:37.340 --> 00:20:39.884
But the thing with ZFS is

00:20:39.903 --> 00:20:40.423
you don't get any...

00:20:42.886 --> 00:20:44.207
like multiplication of

00:20:44.267 --> 00:20:46.127
performance so for example

00:20:46.147 --> 00:20:47.528
if you put all those in in

00:20:47.608 --> 00:20:48.749
raid zero you would end up

00:20:48.788 --> 00:20:49.808
with like you know

00:20:49.848 --> 00:20:50.970
performance multiplication

00:20:50.990 --> 00:20:52.990
you'd get basically four

00:20:53.029 --> 00:20:54.211
times the iops because of

00:20:54.250 --> 00:20:56.751
the striping um and the

00:20:56.811 --> 00:20:58.692
right speed you know you'd

00:20:58.711 --> 00:21:00.553
be able to max out a 100

00:21:00.553 --> 00:21:01.432
gig network or something on

00:21:01.452 --> 00:21:03.253
the on the right speed but

00:21:03.334 --> 00:21:06.275
because we use zfs on archives um

00:21:07.929 --> 00:21:09.190
But in practice, that shit doesn't matter,

00:21:09.230 --> 00:21:09.509
does it?

00:21:09.569 --> 00:21:11.432
Because although the

00:21:11.612 --> 00:21:13.013
theoretical right of the

00:21:13.054 --> 00:21:14.894
drives would be higher,

00:21:15.035 --> 00:21:16.257
they do depend on what's

00:21:16.297 --> 00:21:18.198
doing the writing to the file system,

00:21:18.258 --> 00:21:18.439
right?

00:21:21.000 --> 00:21:21.260
So...

00:21:22.381 --> 00:21:25.423
Because almost all of the

00:21:25.544 --> 00:21:26.464
programs you're going to be

00:21:26.585 --> 00:21:28.267
running are going to do

00:21:28.988 --> 00:21:30.528
like their bottleneck of

00:21:30.548 --> 00:21:31.710
write speed is going to be

00:21:31.911 --> 00:21:33.751
application state machine level, right?

00:21:33.791 --> 00:21:34.553
Which will be single

00:21:34.593 --> 00:21:37.175
threaded or is often single threaded,

00:21:37.296 --> 00:21:37.455
right?

00:21:37.496 --> 00:21:40.618
Which is why your CPU is your bottleneck,

00:21:41.539 --> 00:21:42.141
not your drives.

00:21:42.300 --> 00:21:42.881
Unless they were a

00:21:42.922 --> 00:21:44.282
bottleneck anyway as well,

00:21:44.482 --> 00:21:45.324
which they could have been.

00:21:45.523 --> 00:21:45.944
I could be wrong.

00:21:46.977 --> 00:21:47.657
Could be way off base.

00:21:47.678 --> 00:21:49.580
I've not dug into those metrics too much,

00:21:49.760 --> 00:21:51.523
to be honest, other than on Aptos.

00:21:51.544 --> 00:21:53.306
I would say that... Go ahead.

00:21:55.509 --> 00:21:55.929
I was going to say,

00:21:55.949 --> 00:21:56.990
I don't particularly know

00:21:57.471 --> 00:21:59.451
about the actual workings

00:21:59.571 --> 00:22:01.453
of how those rights occur.

00:22:02.433 --> 00:22:04.536
How I have to spec my

00:22:04.556 --> 00:22:05.636
hardware is by looking at

00:22:06.196 --> 00:22:08.538
the usage under different

00:22:08.558 --> 00:22:11.221
scenarios and then size the

00:22:11.320 --> 00:22:12.842
hardware appropriately to

00:22:12.862 --> 00:22:13.762
the real world usage

00:22:13.843 --> 00:22:15.483
instead of trying to assume

00:22:15.523 --> 00:22:16.585
what's going on under the hood.

00:22:17.125 --> 00:22:20.127
So basically on this server,

00:22:20.147 --> 00:22:21.348
we just over-spec everything.

00:22:22.249 --> 00:22:22.410
And

00:22:23.981 --> 00:22:25.804
we are like most of the time

00:22:25.824 --> 00:22:28.685
um probably at about 60

00:22:28.685 --> 00:22:31.288
percent of the um read

00:22:31.328 --> 00:22:32.249
write capacity of that

00:22:32.289 --> 00:22:34.230
drive or those drives in

00:22:34.270 --> 00:22:36.874
zfs mode because with zfs

00:22:36.913 --> 00:22:37.854
you rewrite the drives all

00:22:37.875 --> 00:22:39.036
the time it's copy on right

00:22:39.115 --> 00:22:42.419
so it'll read a block uh

00:22:43.259 --> 00:22:45.101
and then if it's changed

00:22:45.580 --> 00:22:46.823
it'll then write a block

00:22:47.688 --> 00:22:48.249
Andrew Mashman- Elsewhere,

00:22:48.269 --> 00:22:49.509
and then just change the

00:22:50.191 --> 00:22:51.291
the log and say that that

00:22:51.451 --> 00:22:52.614
block no longer exists,

00:22:52.814 --> 00:22:54.195
that it read from so it's

00:22:54.236 --> 00:22:56.218
constantly like rewriting

00:22:56.258 --> 00:22:57.940
the log it'll write data

00:22:58.099 --> 00:22:59.181
write a log entry for that

00:22:59.240 --> 00:23:00.423
new block and then it'll

00:23:00.442 --> 00:23:03.026
delete the entry for the old block.

00:23:03.501 --> 00:23:04.722
so it constantly rewrites

00:23:04.762 --> 00:23:06.223
the drives round robin

00:23:07.586 --> 00:23:08.246
that's why you don't get

00:23:08.286 --> 00:23:09.307
any write performance

00:23:09.366 --> 00:23:10.028
increase because it

00:23:10.087 --> 00:23:11.189
actually just writes a

00:23:11.209 --> 00:23:13.009
block a block block and it

00:23:13.049 --> 00:23:15.432
won't necessarily write one

00:23:15.471 --> 00:23:16.432
drive then the next drive

00:23:16.452 --> 00:23:17.453
than the next drive it'll

00:23:17.894 --> 00:23:20.977
actually fill up to level

00:23:21.037 --> 00:23:23.058
out the drive usage so if

00:23:23.098 --> 00:23:25.200
you put a new drive in or a

00:23:25.240 --> 00:23:26.721
new vdev right so say if you

00:23:28.319 --> 00:23:28.440
I,

00:23:28.799 --> 00:23:30.701
people wouldn't be familiar with like V

00:23:30.721 --> 00:23:31.623
devs and all this type of stuff,

00:23:31.643 --> 00:23:32.743
but basically you can take

00:23:32.763 --> 00:23:34.404
a bunch of drives as your

00:23:34.444 --> 00:23:35.465
original set of drives,

00:23:35.905 --> 00:23:36.626
and then you can add

00:23:36.686 --> 00:23:38.347
another bunch of drives, um,

00:23:38.428 --> 00:23:39.568
when you need more capacity.

00:23:39.608 --> 00:23:39.809
Right.

00:23:40.470 --> 00:23:41.530
And then it'll basically

00:23:41.570 --> 00:23:43.011
just keep writing into the

00:23:43.071 --> 00:23:44.553
new drives until it reaches

00:23:44.614 --> 00:23:46.414
about the same level of usage as the next,

00:23:47.056 --> 00:23:47.996
as the old set of drives.

00:23:48.016 --> 00:23:49.718
And then it'll start going

00:23:49.738 --> 00:23:52.240
across all of the drives one by one, but

00:23:53.185 --> 00:23:53.945
The problem is you don't get

00:23:53.986 --> 00:23:55.787
any advantage in write speed.

00:23:55.807 --> 00:23:57.267
You do get a read speed advantage,

00:23:57.326 --> 00:24:00.387
but not a write speed advantage.

00:24:01.568 --> 00:24:01.989
Anyway.

00:24:02.788 --> 00:24:02.929
Well,

00:24:02.949 --> 00:24:04.429
if you need this kind of pedantry for

00:24:04.449 --> 00:24:05.349
your archive nodes,

00:24:05.430 --> 00:24:06.569
don't forget to get in

00:24:06.589 --> 00:24:07.250
touch with Big Bull's

00:24:07.269 --> 00:24:10.270
blockchain for all of your

00:24:11.551 --> 00:24:13.011
archive node needs.

00:24:13.932 --> 00:24:15.613
Because you're in possession

00:24:15.712 --> 00:24:17.874
of several large machines

00:24:17.973 --> 00:24:19.354
in want of an application.

00:24:20.458 --> 00:24:22.679
We, we do do a pretty good archive.

00:24:23.159 --> 00:24:26.140
And, um, the thing with archive is,

00:24:26.160 --> 00:24:27.441
is that they become out of,

00:24:27.941 --> 00:24:29.260
out of reach after a while

00:24:29.520 --> 00:24:30.781
for anyone else to enter

00:24:30.821 --> 00:24:31.541
the game as well.

00:24:31.602 --> 00:24:33.303
So once your database is

00:24:33.363 --> 00:24:34.343
like a hundred terabytes,

00:24:34.563 --> 00:24:35.324
there ain't no one trying

00:24:35.344 --> 00:24:35.963
to sync that up.

00:24:36.223 --> 00:24:38.884
So interestingly, um,

00:24:39.785 --> 00:24:42.046
so DYDX has been running for what?

00:24:42.806 --> 00:24:43.767
Five, six months now.

00:24:44.826 --> 00:24:48.208
And I have to say it is a

00:24:48.327 --> 00:24:49.648
healthy network for history.

00:24:50.678 --> 00:24:54.339
um we move around archives

00:24:54.380 --> 00:24:57.320
occasionally and so the way

00:24:57.601 --> 00:25:00.041
um our dydx archives work

00:25:00.061 --> 00:25:01.422
is we have one in australia

00:25:01.481 --> 00:25:03.863
which is not uh public it's

00:25:03.982 --> 00:25:06.403
just um it basically stops

00:25:06.483 --> 00:25:08.684
once a day uh writes a new

00:25:09.244 --> 00:25:11.006
um tarball so people can

00:25:11.046 --> 00:25:13.186
download it and then um

00:25:14.528 --> 00:25:15.448
starts up again right

00:25:16.967 --> 00:25:18.067
So that one's like a private

00:25:18.087 --> 00:25:20.230
thing with a public accessible tarball.

00:25:20.990 --> 00:25:23.372
And then we have like out in the wild ones,

00:25:23.451 --> 00:25:24.932
which we can still at the

00:25:24.972 --> 00:25:28.715
moment run on some rentable

00:25:28.756 --> 00:25:30.096
hardware at a reasonable cost,

00:25:30.517 --> 00:25:31.438
but it's starting to get a

00:25:31.478 --> 00:25:32.898
little bit big for that.

00:25:32.999 --> 00:25:38.242
But I'm moving one at the moment.

00:25:38.343 --> 00:25:41.204
So I'm actually just decided to sync

00:25:42.155 --> 00:25:42.955
it from scratch,

00:25:43.675 --> 00:25:44.797
just to see like how

00:25:44.856 --> 00:25:46.277
healthy the network is for history.

00:25:47.317 --> 00:25:48.938
And it's sinking like 2

00:25:48.938 --> 00:25:49.798
million blocks a day.

00:25:50.357 --> 00:25:51.558
And I didn't even have to

00:25:51.719 --> 00:25:52.898
give it a persistent peer

00:25:52.959 --> 00:25:54.859
to an existing archive.

00:25:54.900 --> 00:25:59.500
I just fed it the pokachu seed and it, uh,

00:25:59.580 --> 00:26:00.520
found on the network,

00:26:00.560 --> 00:26:01.701
the history it needed and

00:26:01.741 --> 00:26:02.882
started sinking right away.

00:26:02.902 --> 00:26:05.303
So it's definitely a good,

00:26:05.363 --> 00:26:06.363
healthy amount of history

00:26:06.762 --> 00:26:08.884
available out there on peers.

00:26:12.230 --> 00:26:13.671
It's interesting that that

00:26:13.691 --> 00:26:14.791
suggests that there hasn't

00:26:14.811 --> 00:26:16.393
been aggressive pruning going on.

00:26:18.273 --> 00:26:19.815
I think there's a lot of archives.

00:26:20.115 --> 00:26:21.115
I know of at least six.

00:26:21.757 --> 00:26:21.916
Yeah,

00:26:22.116 --> 00:26:23.938
I was going to say that the DYDX team

00:26:24.117 --> 00:26:25.839
is paying for a lot of archives,

00:26:25.960 --> 00:26:27.500
so it makes sense that it's healthy.

00:26:28.942 --> 00:26:30.383
Yeah, and it's working well.

00:26:31.384 --> 00:26:32.584
I didn't have to do anything.

00:26:32.644 --> 00:26:33.345
I didn't have to wait.

00:26:34.226 --> 00:26:35.646
As soon as I fired it up and

00:26:35.707 --> 00:26:37.288
it started connecting to peers,

00:26:37.327 --> 00:26:38.367
it started syncing.

00:26:40.190 --> 00:26:41.750
But also, I think when you prune...

00:26:42.813 --> 00:26:44.713
So I think you can actually

00:26:45.494 --> 00:26:48.217
sync history from, and Frey,

00:26:48.237 --> 00:26:50.219
you might know a bit more about this,

00:26:50.298 --> 00:26:52.721
but there's like two levels of data.

00:26:53.340 --> 00:26:54.721
There's the ABCI data,

00:26:54.801 --> 00:26:57.845
and then there's like the state, right?

00:26:58.865 --> 00:26:59.486
That gets written.

00:27:00.226 --> 00:27:03.709
And I think you can sync

00:27:04.730 --> 00:27:09.473
from pruned nodes an archive if they...

00:27:10.415 --> 00:27:12.076
have it from number one I'm

00:27:12.096 --> 00:27:14.898
not 100 sure the the phrase

00:27:14.959 --> 00:27:15.920
wobbling around there but

00:27:16.220 --> 00:27:16.779
I'm not sure if he's

00:27:16.839 --> 00:27:19.241
nodding or thinking well

00:27:19.261 --> 00:27:19.961
now it looks like he's

00:27:19.981 --> 00:27:23.364
thinking for the listeners

00:27:23.384 --> 00:27:25.346
it looks like he's taking a

00:27:25.486 --> 00:27:27.807
I think the prune I think I

00:27:27.846 --> 00:27:29.087
think once I think once

00:27:29.188 --> 00:27:30.828
pruned you wouldn't be able

00:27:30.888 --> 00:27:33.371
to because although you would have

00:27:34.490 --> 00:27:36.531
hashes of the aggregate com you, you would,

00:27:36.711 --> 00:27:37.612
you would have hashes of

00:27:37.652 --> 00:27:38.813
the aggregate commitments

00:27:38.932 --> 00:27:41.653
and you could step back through, um,

00:27:41.673 --> 00:27:45.435
you could step back through the tree.

00:27:49.498 --> 00:27:50.458
No, you don't, you know,

00:27:50.478 --> 00:27:51.137
you would only have the

00:27:51.178 --> 00:27:52.659
hashes of the commitments.

00:27:52.818 --> 00:27:54.339
In fact, that's, that's literally it.

00:27:54.460 --> 00:27:56.780
You wouldn't have the full

00:27:56.820 --> 00:28:01.222
block data unless I'm very much mistaken.

00:28:02.667 --> 00:28:05.209
Review incoming listeners, dear listener.

00:28:06.190 --> 00:28:07.230
Well, when a staff,

00:28:07.309 --> 00:28:09.050
when a staff catches up with this episode,

00:28:09.111 --> 00:28:10.231
no doubt we'll get tweeted.

00:28:10.471 --> 00:28:12.913
If that was, if that was, he'll tweet,

00:28:12.932 --> 00:28:14.334
what in the fuck is Nell talking about?

00:28:14.354 --> 00:28:17.194
He's an idiot.

00:28:17.635 --> 00:28:18.895
I do think that's how it works.

00:28:19.076 --> 00:28:19.876
Threading coming.

00:28:22.577 --> 00:28:24.479
Your, uh, your homework's been set as a,

00:28:25.859 --> 00:28:25.940
um,

00:28:27.260 --> 00:28:28.441
But yeah, anyway,

00:28:28.922 --> 00:28:30.741
so lots of interesting

00:28:30.781 --> 00:28:32.423
behind-the-scene stuff

00:28:32.462 --> 00:28:34.282
going on over the last week or so,

00:28:36.084 --> 00:28:37.703
which has resulted in less alarms,

00:28:37.763 --> 00:28:38.365
which is nice.

00:28:39.785 --> 00:28:40.525
That's interesting.

00:28:40.605 --> 00:28:42.105
And our Pego seems to be

00:28:42.145 --> 00:28:43.526
working fantastically after

00:28:43.546 --> 00:28:44.247
the move as well.

00:28:44.267 --> 00:28:47.528
Well, it just ups back the machine or...?

00:28:47.548 --> 00:28:50.788
Well, I mean,

00:28:50.828 --> 00:28:51.949
it's not really... The only really...

00:28:54.840 --> 00:28:56.301
Well, it is a faster CPU,

00:28:56.342 --> 00:28:57.323
but I can't see how that

00:28:57.343 --> 00:28:59.125
would change things.

00:28:59.305 --> 00:29:01.126
It's faster CPU, same RAM,

00:29:01.406 --> 00:29:03.008
and bigger hard drives.

00:29:04.269 --> 00:29:05.349
But I don't really... You know,

00:29:05.390 --> 00:29:06.852
Pega is a really strange thing.

00:29:07.332 --> 00:29:10.375
It'll hang for reasons unknown to man.

00:29:10.875 --> 00:29:12.557
Well, I mean, I think we just... I mean,

00:29:12.576 --> 00:29:12.737
again,

00:29:12.757 --> 00:29:15.739
I'm not familiar with the software for it,

00:29:15.838 --> 00:29:17.681
but it wouldn't surprise me

00:29:17.740 --> 00:29:19.363
if it's essentially a

00:29:19.423 --> 00:29:20.624
single-threaded application.

00:29:22.955 --> 00:29:24.637
Oh, I'm sure it is.

00:29:24.798 --> 00:29:27.240
I'm only certain.

00:29:27.359 --> 00:29:27.539
Yeah,

00:29:27.619 --> 00:29:29.260
relatively obvious reasons why that

00:29:29.300 --> 00:29:30.342
might be the case in the

00:29:30.422 --> 00:29:32.023
industry that we work in.

00:29:32.903 --> 00:29:34.144
What's the easiest way to

00:29:34.184 --> 00:29:35.226
make sure you don't do

00:29:35.286 --> 00:29:36.767
something that causes

00:29:36.827 --> 00:29:38.588
non-determinism on local nodes?

00:29:38.969 --> 00:29:39.869
Just don't bother with any

00:29:39.890 --> 00:29:42.132
of that parallelism shit.

00:29:42.311 --> 00:29:44.394
That's a good way of doing it, right?

00:29:44.973 --> 00:29:45.875
Which just leaves a lot of

00:29:46.075 --> 00:29:47.536
processing power on the table,

00:29:47.816 --> 00:29:49.897
given the dominant multi-core

00:29:51.695 --> 00:29:52.977
multi-vcore type

00:29:54.017 --> 00:29:55.417
architectures that we're used to now,

00:29:55.458 --> 00:29:55.659
right?

00:29:56.939 --> 00:29:57.960
I'll tell you what, though.

00:29:58.299 --> 00:29:59.181
So I don't know the

00:29:59.240 --> 00:30:00.401
architecture of the software,

00:30:00.461 --> 00:30:03.482
but we definitely, as validators,

00:30:03.522 --> 00:30:04.604
made a lot of complaints

00:30:05.424 --> 00:30:11.087
about it over the last several months.

00:30:11.748 --> 00:30:13.509
And the last update did

00:30:13.930 --> 00:30:15.471
improve things significantly.

00:30:15.611 --> 00:30:17.531
So I don't know if you noticed, Chilti,

00:30:17.731 --> 00:30:20.473
but... Fucking hell.

00:30:21.538 --> 00:30:25.202
When, uh, when they, sorry,

00:30:25.222 --> 00:30:26.624
I was just distracted by that,

00:30:26.683 --> 00:30:27.964
whatever the fuck is going on over there,

00:30:28.226 --> 00:30:29.707
strangling a calf or something.

00:30:30.587 --> 00:30:33.730
Um, so when you actually, if it stops,

00:30:33.810 --> 00:30:34.011
right.

00:30:34.051 --> 00:30:34.731
And you reset it,

00:30:34.811 --> 00:30:35.993
say if you're like 50

00:30:35.993 --> 00:30:37.015
nonsense behind or something,

00:30:37.875 --> 00:30:39.497
I noticed that it like batches now.

00:30:40.337 --> 00:30:41.659
I'm not sure if it did that before, but if,

00:30:41.878 --> 00:30:42.900
if you're way behind,

00:30:42.980 --> 00:30:44.541
it'll catch up like almost

00:30:44.602 --> 00:30:45.423
instantaneously.

00:30:47.385 --> 00:30:48.747
I think it's been there for a long time.

00:30:49.166 --> 00:30:50.186
It's always been pretty quick.

00:30:50.487 --> 00:30:51.386
Yeah, I think so.

00:30:53.968 --> 00:30:54.367
Interesting,

00:30:54.387 --> 00:30:57.788
because I noticed previously

00:30:57.828 --> 00:30:59.609
when I would observe the history of it,

00:30:59.690 --> 00:31:03.411
you'd see if it was going

00:31:03.471 --> 00:31:04.891
really slow or something,

00:31:05.471 --> 00:31:06.791
or even after a restart,

00:31:06.832 --> 00:31:07.832
it would catch up and then

00:31:08.152 --> 00:31:09.612
it would do a couple and

00:31:09.632 --> 00:31:10.633
then it would wait a while

00:31:10.673 --> 00:31:11.313
and then do a couple.

00:31:11.792 --> 00:31:13.192
It seemed previously to take

00:31:13.653 --> 00:31:15.213
hours to catch up sometimes.

00:31:16.161 --> 00:31:17.561
Um, I just know that now, whenever,

00:31:17.582 --> 00:31:19.923
you know, if it hangs and you restart it,

00:31:20.923 --> 00:31:22.753
um, and there's like, you know, 20,

00:31:22.753 --> 00:31:24.424
50 nuances or something like that,

00:31:24.444 --> 00:31:25.685
it would just do them all

00:31:25.746 --> 00:31:26.586
in one transaction.

00:31:28.067 --> 00:31:28.247
Okay.

00:31:28.267 --> 00:31:28.946
That I haven't seen.

00:31:28.967 --> 00:31:29.948
I haven't seen them all done

00:31:29.968 --> 00:31:30.748
in one transaction,

00:31:30.847 --> 00:31:32.189
just that they like blast

00:31:32.209 --> 00:31:33.009
them out really quick.

00:31:34.650 --> 00:31:35.951
It actually on the line.

00:31:36.010 --> 00:31:37.511
Now, um, if you look at the logs,

00:31:37.551 --> 00:31:38.612
it actually says the amount

00:31:38.652 --> 00:31:40.113
of transactions that it puts in there.

00:31:41.903 --> 00:31:42.742
or the amount of,

00:31:42.864 --> 00:31:43.943
like for all the different

00:31:44.364 --> 00:31:46.444
types of bridging,

00:31:47.965 --> 00:31:49.946
it'll actually have numbers

00:31:49.987 --> 00:31:51.728
for each of them in the log line,

00:31:52.268 --> 00:31:52.867
I'm pretty sure.

00:31:52.887 --> 00:31:55.710
But anyway, who cares?

00:31:55.829 --> 00:31:57.089
So from the chat, Noel,

00:31:57.971 --> 00:31:58.931
it seems that you might

00:31:59.010 --> 00:32:00.291
actually be right.

00:32:00.352 --> 00:32:01.432
Reece says in the chat,

00:32:02.173 --> 00:32:03.752
you can sync an archive

00:32:03.792 --> 00:32:05.114
from an event-prune node

00:32:05.574 --> 00:32:06.755
since events just come from

00:32:06.795 --> 00:32:08.836
messages begin and block as

00:32:08.875 --> 00:32:09.756
far as he knows.

00:32:10.817 --> 00:32:11.017
So...

00:32:11.913 --> 00:32:13.255
All you're doing by pruning

00:32:13.855 --> 00:32:17.898
that is not pruning the...

00:32:19.059 --> 00:32:21.001
Which I guess intuitively makes sense.

00:32:21.102 --> 00:32:22.182
I guess you're not actually

00:32:22.202 --> 00:32:23.523
pruning the state per se.

00:32:23.564 --> 00:32:26.105
You're pruning essentially

00:32:26.125 --> 00:32:28.627
the additional block metadata.

00:32:29.909 --> 00:32:31.330
If that's the... That might

00:32:31.351 --> 00:32:32.892
not be quite the correct technical term.

00:32:34.877 --> 00:32:35.898
But yeah,

00:32:36.138 --> 00:32:37.440
I'm not up enough with the

00:32:37.640 --> 00:32:38.661
pruning mechanics and what

00:32:38.681 --> 00:32:39.642
you're actually pruning to

00:32:40.301 --> 00:32:41.103
make a call on that.

00:32:41.182 --> 00:32:42.743
So I'll take Rhys' word for it.

00:32:43.365 --> 00:32:44.085
So yeah,

00:32:44.105 --> 00:32:45.566
it says as long as the event prune

00:32:45.605 --> 00:32:47.728
node is still an archive of blocks.

00:32:49.970 --> 00:32:52.832
So I'm not completely off the track.

00:32:55.213 --> 00:32:56.914
It seems not, is the conclusion.

00:32:59.237 --> 00:33:00.258
By the way, hi, Rhys.

00:33:00.939 --> 00:33:01.858
I sent you a message the

00:33:01.898 --> 00:33:03.259
other day to which you didn't respond,

00:33:03.279 --> 00:33:03.319
so...

00:33:05.478 --> 00:33:07.938
Would you like a commiseration prize,

00:33:07.998 --> 00:33:10.019
which is doing drill tweet of the week?

00:33:10.618 --> 00:33:11.519
Oh, fuck.

00:33:11.638 --> 00:33:12.838
It's been weeks since we've

00:33:12.858 --> 00:33:13.499
done a drill tweet.

00:33:13.719 --> 00:33:13.939
All right.

00:33:14.219 --> 00:33:14.519
Say when?

00:33:14.539 --> 00:33:15.019
Maybe months.

00:33:16.480 --> 00:33:16.660
When?

00:33:18.680 --> 00:33:20.260
Left page or right page?

00:33:20.760 --> 00:33:21.681
I literally have to say it

00:33:21.721 --> 00:33:23.861
before you start to get an early one.

00:33:23.881 --> 00:33:24.040
Well,

00:33:24.141 --> 00:33:26.801
it's because there's a speed of light lag,

00:33:26.842 --> 00:33:27.201
isn't there?

00:33:27.221 --> 00:33:28.821
We're in different continents and whatnot.

00:33:29.721 --> 00:33:29.902
Well,

00:33:29.961 --> 00:33:31.662
I think around here it's probably

00:33:31.721 --> 00:33:32.663
more speed of copper.

00:33:33.123 --> 00:33:34.982
But, yeah, I take your meaning.

00:33:37.413 --> 00:33:39.913
Left, left, left, middle, left, middle.

00:33:40.753 --> 00:33:41.714
The good ones are always in the middle.

00:33:43.994 --> 00:33:45.576
Okay.

00:33:46.955 --> 00:33:47.155
Okay.

00:33:47.175 --> 00:33:50.497
So every word in this tweet

00:33:50.636 --> 00:33:52.297
has a capital first letter.

00:33:52.836 --> 00:33:54.498
That's all you need to know.

00:33:54.538 --> 00:33:56.557
So it's formatted like a newspaper title,

00:33:56.698 --> 00:33:57.038
I guess.

00:33:59.058 --> 00:34:01.319
Disgusting Pear Man fucks

00:34:01.359 --> 00:34:02.859
his hideous orange wife.

00:34:04.157 --> 00:34:08.721
colon read more colon Reuters.com.

00:34:15.905 --> 00:34:17.905
I missed the precursor to

00:34:17.945 --> 00:34:20.987
that because like whatever that,

00:34:21.168 --> 00:34:22.329
that pre conversation you

00:34:22.369 --> 00:34:23.449
had where your lips were moving,

00:34:23.528 --> 00:34:25.230
I couldn't hear because

00:34:26.331 --> 00:34:27.411
Reese sent me a message

00:34:27.452 --> 00:34:29.012
that annihilated my eardrums.

00:34:30.016 --> 00:34:31.438
through my phone which is

00:34:31.518 --> 00:34:32.378
also connected to my

00:34:32.398 --> 00:34:33.938
headphones so sorry about

00:34:33.958 --> 00:34:35.840
that amazing well in

00:34:35.880 --> 00:34:36.760
conclusion you didn't miss

00:34:36.800 --> 00:34:38.141
anything um what was it

00:34:38.242 --> 00:34:39.922
pear man his hideous orange

00:34:39.963 --> 00:34:43.284
wife reuters why is she

00:34:43.364 --> 00:34:45.505
orange though one of the

00:34:45.565 --> 00:34:46.987
many one of the many

00:34:47.007 --> 00:34:50.168
mysteries of drill what you

00:34:50.208 --> 00:34:53.030
will yeah it's like the

00:34:53.050 --> 00:34:53.871
many layers of drill

00:34:56.188 --> 00:34:56.389
What?

00:34:56.548 --> 00:34:59.010
The book doesn't say when it

00:34:59.050 --> 00:35:00.152
was written or when it was tweeted?

00:35:00.291 --> 00:35:00.952
That's ridiculous.

00:35:00.972 --> 00:35:01.914
There's no quote date.

00:35:02.454 --> 00:35:03.315
I'm beginning to think a lot

00:35:03.355 --> 00:35:03.914
of these are fake.

00:35:04.195 --> 00:35:05.096
They're just made up.

00:35:05.916 --> 00:35:06.077
Right?

00:35:06.117 --> 00:35:07.498
He just comes up with, I'm on the spot.

00:35:08.318 --> 00:35:11.481
I feel like he just sat on

00:35:11.521 --> 00:35:12.722
his couch and came up with

00:35:12.742 --> 00:35:14.244
these ridiculous things and

00:35:14.284 --> 00:35:15.304
didn't even tweet them.

00:35:19.367 --> 00:35:20.489
Someone's searching.

00:35:22.090 --> 00:35:22.630
Yeah, right.

00:35:24.385 --> 00:35:25.547
like, fuck it,

00:35:25.606 --> 00:35:26.387
I need to get to the bottom

00:35:26.427 --> 00:35:27.148
of this bullshit.

00:35:30.891 --> 00:35:31.472
Okay, well,

00:35:31.492 --> 00:35:33.233
so it turns out that if you just,

00:35:33.693 --> 00:35:34.094
if you don't,

00:35:34.434 --> 00:35:35.536
because I don't know what

00:35:35.956 --> 00:35:36.936
the whole tweet was because

00:35:36.956 --> 00:35:38.378
I've now closed the book and put it away.

00:35:38.398 --> 00:35:40.641
So I just from memory

00:35:41.300 --> 00:35:43.864
Googled what I just said

00:35:44.483 --> 00:35:45.244
for the drill tweet.

00:35:47.246 --> 00:35:48.286
And it turns out

00:35:49.960 --> 00:35:52.181
that with safe search off if

00:35:52.260 --> 00:35:55.001
you type pair man fucks his

00:35:55.061 --> 00:35:58.123
hideous orange wife you can

00:35:58.182 --> 00:35:59.043
imagine what the internet

00:35:59.083 --> 00:36:00.224
does for you it does not

00:36:00.764 --> 00:36:02.965
give you back the twitter

00:36:04.364 --> 00:36:05.704
post by drill that you were

00:36:05.726 --> 00:36:10.567
looking for it instead has

00:36:10.606 --> 00:36:12.748
a load of stuff on dating

00:36:12.987 --> 00:36:15.748
and yeah just lots of

00:36:18.139 --> 00:36:20.521
yeah and and you know not

00:36:20.541 --> 00:36:22.822
because just just yes just

00:36:22.862 --> 00:36:25.521
let's just move on so

00:36:25.581 --> 00:36:26.643
whatever is rule six of the

00:36:26.682 --> 00:36:28.563
internet it just don't

00:36:28.663 --> 00:36:30.204
especially don't provoke it

00:36:30.224 --> 00:36:32.023
by by adding in the phrase

00:36:32.204 --> 00:36:34.085
idiot wife let's just say

00:36:34.605 --> 00:36:37.746
that was a mistake that's

00:36:37.766 --> 00:36:39.126
now in your search history

00:36:39.166 --> 00:36:40.726
for the books maybe we

00:36:40.746 --> 00:36:41.967
should have a new a new

00:36:42.088 --> 00:36:43.208
type of book it's like

00:36:43.668 --> 00:36:45.568
phrase search history um

00:36:47.501 --> 00:36:50.043
So I do need to make a

00:36:50.103 --> 00:36:51.344
public apology to Rhys.

00:36:51.583 --> 00:36:52.585
Apparently I didn't send him

00:36:52.605 --> 00:36:53.985
a message and I only thought it.

00:36:56.186 --> 00:36:56.525
Wow.

00:36:57.806 --> 00:37:01.088
His, uh, his, his message to me,

00:37:01.208 --> 00:37:06.251
which annihilated my eardrums was, um,

00:37:06.271 --> 00:37:07.530
where's this message I've

00:37:07.550 --> 00:37:08.251
searched everywhere.

00:37:08.271 --> 00:37:11.313
Re retort.

00:37:12.699 --> 00:37:15.059
okay well good that your

00:37:15.119 --> 00:37:16.001
social life is back on

00:37:16.041 --> 00:37:19.322
track now shall we do a

00:37:19.583 --> 00:37:21.103
news item there's quite a

00:37:21.123 --> 00:37:23.264
lot of news this week quite

00:37:23.284 --> 00:37:26.326
a lot of shenanigans drama

00:37:26.487 --> 00:37:28.628
was a little bit thrown

00:37:28.688 --> 00:37:29.947
aback by the amount of

00:37:31.188 --> 00:37:32.489
already available news in

00:37:32.510 --> 00:37:35.251
the spreadsheet he strongly

00:37:35.271 --> 00:37:36.351
suggested that we're

00:37:36.371 --> 00:37:39.873
stepping on his uh job yeah well

00:37:40.802 --> 00:37:41.523
I thought it was very,

00:37:41.563 --> 00:37:43.905
very funny that on crypto betting,

00:37:44.186 --> 00:37:46.047
you can currently bet on

00:37:46.246 --> 00:37:49.349
SBF's expected jail term.

00:37:50.891 --> 00:37:52.552
So according to...

00:37:53.559 --> 00:37:54.679
what is crypto betting is

00:37:54.699 --> 00:37:57.382
this some website uh

00:37:57.422 --> 00:37:58.882
something else on the

00:37:58.922 --> 00:38:00.103
crypto petting site

00:38:00.184 --> 00:38:02.606
polymarket according to

00:38:02.646 --> 00:38:05.807
coindesk um you can bet on

00:38:05.967 --> 00:38:08.489
sbf's jail term um one

00:38:08.530 --> 00:38:09.990
percent have bet five to

00:38:10.050 --> 00:38:11.791
ten years eight percent

00:38:11.831 --> 00:38:14.014
have bet over 50 years uh

00:38:14.134 --> 00:38:15.414
and most better's money is

00:38:15.474 --> 00:38:17.175
falling on between 20 to 50 years so

00:38:19.097 --> 00:38:20.719
um not financial advice but

00:38:20.739 --> 00:38:22.563
uh apparently a poly market

00:38:22.663 --> 00:38:23.925
is the is the place to go

00:38:23.945 --> 00:38:27.309
uh for whether yeah the um

00:38:27.630 --> 00:38:28.972
the the there was there was

00:38:29.012 --> 00:38:31.054
that insane will sbf sentence babe

00:38:31.721 --> 00:38:34.963
Yeah, so there was a great thing,

00:38:35.003 --> 00:38:35.403
wasn't there?

00:38:35.443 --> 00:38:36.485
Where basically he's been

00:38:36.525 --> 00:38:38.286
trying to argue like, ah, you know,

00:38:38.326 --> 00:38:39.606
people will be made whole.

00:38:39.827 --> 00:38:40.728
It's all fine.

00:38:41.809 --> 00:38:43.929
You know, client is very, very sorry.

00:38:44.490 --> 00:38:46.731
And then they discovered, I think,

00:38:46.771 --> 00:38:48.193
like a Google Doc in the

00:38:48.253 --> 00:38:49.835
dump of data and stuff that

00:38:49.855 --> 00:38:51.275
they subpoenaed.

00:38:51.295 --> 00:38:53.858
Or no, it was like a spreadsheet.

00:38:53.878 --> 00:38:55.038
It wasn't even a Google Doc.

00:38:55.057 --> 00:38:56.239
It was like this fucking

00:38:56.378 --> 00:38:59.481
Excel file with just like,

00:38:59.922 --> 00:39:01.023
it was called something like,

00:39:02.454 --> 00:39:05.018
probably bad ideas lol and

00:39:05.057 --> 00:39:06.119
it was like all of his

00:39:06.219 --> 00:39:07.059
thoughts for like

00:39:07.119 --> 00:39:08.681
rehabilitating his image

00:39:09.322 --> 00:39:10.443
and it was just again in a

00:39:10.583 --> 00:39:12.005
file in a pile of stuff

00:39:12.045 --> 00:39:13.126
that obviously was gonna

00:39:13.146 --> 00:39:14.927
get seized by the feds and it's like

00:39:16.800 --> 00:39:17.219
I don't know,

00:39:17.239 --> 00:39:19.760
some bullshit like go on Oprah.

00:39:19.820 --> 00:39:20.581
No, it's not even that.

00:39:20.862 --> 00:39:22.942
It's like, it wouldn't be go on Oprah.

00:39:23.081 --> 00:39:24.182
That was Lance Armstrong.

00:39:25.302 --> 00:39:26.704
But it's just like a load of really,

00:39:26.764 --> 00:39:27.963
really disingenuous shit.

00:39:28.083 --> 00:39:29.164
And then obviously it just

00:39:29.204 --> 00:39:30.585
comes up in court where they're like,

00:39:31.465 --> 00:39:32.525
but Mr. Bankman Freed,

00:39:32.965 --> 00:39:35.327
in the piece of evidence, you know,

00:39:35.586 --> 00:39:37.146
presented by the prosecution, blah, blah,

00:39:37.166 --> 00:39:38.688
blah, entitled

00:39:39.088 --> 00:39:40.307
probably bad ideas to

00:39:40.347 --> 00:39:42.309
rehabilitate my image colon

00:39:42.369 --> 00:39:44.670
lol uh you have stated uh

00:39:44.690 --> 00:39:48.010
it's a comma lol uh you you

00:39:48.030 --> 00:39:49.670
have stated blah blah blah

00:39:49.891 --> 00:39:50.731
you know should make the

00:39:50.771 --> 00:39:52.351
dj's happier or something

00:39:53.092 --> 00:39:54.032
do you think this is in

00:39:54.112 --> 00:39:55.552
good faith or bad faith and

00:39:55.592 --> 00:39:57.612
it's just like oh my god

00:39:57.873 --> 00:40:01.153
he's going to prison for a long time like

00:40:02.838 --> 00:40:03.059
I just,

00:40:03.119 --> 00:40:04.139
I don't have faith he's going to

00:40:04.179 --> 00:40:05.079
prison for a long time.

00:40:05.199 --> 00:40:07.460
I wish I did, but after, um,

00:40:07.480 --> 00:40:11.181
what was that lady that did the, uh, she,

00:40:11.300 --> 00:40:14.342
she led, um,

00:40:14.362 --> 00:40:15.961
a medical company that was supposed to,

00:40:15.981 --> 00:40:17.442
like, take a drop of your blood.

00:40:17.461 --> 00:40:18.862
Oh, Theranos.

00:40:19.362 --> 00:40:20.123
That's the one, Theranos.

00:40:20.143 --> 00:40:21.143
Yeah, she got, she went to prison for,

00:40:21.163 --> 00:40:22.242
like, what, six years?

00:40:22.503 --> 00:40:23.503
She's about to get out soon?

00:40:24.344 --> 00:40:26.463
That seems more egregious than FTX,

00:40:26.483 --> 00:40:27.744
even though FTX, like,

00:40:28.025 --> 00:40:28.684
could cost a lot of money.

00:40:31.349 --> 00:40:33.110
But that was the Ponzi company, right?

00:40:33.150 --> 00:40:35.429
She just wasn't a doctor,

00:40:35.550 --> 00:40:36.650
didn't create anything,

00:40:37.010 --> 00:40:38.731
sold all these fucking shares.

00:40:38.831 --> 00:40:41.092
It was only VCs that lost money.

00:40:41.152 --> 00:40:43.172
I mean, like world's smallest violin,

00:40:43.213 --> 00:40:43.432
right?

00:40:44.373 --> 00:40:45.233
Yes, for sure.

00:40:45.393 --> 00:40:47.753
But she still only got, in effect,

00:40:47.773 --> 00:40:48.773
for how much money it was,

00:40:48.793 --> 00:40:50.355
a slap on the wrist.

00:40:50.574 --> 00:40:51.534
I just don't have faith that

00:40:51.554 --> 00:40:52.215
SPF is going to go away.

00:40:52.235 --> 00:40:53.576
Did she get to keep any of the money,

00:40:53.596 --> 00:40:53.755
though?

00:40:55.545 --> 00:40:56.766
She was very well connected.

00:40:56.806 --> 00:40:58.547
She was from a well-off family and stuff,

00:40:58.586 --> 00:40:59.927
wasn't she?

00:40:59.987 --> 00:41:02.188
The reason that something

00:41:02.507 --> 00:41:05.409
happened was because the

00:41:05.429 --> 00:41:06.869
people who lost money were

00:41:06.929 --> 00:41:08.510
very well connected and

00:41:08.610 --> 00:41:09.731
demanded something be done.

00:41:10.411 --> 00:41:12.612
But like all these things, also,

00:41:12.652 --> 00:41:13.851
if you're very well connected,

00:41:13.891 --> 00:41:15.152
it's like the scene in Wolf

00:41:15.172 --> 00:41:17.632
of Wall Street where he's like,

00:41:17.713 --> 00:41:18.974
but then I remembered I was

00:41:19.034 --> 00:41:20.353
going to jail in America

00:41:20.434 --> 00:41:21.393
and I was rich and that

00:41:21.434 --> 00:41:22.614
shows him playing tennis.

00:41:22.735 --> 00:41:23.195
And you're like,

00:41:23.815 --> 00:41:24.795
yeah I mean that's exactly

00:41:24.815 --> 00:41:25.516
what happened to her she

00:41:25.536 --> 00:41:26.396
was slapped on the wrist

00:41:26.456 --> 00:41:28.719
and sent to tennis jail um

00:41:29.018 --> 00:41:30.239
for a few years which is

00:41:30.280 --> 00:41:31.400
basically just like a shit

00:41:31.440 --> 00:41:33.983
college um to think about

00:41:34.583 --> 00:41:35.724
what she's done before she

00:41:35.784 --> 00:41:37.144
comes out and inevitably

00:41:37.585 --> 00:41:38.545
raise the venture capital

00:41:38.585 --> 00:41:40.788
for her next venture oh

00:41:40.807 --> 00:41:41.568
yeah you know she's gonna

00:41:41.588 --> 00:41:42.568
be sent to the corner like

00:41:42.708 --> 00:41:45.371
the day after yeah exactly

00:41:45.391 --> 00:41:46.411
or she'll sell the right

00:41:46.572 --> 00:41:47.932
amazon yeah there'll be a

00:41:47.972 --> 00:41:50.114
book for sure yeah yeah exactly um

00:41:51.835 --> 00:41:54.396
so you said you had no faith

00:41:54.416 --> 00:41:55.077
that there's going to be a

00:41:55.117 --> 00:41:56.717
jail term shortsy would you

00:41:56.777 --> 00:41:59.519
care to put money on that I

00:41:59.559 --> 00:42:00.161
think there's going to be a

00:42:00.201 --> 00:42:01.762
jail term I don't think it

00:42:02.141 --> 00:42:03.643
like people putting down 50

00:42:03.643 --> 00:42:05.983
plus years absolutely so

00:42:06.003 --> 00:42:07.445
you're thinking five to ten

00:42:07.764 --> 00:42:08.846
can I put you down for a

00:42:08.865 --> 00:42:13.708
hundred thousand coins the

00:42:14.210 --> 00:42:15.831
popular opinion is 30 to 30

00:42:15.831 --> 00:42:17.391
to 40 years 28 wait how

00:42:17.411 --> 00:42:19.333
many how many uh cabarets

00:42:19.373 --> 00:42:20.393
do we want to put on this

00:42:21.570 --> 00:42:22.911
What shit coins do they take

00:42:22.971 --> 00:42:24.431
on this best thing site anyway?

00:42:25.112 --> 00:42:26.492
You'll have to get them out of storage,

00:42:26.853 --> 00:42:27.172
i.e.

00:42:27.253 --> 00:42:29.494
fucking boot up the network again.

00:42:29.914 --> 00:42:30.775
Boot up the network.

00:42:33.235 --> 00:42:34.617
Presumably this is Ethereum

00:42:35.237 --> 00:42:39.840
or some L2 powered by Polygon and Lima.

00:42:40.199 --> 00:42:40.340
Yeah.

00:42:40.938 --> 00:42:41.318
Okay,

00:42:41.458 --> 00:42:44.000
so second best piece of news of the week?

00:42:44.641 --> 00:42:45.960
Well, I mean,

00:42:45.981 --> 00:42:46.981
we're still not off this yet.

00:42:47.282 --> 00:42:47.742
Firstly,

00:42:47.782 --> 00:42:49.523
I looked up this Polymarket and it

00:42:49.583 --> 00:42:50.463
is fucking amazing.

00:42:51.583 --> 00:42:52.364
I think this is going to be

00:42:52.384 --> 00:42:53.123
my new homepage.

00:42:54.005 --> 00:42:55.905
But I want to know,

00:42:56.925 --> 00:42:58.547
and maybe this is a follow-up,

00:42:58.726 --> 00:43:00.228
like how they actually

00:43:00.307 --> 00:43:04.228
record the results on here in a, you know,

00:43:04.369 --> 00:43:05.530
decentralized manner.

00:43:05.750 --> 00:43:08.670
So that, because these are all very,

00:43:09.592 --> 00:43:09.871
you know,

00:43:11.081 --> 00:43:12.302
user input type things,

00:43:12.824 --> 00:43:14.244
whether or not these things happened.

00:43:14.806 --> 00:43:16.507
Do people like vote on them after they.

00:43:16.527 --> 00:43:23.574
Generously Oracle where, yeah, I mean,

00:43:23.614 --> 00:43:25.195
it would need some kind of Oracle, right.

00:43:26.204 --> 00:43:27.164
Oh, here's another one.

00:43:27.704 --> 00:43:28.905
They've got the top ones up here.

00:43:28.945 --> 00:43:30.286
So the top ones are the

00:43:30.706 --> 00:43:34.447
presidential election winner 2024.

00:43:34.447 --> 00:43:34.668
You know,

00:43:34.728 --> 00:43:36.309
they don't say US presidential

00:43:36.369 --> 00:43:37.010
election winners.

00:43:37.070 --> 00:43:38.130
So they're just assuming

00:43:38.170 --> 00:43:39.490
that the entire world only

00:43:39.550 --> 00:43:40.550
thinks about the US.

00:43:40.731 --> 00:43:42.672
But it looks like we're

00:43:42.692 --> 00:43:43.452
going to have a Trump president.

00:43:43.472 --> 00:43:44.132
Which is true.

00:43:44.492 --> 00:43:47.655
Which is true.

00:43:47.675 --> 00:43:50.036
Ethereum ETF approved by May 31st.

00:43:55.318 --> 00:43:56.260
Doesn't say the year,

00:43:56.300 --> 00:43:57.201
but I'm assuming 2024.

00:43:57.201 --> 00:44:00.623
That seems unlikely.

00:44:01.003 --> 00:44:02.083
Good point.

00:44:02.103 --> 00:44:05.126
This is pretty weak that it

00:44:05.146 --> 00:44:06.527
didn't say the actual... Oh, no, no.

00:44:06.628 --> 00:44:07.668
It says it in the rules.

00:44:08.268 --> 00:44:09.831
The title itself says just May 31st,

00:44:09.851 --> 00:44:11.112
but in the rules it says

00:44:11.192 --> 00:44:12.172
this market will resolve to

00:44:12.273 --> 00:44:13.994
yes if any spot Ethereum

00:44:14.094 --> 00:44:15.715
ETF resolves receives

00:44:15.755 --> 00:44:16.996
approval from the SEC by May 31st,

00:44:16.996 --> 00:44:17.237
2024 by 12 p.m.

00:44:17.257 --> 00:44:17.617
Eastern Time.

00:44:22.766 --> 00:44:23.286
Ah, copy.

00:44:23.347 --> 00:44:25.829
The chance is becoming less and less.

00:44:26.670 --> 00:44:26.949
Yeah.

00:44:27.771 --> 00:44:30.954
There is the... Not UTC.

00:44:30.994 --> 00:44:32.275
Fucking Eastern Time.

00:44:32.554 --> 00:44:34.277
Not even PST.

00:44:34.617 --> 00:44:36.418
Not even like the time zone of Tag.

00:44:36.878 --> 00:44:40.161
The time zone of... What?

00:44:41.730 --> 00:44:41.989
No,

00:44:42.130 --> 00:44:43.710
I think that makes sense because the

00:44:43.751 --> 00:44:46.172
New York Stock Exchange is Eastern Time,

00:44:46.213 --> 00:44:46.452
right?

00:44:46.893 --> 00:44:47.873
And so if the ETF would

00:44:47.893 --> 00:44:49.534
probably be based off of that.

00:44:49.635 --> 00:44:50.655
So I'd give it to him.

00:44:51.255 --> 00:44:51.976
I think that makes sense.

00:44:52.577 --> 00:44:54.157
And the ETF probably assumes

00:44:54.297 --> 00:44:55.978
US ETFs anyway, right?

00:44:55.998 --> 00:44:56.860
Because I think Canada

00:44:56.900 --> 00:44:58.661
actually has an Ethereum ETF already.

00:44:58.681 --> 00:45:00.862
Oh, I mean, yeah, probably.

00:45:02.923 --> 00:45:04.264
Not that I'm defending them too much.

00:45:04.364 --> 00:45:05.005
I'm just saying.

00:45:05.025 --> 00:45:08.106
I'm just saying Eastern Time

00:45:08.146 --> 00:45:09.108
makes a lot of sense.

00:45:11.722 --> 00:45:15.706
So, interestingly, out of the top four,

00:45:16.027 --> 00:45:16.927
one of them is the

00:45:17.188 --> 00:45:18.409
presidential election winner,

00:45:18.509 --> 00:45:20.489
which the top one at the

00:45:20.530 --> 00:45:22.311
moment is Donald Trump.

00:45:23.753 --> 00:45:26.914
But then the number four is

00:45:27.396 --> 00:45:28.597
Trump convicted of felony

00:45:28.617 --> 00:45:29.376
before election.

00:45:30.418 --> 00:45:31.539
Overwhelmingly, yes.

00:45:31.559 --> 00:45:32.059
I mean...

00:45:37.304 --> 00:45:38.144
The more interesting

00:45:38.184 --> 00:45:39.505
question really is not who

00:45:39.525 --> 00:45:40.425
wins the election,

00:45:40.465 --> 00:45:41.445
but does the Electoral

00:45:41.505 --> 00:45:44.206
College actually say, whoa,

00:45:44.286 --> 00:45:44.967
hang on a minute,

00:45:45.527 --> 00:45:46.628
you can't be president

00:45:46.967 --> 00:45:48.929
because of the other thing,

00:45:49.909 --> 00:45:50.949
which probably won't happen.

00:45:51.130 --> 00:45:51.530
I don't know.

00:45:51.550 --> 00:45:53.210
I'm not familiar enough with

00:45:53.291 --> 00:45:53.771
whether or not the

00:45:53.811 --> 00:45:55.291
Electoral College is just

00:45:57.371 --> 00:45:58.632
like a rubber stamp or

00:45:58.672 --> 00:46:00.974
whether it actually would ever say,

00:46:00.994 --> 00:46:03.054
our job is oversight and we

00:46:03.094 --> 00:46:03.914
are going to say, nope.

00:46:06.940 --> 00:46:10.762
can a can a felon be the

00:46:10.802 --> 00:46:13.226
president yes but certain

00:46:13.266 --> 00:46:15.467
types of felony disbar you

00:46:15.847 --> 00:46:21.313
right so uh when like what

00:46:21.652 --> 00:46:22.554
well actually no I don't

00:46:22.614 --> 00:46:24.514
know in the u.s I know I'm

00:46:24.594 --> 00:46:26.097
pretty certain here if

00:46:26.137 --> 00:46:27.438
you're convicted of treason

00:46:27.478 --> 00:46:28.679
or high treason you can't

00:46:28.719 --> 00:46:29.880
hold high office like it's

00:46:29.920 --> 00:46:30.621
really specific

00:46:32.809 --> 00:46:33.309
Wait, hold on.

00:46:33.329 --> 00:46:34.190
We've got to stop for a second.

00:46:34.269 --> 00:46:34.710
What's the difference

00:46:34.730 --> 00:46:35.771
between treason and high treason?

00:46:35.811 --> 00:46:36.871
I didn't realize there was a difference.

00:46:36.911 --> 00:46:38.391
I thought one was like how

00:46:38.431 --> 00:46:39.351
dramatic you were going to

00:46:39.371 --> 00:46:40.411
be when you said treason.

00:46:41.851 --> 00:46:43.672
Treason is you're going to prison.

00:46:43.751 --> 00:46:44.492
High treason is you're going

00:46:44.512 --> 00:46:45.132
to prison for life.

00:46:47.273 --> 00:46:50.034
But it's degrees of the crime.

00:46:51.273 --> 00:46:52.675
I don't know the exact definition,

00:46:52.835 --> 00:46:54.434
but I think you'd have to...

00:46:55.545 --> 00:46:56.545
I think you could probably

00:46:56.606 --> 00:46:58.067
commit treason with a fuck up,

00:46:58.266 --> 00:46:59.407
but I think you'd have to

00:46:59.527 --> 00:47:01.248
actively work against the

00:47:01.288 --> 00:47:03.887
state to commit high treason.

00:47:05.228 --> 00:47:09.449
Like you'd have to like, no,

00:47:09.469 --> 00:47:10.769
be a spy or try and

00:47:10.909 --> 00:47:13.231
assassinate somebody or something.

00:47:13.291 --> 00:47:13.650
I don't know.

00:47:14.431 --> 00:47:15.110
I think if you broke the

00:47:15.130 --> 00:47:16.050
official secrets act,

00:47:16.090 --> 00:47:17.632
that would be treason, for example.

00:47:18.172 --> 00:47:18.992
And a lot of government

00:47:19.032 --> 00:47:20.293
contractors have to sign

00:47:20.733 --> 00:47:21.893
the official secrets act.

00:47:23.757 --> 00:47:25.237
If you work on defense radar

00:47:25.318 --> 00:47:26.077
as a programmer,

00:47:26.577 --> 00:47:28.199
you could commit treason by

00:47:28.699 --> 00:47:29.340
accidentally telling

00:47:29.360 --> 00:47:30.101
somebody down the pub

00:47:30.121 --> 00:47:31.461
something about our radar system.

00:47:32.061 --> 00:47:34.003
But you're not committing

00:47:34.063 --> 00:47:36.244
high treason by telling a drunk person,

00:47:36.824 --> 00:47:38.146
we've got this great new radar.

00:47:38.545 --> 00:47:39.206
It's quite cool.

00:47:39.266 --> 00:47:40.586
I wrote some cool code for it.

00:47:41.108 --> 00:47:44.949
Whereas if you blew up a building,

00:47:45.010 --> 00:47:46.530
that would probably be high treason.

00:47:47.652 --> 00:47:49.393
I'm going to have to look this up.

00:47:49.413 --> 00:47:50.273
Well, I just looked it up.

00:47:51.663 --> 00:47:52.284
In the UK,

00:47:52.603 --> 00:47:54.746
treason can be classified into two types,

00:47:55.447 --> 00:47:57.088
high treason and petty treason.

00:47:57.509 --> 00:47:58.871
High treason is a betrayal

00:47:58.911 --> 00:48:00.172
against the sovereign monarch,

00:48:00.251 --> 00:48:02.974
while petty treason refers to disloyalty.

00:48:04.135 --> 00:48:06.679
So the sovereign monarch is the king.

00:48:06.699 --> 00:48:06.739
So...

00:48:09.864 --> 00:48:11.164
I feel like you can get high

00:48:11.204 --> 00:48:12.306
treason pretty easily.

00:48:12.326 --> 00:48:15.947
Yeah, but that's like olden times.

00:48:16.047 --> 00:48:19.630
Now it must be the state

00:48:20.010 --> 00:48:21.331
because the monarch's just

00:48:21.351 --> 00:48:22.052
the head of state.

00:48:22.592 --> 00:48:24.092
The monarch's a proxy for state.

00:48:27.175 --> 00:48:32.018
Okay, so hold on.

00:48:32.097 --> 00:48:32.318
Is he...

00:48:34.340 --> 00:48:35.402
don't know about the wording

00:48:35.442 --> 00:48:36.561
of the law maybe it is

00:48:36.681 --> 00:48:38.282
still written as as the

00:48:38.322 --> 00:48:39.164
monarch in which case

00:48:39.664 --> 00:48:40.824
that's another wild bit of

00:48:40.885 --> 00:48:42.545
british law that needs an

00:48:42.626 --> 00:48:46.487
update I didn't realize

00:48:46.547 --> 00:48:47.768
that okay you know we've

00:48:47.807 --> 00:48:50.010
talked about the uk's

00:48:51.230 --> 00:48:53.170
ridiculous royalty enough

00:48:54.431 --> 00:48:57.673
yeah those guys anyway petty treason um

00:48:59.255 --> 00:48:59.856
So, yeah,

00:48:59.876 --> 00:49:01.838
but so the equivalent thing in the US,

00:49:01.898 --> 00:49:04.699
like like I say, hypothetically,

00:49:04.719 --> 00:49:06.942
you incite an insurrection,

00:49:07.202 --> 00:49:09.123
which would be I'm pretty

00:49:09.164 --> 00:49:11.186
certain high treason in this country.

00:49:13.007 --> 00:49:14.570
If you incite an insurrection,

00:49:14.730 --> 00:49:16.972
presumably this is the

00:49:16.992 --> 00:49:17.692
interesting thing about

00:49:17.731 --> 00:49:19.114
Trump going for number two.

00:49:19.134 --> 00:49:21.315
I'm like, shouldn't like.

00:49:22.588 --> 00:49:23.327
If you incite an

00:49:23.588 --> 00:49:24.528
insurrection against the

00:49:24.608 --> 00:49:26.349
capital of the US,

00:49:26.929 --> 00:49:29.650
doesn't that automatically

00:49:29.730 --> 00:49:31.630
make you an enemy of the state?

00:49:32.291 --> 00:49:36.492
By literal constitutional

00:49:36.552 --> 00:49:38.032
criminal definition?

00:49:39.932 --> 00:49:41.452
So one thing to be aware of

00:49:41.594 --> 00:49:45.454
there is that a lot of

00:49:45.494 --> 00:49:46.514
people believe that it

00:49:46.574 --> 00:49:48.275
wasn't Trump that instigated it,

00:49:48.355 --> 00:49:49.856
but that it was Antifa.

00:49:51.552 --> 00:49:53.213
so like there isn't a single

00:49:54.034 --> 00:49:55.313
consistent story around

00:49:55.353 --> 00:49:56.574
what happened now I can

00:49:56.594 --> 00:49:57.454
tell you what I think what

00:49:57.474 --> 00:49:58.373
happened and what

00:49:58.835 --> 00:49:59.715
everything else seems to

00:49:59.755 --> 00:50:01.295
say what happened but

00:50:02.195 --> 00:50:02.954
because there's so much

00:50:02.994 --> 00:50:04.175
like shuffling of the feet

00:50:04.255 --> 00:50:07.096
around the reality nobody

00:50:07.135 --> 00:50:08.717
actually says that he

00:50:08.777 --> 00:50:11.317
instigated it that's

00:50:11.356 --> 00:50:12.737
interesting because if you

00:50:12.836 --> 00:50:14.338
read a newspaper on this

00:50:14.378 --> 00:50:15.617
side of the pond they go

00:50:16.358 --> 00:50:17.338
trump incited an

00:50:17.418 --> 00:50:19.938
insurrection in america on this day like

00:50:20.856 --> 00:50:21.976
it's that's just how it'd be

00:50:22.016 --> 00:50:25.737
talked about like I don't

00:50:25.757 --> 00:50:27.599
think even a right-wing

00:50:27.639 --> 00:50:28.639
newspaper I think would be

00:50:28.719 --> 00:50:32.360
like yep smoking gun it's

00:50:32.541 --> 00:50:34.362
like cause and effect baby

00:50:35.282 --> 00:50:37.103
you would think so but yeah

00:50:37.224 --> 00:50:38.264
I know quite a few people

00:50:38.284 --> 00:50:39.565
that think that it was

00:50:39.804 --> 00:50:41.746
actually the liberals that

00:50:42.025 --> 00:50:43.545
uh that incited the

00:50:43.626 --> 00:50:47.047
insurrection how because I

00:50:47.068 --> 00:50:47.847
didn't see many of them

00:50:47.907 --> 00:50:48.969
like storming the building

00:50:51.047 --> 00:50:54.148
exactly fox news probably uh

00:50:56.369 --> 00:50:57.791
yeah I mean that's I think

00:50:57.811 --> 00:50:58.431
that's probably like the

00:50:58.510 --> 00:51:00.371
wildest part of that entire

00:51:00.391 --> 00:51:02.213
you know disorienting

00:51:02.253 --> 00:51:03.353
period where he was the

00:51:03.393 --> 00:51:05.054
president was just the the

00:51:05.114 --> 00:51:06.275
idea that some people could

00:51:06.635 --> 00:51:08.956
read the word antifa which

00:51:09.016 --> 00:51:09.556
obviously means

00:51:09.677 --> 00:51:10.557
anti-fascist or

00:51:10.617 --> 00:51:12.438
anti-fascist action and go

00:51:12.639 --> 00:51:14.760
yep those guys must be the

00:51:14.800 --> 00:51:17.340
bad guys and be like okay

00:51:17.380 --> 00:51:18.461
let's take a step back

00:51:19.735 --> 00:51:21.976
And remember that time there

00:51:21.996 --> 00:51:23.679
was a bit of a hoo-ha in

00:51:23.798 --> 00:51:25.721
Europe for about five years.

00:51:27.041 --> 00:51:28.764
There was a bit of anti-fascist action,

00:51:28.844 --> 00:51:29.503
as I recall.

00:51:29.684 --> 00:51:31.405
And I still enjoy many video

00:51:31.445 --> 00:51:32.507
games on the subject.

00:51:33.407 --> 00:51:35.389
And I've noticed in those

00:51:35.449 --> 00:51:37.952
video games that the people

00:51:37.972 --> 00:51:38.833
participating in

00:51:38.893 --> 00:51:40.635
anti-fascist action tend to

00:51:40.675 --> 00:51:41.494
be the heroes.

00:51:43.929 --> 00:51:45.170
I did know that was one.

00:51:45.210 --> 00:51:46.429
I think it was quite subtle

00:51:46.469 --> 00:51:48.371
subtext in Saving Private Ryan as well.

00:51:48.411 --> 00:51:49.632
But I think that... Yeah,

00:51:49.711 --> 00:51:50.693
one small takeaway.

00:51:50.713 --> 00:51:52.833
I think one small takeaway

00:51:52.893 --> 00:51:55.135
from that film would be that in general,

00:51:55.215 --> 00:51:57.436
the Antifa were the good guys.

00:51:57.815 --> 00:52:01.338
And I think that it's very subtle, right?

00:52:01.757 --> 00:52:03.338
The condemnation of the other side.

00:52:03.639 --> 00:52:04.880
They do like to try and present...

00:52:06.411 --> 00:52:08.050
balance but I think it's

00:52:08.092 --> 00:52:08.751
quite clear that you're

00:52:08.771 --> 00:52:10.112
supposed to root for for

00:52:10.152 --> 00:52:11.632
tom hanks I know normally

00:52:11.652 --> 00:52:12.932
he plays the bad guy so you

00:52:12.972 --> 00:52:15.534
know it's he's not a very

00:52:15.594 --> 00:52:17.034
likable actor is he so like

00:52:17.074 --> 00:52:17.713
I think you know they

00:52:17.773 --> 00:52:18.594
deliberately they tried to

00:52:18.675 --> 00:52:19.815
even it out with that you

00:52:19.855 --> 00:52:20.534
know so you wouldn't

00:52:20.574 --> 00:52:21.675
automatically gravitate

00:52:21.695 --> 00:52:22.615
towards his point of view

00:52:22.735 --> 00:52:24.956
but they also put vin

00:52:24.996 --> 00:52:26.137
diesel on that side as well

00:52:26.157 --> 00:52:26.916
and you're just like you

00:52:26.956 --> 00:52:28.918
can't trust vin diesel one

00:52:28.938 --> 00:52:29.657
minute he's like unless

00:52:29.677 --> 00:52:31.737
he's in triple x hey

00:52:34.141 --> 00:52:35.641
Were there two XXXs,

00:52:35.681 --> 00:52:36.822
or did I hallucinate that?

00:52:37.581 --> 00:52:38.121
I think there were,

00:52:38.161 --> 00:52:38.981
but I think Vin Diesel was

00:52:39.021 --> 00:52:39.802
only in the first one.

00:52:40.862 --> 00:52:41.543
Was that the one we were

00:52:41.563 --> 00:52:43.182
supposed to set in Prague, and it had,

00:52:43.242 --> 00:52:44.262
like, Rammstein in it?

00:52:44.503 --> 00:52:46.204
It was, like, kind of okay.

00:52:46.943 --> 00:52:48.443
Yeah, I remember enjoying it when I was,

00:52:48.483 --> 00:52:48.623
like, 12.

00:52:48.623 --> 00:52:51.125
Yeah, it was, like, okay.

00:52:51.204 --> 00:52:52.684
I mean, it wasn't The Rock,

00:52:52.764 --> 00:52:53.344
but it was fine.

00:52:53.364 --> 00:52:56.246
I'm sure the second one had

00:52:56.286 --> 00:52:57.565
him in it as well.

00:52:58.666 --> 00:52:59.126
Yeah, it did.

00:52:59.146 --> 00:52:59.666
100% did.

00:52:59.686 --> 00:52:59.726
So...

00:53:03.943 --> 00:53:06.105
We're done with betting on SPF?

00:53:07.085 --> 00:53:07.346
Yeah.

00:53:07.865 --> 00:53:08.827
We're done with betting on SPF.

00:53:08.847 --> 00:53:13.750
So the second one... Oh, hold up.

00:53:13.809 --> 00:53:14.831
Okay, please.

00:53:15.030 --> 00:53:17.733
Do not search XXX movie.

00:53:21.114 --> 00:53:22.536
Wow, I could have told you that one.

00:53:23.382 --> 00:53:24.565
Why did that not occur to me?

00:53:24.585 --> 00:53:27.349
Try triple X Vin Diesel.

00:53:27.610 --> 00:53:28.311
See if that helps.

00:53:29.414 --> 00:53:29.574
Look,

00:53:29.695 --> 00:53:31.518
I'm aware that I am the guy that just

00:53:31.538 --> 00:53:33.661
searched Pear Man fucked his orange wife.

00:53:35.304 --> 00:53:36.467
And didn't have a good time.

00:53:38.487 --> 00:53:40.248
But your search is even more

00:53:40.307 --> 00:53:41.748
obviously going to end in a bad time.

00:53:42.309 --> 00:53:43.369
Hold on.

00:53:43.929 --> 00:53:44.670
We got to go back to that

00:53:44.750 --> 00:53:45.291
just a little bit.

00:53:45.630 --> 00:53:46.510
When you say pair,

00:53:46.590 --> 00:53:47.552
do you mean like pair as in

00:53:47.592 --> 00:53:49.152
a pair of men or pair as in

00:53:49.193 --> 00:53:50.393
like the fruit?

00:53:50.873 --> 00:53:51.773
The fruit, obviously.

00:53:52.293 --> 00:53:52.855
Okay.

00:53:52.914 --> 00:53:54.496
Why is that obviously?

00:53:54.516 --> 00:53:57.536
It must be a pair of shades men, right?

00:53:58.117 --> 00:53:58.878
I think it's one fruit

00:53:58.938 --> 00:54:00.798
fucking the other one is

00:54:00.818 --> 00:54:01.980
the intention of the drill tweet,

00:54:02.079 --> 00:54:02.320
I think.

00:54:03.442 --> 00:54:04.563
got it I got stuck on the

00:54:04.583 --> 00:54:06.103
whole orange shade thing

00:54:06.164 --> 00:54:07.304
and so then which makes me

00:54:07.324 --> 00:54:08.364
immediately go to trump so

00:54:08.405 --> 00:54:10.346
I was just trying to like I

00:54:10.385 --> 00:54:11.746
think I think it was kind

00:54:11.806 --> 00:54:15.349
of like a sort of I think

00:54:15.429 --> 00:54:17.289
it may have been okay don't

00:54:17.329 --> 00:54:18.349
read too much into drill

00:54:18.369 --> 00:54:19.451
tweets it's been a long

00:54:19.490 --> 00:54:20.711
working day for for this

00:54:20.771 --> 00:54:21.771
guy and clearly he's

00:54:21.811 --> 00:54:23.172
overthinking this but I

00:54:23.213 --> 00:54:24.072
think maybe it was some

00:54:24.112 --> 00:54:25.494
kind of satirical statement

00:54:25.934 --> 00:54:30.577
on um no it wasn't what I'm tired I'm not

00:54:31.072 --> 00:54:31.891
I'm not even going to finish

00:54:31.911 --> 00:54:32.413
that statement.

00:54:33.012 --> 00:54:33.373
Anyway,

00:54:33.572 --> 00:54:34.974
so other funny thing that happened

00:54:35.014 --> 00:54:35.414
this week.

00:54:36.675 --> 00:54:39.275
It's not fucking satire or anything, Frey,

00:54:39.396 --> 00:54:40.016
is it?

00:54:40.237 --> 00:54:41.217
It's just a drill tweet.

00:54:41.257 --> 00:54:42.097
It doesn't mean anything.

00:54:42.637 --> 00:54:44.639
It's just monkey sitting typewriters.

00:54:44.798 --> 00:54:45.119
Anyway,

00:54:46.480 --> 00:54:48.521
two Binance execs were detained in

00:54:48.581 --> 00:54:50.521
Nigeria the other week because, you know,

00:54:50.541 --> 00:54:53.184
this whole money laundering thing.

00:54:53.503 --> 00:54:54.583
I don't know if it's like

00:54:54.704 --> 00:54:56.184
the government exercising

00:54:56.264 --> 00:54:57.126
arbitrary control

00:54:59.030 --> 00:55:00.213
not clued up enough on the

00:55:00.253 --> 00:55:01.173
internal politics of

00:55:01.213 --> 00:55:02.295
Nigeria at this current

00:55:02.396 --> 00:55:04.699
time to make a call on that.

00:55:05.139 --> 00:55:07.864
But one of them,

00:55:08.204 --> 00:55:09.766
it's Ramadan at the moment,

00:55:09.925 --> 00:55:11.588
one of them asked to go to mosque

00:55:13.817 --> 00:55:15.317
And then slipped his captors

00:55:15.376 --> 00:55:16.458
and escaped the fucking

00:55:16.498 --> 00:55:18.318
country like James Bond style.

00:55:18.338 --> 00:55:20.699
This Binance exec.

00:55:21.418 --> 00:55:22.978
And fucking escaped the

00:55:23.018 --> 00:55:24.599
country and gone like that.

00:55:24.960 --> 00:55:25.239
Woosh.

00:55:25.840 --> 00:55:27.059
Presumably just like, oh,

00:55:27.159 --> 00:55:30.701
I need to go do a bit of

00:55:30.740 --> 00:55:33.141
praying as is right at this time of year.

00:55:34.521 --> 00:55:35.782
Nipped to the toilet for a slash.

00:55:36.702 --> 00:55:38.643
Did the cartoon thing of

00:55:38.682 --> 00:55:40.103
climbing out the toilet window.

00:55:40.483 --> 00:55:41.684
Runs to the airport.

00:55:42.304 --> 00:55:42.864
And yeah.

00:55:43.099 --> 00:55:45.204
fucking A. Do you think he

00:55:45.264 --> 00:55:47.869
was playing... It sounds

00:55:47.949 --> 00:55:49.974
like he was collected by the CIA.

00:55:55.018 --> 00:55:55.197
Well,

00:55:55.217 --> 00:55:57.420
you would think... I think both of

00:55:57.500 --> 00:55:58.800
the... Maybe both the execs

00:55:59.221 --> 00:56:00.021
are... I think both of them

00:56:00.101 --> 00:56:01.443
are actually American citizens.

00:56:01.503 --> 00:56:02.563
So you would think that

00:56:03.123 --> 00:56:04.244
potentially there would be

00:56:04.364 --> 00:56:06.186
somebody from the US

00:56:06.226 --> 00:56:07.507
government making contact

00:56:07.527 --> 00:56:08.788
with them to be like, hey, if you can,

00:56:08.827 --> 00:56:09.688
slip your captors.

00:56:10.409 --> 00:56:11.210
And the only thing that made

00:56:11.250 --> 00:56:12.670
me think that it was just

00:56:12.811 --> 00:56:13.670
completely independently

00:56:13.731 --> 00:56:14.952
done and maybe he had just

00:56:15.012 --> 00:56:16.052
cashed down his pants or

00:56:16.072 --> 00:56:18.534
whatever was that it was

00:56:18.875 --> 00:56:20.135
specifically... I think

00:56:20.175 --> 00:56:20.936
specifically they...

00:56:21.916 --> 00:56:23.277
He managed to jump a flight

00:56:23.297 --> 00:56:25.099
basically to somewhere in the Middle East,

00:56:25.219 --> 00:56:26.840
just like a relatively

00:56:27.159 --> 00:56:29.740
short haul connecting flight.

00:56:30.222 --> 00:56:31.302
So it might have been a case

00:56:31.322 --> 00:56:32.182
of literally just being like,

00:56:32.262 --> 00:56:33.282
what's the nearest flight

00:56:33.302 --> 00:56:34.583
that he's leaving in an hour?

00:56:35.083 --> 00:56:36.744
And I have the money down my

00:56:36.764 --> 00:56:37.706
pants to pay for.

00:56:38.585 --> 00:56:39.786
Well, well,

00:56:39.867 --> 00:56:41.807
did he even need money down his pants?

00:56:41.927 --> 00:56:43.128
Like,

00:56:44.670 --> 00:56:46.791
all he had to do was go to the crypto

00:56:46.871 --> 00:56:48.731
ATM and punch in his seed phrase.

00:56:49.519 --> 00:56:50.641
be fair he must have had his

00:56:50.681 --> 00:56:51.661
passport with him to get on

00:56:51.681 --> 00:56:52.822
the plane so maybe it was

00:56:52.862 --> 00:56:53.782
simply enough to go up to

00:56:53.824 --> 00:56:55.405
the desk and be like look I

00:56:55.525 --> 00:56:56.346
have been detained by the

00:56:56.385 --> 00:56:58.967
government unlawfully here

00:56:59.027 --> 00:57:01.128
is my passport let me get

00:57:01.188 --> 00:57:02.409
on this plane you will be

00:57:02.469 --> 00:57:03.590
repaid by the binance

00:57:03.630 --> 00:57:06.494
corporation I i have to say

00:57:06.514 --> 00:57:08.375
on what country would that

00:57:08.434 --> 00:57:09.976
work going up to the teller

00:57:10.016 --> 00:57:11.097
and be like look your

00:57:11.177 --> 00:57:12.077
country is holding me

00:57:12.137 --> 00:57:13.978
hostage I'd like to off now

00:57:14.500 --> 00:57:15.400
can I get on a flight

00:57:16.302 --> 00:57:18.083
It certainly would work in Australia.

00:57:18.123 --> 00:57:19.304
There's people who are paid

00:57:19.344 --> 00:57:20.023
by the airline.

00:57:21.943 --> 00:57:23.043
I don't know.

00:57:23.063 --> 00:57:23.684
Either way.

00:57:23.744 --> 00:57:25.425
I feel like that's some kind of treason.

00:57:26.525 --> 00:57:27.224
It probably is.

00:57:27.405 --> 00:57:27.925
Who knows?

00:57:30.125 --> 00:57:32.925
Well, yeah, it is aiding and abetting,

00:57:32.965 --> 00:57:33.346
isn't it?

00:57:33.505 --> 00:57:36.266
It is aiding and abetting.

00:57:36.286 --> 00:57:37.527
So anyway,

00:57:38.327 --> 00:57:39.306
one of them is still in

00:57:39.387 --> 00:57:40.666
captivity in Nigeria.

00:57:40.706 --> 00:57:41.786
The funny thing being the

00:57:41.887 --> 00:57:42.666
one that is still in

00:57:42.706 --> 00:57:44.228
captivity is apparently...

00:57:46.489 --> 00:57:48.050
one of the main voices in

00:57:48.110 --> 00:57:50.793
Binance who actually is

00:57:50.853 --> 00:57:52.313
responsible for dealing

00:57:52.333 --> 00:57:53.534
with money laundering so

00:57:55.317 --> 00:58:00.380
yeah basically whatever's

00:58:00.420 --> 00:58:06.425
going on with that but I

00:58:06.445 --> 00:58:08.967
just like the idea of some

00:58:10.128 --> 00:58:11.849
crypto finance bro who's

00:58:11.889 --> 00:58:15.193
like working for a massive crypto company

00:58:15.922 --> 00:58:16.862
in a shirt and tie,

00:58:17.101 --> 00:58:18.523
doing a James Bond out of a

00:58:19.123 --> 00:58:20.884
toilet window to escape from Nigeria.

00:58:22.284 --> 00:58:23.965
I can say for certain that I

00:58:24.005 --> 00:58:24.664
would have had Mission

00:58:24.684 --> 00:58:25.945
Impossible music playing in

00:58:25.985 --> 00:58:27.465
my mind when I was escaping.

00:58:28.527 --> 00:58:29.427
Not James Bond.

00:58:30.927 --> 00:58:31.628
I would have been running

00:58:31.668 --> 00:58:33.168
down the street going, fuck, fuck, fuck,

00:58:33.208 --> 00:58:37.969
fuck, fuck, fuck, fuck, fuck, fuck.

00:58:37.989 --> 00:58:39.150
Do you remember the first

00:58:39.210 --> 00:58:40.190
Mission Impossible film

00:58:40.251 --> 00:58:43.452
with Tom Cruise in it?

00:58:44.492 --> 00:58:45.092
It was a good film.

00:58:45.989 --> 00:58:46.449
It was great.

00:58:46.570 --> 00:58:46.769
I mean,

00:58:46.809 --> 00:58:48.610
I've enjoyed all the ones I've watched.

00:58:48.630 --> 00:58:51.211
The one where he came down the finger,

00:58:51.271 --> 00:58:51.693
right?

00:58:52.612 --> 00:58:52.913
Yeah.

00:58:53.873 --> 00:58:58.074
It's actually aged really well.

00:58:58.815 --> 00:58:58.956
I mean,

00:58:58.976 --> 00:58:59.936
all the other ones are kind of shit,

00:59:00.255 --> 00:59:01.556
but that one's aged really, really well.

00:59:02.677 --> 00:59:03.617
It's amazing that they're

00:59:03.657 --> 00:59:05.099
able to just delete his

00:59:05.159 --> 00:59:06.918
shortness in those films.

00:59:08.679 --> 00:59:09.641
And his center tooth.

00:59:11.300 --> 00:59:12.762
They have so many tricks, don't they?

00:59:13.922 --> 00:59:14.762
His what, Schultzy?

00:59:15.996 --> 00:59:16.516
Center tooth.

00:59:16.536 --> 00:59:17.436
Have you not noticed that?

00:59:17.976 --> 00:59:19.237
Tom Cruise has a tooth right

00:59:19.277 --> 00:59:19.759
in the center.

00:59:21.280 --> 00:59:22.840
I shit you not.

00:59:23.121 --> 00:59:23.581
Look it up.

00:59:24.121 --> 00:59:25.182
They try to always get him

00:59:25.382 --> 00:59:26.342
at an angle like this

00:59:26.443 --> 00:59:27.744
because if you get an angle like this,

00:59:28.105 --> 00:59:28.965
you don't see the center tooth.

00:59:28.985 --> 00:59:30.786
But if you do see it from straight on,

00:59:31.166 --> 00:59:32.268
he has a tooth right in the middle.

00:59:34.708 --> 00:59:36.570
There's like two scenes I've seen.

00:59:36.610 --> 00:59:37.831
I think one's in Top Gun,

00:59:37.851 --> 00:59:39.913
the original Top Gun, and I think Legend.

00:59:40.132 --> 00:59:40.793
I think those are the two

00:59:40.813 --> 00:59:41.434
movies I've seen it.

00:59:43.275 --> 00:59:43.856
Oh my god.

00:59:45.255 --> 00:59:46.956
this uh this search did not

00:59:47.016 --> 00:59:50.697
yield porn which is nice oh

00:59:50.737 --> 00:59:52.378
yeah yeah it is right bang

00:59:52.398 --> 00:59:53.157
in the fucking middle

00:59:53.878 --> 00:59:55.458
that's a bit weird isn't

00:59:55.498 --> 01:00:00.079
that strange I'll never

01:00:00.099 --> 01:00:01.139
look at him the same again

01:00:01.159 --> 01:00:02.521
he's short and got a center

01:00:02.541 --> 01:00:05.340
tooth weirdo yeah what's

01:00:05.380 --> 01:00:07.501
the secret to tom cruise's uni tooth

01:00:11.876 --> 01:00:13.398
Tom Cruise's teeth have been

01:00:13.418 --> 01:00:16.498
at the center of rumors and

01:00:16.539 --> 01:00:17.679
controversies.

01:00:19.139 --> 01:00:19.500
Wow.

01:00:19.780 --> 01:00:22.420
Copywriter, their shit salary this day.

01:00:23.141 --> 01:00:23.721
Amazing.

01:00:24.860 --> 01:00:25.722
What else is in the news?

01:00:25.782 --> 01:00:26.161
The fray.

01:00:30.077 --> 01:00:32.119
Do you hear about the Celsius thing?

01:00:32.159 --> 01:00:33.721
They're basically clawing

01:00:33.760 --> 01:00:34.460
back money from their

01:00:34.521 --> 01:00:36.362
customers to pay their other customers.

01:00:36.382 --> 01:00:37.123
That's pretty funny.

01:00:38.184 --> 01:00:39.405
I think that's really bizarre.

01:00:39.704 --> 01:00:40.204
First of all,

01:00:40.286 --> 01:00:41.505
because I was one of the

01:00:41.545 --> 01:00:42.746
customers getting paid back.

01:00:43.148 --> 01:00:44.588
Yeah, I had money in there.

01:00:44.668 --> 01:00:45.188
Not a lot,

01:00:45.688 --> 01:00:49.112
but enough that I actually got the payout,

01:00:49.552 --> 01:00:50.873
I don't know, two weeks ago for it.

01:00:52.393 --> 01:00:53.635
I don't understand the clawback thing.

01:00:53.655 --> 01:00:53.994
Apparently,

01:00:54.034 --> 01:00:55.936
customers that had over 100,000 withdrawn,

01:00:55.976 --> 01:00:57.277
they want to pull back?

01:00:57.438 --> 01:00:57.617
What?

01:00:59.224 --> 01:01:00.164
So, right,

01:01:00.204 --> 01:01:02.027
my limited understanding of this,

01:01:02.106 --> 01:01:03.108
what happened is there are

01:01:03.128 --> 01:01:03.748
a certain amount of

01:01:03.827 --> 01:01:05.188
customers that just before

01:01:05.228 --> 01:01:06.250
it imploded could tell it

01:01:06.289 --> 01:01:06.990
was going to implode.

01:01:07.070 --> 01:01:08.371
So we drew their money and

01:01:08.391 --> 01:01:09.532
that accelerated the

01:01:09.572 --> 01:01:12.275
implosion of the company, right?

01:01:13.597 --> 01:01:15.518
Which is a bank run, right?

01:01:15.619 --> 01:01:17.079
And they had their pants down.

01:01:17.099 --> 01:01:19.001
I don't think anybody

01:01:19.061 --> 01:01:20.083
reasonable has any fucking

01:01:20.123 --> 01:01:22.003
sympathy for these fucks anyway.

01:01:22.907 --> 01:01:23.807
they're now obviously trying

01:01:23.827 --> 01:01:26.210
to repay people that lost money.

01:01:26.769 --> 01:01:27.731
And so they're getting in

01:01:27.771 --> 01:01:28.871
touch with people that did

01:01:28.911 --> 01:01:30.353
those large withdrawals in

01:01:30.373 --> 01:01:31.554
the run up to it,

01:01:31.574 --> 01:01:32.795
specifically like the final

01:01:32.856 --> 01:01:34.416
day or the final few hours

01:01:34.456 --> 01:01:35.518
when it was falling apart.

01:01:36.217 --> 01:01:37.199
And they are saying,

01:01:37.639 --> 01:01:39.701
we are inviting you to give

01:01:39.760 --> 01:01:41.222
the money back so that we

01:01:41.242 --> 01:01:42.403
can repay our customers.

01:01:42.704 --> 01:01:43.405
And if you don't,

01:01:43.965 --> 01:01:45.246
we're going to pursue legal

01:01:45.326 --> 01:01:46.547
action against you which

01:01:46.586 --> 01:01:47.648
begs the fucking question

01:01:48.009 --> 01:01:49.250
you and whose fucking army

01:01:49.369 --> 01:01:50.231
because if all of those

01:01:50.251 --> 01:01:51.512
people get together and go

01:01:51.532 --> 01:01:53.333
yeah okay we'll fucking see

01:01:53.353 --> 01:01:54.114
you in court well then

01:01:54.134 --> 01:01:54.715
these guys are going to

01:01:54.775 --> 01:01:55.655
fold like a packet of

01:01:55.715 --> 01:01:56.516
crisps because they're

01:01:56.536 --> 01:01:57.878
already fucking bankrupt

01:01:58.277 --> 01:01:59.518
it's not like they've oh

01:01:59.559 --> 01:02:01.420
yeah it's us and a fucking

01:02:01.501 --> 01:02:02.641
army behind us it's like no

01:02:02.702 --> 01:02:03.802
it's you in a bankruptcy

01:02:03.842 --> 01:02:05.083
court and like some fucking

01:02:05.123 --> 01:02:06.826
court appointed lawyers or whatever like

01:02:08.862 --> 01:02:09.943
doesn't bear it doesn't it's

01:02:09.963 --> 01:02:10.784
not like the the most

01:02:10.844 --> 01:02:11.603
terrifying thing in the

01:02:11.643 --> 01:02:12.903
world as far as I can tell

01:02:12.943 --> 01:02:14.244
I mean because presumably

01:02:14.364 --> 01:02:15.525
people that were that were

01:02:15.545 --> 01:02:16.565
taken out more than four

01:02:16.585 --> 01:02:17.405
hundred thousand dollars

01:02:17.766 --> 01:02:19.226
were institutions like if

01:02:19.246 --> 01:02:21.067
you're a hedge fund or

01:02:21.086 --> 01:02:22.266
something and fucking

01:02:22.306 --> 01:02:23.407
celsius come up to you and

01:02:23.427 --> 01:02:24.487
they're like we're shaking

01:02:24.527 --> 01:02:26.007
you down for 600 grand or

01:02:26.027 --> 01:02:27.849
something you'd be like yeah fuck off

01:02:29.559 --> 01:02:30.840
And what kind of leg would

01:02:30.860 --> 01:02:32.360
they have to stand on in court, right?

01:02:32.380 --> 01:02:32.721
They'd be like,

01:02:32.740 --> 01:02:33.621
I'm going to take you to court.

01:02:34.222 --> 01:02:36.202
Under what pretext, first of all?

01:02:36.222 --> 01:02:36.922
Under second of all,

01:02:37.282 --> 01:02:37.963
you're going to go after

01:02:37.983 --> 01:02:38.983
the people that have the

01:02:39.023 --> 01:02:39.884
money to fight back?

01:02:41.085 --> 01:02:41.244
Yeah.

01:02:41.724 --> 01:02:42.184
And also, like,

01:02:42.284 --> 01:02:43.925
what jurisdiction would that work in?

01:02:43.985 --> 01:02:45.586
It's like, yeah, okay,

01:02:45.947 --> 01:02:46.827
you can sue people for a

01:02:46.847 --> 01:02:48.447
whole bunch of shit in the US, but, like,

01:02:48.547 --> 01:02:50.068
try it in a bunch of other jurisdictions,

01:02:50.128 --> 01:02:52.150
and people are going to be like, yeah,

01:02:52.190 --> 01:02:52.869
come at me, bro.

01:02:53.010 --> 01:02:53.190
Like,

01:02:53.210 --> 01:02:55.110
you're going to get thrown out of court,

01:02:55.231 --> 01:02:55.871
and you're going to be made

01:02:55.891 --> 01:02:56.751
to pay my costs.

01:02:56.992 --> 01:02:57.152
So...

01:03:00.070 --> 01:03:02.210
yeah it's super weird isn't

01:03:02.271 --> 01:03:04.532
it like but I i do like

01:03:04.811 --> 01:03:06.092
this is the insanity of

01:03:06.152 --> 01:03:07.692
like oh we have to repay

01:03:07.751 --> 01:03:08.853
people so we're gonna like

01:03:09.072 --> 01:03:10.172
threaten to sue the people

01:03:10.213 --> 01:03:12.472
that didn't lose money ah

01:03:15.853 --> 01:03:17.074
love it absolutely love it

01:03:17.114 --> 01:03:19.235
it's it's it's peaks what

01:03:19.295 --> 01:03:20.815
is it circle bankruptcy I

01:03:20.855 --> 01:03:22.315
don't know it's it's

01:03:22.355 --> 01:03:24.615
something like that it's

01:03:24.635 --> 01:03:26.115
it's sometimes bankruptcy

01:03:26.900 --> 01:03:27.800
it's some kind of it's some

01:03:27.840 --> 01:03:29.083
kind of circle jerk like

01:03:29.202 --> 01:03:30.264
like every like every

01:03:30.304 --> 01:03:31.505
situation and every drama

01:03:31.545 --> 01:03:32.507
and crypto but I'm not sure

01:03:32.567 --> 01:03:33.708
quite quite the definition

01:03:33.748 --> 01:03:37.853
of this one so um yeah do

01:03:37.873 --> 01:03:38.494
you want to do it do you

01:03:38.514 --> 01:03:39.476
want to crack out piece of

01:03:39.516 --> 01:03:40.717
news now get out the get

01:03:40.737 --> 01:03:41.697
out the spreadsheet do some

01:03:41.717 --> 01:03:44.201
honest work fuck me I have

01:03:44.240 --> 01:03:45.143
to load up the spreadsheet

01:03:48.166 --> 01:03:52.751
I noticed that usurper who's

01:03:52.771 --> 01:03:53.612
supposed to be on fucking

01:03:53.632 --> 01:03:54.572
holiday and is probably

01:03:54.612 --> 01:03:55.673
listening to this podcast

01:03:55.693 --> 01:03:56.954
this exact fucking second

01:03:57.615 --> 01:04:00.117
uh is in the spreadsheet

01:04:00.498 --> 01:04:02.559
looking at the news so go

01:04:03.521 --> 01:04:04.402
back to your holiday you

01:04:04.442 --> 01:04:05.382
said but what the hell man

01:04:05.583 --> 01:04:06.844
be on the podcast or be on

01:04:06.884 --> 01:04:09.686
holiday enjoy your uh

01:04:09.927 --> 01:04:13.210
Magito and um and pool

01:04:16.552 --> 01:04:17.373
You haven't put a cross

01:04:17.393 --> 01:04:18.514
through the ones that you've read, dude.

01:04:19.554 --> 01:04:21.255
We could talk about CosmWasm

01:04:21.315 --> 01:04:21.996
on the Hub again.

01:04:23.557 --> 01:04:23.757
Wait,

01:04:23.958 --> 01:04:26.019
did we have CosmWasm on the Hub drama

01:04:26.079 --> 01:04:26.739
last time?

01:04:26.940 --> 01:04:27.860
At the time before?

01:04:28.021 --> 01:04:29.041
At the time before that?

01:04:31.443 --> 01:04:31.623
Well,

01:04:31.664 --> 01:04:33.005
now there's actually a vote up for it.

01:04:33.824 --> 01:04:34.346
Will it pass?

01:04:36.146 --> 01:04:37.128
Right now it's at a yes,

01:04:37.407 --> 01:04:39.489
but only 8% turnout so far.

01:04:40.630 --> 01:04:42.931
So probably not, but there is turnout.

01:04:45.905 --> 01:04:47.967
I mean, as we've said before,

01:04:48.027 --> 01:04:49.347
if you get Cosmos on the hub,

01:04:49.387 --> 01:04:50.969
then maybe the hub will have a purpose.

01:04:51.989 --> 01:04:52.550
But probably not.

01:04:53.871 --> 01:04:55.311
That's kind of my take as well.

01:04:55.873 --> 01:04:56.592
It needs something.

01:04:57.594 --> 01:04:59.135
Can that something not just

01:04:59.175 --> 01:05:02.257
be... With full

01:05:02.277 --> 01:05:03.518
understanding that we already voted yes.

01:05:03.878 --> 01:05:05.480
So with that context,

01:05:07.701 --> 01:05:08.362
I see it as a good thing.

01:05:17.467 --> 01:05:18.427
No, you have no take there.

01:05:18.487 --> 01:05:21.469
You have no opinions on whether I don't,

01:05:22.570 --> 01:05:23.831
I don't validate the hub

01:05:24.032 --> 01:05:25.673
and thus don't give a fuck.

01:05:27.295 --> 01:05:27.695
Beautiful.

01:05:28.655 --> 01:05:28.815
Um,

01:05:29.916 --> 01:05:32.318
but don't they have cause and wasn't like,

01:05:32.358 --> 01:05:33.380
you know, neutral.

01:05:33.679 --> 01:05:35.501
It's basically, well, yeah.

01:05:35.561 --> 01:05:37.163
So that's the main argument

01:05:37.202 --> 01:05:38.083
against cause and wasn't

01:05:38.123 --> 01:05:39.824
the hub is that giving it

01:05:39.885 --> 01:05:42.686
to putting on the hub means

01:05:42.726 --> 01:05:44.367
it takes away from neutron.

01:05:45.208 --> 01:05:45.329
Um,

01:05:46.809 --> 01:05:48.309
And the problem with that is

01:05:48.931 --> 01:05:49.711
that still doesn't give

01:05:49.771 --> 01:05:52.713
Cosmos have a purpose.

01:05:53.454 --> 01:05:54.356
If they start moving forward

01:05:54.376 --> 01:05:55.836
with getting IBC going and

01:05:55.856 --> 01:05:57.219
getting fees going on it,

01:05:57.418 --> 01:05:59.179
I think that the hub would

01:05:59.219 --> 01:06:00.621
have a lot more purpose and

01:06:00.641 --> 01:06:03.083
suddenly have actual funding methods.

01:06:03.603 --> 01:06:04.144
Until then,

01:06:04.164 --> 01:06:07.748
it still is completely worthless.

01:06:08.128 --> 01:06:11.130
When you say IBC in that situation,

01:06:11.190 --> 01:06:11.592
what do you mean?

01:06:13.945 --> 01:06:14.786
The fee middleware.

01:06:14.945 --> 01:06:16.286
The fee middleware for IBC.

01:06:17.088 --> 01:06:18.108
So there's actual revenue

01:06:18.128 --> 01:06:18.849
streams coming in.

01:06:19.389 --> 01:06:20.331
Right now there's no way the

01:06:20.391 --> 01:06:22.052
Cosmos have to actually

01:06:22.072 --> 01:06:23.034
have revenue streams.

01:06:23.393 --> 01:06:24.976
So the funny thing about

01:06:25.235 --> 01:06:26.978
that particular revenue stream model,

01:06:27.257 --> 01:06:28.358
and I appreciate that

01:06:28.398 --> 01:06:29.519
relayers are currently

01:06:29.579 --> 01:06:30.021
running loads of

01:06:30.061 --> 01:06:30.721
infrastructure and not

01:06:30.740 --> 01:06:31.681
getting fucking paid for it.

01:06:31.922 --> 01:06:32.922
I do get that.

01:06:32.943 --> 01:06:33.804
I do understand that.

01:06:33.824 --> 01:06:36.166
I do understand that it can't scale.

01:06:38.768 --> 01:06:39.028
You know,

01:06:39.048 --> 01:06:41.429
like how the major internet trunk

01:06:41.449 --> 01:06:42.751
providers like shuffle

01:06:42.771 --> 01:06:43.931
around packets and whatnot

01:06:44.251 --> 01:06:46.032
is that when they hit each

01:06:46.072 --> 01:06:47.032
other's infrastructure,

01:06:47.112 --> 01:06:49.713
they just take each other's traffic.

01:06:53.195 --> 01:06:58.079
So it's kind of back to the, like,

01:06:58.159 --> 01:06:59.059
I wrote a very sleep

01:06:59.099 --> 01:06:59.960
deprived and like half

01:07:00.019 --> 01:07:01.559
baked a blog post the other

01:07:01.599 --> 01:07:02.121
week about how.

01:07:03.322 --> 01:07:05.905
um ibc stateful right it has

01:07:05.945 --> 01:07:06.786
to be in order to do the

01:07:06.806 --> 01:07:08.686
packet exchange um it's

01:07:08.706 --> 01:07:10.887
like you know it's request

01:07:11.228 --> 01:07:13.610
act act type type thing

01:07:14.050 --> 01:07:15.931
it's inherently stateful um

01:07:16.411 --> 01:07:17.753
relay is a stateful right

01:07:17.952 --> 01:07:20.715
it's volatile but um but

01:07:20.755 --> 01:07:22.315
stateful resulting in an

01:07:22.516 --> 01:07:26.659
end right and am I think

01:07:26.699 --> 01:07:27.460
what's the blockchain I'm

01:07:27.480 --> 01:07:28.661
thinking of is well it's

01:07:28.681 --> 01:07:30.541
not even actually a blockchain but um

01:07:34.380 --> 01:07:36.344
I might be thinking of

01:07:36.463 --> 01:07:38.947
Arbitrum where there is a

01:07:39.007 --> 01:07:41.231
concept like relayers and

01:07:43.672 --> 01:07:45.233
They shuffle the packets

01:07:45.253 --> 01:07:46.594
between nodes and then the

01:07:46.653 --> 01:07:48.195
writing to the blockchain

01:07:48.235 --> 01:07:49.735
is like an afterthought, right?

01:07:50.916 --> 01:07:55.719
But the protocol is the network, I suppose,

01:07:55.918 --> 01:07:56.440
in that sense.

01:07:56.460 --> 01:07:58.141
Like as in the people that

01:07:58.181 --> 01:07:59.882
would do exchange between

01:08:00.101 --> 01:08:01.563
any system at the edge,

01:08:01.643 --> 01:08:03.083
like a different protocol,

01:08:03.164 --> 01:08:04.043
a different network,

01:08:04.063 --> 01:08:05.025
a different blockchain.

01:08:05.728 --> 01:08:07.070
are also inherently

01:08:07.269 --> 01:08:09.170
incentivized as a part of

01:08:09.530 --> 01:08:10.710
like it's part and parcel

01:08:10.731 --> 01:08:13.231
of being a node operator is

01:08:13.271 --> 01:08:14.952
that you have like the

01:08:15.012 --> 01:08:16.092
protocol itself is an

01:08:16.153 --> 01:08:17.773
interop layer like there

01:08:18.313 --> 01:08:19.613
and it just so happens that

01:08:19.793 --> 01:08:20.434
one of the things it

01:08:20.514 --> 01:08:22.534
interrupts with is a blockchain

01:08:23.293 --> 01:08:24.614
which is your home

01:08:24.676 --> 01:08:26.858
blockchain but the idea

01:08:26.877 --> 01:08:28.078
that your state machine

01:08:28.699 --> 01:08:29.820
should only write to that

01:08:29.860 --> 01:08:32.023
blockchain um and not in

01:08:32.082 --> 01:08:34.244
fact be instead directed to

01:08:34.305 --> 01:08:35.667
some other blockchain that

01:08:35.747 --> 01:08:37.287
has a compatible client for

01:08:37.328 --> 01:08:39.671
you to write to is is like

01:08:39.751 --> 01:08:44.034
somewhat arbitrary um yeah

01:08:45.713 --> 01:08:46.515
Anyway, that's the end of the show,

01:08:46.534 --> 01:08:46.795
I thought.

01:08:47.015 --> 01:08:47.975
That's the end of the show, I thought.

01:08:48.015 --> 01:08:48.176
Like,

01:08:48.235 --> 01:08:50.216
is the incentive mechanisms being

01:08:50.256 --> 01:08:51.238
tied to the state machine?

01:08:51.257 --> 01:08:52.960
So the interesting thing

01:08:52.979 --> 01:08:54.239
about the Cosmos hub, right,

01:08:54.541 --> 01:08:56.421
or Cosmos stack, right,

01:08:56.782 --> 01:08:59.805
is you've got blockchain, ABCI,

01:09:00.404 --> 01:09:01.365
and you've got state machine,

01:09:01.626 --> 01:09:02.707
and then you've got stuff,

01:09:03.507 --> 01:09:04.228
additional stuff,

01:09:04.247 --> 01:09:05.229
like additional plumbing,

01:09:05.689 --> 01:09:06.590
including the relays,

01:09:06.630 --> 01:09:07.570
including all of that stuff.

01:09:08.251 --> 01:09:10.972
which actually a lot of it is very,

01:09:11.012 --> 01:09:12.094
very tightly integrated

01:09:12.134 --> 01:09:13.213
with both the state machine

01:09:13.475 --> 01:09:15.296
and the consensus engine underneath it.

01:09:15.935 --> 01:09:17.577
So there's an argument for

01:09:17.997 --> 01:09:19.738
the blockchain should be more generic,

01:09:20.059 --> 01:09:23.060
although to be fair to Tendermint,

01:09:24.421 --> 01:09:25.483
the Tendermint stack is

01:09:25.542 --> 01:09:26.703
quite generic and just

01:09:26.823 --> 01:09:27.724
orders transactions and

01:09:27.743 --> 01:09:29.425
writes and that's basically it.

01:09:30.065 --> 01:09:32.646
Even if ABCI itself makes

01:09:32.686 --> 01:09:33.408
quite a bit of assumptions

01:09:33.448 --> 01:09:34.889
about the state machine,

01:09:35.506 --> 01:09:37.207
You know, fair enough, but, but on,

01:09:37.287 --> 01:09:38.707
on the whole, that that's architecturally,

01:09:38.887 --> 01:09:40.087
you know, how it's designed and, and,

01:09:40.167 --> 01:09:41.628
and whatever it is.

01:09:43.109 --> 01:09:43.890
The question is like,

01:09:43.909 --> 01:09:44.610
as soon as you start going

01:09:44.631 --> 01:09:45.690
towards the interrupt piece,

01:09:45.730 --> 01:09:46.551
you start questioning

01:09:46.591 --> 01:09:47.712
whether the architecture of

01:09:47.752 --> 01:09:48.912
how the state machine works,

01:09:49.533 --> 01:09:55.136
if it's going to inherently, um, if the,

01:09:55.636 --> 01:09:56.476
if the state machine is

01:09:56.516 --> 01:09:57.997
going to be inherently, uh,

01:09:59.358 --> 01:10:01.779
special purpose and tied in

01:10:01.859 --> 01:10:03.340
some way to the working of

01:10:03.380 --> 01:10:04.520
your interop layer.

01:10:05.287 --> 01:10:06.729
then those two things being

01:10:06.949 --> 01:10:08.152
more tightly coupled so

01:10:08.192 --> 01:10:09.635
that they are a part of the

01:10:09.675 --> 01:10:11.939
same incentive mechanism

01:10:12.680 --> 01:10:13.582
maybe makes more sense.

01:10:13.662 --> 01:10:15.826
And I know they sort of are

01:10:15.966 --> 01:10:16.887
already in Cosmos,

01:10:16.908 --> 01:10:17.829
but it's one of those like,

01:10:19.846 --> 01:10:20.768
they are in practice,

01:10:20.787 --> 01:10:22.449
but the incentives aren't tied together.

01:10:22.550 --> 01:10:23.170
So you can,

01:10:23.690 --> 01:10:24.952
you're making money from your validator,

01:10:24.971 --> 01:10:26.193
but you're losing money on your,

01:10:26.332 --> 01:10:26.913
your relay.

01:10:26.974 --> 01:10:27.173
Right.

01:10:28.095 --> 01:10:31.297
Um, it's, it's, it's very tightly coupled,

01:10:31.377 --> 01:10:32.739
but it's not economically

01:10:33.640 --> 01:10:35.301
represented in the incentive mechanism.

01:10:35.362 --> 01:10:35.542
Right.

01:10:36.483 --> 01:10:39.105
Um, so I, I don't know, it's, it's,

01:10:39.206 --> 01:10:39.926
it's quite hard to,

01:10:40.226 --> 01:10:41.448
it's quite hard to unravel

01:10:41.467 --> 01:10:42.229
the shower thoughts and

01:10:42.248 --> 01:10:43.350
something more coherent than,

01:10:44.257 --> 01:10:46.698
then then I don't know how

01:10:47.439 --> 01:10:49.880
and so the thing I guess it

01:10:49.899 --> 01:10:50.520
boils down to this right

01:10:50.539 --> 01:10:51.039
the thing that's really

01:10:51.060 --> 01:10:51.880
important and interesting

01:10:51.899 --> 01:10:54.041
about the ibc verse is ibc

01:10:54.541 --> 01:10:55.680
and is the packets moving

01:10:55.720 --> 01:10:56.820
around the transactions

01:10:56.860 --> 01:10:58.141
moving around and the fact

01:10:58.181 --> 01:10:59.502
that those transactions and

01:10:59.542 --> 01:11:01.743
packets are valid wherever

01:11:01.783 --> 01:11:03.283
they land as long as the

01:11:03.342 --> 01:11:06.024
destination um accepts that

01:11:06.083 --> 01:11:07.944
format right as long as the

01:11:08.123 --> 01:11:10.064
the protocol is sound the

01:11:10.125 --> 01:11:13.365
destination is is is uh is generic

01:11:14.059 --> 01:11:15.359
The blockchain is generic.

01:11:15.960 --> 01:11:17.060
And I wonder if you should

01:11:17.100 --> 01:11:18.301
just push that idea further.

01:11:18.421 --> 01:11:19.542
That's essentially what it is.

01:11:20.104 --> 01:11:22.404
And pushing the idea further would be,

01:11:22.425 --> 01:11:24.247
I suppose, saying, well,

01:11:24.466 --> 01:11:26.769
what part of the Cosmos SDK

01:11:28.350 --> 01:11:29.411
is actually necessary?

01:11:29.451 --> 01:11:30.692
In fact, any SDK.

01:11:30.771 --> 01:11:31.752
In fact, any...

01:11:33.371 --> 01:11:35.292
smart contract VM, like,

01:11:35.511 --> 01:11:36.511
should you not simply just

01:11:36.551 --> 01:11:37.832
be writing an interop layer

01:11:37.872 --> 01:11:39.173
to accept an arbitrary

01:11:39.213 --> 01:11:40.673
protocol connection and

01:11:40.694 --> 01:11:42.074
then just get that data

01:11:42.135 --> 01:11:46.636
onto a blockchain as it's, um, uh,

01:11:46.676 --> 01:11:47.497
storage at rest,

01:11:47.556 --> 01:11:50.097
but actually use volatile storage for the,

01:11:50.118 --> 01:11:52.399
uh, transaction resolution on top.

01:11:54.060 --> 01:11:54.220
Well,

01:11:54.260 --> 01:11:55.860
I think that's basically what wormhole is,

01:11:55.921 --> 01:11:56.261
isn't it?

01:11:57.702 --> 01:12:00.283
Wormhole is actually, I think maybe yes.

01:12:01.670 --> 01:12:01.850
Yeah,

01:12:01.890 --> 01:12:02.869
I think it's basically a measured

01:12:02.890 --> 01:12:03.810
protocol that they

01:12:03.951 --> 01:12:06.271
instantiate on their respective chains,

01:12:06.351 --> 01:12:08.393
and then they have, in effect,

01:12:08.493 --> 01:12:10.673
relayers that can work in

01:12:10.713 --> 01:12:12.594
between what amounts to any chain.

01:12:16.876 --> 01:12:17.475
Yeah,

01:12:17.655 --> 01:12:19.537
I think that is a similar model to

01:12:19.556 --> 01:12:20.438
what I'm talking about.

01:12:21.377 --> 01:12:21.917
But that's not like,

01:12:22.438 --> 01:12:23.779
is that super widely adopted?

01:12:25.653 --> 01:12:27.194
It's not super widely adopted.

01:12:27.215 --> 01:12:30.599
There's probably between 12

01:12:30.599 --> 01:12:31.659
and 15 chains that are

01:12:31.720 --> 01:12:32.701
using wormhole right now.

01:12:33.881 --> 01:12:34.622
But I know that they are

01:12:35.725 --> 01:12:36.585
actively expanding.

01:12:38.447 --> 01:12:39.228
And in my opinion,

01:12:39.247 --> 01:12:41.530
they're kind of walking

01:12:41.591 --> 01:12:43.252
backwards a little bit in that it

01:12:44.827 --> 01:12:45.266
I think that,

01:12:45.426 --> 01:12:46.768
I think the goal that they're

01:12:46.787 --> 01:12:47.948
going to start reaching for

01:12:48.149 --> 01:12:49.109
is becoming kind of like

01:12:49.288 --> 01:12:51.751
axel art in that you would have, um,

01:12:52.131 --> 01:12:54.853
kind of like a central wormhole chain,

01:12:55.113 --> 01:12:57.253
quote unquote, unquote, um,

01:12:58.033 --> 01:13:00.315
that everything bridges into it.

01:13:00.336 --> 01:13:02.157
And then you bridge out from there, right.

01:13:02.537 --> 01:13:03.938
Rather than it being interdependent,

01:13:03.957 --> 01:13:05.198
it would effectively become

01:13:05.238 --> 01:13:06.359
the wormhole hub.

01:13:13.134 --> 01:13:13.994
Which I'm actually okay with

01:13:14.034 --> 01:13:15.055
now that I'm thinking about it.

01:13:15.756 --> 01:13:15.956
I mean,

01:13:15.996 --> 01:13:18.358
if I want ABC to have fees and to

01:13:18.698 --> 01:13:20.019
be bringing in profit, which again,

01:13:20.038 --> 01:13:20.979
I think is one of the

01:13:21.020 --> 01:13:22.381
clearest profit mechanisms

01:13:23.001 --> 01:13:27.645
for basically all of IBC zones, then yeah,

01:13:27.885 --> 01:13:28.484
I think it makes sense.

01:13:28.524 --> 01:13:29.546
I mean, it's what Noble's doing.

01:13:33.007 --> 01:13:36.530
I... Yeah, I didn't agree with that.

01:13:36.711 --> 01:13:37.511
I mean, I'm kind of just...

01:13:41.006 --> 01:13:43.149
Other than this DDoS prevention, um,

01:13:46.211 --> 01:13:48.172
I'm increasingly less and

01:13:48.212 --> 01:13:50.454
less fussed about fees in general.

01:13:50.475 --> 01:13:53.778
And I just more and more

01:13:53.837 --> 01:13:57.161
think it just doesn't fucking work, um,

01:13:57.461 --> 01:13:58.462
for anything useful.

01:14:00.382 --> 01:14:03.805
Um, I mean, maybe the whole,

01:14:04.086 --> 01:14:05.146
maybe the whole thing doesn't work.

01:14:05.527 --> 01:14:05.948
I don't know.

01:14:05.967 --> 01:14:06.007
Um,

01:14:08.253 --> 01:14:09.835
Well, there is a blockchain,

01:14:09.875 --> 01:14:10.836
I can't remember which one right now,

01:14:11.195 --> 01:14:13.858
that actually has IBC fees being free.

01:14:14.439 --> 01:14:15.399
Like they have a secondary

01:14:15.439 --> 01:14:17.761
packet type that has IBC

01:14:18.301 --> 01:14:19.561
transactions are free, right?

01:14:19.582 --> 01:14:19.881
And so...

01:14:21.158 --> 01:14:21.398
For that,

01:14:21.438 --> 01:14:22.198
I think it's a really interesting

01:14:22.219 --> 01:14:24.479
case that you still need to

01:14:24.500 --> 01:14:25.680
pay for the infrastructure for IBC.

01:14:25.899 --> 01:14:27.081
The best way to have good

01:14:27.140 --> 01:14:28.981
IBC relaying is to have a

01:14:29.242 --> 01:14:30.882
lot of the nodes local to

01:14:30.903 --> 01:14:31.722
each other on the same

01:14:31.783 --> 01:14:33.024
machine so that they have

01:14:33.104 --> 01:14:34.344
really quick latency or

01:14:34.404 --> 01:14:38.945
really low latency, which has a cost.

01:14:40.667 --> 01:14:41.807
But to be able to bypass the

01:14:41.847 --> 01:14:43.948
typical blockchain fees is

01:14:43.988 --> 01:14:44.988
a really cool concept.

01:14:48.270 --> 01:14:48.551
Yeah.

01:14:50.171 --> 01:14:51.671
I mean, so I guess I, I mean,

01:14:51.912 --> 01:14:52.792
I guess like the background

01:14:52.813 --> 01:14:54.052
to this is that obviously these days,

01:14:54.113 --> 01:14:55.474
like I think a lot about payments.

01:14:55.573 --> 01:14:57.354
I think a lot, a lot, a lot,

01:14:57.395 --> 01:14:59.577
a lot about going to a

01:14:59.617 --> 01:15:01.778
coffee shop and buying a cup of coffee.

01:15:01.858 --> 01:15:02.078
Right.

01:15:02.759 --> 01:15:04.220
And as soon as soon as you

01:15:04.239 --> 01:15:05.119
start breaking that down,

01:15:05.140 --> 01:15:06.480
you're like the things that

01:15:06.801 --> 01:15:08.502
the amount of changes you

01:15:08.521 --> 01:15:09.323
would have to do.

01:15:10.244 --> 01:15:12.127
in order to make that

01:15:12.186 --> 01:15:13.747
adoption pattern happen.

01:15:13.807 --> 01:15:14.828
And one of them has to be

01:15:14.849 --> 01:15:16.869
speed and ease to the consumer,

01:15:17.029 --> 01:15:17.570
absolutely.

01:15:17.970 --> 01:15:19.131
But one of them has to be fees.

01:15:19.452 --> 01:15:21.293
And as soon as you start

01:15:21.373 --> 01:15:23.354
layering on any

01:15:23.574 --> 01:15:25.377
sufficiently complex set of fees,

01:15:25.777 --> 01:15:29.300
gas included, number one,

01:15:29.720 --> 01:15:31.240
you end up in a situation

01:15:31.261 --> 01:15:36.104
that the gas can become unknowable.

01:15:37.168 --> 01:15:37.769
Very, very quickly.

01:15:37.868 --> 01:15:38.770
I mean, almost all chains,

01:15:38.789 --> 01:15:39.829
it's an estimation, right?

01:15:41.131 --> 01:15:42.572
And that means that as a

01:15:42.612 --> 01:15:44.152
consumer and particularly as a vendor,

01:15:44.192 --> 01:15:46.353
who's in most, in a lot of jurisdictions,

01:15:46.372 --> 01:15:47.134
the vendor is going to have

01:15:47.154 --> 01:15:48.173
to suck up that cost.

01:15:49.095 --> 01:15:50.534
They're going to have to know,

01:15:50.555 --> 01:15:51.576
they're going to want to

01:15:51.615 --> 01:15:52.315
know how much that is.

01:15:52.336 --> 01:15:52.796
Ideally,

01:15:52.817 --> 01:15:53.997
they're going to want to know what

01:15:54.056 --> 01:15:55.658
is ahead of time for accounting reasons.

01:15:56.768 --> 01:15:57.828
and be able to you know to

01:15:57.889 --> 01:15:59.310
calculate it just calculate

01:15:59.331 --> 01:16:00.251
it easily without it being

01:16:00.291 --> 01:16:01.032
an accounting overhead

01:16:01.051 --> 01:16:01.693
otherwise they're going to

01:16:01.712 --> 01:16:02.953
go fuck it you know if it

01:16:02.993 --> 01:16:04.854
costs us another week a

01:16:04.875 --> 01:16:05.996
year to do the accounting

01:16:06.055 --> 01:16:06.877
to work out what we're

01:16:06.896 --> 01:16:08.137
spending at cost at point

01:16:08.177 --> 01:16:09.458
of sale it turns out it's

01:16:09.498 --> 01:16:11.341
cheaper right until we put

01:16:11.720 --> 01:16:13.283
the accounting line item

01:16:13.323 --> 01:16:15.064
against it and then it

01:16:15.123 --> 01:16:15.765
turns out that the

01:16:15.784 --> 01:16:16.545
percentage difference

01:16:16.564 --> 01:16:18.167
between that using visa or

01:16:18.207 --> 01:16:20.649
whatever um clear pay

01:16:20.689 --> 01:16:23.051
whoever I don't know who it'd be um it

01:16:23.936 --> 01:16:25.438
It becomes negligible, right?

01:16:25.457 --> 01:16:26.137
And we're moving

01:16:26.177 --> 01:16:27.378
infrastructure for no reason.

01:16:28.918 --> 01:16:29.960
And that's before you think

01:16:30.020 --> 01:16:31.159
about all of the additional

01:16:31.680 --> 01:16:33.201
things you can get in public networks,

01:16:33.240 --> 01:16:34.402
like MEV and all that kind

01:16:34.442 --> 01:16:36.483
of fun shit where you're like, look,

01:16:36.502 --> 01:16:37.622
if I'm buying a coffee,

01:16:37.643 --> 01:16:39.963
I don't want like the idea

01:16:40.003 --> 01:16:40.805
of like blocks and things

01:16:40.824 --> 01:16:41.984
like that with like MEV

01:16:42.204 --> 01:16:43.685
transactions and all that

01:16:43.706 --> 01:16:44.646
kind of shit happening in

01:16:44.707 --> 01:16:48.427
it is like total mad stuff.

01:16:48.528 --> 01:16:48.707
Right.

01:16:52.438 --> 01:16:54.119
yeah like fees fees is not

01:16:54.239 --> 01:16:55.841
one I think you like you

01:16:55.862 --> 01:16:56.762
take it for granted so you

01:16:56.802 --> 01:17:00.546
go well okay but but is

01:17:00.606 --> 01:17:02.268
this the right is there

01:17:02.328 --> 01:17:03.208
another model and I don't

01:17:03.248 --> 01:17:04.149
have a good like it's not

01:17:04.170 --> 01:17:05.851
like I have a good counter

01:17:05.872 --> 01:17:06.893
suggestion at the moment

01:17:06.953 --> 01:17:08.375
but for how you pay people

01:17:08.414 --> 01:17:09.775
to run infrastructure other

01:17:09.815 --> 01:17:12.399
than you know they offer it

01:17:12.479 --> 01:17:14.780
as a service and people pay for it

01:17:15.492 --> 01:17:16.212
But you know,

01:17:16.271 --> 01:17:18.132
who's paying for it and on what basis?

01:17:18.193 --> 01:17:18.912
I mean, like, you know,

01:17:18.932 --> 01:17:20.153
you look at provision of

01:17:20.273 --> 01:17:22.753
RPC nodes and there's basically two,

01:17:22.993 --> 01:17:23.833
two versions, right?

01:17:23.854 --> 01:17:26.295
There's poverty tragedy of the commons,

01:17:26.734 --> 01:17:27.154
and then there's a

01:17:27.215 --> 01:17:28.416
foundation paying tens of

01:17:28.435 --> 01:17:30.176
thousands of dollars for

01:17:30.515 --> 01:17:32.356
what is a technical service

01:17:32.457 --> 01:17:33.777
with high availability.

01:17:34.417 --> 01:17:34.658
Right.

01:17:35.358 --> 01:17:39.238
And it, it would be hard to.

01:17:42.095 --> 01:17:43.136
I think if you start from

01:17:43.176 --> 01:17:44.296
the premise that we're in a

01:17:44.337 --> 01:17:45.438
situation right now where

01:17:45.497 --> 01:17:47.478
decentralization is

01:17:47.759 --> 01:17:51.220
basically theater on almost every network,

01:17:51.800 --> 01:17:52.600
the reality is all the

01:17:52.640 --> 01:17:53.780
tokens are concentrated.

01:17:53.801 --> 01:17:55.221
A lot of the voting power is concentrated,

01:17:55.242 --> 01:17:56.261
particularly in proof of stake.

01:17:57.743 --> 01:17:59.083
And you start to go, yeah, okay, well,

01:17:59.123 --> 01:18:01.704
these networks, they are businesses.

01:18:02.444 --> 01:18:03.485
The rest of it is theater.

01:18:04.594 --> 01:18:06.274
essentially so they should

01:18:06.295 --> 01:18:07.796
just act like it pay nodes

01:18:07.855 --> 01:18:08.796
for professional service

01:18:08.837 --> 01:18:10.177
provision and then move on

01:18:10.818 --> 01:18:13.060
right then we then we go

01:18:13.100 --> 01:18:13.860
okay well that's that's

01:18:13.900 --> 01:18:14.801
problem solved that's how

01:18:14.860 --> 01:18:16.221
you would get that robust

01:18:16.301 --> 01:18:17.622
architecture for payments

01:18:17.643 --> 01:18:19.104
and whatnot to to sort of

01:18:19.163 --> 01:18:20.765
work but you then go it

01:18:20.985 --> 01:18:21.945
then does beg the question

01:18:21.966 --> 01:18:23.868
where you go okay could we have

01:18:24.729 --> 01:18:26.371
a radically decentralized

01:18:26.411 --> 01:18:28.092
future where you are

01:18:28.273 --> 01:18:29.913
actually meeting a bunch of

01:18:29.953 --> 01:18:32.435
the things that... So if

01:18:32.456 --> 01:18:33.417
you remember back to

01:18:33.978 --> 01:18:35.838
Vitalik's early writings on

01:18:36.019 --> 01:18:36.920
proof of stake when it was

01:18:37.159 --> 01:18:38.942
very early in the mooting

01:18:39.002 --> 01:18:41.743
process for Ethereum,

01:18:41.764 --> 01:18:42.824
some of that stuff around

01:18:43.444 --> 01:18:44.985
none of this stuff... Even

01:18:45.207 --> 01:18:47.668
he said a lot of the

01:18:47.689 --> 01:18:48.970
decentralization stuff is

01:18:49.050 --> 01:18:50.810
theater unless you can run...

01:18:51.992 --> 01:18:52.993
all this stuff on consumer

01:18:53.033 --> 01:18:54.432
hardware on on laptops

01:18:54.493 --> 01:18:55.493
phones that sort of stuff

01:18:56.033 --> 01:18:57.154
and so like I guess you get

01:18:57.173 --> 01:19:01.256
to moot a future where the

01:19:01.315 --> 01:19:02.096
provision of the

01:19:02.136 --> 01:19:03.516
infrastructure is as cheap

01:19:03.577 --> 01:19:05.158
and as ready as water right

01:19:05.637 --> 01:19:06.838
that's the other flip of

01:19:06.878 --> 01:19:09.800
the coin where the party

01:19:09.819 --> 01:19:12.341
can happen but in the world

01:19:12.400 --> 01:19:14.341
where you need service provision

01:19:15.546 --> 01:19:16.646
with all the dedicated

01:19:16.686 --> 01:19:17.686
hardware and all that kind

01:19:17.707 --> 01:19:18.287
of other stuff.

01:19:18.327 --> 01:19:19.747
It just, it, it,

01:19:20.068 --> 01:19:21.908
it tends towards centralization anyway,

01:19:21.988 --> 01:19:23.350
like our entire model and

01:19:23.890 --> 01:19:24.770
all everything around it

01:19:24.810 --> 01:19:26.891
currently tends that way.

01:19:26.971 --> 01:19:30.314
And the fee model as a

01:19:30.354 --> 01:19:31.554
result is not enough to

01:19:31.613 --> 01:19:32.835
support that professional

01:19:32.895 --> 01:19:34.216
level of service provision.

01:19:34.555 --> 01:19:35.775
Whereas like micro payments

01:19:35.796 --> 01:19:36.837
for somebody just renting

01:19:36.896 --> 01:19:38.797
out a bit of extra, you know,

01:19:38.957 --> 01:19:40.618
idle bandwidth on the laptop is,

01:19:42.039 --> 01:19:43.560
that's a completely different game.

01:19:43.600 --> 01:19:44.122
And you're like, yeah,

01:19:44.202 --> 01:19:46.422
fees might be sufficient to

01:19:47.064 --> 01:19:47.863
trade off against the

01:19:47.904 --> 01:19:48.984
slight bit of hard drive

01:19:49.024 --> 01:19:50.405
wear or whatever you'd have

01:19:51.587 --> 01:19:53.068
for running a small light

01:19:53.108 --> 01:19:54.108
client or something on your

01:19:54.148 --> 01:19:56.289
laptop while you're doom

01:19:56.310 --> 01:19:57.890
scrolling on YouTube or whatever.

01:19:57.911 --> 01:20:03.734
I don't know.

01:20:03.954 --> 01:20:05.335
The more I think hard about payments,

01:20:05.376 --> 01:20:10.639
the more kind of hopeful I get about

01:20:11.764 --> 01:20:14.246
um the solutions that are

01:20:14.265 --> 01:20:15.106
going to come along in five

01:20:15.146 --> 01:20:16.988
ten years for actually

01:20:17.069 --> 01:20:18.630
radically decentralized

01:20:18.670 --> 01:20:22.393
solutions to economic

01:20:22.432 --> 01:20:23.833
systems that only exist in

01:20:23.894 --> 01:20:26.256
cyberspace but it's going

01:20:26.275 --> 01:20:27.337
to be so different to what

01:20:27.356 --> 01:20:28.478
we currently have now I

01:20:28.497 --> 01:20:29.618
don't know because because

01:20:29.639 --> 01:20:30.579
what we have now is just

01:20:31.380 --> 01:20:32.541
the things that support it

01:20:32.801 --> 01:20:33.662
everything just seems like

01:20:33.702 --> 01:20:34.783
tragedy of the commons like

01:20:34.823 --> 01:20:36.864
in every direction um

01:20:38.796 --> 01:20:39.676
And you can see from the

01:20:39.716 --> 01:20:41.278
business models that we as

01:20:41.337 --> 01:20:42.158
node operators and

01:20:42.198 --> 01:20:43.097
infrastructure provision

01:20:43.679 --> 01:20:45.618
providers have to do,

01:20:45.679 --> 01:20:46.338
which are not that

01:20:46.619 --> 01:20:49.359
dissimilar to traditional

01:20:50.060 --> 01:20:51.640
enterprise infrastructure contracts.

01:20:53.662 --> 01:20:54.782
You go, well, yeah, okay,

01:20:54.822 --> 01:20:56.662
so this is the world we

01:20:56.682 --> 01:20:57.582
live in because that's what

01:20:57.603 --> 01:20:58.342
we actually have to do in

01:20:58.363 --> 01:20:58.903
order to survive.

01:20:59.104 --> 01:21:03.805
What do you think about the curtain?

01:21:04.984 --> 01:21:06.466
Niles is busy filing his taxes, of course,

01:21:06.506 --> 01:21:06.645
there.

01:21:07.400 --> 01:21:08.721
Yes, that's an important part.

01:21:09.322 --> 01:21:11.643
One thing I've thought about a bit is, um,

01:21:12.262 --> 01:21:13.904
having something, uh, like, uh,

01:21:14.123 --> 01:21:15.024
I don't wanna say community fund,

01:21:15.064 --> 01:21:15.685
but let's say there's a

01:21:15.725 --> 01:21:16.744
secondary type of community

01:21:16.784 --> 01:21:17.886
fund that works as

01:21:17.926 --> 01:21:19.787
effectively an escrow for fees, right.

01:21:20.167 --> 01:21:22.268
Where it's too common that

01:21:22.908 --> 01:21:24.009
you sent out a transaction.

01:21:24.069 --> 01:21:24.849
The estimate wasn't right.

01:21:24.889 --> 01:21:27.430
You need to increase it by like 50 gas,

01:21:27.711 --> 01:21:28.511
let's say, right.

01:21:29.310 --> 01:21:30.912
I don't understand why there

01:21:30.952 --> 01:21:32.252
isn't some level of escrow

01:21:32.353 --> 01:21:33.313
where once that estimate is

01:21:33.353 --> 01:21:34.993
done and the payment is done is paid.

01:21:37.368 --> 01:21:40.451
the overpayment instead of like,

01:21:40.530 --> 01:21:41.511
I don't see why that

01:21:41.551 --> 01:21:42.511
overpayment doesn't go to

01:21:42.551 --> 01:21:44.372
like an escrow system or an account,

01:21:44.512 --> 01:21:45.213
which would then pay the

01:21:45.253 --> 01:21:47.414
difference on accidentally

01:21:47.534 --> 01:21:50.176
underpaid transactions for small things,

01:21:50.216 --> 01:21:51.978
for like a contract execution,

01:21:52.018 --> 01:21:52.597
maybe less.

01:21:53.658 --> 01:21:54.418
But if you're doing a basic

01:21:54.458 --> 01:21:57.280
send or update your

01:21:57.301 --> 01:21:58.362
validator transaction,

01:21:59.670 --> 01:22:01.110
Those have a pretty consistent gas, right?

01:22:01.150 --> 01:22:02.212
If it goes down just a little bit,

01:22:02.231 --> 01:22:03.012
it goes up a little bit.

01:22:03.472 --> 01:22:04.033
I don't think it should

01:22:04.052 --> 01:22:05.595
require sending a new transaction.

01:22:05.994 --> 01:22:06.854
Pull from that escrow.

01:22:06.996 --> 01:22:07.876
And if it's overestimated,

01:22:08.476 --> 01:22:09.837
push the rest from that escrow account.

01:22:11.259 --> 01:22:12.479
I haven't thought too much about this,

01:22:12.520 --> 01:22:13.461
but it's something that it

01:22:13.520 --> 01:22:15.442
seems like fees are an

01:22:15.742 --> 01:22:17.623
ongoing issue within blockchains.

01:22:19.845 --> 01:22:20.485
And it seems like there's

01:22:20.765 --> 01:22:22.247
solutions that can be found

01:22:22.287 --> 01:22:22.927
that doesn't mean...

01:22:24.451 --> 01:22:25.570
just a failed transaction.

01:22:25.811 --> 01:22:26.712
Like failed transactions

01:22:26.912 --> 01:22:27.692
shouldn't happen unless

01:22:27.712 --> 01:22:28.292
something egregious

01:22:28.493 --> 01:22:29.792
egregious happens in my opinion.

01:22:30.113 --> 01:22:30.913
Or like you're not actually

01:22:30.953 --> 01:22:32.274
providing the gas or whatever.

01:22:32.293 --> 01:22:33.074
Like if you don't have the

01:22:33.095 --> 01:22:34.354
gas to pay great fail.

01:22:34.614 --> 01:22:35.876
Otherwise let it go through.

01:22:37.235 --> 01:22:39.596
I, I just wonder if like the,

01:22:40.997 --> 01:22:45.079
the solution is to cause

01:22:45.399 --> 01:22:46.779
fees at the moment are

01:22:46.840 --> 01:22:49.761
mainly to stop spam.

01:22:49.942 --> 01:22:50.202
Right.

01:22:50.362 --> 01:22:52.922
That's kind of the, the reason.

01:22:54.036 --> 01:22:54.837
So, I mean,

01:22:54.856 --> 01:22:55.697
there are a lot of different

01:22:55.737 --> 01:22:56.917
models for how you store

01:22:56.997 --> 01:22:58.298
state on blockchains that

01:22:58.359 --> 01:22:59.539
involve like one of the

01:22:59.579 --> 01:23:00.399
things you can do.

01:23:01.360 --> 01:23:01.701
And again,

01:23:01.720 --> 01:23:02.761
I would think this because a lot

01:23:02.782 --> 01:23:03.582
of the stuff I look at the

01:23:03.601 --> 01:23:05.103
moment is privacy stuff, right?

01:23:05.523 --> 01:23:08.145
Is if you store less state, right?

01:23:08.284 --> 01:23:09.826
If you store less stuff and

01:23:09.865 --> 01:23:11.226
keep more stuff private,

01:23:11.948 --> 01:23:12.828
you store less state.

01:23:12.887 --> 01:23:14.368
And it's a lot harder to

01:23:14.529 --> 01:23:17.251
clog up a blockchain with random shit,

01:23:17.470 --> 01:23:17.690
right?

01:23:18.091 --> 01:23:19.212
And then your need for fees

01:23:19.271 --> 01:23:20.332
does become bigger.

01:23:21.212 --> 01:23:22.393
Um, substantially lower, I mean,

01:23:22.412 --> 01:23:23.715
at the most extreme level,

01:23:23.734 --> 01:23:26.757
you can store a tiny root hashes, um,

01:23:29.119 --> 01:23:31.363
and then just get linear, you know,

01:23:31.622 --> 01:23:33.585
just small linear growth of, of,

01:23:33.784 --> 01:23:34.565
of these sorts of things.

01:23:34.605 --> 01:23:36.226
And that's an extreme example, right?

01:23:37.868 --> 01:23:39.270
But in that world, you're like, well,

01:23:40.051 --> 01:23:40.431
you know, the,

01:23:40.591 --> 01:23:42.493
the marginal cost of node operators is,

01:23:42.613 --> 01:23:44.475
is effectively zero trending to zero.

01:23:45.887 --> 01:23:48.010
You don't need fees to prevent spam,

01:23:48.229 --> 01:23:49.332
let people spam away.

01:23:50.011 --> 01:23:52.774
And if you make the transactions private,

01:23:53.555 --> 01:23:56.318
you prevent certain types

01:23:56.378 --> 01:23:58.421
of spam like bots.

01:24:00.322 --> 01:24:03.365
Because you can't MEV, you can't do MEV,

01:24:03.805 --> 01:24:04.587
flash attacks,

01:24:04.686 --> 01:24:05.547
any of that stuff on

01:24:05.627 --> 01:24:06.628
individual transactions if

01:24:06.668 --> 01:24:07.510
you can't introspect the

01:24:07.550 --> 01:24:08.631
transactions in the mempool.

01:24:10.298 --> 01:24:11.340
It becomes a lot harder.

01:24:11.479 --> 01:24:13.180
So the only situation, in fact,

01:24:13.261 --> 01:24:14.502
where you can attack a

01:24:14.542 --> 01:24:18.485
transaction is if you are

01:24:18.546 --> 01:24:19.367
the person with the

01:24:19.426 --> 01:24:21.748
transaction and you know

01:24:23.110 --> 01:24:24.431
before the transaction

01:24:24.471 --> 01:24:26.814
settles that you are about to lose money,

01:24:27.595 --> 01:24:28.855
if you are also a node

01:24:28.895 --> 01:24:30.537
operator and could type at

01:24:30.557 --> 01:24:31.398
the speed of light,

01:24:32.734 --> 01:24:34.216
you could maybe do something

01:24:34.296 --> 01:24:36.358
to modify your binary, stop your binary,

01:24:36.918 --> 01:24:38.119
reload your binary with

01:24:38.180 --> 01:24:39.461
changed code in order to,

01:24:39.621 --> 01:24:41.943
but that's like theoretical

01:24:41.983 --> 01:24:43.203
to the point of comedy that

01:24:43.243 --> 01:24:45.805
you could modify a mempool

01:24:45.826 --> 01:24:47.306
and attack the blockchain

01:24:47.407 --> 01:24:48.608
on behalf of yourself to

01:24:48.667 --> 01:24:50.408
merely reverse your own transaction.

01:24:50.429 --> 01:24:53.011
Yeah, I mean,

01:24:53.051 --> 01:24:53.832
maybe there's a way of doing

01:24:53.851 --> 01:24:54.551
that that I haven't thought

01:24:54.591 --> 01:24:56.293
of that doesn't involve a comical setup,

01:24:56.434 --> 01:24:57.854
but yeah, I don't know.

01:24:58.880 --> 01:24:59.661
it feels like you can tackle

01:24:59.680 --> 01:25:00.421
a lot of these situations,

01:25:00.480 --> 01:25:03.203
a lot of these solutions by, you know,

01:25:03.342 --> 01:25:04.323
like practical Byzantine

01:25:04.344 --> 01:25:05.783
fault tolerance relies on

01:25:05.824 --> 01:25:07.244
you loosening some of the

01:25:07.265 --> 01:25:09.407
assumptions around asynchrony,

01:25:09.447 --> 01:25:10.627
like to have partial

01:25:10.667 --> 01:25:11.707
synchrony and stuff like that,

01:25:11.728 --> 01:25:12.488
where you go, okay, well,

01:25:12.509 --> 01:25:12.988
we're going to have a

01:25:13.048 --> 01:25:14.090
timeout that's going to

01:25:14.149 --> 01:25:15.390
make sure that it is

01:25:15.451 --> 01:25:16.631
eventually synchronous, right?

01:25:16.992 --> 01:25:18.313
You can start saying, well, okay,

01:25:19.332 --> 01:25:20.953
What if our default is that

01:25:21.393 --> 01:25:22.434
fee should be zero,

01:25:22.974 --> 01:25:24.854
but that you could specify

01:25:24.934 --> 01:25:26.673
fees on top for the X, Y,

01:25:26.713 --> 01:25:28.534
Z reason to enhance security and X, Y,

01:25:28.614 --> 01:25:30.414
Z situation, or like, you know,

01:25:31.095 --> 01:25:31.994
on things like privacy,

01:25:32.034 --> 01:25:33.515
like the default should be

01:25:34.136 --> 01:25:35.595
that other people other

01:25:35.636 --> 01:25:37.115
than the sender cannot

01:25:37.256 --> 01:25:38.515
introspect to transaction.

01:25:38.536 --> 01:25:39.636
Right.

01:25:40.237 --> 01:25:42.457
And then suddenly you start adding,

01:25:42.697 --> 01:25:43.716
adding stuff on top.

01:25:45.358 --> 01:25:46.537
That means that you get

01:25:46.578 --> 01:25:47.738
additional things for free.

01:25:49.007 --> 01:25:49.328
I don't know.

01:25:50.368 --> 01:25:50.889
Like I say,

01:25:50.908 --> 01:25:51.788
we're very firmly into my

01:25:51.828 --> 01:25:53.208
shower thoughts section here,

01:25:53.248 --> 01:25:55.369
so apologies to anybody listening.

01:25:56.750 --> 01:25:59.310
I've just turned in a draft paper,

01:25:59.390 --> 01:26:02.412
so there's just a lot of...

01:26:03.032 --> 01:26:04.492
You know when you've just

01:26:04.532 --> 01:26:05.511
done a piece of woodwork

01:26:06.153 --> 01:26:07.193
and you haven't swept up yet?

01:26:08.274 --> 01:26:09.916
And there's just like all of

01:26:09.956 --> 01:26:11.136
the sawdust is on the floor.

01:26:11.617 --> 01:26:12.778
And in the sawdust,

01:26:13.038 --> 01:26:14.720
like there are some useful offcuts,

01:26:14.779 --> 01:26:16.100
but they're buried in the sawdust.

01:26:16.582 --> 01:26:17.563
And you do that thing where, you know,

01:26:17.582 --> 01:26:18.384
you kick around with your

01:26:18.423 --> 01:26:20.265
shoes in like the kind of

01:26:20.345 --> 01:26:21.326
ankle deep sawdust.

01:26:21.405 --> 01:26:23.809
And you're like trying to find any useful,

01:26:23.868 --> 01:26:24.750
like, you know,

01:26:24.770 --> 01:26:26.091
there's like magic offcuts

01:26:26.110 --> 01:26:27.752
that are like about a centimeter big.

01:26:28.880 --> 01:26:30.001
And they're like that really

01:26:30.180 --> 01:26:32.221
useful size for like door

01:26:32.261 --> 01:26:34.184
wedges or propping shit up or whatever.

01:26:34.203 --> 01:26:34.783
And you're like, Ooh,

01:26:34.863 --> 01:26:35.685
I bet there's some good off

01:26:35.744 --> 01:26:36.444
cuts down here.

01:26:36.886 --> 01:26:38.226
I feel like I'm at that stage.

01:26:38.287 --> 01:26:39.747
Like I've just got the

01:26:39.787 --> 01:26:40.868
majority of a thing done.

01:26:40.908 --> 01:26:41.868
I'm just kicking around in

01:26:41.908 --> 01:26:43.149
the sawdust for any other

01:26:43.250 --> 01:26:44.690
like half baked ideas that

01:26:44.730 --> 01:26:47.493
might be useful for the future.

01:26:47.512 --> 01:26:49.795
So I'm sorry for subjecting you to it.

01:26:51.355 --> 01:26:51.636
Anyway,

01:26:52.436 --> 01:26:54.618
you're like that dad with that box

01:26:55.099 --> 01:26:57.159
filled with useless fucking

01:26:57.199 --> 01:26:58.240
off cuts that you never use.

01:26:59.984 --> 01:27:02.746
I literally under my desk here right now.

01:27:02.826 --> 01:27:04.207
Cause I was literally doing

01:27:04.247 --> 01:27:05.368
something the other day.

01:27:05.387 --> 01:27:06.949
I have a box of off cuts

01:27:07.010 --> 01:27:08.350
that I have yet to sort.

01:27:09.110 --> 01:27:10.351
It's a very exciting box.

01:27:10.391 --> 01:27:11.052
There's some real,

01:27:12.134 --> 01:27:13.375
some real good off cuts in there.

01:27:13.734 --> 01:27:14.234
I'm pretty pleased.

01:27:14.255 --> 01:27:15.176
I feel like you don't have

01:27:15.235 --> 01:27:16.117
enough to do if you're

01:27:16.157 --> 01:27:18.177
spending your time sorting off cuts.

01:27:18.798 --> 01:27:19.779
Although, you know,

01:27:19.800 --> 01:27:20.619
it seems like you have

01:27:20.640 --> 01:27:22.542
spare time these days now

01:27:22.561 --> 01:27:25.564
that you are not painting

01:27:25.604 --> 01:27:26.203
your little men.

01:27:26.224 --> 01:27:26.265
Uh,

01:27:28.993 --> 01:27:30.373
Yeah, yeah, no, that's true.

01:27:30.474 --> 01:27:32.033
Not painting your little men.

01:27:33.614 --> 01:27:34.835
Noel has a very,

01:27:34.895 --> 01:27:36.136
very dim view of hobbies

01:27:36.296 --> 01:27:38.237
because Noel has decided to

01:27:38.296 --> 01:27:41.057
work every single hour God gave him.

01:27:42.878 --> 01:27:44.298
Whereas, yeah,

01:27:44.838 --> 01:27:46.000
some of us have decided

01:27:46.300 --> 01:27:47.961
since having children to

01:27:49.060 --> 01:27:49.961
pick up hobbies again

01:27:49.980 --> 01:27:50.761
because otherwise we'll go

01:27:50.841 --> 01:27:51.981
fucking insane.

01:27:52.002 --> 01:27:53.502
My guy,

01:27:54.063 --> 01:27:55.564
I'll have you know that I left the

01:27:55.604 --> 01:27:56.323
house yesterday.

01:27:57.867 --> 01:27:58.306
To do what?

01:27:58.346 --> 01:27:58.967
To do more work?

01:27:58.988 --> 01:28:00.088
Did you go to the data center?

01:28:00.128 --> 01:28:01.010
Is that why you left the house?

01:28:02.930 --> 01:28:04.853
I bought a charge cable for my mouse.

01:28:07.095 --> 01:28:08.756
That sounds like very unproductive time,

01:28:08.777 --> 01:28:09.016
Niall.

01:28:09.037 --> 01:28:10.158
You should be ashamed of yourself.

01:28:11.139 --> 01:28:12.359
I didn't realize you went so hard.

01:28:14.180 --> 01:28:15.162
My mouse stopped working.

01:28:17.064 --> 01:28:17.384
No,

01:28:18.864 --> 01:28:20.306
I haven't been to the data center in a

01:28:20.327 --> 01:28:20.606
while.

01:28:20.787 --> 01:28:21.768
I don't intend to go there

01:28:21.807 --> 01:28:22.769
unless something blows up.

01:28:27.250 --> 01:28:27.890
Yeah, I have been,

01:28:28.110 --> 01:28:30.511
I kind of want to buy some

01:28:30.532 --> 01:28:32.814
more stuff to build a

01:28:32.873 --> 01:28:34.154
Proxmox cluster now though.

01:28:34.175 --> 01:28:36.337
What?

01:28:37.518 --> 01:28:39.078
Proxmox, the hypervisor.

01:28:39.099 --> 01:28:42.161
I've rekindled my love of hypervisors.

01:28:43.702 --> 01:28:45.804
And yeah,

01:28:46.344 --> 01:28:48.005
Proxmox is like the most annoying

01:28:48.065 --> 01:28:48.525
one to use.

01:28:49.365 --> 01:28:50.367
So I figured that'd be a

01:28:50.407 --> 01:28:51.127
great place to start.

01:28:53.921 --> 01:28:57.226
I don't even know what to say to that.

01:28:57.287 --> 01:28:58.007
So why?

01:28:59.529 --> 01:29:00.332
Well, I mean,

01:29:00.351 --> 01:29:04.056
why use something easy when

01:29:04.096 --> 01:29:05.158
you can use something hard?

01:29:05.418 --> 01:29:06.560
And then, you know,

01:29:06.881 --> 01:29:07.762
if you ever have to fall

01:29:07.802 --> 01:29:09.164
back to the easy one, you'll be like, oh,

01:29:09.185 --> 01:29:09.886
fuck, this is easy.