WEBVTT

00:00:01.490 --> 00:00:03.532
And there's like so many

00:00:03.612 --> 00:00:05.474
fucking buttons on my audio interface.

00:00:05.514 --> 00:00:06.554
I don't know what most of them do.

00:00:07.155 --> 00:00:08.317
And I think it's actually

00:00:08.336 --> 00:00:09.817
turned up a little bit too far anyway.

00:00:10.739 --> 00:00:11.900
I'm just happy we got

00:00:12.060 --> 00:00:12.881
Shortsy's audio solved.

00:00:12.900 --> 00:00:13.480
That sounds pretty good.

00:00:14.401 --> 00:00:14.662
Yeah.

00:00:14.682 --> 00:00:18.745
I feel pretty sorry about that too.

00:00:18.865 --> 00:00:19.065
Mm-hmm.

00:00:20.428 --> 00:00:22.750
The audio is crispy.

00:00:41.018 --> 00:00:41.917
Hello, everybody.

00:00:42.499 --> 00:00:45.380
Welcome to Game of Nodes,

00:00:45.399 --> 00:00:49.762
a podcast about things and shits.

00:00:49.781 --> 00:00:51.162
A podcast.

00:00:51.942 --> 00:00:52.563
A podcast.

00:00:52.603 --> 00:00:53.344
Well, you know,

00:00:54.084 --> 00:00:57.125
it's always whenever the

00:00:57.164 --> 00:00:59.405
phrase here is like a podcast about, well,

00:00:59.466 --> 00:01:00.807
it's not really fucking about anything.

00:01:04.754 --> 00:01:07.456
So if you've hung around for

00:01:07.477 --> 00:01:08.819
the sixteen minutes it took

00:01:08.858 --> 00:01:10.760
to press the button, our one viewer,

00:01:10.840 --> 00:01:11.602
Lil D, welcome.

00:01:12.341 --> 00:01:15.365
Yeah, we have exactly one viewer.

00:01:15.825 --> 00:01:16.105
Cool.

00:01:16.126 --> 00:01:17.707
I mean, what have we done?

00:01:17.768 --> 00:01:19.390
We joined twenty minutes late and

00:01:21.302 --> 00:01:22.643
Yeah, I mean,

00:01:22.683 --> 00:01:23.944
that just really shows the

00:01:23.983 --> 00:01:24.983
kind of loyalty of the

00:01:25.024 --> 00:01:26.784
people who watch this.

00:01:26.825 --> 00:01:27.305
Like, ah,

00:01:27.344 --> 00:01:29.225
they're not here after fifteen minutes,

00:01:29.245 --> 00:01:30.647
so I'm going to like, I don't know,

00:01:30.706 --> 00:01:31.706
go and make some tea.

00:01:32.867 --> 00:01:33.528
Some breakfast.

00:01:34.308 --> 00:01:35.829
So how is everybody doing anyway?

00:01:36.329 --> 00:01:37.030
It's been busy.

00:01:37.430 --> 00:01:41.772
It's been network launches, market pumps,

00:01:41.852 --> 00:01:42.793
market dumps.

00:01:44.093 --> 00:01:45.174
Network almost launches.

00:01:46.194 --> 00:01:47.314
Network almost launches.

00:01:47.355 --> 00:01:48.355
What was the almost launch?

00:01:48.855 --> 00:01:49.716
Well, like pre-mainnet,

00:01:49.757 --> 00:01:50.557
pre-mainnet launch.

00:01:51.042 --> 00:01:51.802
Oh, yeah, yeah,

00:01:51.841 --> 00:01:53.721
like the ones in the pipeline.

00:01:53.742 --> 00:01:54.503
The ones in the pipeline.

00:01:54.522 --> 00:01:56.003
Discovering new chains that

00:01:56.022 --> 00:01:57.903
have been out there.

00:01:58.582 --> 00:01:59.644
Yeah.

00:01:59.683 --> 00:02:01.944
So, yeah, man,

00:02:02.203 --> 00:02:04.924
there's like getting some

00:02:05.164 --> 00:02:06.465
introductions lately of

00:02:06.504 --> 00:02:07.545
just these things that have

00:02:07.564 --> 00:02:12.066
been running in testnet for like a year.

00:02:12.126 --> 00:02:12.346
Oh, really?

00:02:12.366 --> 00:02:13.165
That no one knew about.

00:02:13.485 --> 00:02:17.606
Yeah.

00:02:17.907 --> 00:02:19.026
Trying to penetrate the...

00:02:20.366 --> 00:02:22.449
The secret squirrel networks.

00:02:24.150 --> 00:02:25.070
A guy jumped into our

00:02:25.151 --> 00:02:27.353
Discord yesterday to find

00:02:27.372 --> 00:02:30.655
out information about Monad.

00:02:30.996 --> 00:02:32.157
Nobody knows anything about Monad,

00:02:32.217 --> 00:02:32.717
first of all.

00:02:33.076 --> 00:02:33.777
That's number one.

00:02:33.957 --> 00:02:35.079
Number two was, hey,

00:02:35.158 --> 00:02:36.560
can you share anything about the Discord?

00:02:36.639 --> 00:02:37.721
And I was like, I don't have any.

00:02:37.741 --> 00:02:38.722
We're not validating.

00:02:38.741 --> 00:02:40.163
We don't really know what's going on.

00:02:40.563 --> 00:02:41.944
And he goes, cool, cool, cool, cool, cool,

00:02:41.965 --> 00:02:42.645
cool, cool, cool.

00:02:42.664 --> 00:02:44.387
For validator-related matters,

00:02:44.426 --> 00:02:45.167
could you share the best

00:02:45.187 --> 00:02:46.307
way to contact their team

00:02:46.427 --> 00:02:47.368
or the channel you use to

00:02:47.389 --> 00:02:48.270
become a validator for them?

00:02:48.289 --> 00:02:49.471
And I'm like,

00:02:51.276 --> 00:02:52.717
Listen, man, I was just asking questions,

00:02:52.838 --> 00:02:53.579
all right?

00:02:53.618 --> 00:02:55.722
Like, you could just help me out.

00:02:55.741 --> 00:02:57.383
Was it someone from Monad or

00:02:57.423 --> 00:02:58.304
someone just trying to get

00:02:58.764 --> 00:03:00.445
in the clique with Monad?

00:03:00.466 --> 00:03:01.627
Someone trying to get into the clique.

00:03:01.728 --> 00:03:03.588
Oh, man, they are impossible.

00:03:03.750 --> 00:03:04.409
Get in line, dude.

00:03:04.691 --> 00:03:06.772
Yeah.

00:03:06.793 --> 00:03:08.454
It's a long line of people

00:03:08.473 --> 00:03:09.115
trying to get in the clique.

00:03:09.891 --> 00:03:11.954
Remember that dude, Serp,

00:03:11.973 --> 00:03:13.895
that we met in Austin?

00:03:15.117 --> 00:03:17.120
He's like the marketing guy.

00:03:17.479 --> 00:03:17.760
Oh, yeah.

00:03:18.161 --> 00:03:18.561
Yeah, yeah, yeah.

00:03:18.621 --> 00:03:20.143
I just send him a message

00:03:20.182 --> 00:03:21.044
every now and then.

00:03:21.063 --> 00:03:22.164
He just hangs me on red

00:03:22.245 --> 00:03:23.126
every fucking time.

00:03:23.606 --> 00:03:25.489
Well, he left Monad, right?

00:03:26.219 --> 00:03:26.580
Did he?

00:03:26.800 --> 00:03:28.420
He's still got Monad in his name.

00:03:28.741 --> 00:03:29.162
Oh, really?

00:03:29.181 --> 00:03:29.282
Well,

00:03:29.301 --> 00:03:30.522
maybe we're talking about somebody else.

00:03:31.763 --> 00:03:33.123
I thought maybe, Schultz,

00:03:33.645 --> 00:03:34.784
we were at some Cosmos event.

00:03:34.844 --> 00:03:37.887
I thought it was the Monad

00:03:37.926 --> 00:03:38.587
team that we met.

00:03:39.228 --> 00:03:40.508
And then we reached out to them.

00:03:40.568 --> 00:03:42.030
I got introduced and then a

00:03:42.050 --> 00:03:42.689
bunch of other types.

00:03:42.729 --> 00:03:43.670
And then basically that

00:03:43.730 --> 00:03:44.972
person left and I keep pinging,

00:03:45.872 --> 00:03:47.372
what's going on?

00:03:47.413 --> 00:03:48.933
We're in a group with that

00:03:48.973 --> 00:03:49.574
team a little bit.

00:03:49.615 --> 00:03:50.574
But again,

00:03:50.594 --> 00:03:51.596
we don't get too much information.

00:03:52.270 --> 00:03:52.949
Was it Monad?

00:03:53.030 --> 00:03:55.830
There was a team that left

00:03:55.872 --> 00:03:56.891
and became a developer somewhere else.

00:03:56.912 --> 00:03:57.472
And we were like, hey,

00:03:57.491 --> 00:04:00.413
can we get in with the other team still?

00:04:00.734 --> 00:04:01.913
Maybe, yeah, maybe that wasn't Monad.

00:04:01.933 --> 00:04:02.493
Was that, what was it?

00:04:02.574 --> 00:04:03.555
I don't know what the heck

00:04:03.574 --> 00:04:05.895
that would have been.

00:04:06.015 --> 00:04:06.355
I don't know.

00:04:07.195 --> 00:04:07.376
Yeah.

00:04:07.596 --> 00:04:09.736
There's, anyway, we're all,

00:04:09.796 --> 00:04:10.557
we're all looking for the

00:04:10.598 --> 00:04:11.518
Monad click for sure.

00:04:13.924 --> 00:04:16.766
Yeah, man.

00:04:16.886 --> 00:04:17.786
I can get a message through.

00:04:17.826 --> 00:04:19.028
I can get read by Monad,

00:04:19.088 --> 00:04:22.449
so I don't elicit a response.

00:04:23.290 --> 00:04:24.031
I guess I'm not saying

00:04:24.071 --> 00:04:27.134
anything interesting.

00:04:27.514 --> 00:04:29.355
Well, they had not a team change,

00:04:29.375 --> 00:04:30.475
but somebody who took over

00:04:30.495 --> 00:04:33.358
that role for some of those discussions.

00:04:33.377 --> 00:04:35.098
And so it felt like two

00:04:35.119 --> 00:04:38.240
years of conversation went out the window,

00:04:38.261 --> 00:04:38.822
starting all over.

00:04:39.322 --> 00:04:39.841
But that's all right.

00:04:39.882 --> 00:04:40.562
What are you going to do?

00:04:41.761 --> 00:04:42.822
yeah I mean it doesn't

00:04:42.841 --> 00:04:44.043
always work out it's been

00:04:45.963 --> 00:04:47.685
yeah some some other

00:04:47.764 --> 00:04:49.026
networks that we've like

00:04:49.086 --> 00:04:50.526
put a lot of time into or

00:04:50.807 --> 00:04:51.887
at least been around a long

00:04:51.927 --> 00:04:55.769
time for right got ignored

00:04:56.031 --> 00:04:57.992
um speaking of launches so

00:04:58.052 --> 00:04:59.213
elixir doesn't always work

00:04:59.233 --> 00:05:00.673
yet the links are launched

00:05:00.814 --> 00:05:01.613
well it was mainnet

00:05:01.634 --> 00:05:02.394
launched a couple weeks ago

00:05:02.415 --> 00:05:03.235
I think is what it was and

00:05:03.254 --> 00:05:04.596
it went public what what

00:05:04.636 --> 00:05:07.017
did elixir oh yeah yeah

00:05:08.043 --> 00:05:09.084
And you, you called it out before,

00:05:09.103 --> 00:05:09.564
but I just,

00:05:09.625 --> 00:05:10.365
I was just logging in to

00:05:10.665 --> 00:05:12.425
retweet this silly podcast.

00:05:12.586 --> 00:05:13.326
And I have like,

00:05:13.386 --> 00:05:14.766
twenty-five retweets of all

00:05:14.786 --> 00:05:17.166
these people who are the

00:05:17.206 --> 00:05:18.708
Elixis Genesis validators

00:05:20.148 --> 00:05:21.709
and institutional

00:05:21.749 --> 00:05:24.610
powerhouses and expert operators.

00:05:24.670 --> 00:05:24.769
Like,

00:05:24.790 --> 00:05:25.850
where do you think we fall and other

00:05:28.110 --> 00:05:29.370
and other yeah.

00:05:29.850 --> 00:05:33.012
That's deep in the other.

00:05:33.192 --> 00:05:34.173
We were in deep in the other.

00:05:34.372 --> 00:05:34.492
Yep.

00:05:35.514 --> 00:05:36.915
Did you join that network, Schultz,

00:05:36.956 --> 00:05:38.255
or did you go into that?

00:05:38.576 --> 00:05:45.319
Did they adorn you with a Genesis slot?

00:05:45.858 --> 00:05:46.519
We were part of it.

00:05:46.540 --> 00:05:47.300
I don't know that we're a

00:05:47.319 --> 00:05:48.781
Genesis validator.

00:05:49.081 --> 00:05:51.622
Now I'm curious.

00:05:51.641 --> 00:05:52.401
You would have been tagged

00:05:52.442 --> 00:05:53.362
many times if you were.

00:05:54.783 --> 00:05:56.363
Who does the...

00:05:58.874 --> 00:05:59.954
twitter I don't know what to

00:05:59.975 --> 00:06:01.735
call it who does the x for

00:06:02.396 --> 00:06:03.617
uh the tweets yeah I don't

00:06:03.637 --> 00:06:08.701
I don't do the tweets what

00:06:08.721 --> 00:06:09.562
do they call it now it's

00:06:09.581 --> 00:06:10.783
not well it's not a tweet

00:06:10.802 --> 00:06:13.124
anymore is it is uh send it

00:06:13.144 --> 00:06:14.564
oh yeah we are it's a we

00:06:14.665 --> 00:06:15.565
are one of the jones's

00:06:15.685 --> 00:06:19.689
validators yeah hey hey are

00:06:19.709 --> 00:06:20.730
you in the are you deep in

00:06:20.750 --> 00:06:22.591
the other as well or are you like

00:06:24.223 --> 00:06:26.286
We are number twenty four.

00:06:26.586 --> 00:06:30.788
So we are below you two.

00:06:30.928 --> 00:06:31.329
Oh, no.

00:06:31.910 --> 00:06:34.552
Yeah, we're ten and eleven respectively.

00:06:34.572 --> 00:06:35.372
That's right.

00:06:35.451 --> 00:06:36.954
Yeah.

00:06:36.994 --> 00:06:37.074
Well,

00:06:37.093 --> 00:06:38.754
Republic was like up there in top left.

00:06:38.774 --> 00:06:39.555
And so, of course,

00:06:39.595 --> 00:06:41.257
I had to ping him or ping

00:06:41.357 --> 00:06:43.959
Will over there and be like, hey, like,

00:06:44.038 --> 00:06:44.838
you don't even know what this is.

00:06:44.959 --> 00:06:48.242
Like, I don't think you even do this.

00:06:49.642 --> 00:06:50.142
That's funny.

00:06:51.180 --> 00:06:52.360
So when can we actually stake then?

00:06:53.182 --> 00:06:54.781
I have no idea.

00:06:54.862 --> 00:06:55.382
I should ask.

00:06:55.562 --> 00:06:58.684
I should ask the tweets.

00:06:58.704 --> 00:06:59.564
Because everybody on Twitter

00:06:59.584 --> 00:07:01.223
knows more about this than I do.

00:07:01.564 --> 00:07:05.446
I think is basically what's happening.

00:07:05.485 --> 00:07:08.687
So Schultz in hardware news,

00:07:10.367 --> 00:07:12.908
Kingnodes now have their own AS number.

00:07:14.928 --> 00:07:16.329
That means literally nothing to me.

00:07:16.348 --> 00:07:17.389
That's pretty much it.

00:07:17.449 --> 00:07:17.829
Never mind.

00:07:20.500 --> 00:07:21.141
So can I look,

00:07:21.201 --> 00:07:22.041
I can look it up and I could

00:07:22.081 --> 00:07:23.661
see a King nose AS number.

00:07:24.182 --> 00:07:27.184
You can, you can, I, I am my own ISP.

00:07:27.283 --> 00:07:29.985
You can, uh, look up my AS number,

00:07:30.524 --> 00:07:33.466
see all my IP addresses.

00:07:34.247 --> 00:07:34.867
Oh, nice.

00:07:35.107 --> 00:07:35.627
That's pretty cool.

00:07:35.646 --> 00:07:35.726
Yeah.

00:07:36.827 --> 00:07:38.949
When, so when, you know, when like, uh,

00:07:39.209 --> 00:07:39.528
you know,

00:07:39.608 --> 00:07:40.829
all those fucking captain

00:07:40.850 --> 00:07:41.990
sleuths are out there with

00:07:42.009 --> 00:07:44.411
their softwares saying, uh,

00:07:44.490 --> 00:07:46.091
Hetzner and fucking whatever.

00:07:46.151 --> 00:07:47.711
Well, now it comes up with King nodes,

00:07:48.273 --> 00:07:48.833
King blockchain.

00:07:51.964 --> 00:07:52.964
So party of one.

00:07:53.504 --> 00:07:54.165
There will be no other

00:07:54.245 --> 00:07:57.307
networks on my network.

