1 00:00:00,000 --> 00:00:02,640 Yeah, 93 54 is 545. 2 00:00:03,120 --> 00:00:07,760 I don't see that. I see 745. Oh wait, now he's hit 93 54. 3 00:00:07,760 --> 00:00:10,160 I thought this was in Tokyo. Maybe it's in fucking Hong Kong. 4 00:00:14,000 --> 00:00:19,600 Welcome to Game of Modes, a weekly podcast from Independent Validator Teams. 5 00:00:23,680 --> 00:00:26,640 Hello and welcome to Game of Modes, a weekly podcast from 6 00:00:26,640 --> 00:00:31,360 Independent Validator Teams. We do shop around. Here's the evidence. 7 00:00:31,920 --> 00:00:33,760 Now I'm scrolling the Hetsner page. 8 00:00:39,200 --> 00:00:44,960 Imagine if that was true. So just on Hetsner, I've forgotten about Hetsner a little bit 9 00:00:44,960 --> 00:00:49,440 because I don't think any of us use them for any servers, right? 10 00:00:51,680 --> 00:00:52,560 Oh yeah, I have a bunch. 11 00:00:53,120 --> 00:00:55,600 Yeah, yeah, true. Where do you got a Hetsner? 12 00:00:55,600 --> 00:00:58,080 Maybe 10 or 12 or 20? 13 00:00:58,080 --> 00:01:01,120 12? What the fuck are you doing? 12 servers at Hetsner? 14 00:01:01,120 --> 00:01:01,920 They're fucking cheap. 15 00:01:03,040 --> 00:01:05,040 12 servers is a lot of servers now. 16 00:01:05,040 --> 00:01:11,040 Yeah, they're 9950X when they're doing auction servers, man. 17 00:01:11,040 --> 00:01:19,920 They had two 3.8 4TB hard drives and they were like 70 euros, something 60 euros. 18 00:01:19,920 --> 00:01:26,080 So it was like for fucking, you know, just pre-RPC and shit. Fuck yeah. 19 00:01:26,640 --> 00:01:28,400 I have 18. 20 00:01:29,680 --> 00:01:32,800 18? What the fuck are all those servers doing? 21 00:01:34,400 --> 00:01:35,440 A bunch of different things. 22 00:01:36,480 --> 00:01:41,920 Stuff. Some are backup nodes that we run out of the US for different chains. 23 00:01:41,920 --> 00:01:43,200 A couple of personal ones in there. 24 00:01:44,720 --> 00:01:48,880 A lot of RPC. I run a bunch of RPC nodes out of there for different chains. 25 00:01:48,880 --> 00:01:51,440 Could have somewhere put all the big photos. 26 00:01:51,440 --> 00:01:56,640 Vigas. We used to have a backup VFN to be fair, knocking around there somewhere. 27 00:01:56,640 --> 00:01:58,320 Was it VFN? No, it was. 28 00:01:58,320 --> 00:02:00,880 It still wasn't Hetsner. That was still a different provider. 29 00:02:00,880 --> 00:02:03,760 I mean, usually we use two different providers in the same region. 30 00:02:03,760 --> 00:02:10,480 Right. So I have another provider that we use in, let's say Amsterdam, Germany. 31 00:02:11,280 --> 00:02:14,640 Also in the UK and also in Dublin, but fuck all that. 32 00:02:14,640 --> 00:02:19,600 But like, at least in Amsterdam and Germany, actually three providers that we use in Germany. 33 00:02:20,640 --> 00:02:22,320 And Hetsner is one of those, which isn't bad. 34 00:02:22,320 --> 00:02:24,160 I mean, we do, I don't have much in Finland though. 35 00:02:24,160 --> 00:02:26,880 I have most of my stuff is in Falkenstein. 36 00:02:26,880 --> 00:02:32,240 Yeah. I think we now are down to just one box, just a monitoring backup. 37 00:02:32,800 --> 00:02:33,440 Yeah. 38 00:02:33,440 --> 00:02:36,000 Because it's just super, super, super reliable. 39 00:02:36,000 --> 00:02:42,080 And the amount of RAM was just, I mean, it has to be fair, 40 00:02:42,080 --> 00:02:48,320 even a monitoring box is not particularly expensive to run on AWS, but you just get more RAM for the 41 00:02:48,320 --> 00:02:50,160 same price. Yeah. 42 00:02:50,160 --> 00:02:54,480 So ended up shuffling our main box over to Hetsner, just because you could digest, 43 00:02:54,480 --> 00:02:57,440 you could just digest a lot more metrics more rapidly. 44 00:02:59,200 --> 00:03:02,800 Yeah. The only thing there that it's limiting is the one gig. 45 00:03:02,800 --> 00:03:07,760 Like it's everything else I think we run is 10 gig now, almost everywhere. 46 00:03:07,760 --> 00:03:12,000 Maybe, I can't even think of another provider that we use is not 10 gig. 47 00:03:12,720 --> 00:03:14,000 So that's always annoying. 48 00:03:14,000 --> 00:03:16,880 Because then you can't really, I mean, I know you can bump them up, right? 49 00:03:16,880 --> 00:03:19,040 You can, there was a way to migrate them. 50 00:03:19,040 --> 00:03:21,040 So you can pay the money and dump it up. 51 00:03:21,040 --> 00:03:22,880 But then they're not cheap, man. 52 00:03:22,880 --> 00:03:25,680 Then they're not, yeah. I thought the 10 gig is pretty high, isn't it? 53 00:03:25,680 --> 00:03:26,560 I forget what the hell it is. 54 00:03:26,560 --> 00:03:31,600 It's like 100, something bucks to move it and then an extra 15 bucks a month or something. 55 00:03:31,600 --> 00:03:32,560 Yeah. It's a fair bit more. 56 00:03:32,560 --> 00:03:38,080 Like it's enough extra money that you can just go with another provider at that point 57 00:03:38,080 --> 00:03:39,360 if you have a different provider. 58 00:03:40,720 --> 00:03:41,920 Maybe. I don't even know. 59 00:03:43,600 --> 00:03:47,360 It's also, I remember, it has to be like, I think it's a manual process 60 00:03:47,360 --> 00:03:50,400 and you have to open a ticket and all that kind of shit. 61 00:03:50,400 --> 00:03:51,360 And I don't know. 62 00:03:51,360 --> 00:03:53,920 And if you're going to exercise tonight. 63 00:03:53,920 --> 00:03:59,680 I think if I was going to get 10 gig, I would get 10 gig in my rack for five grand a month. 64 00:03:59,680 --> 00:04:01,920 10 gig in the, oh yeah. 65 00:04:03,200 --> 00:04:06,720 But I mean elsewhere, elsewhere, it's, I do like it, especially for, 66 00:04:08,240 --> 00:04:10,640 it's mostly like taking snapshots and uploading. 67 00:04:10,640 --> 00:04:16,160 Hey, man, I get a snapshot of you occasionally and that shit is fast. 68 00:04:17,040 --> 00:04:19,440 Off my, oh, the box in Utah? 69 00:04:19,440 --> 00:04:21,280 Yeah. That thing fucking hauls ass. 70 00:04:21,280 --> 00:04:26,320 Yeah. I pulled a snapshot onto another box with a 10 gig connection 71 00:04:26,320 --> 00:04:29,840 and it was not a long wait, which was nice. 72 00:04:29,840 --> 00:04:31,360 Yeah. I think it was quite large too. 73 00:04:31,360 --> 00:04:33,920 What was that fucking, I think it might have been an autonomy. 74 00:04:33,920 --> 00:04:37,200 Is that the, is that the thing I was badgering you about the other day? 75 00:04:37,200 --> 00:04:38,560 Yeah, I think so. Yeah. Yeah. 76 00:04:38,560 --> 00:04:40,560 I took it back up in a time, you know. Yeah. 77 00:04:40,560 --> 00:04:41,840 Yeah. It's nice and fast. 78 00:04:41,840 --> 00:04:46,240 Yeah. Some of those things really move, like they get whatever that is, like fucking, 79 00:04:48,800 --> 00:04:50,800 like four, 500 megs a second. 80 00:04:50,800 --> 00:04:52,640 Like it's fast. Shit moves. 81 00:04:52,640 --> 00:04:56,240 All right. I'm taking the hit on this fucking Terra switch box. 82 00:04:56,800 --> 00:04:58,160 It's actually, yeah. 83 00:04:59,760 --> 00:05:01,040 Data center buddies. 84 00:05:01,040 --> 00:05:05,680 I'll know a, just emailed me is like, oh, I just let you know your box is activated. 85 00:05:05,680 --> 00:05:07,840 I'm like, bro, I don't even know what the fuck this is for, but I'll take it. 86 00:05:09,360 --> 00:05:10,640 I ordered it in 2023. 87 00:05:12,400 --> 00:05:15,920 Literally ordered it fucking nine months ago, but I'll take it. 88 00:05:15,920 --> 00:05:19,040 Yeah. Ethereum was at four grand. 89 00:05:19,040 --> 00:05:24,960 Yeah. I love how they don't even bother being like, hey, do you still want this or? 90 00:05:24,960 --> 00:05:27,120 Oh, yeah. It's just like, it's an order. 91 00:05:27,120 --> 00:05:29,280 Did you forget about this order you put in fucking one? 92 00:05:30,560 --> 00:05:33,120 I know. They also treated it like it's totally normal. Like, oh, here it is. 93 00:05:33,120 --> 00:05:36,320 Like, I know we just emailed, we just emailed six months ago, but you know, it's right here. 94 00:05:36,320 --> 00:05:38,720 I've been begging you for this thing. 95 00:05:39,920 --> 00:05:41,280 They're just nonchalantly. 96 00:05:41,280 --> 00:05:42,160 Yeah. That's right. 97 00:05:42,160 --> 00:05:44,240 We're going to charge, we charge your card. 98 00:05:44,240 --> 00:05:44,960 Like for what? 99 00:05:46,960 --> 00:05:48,320 We had this conversation. 100 00:05:48,320 --> 00:05:51,680 We're discharged to 1000 US dollars. 101 00:05:52,240 --> 00:05:53,680 It's like Christmas 2023. 102 00:05:53,680 --> 00:05:58,560 If you would like the logic complaint, please wait for 17 hours. 103 00:05:59,920 --> 00:06:05,200 It's kind of like trying to get Epic 9 series back in like winter 2023. 104 00:06:05,760 --> 00:06:09,840 Yeah. We were doing that for those previous net or whatever that was. 105 00:06:09,840 --> 00:06:16,160 That was literally like emailed to every, you know, what's it called? 106 00:06:16,160 --> 00:06:20,400 Client Manager you have. I need fucking Epic's. 107 00:06:21,440 --> 00:06:23,840 What you got? And they're like, yeah, we should put it on order for you. 108 00:06:23,840 --> 00:06:27,680 And you're like, when will it actually fucking arrive? 109 00:06:27,680 --> 00:06:33,200 And then like two weeks later, four people at the same time sent you the email on the same day saying, 110 00:06:33,920 --> 00:06:40,800 we've invoiced you for two months minimum contract on an Epic box at $2,000 a part or 111 00:06:40,800 --> 00:06:44,160 whatever. And you're like, cool. Four of you emailed me on the same day. 112 00:06:44,160 --> 00:06:44,480 Sick. 113 00:06:44,480 --> 00:06:46,080 We've reversed that shit. 114 00:06:46,080 --> 00:06:46,560 Yeah. 115 00:06:46,560 --> 00:06:54,000 Have you seen the new Epics with the like the 9555s and that type of stuff? 116 00:06:54,640 --> 00:06:57,040 And they are, they're getting the clock speeds up now. 117 00:06:57,040 --> 00:06:57,920 They're getting bias. 118 00:06:57,920 --> 00:06:58,560 Yeah. 119 00:06:58,560 --> 00:06:59,040 Yeah. 120 00:06:59,040 --> 00:06:59,360 Yeah. 121 00:06:59,360 --> 00:07:05,440 I was also looking at, because I've always looked at, I mean, thread rippers are really 122 00:07:05,440 --> 00:07:11,360 like the sweet spot for us for node apps because it does have the high clock speed and the cores 123 00:07:11,360 --> 00:07:16,800 are there more than the Epic. Like it doesn't have as much cores as the Epics do, but the clock 124 00:07:16,800 --> 00:07:20,160 speeds are really there. And I tried those like a lot in preview net two, trying to like, because 125 00:07:20,160 --> 00:07:25,360 there's a couple of thread rippers that are fucking fast, like five points, something gigahertz boosting 126 00:07:25,360 --> 00:07:29,360 and then with like a good 2432 cores. And I'm like, they're ridiculously fast. 127 00:07:30,000 --> 00:07:32,640 They still have like the same, they don't have the same series. 128 00:07:32,640 --> 00:07:33,600 Are they the thread rippers? 129 00:07:35,280 --> 00:07:36,480 Like the Epic 4000s. 130 00:07:36,480 --> 00:07:37,840 Are they what they calling thread? 131 00:07:37,840 --> 00:07:38,640 Oh, I don't know. 132 00:07:38,640 --> 00:07:39,840 I don't know. I don't even know. 133 00:07:39,840 --> 00:07:46,480 Actually, they might be because those Epic 4000s are kind of like Ryzen like in performance. 134 00:07:47,200 --> 00:07:52,000 No, those are the, no, those aren't the, no, no, no, those are like the, those are like the 79X, 135 00:07:52,000 --> 00:07:53,520 right? I'm sorry. I know what you're talking about. 136 00:07:53,520 --> 00:07:57,040 Oh, those are like the consumer Epic series, I guess is what they are. 137 00:07:57,040 --> 00:07:59,280 Right. Is that how they kind of position them? 138 00:07:59,280 --> 00:07:59,440 Yeah. 139 00:08:00,880 --> 00:08:04,880 The thread rippers are the, where's the specs? 140 00:08:04,880 --> 00:08:14,320 Yeah. Like the Pro 7995. Like for instance, a good example is the 7945WX, which is, 141 00:08:14,320 --> 00:08:20,320 it's only 12 core 24 thread, but it's base at 4.7 and boost to 5.3. 142 00:08:20,320 --> 00:08:25,600 Like that's a good fast, like, and there's another one that's like base of 4.5 boost to 5.3, 143 00:08:25,600 --> 00:08:30,480 which is 1632. So it's like basically a 75X with a ton more cash to it and, 144 00:08:30,480 --> 00:08:32,400 and like a little faster clock speed to it. 145 00:08:32,400 --> 00:08:36,800 But some of these things are, they're, they're pretty blistering, man. Anything over 4 GHz, 146 00:08:36,800 --> 00:08:38,720 like for what we do is like crazy good. 147 00:08:38,720 --> 00:08:46,320 Like the, the 9,005 series is not, yeah, it's not there. It's up to 4.8. 148 00:08:46,320 --> 00:08:53,120 Yeah. Yeah. I mean, this base at, base at 4, base at 4.5 and boost to 5.3 at 32 threads. 149 00:08:53,120 --> 00:08:58,320 Like that's basically like a 7950X on steroids. They're huge too. They're like these massive 150 00:08:58,320 --> 00:09:00,800 chips and they do make them like, there's workstation boards, like you can get, 151 00:09:00,800 --> 00:09:04,800 there are definitely boards with IPMI and everything else. So you see them in like, 152 00:09:05,440 --> 00:09:08,080 in different data centers, but most people just get the epics. 153 00:09:09,120 --> 00:09:11,760 Epics are a little bit of a waste for us. I think sometimes other than like what we're 154 00:09:11,760 --> 00:09:15,120 talking about here in this, in this situation, there's just, there's just sometimes there's 155 00:09:15,120 --> 00:09:19,200 too many cores and like, it's better to have a couple, seven, like fifties, and it's to have a 156 00:09:19,200 --> 00:09:21,440 bunch, a huge epic, you know, doing a bunch of shit. 157 00:09:22,000 --> 00:09:28,480 9175F is a 16 core up to 5 gigs, base clock 4.2. 158 00:09:28,480 --> 00:09:33,120 Oh yeah. Like, like the smaller epics that have less threads. 159 00:09:33,120 --> 00:09:36,320 But it's got high, high cage too. It's like 512 meg of cache. 160 00:09:36,960 --> 00:09:38,560 Layers. Cache. Cash. 161 00:09:39,200 --> 00:09:42,080 Get that cache. Yeah. Get that cache money. 162 00:09:43,680 --> 00:09:46,320 That looks like a nice CPU. I might buy one of those. 163 00:09:46,320 --> 00:09:48,240 Yeah. There's a, I mean, that whole line is pretty good. 164 00:09:48,960 --> 00:09:54,640 So hopefully. So like, we've got high core count fucking thread rippers in the rack and 165 00:09:54,640 --> 00:10:01,760 fuck man, I use about three cores. Like I got like one of those has got maybe 20 fucking VMs on it 166 00:10:01,760 --> 00:10:05,280 and it's idle. Like it's, yeah, just doing nothing. 167 00:10:05,840 --> 00:10:11,520 Yeah. So RAM bound to have fast, the fast clock speeds and the RAM, you can't put too much RAM in 168 00:10:11,520 --> 00:10:17,600 them. So they got like half a tip and I think I only get up to like performance servers just 169 00:10:17,600 --> 00:10:22,640 sat in a rack doing nothing. It's kind of like peak what we do, isn't it? 170 00:10:22,640 --> 00:10:30,320 Yeah. It's pretty fair. I mean, most of our machines, most of my machines are like the 171 00:10:30,320 --> 00:10:35,760 utilization is way too low. Yeah. Like 3% or something a lot, but especially the high end ones 172 00:10:35,760 --> 00:10:40,960 like outside of load tests. Forget about it. 173 00:10:42,640 --> 00:10:45,680 His hard drives get fucking pummeled though. Am I right? 174 00:10:45,680 --> 00:10:45,920 Yeah. 175 00:10:47,440 --> 00:10:48,400 Someone told me. 176 00:10:48,880 --> 00:10:51,040 The two things are going to hard drives and RAM. 177 00:10:51,040 --> 00:10:55,680 I saw it in a movie. They said build it and they'll come and I built it and they didn't come. 178 00:10:56,160 --> 00:11:02,480 Yeah. I've also noticed this phenomenon over the last few years. 179 00:11:03,040 --> 00:11:06,480 So anyway, I also won't. 180 00:11:09,040 --> 00:11:12,560 I'm also desperate to buy more drives. I don't know why I just have a drive problem. 181 00:11:13,680 --> 00:11:16,880 You really do. Like you've literally got just like stacks of them lying around. 182 00:11:16,880 --> 00:11:22,880 You know, like so much unused space. We're going to have this conversation like in a 183 00:11:22,880 --> 00:11:26,560 couple of years where it's going to be like, well, that was a wild ride. 184 00:11:26,560 --> 00:11:32,400 Anyway, like literally back to McDonald's and we'll be like, yeah, but like you were doing 185 00:11:32,400 --> 00:11:38,000 pretty well there for a while, Big Balls blockchain. Like did you not put any money aside and it 186 00:11:38,000 --> 00:11:44,000 would turn out you just spend it all on hard drives and then thrash the hard drives to death 187 00:11:44,000 --> 00:11:50,400 and now the hard drives are worth nothing and all you have left is a broken pile of hard drives. 188 00:11:50,400 --> 00:11:55,120 And you're like, can you pay your mortgage and like broken hard drives? And the answer is no. 189 00:11:55,120 --> 00:12:03,760 So I've been flogging some 15 terabyte drives for like a good two and a half years now. 190 00:12:03,760 --> 00:12:06,880 And I don't think they've even got 5% where. 191 00:12:06,880 --> 00:12:10,080 Is that what your super brand, right? What the hell is that? 192 00:12:10,080 --> 00:12:16,800 Oh, the Dappel store. All my expensive drives are all Dappel store. 193 00:12:19,200 --> 00:12:27,520 I totally thought that I was. Dappel store. It's been like this last week has been like 194 00:12:27,520 --> 00:12:33,600 quite a lot of debugging. I'm doing like a pass through and some drives to some VMs to get like 195 00:12:33,600 --> 00:12:40,960 that, that near native performance, baby. And now because your performance of not that these 196 00:12:40,960 --> 00:12:47,200 shit chains haven't got any users. I know that you know all about this fucking 197 00:12:47,200 --> 00:12:54,880 numer nodes. The numer, like the drives have to be plugged in certain places so that they're on 198 00:12:54,880 --> 00:13:00,240 different numer nodes so that you can pass them through without breaking other connections. So 199 00:13:00,240 --> 00:13:07,840 we use, I didn't realize at the beginning, but I had some drives running on Ceph and I had other 200 00:13:07,840 --> 00:13:14,640 drives that I wanted to pass through to VMs, right? And if you've got say four drives on one 201 00:13:14,640 --> 00:13:20,080 numer node, you can only pass like you can pass all of them to one VM, but you can't individually 202 00:13:20,080 --> 00:13:25,280 pass them to different VMs. And if you've got Ceph running on that same numer node, if you pass 203 00:13:25,280 --> 00:13:32,960 one, it'll break Ceph and then your Ceph will go offline. Yeah. I mean that that OSD will go offline 204 00:13:32,960 --> 00:13:36,720 so that that one drive will. I didn't know it was that it was that rigid. I thought it was 205 00:13:36,720 --> 00:13:41,520 really more performance thing. No, no, it's just like what's using too much memory in the land or 206 00:13:41,520 --> 00:13:48,560 same. Yeah, it's because like the all those controllers are like adjoined and you know, 207 00:13:48,560 --> 00:13:54,720 it's like you can't close a door between them. And they're all on the same sort of, 208 00:13:54,720 --> 00:14:01,680 you know, PCI bus because they're joined to that. You can break up your CPU into more 209 00:14:01,680 --> 00:14:08,640 numer nodes though, like you can go into the the BIOS and you can do one, two, four and maybe eight. 210 00:14:08,640 --> 00:14:16,960 I'm not sure about the eight one. And then your RAM and your CPUs and your lanes, your PCI lanes 211 00:14:16,960 --> 00:14:23,120 all get divided by those numer nodes, right? So anyway, I had to go through the manual, 212 00:14:23,120 --> 00:14:29,120 find out which slots are connected to, you know, which connectors on the board and then figure 213 00:14:29,120 --> 00:14:34,080 out where those connectors on the board are connected to the CPU. So you can like work out 214 00:14:34,080 --> 00:14:39,760 the numer node partitioning and then go and move the fucking drives. And then you can don't you 215 00:14:39,760 --> 00:14:43,840 and you can can you change or you can bond those lanes and BIOS and things like that you could say. 216 00:14:44,720 --> 00:14:49,680 No, it's a physical connection. So you just go and unplug it and plug it into a different slot 217 00:14:49,680 --> 00:14:54,960 that's on that that's connected to a different part of the CPU. Right. But I thought you could in the 218 00:14:54,960 --> 00:14:59,280 but in the BIOS you could say that these two nodes like one and two are one and you can like you 219 00:14:59,280 --> 00:15:02,640 can like bond them or some sort of structure and then I thought there's some shit with that. 220 00:15:03,360 --> 00:15:13,600 So there when you assign your numer partitions, if you go and run numer CTL, it'll tell you like 221 00:15:13,600 --> 00:15:19,840 what resources are allocated to what numer node. So to tell you what CPUs are allocated, 222 00:15:20,720 --> 00:15:25,920 how much RAM, I'm not sure how you pin the RAM to. So, you know, if you wanted to the absolute 223 00:15:25,920 --> 00:15:32,960 lowest latency for a VM, right, you would have the hard you would pass through a PCI pass through 224 00:15:32,960 --> 00:15:39,280 a drive on it. Say it was on numer node zero, right, you would find the drive that's on numer 225 00:15:39,280 --> 00:15:45,520 node zero pass that through PCI and then you would pin the RAM and the CPU cores that are 226 00:15:45,520 --> 00:15:50,800 associated with numer node zero to that VM. And then you'd get like the fastest lowest latency 227 00:15:50,800 --> 00:15:58,560 possible for that VM. And you also turn off like a bunch of different power saving options and 228 00:15:58,560 --> 00:16:07,120 shit in the BIOS. And after I did that, I got a call from my data center provider asking for more 229 00:16:07,120 --> 00:16:13,360 money because turning off your power saving options really ramps up the. 230 00:16:13,360 --> 00:16:18,720 Did they I told you that I told you like that he turned that thing on to what is it not efficiency 231 00:16:18,720 --> 00:16:23,600 is turned on the fuck it mode and like it uses it just both power supplies is 100%. We're just 232 00:16:23,600 --> 00:16:29,040 jagged. We're just pushing this CPU as much as we can. Yeah, man, you turn off like the the C state 233 00:16:29,040 --> 00:16:35,200 controls the P state controls turn everything on the fucking performance and you get a call from 234 00:16:35,200 --> 00:16:39,600 your your rack provider. They call you like right away. They're like, what are you doing? What the 235 00:16:39,600 --> 00:16:47,680 happened here, man? Did you add some new hardware? I turned off the power saving options. You're 236 00:16:47,680 --> 00:16:54,640 like, I know I might have maybe turned off the power saving options that and I have like just 237 00:16:54,640 --> 00:17:00,640 a shitload of spinning rust powering away in this. Those things. I assume you turned it back off. 238 00:17:00,640 --> 00:17:06,640 No, you left it. Yeah, I don't think you should check and see if it actually makes that much of 239 00:17:06,640 --> 00:17:12,800 a difference. It does for sef. So the reason I turned all that shit off is to get the lowest 240 00:17:12,800 --> 00:17:20,400 latency for sef. Otherwise, it affects your IOPS. So my network strong enough, it's just that with 241 00:17:20,400 --> 00:17:26,960 the power saving options on the CPU, because it has to ramp up and down, it adds latency to the 242 00:17:26,960 --> 00:17:34,080 to the CPU instructions. So when you just have it like balls to the wall all the time, it's like, 243 00:17:34,080 --> 00:17:40,560 hey, hey, instructions. What do you need? Right? Yeah. And the governor is set to performance. So 244 00:17:40,560 --> 00:17:43,920 even even with the C states on, you still the governor of performance is still wasn't fast 245 00:17:43,920 --> 00:17:48,240 enough. Governor is always performance, but it doesn't make a difference. It's once it stops 246 00:17:48,240 --> 00:17:56,320 seeing any load, it'll just fucking start taking power away. Yeah, interesting. Yeah. Yeah, which 247 00:17:56,320 --> 00:18:03,760 is great for the pocket, not great for the performance. So but yeah, so I really, you know, 248 00:18:03,760 --> 00:18:08,720 I'm dedicated to sef and it's very poor performance. So yeah, that's what I've heard. 249 00:18:08,720 --> 00:18:13,040 Need more nodes. Well, it's you can get really good performance out of it, but you just need 250 00:18:13,040 --> 00:18:18,240 to like spend more money. I always thought it was like a it's like, I mean, it's no different 251 00:18:19,120 --> 00:18:23,920 than these fear data stores in some sort of way where not quite the same thing. But but the idea 252 00:18:23,920 --> 00:18:29,920 is that it's liveliness over performance, right? And so exactly. Yeah, right. At the moment, 253 00:18:29,920 --> 00:18:34,560 it serves a very good purpose. I've got way too much storage allocated to it. So we're going to buy 254 00:18:34,560 --> 00:18:40,720 some more drives and then cycle those larger drives down to smaller drives and just use it for like 255 00:18:40,720 --> 00:18:51,280 mission critical services. So you things like signers, bloody, you know, Pego, Zabix, proxies, 256 00:18:51,280 --> 00:18:56,960 all that type of stuff, like all mission critical services that can't go down or go on sef. And 257 00:18:56,960 --> 00:19:02,960 then, you know, partition out bigger. And we've talked about this before partitioning out bigger 258 00:19:02,960 --> 00:19:13,120 allocations of resources to run, you know, multi homed fucking boxes with a bunch of 259 00:19:13,120 --> 00:19:17,360 different things on them. So at the moment, we have a lot of individual services running around 260 00:19:17,360 --> 00:19:21,360 the place, which I'll still do for things that for temporary things. I think I'll keep doing that for 261 00:19:21,360 --> 00:19:27,360 test nets because you do like it's handy just to be able to like make an environment, fuck around 262 00:19:27,360 --> 00:19:33,680 with it, delete it. Whereas like when you've got like you can you can bring you can cluster things 263 00:19:33,680 --> 00:19:38,960 together in a production environment because nothing ever really changes there. It's like it's 264 00:19:38,960 --> 00:19:45,040 just running. Yeah, yeah, definitely like the flexibility of being able to do both. And I'm 265 00:19:45,040 --> 00:19:52,480 going to buy another box for like a large storage array and run, you know, services that need 266 00:19:52,480 --> 00:19:58,880 shitloads of storage on just that one box. Mainly, I'm going to start putting my archives back on 267 00:19:58,880 --> 00:20:04,880 their own boxes, because it's just a little bit more difficult to manage with all of the drives. 268 00:20:06,000 --> 00:20:12,960 Are they in sef now? They're not in sef, fuck no. But they're on Proxmox. So they're still 269 00:20:12,960 --> 00:20:18,400 VMs, they're just big VMs with a bunch of drives. Oh, it drives map too. Yeah. Yeah, which is still 270 00:20:18,400 --> 00:20:23,280 to my surprise, it works quite well. I do that here at the house, like just the ZFS and just 271 00:20:23,280 --> 00:20:28,320 map it in there and whatever. Yeah, yeah, exactly. Because I didn't even when I set that up because 272 00:20:28,320 --> 00:20:36,000 I took that, I migrated this from a from just a bare metal box, right? And when I migrated it, 273 00:20:36,000 --> 00:20:44,240 all I did was I preset up a VM, installed all the softwares, right? And then I literally just 274 00:20:44,240 --> 00:20:50,560 unplugged the hard drives, plugged them into one of the Proxmox boxes, passed them through, 275 00:20:50,560 --> 00:20:57,200 that took maybe 10 minutes, and then just went into that VM and then just imported the ZFS 276 00:20:57,760 --> 00:21:03,520 cluster and then just changed all like, sim linked all the homes, and then turned everything on and 277 00:21:03,520 --> 00:21:08,960 it was fine. So it's cool. Really fast. That's ZFS, man, just being able to like import pools. 278 00:21:09,520 --> 00:21:15,600 And it's all just there is perfect. I love that. Yeah, it works. Even actually, to my surprise, 279 00:21:15,600 --> 00:21:22,080 like, I know you don't have necessarily a lot of experience with Proxmox or recent experience 280 00:21:22,080 --> 00:21:26,800 with Proxmox, I think you say you used to use it. But there's a lot of nuances with passing through 281 00:21:26,800 --> 00:21:33,040 drives as I've talked about. And like to do with these numeros, it can be a real fucking pain on 282 00:21:33,040 --> 00:21:40,240 the ass to try and actually pass the full drive through with PCI era. But you can, you can pass 283 00:21:40,240 --> 00:21:49,920 the drive as a block device with SCSI, like Vert.io SCSI controller, and pass the whole drive. 284 00:21:50,560 --> 00:21:58,720 And, you know, normally, right, you mount a drive in Proxmox, you make like a QCOW or a raw drive, 285 00:21:58,720 --> 00:22:03,120 and then, you know, you give that to the VM and then that's your virtualized driver. 286 00:22:03,120 --> 00:22:08,400 This other method does actually pass it through to a block device. And to my surprise, 287 00:22:09,520 --> 00:22:15,440 it fully functions as a block device. But you do, there is like overhead in that translation 288 00:22:15,440 --> 00:22:20,320 between Vert.io. So you don't get fully the native speed of it. But like, you get pretty, 289 00:22:20,320 --> 00:22:29,760 like you get pretty good enough. Yeah. But if you create a ZFS device on that drive that you've 290 00:22:29,760 --> 00:22:35,040 passed through, and then take it out and then do the PCI E pass through all the way through to that 291 00:22:35,040 --> 00:22:41,200 VM, it still functions as a ZFS device if you just, you know, import it again. I didn't think 292 00:22:41,200 --> 00:22:45,840 that I thought it might have still had some sort of virtualization layer that would break it, but 293 00:22:45,840 --> 00:22:51,680 it doesn't. It's fully a fucking block device. So that's cool. Yeah, it's, it actually works pretty 294 00:22:51,680 --> 00:22:59,040 good. But one thing, so I had like a bit of a speed issue. And I think I'm not sure if I did that 295 00:22:59,040 --> 00:23:05,680 scuzzy mounting properly. But that one drive that I was messing around with, when I looked at the, 296 00:23:06,320 --> 00:23:13,840 you know, like verbose LSPCI E output, right, or the hardware LS hardware, you could see that, 297 00:23:13,840 --> 00:23:22,640 that one drive got nerfed all the way down to like gen three speed. So I actually had to restart 298 00:23:22,640 --> 00:23:27,440 that server to get it back out of gen three speed. I'm not sure if I went and unplugged it and plugged 299 00:23:27,440 --> 00:23:32,480 it back in, it might have gone back to like a gen five speed, but yeah, it was slow. And I was like, 300 00:23:32,480 --> 00:23:36,960 why the fuck is this thing slow? And then I started fishing around that, you know, all those values 301 00:23:36,960 --> 00:23:42,960 of what it was getting out of the port. Yeah. And I was like, Oh, it's been fucking, it's slow, 302 00:23:42,960 --> 00:23:51,760 because it's been like governed somehow. But yeah, anyway, I restarted the machine, 303 00:23:51,760 --> 00:23:55,680 passed it through his PCI and had the full speed of it again. So I don't know. 304 00:23:55,680 --> 00:24:00,400 And we've been messing with a little bit this week, too, because Stargaze, because familiar 305 00:24:00,400 --> 00:24:08,960 is going, so they're pushing to IAVL one. Yeah. So you're hosting the, the, the snapshot for that. 306 00:24:08,960 --> 00:24:12,560 Yeah. Yeah. So for I don't really know that maybe you could, I don't even know the differences 307 00:24:12,560 --> 00:24:17,120 between those two, honestly, and what the hell it's about. But I know it's faster. 308 00:24:18,160 --> 00:24:23,360 I know it takes a long time to migrate. It does. Yeah. I think once it's in operation, it's kind of like 309 00:24:26,000 --> 00:24:29,360 conceptually similar, because it's all the key value stores, right? It's a little bit similar 310 00:24:29,360 --> 00:24:35,760 to like the RocksDB sharding stuff that we had to do over in Aptos land. Yeah. Like you can do a 311 00:24:35,760 --> 00:24:39,840 lot of things that will change like storage format. And it's always going to result in 312 00:24:39,840 --> 00:24:46,160 yeah, like a slow re-import in exchange for whatever. So it's a storage, it's a storage format 313 00:24:46,160 --> 00:24:49,120 change. Is that what that is? I think it's a storage format change. Yeah. Okay. All right. Yeah. So, 314 00:24:50,080 --> 00:24:54,800 so what, what are you doing, which, which I really like, so he wants to obviously make it as part of 315 00:24:54,800 --> 00:25:01,360 this v15 upgraded. So he pushed an upgrade, a change now, basically a state compatible version 316 00:25:01,360 --> 00:25:05,760 that has IAVL one. So people could just run the migration as they want to, right? And there's 317 00:25:05,760 --> 00:25:10,160 providing some snapshots that are already converted. But the same thing with it. So, and then we were 318 00:25:10,160 --> 00:25:15,280 on the Stargate, Stargate's archive. And so that was, it was really like, I mean, obviously we 319 00:25:15,280 --> 00:25:20,400 take snapshots every week for, we take ZFS snapshots to be able to actually snapshot the node and 320 00:25:20,400 --> 00:25:23,440 push it all across and things like that. It's about, it's growing. That's like almost seven 321 00:25:23,440 --> 00:25:27,840 terabytes, I think, somewhere around that line. I mean, it's still, it's been a couple years, 322 00:25:27,840 --> 00:25:32,880 right? So it's still, it's getting a little beefy. But it's like, it's, it's like, I, we don't, 323 00:25:32,880 --> 00:25:38,480 I should use ZFS more is really what I'm saying is because it's so frickin nice to be able to 324 00:25:38,480 --> 00:25:44,080 snapshot up and then we just ran that upgrade. Took like, I think it took three hours to upgrade 325 00:25:44,080 --> 00:25:47,840 the node, at least the initial migration, I guess it does some migration in the background as well, 326 00:25:47,840 --> 00:25:54,320 maybe a couple hours, actually. And then, yeah, no issues, no problem. Took another snapshot of it, 327 00:25:54,320 --> 00:26:00,000 blah, blah, blah. Like it's, it's so, it's so frickin handy to do those types of state issues 328 00:26:00,000 --> 00:26:05,520 and things that are really, you really don't want to break, you know what I mean? So plus, 329 00:26:05,520 --> 00:26:09,840 plus we ended up doing a, I am doing a state restore on old snapshot as well as to make sure 330 00:26:09,840 --> 00:26:13,520 that everything is working and then we have, you know, like we want to test our backups, obviously. 331 00:26:14,960 --> 00:26:20,880 So all that's been good. So I am, I'm definitely already fucking blue peeled on ZFS. You don't 332 00:26:20,880 --> 00:26:30,720 have to sell it to me. I know my naive understanding and like relooking at the the I have all tree docs. 333 00:26:31,440 --> 00:26:38,720 Yeah. Suggest that if there's like a major, if there's a change to the way maybe serialization 334 00:26:38,720 --> 00:26:43,200 works or something like that, then that might result in having to rebuild the tree. I don't know 335 00:26:43,200 --> 00:26:51,920 that maybe that's why it took, I mean, how long are we talking for a, for a node with, I don't know, 336 00:26:51,920 --> 00:26:58,880 a few weeks of data on it, maybe five, 10 minutes. My archive node, which is seven terabytes took 337 00:26:59,680 --> 00:27:07,760 two hours, a little over two hours. And based on ZFS, it modified around 360 gigs of data 338 00:27:07,760 --> 00:27:14,880 out of seven terabytes. Okay. So that sounds like it's rebuilt the whole tree. Yeah, I think it was. 339 00:27:14,880 --> 00:27:19,040 Yeah, I think it was, I think it was. There's not really, there's some pretty shitty reporting 340 00:27:19,040 --> 00:27:22,720 around that because you can't really see progress. It's really difficult to actually tell if it's, 341 00:27:22,720 --> 00:27:28,720 if the migration's occurred on a node. Like it's, because I think what it will be doing is, again, 342 00:27:28,720 --> 00:27:32,880 I like, I don't know the exact thing that happened in the Stargaze upgrade, but I guess it's going 343 00:27:32,880 --> 00:27:40,240 to rebuild the tree. Yeah. And it's also then going to be rebuilding it in place. So it's then 344 00:27:40,240 --> 00:27:49,120 saving it to, Christ was called level DB. Yeah. The tree is just the representation of each 345 00:27:50,720 --> 00:27:57,440 Merkel route. Well, it's not a Merkel route. So it's an AVL tree. I don't know what AVL stands 346 00:27:57,440 --> 00:28:04,000 for. Apologies. I probably should know that. But anyway, it's the equivalent of the Patricia 347 00:28:04,000 --> 00:28:09,360 Merkel tree that Ethereum uses. But this, yeah, whatever. I think, you know, as an aside, I think 348 00:28:09,360 --> 00:28:14,080 the reason that we have to have some cosmos with the, with non-deterministic transaction 349 00:28:14,080 --> 00:28:21,440 ordering on occasion, I think is because of the way the hash, I think because of, I think leaf 350 00:28:21,440 --> 00:28:29,760 nodes are not hashed. Only the root hash is hashed. So when you get an app hash, it's a root hash, 351 00:28:30,400 --> 00:28:36,800 not matching, right? So the transactions are different. But if you hash all the leaves, 352 00:28:36,800 --> 00:28:40,720 then the leaves are deterministic up to the root, like in the Patricia Merkel tree. 353 00:28:41,520 --> 00:28:45,600 So there are some trade-offs there. But I think that design decision is part of the reason we 354 00:28:45,600 --> 00:28:51,680 have app hashes in cosmos. Sorry, not app hash. Well, actually, maybe it is app hashes because it 355 00:28:51,680 --> 00:28:56,720 would be different transaction ordering with the same transactions. But I guess, yeah, app hash could 356 00:28:56,720 --> 00:29:03,280 also be some other malicious thing. It could actually be anything where the root hash is 357 00:29:03,280 --> 00:29:08,960 different. But it feels like issues around non-deterministic transaction ordering are maybe 358 00:29:08,960 --> 00:29:16,720 potentially related to using Iavl rather than the Merkel trees. Yeah. So I think you're like, 359 00:29:16,720 --> 00:29:23,200 at least target is to go on the right way with it, which is, you know, allow validators to make the 360 00:29:23,200 --> 00:29:29,760 change now, do it at their own pace, right? With a non-state breaking type of change, change a 361 00:29:29,760 --> 00:29:33,920 node out, you know, a lot of people are running obviously Horcrux things like that, take your time. 362 00:29:33,920 --> 00:29:39,360 So it's not happening at the upgrade. So when the upgrade actually occurs on v15, you're not 363 00:29:39,360 --> 00:29:43,440 waiting for, you know, the upgrade, hopefully you're not waiting for two hours or upgrade to occur, 364 00:29:43,440 --> 00:29:47,600 right? For all these nodes to sit there and churn through whatever fucking block history they have. 365 00:29:48,160 --> 00:29:52,240 So it's nice that it's state compatible. It's only the store that's really changing, right? 366 00:29:52,240 --> 00:29:57,040 Yeah. I have noticed a lot of fucking, well, I've been having since they've been doing that, 367 00:29:57,040 --> 00:30:03,360 I've been having some sinking issues on my RPC. So really? Yeah, I'm not sure. Like, 368 00:30:03,360 --> 00:30:08,400 I haven't changed the, oh, fuck, I better do that. When's that upgrade? They haven't, 369 00:30:08,400 --> 00:30:11,440 they haven't even put the thing. I think it's, I think it's coming Monday. 370 00:30:12,160 --> 00:30:18,080 Yeah. Just had fucking, in the last couple of days, it's just been like having a bit of a 371 00:30:18,080 --> 00:30:21,600 sinking issue. So I'm assuming that's because more and more people are moving to that. 372 00:30:21,600 --> 00:30:26,320 It could be. They store, but I don't know. Yeah, unstable pairs maybe. It could be. We've had, 373 00:30:26,320 --> 00:30:30,160 we've had, I've had bad peers of like a fucking ton of nodes actually, 374 00:30:30,160 --> 00:30:34,000 not just not in Stargaze. I mean, just elsewhere say has been really brutal, 375 00:30:34,000 --> 00:30:40,080 like really bad peers. Yeah. So anyway, yeah, pretty cool. I think, and also I've noticed, 376 00:30:40,080 --> 00:30:45,840 like, you know, the, just how fast IBL is, I'll be a one is, I guess, things like startup on 377 00:30:45,840 --> 00:30:50,480 that archive would take, I'm not sure how long it takes and say, but like, like it would take 378 00:30:50,480 --> 00:30:56,560 probably a minute, minute or two minutes for it to like, I don't know, do it shit before it started 379 00:30:56,560 --> 00:31:00,720 to peer out and get moving just a little in the store, I guess. And now that's down to, 380 00:31:00,720 --> 00:31:05,760 you know, I don't know, 10, 15 seconds or less. It's just way faster. So some things like that, 381 00:31:05,760 --> 00:31:11,040 like it's really nice quality improvement there. So anyway, nice little, nice little. 382 00:31:11,040 --> 00:31:16,160 What, what version of the SDK is that on? I have no idea. 383 00:31:18,080 --> 00:31:22,080 I guess it must be version 50 or so. That's 50.1. Yeah. 384 00:31:22,080 --> 00:31:27,680 Right. Right. Okay. It's moving at all because, because like the implementation of IAVL is like, 385 00:31:29,200 --> 00:31:33,040 I think version 1.0 is on version 1.3 on the bleeding edge. 386 00:31:35,360 --> 00:31:42,560 And there's a, actually in the repo, there's a curious tag, Cosmos SDK.io store V2 387 00:31:43,680 --> 00:31:48,640 for version two of IAVL. So heart. Heart of the press. 388 00:31:48,640 --> 00:31:56,000 I guess I see all on that now. What's that? Is that I see all now that owns that must be right? 389 00:31:56,000 --> 00:32:02,000 Was that, uh, I mean, before, was that binary or Confio or somebody else? 390 00:32:02,880 --> 00:32:08,560 Well, it'll be, it's in the Cosmos repo. So whoever wants the Cosmos repo. 391 00:32:08,560 --> 00:32:15,040 Yeah. Just probably like every, I imagine that whoever, yeah, it would have been ICF, I think, 392 00:32:15,040 --> 00:32:19,680 but whoever has that has, has got a little bit more, um, yeah, it's got a bunch of, 393 00:32:19,680 --> 00:32:22,640 it would just have like a bunch of people in the repo like anybody else. But yeah. 394 00:32:23,520 --> 00:32:26,160 And I pulled some news out since 395 00:32:30,320 --> 00:32:35,520 26 minutes. So we've got just about enough time to do some news before everybody's 396 00:32:36,400 --> 00:32:40,160 goes to bed. Well, I think we've like only got little D here. So 397 00:32:40,160 --> 00:32:45,760 a little, excuse me, a little, a little D, a little D. Oh, yeah. I don't know where the fuck 398 00:32:45,760 --> 00:32:50,400 everyone else is. It's fucking whizzle. Yeah. Well, it's because they heard you back and we 399 00:32:50,400 --> 00:32:56,720 didn't have a guest. So they thought like last week, last week's episode was like such a like 400 00:32:56,720 --> 00:33:02,160 informative, interesting, nuanced discussion. It was a good discussion. Actually, they were just 401 00:33:02,160 --> 00:33:05,680 like, I think the regular viewers were just like, no, it's just going to come on and like blow off 402 00:33:05,680 --> 00:33:10,880 two weeks worth of steam about hard drives, man. Did you get on the mags afterwards? Yeah. We had a, 403 00:33:10,880 --> 00:33:17,360 we had a talk after the show, like a little chat. Yeah. Nice. Yeah. It's cool. I'm going to catch up 404 00:33:17,360 --> 00:33:27,280 with him soon actually as well and just have a, a conversation about some of the other things that 405 00:33:27,280 --> 00:33:29,200 we're talking about. Cause I thought it was kind of interesting. 406 00:33:29,200 --> 00:33:31,200 Yeah. 407 00:33:33,840 --> 00:33:39,120 I could be Tato in the chat saying, I thought this Aussie guy was the guest. You'd be, you know, 408 00:33:39,920 --> 00:33:48,160 you could think that. We too, we've had Ram Ram before as a guest. Sure. Maybe I've been mistaken 409 00:33:48,160 --> 00:33:55,680 for Ram Ram. That'd be difficult. Yeah. Yeah. Ram is more handsome. Let's see. Thor chain teeters on 410 00:33:55,680 --> 00:34:01,440 the edge of insolvency. Thor chain who just, who, did they buy Kujira? Is that what it was? Was it an 411 00:34:01,440 --> 00:34:04,480 acquisition or was it, it was a salvage, right? Is that what it was? Yeah. 412 00:34:08,000 --> 00:34:12,800 Thor bought out Kujira and now it turns out they themselves are insolvent because they don't 413 00:34:12,800 --> 00:34:20,880 understand the complexities of their own, of their own complicated D5S, right? Yeah. Right. 414 00:34:20,880 --> 00:34:25,040 They've made so many, it's like, you know that scene in the big short where he's just like, 415 00:34:25,040 --> 00:34:29,760 hey, you know what you could also do? You could make a derivative where you bet against yourself 416 00:34:29,760 --> 00:34:32,880 and then you make money off betting against yourself. And the other guy's like, 417 00:34:33,440 --> 00:34:38,320 oh my God, the entire world economy is about to explode. That's in my head. That's what happened 418 00:34:38,320 --> 00:34:42,960 with Thor chain this week. So developer confirmed the vote had gone through and the community has 419 00:34:42,960 --> 00:34:47,040 decided to temporarily pause redemptions as recommended. Founding a vote by node operators, 420 00:34:47,040 --> 00:34:51,760 redemptions for Thor 5 lending and saver products have been temporarily paused. Developer said, 421 00:34:51,760 --> 00:34:55,520 core functionalities remain fully operational, which I don't know what that would be, but whatever. 422 00:34:55,520 --> 00:35:02,240 What's core functionality of a product? Sends. Bank sends remain possible. Everybody is using 423 00:35:02,240 --> 00:35:08,080 liquid staking anyway, but hey, if you've got any liquid tokens left, you can send them to 424 00:35:08,080 --> 00:35:13,280 Kraken and sell them at a massive loss because we've halted the chain. Rune on a slow slide, 425 00:35:13,280 --> 00:35:20,640 it's down 54% in 30 days. And before that was actually somewhat holding on, but what was it 426 00:35:20,640 --> 00:35:26,000 before that? Well, I mean, it's since, let's say, what are we going to look at a year ago? 427 00:35:26,880 --> 00:35:36,000 A year ago, it was at $4.35 bumping up to over 10. And now we're at 212. So it's right now. I mean, 428 00:35:36,000 --> 00:35:41,840 since that, since that, it really, it's been on the slide since middle of December. But since that 429 00:35:42,960 --> 00:35:49,040 tweet, it's been, it's probably down 50% since that tweet. Down a bit. Yeah. Yeah. Which, I mean, 430 00:35:49,040 --> 00:35:55,040 you would think. Yeah. I only realized, you know, when Artifact was talking about this the other day, 431 00:35:55,040 --> 00:36:00,160 I was like, shit, I hold some rune, like not the company, but me personally, I hold some rune from 432 00:36:00,160 --> 00:36:08,160 like many years ago. And I was like, remember it just in time to get rugged. Didn't remember in 433 00:36:08,160 --> 00:36:12,400 time to sell it at the top. Just remembered in time to be like, wait, am I the victim? 434 00:36:12,400 --> 00:36:21,840 Wait, shit. Wait, I'm one of the, wait, I'm one of the plaintiffs. It's actually the podcast 435 00:36:21,840 --> 00:36:27,200 episode title, actually. That feeling when you realize you're a plaintiff too. 436 00:36:28,800 --> 00:36:32,240 You only realize you have the token when you're a plaintiff. So I'm going to the, 437 00:36:33,280 --> 00:36:37,120 yeah, I'm going to say from the sublime to the ridiculous, right? I'm going to the digital 438 00:36:37,120 --> 00:36:44,320 assets forum in London on Monday, which is like, it's basically like a lot of institutional type 439 00:36:44,320 --> 00:36:54,240 shit. I mean, the most tedious panel I've seen on there is navigating crypto assets as a family 440 00:36:54,800 --> 00:36:59,440 wealth fund or a family office or whatever it's cool when, you know, people are zillionaires. 441 00:37:00,240 --> 00:37:04,640 And I was like, oh, that's a panel that I don't give a shit about. Cool. 442 00:37:04,640 --> 00:37:10,560 That's not so fun. Okay. Just like fucking, you know, there's some bits about like the whole 443 00:37:10,560 --> 00:37:16,160 institutional thing where I'm like, if you know, here the use cases number one, and we bring them 444 00:37:16,160 --> 00:37:22,560 into the ecosystems that we're in, otherwise we're fucked. But also like we do and we don't, right? 445 00:37:22,560 --> 00:37:26,880 We can, we can just fucking sell the high seas of stupidity forever, basically. And that's also 446 00:37:26,880 --> 00:37:36,240 fine. Like in my in my cipherpunk heart, I'm kind of like, who cares, you know, on some level about 447 00:37:36,240 --> 00:37:41,760 about, you know, who cares about use cases, who cares about tried fight, you know, maybe it is 448 00:37:41,760 --> 00:37:47,920 cool to just do stupid shit forever and continue doing stupid shit. But yeah, some of the some of 449 00:37:47,920 --> 00:37:53,120 the panels at the event, obviously, if you're going to be at the digital assets forum, and 450 00:37:53,120 --> 00:38:01,040 you're going to go to any of the CBDC or digital cash or stablecoin tracks, you'll see me with a 451 00:38:01,040 --> 00:38:08,160 fucking notepad and my fucking glasses on like a nerd say hey, but I reckon that's probably not 452 00:38:08,160 --> 00:38:16,000 the audience of this podcast in general. But anyway, I was thinking I noticed so relevant to this 453 00:38:16,000 --> 00:38:21,920 podcast, the fucking, I think figment sponsoring and talking on a panel and block demon and that's 454 00:38:21,920 --> 00:38:29,600 like the guys that sponsored, what was it? Cosmos gateway in 22 just went and they double signed 455 00:38:29,600 --> 00:38:36,960 twice the week before. And I was like, these guys are huge. I always forget. I always forget how huge 456 00:38:36,960 --> 00:38:41,200 those guys are until I go to literally any conference. They're like, we're the greatest. I'm 457 00:38:41,200 --> 00:38:48,560 like, what? You're the double sign guys. You guys have the worst 458 00:38:48,560 --> 00:38:56,880 90% of just the double guys. You're the double sign guys. The motto could be like blocks, 459 00:38:56,880 --> 00:39:04,800 colon, you make them, we sign them twice. Or maybe there's just a t-shirt that says signed, 460 00:39:04,800 --> 00:39:11,680 signed, sealed, delivered. I thought, yeah. Yeah, they're huge. There's like, what is that 150 461 00:39:11,680 --> 00:39:16,640 people there or something? Like it's still up there. I think on, yeah, I think on LinkedIn, 462 00:39:16,640 --> 00:39:22,320 even figment is like a hundred or something. Yeah. I guess that's not coming from Cosmos, but 463 00:39:23,600 --> 00:39:29,680 no, it must be coming from, it literally must be Ethereum, right? Because I was talking to somebody 464 00:39:29,680 --> 00:39:34,480 a little while ago about their, I can't remember who it was, but there was an organization in the UK 465 00:39:34,480 --> 00:39:39,760 actually who is a very big validator in terms of like the value of the company. And I was like, 466 00:39:40,400 --> 00:39:44,720 somebody said the valuation, I can't remember what it was. I was like, Christ, that's huge. 467 00:39:44,720 --> 00:39:49,360 Like that's absolutely huge. How can they possibly have that big evaluation as a validator? 468 00:39:50,320 --> 00:39:56,960 And the answer of course was they are in the Ethereum ecosystem. They have like a big load of 469 00:39:58,080 --> 00:40:01,120 liquid state Lido. They were early on that maybe, something like that. 470 00:40:01,120 --> 00:40:05,360 I did it. Yes. I'm not sure how many validators. I can actually take a look though. 471 00:40:05,360 --> 00:40:08,400 Sure. It was like something like that. And I was like, oh, right, that's where the number 472 00:40:08,400 --> 00:40:14,000 comes from. Okay, cool. Whatever. It's like, it's like a completely different world to the 473 00:40:14,000 --> 00:40:21,600 garage rock bands that are validators in other ecosystems. Oh yeah. Like, yeah, full show. 474 00:40:22,160 --> 00:40:25,600 Yeah, I don't even, I couldn't even tell you how many they have there, but yeah. 475 00:40:25,600 --> 00:40:32,560 Somebody else talking to you this week made the joke that on any ecosystem below the top five, 476 00:40:32,560 --> 00:40:38,560 if you see 150 validators, that means that chain is run and primarily used by 150 people. 477 00:40:38,560 --> 00:40:48,000 That's like, probably more like 180. Not too far off. 478 00:40:49,520 --> 00:40:51,360 That's not true. Most of the validators wouldn't use those chains. 479 00:40:52,080 --> 00:40:55,280 Yeah, yeah. Most validators don't use those chains. They just validate. 480 00:40:56,000 --> 00:40:59,440 Yeah. We just make them, we just make them blocks. 481 00:40:59,440 --> 00:41:03,040 We just make them the blocks. What else we had news? 482 00:41:03,040 --> 00:41:09,760 I've definitely been seeing a trend lately of like these new launches happening with less and 483 00:41:09,760 --> 00:41:14,720 less validators, which kind of makes sense. I mean, it's less of a year around these days, right? 484 00:41:14,720 --> 00:41:20,160 I like that, especially if we're in that. Yeah, yeah, especially if we're anointed one. 485 00:41:20,720 --> 00:41:23,360 It would be a lot cooler if we were in any of those sets. 486 00:41:25,600 --> 00:41:29,120 No, they are, I think, which I think is good. I don't know if words get around or what, 487 00:41:29,120 --> 00:41:34,400 but it's good. Start with small. There's no reason, especially Genesis ceremonies are so delicate. 488 00:41:34,960 --> 00:41:40,880 There is no reason to start off with fucking like 150 validators. And then you're like, 489 00:41:41,440 --> 00:41:45,040 actually, all these people are a mouth to feed. Yeah. 490 00:41:45,040 --> 00:41:50,560 Well, also that whole fucking, even like Mars where it was like 10 validators still 491 00:41:50,560 --> 00:41:56,320 managed to get screwed up. Like it's, you know, nothing's a guarantee. And like, yeah, I don't know. 492 00:41:56,320 --> 00:42:00,080 I mean, just people fucking losing keys and shit before, 493 00:42:02,640 --> 00:42:06,480 before, after the Gen-Tex launch and like just stupid shit. 494 00:42:07,040 --> 00:42:11,760 Well, yeah, I mean, even, I think even like some of the remaining big, 495 00:42:11,760 --> 00:42:15,200 big stuff that we've been involved in the past, you look at it now and you're like, well, 496 00:42:16,320 --> 00:42:23,440 yeah, like 100 validates, 150 validators, like you have to get quite a lot of commission 497 00:42:23,440 --> 00:42:31,200 on a regular basis for that, for that to even break even let alone cover all the other costs 498 00:42:32,000 --> 00:42:37,520 and whatnot. And it does start to, yeah, I mean, I guess it's kind of crazy, isn't it? Like the 499 00:42:37,520 --> 00:42:42,240 default in the cosmos quickly behaved like 125. And even then, like even in a bull market, 500 00:42:42,240 --> 00:42:47,600 people were saying, oh, but the bottom tail of the validators aren't even. And it's like, yeah, 501 00:42:47,600 --> 00:42:52,080 exactly. And then now we're here like several years later. And it's like, well, you know, 502 00:42:52,080 --> 00:42:58,160 the top 50 are breaking even. So yeah, we've still got these huge sets. And you know, that was, 503 00:42:58,800 --> 00:43:03,280 I can't remember if it like, yeah, I mean, like other than maybe, do you reckon the 504 00:43:03,280 --> 00:43:06,560 validator at the bottom of the cosmos hub is breaking even? 505 00:43:06,560 --> 00:43:07,840 No fucking way. 506 00:43:07,840 --> 00:43:08,640 I don't think so. 507 00:43:10,160 --> 00:43:14,640 Well, not with the interchange security, but before they would have been, 508 00:43:14,640 --> 00:43:16,800 you run fucking Cosmos on a potato. 509 00:43:16,800 --> 00:43:19,760 I swear at the bottom is like 3000 atom though. 510 00:43:19,760 --> 00:43:22,560 Yeah, yeah, it's it's relatively small. 511 00:43:23,600 --> 00:43:28,800 Nobody's making shit on that. There's no fucking way 3000 atom is like, what is that 18 grand? 512 00:43:28,800 --> 00:43:32,560 Well, yeah, sure. But like, don't shame my validator, man. 513 00:43:35,760 --> 00:43:41,440 2953. Oh, oh, no, wait, that's inactive. My bad. My bad. My bad. Why are they showing? 514 00:43:42,560 --> 00:43:48,400 I was going to say, because like, that's really low. It's got to be like 20, 30, 40, 50 K. At least 515 00:43:48,400 --> 00:43:51,440 this is my calculation. My bad. My bad. It's 105,000. 516 00:43:51,440 --> 00:43:53,440 105,000. 105,000. Yeah. 517 00:43:53,440 --> 00:43:54,560 It's still not breaking even on that. 518 00:43:55,360 --> 00:44:01,120 100. Well, well, no, no's the math, right? 105,000 at 5%. Actually, they're running it. 519 00:44:01,120 --> 00:44:03,520 Oh, I'm sorry. They're excuse me. They're running at 9%. 520 00:44:04,560 --> 00:44:06,480 What is it 105,000? 521 00:44:06,480 --> 00:44:08,000 105,000 atom at 9%. 522 00:44:12,960 --> 00:44:15,280 Where is the parameters? 523 00:44:15,280 --> 00:44:19,520 Let's call it 10%. 10. Min, seven, max, 10. 524 00:44:20,080 --> 00:44:27,200 So that's, well, that's respectable. Would you say 105,000? It's 945,000 a year times. 525 00:44:29,200 --> 00:44:30,560 Oh, hang on. No, it's not. 526 00:44:34,640 --> 00:44:35,280 Point one. 527 00:44:35,280 --> 00:44:37,680 I was going to say that sounded like super optimistic. I was like, 528 00:44:39,200 --> 00:44:40,240 Mr. Zero, man. 529 00:44:40,800 --> 00:44:40,880 Yeah. 530 00:44:40,880 --> 00:44:48,080 Yeah. What's Adam worth a dollar? $5,000 a year. 531 00:44:48,800 --> 00:44:50,720 Yeah. So run it on a hat, Snobox. 532 00:44:50,720 --> 00:44:52,320 $416 bucks. Yeah. 533 00:44:52,320 --> 00:44:56,480 Yeah. Run it on a hat Snobox. You could make a couple of K. 534 00:44:56,480 --> 00:44:59,040 You're making, yeah, you're making $200 a month. 535 00:44:59,040 --> 00:45:01,840 $400 a month. That's fucking, that's all right. 536 00:45:01,840 --> 00:45:04,080 I'm in the top five on some networks and don't make that. 537 00:45:04,080 --> 00:45:10,800 Yeah. I mean, to be fair, that's what we were making when we turned off our validator in the end. 538 00:45:11,360 --> 00:45:16,160 For the bottom slot, that is pretty respectable out of 150 validated. 539 00:45:16,160 --> 00:45:18,160 180 validators. 540 00:45:18,160 --> 00:45:20,400 180 validators. 541 00:45:20,400 --> 00:45:23,040 They're not going to back to like 70. 542 00:45:23,040 --> 00:45:28,000 Yeah. There are plenty of networks in the cosmos where you could be in the top 50, 543 00:45:28,000 --> 00:45:31,840 top 30, top 20 and not make anywhere near that in a year right now. 544 00:45:31,840 --> 00:45:38,320 Yeah. Yeah. I mean, that's a lot of bonds. A lot of, a lot of bonded tokens to be honest. 545 00:45:39,120 --> 00:45:41,600 I mean, the percentages down here are just a waste of time though. 546 00:45:42,560 --> 00:45:43,360 You're really, 547 00:45:43,360 --> 00:45:47,920 A million bonded runs. The inflation is quite hard there. 548 00:45:47,920 --> 00:45:54,640 Yeah. It's.1% stake is at spot 123 out of 180. 549 00:45:54,640 --> 00:46:00,400 So you have basically 60 validators running at.09% or below. 550 00:46:00,400 --> 00:46:02,080 Like it's not worth, it's why. 551 00:46:02,080 --> 00:46:03,280 It's not worth bothering. 552 00:46:03,280 --> 00:46:04,400 It's not worth bothering. 553 00:46:04,400 --> 00:46:08,320 Especially with ICS and stuff. But then, hey, like, you know, with any luck, 554 00:46:08,320 --> 00:46:10,080 ICS is going to get turned off at some point. 555 00:46:10,800 --> 00:46:16,800 So if ICS gets turned off, I think we'd consider running a cosmos validator. 556 00:46:16,800 --> 00:46:19,840 Well, then it'd be pretty hard to back out a fucking ICS. 557 00:46:20,640 --> 00:46:21,840 Wouldn't it go to partial? 558 00:46:21,840 --> 00:46:23,040 Yeah, just go to where we do. 559 00:46:23,840 --> 00:46:27,200 Yeah. Maybe go to partial and then just not like nobody would run it. 560 00:46:27,200 --> 00:46:32,800 Yeah. They would die. It would be like every ICS chair would be like, 561 00:46:32,800 --> 00:46:35,920 Oh, God, no validators. Wait, people need to volunteer. 562 00:46:35,920 --> 00:46:37,360 Wait, that needs to be an incentive. 563 00:46:37,360 --> 00:46:40,720 And then just L5 and Pogachu doing God's work. 564 00:46:40,720 --> 00:46:41,680 Yeah. Basically. 565 00:46:42,960 --> 00:46:44,080 An imperative. 566 00:46:45,520 --> 00:46:51,440 I mean, just yeah, just cosmos getting fucking strangled by ICS is the 567 00:46:52,320 --> 00:46:55,760 absolute non-plot twist that everybody knew was coming. 568 00:46:55,760 --> 00:46:56,000 Yeah. 569 00:46:56,000 --> 00:47:03,200 Yeah. But, you know, I think, no, did you listen back to last week's episode with no 570 00:47:03,200 --> 00:47:04,400 about the future of the cosmos? 571 00:47:04,400 --> 00:47:06,720 I watched last week's episode. 572 00:47:06,720 --> 00:47:08,240 You watched last week's episode. 573 00:47:08,240 --> 00:47:10,000 Made comments to Sir. 574 00:47:10,000 --> 00:47:11,520 Told him to tell you to shut the fuck up. 575 00:47:13,200 --> 00:47:14,480 You say that all the time anyway. 576 00:47:14,480 --> 00:47:15,760 That's not indicative of anything. 577 00:47:16,320 --> 00:47:18,480 You talked about hard drives for 27 minutes. 578 00:47:20,480 --> 00:47:23,280 Look, man, I talk about what's near and dear to my heart, all right? 579 00:47:23,280 --> 00:47:23,600 I know. 580 00:47:23,600 --> 00:47:27,360 I talk about snowmen and little figurines. 581 00:47:27,360 --> 00:47:28,240 I don't mind. 582 00:47:28,240 --> 00:47:29,040 Snowman? 583 00:47:29,040 --> 00:47:29,600 Yeah. I don't know. 584 00:47:29,600 --> 00:47:30,800 It's the first thing that came to mind. 585 00:47:31,360 --> 00:47:32,800 Do you not talk about snowmen all the time? 586 00:47:34,000 --> 00:47:34,240 Shit. 587 00:47:34,240 --> 00:47:35,760 I think you shit about snowmen. 588 00:47:35,760 --> 00:47:38,080 Crosses out note of snowmen. 589 00:47:38,640 --> 00:47:39,600 Care about movies? 590 00:47:40,160 --> 00:47:42,960 Like, we're going to do the movie fucking section. 591 00:47:42,960 --> 00:47:43,760 Watch some movies. 592 00:47:44,320 --> 00:47:47,920 Hey, hey, hey, hey, hey, hey. 593 00:47:48,560 --> 00:47:52,000 You want to hear about the shitest movie I've ever seen? 594 00:47:52,000 --> 00:47:55,040 And I don't know if you've watched this, Sir. 595 00:47:55,040 --> 00:47:56,240 What an intro. 596 00:47:57,440 --> 00:47:57,920 Armour. 597 00:47:59,280 --> 00:48:05,520 Armour is just the shitest movie I have ever seen in my life. 598 00:48:06,080 --> 00:48:08,560 A-R-M-O-R, I think it is. 599 00:48:08,560 --> 00:48:09,520 Oh, I watched that. 600 00:48:09,520 --> 00:48:10,080 Was slide. 601 00:48:10,080 --> 00:48:11,200 Oh, my God. 602 00:48:11,200 --> 00:48:11,920 It was bad. 603 00:48:13,920 --> 00:48:14,720 It's got slide. 604 00:48:14,720 --> 00:48:15,680 What are you talking about? 605 00:48:15,680 --> 00:48:18,720 I know, but like, it was just so fucking bad. 606 00:48:18,720 --> 00:48:21,760 Like, the whole plot was just dumb. 607 00:48:21,760 --> 00:48:24,160 All the fucking physics in it didn't work. 608 00:48:24,160 --> 00:48:25,760 The fucking like. 609 00:48:25,760 --> 00:48:26,720 How dare you? 610 00:48:26,720 --> 00:48:27,680 Oh, man. 611 00:48:27,680 --> 00:48:28,880 How fucking dare you? 612 00:48:28,880 --> 00:48:29,680 Listen. 613 00:48:29,680 --> 00:48:32,720 The special effects was embarrassing. 614 00:48:32,720 --> 00:48:33,600 Listen to me. 615 00:48:33,600 --> 00:48:35,440 Did you see him in that truck? 616 00:48:35,440 --> 00:48:41,200 And the fucking, you could see like a little fucking thing sticking out of the hole with sparks coming off it like a fucking. 617 00:48:41,200 --> 00:48:42,960 Don't fucking disunslide. 618 00:48:42,960 --> 00:48:44,000 Slide was good in that, though. 619 00:48:44,000 --> 00:48:44,640 What? 620 00:48:44,640 --> 00:48:45,280 No, he wasn't. 621 00:48:45,280 --> 00:48:46,320 Why was he even in that? 622 00:48:46,320 --> 00:48:47,200 I don't know. 623 00:48:47,200 --> 00:48:47,840 I don't know. 624 00:48:47,840 --> 00:48:49,040 I have no idea. 625 00:48:49,040 --> 00:48:51,520 Like, slide is like, he's like B grade. 626 00:48:51,520 --> 00:48:53,360 Everyone else in there was like fucking D grade. 627 00:48:54,000 --> 00:48:56,560 It was just such a bad movie. 628 00:48:56,560 --> 00:48:56,880 Okay. 629 00:48:56,880 --> 00:49:04,480 So on Rotten Tomatoes, it has 0% from critics because not a single critic, as far as I can tell, 630 00:49:05,280 --> 00:49:06,400 has watched it. 631 00:49:06,400 --> 00:49:10,000 Anything about it in the Rotten Tomatoes aggregator. 632 00:49:10,000 --> 00:49:12,960 So the needle does not pass 0%. 633 00:49:12,960 --> 00:49:16,080 0% hasn't heard here in the United States. 634 00:49:16,080 --> 00:49:27,200 It's easy to turn over a armored vehicle on a bridge and then to stand outside that vehicle for 12, 14 hours with nobody ever to show up. 635 00:49:28,720 --> 00:49:30,800 No one ever to look at where that vehicle is. 636 00:49:31,360 --> 00:49:32,800 No other cars come by ever. 637 00:49:33,360 --> 00:49:34,160 No police. 638 00:49:34,160 --> 00:49:36,320 Clearly nobody's calling it in to say where is it? 639 00:49:36,800 --> 00:49:37,520 Look, no. 640 00:49:37,520 --> 00:49:38,880 And there's houses right there. 641 00:49:38,880 --> 00:49:39,440 Like they do. 642 00:49:39,440 --> 00:49:42,160 They do these pan shots past these houses all the fucking time. 643 00:49:42,160 --> 00:49:43,680 That happens all the time here. 644 00:49:45,280 --> 00:49:47,680 Let's just paraphrase the plot. 645 00:49:47,680 --> 00:49:53,920 Armored car turns over and then it's all just as it's just a standoff. 646 00:49:53,920 --> 00:49:56,800 Precinct 13 but with an armored car from that point on. 647 00:49:57,920 --> 00:50:03,760 So the whole fucking, yeah, it's like a dad and his son drive this armored car, right? 648 00:50:04,560 --> 00:50:08,320 Dad's got drinking issues and shit from when he was a cop. 649 00:50:08,320 --> 00:50:11,760 And then in the sun like it's just a woozy boy. 650 00:50:11,760 --> 00:50:12,960 I don't know why is there. 651 00:50:12,960 --> 00:50:19,760 And then they were driving, you know, they pick up from this guy every day who's a real dick apparently. 652 00:50:21,120 --> 00:50:25,040 And then they were driving to the, you know, storage point or whatever. 653 00:50:25,760 --> 00:50:35,680 And and Sly and crew who have in separate flash scenes over the past fucking five minutes been loading bullets in the guns. 654 00:50:35,680 --> 00:50:43,840 So then they seemingly just like are running them off the road. 655 00:50:43,840 --> 00:50:52,400 But the the protagonist take all of the right turns to end up at this bridge somehow that 656 00:50:53,280 --> 00:51:00,720 is the choke point to like fucking stop this van with these other two vans, right? 657 00:51:01,280 --> 00:51:05,440 It happens to be just just wide enough to like get this thing in there. 658 00:51:05,440 --> 00:51:12,800 But like they were seemingly taking random turns and it seemed like they were controlling the narrative of where they were going. 659 00:51:13,280 --> 00:51:17,600 But all the while they were being funneled into this bridge somehow. 660 00:51:18,080 --> 00:51:21,680 I mean, it's not like it's particularly well written plotted choreograph. 661 00:51:21,680 --> 00:51:23,920 Oh, no, it's fucking fantastic writing. 662 00:51:24,640 --> 00:51:28,240 And and this bridge is right by these houses. 663 00:51:28,240 --> 00:51:30,080 It's obviously over the top of a river. 664 00:51:30,080 --> 00:51:39,840 It did appear as though the bridge was closed for no particular reason because there was no like inkling of catastrophic damage or like there was no. 665 00:51:40,960 --> 00:51:45,040 It didn't look like it was going to be or was under construction at all. 666 00:51:45,040 --> 00:51:52,400 So why it had these water fill barriers out the front as a closed bridge situation is beyond me. 667 00:51:52,400 --> 00:51:59,440 It seems like it must have been known to be closed because no one was trying to get over the bridge, right? 668 00:51:59,440 --> 00:52:06,960 But no one to I didn't see anyone go back and like put the water barriers back up after they fucking ran through it. 669 00:52:06,960 --> 00:52:11,280 So presumably people know that this bridge is closed and don't bother going there. 670 00:52:11,280 --> 00:52:18,480 What I did find interesting is that when fucking Sly just walked off the bridge at the end there at the end, there was a guy who was just already driving past like. 671 00:52:18,480 --> 00:52:25,440 To get a lift is like, hey, it was like way inside the barrier area. 672 00:52:25,440 --> 00:52:31,440 So I've you know, that doesn't really fit. And then all of a sudden all of the police show up at the end like. 673 00:52:31,440 --> 00:52:35,440 Yeah, like someone call them finally or is that just they knew to come then? 674 00:52:35,440 --> 00:52:38,000 Is that like a prearranged time to just show up? 675 00:52:38,000 --> 00:52:39,440 Like a 12 hour response time. 676 00:52:39,440 --> 00:52:40,400 Yeah. 677 00:52:40,400 --> 00:52:44,400 How long did it take in heat for the police to show up in the armored car scene? 678 00:52:44,400 --> 00:52:46,400 It's like two minutes something like that. 679 00:52:46,400 --> 00:52:47,440 They have to get the stingers out. 680 00:52:47,440 --> 00:52:49,440 Don't they to stop the police cars? 681 00:52:49,440 --> 00:52:55,440 There were just so many fucking plot holes. It was absolutely ridiculous. 682 00:52:55,440 --> 00:52:57,440 Sounds like. 683 00:52:57,440 --> 00:53:01,440 And then even like the way that the truck was slowly filling up when it was in the river. 684 00:53:01,440 --> 00:53:03,440 Oh, yeah, that was going on here, man. 685 00:53:03,440 --> 00:53:09,440 It's like was it like something sticking up in the middle of the river that the truck was like stuck on? 686 00:53:09,440 --> 00:53:11,440 Did you see that? 687 00:53:11,440 --> 00:53:13,440 I don't remember. 688 00:53:13,440 --> 00:53:15,440 And that's why it was like slowly filling through the hatch. 689 00:53:15,440 --> 00:53:17,440 And then all of a sudden it after it's fucking. 690 00:53:17,440 --> 00:53:19,440 Yeah, it's fucking. 691 00:53:19,440 --> 00:53:21,440 35% rotten tomatoes. 692 00:53:21,440 --> 00:53:23,440 35% can't be wrong. 693 00:53:23,440 --> 00:53:25,440 I'm telling you. 694 00:53:25,440 --> 00:53:27,440 35% audience, 0% critics. 695 00:53:27,440 --> 00:53:33,440 35% of people didn't fucking bash their head against the wall until they died. 696 00:53:33,440 --> 00:53:35,440 Yeah. 697 00:53:35,440 --> 00:53:37,440 So anyway, needless to say, I quite enjoyed it. 698 00:53:37,440 --> 00:53:39,440 Yeah, it's not bad. 699 00:53:39,440 --> 00:53:41,440 Good back. 700 00:53:41,440 --> 00:53:43,440 Which is was he son? 701 00:53:43,440 --> 00:53:45,440 Yeah, good work movie. 702 00:53:45,440 --> 00:53:49,440 They didn't do anything with the with the alcoholism piece. 703 00:53:49,440 --> 00:53:51,440 Yeah, they did. 704 00:53:51,440 --> 00:53:55,440 Yeah, because he ended up using his fucking thermos as a fucking Molotov cocktail. 705 00:53:55,440 --> 00:53:59,440 Oh, and to end a fucking disinfect of made leg. 706 00:53:59,440 --> 00:54:03,440 Look, we're not breaking any block points is fucking stupid movie. 707 00:54:03,440 --> 00:54:05,440 No one's going to watch it. 708 00:54:05,440 --> 00:54:07,440 Yeah, so fucking dumb. 709 00:54:07,440 --> 00:54:14,440 But yeah, that was the whole point of that fucking out baking in the algorithm and hold hiding the fucking vodka. 710 00:54:14,440 --> 00:54:18,440 And his thermos was just so they could like make a Molotov. 711 00:54:18,440 --> 00:54:20,440 How how these how they're going to defend you? 712 00:54:20,440 --> 00:54:22,440 I know they'll make a Molotov cocktail. 713 00:54:22,440 --> 00:54:24,440 Where are they going to have alcohol from? 714 00:54:24,440 --> 00:54:26,440 I don't know. We'll make the guy alcoholic. 715 00:54:26,440 --> 00:54:28,440 There you go. 716 00:54:28,440 --> 00:54:30,440 Genius. 717 00:54:30,440 --> 00:54:32,440 Genius time for another beer. 718 00:54:32,440 --> 00:54:34,440 Let's go. 719 00:54:34,440 --> 00:54:38,440 They obviously wrote this at the bar after fucking three bottles of whiskey. 720 00:54:38,440 --> 00:54:40,440 It's pretty good. 721 00:54:40,440 --> 00:54:42,440 Yeah. 722 00:54:42,440 --> 00:54:52,440 And I just love that there's a plastic hatch on top, but they're drilling a hole through the fucking door. 723 00:54:52,440 --> 00:55:00,440 It gets just comes flooding in like, you know, in a closed area, like it just comes. 724 00:55:00,440 --> 00:55:02,440 See this thing. 725 00:55:02,440 --> 00:55:06,440 Have you noticed that on the theatric poster in the middle, there's a little bit of text. 726 00:55:06,440 --> 00:55:10,440 And if you zoom in, it says on the bridge of death. 727 00:55:10,440 --> 00:55:18,440 It's like, oh my God, I think this film is money laundering in some way. 728 00:55:18,440 --> 00:55:20,440 I can't put my finger on it. 729 00:55:20,440 --> 00:55:22,440 Don't knock it. It's good stuff. 730 00:55:22,440 --> 00:55:36,440 But it has it has that kind of whatever it's called, you know, Guy Hans films that never really got released or got released in one cinema, just that they could then be used for tax evasion purposes like the lobster man film. 731 00:55:36,440 --> 00:55:38,440 Listen to me. 732 00:55:38,440 --> 00:55:44,440 And yet, but we seem to find him all the time. 733 00:55:44,440 --> 00:55:50,440 The that TV show that he does isn't too bad. The Tulsa one Tulsa King is great. Yeah, I enjoy it. 734 00:55:50,440 --> 00:55:52,440 Yeah, it's good. 735 00:55:52,440 --> 00:55:56,440 I really like that fucking oil one that recent one land man. Yeah. 736 00:55:56,440 --> 00:56:02,440 Landman is good. That just finished right. I think episode 10 is the last. Yeah, man. I'm so fucking devastated. 737 00:56:02,440 --> 00:56:04,440 I didn't actually watch 10 yet. So don't fuck it up. 738 00:56:04,440 --> 00:56:12,440 Fuck in man. He's so good for that role. Fuck in that. What's his name? Billy Bob. Yeah, Billy Bob Thornton. He's so good in that role. 739 00:56:12,440 --> 00:56:15,440 So you know what? You know what is good? 740 00:56:15,440 --> 00:56:20,440 So they conclave. If you get a chance to fucking see that film. 741 00:56:20,440 --> 00:56:22,440 So right in the cinema, can't leave yet. 742 00:56:22,440 --> 00:56:40,440 Sorry, in the cinema of all fucking places and it is great.