00:07:57.327 --> 00:07:57.807
I'm searching.

00:07:57.927 --> 00:07:58.408
I don't see it.

00:08:00.310 --> 00:08:02.050
I would have to tell you the AS number,

00:08:02.250 --> 00:08:02.591
I think.

00:08:02.810 --> 00:08:03.771
I should be able to search by string.

00:08:05.052 --> 00:08:05.452
By what?

00:08:05.973 --> 00:08:06.473
By string.

00:08:08.613 --> 00:08:09.495
All right.

00:08:09.855 --> 00:08:13.057
Let me see if I can find so many kings.

00:08:13.817 --> 00:08:14.617
We should be able to look it

00:08:14.677 --> 00:08:16.819
up via your IP address, right?

00:08:17.540 --> 00:08:17.759
Yeah.

00:08:17.980 --> 00:08:19.060
Yeah, you don't have any, Mark.

00:08:19.081 --> 00:08:19.800
That would be easy, but.

00:08:24.209 --> 00:08:24.869
That's pretty hot.

00:08:24.908 --> 00:08:26.009
That's actually pretty decent.

00:08:26.269 --> 00:08:29.451
It's not King Nodes, is it?

00:08:29.490 --> 00:08:32.591
It might be King Blockchain.

00:08:32.652 --> 00:08:34.371
Or maybe it's just not updated yet.

00:08:34.392 --> 00:08:35.871
Did you try Big Ball's blockchain?

00:08:36.293 --> 00:08:36.613
I didn't.

00:08:36.873 --> 00:08:37.832
That's what you should have done.

00:08:40.134 --> 00:08:40.413
Man,

00:08:40.453 --> 00:08:42.533
it's a fucking rigmarole to get some

00:08:42.553 --> 00:08:44.154
IPv for addresses, I'll tell you.

00:08:45.993 --> 00:08:49.297
yeah it's um it's a bit

00:08:49.538 --> 00:08:55.044
pricey and it can be um but

00:08:55.065 --> 00:08:56.005
like it's nice to rent and

00:08:56.025 --> 00:08:56.886
it's it's cool to be able

00:08:56.907 --> 00:08:58.089
to take do you own those

00:08:58.269 --> 00:08:58.909
did you you didn't buy

00:08:58.929 --> 00:08:59.490
those you're renting them

00:08:59.510 --> 00:09:02.514
right so we kind of rent them it's like

00:09:03.475 --> 00:09:06.738
There's an organization that

00:09:06.778 --> 00:09:08.719
you can join as a member.

00:09:08.960 --> 00:09:11.081
And as a paying member,

00:09:11.260 --> 00:09:15.083
you are allotted an IPv for

00:09:15.144 --> 00:09:15.903
slash twenty four.

00:09:16.323 --> 00:09:17.304
Okay.

00:09:17.325 --> 00:09:17.605
Yeah.

00:09:17.705 --> 00:09:21.227
So you get your own AS and

00:09:21.868 --> 00:09:24.509
you control the

00:09:24.570 --> 00:09:25.210
interconnects and

00:09:25.250 --> 00:09:27.251
everything for your allotment.

00:09:28.836 --> 00:09:31.298
So, yeah, but you don't own them.

00:09:31.678 --> 00:09:32.220
Yeah.

00:09:32.500 --> 00:09:33.139
They're portable.

00:09:33.321 --> 00:09:35.903
I can interconnect them anywhere I want.

00:09:36.482 --> 00:09:38.384
So you're basically leasing them,

00:09:38.403 --> 00:09:39.384
but you can move them if

00:09:39.404 --> 00:09:39.985
you want to move them.

00:09:40.826 --> 00:09:42.727
Yeah, so I can definitely,

00:09:42.807 --> 00:09:45.509
I just control the interconnect.

00:09:45.830 --> 00:09:48.312
And I can use BGP with them

00:09:48.351 --> 00:09:51.955
now and have like multi-home.

00:09:52.235 --> 00:09:52.794
I have the...

00:09:54.419 --> 00:09:57.562
Two incoming internet connections now,

00:09:57.802 --> 00:09:59.123
so I can have failover

00:09:59.462 --> 00:10:00.703
routers and that type of stuff.

00:10:01.323 --> 00:10:01.683
That's fun.

00:10:02.404 --> 00:10:04.865
It is a lot more robust to

00:10:04.926 --> 00:10:06.106
be able to do that than

00:10:06.167 --> 00:10:11.629
rely on your ISP for a range.

00:10:11.910 --> 00:10:12.571
It's not easy, though.

00:10:14.013 --> 00:10:15.953
running bg no like it's it's

00:10:15.994 --> 00:10:17.615
a whole thing especially in

00:10:17.676 --> 00:10:18.996
like a rack situation like

00:10:19.017 --> 00:10:20.498
that unless your provider

00:10:20.538 --> 00:10:21.577
does it you give them like

00:10:21.638 --> 00:10:22.658
here's my ip and I want to

00:10:22.678 --> 00:10:23.980
have and let and you pay

00:10:24.019 --> 00:10:24.801
for some of them to do it

00:10:24.821 --> 00:10:25.380
which would be the way to

00:10:25.400 --> 00:10:29.003
do it the um the fucking

00:10:29.144 --> 00:10:30.644
emails man it's like all of

00:10:30.684 --> 00:10:33.245
these uh like interconnect

00:10:33.285 --> 00:10:34.726
companies and stuff and ip

00:10:34.746 --> 00:10:35.768
providers and shit are

00:10:35.788 --> 00:10:36.808
emailing me now it's like

00:10:36.948 --> 00:10:38.470
oh yeah we saw you oh yeah

00:10:39.537 --> 00:10:41.618
We just, I see you.

00:10:42.018 --> 00:10:43.759
Can we get a meeting to talk about,

00:10:43.778 --> 00:10:46.059
I don't know, fucking IPs?

00:10:46.080 --> 00:10:49.360
You're balls enough to have

00:10:49.400 --> 00:10:53.001
your own IPs set, so that's cool.

00:10:53.543 --> 00:10:53.942
So, you know,

00:10:54.503 --> 00:10:56.803
Cogent's emailed me like ten times.

00:10:57.063 --> 00:10:57.364
Oh, really?

00:10:57.423 --> 00:10:58.004
Like, oh,

00:10:58.024 --> 00:10:59.605
have you seen my other nine emails?

00:11:00.284 --> 00:11:00.945
Can we get a meeting?

00:11:00.965 --> 00:11:02.066
I'm like, what for, man?

00:11:02.698 --> 00:11:02.960
So they're,

00:11:03.039 --> 00:11:04.201
they use that as a lead source.

00:11:04.442 --> 00:11:04.602
They're,

00:11:04.623 --> 00:11:06.807
they're watching the IP ASN or AS

00:11:07.349 --> 00:11:08.510
registrations and using it to say, Hey,

00:11:08.530 --> 00:11:09.493
where are you hosting this shit?

00:11:09.874 --> 00:11:10.495
We have data centers.

00:11:11.538 --> 00:11:13.760
Yeah, but they just want to interconnect.

00:11:13.780 --> 00:11:14.280
They're like, yeah,

00:11:14.421 --> 00:11:15.121
interconnect with this.

00:11:15.182 --> 00:11:17.864
I'm like, fucking... For what?

00:11:17.884 --> 00:11:19.304
For what?

00:11:19.524 --> 00:11:21.106
I'm already connected with something.

00:11:21.206 --> 00:11:22.927
I don't need... That's weird.

00:11:22.988 --> 00:11:23.849
Yeah.

00:11:23.889 --> 00:11:24.328
But anyway.

00:11:24.349 --> 00:11:24.990
That's cool.

00:11:25.009 --> 00:11:26.850
That's nice.

00:11:26.870 --> 00:11:27.392
That is cool.

00:11:27.451 --> 00:11:28.032
So, you know,

00:11:28.152 --> 00:11:29.673
that whole thing is advancing.

00:11:29.894 --> 00:11:31.235
I'm running out of RAM already.

00:11:33.056 --> 00:11:33.697
Need more RAM.

00:11:34.557 --> 00:11:35.378
Need more drives.

00:11:35.898 --> 00:11:37.198
You know, I don't know...

00:11:40.149 --> 00:11:42.130
So if you,

00:11:42.171 --> 00:11:42.831
have you done any

00:11:42.890 --> 00:11:44.511
hyper-converged storage before?

00:11:45.072 --> 00:11:45.892
You would have with your,

00:11:47.692 --> 00:11:49.754
with like your VMware deployments, right?

00:11:50.215 --> 00:11:51.735
So like distributed.

00:11:52.155 --> 00:11:52.596
Not at Rhino.

00:11:53.856 --> 00:11:54.616
No?

00:11:54.636 --> 00:11:55.057
I don't think it's,

00:11:55.356 --> 00:11:55.878
I just don't think it's

00:11:55.918 --> 00:11:57.558
fast enough for what we do,

00:11:57.879 --> 00:11:59.078
but it doesn't really matter.

00:11:59.139 --> 00:12:00.059
Cause I wasn't, I mean,

00:12:00.120 --> 00:12:00.860
when we were originally

00:12:01.059 --> 00:12:01.821
building all this out,

00:12:03.163 --> 00:12:03.924
There's some things that we

00:12:04.044 --> 00:12:05.485
that we should do that for.

00:12:05.546 --> 00:12:08.307
So like like in our own data

00:12:08.326 --> 00:12:09.048
centers are turning more

00:12:09.067 --> 00:12:09.927
into like monitoring

00:12:09.967 --> 00:12:11.469
management and signing than

00:12:11.489 --> 00:12:12.990
they are turning into like nodes,

00:12:14.230 --> 00:12:14.711
which is fine.

00:12:14.730 --> 00:12:16.011
So it should be so.

00:12:16.572 --> 00:12:17.732
So from that perspective,

00:12:18.113 --> 00:12:19.214
there is benefit to that

00:12:20.614 --> 00:12:21.875
versus just like having on

00:12:22.115 --> 00:12:23.076
and some sort of redundant

00:12:23.115 --> 00:12:23.735
storage and then like

00:12:23.775 --> 00:12:25.197
moving things across when we want to,

00:12:25.277 --> 00:12:25.957
which is what we do now.

00:12:26.928 --> 00:12:28.831
But but we've talked about

00:12:28.850 --> 00:12:29.370
it a couple of times

00:12:29.390 --> 00:12:30.192
because we do have I mean,

00:12:30.251 --> 00:12:31.092
all of our I mean,

00:12:31.113 --> 00:12:31.773
the issue with owning all

00:12:31.793 --> 00:12:32.573
this shit is that it all

00:12:32.833 --> 00:12:33.835
starts to age out and it's

00:12:33.855 --> 00:12:34.875
already been a few years now.

00:12:35.416 --> 00:12:37.859
And so we're starting to have SSD,

00:12:37.918 --> 00:12:39.299
obviously SSD failures all the time,

00:12:39.320 --> 00:12:41.221
but or NVME failures as well.

00:12:41.240 --> 00:12:42.042
But now we're starting to

00:12:42.062 --> 00:12:42.802
get like other types of

00:12:42.842 --> 00:12:43.823
things that are starting to happen,

00:12:43.864 --> 00:12:45.884
like fans dying and, you know,

00:12:45.904 --> 00:12:46.826
like weird shit like that

00:12:46.846 --> 00:12:47.826
that ends up just getting

00:12:47.866 --> 00:12:48.648
stressed over years.

00:12:49.628 --> 00:12:50.489
So we're starting to replace

00:12:50.548 --> 00:12:51.089
more hardware.

00:12:51.109 --> 00:12:52.349
And as we replace more hardware,

00:12:52.749 --> 00:12:54.590
moving shit is a fucking pain in the ass.

00:12:54.750 --> 00:12:55.470
Like it just takes,

00:12:55.910 --> 00:12:56.990
it's just slow to move and

00:12:57.010 --> 00:12:58.331
I don't have enough room on machines.

00:12:58.390 --> 00:12:59.011
And so you're kind of like,

00:12:59.211 --> 00:13:00.611
it's this fucking nightmare

00:13:00.672 --> 00:13:02.352
jigsaw puzzle of trying to

00:13:02.373 --> 00:13:03.092
move shit around to get

00:13:03.133 --> 00:13:03.753
something offline.

00:13:03.773 --> 00:13:04.273
And then we're going to

00:13:04.293 --> 00:13:05.394
replace it and you rebuild

00:13:05.453 --> 00:13:06.274
it and add it to all the

00:13:06.293 --> 00:13:07.455
distributed port switches

00:13:07.475 --> 00:13:08.014
and all that shit.

00:13:08.934 --> 00:13:09.554
It just takes time.

00:13:09.575 --> 00:13:10.534
It's a pain in the dick.

00:13:11.755 --> 00:13:13.535
So just to answer your question,

00:13:14.015 --> 00:13:14.856
some of that storage would

00:13:14.876 --> 00:13:16.476
be easier because it would

00:13:16.496 --> 00:13:17.917
just make those moves a lot faster.

00:13:18.096 --> 00:13:21.138
And moving CPU and computer is easy.

00:13:21.197 --> 00:13:23.219
It's just the drives that really make a,

00:13:23.839 --> 00:13:24.099
you know,

00:13:24.519 --> 00:13:26.639
moving at two hundred fifty six gigabyte,

00:13:26.720 --> 00:13:28.620
even over ten gig just takes some time.

00:13:28.639 --> 00:13:29.440
And it's, you know,

00:13:29.480 --> 00:13:30.279
you got to have enough room

00:13:30.299 --> 00:13:31.181
for it and all that kind of shit,

00:13:31.520 --> 00:13:32.280
which would be nice to get rid of.

00:13:33.214 --> 00:13:34.014
So we,

00:13:34.274 --> 00:13:36.395
like I have migrations over a fifty

00:13:36.416 --> 00:13:39.197
gig network, which is reasonably fast.

00:13:39.597 --> 00:13:40.097
Yeah.

00:13:40.357 --> 00:13:43.539
Um, but so we have two, I have two things,

00:13:43.600 --> 00:13:43.841
right?

00:13:44.081 --> 00:13:49.083
So I have on each host, I have like a, um,

00:13:50.465 --> 00:13:53.726
an array of gen five discs with, um,

00:13:56.620 --> 00:13:58.841
uh, ZFS, uh, as local storage.

00:13:59.381 --> 00:14:00.702
So some things run off the

00:14:00.722 --> 00:14:02.222
local storage and then

00:14:02.822 --> 00:14:03.683
other things run off

00:14:03.703 --> 00:14:04.803
hyperconverged storage,

00:14:04.923 --> 00:14:06.125
which is exactly like what

00:14:06.144 --> 00:14:07.384
you were talking about before.

00:14:08.345 --> 00:14:11.586
Um, like we have, for example,

00:14:12.826 --> 00:14:14.326
maybe HA proxy is a couple

00:14:14.346 --> 00:14:17.207
of instances of HA proxy running off, um,

00:14:17.268 --> 00:14:19.249
hyperconverged storage, uh,

00:14:19.349 --> 00:14:22.309
other controllers, monitoring, um,

00:14:22.450 --> 00:14:24.390
signers, uh,

00:14:25.875 --> 00:14:27.657
validators that don't like

00:14:27.697 --> 00:14:28.937
stateless validators that

00:14:28.998 --> 00:14:31.538
type of stuff um but all

00:14:31.599 --> 00:14:32.940
backing nodes at the moment

00:14:32.960 --> 00:14:35.160
are all on local storage um

00:14:36.361 --> 00:14:38.363
yeah and a lot of those

00:14:38.482 --> 00:14:41.585
will stay with our old um

00:14:41.625 --> 00:14:43.066
depending on like the

00:14:43.105 --> 00:14:44.067
network and what the

00:14:44.126 --> 00:14:45.748
expectation is from the

00:14:45.788 --> 00:14:47.828
network level because you

00:14:47.849 --> 00:14:49.309
know part of our um our

00:14:52.866 --> 00:14:53.947
appeal has been an

00:14:53.988 --> 00:14:56.149
australian um validator so

00:14:56.168 --> 00:14:57.230
we run some stuff

00:14:57.490 --> 00:14:58.431
specifically out of

00:14:58.451 --> 00:15:01.232
australia for that um and

00:15:01.293 --> 00:15:03.254
other big heavy items like

00:15:03.434 --> 00:15:04.655
um you know archives and

00:15:04.676 --> 00:15:05.475
stuff it's good to be able

00:15:05.495 --> 00:15:06.517
to run those locally just

00:15:06.537 --> 00:15:08.357
with good network storage

00:15:09.519 --> 00:15:10.620
yeah because it's too

00:15:10.659 --> 00:15:12.701
expensive expensive yeah yeah

00:15:13.789 --> 00:15:14.870
So all the throwaway nodes I

00:15:14.890 --> 00:15:16.272
think we'll keep elsewhere,

00:15:16.331 --> 00:15:17.552
but all the important stuff

00:15:17.572 --> 00:15:18.734
is like in-house now.

00:15:19.693 --> 00:15:20.674
But the hyper-converged storage,

00:15:20.835 --> 00:15:21.414
as you said,

00:15:21.514 --> 00:15:24.116
is slow if you don't have

00:15:24.157 --> 00:15:25.217
shitloads of drives.

00:15:25.378 --> 00:15:28.519
So we had the initial idea

00:15:28.559 --> 00:15:29.821
of having like some bigger

00:15:29.860 --> 00:15:31.763
drives on there, thinking that...

00:15:32.743 --> 00:15:34.225
uh you know really high

00:15:34.264 --> 00:15:35.525
performance discs would

00:15:35.586 --> 00:15:39.408
pick up the slack um of you

00:15:39.428 --> 00:15:40.789
know the overhead of a

00:15:40.830 --> 00:15:43.111
hyper converged uh solution

00:15:43.692 --> 00:15:46.075
but don't really work out

00:15:46.115 --> 00:15:47.756
that way they only go so

00:15:47.777 --> 00:15:50.739
fast so um we're like

00:15:51.100 --> 00:15:52.160
getting rid of those discs

00:15:52.240 --> 00:15:53.100
or keeping them using

00:15:53.221 --> 00:15:54.783
something else and then I

00:15:54.802 --> 00:15:55.683
think I'm just going to end

00:15:55.744 --> 00:15:56.605
up ordering just

00:15:57.748 --> 00:16:01.113
like boxes of uh like nine

00:16:01.173 --> 00:16:04.017
sixty gig discs um like

00:16:04.116 --> 00:16:05.479
older gen nine sixty gig

00:16:06.100 --> 00:16:07.903
discs and see how that goes

00:16:07.942 --> 00:16:09.085
just populate everything

00:16:09.644 --> 00:16:11.288
you mean mvmes or what do you mean

00:16:12.216 --> 00:16:13.677
uh like gen three or four

00:16:13.697 --> 00:16:14.238
nvmes oh okay yeah yeah

00:16:15.337 --> 00:16:16.499
like nine sixties or one

00:16:16.538 --> 00:16:18.039
point seven uh nine twos or

00:16:18.059 --> 00:16:18.541
something like that but

00:16:18.581 --> 00:16:19.541
enterprise like you know

00:16:19.682 --> 00:16:20.501
you slide it enterprise

00:16:20.542 --> 00:16:22.263
drives udot too yeah yeah

00:16:22.364 --> 00:16:23.563
yeah that's basically what

00:16:23.583 --> 00:16:24.784
we have it's kind of what

00:16:24.884 --> 00:16:26.486
that's kind of been our our

00:16:26.547 --> 00:16:27.427
thing around it would you

00:16:27.447 --> 00:16:30.610
know again like I think the

00:16:30.730 --> 00:16:31.269
it's a nice thing you

00:16:31.289 --> 00:16:32.471
should be able you really

00:16:32.490 --> 00:16:33.451
should have a mix of those

00:16:33.552 --> 00:16:34.773
I think would be good because like

00:16:35.432 --> 00:16:36.192
Things like, you know,

00:16:36.373 --> 00:16:37.573
Postgres or like some

00:16:37.614 --> 00:16:39.575
database type stuff or monitoring or,

00:16:41.615 --> 00:16:41.835
you know,

00:16:41.875 --> 00:16:43.755
some sort of storage things or I

00:16:43.916 --> 00:16:46.576
don't know, maybe logs, shit like that,

00:16:46.616 --> 00:16:46.937
like that.

00:16:47.017 --> 00:16:47.957
That stuff's nice to have in

00:16:47.998 --> 00:16:49.457
a centralized piece that

00:16:49.557 --> 00:16:50.639
you can just have a block

00:16:50.658 --> 00:16:51.458
and not worry about if it's

00:16:51.479 --> 00:16:52.099
a little bit slow.

00:16:52.119 --> 00:16:53.078
It doesn't make a difference, right?

00:16:53.099 --> 00:16:53.940
You're not missing anything.

00:16:54.984 --> 00:16:56.745
Um, and then leave notes to be notes,

00:16:56.884 --> 00:16:57.065
right.

00:16:57.105 --> 00:16:58.105
Or even signer signers are a

00:16:58.125 --> 00:16:58.644
great thing with that.

00:16:58.664 --> 00:16:59.546
You can just move that around.

00:16:59.566 --> 00:17:00.426
CPU doesn't matter.

00:17:00.446 --> 00:17:01.866
You know, if you, yeah,

00:17:01.907 --> 00:17:03.106
things that don't have like

00:17:03.126 --> 00:17:04.728
a whole lot of IO.

00:17:04.748 --> 00:17:04.867
Yeah.

00:17:04.887 --> 00:17:06.167
Um, yeah.

00:17:06.969 --> 00:17:09.229
And so we tag everything in here.

00:17:09.410 --> 00:17:12.730
So if it's like, um, on the CIF,

00:17:12.770 --> 00:17:14.590
the hyperconverged storage, uh,

00:17:14.611 --> 00:17:17.913
we can tag it then as, um, fully HA.

00:17:18.192 --> 00:17:19.232
So we get all the fail over

00:17:19.252 --> 00:17:20.634
and everything works perfectly.

00:17:21.634 --> 00:17:22.835
um which is great but other

00:17:22.855 --> 00:17:24.016
things yeah we either have

00:17:24.036 --> 00:17:25.076
to migrate them or just let

00:17:25.096 --> 00:17:26.178
them go down if I need to

00:17:26.218 --> 00:17:27.598
restart a host or something

00:17:27.778 --> 00:17:28.838
it's not it's pretty quick

00:17:28.858 --> 00:17:30.861
to migrate like even a you

00:17:30.881 --> 00:17:31.801
know a terabyte it's pretty

00:17:31.821 --> 00:17:33.843
quick over fifty gig yeah

00:17:34.063 --> 00:17:35.243
um it's really and we don't

00:17:35.263 --> 00:17:36.525
I don't move that that

00:17:36.605 --> 00:17:37.346
often you know what I mean

00:17:37.365 --> 00:17:38.226
it's not that it's not that

00:17:38.246 --> 00:17:39.047
it moves that often just

00:17:39.106 --> 00:17:41.548
when it does for me usually

00:17:41.588 --> 00:17:42.689
we're constantly bumping up

00:17:42.710 --> 00:17:44.211
against having too much and

00:17:44.230 --> 00:17:45.932
not enough storage so yeah

00:17:46.352 --> 00:17:47.073
Then it's like, all right,

00:17:47.113 --> 00:17:48.513
what machine has enough room for this?

00:17:48.574 --> 00:17:49.234
And oh, fuck,

00:17:49.255 --> 00:17:50.055
this machine only has turn

00:17:50.075 --> 00:17:50.875
fifty six gigs.

00:17:50.915 --> 00:17:52.518
And I'm shutting down a

00:17:52.538 --> 00:17:53.759
machine with a terabyte of RAM.

00:17:54.278 --> 00:17:54.398
Well,

00:17:54.419 --> 00:17:55.299
you shut down a machine with terabyte

00:17:55.319 --> 00:17:56.340
of RAM with a bunch of shit on it.

00:17:56.540 --> 00:17:58.021
Like it's tough to find

00:17:58.061 --> 00:18:00.324
places to go stick this type of stuff.

00:18:00.364 --> 00:18:00.684
Right.

00:18:00.724 --> 00:18:02.026
And so that's just turn off like.

00:18:02.486 --> 00:18:03.546
I don't move everything.

00:18:03.586 --> 00:18:04.326
If it's redundant, no,

00:18:04.366 --> 00:18:04.987
I don't give a shit.

00:18:05.047 --> 00:18:06.166
But if it's some other type of stuff,

00:18:06.186 --> 00:18:09.489
you've got to find a place for it.

00:18:10.409 --> 00:18:14.109
We just got another batch of

00:18:14.150 --> 00:18:15.211
last-gen hardware in,

00:18:15.530 --> 00:18:17.432
and then we ended up

00:18:17.571 --> 00:18:19.692
ordering a RAM for it.

00:18:19.732 --> 00:18:21.512
I think we have something

00:18:21.553 --> 00:18:23.673
along the lines of sixty-four,

00:18:23.733 --> 00:18:25.134
sixteen gig sticks or

00:18:25.154 --> 00:18:25.875
something like that.

00:18:26.815 --> 00:18:28.996
We unboxed all that and

00:18:29.016 --> 00:18:29.836
tried to get that stuff

00:18:29.855 --> 00:18:30.836
figured out what's going on what.

00:18:31.737 --> 00:18:32.357
You can never have enough

00:18:32.377 --> 00:18:33.337
RAM in those machines, though.

00:18:33.397 --> 00:18:36.119
That's one thing we always over-provision.

00:18:37.740 --> 00:18:39.461
So I've been assisting a

00:18:39.560 --> 00:18:40.781
friend of mine who's got a

00:18:40.882 --> 00:18:42.123
software development company.

00:18:42.143 --> 00:18:43.403
He's been building his own

00:18:43.442 --> 00:18:47.905
cluster for Kubernetes.

00:18:47.986 --> 00:18:48.605
Mm-hmm.

00:18:49.364 --> 00:18:51.825
And every time he gets some

00:18:52.085 --> 00:18:53.506
new hardware in the mail, he, like,

00:18:53.526 --> 00:18:54.346
sends me a photo.

00:18:55.105 --> 00:18:57.106
But he's on, like, older hardware, like,

00:18:57.467 --> 00:18:59.248
Gen XIV Dell stuff.

00:19:00.127 --> 00:19:04.429
And he got this bag of RAM.

00:19:05.869 --> 00:19:08.211
And it's just a sack.

00:19:08.770 --> 00:19:10.791
Literally just a sack of RAM sticks.

00:19:12.211 --> 00:19:13.172
Like, garbage bag.

00:19:13.192 --> 00:19:14.452
I was like, holy shit, man.

00:19:15.286 --> 00:19:16.268
This stuff is like a mix of

00:19:16.288 --> 00:19:19.592
high speed DDR three and early DDR four.

00:19:19.872 --> 00:19:21.134
They're not expensive things.

00:19:21.173 --> 00:19:23.576
So they just end up like

00:19:23.616 --> 00:19:24.538
some enterprise gets rid of

00:19:25.498 --> 00:19:26.858
whatever a thousands of the

00:19:26.878 --> 00:19:27.839
sticks that they bought

00:19:27.880 --> 00:19:28.339
over the years right

00:19:28.359 --> 00:19:28.921
they're just getting rid of

00:19:28.941 --> 00:19:29.861
this shit and so they part

00:19:29.881 --> 00:19:30.602
all this stuff out and just

00:19:30.701 --> 00:19:32.022
like I'll send you a twenty

00:19:32.063 --> 00:19:33.503
pound bag of ram and then

00:19:34.044 --> 00:19:35.486
yeah I was just amazed that

00:19:35.506 --> 00:19:36.425
they're like not even in a

00:19:36.465 --> 00:19:37.567
tray it's just like just a

00:19:37.626 --> 00:19:38.928
fucking just chucked in a

00:19:38.968 --> 00:19:40.548
bag just get it out of here

00:19:40.689 --> 00:19:41.450
it's like a garage sale

00:19:41.470 --> 00:19:42.171
like just get the shit out

00:19:42.191 --> 00:19:43.852
of here yeah I don't get

00:19:43.892 --> 00:19:45.113
all these old like xeon

00:19:45.173 --> 00:19:47.615
gold cpus that were like I

00:19:47.634 --> 00:19:48.615
don't know fifty bucks each

00:19:48.654 --> 00:19:49.875
but they would like some of

00:19:49.895 --> 00:19:50.636
them were just butchered

00:19:50.656 --> 00:19:52.157
from transport they just

00:19:52.178 --> 00:19:53.179
love floating around just

00:19:54.491 --> 00:19:55.237
Sorry.

00:19:55.277 --> 00:19:55.961
Clean them up a little bit.

00:19:56.727 --> 00:19:57.451
Just blow on them.

00:19:58.617 --> 00:20:02.759
He bought some like SAS NVMe.

00:20:03.058 --> 00:20:05.240
Sorry, SAS SSDs.

00:20:06.259 --> 00:20:08.119
And I think like they're all

00:20:08.140 --> 00:20:08.980
like nine sixties.

00:20:09.101 --> 00:20:09.381
Oh, sorry.

00:20:09.401 --> 00:20:10.101
That was SATA SSDs.

00:20:10.121 --> 00:20:11.780
I think one of them had like

00:20:11.861 --> 00:20:15.541
seven years of fucking like hours on it.

00:20:16.561 --> 00:20:20.603
Oh, really?

00:20:20.682 --> 00:20:20.823
Yeah.

00:20:20.843 --> 00:20:21.943
You can't find big SAS drives.

00:20:22.523 --> 00:20:23.604
All of our stuff has SAS and

00:20:23.763 --> 00:20:24.564
SATA backplanes.

00:20:24.584 --> 00:20:25.605
And SAS is usually nice if

00:20:25.625 --> 00:20:26.164
you can find them,

00:20:26.184 --> 00:20:26.904
but they're always like...

00:20:27.744 --> 00:20:29.605
either their fifteen thousand RPM spinners,

00:20:30.106 --> 00:20:31.146
which can be useful in

00:20:31.186 --> 00:20:35.329
certain situations or their smaller SSDs.

00:20:35.349 --> 00:20:36.391
They didn't really make like

00:20:36.411 --> 00:20:37.171
I don't think there's any

00:20:37.211 --> 00:20:40.212
four terabyte or eight terabyte SAS SSDs.

00:20:40.232 --> 00:20:41.294
I think those things exist.

00:20:42.954 --> 00:20:44.256
I have three point eight

00:20:44.276 --> 00:20:46.637
four terabyte SAS SSDs.

00:20:46.678 --> 00:20:46.778
Yeah,

00:20:46.798 --> 00:20:48.999
that might be the biggest that they make.

00:20:50.140 --> 00:20:50.400
Yeah,

00:20:50.420 --> 00:20:52.922
it could be pretty like they're not

00:20:52.942 --> 00:20:54.742
much cheaper than NVMe.

00:20:54.762 --> 00:20:56.644
In some cases, they're like more expensive,

00:20:56.723 --> 00:20:57.484
even secondhand.

00:20:57.659 --> 00:20:58.180
No, they should be,

00:20:58.220 --> 00:20:59.481
they usually are more expensive.

00:21:00.865 --> 00:21:01.144
Yeah.

00:21:01.184 --> 00:21:02.166
I think if I remember correctly,

00:21:02.307 --> 00:21:07.036
a little less latency, more direct path.

00:21:08.119 --> 00:21:09.119
well they're just they're

00:21:09.140 --> 00:21:10.840
just discontinued nvme's

00:21:10.861 --> 00:21:12.641
got a more direct path

00:21:12.661 --> 00:21:13.521
because it's connected to

00:21:13.541 --> 00:21:15.001
the cpu yeah there's

00:21:15.061 --> 00:21:16.363
nothing better about sass

00:21:16.403 --> 00:21:17.942
it's just fucking that they

00:21:18.002 --> 00:21:19.663
don't make them yeah no I'm

00:21:19.683 --> 00:21:20.423
talking about like I'm not

00:21:20.463 --> 00:21:22.125
talking about like um nvme

00:21:22.164 --> 00:21:23.045
interfaces I'm just talking

00:21:23.065 --> 00:21:24.884
about like just uh what was

00:21:24.904 --> 00:21:26.625
available in our twenty

00:21:26.685 --> 00:21:27.806
eighteen to twenty twenty

00:21:27.846 --> 00:21:29.586
frame of hardware that we own

00:21:30.887 --> 00:21:31.169
Yeah.

00:21:31.209 --> 00:21:32.913
There's like a, well, I mean,

00:21:32.932 --> 00:21:34.537
it's been hard to get hardware lately.

00:21:34.557 --> 00:21:35.638
You're paying ridiculous

00:21:35.699 --> 00:21:38.846
money for just mediocre shit.

00:21:38.926 --> 00:21:39.186
Yep.

00:21:39.689 --> 00:21:39.729
Um,

00:21:41.363 --> 00:21:41.844
I think it's getting a

00:21:41.864 --> 00:21:42.604
little bit better now.

00:21:42.663 --> 00:21:43.664
I think the storage prices

00:21:43.705 --> 00:21:45.607
are coming down a little bit.

00:21:45.647 --> 00:21:46.848
But, you know,

00:21:47.048 --> 00:21:50.532
when all of the AI hype

00:21:50.553 --> 00:21:51.993
started and they started

00:21:52.034 --> 00:21:54.636
building like GPU arrays everywhere,

00:21:54.717 --> 00:21:56.239
like with millions of GPUs,

00:21:57.420 --> 00:21:58.480
that put like a massive

00:21:58.500 --> 00:22:01.564
strain on Flash because...

00:22:03.806 --> 00:22:05.186
Like, sure, you need GPUs,

00:22:05.227 --> 00:22:06.827
but the GPUs take memory

00:22:07.268 --> 00:22:08.269
and then the systems with

00:22:08.288 --> 00:22:09.670
the GPUs in them take memory.

00:22:09.890 --> 00:22:10.611
And then you have to have

00:22:10.651 --> 00:22:11.851
huge storage arrays to go

00:22:11.892 --> 00:22:13.532
along with the GPUs.

00:22:14.353 --> 00:22:15.294
And so, I mean,

00:22:15.634 --> 00:22:17.976
the hype was on Nvidia and

00:22:18.016 --> 00:22:19.076
stuff like that with all of

00:22:19.115 --> 00:22:21.178
the GPUs that they were selling for AI,

00:22:21.218 --> 00:22:22.338
like all the H. One

00:22:22.378 --> 00:22:23.638
hundreds and H. Two hundreds of stuff.

00:22:24.779 --> 00:22:26.361
And people didn't really

00:22:26.421 --> 00:22:28.121
talk about the strain that

00:22:28.161 --> 00:22:29.541
put on the supply chain for

00:22:29.781 --> 00:22:30.862
storage and flash.

00:22:32.022 --> 00:22:32.762
But it was real.

00:22:32.923 --> 00:22:34.663
And the fucking prices went

00:22:34.683 --> 00:22:37.204
through the roof over the

00:22:37.244 --> 00:22:38.484
period of like six months.

00:22:39.326 --> 00:22:41.026
So hopefully that's like

00:22:41.066 --> 00:22:42.227
starting to alleviate now

00:22:42.307 --> 00:22:44.007
or they've ramped up supply or whatever.

00:22:44.027 --> 00:22:46.647
But yeah,

00:22:46.667 --> 00:22:48.288
if you've been buying flash over

00:22:48.308 --> 00:22:50.089
the last year,

00:22:50.369 --> 00:22:51.390
you've probably been stung.

00:22:52.270 --> 00:22:53.050
The AI tax.

00:22:54.010 --> 00:22:54.790
I should have been buying more NVIDIA.

00:22:54.810 --> 00:22:57.393
NVIDIA is what I should have been buying.

00:22:57.413 --> 00:22:58.492
Stocks?

00:22:58.613 --> 00:23:00.233
Yeah.

00:23:00.294 --> 00:23:00.815
Stocks.

00:23:01.234 --> 00:23:03.256
So I remember just after...

00:23:03.355 --> 00:23:07.298
Do you remember NVIDIA had

00:23:07.317 --> 00:23:10.160
a bit of a run during COVID

00:23:10.180 --> 00:23:12.580
when everyone was buying gaming GPUs?

00:23:12.621 --> 00:23:12.721
Yeah.

00:23:13.580 --> 00:23:14.321
And then after...

00:23:15.423 --> 00:23:16.663
COVID, it like crashed.

00:23:17.625 --> 00:23:19.105
When everyone stopped buying GPUs,

00:23:19.145 --> 00:23:20.507
just the ass fell out of it

00:23:21.567 --> 00:23:22.627
for like a week.

00:23:23.249 --> 00:23:24.849
And then they're like, oh,

00:23:25.049 --> 00:23:26.431
did we mention about AI?

00:23:26.671 --> 00:23:29.792
We have this other group

00:23:29.813 --> 00:23:30.634
that's growing at four

00:23:30.653 --> 00:23:31.594
hundred percent a quarter.

00:23:31.614 --> 00:23:35.477
And it just made the the

00:23:35.537 --> 00:23:38.979
entire pump of COVID for

00:23:39.078 --> 00:23:40.500
NVIDIA just look like a

00:23:40.560 --> 00:23:42.501
little blip on the fucking chart.

00:23:43.592 --> 00:23:44.292
What are they like?

00:23:45.233 --> 00:23:47.096
Top five now?

00:23:47.135 --> 00:23:47.175
No,

00:23:47.195 --> 00:23:48.116
I think they're by far the largest

00:23:48.136 --> 00:23:49.238
company in the world, aren't they?

00:23:49.959 --> 00:23:50.278
Are they?

00:23:50.759 --> 00:23:51.441
Bigger than Apple?

00:23:51.760 --> 00:23:52.060
Oh, yeah.

00:23:52.721 --> 00:23:53.083
I think so.

00:23:53.163 --> 00:23:53.722
Oh, shit.

00:23:53.742 --> 00:23:55.384
I'm pretty sure.

00:23:55.464 --> 00:23:57.047
They're like, what's their market cap?

00:23:57.267 --> 00:23:58.248
Three point three three.

00:23:58.348 --> 00:23:59.329
And Apple is...

00:24:01.424 --> 00:24:03.405
Actually, three point seven six.

00:24:03.425 --> 00:24:03.885
Now they're behind.

00:24:03.905 --> 00:24:05.326
They're behind.

00:24:05.346 --> 00:24:06.126
Apple's been up a little bit

00:24:06.366 --> 00:24:08.086
the last the last month or so,

00:24:08.106 --> 00:24:09.907
which I don't know why.

00:24:09.968 --> 00:24:11.148
I just don't understand the stock.

00:24:12.388 --> 00:24:14.490
It doesn't mean while there

00:24:14.529 --> 00:24:16.390
is no strategy at this organization.

00:24:16.911 --> 00:24:18.330
Zero at Apple.

00:24:18.651 --> 00:24:19.872
Yeah.

00:24:19.991 --> 00:24:21.471
Just all this stuff is such

00:24:21.491 --> 00:24:23.173
a fucking bolt on last minute.

00:24:23.353 --> 00:24:23.932
Oh, shit.

00:24:24.173 --> 00:24:25.334
I guess people want this stuff.

00:24:27.608 --> 00:24:29.790
iPhone is like, it's totally stagnant.

00:24:31.031 --> 00:24:31.971
Vision Pro is dead.

00:24:32.553 --> 00:24:33.673
The watch is going nowhere.

00:24:34.213 --> 00:24:35.054
Hardware is fucking awesome.

00:24:35.094 --> 00:24:35.634
Don't get me wrong.

00:24:35.894 --> 00:24:36.895
But like, what's next?

00:24:37.096 --> 00:24:37.635
Where are they going?

00:24:37.655 --> 00:24:38.757
I don't know.

00:24:38.797 --> 00:24:42.138
Yeah, I still like their laptops.

00:24:42.298 --> 00:24:44.040
Me too.

00:24:44.060 --> 00:24:44.800
That only counts for like

00:24:44.961 --> 00:24:46.082
four percent of the business or whatever,

00:24:46.122 --> 00:24:46.903
or fourteen percent or

00:24:46.923 --> 00:24:47.363
something like that.

00:24:48.507 --> 00:24:50.227
I remember when they just...

00:24:51.327 --> 00:24:54.387
They ignored their compute

00:24:54.528 --> 00:24:57.269
arm for so long when they

00:24:57.328 --> 00:24:58.449
first started the iPhone

00:24:58.489 --> 00:24:59.409
and it sort of took off.

00:24:59.808 --> 00:25:01.269
Because Mac was dead.

00:25:01.328 --> 00:25:03.710
No one really used it.

00:25:03.769 --> 00:25:05.109
Maybe the odd rich person

00:25:05.150 --> 00:25:06.490
would just have one of

00:25:06.509 --> 00:25:07.871
those funky colored plastic

00:25:07.971 --> 00:25:09.211
things lying around their house.

00:25:09.230 --> 00:25:11.971
For software, it's always been deeply,

00:25:12.050 --> 00:25:13.291
deeply, deeply popular.

00:25:13.311 --> 00:25:15.291
It never fell out of vogue.

00:25:15.663 --> 00:25:17.864
But it was not a consumer device.

00:25:18.223 --> 00:25:20.184
Like I'm going back to like

00:25:20.305 --> 00:25:21.765
the early two thousands, you know,

00:25:22.404 --> 00:25:23.826
where you'd see like a G

00:25:23.846 --> 00:25:24.965
four floating around

00:25:25.026 --> 00:25:26.267
someone's house or some shit,

00:25:26.886 --> 00:25:28.528
the green plastic fucking

00:25:28.548 --> 00:25:29.208
see-through thing.

00:25:30.897 --> 00:25:32.219
Uh, Apple had Motorola.

00:25:32.419 --> 00:25:34.559
They, they went to par PC,

00:25:34.619 --> 00:25:35.359
which was a nice little

00:25:35.400 --> 00:25:36.121
bump at that time.

00:25:36.141 --> 00:25:38.422
But Intel was so fucking good at,

00:25:38.701 --> 00:25:40.522
at fab for so many years.

00:25:40.762 --> 00:25:42.703
And X-Eighty-six was just kicking ass.

00:25:42.784 --> 00:25:42.983
Right.

00:25:43.183 --> 00:25:44.365
And yeah,

00:25:44.384 --> 00:25:46.144
Steve finally came back and then they,

00:25:46.346 --> 00:25:47.766
obviously I've before iPhone,

00:25:47.786 --> 00:25:48.686
they made a decision to

00:25:48.727 --> 00:25:50.647
move to Intel and that took

00:25:50.688 --> 00:25:51.768
some time to be able to do that.

00:25:51.887 --> 00:25:52.888
Intel is by far the biggest

00:25:52.909 --> 00:25:54.509
fab let's go X-Eighty-six

00:25:54.690 --> 00:25:55.430
that happened right when

00:25:55.450 --> 00:25:56.130
they moved to Intel.

00:25:56.730 --> 00:25:57.111
And then

00:25:57.971 --> 00:26:00.093
um after iphone launched and

00:26:00.472 --> 00:26:01.473
and the revenue went to

00:26:01.973 --> 00:26:02.734
seventy percent or eight

00:26:02.755 --> 00:26:03.715
percent of the all revenue

00:26:04.096 --> 00:26:04.916
and look at the mac that's

00:26:04.936 --> 00:26:05.797
sitting there as intel and

00:26:05.857 --> 00:26:06.938
intel starts falling apart

00:26:06.978 --> 00:26:08.380
because they start going to

00:26:09.299 --> 00:26:10.760
like that that company I

00:26:10.780 --> 00:26:12.242
mean that guy just uh was

00:26:12.282 --> 00:26:14.163
just exited yesterday right

00:26:14.423 --> 00:26:14.984
uh what's his face

00:26:15.644 --> 00:26:17.086
And so Intel's had... I mean,

00:26:17.267 --> 00:26:18.087
it's such a sad story.

00:26:18.208 --> 00:26:18.868
We'll see what happens.

00:26:18.888 --> 00:26:19.951
But it's the only one that

00:26:19.990 --> 00:26:21.352
makes any... The only fab

00:26:21.372 --> 00:26:22.173
left in the United States

00:26:22.192 --> 00:26:23.634
other than TSMC that has some stuff here.

00:26:23.714 --> 00:26:28.760
And then when all the TSMC

00:26:28.780 --> 00:26:30.242
stuff happened with ARM...

00:26:30.803 --> 00:26:32.784
And with iPhone and then obviously moving,

00:26:33.324 --> 00:26:34.204
then getting off Intel

00:26:34.224 --> 00:26:35.184
because Intel had zero

00:26:35.204 --> 00:26:37.205
strategy around desktop whatsoever,

00:26:37.526 --> 00:26:40.528
no CPU strategy, just awful.

00:26:40.548 --> 00:26:41.167
So that's the reason they

00:26:41.208 --> 00:26:42.468
moved to their own chipset, right,

00:26:42.488 --> 00:26:43.409
to take it all in-house to

00:26:43.449 --> 00:26:44.648
be able to get out of the situation.

00:26:45.450 --> 00:26:46.170
And now here we are.

00:26:46.650 --> 00:26:49.632
Like, there's no, I mean, it's AMD.

00:26:51.011 --> 00:26:52.212
Who else is doing major chip,

00:26:52.252 --> 00:26:53.634
like massive chipset design?

00:26:54.034 --> 00:26:55.253
AMD, Qualcomm, and Apple?

00:26:55.374 --> 00:26:55.875
That's really it?

00:26:56.994 --> 00:26:57.315
Yeah.

00:26:57.335 --> 00:26:58.955
Intel's not doing it?

00:26:59.653 --> 00:27:01.734
Did I ever share my Intel Bitcoin story?

00:27:02.335 --> 00:27:03.557
I think Risk are working hard.

00:27:03.757 --> 00:27:04.477
Yeah, man, go for it.

00:27:06.419 --> 00:27:07.160
When I was an intern at

00:27:07.259 --> 00:27:08.641
Intel in twenty thirteen,

00:27:09.561 --> 00:27:10.843
I worked on the Xeon Phi team,

00:27:10.883 --> 00:27:13.645
which was kind of Intel's

00:27:13.965 --> 00:27:14.767
argument for what a

00:27:14.807 --> 00:27:15.667
graphics card should be.

00:27:15.867 --> 00:27:16.669
It's like one hundred ninety

00:27:17.269 --> 00:27:19.111
CPUs on PCI bus.

00:27:20.542 --> 00:27:21.083
My team wouldn't mind

00:27:21.143 --> 00:27:22.242
Bitcoin to test it out.

00:27:22.903 --> 00:27:23.703
So there were,

00:27:23.824 --> 00:27:25.003
there was basically like a

00:27:25.044 --> 00:27:28.184
data center of ZN fives in mineral oil,

00:27:28.845 --> 00:27:28.904
um,

00:27:28.924 --> 00:27:31.165
to cool them mining Bitcoin to see

00:27:31.226 --> 00:27:32.385
like failure modes.

00:27:33.326 --> 00:27:35.487
They're like, yeah, yeah, really.

00:27:35.946 --> 00:27:36.747
They, um,

00:27:38.127 --> 00:27:38.928
I think this was like my

00:27:38.968 --> 00:27:41.308
manager's pet project to

00:27:41.348 --> 00:27:42.209
mine Bitcoin with it.

00:27:42.808 --> 00:27:45.950
And so I had to like sneak

00:27:45.970 --> 00:27:47.750
around to find out how, how it happened.

00:27:47.871 --> 00:27:49.351
And he was like, yeah, we're doing that.

00:27:49.809 --> 00:27:50.730
Just don't tell anyone.

00:27:51.951 --> 00:27:53.413
Um, but yeah,

00:27:53.452 --> 00:27:54.393
so he used to mine Bitcoin

00:27:54.432 --> 00:27:56.454
with like a thousand C on five cards,

00:27:56.755 --> 00:27:57.635
which in I think probably

00:27:57.675 --> 00:27:58.957
would have been pretty decent.

00:27:58.977 --> 00:27:59.896
I don't know if they had a

00:27:59.916 --> 00:28:00.817
six back then for it.

00:28:01.959 --> 00:28:03.519
So where is all the Bitcoin now?

00:28:04.380 --> 00:28:05.500
Where is the Bitcoin?

00:28:05.980 --> 00:28:06.441
Great question.

00:28:06.601 --> 00:28:07.060
I have no idea.

00:28:07.422 --> 00:28:08.962
I never like followed up too far with it.

00:28:09.042 --> 00:28:09.682
I just thought it was funny

00:28:09.823 --> 00:28:11.284
that somebody on that team

00:28:11.304 --> 00:28:13.765
is like on a fucking beach.

00:28:13.825 --> 00:28:14.905
He's not on a beach, man.

00:28:14.945 --> 00:28:16.987
He's like in a Utah dump

00:28:17.047 --> 00:28:18.347
fucking hunting around for

00:28:18.367 --> 00:28:20.769
that USB stick or that.

00:28:20.909 --> 00:28:21.249
Yeah.

00:28:21.269 --> 00:28:22.170
Funnel it away into some

00:28:22.210 --> 00:28:23.830
wallet stuck on the USB stick.

00:28:24.250 --> 00:28:25.711
I know it's here somewhere, man.

00:28:25.771 --> 00:28:26.491
I'm going to spend the rest

00:28:26.531 --> 00:28:27.633
of my life looking for it.

00:28:28.496 --> 00:28:31.636
Well, my manager was a prepper too.

00:28:31.777 --> 00:28:32.917
So his vehicle,

00:28:32.938 --> 00:28:33.978
he'd take him to work every day,

00:28:34.298 --> 00:28:36.439
had a huge ham radio on the side.

00:28:36.459 --> 00:28:37.239
And he'd always be talking

00:28:37.259 --> 00:28:40.520
about the way he's

00:28:40.560 --> 00:28:41.701
improving his cabin for

00:28:41.740 --> 00:28:42.740
whenever the big one comes.

00:28:42.840 --> 00:28:44.721
The big one being the

00:28:44.801 --> 00:28:46.563
Cascadia subduction fault,

00:28:46.682 --> 00:28:47.923
I think it's called in Oregon,

00:28:47.962 --> 00:28:49.344
where there's supposed to

00:28:49.364 --> 00:28:49.884
be an earthquake,

00:28:49.903 --> 00:28:51.305
kind of like the San Andreas fault,

00:28:51.484 --> 00:28:52.664
except Oregon's basically

00:28:52.684 --> 00:28:53.566
just supposed to fall off

00:28:53.586 --> 00:28:54.885
the face of the earth effectively.

00:28:55.365 --> 00:28:56.166
And so Oregon has a lot of

00:28:56.207 --> 00:28:56.866
preppers for that.

00:28:57.426 --> 00:28:58.567
So he would talk about that a lot.

00:29:00.588 --> 00:29:01.808
Added another three feet of

00:29:01.888 --> 00:29:03.049
concrete to my bunker.

00:29:04.570 --> 00:29:05.191
Yeah, exactly.

00:29:05.230 --> 00:29:06.352
That kind of thing.

00:29:06.672 --> 00:29:07.412
On the weekend.

00:29:07.571 --> 00:29:09.313
Turn that Bitcoin up into concrete.

00:29:10.292 --> 00:29:10.834
Well,

00:29:10.973 --> 00:29:12.634
he would go up on the roof of Intel

00:29:12.654 --> 00:29:14.915
and put satellite dishes up

00:29:14.935 --> 00:29:15.935
there so that he could

00:29:15.976 --> 00:29:17.916
bounce it off of Intel to

00:29:17.957 --> 00:29:19.198
like talk to anyone in

00:29:22.078 --> 00:29:22.980
basically the Portland area.

00:29:23.140 --> 00:29:24.319
Radio antennas, not satellites,

00:29:24.339 --> 00:29:24.861
radio antennas.

00:29:24.881 --> 00:29:25.320
Yeah.

00:29:28.290 --> 00:29:32.653
Do you watch that British dude on YouTube?

00:29:34.073 --> 00:29:38.815
He's digging tunnels under

00:29:38.855 --> 00:29:40.776
his house and shit.

00:29:40.816 --> 00:29:41.516
Colin Firth.

00:29:41.635 --> 00:29:42.435
I like that dude.

00:29:44.557 --> 00:29:45.057
Fuck, man.

00:29:45.498 --> 00:29:46.498
If you want to lose a day,

00:29:46.538 --> 00:29:47.557
just go back and watch all

00:29:47.577 --> 00:29:49.598
his tunnel videos.

00:29:49.638 --> 00:29:51.079
He's building that car lift

00:29:51.099 --> 00:29:51.680
or whatever right now.

00:29:52.462 --> 00:29:53.623
yeah he started off with a

00:29:53.702 --> 00:29:55.223
bunker like in his backyard

00:29:55.263 --> 00:29:56.903
he just dug a big hole and

00:29:56.943 --> 00:29:58.285
put a bunker in there and

00:29:58.345 --> 00:29:59.805
covered it in concrete yeah

00:30:00.125 --> 00:30:01.085
make some noise underground

00:30:01.125 --> 00:30:02.865
all that kind of yeah so he

00:30:02.885 --> 00:30:04.526
would like go into his

00:30:04.566 --> 00:30:05.606
garden shed and then just

00:30:05.646 --> 00:30:06.686
like open a hatch and go

00:30:06.707 --> 00:30:08.886
down into the the man cave

00:30:08.926 --> 00:30:10.188
he had there then he just

00:30:10.228 --> 00:30:12.347
like started building his

00:30:12.387 --> 00:30:14.969
tunnels under his under the

00:30:14.989 --> 00:30:16.569
ground uh to go up to his

00:30:16.609 --> 00:30:18.170
house so it comes up in

00:30:18.190 --> 00:30:18.950
like a cupboard in his

00:30:19.009 --> 00:30:20.891
house in his house and then

00:30:20.911 --> 00:30:21.770
he's like oh well

00:30:22.287 --> 00:30:24.128
now like make another tunnel

00:30:24.148 --> 00:30:25.930
that goes out the front and

00:30:25.950 --> 00:30:27.172
he's just excavated this

00:30:27.251 --> 00:30:28.532
massive fucking hole out

00:30:28.553 --> 00:30:29.594
the front of his house and

00:30:29.653 --> 00:30:30.515
filled it with like

00:30:31.075 --> 00:30:33.837
concrete and steel and so

00:30:33.857 --> 00:30:35.358
he's got his big cavity out

00:30:35.378 --> 00:30:36.259
the front underneath his

00:30:36.279 --> 00:30:38.000
driveway and he's making

00:30:38.561 --> 00:30:40.804
like a lift a car lift so

00:30:40.923 --> 00:30:42.285
uh the roof will slide back

00:30:42.305 --> 00:30:43.987
and his car will come out of the driveway

00:30:45.171 --> 00:30:46.510
he wanted to put like he

00:30:46.530 --> 00:30:47.311
wanted to put a round table

00:30:47.352 --> 00:30:48.291
down there where like he'd

00:30:48.332 --> 00:30:49.071
pull in and then like it

00:30:49.092 --> 00:30:49.873
would like yeah like a

00:30:49.893 --> 00:30:50.593
rotisserie yeah I don't

00:30:50.712 --> 00:30:51.512
think it's got a room but

00:30:51.893 --> 00:30:55.953
yeah it's pretty hilarious

00:30:56.914 --> 00:30:58.335
it's it's definitely like

00:31:00.076 --> 00:31:01.756
youtube has just given like

00:31:01.955 --> 00:31:03.477
people with crazy ideas

00:31:03.517 --> 00:31:05.017
just the leverage to do

00:31:05.037 --> 00:31:06.298
whatever the they want dude

00:31:06.317 --> 00:31:07.337
how does that guy have that much energy

00:31:09.289 --> 00:31:09.789
I don't know, man.

00:31:09.809 --> 00:31:11.030
He's not a young man anymore.

00:31:11.852 --> 00:31:12.311
But the other thing,

00:31:12.652 --> 00:31:13.813
that pole that was on a

00:31:13.973 --> 00:31:14.953
concrete thing where he

00:31:14.993 --> 00:31:16.256
gets on and he swings all the way down.

00:31:16.276 --> 00:31:17.916
Yeah.

00:31:18.076 --> 00:31:19.458
The zero gravity fucking

00:31:19.538 --> 00:31:20.338
thing that he made where

00:31:20.358 --> 00:31:21.460
you just run around in circles.

00:31:21.480 --> 00:31:21.859
That's right.

00:31:21.880 --> 00:31:22.059
I know.

00:31:22.079 --> 00:31:24.923
I'm always amazed how much

00:31:24.962 --> 00:31:25.624
energy that guy has.

00:31:25.644 --> 00:31:27.605
This massive fucking barn.

00:31:29.507 --> 00:31:30.407
You know,

00:31:30.428 --> 00:31:31.588
there's this other dude that I

00:31:31.608 --> 00:31:32.869
just cannot stop watching.

00:31:33.089 --> 00:31:33.490
He's a...

00:31:34.598 --> 00:31:35.640
I can't remember what his name is,

00:31:35.680 --> 00:31:37.643
but the YouTube channel is Outdoor Boys.

00:31:37.823 --> 00:31:39.545
It's just this guy in fucking Alaska.

00:31:39.565 --> 00:31:40.306
Oh, yeah.

00:31:40.465 --> 00:31:42.469
And he's got sixty three

00:31:42.528 --> 00:31:44.250
million subscribers.

00:31:44.590 --> 00:31:45.673
Like, it's insane.

00:31:48.015 --> 00:31:49.576
He must be making a shitload

00:31:49.616 --> 00:31:50.719
of money out of YouTube.

00:31:51.787 --> 00:31:52.067
Right.

00:31:52.228 --> 00:31:53.548
But he just lives in like a

00:31:53.608 --> 00:31:55.250
regular ass house in Alaska.

00:31:55.670 --> 00:31:56.790
You can tell he's making

00:31:56.810 --> 00:31:58.373
bank because of his camping

00:31:58.413 --> 00:32:01.234
equipment is always like good shit.

00:32:01.516 --> 00:32:04.198
He's the one that'll like dig a like, yeah,

00:32:04.218 --> 00:32:05.439
dig a fucking hole into like,

00:32:05.459 --> 00:32:06.039
and then like, yeah,

00:32:06.059 --> 00:32:07.059
like build a fire down

00:32:07.079 --> 00:32:07.861
there and like he'll build

00:32:07.881 --> 00:32:09.221
a bed in there and all that kind of shit.

00:32:09.241 --> 00:32:09.382
Yeah.

00:32:09.402 --> 00:32:10.083
Yeah.

00:32:10.143 --> 00:32:10.583
It's just like,

00:32:10.603 --> 00:32:11.624
I'm going to go camping in

00:32:11.663 --> 00:32:12.865
the woods for three days

00:32:12.904 --> 00:32:13.766
and build a bunker.

00:32:13.806 --> 00:32:14.346
Yeah.

00:32:15.603 --> 00:32:17.364
yeah and but it's it's so

00:32:17.423 --> 00:32:18.223
interesting man he's just

00:32:18.284 --> 00:32:19.005
like yeah I'm just gonna

00:32:19.045 --> 00:32:19.984
dig this out and he's like

00:32:20.265 --> 00:32:21.246
I've just spent four hours

00:32:21.286 --> 00:32:22.306
digging out four hundred

00:32:22.346 --> 00:32:23.807
cubic meters I know the

00:32:23.846 --> 00:32:25.027
patience and uh fucking

00:32:25.067 --> 00:32:27.048
patience yeah he's just

00:32:27.067 --> 00:32:28.388
like he's like I gotta heat

00:32:28.409 --> 00:32:29.368
up the ground you know just

00:32:29.390 --> 00:32:30.809
go and chop down like forty

00:32:30.869 --> 00:32:35.972
fucking trees this is a

00:32:36.012 --> 00:32:36.952
hatchet I've got from my

00:32:37.012 --> 00:32:39.894
time in japan crazy fucking

00:32:40.154 --> 00:32:41.055
yakuza looking thing

00:32:43.413 --> 00:32:43.593
Yeah.

00:32:44.094 --> 00:32:44.334
Anyway,

00:32:44.713 --> 00:32:46.174
the point is I really enjoy those videos.

00:32:46.194 --> 00:32:47.375
I only discovered that dude

00:32:47.415 --> 00:32:48.276
like just the other day.

00:32:48.916 --> 00:32:49.257
Colin.

00:32:50.317 --> 00:32:51.038
Yeah.

00:32:51.377 --> 00:32:52.558
Now it's like my bedtime

00:32:52.798 --> 00:32:53.538
video every night.

00:32:53.700 --> 00:32:54.680
I watch one of his crazy

00:32:54.700 --> 00:32:55.881
shit because they're good length too.

00:32:55.921 --> 00:32:56.780
It's like twenty minutes.

00:32:57.061 --> 00:32:57.961
Yeah.

00:32:57.981 --> 00:32:58.923
He's a good family man.

00:32:58.942 --> 00:33:00.324
He like gets the kids out there.

00:33:00.743 --> 00:33:02.265
Makes toboggan sleds and shit.

00:33:02.644 --> 00:33:03.305
Are you all caught up on

00:33:03.325 --> 00:33:05.207
Drain Addict or what?

00:33:05.247 --> 00:33:06.846
Fuck, I do not watch Drain Addict, man.

00:33:06.867 --> 00:33:08.087
I don't know how the fuck you watch that.

00:33:08.107 --> 00:33:09.909
It looks so boring.

00:33:12.030 --> 00:33:12.611
He's a good dude.

00:33:13.711 --> 00:33:14.873
I'm sure he's a great guy.

00:33:14.932 --> 00:33:16.453
I'd love to have a chat to him at the pub.

00:33:16.534 --> 00:33:17.275
The other one to watch at

00:33:17.315 --> 00:33:19.116
night is wrist watch revival.

00:33:20.976 --> 00:33:22.277
with marshall guy's got

00:33:22.436 --> 00:33:25.118
total like calm voice he

00:33:25.159 --> 00:33:26.599
takes he basically tears

00:33:26.640 --> 00:33:28.080
down like older omega and

00:33:28.121 --> 00:33:29.182
rolex and all the types of

00:33:29.201 --> 00:33:29.961
watches from the fifties

00:33:30.001 --> 00:33:30.883
sixties seventies with like

00:33:30.923 --> 00:33:32.243
stories to them little

00:33:32.263 --> 00:33:33.285
voiceover takes everything

00:33:33.305 --> 00:33:34.566
down cleans it all up gets

00:33:34.605 --> 00:33:36.386
it working repot like and

00:33:36.406 --> 00:33:37.928
polishes it makes it

00:33:37.968 --> 00:33:39.249
beautiful totally you're

00:33:39.729 --> 00:33:41.089
twenty fifteen minutes out

00:33:41.230 --> 00:33:42.391
you're done it's all over

00:33:42.451 --> 00:33:44.051
so like it's like he's got

00:33:44.071 --> 00:33:44.992
like a bob ross type of

00:33:45.032 --> 00:33:46.074
voice to him just kind of like

00:33:47.755 --> 00:33:48.895
Oh, nice and calming.

00:33:49.016 --> 00:33:50.217
Yeah, just like calming.

00:33:50.356 --> 00:33:52.739
We're just going to take this apart.

00:33:53.839 --> 00:33:55.020
Have you seen any videos

00:33:55.060 --> 00:33:56.561
from JohnnyQNinety?

00:33:57.242 --> 00:33:57.423
No.

00:33:58.183 --> 00:34:01.445
He does like model engines

00:34:02.586 --> 00:34:04.008
and he doesn't talk at all.

00:34:04.028 --> 00:34:05.229
Oh, really?

00:34:05.249 --> 00:34:06.750
It's just hands.

00:34:07.691 --> 00:34:08.072
Yeah.

00:34:08.251 --> 00:34:09.913
And he like just machines

00:34:10.172 --> 00:34:10.954
all of this stuff.

00:34:11.414 --> 00:34:12.135
He's some...

00:34:13.282 --> 00:34:14.204
He has these projects where

00:34:14.224 --> 00:34:15.824
he just machines entire motors,

00:34:16.505 --> 00:34:18.666
like piece by piece by piece by piece,

00:34:18.686 --> 00:34:20.128
and he just fucking records all of it.

00:34:21.489 --> 00:34:22.110
You watch like a

00:34:22.469 --> 00:34:23.490
three-hour-long fucking

00:34:23.510 --> 00:34:25.353
video of a guy making a motor.

00:34:27.393 --> 00:34:28.655
But yeah, I don't know.

00:34:28.695 --> 00:34:29.735
He must have a thousand

00:34:29.775 --> 00:34:30.757
model engines by now.

00:34:32.018 --> 00:34:32.898
If you like that type of stuff,

00:34:32.938 --> 00:34:35.981
you should also watch RC Test Flight.

00:34:36.021 --> 00:34:37.242
RC Test Flight for planes?

00:34:37.262 --> 00:34:37.762
RC Test Flight.

00:34:37.802 --> 00:34:38.742
He's in Seattle.

00:34:38.983 --> 00:34:40.563
He builds and does a ton...

00:34:41.442 --> 00:34:42.342
that guy's fucking awesome.

00:34:42.762 --> 00:34:44.923
Like great engineer builds

00:34:44.943 --> 00:34:48.125
like a ton of planes, hydrofoils,

00:34:49.144 --> 00:34:50.465
propeller design type stuff,

00:34:50.505 --> 00:34:51.586
like heavily engineering,

00:34:51.646 --> 00:34:53.467
but like can build anything.

00:34:53.666 --> 00:34:54.907
Number one, like three D Prince,

00:34:54.927 --> 00:34:56.648
a ton of shit does a ton of modeling,

00:34:56.748 --> 00:34:59.090
like re like really strong, smart dude.

00:34:59.730 --> 00:35:01.831
Like he does like a bunch of

00:35:01.851 --> 00:35:02.911
autonomous stuff and things like that.

00:35:02.931 --> 00:35:03.371
You'd like it.

00:35:03.552 --> 00:35:06.112
It's, it's pretty fun guys.

00:35:06.913 --> 00:35:09.034
Crazy, like really, really,

00:35:09.074 --> 00:35:09.815
really intelligent.

00:35:09.835 --> 00:35:10.494
It's like fun to watch.

00:35:11.675 --> 00:35:12.836
What's your go-to, Schultz?

00:35:15.778 --> 00:35:16.639
Learn Linux TV?

00:35:21.643 --> 00:35:23.184
I don't really have a go-to right now.

00:35:23.945 --> 00:35:24.485
I used to.

00:35:24.925 --> 00:35:27.327
Honestly, with kiddo,

00:35:27.347 --> 00:35:30.090
I haven't had time to really enjoy.

00:35:30.451 --> 00:35:31.150
I think you'd be watching

00:35:31.170 --> 00:35:32.552
YouTube all the time in those situations.

00:35:33.072 --> 00:35:33.592
Yeah, man.

00:35:33.612 --> 00:35:35.074
I'd be watching that shit.

00:35:35.155 --> 00:35:36.436
I'd be watching that shit.

00:35:37.505 --> 00:35:38.565
I have the morning shift.

00:35:38.666 --> 00:35:39.606
And when you're watching the kid,

00:35:39.646 --> 00:35:40.947
you can't really do anything else.

00:35:40.987 --> 00:35:45.447
So I just like put on YouTube or Plex.

00:35:45.487 --> 00:35:45.688
Fair.

00:35:45.708 --> 00:35:47.108
I mean, yeah, I should.

00:35:52.329 --> 00:35:52.730
No, I don't know.

00:35:52.750 --> 00:35:52.969
I used to.

00:35:52.989 --> 00:35:53.989
He's so noise sensitive right now.

00:35:54.010 --> 00:35:54.670
Stare at the wall?

00:35:54.710 --> 00:35:55.090
Stare at the wall.

00:35:55.110 --> 00:35:56.791
Stare at the wall, pretty much.

00:35:57.911 --> 00:35:59.132
It really depends on what

00:35:59.291 --> 00:36:00.492
his mood is at the time.

00:36:00.811 --> 00:36:02.773
Otherwise, I'll play games, watch TV.

00:36:02.853 --> 00:36:03.012
Yeah.

00:36:04.471 --> 00:36:05.311
much movies,

00:36:05.331 --> 00:36:06.010
but it's really depends on

00:36:06.030 --> 00:36:07.311
like how he's sleeping.

00:36:08.032 --> 00:36:08.291
Lately,

00:36:08.351 --> 00:36:10.672
I've been I've got a big old yoga ball.

00:36:11.311 --> 00:36:12.873
And I'll bounce him while I

00:36:12.913 --> 00:36:14.032
do other things because he

00:36:14.052 --> 00:36:15.672
can't like get woken up

00:36:15.793 --> 00:36:17.153
when he's on the yoga ball being bounced.

00:36:17.594 --> 00:36:18.273
So I'll just sit on the yoga

00:36:18.293 --> 00:36:19.594
ball for like six hours in

00:36:19.614 --> 00:36:20.873
the morning bouncing him so

00:36:20.893 --> 00:36:21.695
I can basically do whatever

00:36:21.715 --> 00:36:23.514
I want so long as I'm on set yoga ball.

00:36:24.155 --> 00:36:26.074
What is he like in a chest

00:36:26.114 --> 00:36:28.076
thing or something?

00:36:28.135 --> 00:36:29.795
Nope, he is on a pillow in my lap.

00:36:30.516 --> 00:36:30.856
Oh, really?

00:36:31.056 --> 00:36:31.456
Okay.

00:36:31.476 --> 00:36:32.157
So he's just like bouncing,

00:36:32.177 --> 00:36:32.777
you just kind of hold on to

00:36:32.797 --> 00:36:33.436
him and just like whatever.

00:36:36.563 --> 00:36:38.485
yeah it worked how many um

00:36:39.385 --> 00:36:40.907
how many months ahead of us

00:36:40.927 --> 00:36:42.387
were you you're like four

00:36:42.407 --> 00:36:44.989
weeks or six weeks or um I

00:36:45.170 --> 00:36:46.070
don't know he just turned

00:36:46.090 --> 00:36:48.413
four months last week okay

00:36:48.432 --> 00:36:49.414
so yeah about a about a

00:36:49.494 --> 00:36:54.097
month is he um like is he

00:36:54.137 --> 00:36:55.780
sit up and stuff yet or

00:36:55.800 --> 00:36:58.222
yeah yep he's sitting yeah

00:36:59.385 --> 00:37:00.226
He started to be able to do

00:37:00.246 --> 00:37:01.387
like squats kind of things.

00:37:01.527 --> 00:37:02.547
He can't crawl or anything yet,

00:37:02.626 --> 00:37:04.628
but he does squat.

00:37:05.027 --> 00:37:07.909
Ass up in the air.

00:37:07.949 --> 00:37:08.248
Yeah.

00:37:08.268 --> 00:37:14.070
Like, dude, you're upside down.

00:37:15.371 --> 00:37:17.052
He's been especially spit up lately.

00:37:17.112 --> 00:37:19.532
And so he did that yesterday.

00:37:19.652 --> 00:37:20.512
Ass went up and they just

00:37:20.592 --> 00:37:22.914
fucking vomited so much.

00:37:22.974 --> 00:37:24.614
It was like at least three ounces.

00:37:24.634 --> 00:37:26.094
I was like, really?

00:37:26.594 --> 00:37:27.235
All over me.

00:37:28.900 --> 00:37:32.943
Our dude has, like, no reaction when he,

00:37:33.242 --> 00:37:33.943
like, vomits.

00:37:35.164 --> 00:37:36.565
He'll just be sitting in his, like,

00:37:36.606 --> 00:37:39.588
chair or something, like, in the pram,

00:37:39.708 --> 00:37:44.030
and then he'll just... He wouldn't even,

00:37:44.050 --> 00:37:44.931
like, open his mouth.

00:37:44.972 --> 00:37:47.974
He'll just, like, just come out, like...

00:37:49.733 --> 00:37:50.833
And just fucking everywhere.

00:37:50.853 --> 00:37:51.514
It's like a leader.

00:37:51.634 --> 00:37:53.054
And you're like, fucking hell, man.

00:37:53.215 --> 00:37:53.934
That's funny.

00:37:54.356 --> 00:37:54.496
Yeah.

00:37:54.516 --> 00:37:56.036
And he's like, I'm ready.

00:37:56.076 --> 00:37:59.177
I'm stoked.

00:37:59.197 --> 00:37:59.617
Super happy.

00:37:59.637 --> 00:38:00.478
I'm hungry now.

00:38:01.298 --> 00:38:01.699
Asshole.

00:38:02.159 --> 00:38:02.460
Feed me.

00:38:02.500 --> 00:38:02.579
Yeah.

00:38:05.181 --> 00:38:07.181
And he's storing up those curds everywhere,

00:38:07.222 --> 00:38:09.264
like under the fat rolls under his chin.

00:38:10.903 --> 00:38:12.025
Just milk curds.

00:38:12.045 --> 00:38:12.105
Yep.

00:38:15.646 --> 00:38:16.768
Oh, man.

00:38:16.847 --> 00:38:17.887
Yeah, they're pretty entertaining.

00:38:18.108 --> 00:38:19.188
You can kind of just look at them.

00:38:21.280 --> 00:38:22.481
Lifting their ass in the air.

00:38:24.282 --> 00:38:24.461
Chilling.

00:38:24.481 --> 00:38:25.742
That's it.

00:38:25.782 --> 00:38:27.264
So do we have, like,

00:38:27.304 --> 00:38:28.344
what's on the agenda for

00:38:28.364 --> 00:38:29.965
the next couple of weeks?

00:38:30.326 --> 00:38:34.367
There's more networks going, yeah.

00:38:34.487 --> 00:38:35.668
There's things in the works.

00:38:38.311 --> 00:38:38.630
Yeah?

00:38:38.731 --> 00:38:38.811
Yeah.

00:38:38.851 --> 00:38:39.251
Well, I mean,

00:38:39.331 --> 00:38:41.472
you guys would have... You

00:38:41.512 --> 00:38:42.833
guys would be well into that.

00:38:42.853 --> 00:38:44.554
I mean,

00:38:44.574 --> 00:38:46.034
there's ones that we're waiting on.

00:38:48.077 --> 00:38:48.436
Um...

00:38:49.400 --> 00:38:50.701
Like, there's a fair few on my list.

00:38:50.721 --> 00:38:51.202
There's, like,

00:38:52.083 --> 00:38:53.603
Warden's ongoing at the moment.

00:38:53.784 --> 00:38:54.425
Aztec.

00:38:55.144 --> 00:38:56.286
Still waiting for Particle

00:38:56.547 --> 00:38:57.106
to do something.

00:38:57.186 --> 00:38:58.268
Nillian's ongoing.

00:38:59.789 --> 00:39:00.369
Maverick.

00:39:02.032 --> 00:39:03.532
Monad, if anyone can get onto him.

00:39:05.295 --> 00:39:06.516
There's a bunch of, like,

00:39:07.516 --> 00:39:09.838
the DVT stuff happening, too.

00:39:10.827 --> 00:39:12.809
so uh I think we just got

00:39:12.849 --> 00:39:17.331
onto mainnet on um obol uh

00:39:17.391 --> 00:39:19.532
lido obol and I think ssv

00:39:19.632 --> 00:39:20.733
is just around the corner

00:39:20.813 --> 00:39:21.653
schiltzer you're already on

00:39:21.954 --> 00:39:23.655
ssv right did you guys do

00:39:23.675 --> 00:39:24.916
the obol testnet are you

00:39:25.076 --> 00:39:26.036
are you live with obol as

00:39:26.056 --> 00:39:28.637
well or just ssv uh we're

00:39:28.657 --> 00:39:30.338
on ssb and we are in two

00:39:30.418 --> 00:39:32.860
oval clusters you're in two

00:39:33.061 --> 00:39:36.702
okay uh our first go around

00:39:36.742 --> 00:39:37.523
at the moment we're just

00:39:37.563 --> 00:39:39.664
getting those live now um

00:39:40.353 --> 00:39:41.273
That's all looking pretty good.

00:39:41.594 --> 00:39:43.974
Runs well out of Australia too.

00:39:44.195 --> 00:39:46.077
Nice long block times on Ethereum.

00:39:46.217 --> 00:39:47.577
Yeah, you got plenty of time.

00:39:47.597 --> 00:39:48.338
Yeah, you can run that.

00:39:48.777 --> 00:39:49.057
You know,

00:39:50.298 --> 00:39:53.820
we were using our Ethereum

00:39:53.860 --> 00:39:55.202
cluster in Japan,

00:39:55.302 --> 00:39:56.762
but ended up making it local.

00:39:56.842 --> 00:40:00.244
It was just a little bit too much latency.

00:40:00.545 --> 00:40:04.148
Didn't look good on the stats.

00:40:04.168 --> 00:40:05.047
I think it worked fine.

00:40:05.208 --> 00:40:06.548
Like it tested just fine,

00:40:06.588 --> 00:40:08.309
but it's like two hundred

00:40:08.349 --> 00:40:09.130
milliseconds of...

00:40:11.027 --> 00:40:12.786
latency is there another

00:40:12.827 --> 00:40:16.007
round trip testnet coming

00:40:16.027 --> 00:40:16.927
not sure if there's another

00:40:17.007 --> 00:40:20.369
one um at the moment so you

00:40:20.409 --> 00:40:21.688
know they're doing the ssv

00:40:21.728 --> 00:40:24.309
right now yeah yeah uh well

00:40:24.329 --> 00:40:25.690
actually there's did they

00:40:25.710 --> 00:40:26.909
just wrap that up we just

00:40:26.929 --> 00:40:27.630
wrapped that up right

00:40:28.230 --> 00:40:29.070
excuse me yeah we just

00:40:29.090 --> 00:40:30.150
wrapped it up uh this week

00:40:30.291 --> 00:40:30.871
actually we just shut

00:40:30.891 --> 00:40:31.550
everything down well I

00:40:31.570 --> 00:40:31.971
actually didn't shut

00:40:31.990 --> 00:40:32.731
anything down but we just

00:40:32.911 --> 00:40:34.911
um just exit all and

00:40:34.952 --> 00:40:35.992
removed all the validators

00:40:36.291 --> 00:40:37.331
just a couple days ago

00:40:38.702 --> 00:40:39.402
Yeah, I don't know.

00:40:40.023 --> 00:40:41.563
I guess I guess we should be

00:40:41.583 --> 00:40:42.965
able to shut that down soon, though.

00:40:43.304 --> 00:40:44.804
Yeah, we can now.

00:40:44.844 --> 00:40:45.505
Now they're removed.

00:40:45.626 --> 00:40:46.425
I haven't done it yet.

00:40:46.465 --> 00:40:47.326
I don't even.

00:40:47.385 --> 00:40:48.507
It's not a big deal.

00:40:48.606 --> 00:40:50.228
Yeah, I haven't done it either,

00:40:50.268 --> 00:40:51.427
but it's just a matter of

00:40:51.467 --> 00:40:52.288
pressing delete.

00:40:52.688 --> 00:40:54.268
Yeah, yeah.

00:40:54.369 --> 00:40:56.849
Yeah,

00:40:56.889 --> 00:40:59.231
so we'll see kind of what we haven't

00:40:59.391 --> 00:41:00.452
heard anything related to mainnet.

00:41:00.871 --> 00:41:03.152
Our cluster did pretty well, so I'm not.

00:41:03.313 --> 00:41:04.753
I don't think I think the

00:41:04.773 --> 00:41:06.173
bar for that is pretty low, right?

00:41:06.213 --> 00:41:06.614
Isn't it like?

00:41:07.255 --> 00:41:08.356
I think, like,

00:41:08.717 --> 00:41:10.538
it's if you don't royally fuck up,

00:41:10.577 --> 00:41:11.619
you're pretty good.

00:41:12.239 --> 00:41:12.378
Like,

00:41:12.418 --> 00:41:14.340
I think even the sign percentage is

00:41:14.380 --> 00:41:14.900
pretty low.

00:41:16.862 --> 00:41:17.742
We had a little bit of

00:41:17.802 --> 00:41:18.842
downtime there when we're

00:41:18.862 --> 00:41:19.963
moving some stuff around.

00:41:20.643 --> 00:41:21.423
Don't think anyone really

00:41:21.463 --> 00:41:22.244
said anything about it.

00:41:22.724 --> 00:41:24.146
Cluster performs as a whole, so.

00:41:25.289 --> 00:41:25.550
Yeah,

00:41:25.929 --> 00:41:27.851
I think a couple times we had the

00:41:28.512 --> 00:41:31.052
distinction of, what was it?

00:41:31.213 --> 00:41:34.155
It was called absolute top

00:41:35.036 --> 00:41:36.135
in terms of network

00:41:36.155 --> 00:41:37.456
performance for our cluster,

00:41:37.476 --> 00:41:38.396
which was actually pretty cool.

00:41:38.416 --> 00:41:40.378
I don't know what that means.

00:41:40.518 --> 00:41:40.838
Oh, yeah?

00:41:40.858 --> 00:41:40.938
Yeah,

00:41:40.978 --> 00:41:42.340
which means there's no way with

00:41:42.380 --> 00:41:46.161
better uptime, better signing performance,

00:41:46.242 --> 00:41:47.202
better something or other.

00:41:47.222 --> 00:41:47.943
I have no idea.

00:41:48.963 --> 00:41:50.344
But yeah, we had that a couple times,

00:41:50.483 --> 00:41:51.184
which I didn't even realize,

00:41:51.204 --> 00:41:52.144
but there's a website you

00:41:52.164 --> 00:41:52.766
can track that shit.

00:41:53.626 --> 00:41:56.288
Actually, everybody did a pretty good job.

00:41:56.487 --> 00:41:57.188
Everybody had uptime,

00:41:57.228 --> 00:41:58.148
and there's little things

00:41:58.168 --> 00:41:58.809
down here and there,

00:41:58.869 --> 00:42:00.090
but it doesn't matter.

00:42:01.030 --> 00:42:03.992
That's cool.

00:42:04.012 --> 00:42:06.554
Initia, is there any timeline on that?

00:42:09.697 --> 00:42:10.556
I'm not in Initia.

00:42:10.617 --> 00:42:11.398
I thought it was live

00:42:11.418 --> 00:42:13.039
already since ages ago.

00:42:14.420 --> 00:42:15.280
You're not in Initia, really?

00:42:15.860 --> 00:42:16.722
I thought you were.

00:42:16.862 --> 00:42:17.222
No, I couldn't...

00:42:19.335 --> 00:42:21.016
When they started that test net,

00:42:21.056 --> 00:42:23.038
it seemed to start like overnight.

00:42:23.639 --> 00:42:25.360
Like no one was talking about it.

00:42:25.420 --> 00:42:26.561
And then I woke up the next

00:42:26.641 --> 00:42:27.822
morning and they're like, oh,

00:42:27.902 --> 00:42:29.023
everyone's missing on an issue.

00:42:29.043 --> 00:42:29.244
I'm like,

00:42:29.264 --> 00:42:31.106
what the fuck are you talking about?

00:42:31.126 --> 00:42:33.788
What the fuck is this network?

00:42:34.289 --> 00:42:36.871
You got that.

00:42:36.951 --> 00:42:38.393
It was like discovered and

00:42:38.472 --> 00:42:40.835
joined while I was like asleep.

00:42:41.355 --> 00:42:43.117
Much like Aptos.

00:42:43.376 --> 00:42:44.358
That sounds like a UTC plus

00:42:44.378 --> 00:42:45.119
twelve issue right there.

00:42:45.835 --> 00:42:46.217
Yeah.

00:42:46.677 --> 00:42:47.079
Ten.

00:42:47.559 --> 00:42:47.900
Ten.

00:42:48.101 --> 00:42:49.083
ETC plus ten.

00:42:51.443 --> 00:42:52.362
yeah man it's amazing how

00:42:52.382 --> 00:42:53.503
many times that's happened

00:42:53.543 --> 00:42:54.385
where something is just

00:42:54.445 --> 00:42:55.706
materialized while I was

00:42:55.726 --> 00:42:58.186
sleeping right no I know I

00:42:58.206 --> 00:42:59.628
know well now at least I

00:42:59.648 --> 00:43:01.969
know like I mean I don't I

00:43:01.989 --> 00:43:02.550
don't think anything's come

00:43:02.590 --> 00:43:03.331
up where I have done that

00:43:03.371 --> 00:43:04.092
but at least I know if I

00:43:04.132 --> 00:43:04.992
hit you on signal like I

00:43:05.393 --> 00:43:06.333
can at least get you up if

00:43:06.413 --> 00:43:07.414
it's worthwhile you know

00:43:07.434 --> 00:43:08.695
what I mean yeah you are

00:43:08.755 --> 00:43:11.657
the only person who is uh

00:43:11.677 --> 00:43:13.838
like whitelisted to make my

00:43:13.878 --> 00:43:15.079
phone ring while I'm asleep

00:43:15.280 --> 00:43:15.980
except for there's

00:43:16.000 --> 00:43:16.641
something that's going on

00:43:16.701 --> 00:43:17.701
it would be worth that way

00:43:17.721 --> 00:43:19.802
I would do it but there hasn't been so

00:43:25.018 --> 00:43:25.059
No.

00:43:25.179 --> 00:43:26.963
Yeah, I'm white-listed on yours, right?

00:43:27.123 --> 00:43:27.565
I can't remember.

00:43:28.436 --> 00:43:30.338
I my signals actually yeah

00:43:30.458 --> 00:43:32.099
my signal is um I don't

00:43:32.119 --> 00:43:32.960
really get too many signals

00:43:33.300 --> 00:43:35.202
so I think for the most

00:43:35.242 --> 00:43:37.565
part it's all open because

00:43:37.885 --> 00:43:39.025
oh yeah but when like do

00:43:39.045 --> 00:43:41.608
you put your phone on um do

00:43:41.648 --> 00:43:42.389
not disturb when you're

00:43:42.409 --> 00:43:43.891
sleeping I do but yeah

00:43:43.911 --> 00:43:44.851
you're right actually you

00:43:45.072 --> 00:43:47.253
yeah that contact is listed

00:43:48.295 --> 00:43:49.255
yeah I think it's only you

00:43:49.295 --> 00:43:50.577
and my partner yeah it's

00:43:50.597 --> 00:43:52.498
the same way will she use signal

00:43:53.902 --> 00:43:56.507
No, but her number is whitelisted,

00:43:56.527 --> 00:43:57.510
so it doesn't matter the app.

00:43:57.570 --> 00:43:58.411
It'll work.

00:43:58.652 --> 00:43:59.112
Same as you.

00:43:59.132 --> 00:43:59.914
It doesn't matter if you

00:43:59.934 --> 00:44:01.137
call me or use Signal.

00:44:01.157 --> 00:44:01.818
It'll still come through.

00:44:01.838 --> 00:44:01.998
Oh, yeah.

00:44:02.018 --> 00:44:04.023
Then I guess I do have that then.

00:44:04.063 --> 00:44:04.302
Okay.

00:44:04.322 --> 00:44:04.563
That's cool.

00:44:04.583 --> 00:44:05.224
I didn't know that worked out.

00:44:06.606 --> 00:44:06.806
Yeah,

00:44:06.827 --> 00:44:08.768
it just doesn't work with Discord

00:44:08.789 --> 00:44:10.309
though because there's no

00:44:10.389 --> 00:44:12.811
number registered in there.

00:44:12.851 --> 00:44:17.936
But Signal, you go in as a regular contact,

00:44:18.016 --> 00:44:18.317
I guess,

00:44:18.396 --> 00:44:20.079
in Signal when you add someone to it.

00:44:21.139 --> 00:44:22.960
So yeah, that kind of works,

00:44:22.981 --> 00:44:23.762
but the other way doesn't.

00:44:25.864 --> 00:44:27.945
Autonity is getting close to

00:44:28.786 --> 00:44:29.487
mainnet launch.

00:44:30.146 --> 00:44:31.728
Yep.

00:44:31.809 --> 00:44:32.909
Are you in there too, Schultz?

00:44:33.851 --> 00:44:34.391
Yep, there he is.

00:44:36.137 --> 00:44:36.398
Yeah.

00:44:36.418 --> 00:44:37.858
Did you get up last night or

00:44:37.898 --> 00:44:38.759
did James do that?

00:44:40.340 --> 00:44:41.641
James did it.

00:44:41.681 --> 00:44:44.041
James did it.

00:44:44.081 --> 00:44:44.643
Nice.

00:44:44.663 --> 00:44:45.563
I'm glad they've actually

00:44:45.623 --> 00:44:49.686
done a few iterations of

00:44:49.706 --> 00:44:51.367
that testnet now because

00:44:52.608 --> 00:44:54.309
The whole process of getting

00:44:54.329 --> 00:44:56.329
that set up is very

00:44:56.369 --> 00:44:57.230
different to what we're

00:44:57.329 --> 00:44:58.349
used to on other things.

00:44:58.650 --> 00:45:00.630
And like the initial learning curve,

00:45:00.650 --> 00:45:01.391
when you're reading that

00:45:01.431 --> 00:45:02.652
documentation is like,

00:45:03.192 --> 00:45:06.713
what in the fuck is going on?

00:45:06.733 --> 00:45:07.574
I remember like,

00:45:08.552 --> 00:45:08.992
Shit, man.

00:45:09.414 --> 00:45:10.635
There's been no other

00:45:11.114 --> 00:45:12.356
network where I've had to

00:45:12.556 --> 00:45:14.657
ask so many questions.

00:45:14.697 --> 00:45:15.719
It's like, well, what is this?

00:45:15.798 --> 00:45:17.541
And why am I doing this other thing?

00:45:17.581 --> 00:45:19.523
And what's happening here?

00:45:19.583 --> 00:45:22.625
But now it sort of all just makes sense.

00:45:22.786 --> 00:45:24.586
So it's been a good exercise

00:45:24.626 --> 00:45:25.987
going through it a couple of times.

00:45:27.510 --> 00:45:29.070
I think they've given the

00:45:29.150 --> 00:45:31.532
option to either generate

00:45:31.612 --> 00:45:35.416
all new keys or reuse old ones for...

00:45:37.577 --> 00:45:38.818
relaunches of that network

00:45:39.199 --> 00:45:40.739
and uh I think every time

00:45:40.778 --> 00:45:43.260
we've like opted to

00:45:43.300 --> 00:45:44.599
generate new keys just to

00:45:44.639 --> 00:45:47.280
get the process down yeah

00:45:47.320 --> 00:45:50.001
but um also runs well out

00:45:50.061 --> 00:45:51.681
here and the big down under

00:45:51.722 --> 00:45:53.561
yeah like that chain runs

00:45:53.682 --> 00:45:56.443
well like it's uh it's very

00:45:56.503 --> 00:45:57.664
light like I had a look at

00:45:57.704 --> 00:45:59.164
the I beefed up that

00:45:59.184 --> 00:46:00.945
machine um and I looked at

00:46:00.985 --> 00:46:02.485
the resource usage this

00:46:02.545 --> 00:46:03.784
morning guaranteed there's

00:46:03.824 --> 00:46:05.945
probably not much action on it right now

00:46:06.831 --> 00:46:09.074
But, man, it'd run on a potato.

00:46:09.373 --> 00:46:11.815
It's not very hungry.

00:46:11.835 --> 00:46:12.536
It is Tendermint-based,

00:46:12.556 --> 00:46:15.358
but is the EL side also Tendermint?

00:46:15.418 --> 00:46:16.820
Or do they bake something else in there?

00:46:16.960 --> 00:46:19.402
Because the logs look like a

00:46:19.503 --> 00:46:20.864
RefGeth type of log,

00:46:21.824 --> 00:46:22.844
at least in terms of format

00:46:22.864 --> 00:46:23.626
and those types of things.

00:46:23.666 --> 00:46:24.646
There is Tendermint in there.

00:46:24.686 --> 00:46:25.367
I do know that.

00:46:26.188 --> 00:46:28.909
But I swear it's one binary running,

00:46:28.969 --> 00:46:30.231
so I'm not sure how that

00:46:30.371 --> 00:46:31.952
actually... It's not like...

00:46:32.847 --> 00:46:34.449
barra or you know initia or

00:46:34.469 --> 00:46:35.130
something else that has

00:46:35.170 --> 00:46:37.132
like an elcl structure yeah

00:46:37.192 --> 00:46:44.177
um I don't even know yeah I

00:46:44.237 --> 00:46:44.878
don't it's well it's all

00:46:44.998 --> 00:46:46.518
one binary and so it is all

00:46:46.579 --> 00:46:47.960
one binary it does but it

00:46:48.059 --> 00:46:50.121
appears really well it like

00:46:50.141 --> 00:46:51.583
it consumes blocks like

00:46:51.603 --> 00:46:52.664
crazy like during catch-up

00:46:52.684 --> 00:46:54.144
it does that great thing

00:46:54.164 --> 00:46:55.465
you know it'll do like two

00:46:55.505 --> 00:46:56.567
thousand blocks a second

00:46:56.706 --> 00:46:58.389
just to catch up um and

00:46:58.409 --> 00:46:59.409
blow through transactions

00:46:59.429 --> 00:47:00.269
like that stuff's really

00:47:00.329 --> 00:47:01.010
nice when it does that

00:47:02.083 --> 00:47:03.403
There's been a lot of like

00:47:04.623 --> 00:47:06.085
different implementations

00:47:06.125 --> 00:47:08.425
of that Cosmos SDK or, um,

00:47:08.485 --> 00:47:09.666
tend to make consensus.

00:47:10.947 --> 00:47:11.108
Yeah.

00:47:11.128 --> 00:47:11.827
Um, lately, man,

00:47:11.867 --> 00:47:14.969
this year has just been so many different,

00:47:15.309 --> 00:47:15.570
um,

00:47:16.510 --> 00:47:18.110
teams come on and just do their own

00:47:18.150 --> 00:47:18.731
thing with it.

00:47:18.992 --> 00:47:19.172
Uh,

00:47:21.248 --> 00:47:21.608
man,

00:47:21.628 --> 00:47:22.949
there's like a handful right now that

00:47:22.969 --> 00:47:23.710
we're sort of looking at

00:47:23.730 --> 00:47:24.449
and they're all different.

00:47:24.929 --> 00:47:25.110
Um,

00:47:25.550 --> 00:47:27.751
even just different implementations of

00:47:28.550 --> 00:47:29.791
how they do their EVM, like,

00:47:29.811 --> 00:47:31.351
cause everyone wants to use EVM, right.

00:47:31.391 --> 00:47:32.132
But I don't,

00:47:32.231 --> 00:47:33.271
there's like hardly anyone's

00:47:33.291 --> 00:47:34.193
doing the same thing.

00:47:35.112 --> 00:47:38.173
Um, seeing a couple of projects now using,

00:47:38.853 --> 00:47:39.094
um,

00:47:42.391 --> 00:47:42.911
What is it?

00:47:43.293 --> 00:47:44.233
The, the Evmos one.

00:47:45.695 --> 00:47:46.177
Yeah.

00:47:46.197 --> 00:47:46.536
Yeah.

00:47:47.298 --> 00:47:48.659
So I don't know if that's

00:47:48.721 --> 00:47:50.784
been improved since the days of Evmos.

00:47:50.884 --> 00:47:52.907
I abandoned Evmos a while ago.

00:47:52.927 --> 00:47:55.190
Cause didn't they shut it down?

00:47:56.460 --> 00:47:59.521
No, they cut the VALSAT down to the bones.

00:47:59.981 --> 00:48:00.902
To like five, right,

00:48:00.943 --> 00:48:01.402
or something like that?

00:48:01.422 --> 00:48:02.164
It might be in there still.

00:48:02.643 --> 00:48:03.284
Twenty, I think.

00:48:03.324 --> 00:48:04.485
No, we're not in there,

00:48:04.664 --> 00:48:08.128
which I'm stoked about.

00:48:08.148 --> 00:48:08.407
Just Polka.

00:48:08.427 --> 00:48:09.168
You don't like a four

00:48:09.188 --> 00:48:10.568
hundred gig state file?

00:48:11.510 --> 00:48:12.110
No state sync?

00:48:12.570 --> 00:48:12.871
Nothing.

00:48:13.670 --> 00:48:14.751
Just grows forever.

00:48:15.788 --> 00:48:16.088
Yeah,

00:48:16.108 --> 00:48:17.990
so hopefully there's been a lot of

00:48:18.050 --> 00:48:18.992
improvements on that.

00:48:19.652 --> 00:48:20.594
I feel like there has been.

00:48:21.275 --> 00:48:22.315
There's some big names

00:48:22.356 --> 00:48:23.398
getting involved with it now,

00:48:23.498 --> 00:48:25.239
so a lot of devs looking at it.

00:48:26.141 --> 00:48:28.003
I imagine if it's not that great,

00:48:28.023 --> 00:48:29.005
there'd be improvements.

00:48:29.985 --> 00:48:30.666
But I don't think any of the

00:48:30.686 --> 00:48:32.309
utmost issues were actually EBM related,

00:48:32.329 --> 00:48:32.509
right?

00:48:32.548 --> 00:48:33.130
Most of that stuff was...

00:48:34.025 --> 00:48:34.746
State-related?

00:48:34.786 --> 00:48:35.106
State.

00:48:35.126 --> 00:48:36.527
Yeah, yeah.

00:48:36.646 --> 00:48:38.489
Well, yes and no,

00:48:38.509 --> 00:48:40.931
because they started off

00:48:40.951 --> 00:48:42.132
with some really

00:48:42.152 --> 00:48:46.094
inefficient shit and improved it later on,

00:48:46.114 --> 00:48:47.036
but it was already too late.

00:48:47.956 --> 00:48:49.998
Right.

00:48:50.038 --> 00:48:51.059
Which is kind of like...

00:48:52.795 --> 00:48:55.559
I wouldn't say it was inefficient, but, um,

00:48:55.699 --> 00:48:55.958
you know,

00:48:56.059 --> 00:48:58.282
say launched with the IAVL

00:48:58.322 --> 00:48:59.804
database and then they

00:48:59.943 --> 00:49:04.347
improved that over time with the say, um,

00:49:04.489 --> 00:49:04.969
DB.

00:49:05.048 --> 00:49:10.815
So say, yeah, you can, man,

00:49:10.936 --> 00:49:12.137
it is just so much better.

00:49:13.057 --> 00:49:14.940
The say DB than the IAVL.

00:49:15.612 --> 00:49:17.572
Like we're running archives on both.

00:49:19.494 --> 00:49:23.197
And now the way the network is,

00:49:23.376 --> 00:49:25.038
I'm really struggling with

00:49:25.137 --> 00:49:27.260
IAVL to stay up to date.

00:49:28.360 --> 00:49:30.202
So luckily my node restarts

00:49:30.242 --> 00:49:31.161
every day and goes into

00:49:31.181 --> 00:49:33.943
block sync mode after its daily backup.

00:49:35.664 --> 00:49:36.806
So it catches up once a day.

00:49:36.846 --> 00:49:38.447
So it never really gets too far behind,

00:49:38.507 --> 00:49:39.827
but yeah,

00:49:40.838 --> 00:49:41.119
yeah,

00:49:41.259 --> 00:49:42.860
thirty thousand blocks in a day I get

00:49:42.900 --> 00:49:47.003
behind, um, before it'll do the backup,

00:49:47.043 --> 00:49:50.045
so, but that's only in the last, like,

00:49:50.786 --> 00:49:52.146
it's been slowly increasing

00:49:52.226 --> 00:49:54.068
over the last week and a half, so,

00:49:54.108 --> 00:49:56.809
we're gonna, been talking to the guys at,

00:49:57.010 --> 00:49:57.110
um,

00:49:57.190 --> 00:49:58.710
SAE to try and get to the bottom of it,

00:49:58.791 --> 00:50:02.012
but no clear indicator at the moment,

00:50:02.092 --> 00:50:02.954
I don't know if it's just

00:50:03.054 --> 00:50:04.195
gotten to that size,

00:50:04.215 --> 00:50:05.815
where it's just too big now, or,

00:50:08.242 --> 00:50:09.023
just takes too long for it

00:50:09.063 --> 00:50:09.983
to catch up I mean for it

00:50:10.023 --> 00:50:11.264
to get some just too

00:50:11.324 --> 00:50:14.286
unwieldy yeah it doesn't

00:50:14.365 --> 00:50:15.445
doesn't take too long to

00:50:15.485 --> 00:50:16.746
catch up it doesn't even

00:50:16.806 --> 00:50:17.847
seem to take that long to

00:50:17.887 --> 00:50:21.748
finalize block like um you

00:50:21.768 --> 00:50:23.230
know we thought that maybe

00:50:23.269 --> 00:50:25.010
it was taking too long to

00:50:25.050 --> 00:50:26.010
read the database and

00:50:26.050 --> 00:50:27.172
finalize the block and then

00:50:27.192 --> 00:50:28.172
it was just slowly getting

00:50:28.211 --> 00:50:30.132
behind but right looking at it

00:50:31.260 --> 00:50:32.981
Like it's still sub-thirty

00:50:33.021 --> 00:50:34.141
milliseconds most of the

00:50:34.161 --> 00:50:35.282
time to finalize blocks.

00:50:35.322 --> 00:50:36.583
So given that they're about

00:50:36.643 --> 00:50:38.965
three hundred millisecond block time,

00:50:40.105 --> 00:50:41.246
can't be too much of a drama.

00:50:41.686 --> 00:50:43.626
So yeah, I don't know.

00:50:43.766 --> 00:50:44.427
Still looking into it.

00:50:45.327 --> 00:50:47.349
But say DB, no dramas.

00:50:47.469 --> 00:50:49.971
And you can really smash it

00:50:50.010 --> 00:50:53.733
with RPC users as well.

00:50:56.344 --> 00:51:00.708
that uh evm only one um you

00:51:00.728 --> 00:51:01.827
know having people smash

00:51:01.867 --> 00:51:03.728
that with like ten thousand

00:51:04.070 --> 00:51:06.291
block requests um calls

00:51:07.311 --> 00:51:09.253
fine you can you know

00:51:09.472 --> 00:51:10.652
millions of requests a day

00:51:10.693 --> 00:51:11.594
on that thing and it just

00:51:11.773 --> 00:51:14.094
comes along yeah yeah we

00:51:14.114 --> 00:51:15.456
are we are running to um

00:51:16.797 --> 00:51:17.496
it's actually it's not that

00:51:17.516 --> 00:51:19.619
good it's just the cdb also the size

00:51:20.882 --> 00:51:22.625
um like we try to keep like

00:51:22.864 --> 00:51:24.945
four million or more blocks

00:51:25.007 --> 00:51:27.108
on the node um most of ours

00:51:27.148 --> 00:51:28.088
are somewhere between four

00:51:28.108 --> 00:51:30.110
and eight so when we when

00:51:30.130 --> 00:51:31.652
we like restore when our pc

00:51:31.711 --> 00:51:32.592
notes they get to be like

00:51:32.632 --> 00:51:33.632
maybe six seven hundred

00:51:33.672 --> 00:51:34.753
eight hundred eight hundred

00:51:34.773 --> 00:51:35.954
gigs they get a little

00:51:35.994 --> 00:51:37.576
unwieldy you know what I

00:51:37.596 --> 00:51:39.117
mean just in terms of like

00:51:39.338 --> 00:51:40.659
just not necessarily our pc

00:51:40.699 --> 00:51:41.378
response time because the

00:51:41.418 --> 00:51:42.099
response time isn't that

00:51:42.119 --> 00:51:42.780
bad but we've had

00:51:43.661 --> 00:51:45.282
other issues where maybe

00:51:45.302 --> 00:51:46.802
it's more on the price feeder notes,

00:51:46.842 --> 00:51:47.663
but whatever.

00:51:47.702 --> 00:51:50.324
So and so we do a we do like

00:51:50.405 --> 00:51:51.965
a snapshot restore on those.

00:51:52.045 --> 00:51:52.826
I always like pull in

00:51:52.846 --> 00:51:53.487
something that has at least

00:51:53.547 --> 00:51:54.367
four million blocks on.

00:51:54.387 --> 00:51:54.987
So we'll try to keep at

00:51:55.007 --> 00:51:57.028
least like if I take a snapshot today,

00:51:57.528 --> 00:51:58.869
that snapshot wouldn't get used.

00:51:59.010 --> 00:51:59.170
I mean,

00:51:59.190 --> 00:52:00.530
that snapshot has at least the last

00:52:00.630 --> 00:52:01.711
week of data on it.

00:52:01.751 --> 00:52:01.952
Right.

00:52:02.092 --> 00:52:02.512
No matter what,

00:52:02.552 --> 00:52:03.572
like ten days or something like that.

00:52:03.873 --> 00:52:04.914
And those things like almost

00:52:04.954 --> 00:52:06.434
three hundred gigs just for

00:52:06.454 --> 00:52:07.054
that amount of data,

00:52:07.074 --> 00:52:07.574
which is like really

00:52:07.594 --> 00:52:09.056
surprising how much how

00:52:09.076 --> 00:52:09.835
much is in there for that

00:52:10.077 --> 00:52:10.817
for that period of time.

00:52:10.976 --> 00:52:11.436
You know what I mean?

00:52:12.077 --> 00:52:12.197
So.

00:52:13.003 --> 00:52:14.847
It's surprising that over a

00:52:14.887 --> 00:52:15.967
short period of time,

00:52:16.748 --> 00:52:18.130
it'll get reasonably large.

00:52:18.150 --> 00:52:19.693
But over a long period of time,

00:52:19.733 --> 00:52:22.416
it doesn't expand as quick

00:52:22.476 --> 00:52:23.438
as that short period,

00:52:23.458 --> 00:52:24.760
which is... I find that

00:52:24.800 --> 00:52:26.061
kind of interesting.

00:52:26.081 --> 00:52:26.222
Yeah.

00:52:26.242 --> 00:52:27.123
Maybe it's just capturing

00:52:27.143 --> 00:52:28.485
the state as of the...

00:52:29.346 --> 00:52:30.266
I don't know the earliest

00:52:30.306 --> 00:52:31.047
height or something like that.

00:52:31.067 --> 00:52:32.889
And that takes a specific amount of time.

00:52:32.909 --> 00:52:34.309
And then there's block level

00:52:34.329 --> 00:52:35.411
data between there or something.

00:52:35.431 --> 00:52:37.253
I'm not exactly sure, but, but yeah,

00:52:37.353 --> 00:52:38.994
I have noticed that where, so,

00:52:39.014 --> 00:52:39.574
and then moving three

00:52:39.594 --> 00:52:41.735
hundred gig snapshots around is always,

00:52:41.956 --> 00:52:45.239
you know, it's a pain in the ass.

00:52:45.278 --> 00:52:46.621
Ten gig or not, it just takes forever.

00:52:47.440 --> 00:52:47.760
So yeah.

00:52:48.762 --> 00:52:48.922
Yeah.

00:52:48.942 --> 00:52:51.525
Especially over like what the standard, um,

00:52:53.025 --> 00:52:54.007
standard, you know,

00:52:54.067 --> 00:52:55.367
internet size on those

00:52:55.847 --> 00:52:57.228
types of nodes is about a gig.

00:52:57.550 --> 00:52:57.730
So.

00:52:59.903 --> 00:53:01.505
That ain't the fastest.

00:53:01.764 --> 00:53:03.226
Most of our stuff is on X right now,

00:53:03.525 --> 00:53:04.206
at least for say.

00:53:04.347 --> 00:53:07.208
I think everything, at least in Pacific,

00:53:07.288 --> 00:53:10.150
I think is all on X. I don't know.

00:53:10.349 --> 00:53:11.969
Atlantic and Pacific, I'm sure.

00:53:12.070 --> 00:53:14.751
Or on Arctic, I'm sure not.

00:53:15.072 --> 00:53:15.891
But at least for Pacific,

00:53:15.911 --> 00:53:18.454
they're all on X. Because otherwise,

00:53:18.474 --> 00:53:19.574
it's just like those snaps

00:53:19.653 --> 00:53:20.414
and other types of things

00:53:20.434 --> 00:53:21.514
just become a bit of a pill.

00:53:21.554 --> 00:53:22.155
We don't have a lot of data.

00:53:22.175 --> 00:53:22.896
We don't have a lot of data.

00:53:22.916 --> 00:53:23.496
We don't have a lot of data.

00:53:23.655 --> 00:53:24.416
We don't have a lot of data.

00:53:24.436 --> 00:53:25.257
We don't have a lot of data.

00:53:25.277 --> 00:53:25.976
We don't have a lot of data.

00:53:25.996 --> 00:53:26.538
We don't have a lot of data.

00:53:26.557 --> 00:53:27.117
We don't have a lot of data.

00:53:27.137 --> 00:53:27.757
We don't have a lot of data.

00:53:27.777 --> 00:53:28.378
We don't have a lot of data.

00:53:28.398 --> 00:53:29.018
We don't have a lot of data.

00:53:30.222 --> 00:53:30.782
Very,

00:53:31.083 --> 00:53:33.023
very seriously considering moving

00:53:33.063 --> 00:53:40.987
that up to two hundred gig.

00:53:41.068 --> 00:53:41.327
So

00:53:43.570 --> 00:53:46.050
I think there is some pretty

00:53:46.090 --> 00:53:47.391
cost-effective hundred gig

00:53:47.431 --> 00:53:48.492
switches out there, like,

00:53:49.092 --> 00:53:51.192
sixteen port hundred gig switches.

00:53:51.853 --> 00:53:52.393
Yeah.

00:53:52.532 --> 00:53:54.012
So, I don't know.

00:53:54.193 --> 00:53:54.972
I kind of like that.

00:53:55.072 --> 00:53:56.673
At the moment, we use hundred gig switches,

00:53:56.693 --> 00:53:57.994
but we use them breakout

00:53:58.034 --> 00:53:59.074
cables so that they're

00:53:59.135 --> 00:54:01.755
hundred gig into four by twenty-fives.

00:54:04.195 --> 00:54:06.476
But I want two hundred gig

00:54:06.496 --> 00:54:08.737
switches with a hundred gig

00:54:08.777 --> 00:54:11.438
line from each into each node.

00:54:12.418 --> 00:54:12.659
Just...

00:54:14.579 --> 00:54:16.922
just to absolutely go

00:54:17.041 --> 00:54:20.344
overboard just uh just put

00:54:20.364 --> 00:54:21.286
that right in the in the

00:54:21.385 --> 00:54:24.228
note on your little as tag

00:54:24.268 --> 00:54:25.628
just just so I can do an

00:54:25.809 --> 00:54:31.173
iperf test and be like yay

00:54:31.213 --> 00:54:33.516
just put that in every rfp

00:54:33.536 --> 00:54:34.677
what's your backbone oh two

00:54:34.717 --> 00:54:35.858
hundred gig no worries yeah

00:54:38.918 --> 00:54:40.019
proceed to never use that

00:54:40.059 --> 00:54:42.541
again or migrate a node in

00:54:43.141 --> 00:54:45.583
one second it's all fine as

00:54:45.603 --> 00:54:46.784
long as you can show it

00:54:46.885 --> 00:54:52.028
once yeah that's it um ah

00:54:52.128 --> 00:54:53.690
anyway it's like fifty

00:54:53.789 --> 00:54:54.811
fifty is fine for the time

00:54:54.851 --> 00:54:57.393
being um quite a lot of

00:54:57.492 --> 00:54:59.574
nuances in uh proxmox

00:54:59.614 --> 00:55:01.516
between different network

00:55:01.536 --> 00:55:02.717
cards have you ever heard

00:55:02.757 --> 00:55:06.840
of OVS like open vswitch

00:55:08.376 --> 00:55:09.592
It's like a software switch.

00:55:13.166 --> 00:55:14.648
I think not on Proxmox, though.

00:55:15.347 --> 00:55:15.507
I mean,

00:55:15.547 --> 00:55:17.309
we use distributed port groups in

00:55:17.369 --> 00:55:17.769
vSphere.

00:55:17.809 --> 00:55:18.190
Like,

00:55:18.230 --> 00:55:19.610
we have virtual switches all over the

00:55:19.650 --> 00:55:20.791
place, if that's what you mean.

00:55:21.931 --> 00:55:23.672
Yeah, there's a virtual switch, yeah.

00:55:23.693 --> 00:55:24.614
DPGs, they call them there,

00:55:24.634 --> 00:55:25.434
because then you build, like,

00:55:25.954 --> 00:55:27.775
virtual switches off of, like,

00:55:28.255 --> 00:55:29.117
paired ten gigs,

00:55:29.137 --> 00:55:31.378
and then you basically say, what, next,

00:55:31.418 --> 00:55:32.438
go into that virtual switch,

00:55:32.458 --> 00:55:33.659
and you can have, when we have, like,

00:55:33.699 --> 00:55:35.701
twenty VLANs across those switches, right,

00:55:35.721 --> 00:55:36.121
to say,

00:55:37.222 --> 00:55:39.023
segment out traffic across to XYZ.

00:55:40.206 --> 00:55:43.228
So to make VLANs work over here,

00:55:44.009 --> 00:55:45.469
some network cards need to

00:55:45.489 --> 00:55:48.672
be on Linux VLANs and other

00:55:48.713 --> 00:55:50.373
network cards need to have

00:55:50.474 --> 00:55:52.516
a vSwitch with a VLAN attached to it.

00:55:52.536 --> 00:55:55.637
I don't know if they're just

00:55:55.737 --> 00:55:58.199
nuances of the cards or the drivers,

00:55:58.260 --> 00:55:59.581
but I've been looking into it.

00:56:00.161 --> 00:56:00.902
That sounds like an open

00:56:00.961 --> 00:56:03.543
source issue solved by the

00:56:03.563 --> 00:56:05.744
hugely expensive enterprise

00:56:05.784 --> 00:56:09.306
shit that exists.

00:56:09.407 --> 00:56:09.987
Sounds like one of those

00:56:10.027 --> 00:56:11.047
problems that gets solved.

00:56:11.068 --> 00:56:12.228
Do you have like a small

00:56:12.289 --> 00:56:13.248
niggling edge problem?

00:56:13.670 --> 00:56:14.809
Fix it with a million dollar

00:56:14.849 --> 00:56:15.710
enterprise solution.

00:56:16.291 --> 00:56:17.891
With the Broadcom vSphere.

00:56:17.911 --> 00:56:18.012
Yeah.

00:56:18.032 --> 00:56:18.132
Yeah.

00:56:18.152 --> 00:56:18.211
Wow.

00:56:18.231 --> 00:56:21.034
You know.

00:56:22.452 --> 00:56:23.713
boffins be building shit

00:56:23.733 --> 00:56:24.773
can't give it away for free

00:56:24.793 --> 00:56:29.335
right oh man what else is

00:56:29.715 --> 00:56:31.956
oh supra yeah should see in

00:56:31.996 --> 00:56:37.217
supra I think so right yeah

00:56:37.239 --> 00:56:38.518
I'm in supra yeah bought

00:56:38.539 --> 00:56:41.059
yourself a bag it's made

00:56:41.420 --> 00:56:44.402
but I don't even know I I I

00:56:44.481 --> 00:56:47.282
don't know is it launched

00:56:48.371 --> 00:56:49.192
Is it launching?

00:56:49.231 --> 00:56:49.931
I don't know if it's,

00:56:49.972 --> 00:56:52.373
is it launch launch or is it like launch?

00:56:52.693 --> 00:56:53.614
Like, no, no.

00:56:53.735 --> 00:56:56.097
Like you can sell tokens on coin gecko.

00:56:56.817 --> 00:56:56.998
Yeah.

00:56:57.177 --> 00:56:58.719
There's like, do I have any?

00:56:59.519 --> 00:56:59.860
Yes.

00:57:00.139 --> 00:57:02.141
You have probably two

00:57:02.181 --> 00:57:04.362
thousand dollars worth or so.

00:57:04.402 --> 00:57:04.663
Really?

00:57:04.804 --> 00:57:05.043
Where?

00:57:05.063 --> 00:57:07.085
I don't know.

00:57:07.125 --> 00:57:07.806
Have I ever set up a wallet

00:57:07.826 --> 00:57:08.545
for that fucking thing?

00:57:08.565 --> 00:57:11.248
I don't even have.

00:57:11.268 --> 00:57:11.989
There was an airdrop.

00:57:14.010 --> 00:57:14.251
Oh, yeah.

00:57:14.311 --> 00:57:15.311
No, not an airdrop.

00:57:15.331 --> 00:57:15.811
Commissions.

00:57:17.485 --> 00:57:18.405
all right somebody are you

00:57:18.485 --> 00:57:19.847
on are you on super as well

00:57:19.927 --> 00:57:22.128
sir yeah yeah I got well I

00:57:22.148 --> 00:57:22.768
got involved with them

00:57:23.547 --> 00:57:24.927
years and years ago like

00:57:25.309 --> 00:57:27.028
way early um in like an

00:57:27.088 --> 00:57:28.228
iteration before this one

00:57:28.710 --> 00:57:30.590
um and then it went quiet

00:57:30.610 --> 00:57:31.510
it went dead for I don't

00:57:31.530 --> 00:57:32.291
know what was it eighteen

00:57:32.351 --> 00:57:33.010
months or something like

00:57:33.030 --> 00:57:33.731
that and there was like a

00:57:33.771 --> 00:57:34.831
new team involved and then

00:57:35.612 --> 00:57:37.112
kind of like they reached

00:57:37.132 --> 00:57:38.152
back out and we you know

00:57:38.172 --> 00:57:39.393
we're like what's going on

00:57:39.853 --> 00:57:41.693
um so we've yeah i

00:57:42.704 --> 00:57:43.204
it's like one of those

00:57:43.224 --> 00:57:44.186
things where you just hear,

00:57:44.206 --> 00:57:45.626
you're not sure why kind of

00:57:45.766 --> 00:57:46.188
like type of thing.

00:57:46.248 --> 00:57:47.168
Like it's got involved in it

00:57:47.188 --> 00:57:49.190
so early that like still involved in it.

00:57:49.210 --> 00:57:50.150
And like, we're, you know,

00:57:50.530 --> 00:57:51.771
I'm doing all the things,

00:57:53.152 --> 00:57:53.672
doing all the things.

00:57:55.275 --> 00:57:56.014
And that like, they've,

00:57:56.135 --> 00:57:56.916
they've worked pretty,

00:57:57.235 --> 00:57:58.016
that team to their credit,

00:57:58.036 --> 00:57:58.836
they've worked really hard

00:57:58.978 --> 00:57:59.438
on trying to build

00:57:59.458 --> 00:58:00.077
something that's stable.

00:58:00.097 --> 00:58:01.500
Cause early on those early test,

00:58:01.519 --> 00:58:02.699
that stuff, even this Latin,

00:58:02.719 --> 00:58:04.061
the last year have been pretty brutal,

00:58:04.681 --> 00:58:06.643
which she'll take in a test to like,

00:58:07.614 --> 00:58:07.773
I mean,

00:58:07.813 --> 00:58:09.074
he and I were on calls for four

00:58:09.114 --> 00:58:10.474
hours trying to get a network going,

00:58:10.655 --> 00:58:10.856
right?

00:58:10.896 --> 00:58:12.697
With like four of us that we

00:58:12.717 --> 00:58:13.677
found like tons of issues

00:58:13.717 --> 00:58:14.838
or six of us or something like that,

00:58:14.858 --> 00:58:15.498
like early days.

00:58:16.538 --> 00:58:17.458
And they're past all that.

00:58:18.298 --> 00:58:19.260
But there's still some things missing.

00:58:19.300 --> 00:58:20.320
Like there's like there's no

00:58:20.380 --> 00:58:21.221
Prometheus endpoint.

00:58:21.661 --> 00:58:23.762
Like I have I have almost no

00:58:23.802 --> 00:58:24.681
visibility to this thing

00:58:24.862 --> 00:58:25.902
other than a container level.

00:58:27.403 --> 00:58:27.583
Yeah.

00:58:27.903 --> 00:58:28.543
Container, yes.

00:58:28.684 --> 00:58:29.244
Container, no.

00:58:29.385 --> 00:58:29.744
That's it.

00:58:29.804 --> 00:58:30.485
That's all I have.

00:58:30.565 --> 00:58:31.025
Like I don't have.