1 00:00:00,000 --> 00:00:03,520 There's some, there's like Matt Berry's one of those people, there's always just so much random 2 00:00:03,520 --> 00:00:07,360 shit like on the internet where you just find a Matt Berry skit and you're like, 3 00:00:07,360 --> 00:00:11,840 this is fucking great. Just very versatile comedic actor in my opinion. Oh wait. 4 00:00:15,440 --> 00:00:21,040 Welcome to Game of Nodes, a weekly podcast from independent Validator teams. 5 00:00:21,040 --> 00:00:29,760 Hello and welcome to Game of Nodes, a weekly podcast from independent Validator teams. 6 00:00:30,320 --> 00:00:38,880 And we're at the beginning of a new format where we are going to, we haven't actually 7 00:00:38,880 --> 00:00:45,360 worked out the new format bit that we're going to do next. But I did make a ticker, so I'm going to 8 00:00:45,360 --> 00:00:55,360 I go to Bravely just roll the ticker. It's very, very important and 9 00:00:57,440 --> 00:01:03,120 no, we don't, we don't have anything prepared for that. 10 00:01:04,960 --> 00:01:08,240 Well, we screwed it up already. So those of you listening back from podcast players, 11 00:01:08,240 --> 00:01:14,480 which I gather is the larger part of our audience. There is a very poor quality ticker 12 00:01:14,480 --> 00:01:21,440 scrolling along the bottom of the screen right now. It is a news corner. However, it's like, 13 00:01:21,440 --> 00:01:23,840 I don't know if that's the name we agreed on on the by the way. It's 14 00:01:26,000 --> 00:01:32,320 you know what happens when we kind of vaguely agree a concept in the Game of Nodes Dow, which 15 00:01:32,320 --> 00:01:38,560 is definitely a Dow, is that we just, you know, whoever does it first gets to claim the former. 16 00:01:38,560 --> 00:01:44,960 That's what happens. You snoozed, you snoozed, you snoozed past tense and 17 00:01:46,160 --> 00:01:52,640 thou lost is what happened there. So no, do you want to take us through the news of the week then? 18 00:01:52,640 --> 00:01:58,560 I don't have any, no. I've got nothing prepared whatsoever for this. 19 00:01:58,560 --> 00:02:00,800 We're talking about this at least 24 hours ago. 20 00:02:00,800 --> 00:02:05,600 Well, you're putting me on the spot and now I can't even think what happened. I don't know. 21 00:02:05,600 --> 00:02:09,520 It's like fucking yesterday was Thursday anyway. I can throw in one for you. 22 00:02:10,320 --> 00:02:15,440 Yeah. How about the Kauzar Stream Swap? Kauzar has been mainnet for, got a month now and then 23 00:02:15,440 --> 00:02:23,920 you just had a stream. Kauzar. Man, you guys hit me hard with that. Kauzar was in Stream Swap 24 00:02:23,920 --> 00:02:34,080 yesterday, two days ago. And so interestingly, so I believe that the price that it ended up being 25 00:02:34,080 --> 00:02:41,200 was significantly below like an order of multiples below the presale price. Is that right, Chelsea? 26 00:02:41,200 --> 00:02:44,560 Yeah, something like that. I mean, I think there's a couple cool points to it, right? 27 00:02:44,560 --> 00:02:47,760 One, Stream Swap is being used because I don't think we've ever talked to that on stream. 28 00:02:48,720 --> 00:02:54,160 And two, the token is actually available now, which probably means inflation is coming here 29 00:02:54,160 --> 00:03:00,960 soon. And three, it's way lower price than expected. And that I think is after there was 30 00:03:00,960 --> 00:03:10,640 a bump in price right at the end. So what then did the actual market cap end up being? 31 00:03:11,680 --> 00:03:15,360 Is it like ultra low or were they shooting for something ultra high? 32 00:03:16,560 --> 00:03:21,280 What is it? Like 11 to 12 cents was the presale price or something like that? Don't quote me. 33 00:03:21,280 --> 00:03:26,880 But did that indicate like a much higher? Were they shooting for a couple of hundred million 34 00:03:26,880 --> 00:03:33,680 or are they shooting for like 20 to 50 million? Because here we go. Entry point 2.5 million. 35 00:03:33,680 --> 00:03:40,960 Ask what? I say let's let's pull Bendy or Rahman have them explain it because I kind of know what's 36 00:03:40,960 --> 00:03:44,880 going on, but it sounds like they really know what's going on. And he's already embarrassed for us. 37 00:03:45,920 --> 00:03:52,000 Yeah, it's down there telling us how it is. Is there any other news then? I mean, 38 00:03:52,000 --> 00:03:58,000 we sort of haven't really talked too much about what this news is going to be and look like anyway. 39 00:03:58,000 --> 00:04:00,960 We said, will we do news? Yes. But like, 40 00:04:00,960 --> 00:04:05,760 There's a ticker on the screen. It's a very key important component of this. 41 00:04:05,760 --> 00:04:12,480 Very key. Very key. But are we going to focus on like ecosystem news or are we going to focus on 42 00:04:12,480 --> 00:04:18,400 like, Validator news? Like, oh, all the validators come and listen to us because they want to get 43 00:04:18,400 --> 00:04:23,360 the gossip on like what the new test nets coming up are and that type of stuff. 44 00:04:23,360 --> 00:04:30,800 Well, I think one of the crucial things that I think we are agreeing to change is not working out 45 00:04:30,800 --> 00:04:37,680 the format on air. Well, you put them in a position to do it. I mean, it's worth the discussion. 46 00:04:37,680 --> 00:04:43,280 Well, this is game of notes, right? And if you weren't prepared to get rug pulled at the beginning 47 00:04:43,280 --> 00:04:49,920 of this show with what we agreed about 72 hours ago, then it does beg the question of what you 48 00:04:49,920 --> 00:04:57,600 expected after 69 episodes that the essential format of this show being that rug pulling the 49 00:04:57,600 --> 00:05:02,960 other participants is the name of the game. I was kind of expecting like more local news. 50 00:05:02,960 --> 00:05:06,720 Last time he brought up this coffee shop or something, right? This time I was expecting, 51 00:05:06,720 --> 00:05:09,600 you know, something about July 4th to be talked about. But I guess you're on a story. 52 00:05:09,600 --> 00:05:13,600 Coffee shops would be more your wheelhouse when you're on the West Coast. 53 00:05:14,400 --> 00:05:17,440 It would, absolutely. But isn't that what he brought up like two weeks ago? He was like, 54 00:05:17,440 --> 00:05:20,880 I have news to share. And then he like read out for local article. 55 00:05:20,880 --> 00:05:24,720 I thought it was like a fight in a deep market car park or something. 56 00:05:24,720 --> 00:05:28,160 There it was. Yeah, a supermarket. Yeah, a supermarket. That's right. 57 00:05:28,160 --> 00:05:34,240 It's like your classic situation. I feel like somebody told me some news about 58 00:05:34,240 --> 00:05:40,080 about either Melbourne or Sydney the other day, but it's gone. So I can't do local Australian news, 59 00:05:40,080 --> 00:05:44,640 unfortunately. What can we do? What's happened in England recently? 60 00:05:44,640 --> 00:05:49,600 So that country's shop, I think the country continues to earn. That's really it. 61 00:05:49,600 --> 00:05:53,200 Yeah. You guys just had happy, happy freedom day. 62 00:05:54,800 --> 00:06:00,080 Happy freedom day. Yes, we did. Yes, we did. Down the British. 63 00:06:00,080 --> 00:06:05,200 Yeah. So on the group chat, we had the conversation that the Americans blow up a bunch of fireworks 64 00:06:05,200 --> 00:06:08,880 and sometimes some fingers once a year to celebrate the removal of the monarchy. 65 00:06:10,080 --> 00:06:15,520 Because we're very enlightened in the United Kingdom, we do the same to celebrate the continued 66 00:06:15,520 --> 00:06:21,040 subjugation of ourselves by the monarchy and also occasionally lose some fingers and some skin. 67 00:06:21,840 --> 00:06:23,360 Different strokes for different folks, I guess. 68 00:06:23,360 --> 00:06:31,360 Yeah. So my friends and I once filled a pinata with petrol in a large balloon 69 00:06:31,920 --> 00:06:36,480 and then just poked a little bit of the balloon out through the hole in the pinata. 70 00:06:36,480 --> 00:06:42,240 There's one at the top, one at the bottom. And then you basically flick lighter to hit that 71 00:06:42,240 --> 00:06:45,040 little gap where you've got the bit of protruding balloon. Obviously, the light just 72 00:06:45,040 --> 00:06:47,600 burns straight through that balloon and the whole thing. Great. 73 00:06:47,600 --> 00:06:49,760 What are we talking about? Thank you. 74 00:06:49,760 --> 00:06:55,040 Thank you. Blowing up a pinata that's filled with petrol on Guy Fawkes night. 75 00:06:56,320 --> 00:07:00,800 So it looks like, what the fuck is Guy Fawkes night? Is it like the fifth of November? 76 00:07:00,800 --> 00:07:02,480 Is that your number? Remember the fifth of November? 77 00:07:02,480 --> 00:07:03,600 Yeah, I remember. 78 00:07:03,600 --> 00:07:07,680 I remember the plot. I know of no reason the gunpowder treason should ever be forgot. 79 00:07:10,240 --> 00:07:16,800 So it was Guy Fawkes. He put a bunch of dynamite, I believe, under parliament and went to go blow 80 00:07:16,800 --> 00:07:21,200 it up and would have been successful if it weren't for that sneak in moisture. He got down there, 81 00:07:21,200 --> 00:07:26,800 he went to blow it and he didn't like water seal the barrels of gunpowder. 82 00:07:26,800 --> 00:07:28,720 I thought it was discovered by a porter. 83 00:07:30,240 --> 00:07:35,360 Was it? Maybe, but I'm fairly certain he actually made it down there. I thought it was 84 00:07:35,360 --> 00:07:38,160 like a moisture issue. So it was just like the classic case of gunpowder. 85 00:07:38,160 --> 00:07:39,760 Are we thinking of beef and vendetta here? 86 00:07:39,760 --> 00:07:44,800 Yeah. No, no, wait, that's an underground trade. No, no, ignore me. 87 00:07:48,240 --> 00:07:51,760 So it very much sounds like you're saying Guy Fawkes. 88 00:07:55,120 --> 00:07:59,120 And that may be, but we're talking about real events here. 89 00:07:59,840 --> 00:08:04,080 So since we've been talking about it, I'm looking at the StreamSwap price for 90 00:08:04,080 --> 00:08:13,440 Quasar and Osmo. I know. And just since 2100, it's gone from, 91 00:08:14,560 --> 00:08:22,880 Quasar was 0.064 Osmo to now 0.135 Osmo. It's doubled since we've discussed it. So we're moving 92 00:08:22,880 --> 00:08:27,680 the needle right here, just in the last five minutes. But I don't even know if this 93 00:08:27,680 --> 00:08:30,480 graph makes any sense. But anyway, it's pretty funny. 94 00:08:30,480 --> 00:08:33,360 I'm not sure if I can handle that level of responsibility. 95 00:08:33,360 --> 00:08:41,040 Is this, after it's complete, how does this thing chart anything? Is it just, 96 00:08:41,040 --> 00:08:44,880 I guess, it's off the liquidity pool? Is that what's going on here? Bring that back? 97 00:08:47,360 --> 00:08:53,600 Yeah, but anyway. That is a pager duty notification I've ever heard one. 98 00:08:55,600 --> 00:09:00,560 It's been live on stream this morning. Yeah. What's going up? 99 00:09:00,560 --> 00:09:08,320 Are you having some issues? No, just that I ran out of space this morning on one of my 100 00:09:10,320 --> 00:09:18,320 boxes with the SAID testnet on it. And I'm trying to state sync it. So that's like an ordeal. 101 00:09:18,320 --> 00:09:22,080 Yeah. And what on Atlantic? Yeah, Atlantic too. It's just, 102 00:09:23,360 --> 00:09:28,320 shit, I had to go back like 100,000 blocks just to get the fucking thing to work. 103 00:09:28,320 --> 00:09:31,840 Yeah. I don't know if they've, I mean, we talked about last week, I don't know if they make a 104 00:09:31,840 --> 00:09:36,720 change or anything else with that. Cause I think they definitely recognized it was a problem, 105 00:09:36,720 --> 00:09:42,160 right? Which is pretty good. At least in terms of the snapshots not being complete and everything 106 00:09:42,160 --> 00:09:46,880 else like that. So the story is that basically on that testnet that chain moves so quick with 107 00:09:46,880 --> 00:09:51,200 400 millisecond blocks and there's so much Oracle data and all these other types of things 108 00:09:51,200 --> 00:09:57,360 that we're identifying that on a node is set to create snapshots every 10,000 blocks or something 109 00:09:57,360 --> 00:10:01,920 similar to that, that it would take upwards of five or six hours to create a snapshot. 110 00:10:01,920 --> 00:10:06,160 And so most of the times that would fail or the next snapshot would try to kick off and then 111 00:10:06,160 --> 00:10:12,000 we'd get into a bunch of issues. And so when you have five or six hours, I think it was like 50, 112 00:10:12,000 --> 00:10:15,680 like four, I think, didn't you calculate it's like 45,000 blocks is five hours or something like 113 00:10:15,680 --> 00:10:21,360 that. But basically it was taking 50,000 blocks to create a snapshot. So if you're not, so you 114 00:10:21,360 --> 00:10:26,000 have to ask for a snapshot that's at least 50,000 back to hope that one node has it somewhere in 115 00:10:26,000 --> 00:10:32,640 the swarm, basically is what was happening. Which is this like this, it will, it will fill the gap. 116 00:10:32,640 --> 00:10:39,280 Like if you have the trusted height like way up closer to the head, that's fine, except when it 117 00:10:39,280 --> 00:10:48,160 has to verify all the blocks between. Yeah. And it'll, it'll like do that against, you know, 118 00:10:49,120 --> 00:10:54,240 some, it'll just pick nodes to do that against, right. And then if they don't have the light block 119 00:10:54,240 --> 00:10:58,800 in between, then it just shits the bed and you have to start again. So, right. Yeah. So you 120 00:10:58,800 --> 00:11:03,440 want to get like a snapshot as close as possible to like your trust height. Yeah. 121 00:11:04,000 --> 00:11:07,280 Yeah. And it was, I think no matter what, I don't even know if that's even true because 122 00:11:07,280 --> 00:11:12,160 anytime I pick a node, it would use the same node, it would probably get like 10 or 15 or maybe, 123 00:11:12,160 --> 00:11:15,200 I don't even know actually, maybe five, 600 blocks and eventually it would fail. 124 00:11:15,200 --> 00:11:18,800 Light block would not be, would be incorrect or something else. So it was always like, 125 00:11:18,800 --> 00:11:22,960 it always ran for like 30 seconds and it would always shit the bed, right? It was always about 126 00:11:22,960 --> 00:11:28,240 the same, same amount of structure back. I think, I think that might be like some sort of rate 127 00:11:28,240 --> 00:11:34,080 limiting thing that does that. Yeah. Well, it was even happening on my own nodes. So, so 128 00:11:34,880 --> 00:11:37,840 actually, was that true? I don't even know if it was, it was happening on my own nodes, 129 00:11:37,840 --> 00:11:42,000 but I'm not sure it was going to a swarm. So I'm not even sure what was doing there. But yeah, 130 00:11:42,880 --> 00:11:45,920 but it seemed like it was more of an error or maybe the node was throwing an error because 131 00:11:45,920 --> 00:11:50,080 it was in the middle of a snapshot creation or something. Good. I don't know. There's something 132 00:11:50,080 --> 00:11:55,760 goofy. In any case, just go way back in history and wait five hours for your node to sync. 133 00:11:56,640 --> 00:12:02,000 Yeah. Right. Yeah, at least took a long time. Yeah. But I like to say that it's really, 134 00:12:02,000 --> 00:12:11,280 it really is a real say specific or Atlantic to specific issue. Yeah. Ends probably have more, 135 00:12:11,280 --> 00:12:15,280 but it most doesn't even work still does it? I don't know. I can't, I can't stay 136 00:12:15,280 --> 00:12:20,000 syncing a node. I know that I know it's literally impossible for me to stay syncing a node. So I'm 137 00:12:20,000 --> 00:12:26,160 reliant on community snapshots or snapshotting myself or just making the drive bigger, which is 138 00:12:26,160 --> 00:12:31,600 what I've been doing lately. Like I'm fine. Making the drive bigger is the real, that's the real 139 00:12:31,600 --> 00:12:37,040 40 chess move. It is, right? You know, the universe brain, it's like, plan ahead of time, 140 00:12:37,600 --> 00:12:42,720 bunch of other things, use AWS and research, use the fucking biggest. I think that machine, 141 00:12:42,720 --> 00:12:48,400 you know, the machine only has like a half a terabyte on it and the snapshots 384 gigs or 142 00:12:48,400 --> 00:12:52,560 something. So what the fuck am I doing? Let's just make it, let's make it twice as big. Exactly. 143 00:12:52,560 --> 00:12:57,680 I'm going to waste my time. E plugging in a bigger physical desk as well. No, this is, 144 00:12:57,680 --> 00:13:01,200 this is all cloud. It's just, actually it's just removing other chains from it from the same, 145 00:13:01,760 --> 00:13:06,720 from the same brings the, bring this, brings the briefcase drive plugs it in. 146 00:13:06,720 --> 00:13:13,360 That would be the, that would definitely be like the universe brain move is to literally just 147 00:13:13,920 --> 00:13:19,120 like get an even bigger drive, plug it in and then just lazily like put it on top of the rack. 148 00:13:19,120 --> 00:13:23,200 Just like stack up Western digital USB drive. Yeah, exactly. Like really shit. 149 00:13:25,360 --> 00:13:29,760 Exactly. They even rack properly. Just like, just, just plunk it on top and be like, 150 00:13:29,760 --> 00:13:33,920 balance it on and then just fuck off for lunch. That's just like, good for another 151 00:13:33,920 --> 00:13:37,440 just have bundles of them actually just hanging from their chaos. 152 00:13:39,200 --> 00:13:45,760 Just one giant. You'd be surprised how long that is. I worked in an office once where there was 153 00:13:45,760 --> 00:13:50,960 like a shared like airport where it's called that time machine. Like, you know, back in the day, 154 00:13:50,960 --> 00:13:57,360 the Apple used to do the swanky back up the shit nas. It was like the Apple nas. That was, 155 00:13:57,360 --> 00:14:02,480 oh yeah, yeah, yeah. Yeah. Time machine. It would always work. And you could back up like 156 00:14:02,480 --> 00:14:06,160 multiple machines at all the work machines that were owned by the company backed up there. 157 00:14:07,120 --> 00:14:11,440 Like everybody just had this like gentleman's agreement, like put your work work in like the 158 00:14:11,440 --> 00:14:17,840 projects folder or whatever in route. And it'll back up just that bit. Just configure your time 159 00:14:17,840 --> 00:14:23,680 machine. So it's not backing up your dick pics or whatever and just back up that whatever it is, 160 00:14:23,680 --> 00:14:26,560 people put on their hard drives. I don't know what you guys are. Whatever. 161 00:14:26,560 --> 00:14:37,200 And yeah, and the anyway, like it was just automatically synced. And then like, 162 00:14:37,200 --> 00:14:40,720 just one day, like, you know, you kind of root in and there was like this. It was, 163 00:14:41,360 --> 00:14:44,720 I can't remember if it was in a secret room. There was definitely a secret room in the office 164 00:14:44,720 --> 00:14:48,480 where there was like a bookcase. And then behind the bookcase was a meeting room. I can't remember 165 00:14:48,480 --> 00:14:53,680 if it was in there or whether it was just in the corner with a bunch of other like network 166 00:14:53,680 --> 00:14:58,320 bits and pieces like router and stuff. But it fell like, you know, one of those things where 167 00:14:58,320 --> 00:15:02,480 you're just like, oh, where is the thing? And then, yeah, literally just found it hanging by its USB 168 00:15:02,480 --> 00:15:07,680 cable from like a windowsill or something. And you're like, I wonder how many months that's just 169 00:15:07,680 --> 00:15:10,880 been because I guess that period as well, I probably would have been spinning disk too. 170 00:15:11,440 --> 00:15:16,480 Just like gently swinging realize that it seems to work whatever man. 171 00:15:17,040 --> 00:15:23,440 Just an LVM volume group with hundreds of 5400 RPM Western Digital USB drives plugged in. 172 00:15:23,440 --> 00:15:28,880 I think that works. I mean, is that any real deal? I mean, like, okay, it is a bit different, 173 00:15:28,880 --> 00:15:34,640 but it's not like that conceptually different from a massive like compute cluster of Raspberry 174 00:15:34,640 --> 00:15:41,920 Pies, is it? Like consumer hardware or least it's like leashing lots of tiny little dojos to a massive 175 00:15:41,920 --> 00:15:46,640 truck, isn't it? Sure. Oh, to pull the truck, not pulling the dojos. 176 00:15:48,240 --> 00:15:51,680 That is normally how sled dog teams work. Yes. Pulling the dojos. 177 00:15:51,680 --> 00:15:57,280 Look, man, all I heard was it's like tying a whole heap of dogs to a truck and driving along. 178 00:16:00,800 --> 00:16:04,560 I mean, I can go one of two ways. Are we done with nulls? 179 00:16:04,560 --> 00:16:08,240 As an engineer, if I was a good artist, I would go away and make that make, 180 00:16:08,240 --> 00:16:12,320 make, just do a, do an artist's rendition of what, what has just been described because I 181 00:16:12,320 --> 00:16:17,120 think that's the two options though. The two options. Ah, does anybody have a homework assignment? 182 00:16:17,120 --> 00:16:24,320 If anybody has like mid-journey credits or whatever, if somebody could get a massive 18-wheeler 183 00:16:24,320 --> 00:16:30,240 truck being pulled by a sled team of dojos, I would be much obliged to you. That would be great. 184 00:16:30,800 --> 00:16:34,320 That sounds like a task for Rama. I don't understand the answer. 185 00:16:34,320 --> 00:16:41,680 I know for a fact, Rama's got a subscription. So, yeah, it's kind of landing on Rama. 186 00:16:41,680 --> 00:16:49,360 Just saying. Okay. Okay. So, somebody mentioned, did Archway also launch? 187 00:16:50,400 --> 00:16:58,480 It did. Yes. Yeah, it absolutely did. I mean, I don't give a shit. I massively long Juno and, 188 00:17:03,600 --> 00:17:08,800 I have also massively long Juno. But we do have some, we do have some friends of ours working, 189 00:17:08,800 --> 00:17:14,800 working on Archway. Like, doesn't Sporthy, Spoo work on Archway? 190 00:17:14,800 --> 00:17:15,280 Really? 191 00:17:15,280 --> 00:17:22,320 Look at the ears perk up. He fucking degens. Look at their all type of emails right now. 192 00:17:22,320 --> 00:17:23,440 Hey, what's the set look like? 193 00:17:23,440 --> 00:17:24,800 I'm checking who's in discord right now. 194 00:17:24,800 --> 00:17:27,040 He's on the set. Hey, what's going on? 195 00:17:29,040 --> 00:17:35,280 Fucking validator degens. As soon as you hear one, one general purpose fucking wasm chain is enough 196 00:17:35,280 --> 00:17:41,360 for me. I mean, the thing is right, like a rising tide lifts all boats, except they're just like 197 00:17:41,360 --> 00:17:48,400 a fucking wasm chain, which case rising tide don't do shit, get off my lawn. That's what I'm saying. 198 00:17:48,400 --> 00:17:50,800 On behalf of the Juno community, I don't speak for it. 199 00:17:50,800 --> 00:17:53,280 So we don't need 75 permissionless wasm chains? 200 00:17:53,840 --> 00:18:00,480 Whoa, hold up. Ben Davis says, is she Sporthy trying to capture the value she creates? 201 00:18:00,480 --> 00:18:07,440 Maybe there's more value in Spoo being there than what there is in a wasm chain. 202 00:18:08,880 --> 00:18:12,400 I mean, that's not untrue though, because Spoo is a good developer. 203 00:18:12,400 --> 00:18:13,120 Yeah, exactly. 204 00:18:17,680 --> 00:18:18,880 It's that little twist, right? 205 00:18:22,400 --> 00:18:27,360 Question is really, if we're going to launch, if we're talking about general purpose wasm 206 00:18:27,360 --> 00:18:31,840 chains, why don't we just, we've already got the domain. Why don't we just launch big balls 207 00:18:31,840 --> 00:18:35,520 blockchain? Might as well. Like commissionless wasm? 208 00:18:35,520 --> 00:18:39,120 People are like, what is the biggest balls blockchain? 209 00:18:39,680 --> 00:18:44,640 Chiwa wasm. With the biggest balls, surely the big balls blockchain. 210 00:18:44,640 --> 00:18:50,960 I mean, yeah, with an open validator form with no limits, a faucet you can spam the shit out of, 211 00:18:50,960 --> 00:18:55,760 huge inflation, right? And then. Yeah, so Chihuahua. 212 00:18:55,760 --> 00:18:57,760 Yeah, exactly. Exactly. 213 00:19:01,120 --> 00:19:05,680 Then you earn points for meaningless things, like how fast your auto compounds for runs and 214 00:19:05,680 --> 00:19:08,800 shit, like things like that. I mean, do you think it's not literally how real life works? 215 00:19:08,800 --> 00:19:10,560 Yeah. Yeah, that's true. I guess we have that one. 216 00:19:10,560 --> 00:19:13,440 Yeah, I was going to say, like if the spamming the auto cobb powder is literally 217 00:19:13,440 --> 00:19:17,600 everybody does every time a chain hits Genesis. It's a good point we have in our 218 00:19:17,600 --> 00:19:20,960 area. God damn. So you said you've just. I'd love to see someone. 219 00:19:20,960 --> 00:19:29,120 Watch. I have. I'd love to see someone raise and then try to market a chain with just one validator. 220 00:19:29,120 --> 00:19:31,360 Isn't that a noble? I was going to say, isn't that Dave? 221 00:19:34,800 --> 00:19:38,720 I mean, is that different than what currently happens though? Most networks start with like 222 00:19:38,720 --> 00:19:43,360 all the team tokens delegated to validators and they're like, this is so decentralized right now. 223 00:19:43,920 --> 00:19:48,080 And really, they would just control it. So is there a difference? 224 00:19:48,080 --> 00:19:51,520 No, no, not really. No. It's just a distribution. Yeah. 225 00:19:51,520 --> 00:19:55,920 The things we don't own or tokens we don't own. That was immediately evident to me, like 226 00:19:56,480 --> 00:20:02,320 when I sort of started validating in them, like these foundations, you speak of how many tokens 227 00:20:02,320 --> 00:20:06,160 do they have? They're like, oh, you know, they hold like 70% of the treasury. I'm like, 228 00:20:07,360 --> 00:20:12,720 but they don't. But it seems like a lot. It's very important to be clear that they're not a 229 00:20:12,720 --> 00:20:17,280 security and they don't hold that security and they control that security. They just control 230 00:20:18,960 --> 00:20:24,560 60 to 70% of the. Everything else. No big deal. Like it's very decentralized now. It's very. 231 00:20:26,080 --> 00:20:34,240 So I'm like, so even though it's decentralized, everything can be decided by the foundation. 232 00:20:34,880 --> 00:20:37,840 Correct. Yeah. Okay. All right. Yeah. 233 00:20:37,840 --> 00:20:44,480 Well, it's okay because the community pool has like 0.1% of all the tokens. So, you know, 234 00:20:44,480 --> 00:20:49,280 it's like give and take. Exactly. Like the community gives and then the foundation takes. 235 00:20:49,280 --> 00:20:59,120 It's really straightforward, actually. It's just like, you know, 40% good, 80% better. 236 00:20:59,680 --> 00:21:05,360 It's just, it's very complicated how this decentralization works, right? It's very, 237 00:21:05,360 --> 00:21:11,440 it's very important that, you know, you look at like Amazon, right? Very centralized, very 238 00:21:11,440 --> 00:21:18,400 centralized, but foundation very decentralized, you know, because, you know, foundation, they only 239 00:21:18,400 --> 00:21:24,720 own like 70% of effectively the value of their product, whereas like, you know, Amazon, you know, 240 00:21:26,000 --> 00:21:31,360 they probably have like way more than 70% of the shares in Amazon. Oh, wait. Hey, wait, 241 00:21:31,360 --> 00:21:36,480 who owns the Amazon shares? Hold on a second. Wait, is it publicly traded? Jeff, he only got 16%. 242 00:21:37,440 --> 00:21:42,160 How would he, how can I second, no, but no, but decentralization you serve, but don't be breaking 243 00:21:42,160 --> 00:21:47,040 my, okay, now I need to Google how much, I'm going to Google some numbers on Amazon. I'll be back. 244 00:21:47,040 --> 00:21:51,760 He's got, he's, he has 17%, is that right? Something like that. Wow. 245 00:21:51,760 --> 00:21:58,160 You're telling me that Mr. Amazon, 16% of you own 16% of Amazon, Mr. Jeff Amazon. Jeff Amazon, 246 00:21:58,160 --> 00:22:02,720 I think owns 16%, which is pretty amazing at this point. I mean, the company's what, decade 247 00:22:02,720 --> 00:22:06,560 old or more and amount of money that they raised and all everything else. But I mean, that's, 248 00:22:06,560 --> 00:22:11,440 it's a good number. He would have had to sell off a fair bit of it to begin with working capital. 249 00:22:11,440 --> 00:22:17,920 Like, public, I mean, public comes out of, I mean, the primary comes out of, okay, John, 250 00:22:17,920 --> 00:22:23,440 John Amazon owns 9.7% of the company. Oh, really? It's even down. It used to, 251 00:22:23,440 --> 00:22:28,160 it used to be like 16 and a half, I think back in, maybe it was like, five years ago or five years 252 00:22:28,160 --> 00:22:33,440 ago or something like that. Like raises probably dilute their holding. Oh yeah, for sure. And like, 253 00:22:33,440 --> 00:22:39,600 you know, these people aren't like rich to begin with. So they don't have like all of the money 254 00:22:39,600 --> 00:22:47,760 in their suitcase that they can just buy into the, the raises to like stop themselves getting 255 00:22:47,760 --> 00:22:53,600 diluted. So like, you know, that's part of the business model for people who are, what companies 256 00:22:53,600 --> 00:22:58,800 that are like developing is they sell their own tokens and dilute themselves to get capital to 257 00:22:58,800 --> 00:23:08,720 make their shit worth more money. So yeah. So if you're a company, can you buy your own stock? 258 00:23:08,720 --> 00:23:13,200 Because that would be like the original circle steak. Buyback. Buybacks. Yeah, buyback. 259 00:23:13,200 --> 00:23:17,440 That's what you're doing. Yeah. Yeah, they were legalized in the 80s. Oh my God, there's literally 260 00:23:17,440 --> 00:23:23,200 nothing new under the sun. Even circle staking is just securities. Crawled? Is it securities 261 00:23:23,200 --> 00:23:28,800 fraud? No, it's just legal. I don't think it's like comparable. I don't think it's comparable. 262 00:23:28,800 --> 00:23:35,280 But if you own, but if you own 40% of your shares, you'll get 40% of the dividend, right? If you 263 00:23:35,280 --> 00:23:41,360 award a dividend. Yeah, I think so. That's how it fucking works. It's a circle steak. 264 00:23:41,360 --> 00:23:46,720 Yeah, I don't know how you're relating this to buying back tokens though. Sorry, 265 00:23:46,720 --> 00:23:48,240 you're not tokens. Security. 266 00:23:50,080 --> 00:23:53,760 So thanks. New merch coming next week on Game of Nades. 267 00:23:54,320 --> 00:23:59,680 Yeah, I would probably wear a t-shirt that said circle steak just because it's so unclear what it 268 00:23:59,680 --> 00:24:07,280 means. If you get it, you are one of the elite people. And if you don't get it, that's cool. 269 00:24:07,280 --> 00:24:16,320 How would you visualize it? Would you have a bunch of community members standing in a circle 270 00:24:16,320 --> 00:24:23,040 sort of handing them each other tokens down real low? You do it like the supreme logo and it would 271 00:24:23,040 --> 00:24:27,920 just say circle steak. No, no, no, no. You would need like, do you remember in second grade how you 272 00:24:27,920 --> 00:24:34,480 had the evolution of a frog from a catab pole, from an egg to a tadpole to a frog to create 273 00:24:34,480 --> 00:24:38,720 tag poles? It'd be like that, but different stages of circle staking where it all just kind of leads 274 00:24:38,720 --> 00:24:45,920 into a circle. That's what I would do. I would have the same thing, but the end of it, just not 275 00:24:45,920 --> 00:24:54,960 joining the circle and being the foundation wallet. There you go. Actually, I guess I don't really know 276 00:24:54,960 --> 00:25:00,160 if the buyback, for some reason in my head, I always thought that they weren't buying back and 277 00:25:00,160 --> 00:25:04,080 holding that they were buying back and destroying those shares, meaning like they're basically 278 00:25:04,080 --> 00:25:08,560 taking them out of circulation completely, but maybe that's wrong. I talk about in like normal 279 00:25:09,680 --> 00:25:14,880 arrow. Yeah, yeah. So what they do is they buy them back and then delist them and destroy them. 280 00:25:14,880 --> 00:25:20,880 So the amount of shares becomes less. Yeah. Okay. So the point of that is sometimes 281 00:25:22,240 --> 00:25:29,040 they're buying burn. They're burning their tokens. They're literally taking the available supply away. 282 00:25:29,040 --> 00:25:33,280 That's correct. Yeah, so they're burning those tokens. That's an awful way of saying that, 283 00:25:33,280 --> 00:25:37,920 but yeah, that's exactly what's happening. Yeah. So what happens is, let's say, 284 00:25:39,440 --> 00:25:49,840 Johnny Big Bull's company has five shopping malls, right? And the real estate price has gone up many, 285 00:25:49,840 --> 00:25:54,720 many multiples and they want to like take some risk off the table. They might sell one of those 286 00:25:54,720 --> 00:26:00,800 shopping centers, right? And end up with a shit ton of cash. And maybe at the time, there's like no 287 00:26:00,800 --> 00:26:08,960 really good opportunities to be able to like deploy that cash and then be able to make a good 288 00:26:08,960 --> 00:26:15,520 return on it. So the board of directors might say, well, maybe we'll just return some of this capital. 289 00:26:15,520 --> 00:26:19,120 They can either do like a capital return to the shareholders or they're like, we want to 290 00:26:19,120 --> 00:26:25,520 fucking pump our share price instead. So they just like slowly buy back on market shares and then 291 00:26:25,520 --> 00:26:30,640 eventually just burn them. Right. Right. Okay. Now, now there's less shares, company's still worth, 292 00:26:31,440 --> 00:26:36,080 same money. So wait, you know all this stuff about business now, and yet you're still a 293 00:26:36,080 --> 00:26:46,640 Cosmos father, right? It's probably a lot about like, you're a cop. You fucking narc man. Are you the 294 00:26:46,640 --> 00:26:56,800 SAC? Fucking narc man. It's very illegal though. Bybox in the US used to be very, very illegal. 295 00:26:56,800 --> 00:27:02,000 They weren't very illegal. Very illegal. I know it's also like heavily frowned upon by some 296 00:27:02,960 --> 00:27:06,720 people and like others. Like I never thought of as being a negative actually, I thought they're 297 00:27:06,720 --> 00:27:11,280 just taking shares out of the circulation. If you take those out, then hopefully no different than 298 00:27:11,280 --> 00:27:16,720 a burn is that there's less available supply. So therefore you're hopefully blah, blah, blah, blah. 299 00:27:16,720 --> 00:27:20,320 Because I know like, I mean, like what Apple's doing right now, I mean, they're doing 300 00:27:20,320 --> 00:27:24,640 what hundreds, like tons of billions, right? I forget what they did 200 billion last year or 301 00:27:24,640 --> 00:27:28,880 something like that. They're buying back something like that. Yeah, Apple buys like huge. 302 00:27:28,880 --> 00:27:36,480 Billion billion billion massive numbers. Apple has shitloads of cash. It can't get rid of it. 303 00:27:36,480 --> 00:27:44,160 There's a big difference between like the Australian companies and the US companies in that 304 00:27:44,160 --> 00:27:49,520 there's like a double taxation thing in the States. I'm not 100% sure how it works, but like 305 00:27:49,520 --> 00:27:58,160 basically the company gets taxed and then you get taxed when you, so if they pay a dividend. 306 00:27:58,160 --> 00:28:02,160 So the company gets taxed to begin with and then if they pay a dividend, then like the holders get 307 00:28:02,160 --> 00:28:09,520 taxed. I think it's like a double tax situation there. So the UK as well, why would it the company 308 00:28:09,520 --> 00:28:13,760 pays corporation tax and then people who get a dividend have to pay tax like this. 309 00:28:14,560 --> 00:28:20,400 Right. Okay. So how it works in Australia is the company pays company tax, right? 310 00:28:20,400 --> 00:28:26,160 Corporate tax and then they they in exchange for paying that tax get what's called 311 00:28:26,160 --> 00:28:34,160 um uh franking credits uh and franking credits are basically like something you have on the company 312 00:28:34,160 --> 00:28:41,920 ledger that accumulate and then when you pay a dividend to the shareholders, you can pay with it 313 00:28:41,920 --> 00:28:49,760 franking credits and it's as good as cash. Like if you receive um a dividend and franking credits 314 00:28:49,760 --> 00:28:56,160 but have and say it's like it's 30% right. So say say you get uh oh it's normally about 30%. So say you 315 00:28:56,160 --> 00:29:03,680 get like $2,000 dividend and just for argument's sake $1,000 um of franking credits right and you 316 00:29:03,680 --> 00:29:08,960 know the money that year then you would be in the tax-free threshold right. So when you do your tax 317 00:29:08,960 --> 00:29:19,520 return just shut the fuck up. The doctor who created the the credits was called franking 318 00:29:19,520 --> 00:29:25,440 credits but the the credits themselves were called the creature. Thank you. I've been trying to like 319 00:29:25,440 --> 00:29:31,760 roll up a joke with that for a little while. I appreciate it. It's a boomer joke. The two people 320 00:29:31,760 --> 00:29:38,880 that read books here we're together on this one. That was worth interrupting, Dull4. Anyhow. Totally. 321 00:29:41,040 --> 00:29:46,560 So say you won't know the um income that year you'd be in the tax-free threshold or under the 322 00:29:46,560 --> 00:29:51,760 tax-free threshold. So you could then do a tax return and you would get that $1,000 worth of 323 00:29:52,320 --> 00:29:59,200 franking credits back as cash right. So the the companies give the the tax they've paid or credits 324 00:29:59,200 --> 00:30:04,160 for the tax that they've paid back to the shareholders. So it's quite common like basically 325 00:30:04,160 --> 00:30:10,000 all of the companies that earn money here pay dividends like 80%. And that franking think that's 326 00:30:10,000 --> 00:30:15,520 a global term or that's an Australian term? Well I don't think they have it in the States. 327 00:30:15,520 --> 00:30:21,120 Oh they don't. Okay. I got you. I was confused because usually Australian term would be like 328 00:30:21,120 --> 00:30:24,240 you call it a Frankie or something like you have to put something on there a little while. 329 00:30:25,920 --> 00:30:29,600 I got my dividends this month with a bag full of Frankies. 330 00:30:31,520 --> 00:30:38,400 Exactly. So on the on the Apple side so far I think they have bought back about $375 billion 331 00:30:38,400 --> 00:30:46,000 worth of stuff. $573 billion in the last decade. Yeah and then this year now they're ramping 332 00:30:46,000 --> 00:30:51,600 it up to $90 billion a year that they're buying back. Whoever it was that said we need we need like 333 00:30:51,600 --> 00:31:00,400 the um what's it called uh thumbnail for YouTube that's my actual reaction $573 billion. 334 00:31:00,400 --> 00:31:09,280 That'd be like the uh the Home Alone kid. That's right. Yes. You were talking about creating some 335 00:31:09,280 --> 00:31:15,360 good faces for YouTube. Have you seen the the film about the beginnings of black metal 336 00:31:16,320 --> 00:31:22,560 Lords of Chaos with his brother in it? It's really good. That's a Game of Nose film recommend. 337 00:31:22,560 --> 00:31:26,880 Okay. What do you have to do with stock buyback? I don't put my name on that recommendation so 338 00:31:26,880 --> 00:31:30,800 it can't we can't say it's a full Game of Nose recommendation. Okay. I'm recommending. I don't 339 00:31:30,800 --> 00:31:35,440 watch anything. The film Lords of Chaos. I believe it's called Lords of Chaos. Lords of Chaos. 340 00:31:35,440 --> 00:31:41,040 About an hour and a half long. It's not super long. It's it's quite snappy, breezes over some stuff, 341 00:31:41,040 --> 00:31:45,040 captures the fact that they were kind of neo-nazis, doesn't really kind of duck the really 342 00:31:45,040 --> 00:31:48,000 problematic things about the beginnings of the black metal scene that they were really 343 00:31:48,000 --> 00:31:58,640 fucking horrible people. It's entertaining film. So she'll see a veil in other news. A veil testnet. 344 00:32:00,320 --> 00:32:07,200 So people they're expanding their their testnet and some more people are getting into it. So I 345 00:32:07,200 --> 00:32:12,400 believe you are there. I am there. I don't know about any of these other chumps. Have you looked 346 00:32:12,400 --> 00:32:18,800 at the like have you spent much time on that Explorer like Kate dot a veil dot tools? No, 347 00:32:18,800 --> 00:32:25,120 I look at it right now. I dig it. The terminology in some of the things is great. Like the 348 00:32:28,000 --> 00:32:34,400 the thing that shows you like your staked amounts, the tab that shows you staked amounts is called 349 00:32:34,400 --> 00:32:43,680 bags. And it's just like all these other random little Easter eggs in here. It's great. Is this 350 00:32:44,240 --> 00:32:48,720 this is a new L one. Is that right? Is it an Easter egg? If it's just like one click away on a tab? 351 00:32:49,360 --> 00:32:55,840 Well, I guess it's not an Easter egg. It depends if your heart wants it to be an Easter egg or 352 00:32:55,840 --> 00:33:00,800 not. If you only happen to see it and think it's precious, that's an Easter egg. It's precious. 353 00:33:00,800 --> 00:33:08,800 That is the most short thing I've heard all week. That's right. So this is 354 00:33:09,680 --> 00:33:14,560 it was so interesting getting like starting the the validator of this network like I'm so cosmos 355 00:33:14,560 --> 00:33:21,840 that everything else is baffling to me. And I was just like, firstly, how the fuck do I build this 356 00:33:21,840 --> 00:33:26,880 thing? Because I had library issues, right? Because I don't know what the hell they built the 357 00:33:26,880 --> 00:33:35,280 binaries on that they distribute. But there's like an issue after Ubuntu 14, where certain libraries 358 00:33:35,280 --> 00:33:41,280 just aren't in the same spot. Oh, the SSL libraries like the Lib C and everything. Yeah, exactly. 359 00:33:43,520 --> 00:33:47,440 So you had to build it because whatever they built it on is either different or like the 360 00:33:47,440 --> 00:33:53,200 libraries are in a different spot. So yeah, I had to build it. I don't build rust on anything like 361 00:33:53,200 --> 00:34:04,080 I've never built rust. I didn't build rust. Big, big go guy. I see sir has no fucking taste. 362 00:34:06,400 --> 00:34:10,720 Were you impressed? Where the fuck is this binary going? And why isn't there a path to it? 363 00:34:11,200 --> 00:34:16,720 So yeah, anyway, I set up my go paths, but this rust binary hasn't appeared on them. 364 00:34:16,720 --> 00:34:23,040 Yeah, I mean, but like I set up some, I'm sure in the setup of the rust seed, there was like 365 00:34:23,040 --> 00:34:27,840 some path shit that went on there anyway. So there's like, there's a cargo. Yeah, exactly. 366 00:34:27,840 --> 00:34:33,520 I'm not sure. Right. That's an actual good package manager and build system. 367 00:34:34,400 --> 00:34:40,320 Well, it doesn't fucking work. I think the problem problem exists between keyboard and chair, my 368 00:34:40,320 --> 00:34:47,120 good man. It's the same. You have to add the path in there. You gotta refresh the shell, 369 00:34:47,120 --> 00:34:52,880 all that same shit. Did you enjoy the rust build process that was massively multi parallel and 370 00:34:53,440 --> 00:34:55,760 pretty text going by and all that kind of thing. Did you like that? 371 00:34:56,560 --> 00:35:00,240 I enjoyed discovering that I was missing dependencies like right towards the end and 372 00:35:00,240 --> 00:35:05,120 then having to redo the process five fucking times. Oh yeah, there must be, there must be a 373 00:35:05,120 --> 00:35:09,440 there must be a shell script that's running to do that because I don't think you wouldn't be 374 00:35:09,440 --> 00:35:14,400 missing it if the rust thing actually started out. I'll think. Yeah. It would probably be like, 375 00:35:14,400 --> 00:35:19,760 yo, this thing's a little bit fucked. And hey, by the way, your problem is on line 200 of this file. 376 00:35:20,320 --> 00:35:23,760 And people would pop up and have nothing to say about it. 377 00:35:24,320 --> 00:35:28,720 Is what you say. Here's what you really meant. And while you're looking into that problem, 378 00:35:28,720 --> 00:35:36,080 how about I go fix you a drink? That's the rust compiler, not clippy. Clippy is a fucking son 379 00:35:36,080 --> 00:35:43,040 of a bitch. The rust compiler is a total scumbag. But the problem is we've all been naughty, 380 00:35:43,040 --> 00:35:47,040 null. We've all been bad at one time or another. And that's why clippy is there. 381 00:35:47,920 --> 00:35:51,840 Although I realized that you might now mean Microsoft clippy and you might not be aware 382 00:35:51,840 --> 00:35:57,120 that there's a rust tool called clippy that everybody uses, which berates you for being a bad 383 00:35:57,120 --> 00:36:04,720 programmer. Here's what I'll say about rust. I went through the rust book, the rust book online. 384 00:36:04,720 --> 00:36:08,960 And by the end of it, I mess my message to my buddy and I was like, Hey, rust is a beautiful 385 00:36:08,960 --> 00:36:13,760 language. I enjoy every second of working with it. And then the first part I do after I like 386 00:36:13,760 --> 00:36:17,200 learn new language, I try and like write data structures that I know, like linked lists kind 387 00:36:17,200 --> 00:36:22,240 of deal. I tried to do that in rust. And after like three hours, I was like, this is the dumbest 388 00:36:22,240 --> 00:36:29,600 language. And rust is so difficult to create data structures. Like it's not it just the way it 389 00:36:29,600 --> 00:36:35,600 handles different settings. It just it's outrageous. And I stepped away and haven't really, it's outrageous. 390 00:36:38,720 --> 00:36:43,520 Has even strong opinions about certain things. So what you're trying to do, it would just be 391 00:36:43,520 --> 00:36:48,080 like literally, my guy, this is built in, it's called an iterator, you just write an iterator. 392 00:36:48,080 --> 00:36:52,960 That's basically, don't worry, pretty little head about those like list, you don't need it anymore. 393 00:36:52,960 --> 00:36:57,520 It's still gonna be okay. That's what it did though. Like so I ended up looking around online 394 00:36:57,520 --> 00:37:01,120 because I was like, there's no way I'm just this dumb. And there's like all sorts of articles 395 00:37:01,120 --> 00:37:05,280 online about people like writing linked lists and rest and being like, oh my god, it's so 396 00:37:05,280 --> 00:37:08,320 difficult. There's even one where the guys like, all right, so I know you guys want to write a 397 00:37:08,320 --> 00:37:13,120 linked list. Here's six ways you can do it and how each way is more difficult and scary than the last. 398 00:37:13,760 --> 00:37:17,920 So really, I just try to tackle a difficult problem in rust, but it's a cool language, 399 00:37:17,920 --> 00:37:25,040 but I'm still afraid of it after that experience. I mean, yeah, it's like anything else. It's pretty 400 00:37:25,040 --> 00:37:32,640 cool. But you know, do it the way the rust compiler wants you to. And don't piss off Clippy. That's 401 00:37:32,640 --> 00:37:38,480 how one clippy don't piss off Clippy. So what is this? I think it did find very entertaining. 402 00:37:40,080 --> 00:37:46,160 Literally just go to get on GitHub and do like a search of commits that say something like fuck 403 00:37:46,160 --> 00:37:52,480 Clippy or appease Clippy or please Clippy. In fact, please Clippy is a good one. I know there's a few 404 00:37:52,480 --> 00:38:01,120 of my commits in there that are just like, please God Clippy, please. 2am by the phrase to clippy. 405 00:38:01,120 --> 00:38:08,080 So one thing that I did find great was that when you're compiling, it'll like it'll throw codes. 406 00:38:08,080 --> 00:38:17,360 It's like, oh, this hasn't worked because of like error, a d fucking 752, but shut the fuck up, 407 00:38:17,360 --> 00:38:23,200 Alex. Oh, the fray. I know you're about to interrupt me because you're a fucking rust guru 408 00:38:23,200 --> 00:38:30,080 and you want to mansplain it to me. But that's about some, but I found it great that it's like, 409 00:38:30,080 --> 00:38:34,720 look, we kind of understand that this is just a code and you've got no fucking idea what this 410 00:38:34,720 --> 00:38:40,560 means. So just type in mansplain this code number into the little rust guy and we'll tell you all 411 00:38:40,560 --> 00:38:46,240 about it. So I found that handy. Yeah, I like how this all stems from you not knowing that 412 00:38:46,240 --> 00:38:54,000 binary is going to the target directory. Yeah, you spoiled. You spoiled with go. I mean, with go, 413 00:38:54,000 --> 00:39:00,160 they just always go in the bin, right? It's fucking. Yeah, but you don't actually want them to go in 414 00:39:00,160 --> 00:39:04,960 the bin most of the time. You want them to go somewhere in your working directory so you can 415 00:39:04,960 --> 00:39:10,880 then decide what to do with them later. And it goes to the general build directory, right? 416 00:39:10,880 --> 00:39:15,680 It doesn't actually for go. If you do go build it, build it inside the directory. However, 417 00:39:15,680 --> 00:39:20,320 if we do make install, it goes build and working directory. Yeah, I mean, to be fair, actually, 418 00:39:20,320 --> 00:39:23,760 that's actually more of a function of the make file that's usually bundled with literally 419 00:39:23,760 --> 00:39:28,960 all Cosmos chains and it's really nothing to do with go. But I'm laying at the door of go because 420 00:39:28,960 --> 00:39:33,600 everything wrong with the world. I didn't get so much sleep the other night, right? Even though I 421 00:39:33,600 --> 00:39:39,520 had no excuse and I really I went to bed early. The baby wasn't here for reasons are unimportant. 422 00:39:39,520 --> 00:39:45,200 So I had a perfect run at it. And yet I could get to sleep properly. Fuck in 12 30 at night, 423 00:39:45,200 --> 00:39:52,000 I'm like, go. And then at 5 15 in the morning, I wake up, I'll get back to sleep. I'm like, 424 00:39:52,000 --> 00:40:08,080 fucking go lang. So in other news, end of financial year in Australia. 425 00:40:08,080 --> 00:40:16,880 So 30. Yeah. Super exciting. Also, also the time of year where you are totally text. 426 00:40:17,520 --> 00:40:20,640 Also the time of year where you add up how much money you lost for the year and want to kill 427 00:40:20,640 --> 00:40:28,080 yourself. So is that is the number closer to one or one million Kanga bucks? 428 00:40:28,080 --> 00:40:39,120 It's between us. It begins with a fucking minus sign. So this is where somebody who's 429 00:40:39,120 --> 00:40:44,640 smarter at maths could probably make a joke. But as I'm on the ledger, it has brackets around it. 430 00:40:44,640 --> 00:40:54,240 It's like, it's like $1 million brackets, which is a loss and not $1 million. Which is a formal 431 00:40:54,240 --> 00:40:59,520 interview type thing situation for something last week. Not really important. What? But I had to 432 00:40:59,520 --> 00:41:06,480 do that. What are your weaknesses? I was like, fucking maths, 100% just linear algebra, all of it. 433 00:41:06,480 --> 00:41:11,680 Just I'm not great at maths, but I can usually figure out something. And they're like, well, 434 00:41:11,680 --> 00:41:18,480 obviously maths is going to be a very key part. I went in way too hard on the be honest about your 435 00:41:18,480 --> 00:41:23,840 week. This is there. And I instantly regret it. You should have gone to matrix mathematics. 436 00:41:23,840 --> 00:41:29,840 Been like, you know what, graphical interfaces, I can't do matrix transpositions. I just can't do 437 00:41:29,840 --> 00:41:34,400 it. They'd be like, okay, whatever. I feel like that was a math joke for somebody that 438 00:41:34,400 --> 00:41:40,320 understands maths. Exactly what I need to bring. Exactly what we're talking about here. 439 00:41:42,320 --> 00:41:48,400 That's one of those linear algebra type things that I type into the funny website with the brackets 440 00:41:48,400 --> 00:41:54,480 that it works out for me, isn't it? Matrices are one of those incredibly powerful mathematical 441 00:41:54,480 --> 00:41:58,880 tools that you hate to learn and then love to fucking forget 40 seconds after you do the exam. 442 00:42:00,000 --> 00:42:04,480 Yeah, that's basically my experience as well. I remember being like, this is some dark magic. 443 00:42:04,480 --> 00:42:10,480 I wasn't supposed to know this. Yeah, like, whoa, I don't want to be on the Illuminati's list. Let's 444 00:42:10,480 --> 00:42:17,680 fucking forget all about this. I feel like that is, that is when I first found out about multi-dimensional. 445 00:42:17,680 --> 00:42:24,400 When I first found out about data cubes, that was my, I was like, you're not supposed to know this. 446 00:42:25,200 --> 00:42:30,480 This is two multi-dimensional data sets when you have several measure properties and you're like, 447 00:42:31,120 --> 00:42:37,440 oh my god. But then I think, I don't know shit about how to use Excel, right? But I'm pretty sure 448 00:42:38,080 --> 00:42:43,680 that having a multi-dimensional data set with multiple measure properties that all intersect 449 00:42:43,680 --> 00:42:50,320 in like a literally a multi-dimensional way. Like if you were to, I guess, is this geometry? 450 00:42:50,320 --> 00:42:56,960 Is this geometry? It would be a multi-dimensional, it'll be a hypercube, right? But you're finding a 451 00:42:56,960 --> 00:43:03,280 point within the hypercube. I think that's geometry, right? That discipline of maths, 452 00:43:03,280 --> 00:43:11,280 is it? Maybe? Yeah, sure. Yeah. But how all of that relates just, yeah, that's pretty fucking cool. 453 00:43:11,280 --> 00:43:16,000 Also, fucking vectors. I've been using them in programming for ages and I've actually only worked 454 00:43:16,000 --> 00:43:21,680 out maybe in the last six months. I was like, hold on a fucking second. Hold on a fucking second. 455 00:43:22,240 --> 00:43:29,360 Use vector like an array of data, but hold on. Wait a minute. Hold on a second. Just like a 456 00:43:29,360 --> 00:43:37,680 hypercube is just geometric coordinates. I think this is just geometric coordinates. The one I feel 457 00:43:37,680 --> 00:43:41,600 like, I think the day I work this out, I'm going to actually have a heart attack and die. That's 458 00:43:41,600 --> 00:43:50,080 going to be my final day on this earth. I gather that when you have a monad, when you lift something 459 00:43:50,080 --> 00:43:56,960 into a monadic context in pure functional programming languages, I gather, I think, 460 00:43:56,960 --> 00:44:05,120 I believe that the lift of a non, that kind of lift operation, I think, has a geometric, 461 00:44:05,120 --> 00:44:11,040 it can be represented as a geometric, like spatial transformation. It's something like 462 00:44:11,040 --> 00:44:15,840 there's a sphere involved and you're transposing the position of it or something like that, 463 00:44:15,840 --> 00:44:19,680 but I don't understand it at the moment. So I could have completely misrepresented that. 464 00:44:19,680 --> 00:44:24,960 And I feel like that's one of those things where I've so dimly understood it that if I ever do 465 00:44:24,960 --> 00:44:27,920 understand it, I will die. I will just have a heart attack and I will be dead. 466 00:44:27,920 --> 00:44:34,560 That could be how you become Dr. The Fray by following that train of thought way too deep. 467 00:44:35,280 --> 00:44:39,520 But isn't that like what Dykstra, no, that's what Simon Peyton Jones did. That's why he has 468 00:44:39,520 --> 00:44:42,800 the crazy eyes. He does have supervillain eyes. Who? 469 00:44:43,680 --> 00:44:48,400 Simon Peyton Jones, SPGA. Just saying it again to answer the question. 470 00:44:52,080 --> 00:44:54,160 I should have prefaced that. Allow me to reiterate. 471 00:44:54,160 --> 00:44:59,120 The real truth of the week for this week is just Simon Peyton Jones. There you go. 472 00:44:59,920 --> 00:45:02,800 I have to look it up. Like you didn't tell me or no, you're just going to say it again. 473 00:45:02,800 --> 00:45:07,760 He's, you know, the guy with the face. Yeah, the face. He's the guy. You know, he's just a guy. 474 00:45:09,040 --> 00:45:12,160 Oh, this guy. I find his eyes and then you'll know. 475 00:45:12,800 --> 00:45:19,040 All right. I know this guy's. Oh, in other valerator related news, well, actually network 476 00:45:19,040 --> 00:45:23,920 related news. Yeah. Sorry, I keep coming up with these things like, you know, while you guys is 477 00:45:23,920 --> 00:45:27,840 dribbling shit. Don't put me in that fucking statement. Go ahead. 478 00:45:28,560 --> 00:45:34,640 I mean, like there's still only one item on the fucking spreadsheet and it says started at time zero. 479 00:45:35,200 --> 00:45:46,800 Dribble. And it's still coming out. It's still coming out. So the DYDX public test net is 480 00:45:46,800 --> 00:45:52,960 live like the app. Yeah. Not not being a validator, but the app is live. So 481 00:45:54,240 --> 00:45:57,600 people can now use it. It looks pretty fucking slick, to be honest. 482 00:45:57,600 --> 00:46:01,520 Test net four, which looks like it's basically the same UI, right? There's nothing different about that. 483 00:46:02,960 --> 00:46:07,440 I mean, it's the same functionality. It's just the different structure for the actual transaction piece. 484 00:46:08,160 --> 00:46:11,440 Yeah. So the back ends different. The front ends should look pretty much the same. 485 00:46:11,440 --> 00:46:16,640 Yeah. But the, but the Oracle prices, I mean, the obviously the site moves. I was on the 486 00:46:16,640 --> 00:46:20,800 side a little bit. I used it a little bit today, but the site's moving very fast. And it's clearly 487 00:46:20,800 --> 00:46:26,240 moving faster than the block speed. So the block speed is about 1.9 seconds, right? And yeah, the 488 00:46:27,440 --> 00:46:32,880 so there must be some sort of middle. Yes, there must be. Right. So that's that's just the transactions. 489 00:46:32,880 --> 00:46:37,280 Right. I assume the transactions and those types of things have to have to happen at block speed. 490 00:46:37,280 --> 00:46:42,560 But clearly it's getting Oracle data faster. Right. It's clearly it's updating like every, 491 00:46:42,560 --> 00:46:46,800 I don't know, couple hundred milliseconds, right? It's like, it's extremely responsive. So how 492 00:46:46,800 --> 00:46:53,120 does that work? That's a good question. And also, like, are the are the orders going straight in at 493 00:46:53,120 --> 00:46:58,800 a rate of like two milliseconds or are they getting cached somewhere in like middleware or 494 00:46:59,440 --> 00:47:02,880 like, yeah, like, when does it end up on chain? I guess is the question, right? Is that maybe, 495 00:47:02,880 --> 00:47:07,600 maybe when it's when it's finalized, like after the funds have been processed and we have 496 00:47:08,160 --> 00:47:12,160 closure on the on the when the orders complete or something or I don't know. I don't know how 497 00:47:12,160 --> 00:47:15,760 that any of that works. But I thought it was interesting that because I was really curious 498 00:47:15,760 --> 00:47:19,600 on what the block time was going to be because obviously, with other tools like say that are 499 00:47:19,600 --> 00:47:25,280 driving that down trying to do whatever and we're driving, you know, all these Oracle data every 300 500 00:47:25,280 --> 00:47:29,120 millisecond block. And then I look at this and say, how is this working at two second block 501 00:47:29,120 --> 00:47:34,400 times when I'm still seeing Oracle data that's flying past? Or not just Oracle data, I just mean 502 00:47:34,400 --> 00:47:38,160 like that the speed of the interface is very fast. The book, the book speed, that's a good way of 503 00:47:38,160 --> 00:47:44,160 saying it. Yeah, the book is like the orders in the book are changing quite rapidly for a block 504 00:47:44,160 --> 00:47:48,800 speed of two seconds. Yeah. So how does that? So that's the question like, how does that actually 505 00:47:48,800 --> 00:47:52,640 work? I guess it had to, I mean, when it was, what was it before? It was on Ethereum, right? 506 00:47:52,640 --> 00:47:58,800 So what it was? Or what was the idea? Or it was a L, I think the point wasn't the point was that it 507 00:47:58,800 --> 00:48:04,880 was an L one, so L two on top of Ethereum. So it was ultimately having to persist them down into 508 00:48:04,880 --> 00:48:10,560 Ethereum, but was presumably doing its own caching thing. So maybe the, maybe the what you're seeing, 509 00:48:10,560 --> 00:48:16,080 the speed is there. Yeah, maybe the same, the same thing is happening where they've kept the same L 510 00:48:16,080 --> 00:48:22,640 two hot cache, whatever it is to do all that. But they've just essentially got a quicker L one 511 00:48:22,640 --> 00:48:28,160 underneath it, which is what they're planning on doing. And cheaper L one, right? Because whatever 512 00:48:28,160 --> 00:48:32,400 they're, whatever, yeah, I don't want to share what the number of transactions and the gas cost 513 00:48:32,400 --> 00:48:37,440 and all that stuff up. I'm guessing they're spinning up some kind of shit coin to support it, right? 514 00:48:37,440 --> 00:48:41,600 Yes. Well, there is a, yeah, there's a DYDX token, is there not? 515 00:48:41,600 --> 00:48:45,760 Was that already in Ethereum? Are they just going to pull over the, the DYDX token? 516 00:48:45,760 --> 00:48:49,760 Damn question. Good question. I would imagine they would migrate it. Yeah. 517 00:48:49,760 --> 00:48:54,400 I feel like this is again, we're, we're on Rama's law and Rama's not happy. That's, 518 00:48:54,400 --> 00:48:56,320 that's how I feel when we get into these kind of conversations. 519 00:48:56,320 --> 00:48:59,600 It's a buck. Do you need to do that? It's a, it's a token. It's a buck. 520 00:48:59,600 --> 00:49:02,720 200, 300, 300 million dollar market cap. Yeah. So 521 00:49:03,920 --> 00:49:09,200 1.8 fully diluted. 38 million dollars in volume. That's actually pretty decent. 522 00:49:09,200 --> 00:49:14,800 Just for your consideration, I've gone and got a picture of Simon Payton-Jones. Very 523 00:49:16,400 --> 00:49:21,040 And just want to draw your attention. Okay. Yeah, I remember who he is. Yeah. 524 00:49:21,040 --> 00:49:22,720 These are the eyes of a man that has seen 525 00:49:22,720 --> 00:49:26,960 now that I've seen you. 526 00:49:28,480 --> 00:49:31,920 Yep. Sorry. Hey buddy. Hey buddy, really crack me up. 527 00:49:34,000 --> 00:49:40,960 Oh my God. This, uh, so the wallets are funny on here as well. Rama quite rightly mentions that 528 00:49:40,960 --> 00:49:47,840 there is no Kepler in there. In what? Oh, in DYDX. In the, in the DYDX. Yeah. Yeah. Yeah. Yeah. 529 00:49:47,840 --> 00:49:52,160 Well, I think say, I'm not sure if that's finalized enough, but I, there was a rumor that 530 00:49:52,160 --> 00:49:57,600 say was not going to support Tepler either. At least I know it is now and obviously it is in 531 00:49:57,600 --> 00:50:01,840 A2 and all other types of stuff, but I thought there was a rumor that on mainnet that that was 532 00:50:01,840 --> 00:50:07,120 not going to happen. So yeah, it's interesting. I don't know how that works. They've got every 533 00:50:07,120 --> 00:50:14,720 other wallet ever created by looks of it. Just no cosmos wallets. It would be kind of funny if 534 00:50:14,720 --> 00:50:19,280 interest in the cosmos ecosystem finally results in the demise of all the tools in the cosmos 535 00:50:19,280 --> 00:50:26,240 ecosystem. It's what it brings with it. The users and the tools. All right guys, this shit's only 536 00:50:26,240 --> 00:50:32,000 going to work if we bring all that crap with us. They're like, good. They're travel bags are filled 537 00:50:32,000 --> 00:50:36,480 with. It's like, you don't really date somebody and then they, they like, they like literally, 538 00:50:36,480 --> 00:50:41,600 you've been, you've got like one day and then there's like a new toothbrush. This is like a very 539 00:50:41,600 --> 00:50:45,840 university slash college like experience, but you're like, hey, like, you know, one of your 540 00:50:45,840 --> 00:50:52,720 housemates is like, hey man, do you know where that extra toothbrushes come from in the bathroom? 541 00:50:54,480 --> 00:50:58,880 And they're like, well, I mean, it kind of seems like, you know, there was that girl around here 542 00:50:58,880 --> 00:51:03,840 the other day and there's another tooth. Is this like it's cool if it's a thing, but like, 543 00:51:03,840 --> 00:51:11,520 is that her toothbrush? And you're like, is it? Have I signed a, I've been off work, 544 00:51:11,520 --> 00:51:16,160 like a chew here? Is there something? Yeah. That's kind of like the other ecosystems moving in. 545 00:51:16,160 --> 00:51:20,400 Like, wait, we'll take the SDK. We'll take the SDK and the IBC and you guys keep the rest of that 546 00:51:20,400 --> 00:51:24,960 stuff. We don't want that. Yeah. It's like, I just, I, you have really customers. Your housemates, 547 00:51:24,960 --> 00:51:29,120 they're kind of weird. I think I ended up on Mint scan. I wonder if, is that going to happen? 548 00:51:29,120 --> 00:51:33,040 Are they already in Mint scan? Yes. They're on test at Mint scan. Yeah. They are at 549 00:51:33,040 --> 00:51:37,440 Mint scan. Has they either, oh yeah, they are at test at Mint scan. I guess that means they'll end 550 00:51:37,440 --> 00:51:42,400 up in Mint scan. It'd be interesting if they did not. Yeah. I mean, I guess there's a point where 551 00:51:42,400 --> 00:51:47,520 it's gone. I'm always certain they will. At a certain point is being on Mint scan, what defines 552 00:51:47,520 --> 00:51:52,400 whether you're a cosmos chain or not? No, it doesn't. Are you sure? At a certain point, 553 00:51:52,400 --> 00:51:56,560 I kind of feel like it does. Like if you look at chains that aren't on Mint scan versus what are, 554 00:51:56,560 --> 00:52:03,840 like those that are on Mint scan, like I think they very clearly have a price benefit to being on 555 00:52:03,840 --> 00:52:10,720 Mint scan. Yeah. Sure. But like is Penumbra going to be on Mint scan? Probably not. Yeah. 556 00:52:10,720 --> 00:52:15,040 Some of these, I just don't know. I mean, a lot aren't. I'm just curious. I mean, I'm just, 557 00:52:15,600 --> 00:52:21,040 just not a good question. It's a good question. Like, and, and I don't know, is it even their choice? 558 00:52:21,040 --> 00:52:26,400 Right? Like I, I assume let's say petition not to be, but it's, isn't it Cosmo station and 559 00:52:26,400 --> 00:52:32,480 and the community kind of defining what, what is up on there? I think they buy in or demand tokens to 560 00:52:32,480 --> 00:52:38,480 be listed on Cosmo. Sure. But it, but, but it, but in or demand. 561 00:52:40,320 --> 00:52:43,360 I think if you're, if you're Jimmy Small balls, they demand. 562 00:52:44,480 --> 00:52:49,600 Exactly. If you're Billy Big balls, if you're lucky, that's right. Now grace you with the, 563 00:52:49,600 --> 00:52:56,240 the big buckaroos. But I wouldn't like to assume that, yeah, I don't think you get anything for 564 00:52:56,240 --> 00:53:01,200 free in this life, particularly when Mint scanner involved. I just noticed that say 565 00:53:01,200 --> 00:53:04,240 Atlantic Tuesday on min scan test. That's interesting. I mean, notice I hadn't been on 566 00:53:04,240 --> 00:53:08,720 there before. I think they're even in Cosmo station is even the validator in there. Oh, 567 00:53:08,720 --> 00:53:14,240 yeah, they are my bad. Of course they are. Come on. I think, I think probably though, 568 00:53:14,240 --> 00:53:19,760 it is fair to say that a min scan kind of defines whether or not you're, I don't know, 569 00:53:19,760 --> 00:53:29,200 maybe a kind of respectable tier SDK chain. Because if you can rinse and repeat 570 00:53:29,200 --> 00:53:36,160 the setup of an SDK rig, RPC is the lot of it, then Cosmo station will have you, 571 00:53:36,160 --> 00:53:42,000 if you have the dollar reduced or you cross their part with silver. Yeah. Cosmo station, 572 00:53:42,960 --> 00:53:45,920 they validate on trash chains as well. 573 00:53:47,760 --> 00:53:53,120 You want to be specific there? I mean, I mean, look at the list of 574 00:53:53,120 --> 00:54:02,560 chains that are on top tier chains. We got going over here. 575 00:54:02,560 --> 00:54:08,480 Yeah. I mean, some of these I've never heard of, to be honest. It's getting busy on there. 576 00:54:08,480 --> 00:54:13,040 I mean, they're going to trench themselves even more though with min scan v2. And they're going 577 00:54:13,040 --> 00:54:17,040 to come out with like, you can access their indexer and stuff. It's going to become a very 578 00:54:17,040 --> 00:54:23,280 true thing that to not be on min scan is going to be like a huge disadvantage, which I think is 579 00:54:23,280 --> 00:54:29,840 just utterly fascinating. I kind of totally agree, disagree with you, Shorzi. 580 00:54:30,960 --> 00:54:36,000 100% okay, not 100%. Wait, that's totally I 100% disagree. 581 00:54:38,480 --> 00:54:42,480 I've backed myself into a corner here and I've gone way too hard, but I'm going to roll with it. 582 00:54:42,480 --> 00:54:46,080 Wow, that was a convenient drop off. 583 00:54:46,080 --> 00:54:53,680 So you know what? We'll go harder. I think that the dominance of min scan is basically 584 00:54:53,680 --> 00:54:59,680 a sign that the Cosmos ecosystem is super fucking immature. And actually, there are much more widely 585 00:54:59,680 --> 00:55:04,960 used tools in the ecosystem, as well as the fact that there could be multiple large profitable 586 00:55:04,960 --> 00:55:09,920 projects doing the same thing, especially given that you can actually copy and paste 587 00:55:09,920 --> 00:55:14,080 across a lot of SDK chains. So the two things I think that it shows are 588 00:55:14,640 --> 00:55:19,680 like some immaturity and tooling and the Cosmos and it shows a bit of weird business thing where I 589 00:55:19,680 --> 00:55:24,400 wonder if the real thing it shows, you know, the thing we always talk about about how the 590 00:55:24,400 --> 00:55:28,560 AppChain thesis may hold in the long run if there's enough adoption, but at the moment, 591 00:55:28,560 --> 00:55:33,760 all it does is fragment value and every project dies in the long run. It's just a long bleed to zero. 592 00:55:34,480 --> 00:55:39,600 Like building any tooling and trying to go after individual chains in the current market 593 00:55:39,600 --> 00:55:45,680 when there's only a few big dogs, you're going to just die because they've all gone with min scan. 594 00:55:45,680 --> 00:55:51,200 But if the ecosystem was actually more mature and or the AppChain thesis was actually viable, 595 00:55:51,200 --> 00:55:55,840 then there would be a huge amount of money. I mean, look how many people obviously do stuff 596 00:55:55,840 --> 00:56:01,600 around just ETHL2s. That shows you how much value is locked in that ecosystem compared to Cosmos. 597 00:56:01,600 --> 00:56:05,120 So which actually I realize now I've said that I'm not sure this is really just me 598 00:56:05,120 --> 00:56:08,400 disagreeing with you at all. It's just saying that this is where we are now, 599 00:56:08,400 --> 00:56:13,280 which is basically what you said. So I think I just stole your homework. Sorry, dude. 600 00:56:16,320 --> 00:56:20,960 Wouldn't be the first time. So the thing is, is right, so Ping.Pub came out with its new version, 601 00:56:20,960 --> 00:56:25,200 right? And I think that's really in many ways, I think it's really well done. There's a couple 602 00:56:25,200 --> 00:56:29,760 of things that like if they wanted to really like take it home, they would have their own back end 603 00:56:29,760 --> 00:56:34,640 as Minskent does, they'd probably index it yourself as I think Minskent does. But like the fact that 604 00:56:34,640 --> 00:56:40,000 you can connect your wallet to it and do transactions on it, like that's such a huge value add that 605 00:56:40,000 --> 00:56:44,640 Minskent does not provide. They might indeed to I haven't checked, but there are a lot of things 606 00:56:44,640 --> 00:56:50,320 that Ping does that Minskent should be doing. But it doesn't matter. Like being in Ping.Pub is 607 00:56:50,320 --> 00:56:53,680 considered like given if you're not in Ping.Pub, like what even happened? How did you how did 608 00:56:53,680 --> 00:56:59,840 you not get on Ping.Pub? If you're not a Ping.Pub, someone just hasn't has it musted the effort to 609 00:56:59,840 --> 00:57:06,000 like do the right thing. Yeah, but I think it's really interesting. I think it's interesting 610 00:57:06,000 --> 00:57:12,000 that Ping.Pub I think provides in many ways, maybe including maybe like IBC transaction data, 611 00:57:12,000 --> 00:57:15,760 like I use Minskent a lot for that. It's really helpful as a relayer. Other than that, I think 612 00:57:15,760 --> 00:57:21,520 that Ping.Pub provides very strong value that they don't get payback for, which I think it's a 613 00:57:21,520 --> 00:57:29,520 completely different point, but is one nonetheless. And Ping.Pub, like in terms of actual like useful 614 00:57:29,520 --> 00:57:33,600 utility tools and stuff for people who are in the ecosystem as well, I think Ping.Pub is way ahead 615 00:57:33,600 --> 00:57:40,080 of Cosmos Station there. And like even like really basic stuff where there were there are like a 616 00:57:40,080 --> 00:57:45,440 load of different validator operations that you would otherwise do on the command line. It's a 617 00:57:45,440 --> 00:57:51,360 fucking pain in the testicles to do with a ledger and then Ping just like threw them in the UI and 618 00:57:51,360 --> 00:57:59,600 you're like, oh, thank fuck. Like, I mean, yeah, those things they have live like November, December, 619 00:57:59,600 --> 00:58:05,840 2021, they got a lot of the core validator operation stuff with ledger just like in, 620 00:58:06,640 --> 00:58:10,640 you know, click around and you'll find it somewhere in the UI. Like Ping's really, really good. 621 00:58:12,560 --> 00:58:19,040 But yeah. I was kind of curious on like at that point around Minskent giving websites 622 00:58:19,040 --> 00:58:23,520 legitimacy or maybe change legitimacy in some sort of sense that you'd have to be there. I was 623 00:58:23,520 --> 00:58:26,640 kind of thinking that like DYDX with the amount of people that they're bringing in, like they wouldn't 624 00:58:26,640 --> 00:58:32,160 even care. It wouldn't create any sort of like inbound marketing or it wouldn't create any additional 625 00:58:33,440 --> 00:58:39,600 like visibility. But I was actually looking, I was curious on like website usage. So DYDX.exchange, 626 00:58:39,600 --> 00:58:45,920 I think it's the exchange site, a global rank of 162,000. They, they, at least this is a, 627 00:58:45,920 --> 00:58:50,400 this is off a web scraper type of thing, but they have total visits of around 260,000 a month, 628 00:58:51,040 --> 00:58:59,200 260,000 visits a month. Their rank in similar websites is not great. It's pretty far down. 629 00:58:59,200 --> 00:59:06,240 Global rank, they are one above taxadermy.net. So, so, so that's that. And then Minskent actually 630 00:59:08,400 --> 00:59:14,960 Minskent, Minskent global rank is 89,000. So about 50 to 60,000 higher. And they have a total 631 00:59:14,960 --> 00:59:22,720 visits of around 703,000 visits a month. And what are they in Minskent? Sexy.com with two E's. 632 00:59:23,840 --> 00:59:34,160 I visit that one every day. Sexy.com. And they're close. They're right in there. 633 00:59:34,160 --> 00:59:41,840 Next to sexy.com and liveapps.com. And yeah. So I mean, but still, I mean, 634 00:59:41,840 --> 00:59:45,200 I mean, 700,000 visitors a month on Minskent is actually, that's a lot higher than I was thinking. 635 00:59:45,200 --> 00:59:49,360 I was thinking this would be the opposite way actually, that it would be more. 636 00:59:49,360 --> 00:59:54,400 Did I just hear another page of duty? No, that was, no, this is my phone going off. Sorry. 637 00:59:54,400 --> 00:59:57,360 Okay. So when you say visitors, do you mean unique? 638 00:59:58,400 --> 01:00:01,920 I don't know. This is, this is, I mean, they're, they're getting this date. I got no, 639 01:00:01,920 --> 01:00:05,520 where are these places get this data? They're, they're buying, these guys are like buying some 640 01:00:05,520 --> 01:00:09,840 sort of ad tracker data from somebody else or something. This is a sum of all visits on desktop 641 01:00:09,840 --> 01:00:15,440 and mobile for the last month. I know these are unique. I was sending them that data null for 642 01:00:16,160 --> 01:00:23,120 a, a reserper from a random number generator on this laptop. I have more than $12,000 a month. 643 01:00:23,120 --> 01:00:27,200 There's a ton of these sites, right? So they, I'm sure they're, they're buying marketing data. 644 01:00:27,200 --> 01:00:32,000 They're buying some company. Just don't rug my scam. Okay, man. I've just told them I've hacked 645 01:00:32,000 --> 01:00:36,240 the matrix and I have the numbers. The numbers are probably not close, but they probably are 646 01:00:36,240 --> 01:00:41,040 relatively, like relative ranking is probably similar, right? Like it's not going to be down to 647 01:00:41,040 --> 01:00:46,160 the thousands of visits, but would you say is it, is there enough data there to say that they're, 648 01:00:46,800 --> 01:00:51,920 that, you know, that mince can has three times as much traffic as DYDX? Yeah, that probably is. 649 01:00:51,920 --> 01:00:56,880 It's that, that part is probably pretty accurate. But, but it's interesting. It's actually, 650 01:00:56,880 --> 01:01:02,480 I was thinking about the taxes. Yeah. Yeah. But if you look at like, I mean, if you want to look 651 01:01:02,480 --> 01:01:06,880 at like min scan versus like open C, you know, that's, those are different, different types of 652 01:01:06,880 --> 01:01:12,960 numbers. I think it's interesting the phrase that you consider min scan to be early tooling. 653 01:01:12,960 --> 01:01:20,000 I consider min scans, um, interface as well as it's, um, I mean, a lot about it to be superior to, 654 01:01:20,880 --> 01:01:25,040 whatever the Ethereum one is, I can't even remember. Ether scan. Ether scan. I don't like 655 01:01:25,040 --> 01:01:32,240 Ether scan. I think that's a way more clogged kind of without a single like unified voice interface, 656 01:01:32,240 --> 01:01:38,400 right? And my opinion, min scan is better than Ether scan. And so that you think it's like immature 657 01:01:38,400 --> 01:01:41,440 for lack of a better, not immature in like a childish sense, but like they have further 658 01:01:41,440 --> 01:01:46,240 to develop. I think it's really interesting. I mean, A, a little bit, but B, I think it's actually 659 01:01:46,240 --> 01:01:53,040 just, it's not so much about min scan themselves, but the fact that they have that market dominant 660 01:01:53,760 --> 01:01:59,280 what in an ecosystem that is supposed to be all about horizontal scaling, that's the sign of, 661 01:01:59,280 --> 01:02:06,720 of immaturity. It's more about immaturity of the concept of product market fit where the product 662 01:02:06,720 --> 01:02:12,800 is the app chain thesis, which I'll admit is quite an abstract thing to call the digital product. But 663 01:02:12,800 --> 01:02:18,000 I think in this case, that's kind of the, the thesis there. Is this another case where the 664 01:02:18,000 --> 01:02:27,440 cosmos is uniquely positioned to commodify like things that normal quote unquote networks, you 665 01:02:27,440 --> 01:02:33,680 know, can give you money off of like in the cosmos, RPCs are commodity. That's not true if you go to 666 01:02:33,680 --> 01:02:44,640 Aptos or near or sweet or sort of. Oh, well, we just stumbled onto the, the PowerPoint from the 667 01:02:44,640 --> 01:02:49,680 other week again. So I just, I just threw it up to point out that you're completely right. RPCs 668 01:02:49,680 --> 01:02:54,640 are commodified. They literally are in the commodity sector on a, on a product value canvas. 669 01:02:54,640 --> 01:02:58,240 Yeah. So yeah, I think like, I mean, tools like Cosmos, 670 01:03:00,400 --> 01:03:05,120 well tools like Cosmos directory and those types of things have definitely gone a long way to, 671 01:03:05,120 --> 01:03:09,840 to commoditize those tools. The other thing that's interesting there about the commoditization of 672 01:03:09,840 --> 01:03:16,320 those tools though, is that in like web two, you'd almost expect to like, if you, if you are the one 673 01:03:16,320 --> 01:03:21,920 commoditizing a tool, you expect to commoditize it and that to be like a revenue generating activity. 674 01:03:21,920 --> 01:03:26,960 Whereas in Cosmos, it feels like a lot of those activities have been commodified by the structure 675 01:03:26,960 --> 01:03:32,640 of the network. And they've just ended up in a tragedy of the commons. They've just like, 676 01:03:32,640 --> 01:03:37,520 exactly. They've just literally picked them up and they've gone, and now we're going to put them 677 01:03:37,520 --> 01:03:43,200 in the bin. And if, so I was trying to explain this in the context like last week, I had this 678 01:03:43,200 --> 01:03:46,560 conversation with some people who were like, coming at it from more of a theoretical standpoint, 679 01:03:46,560 --> 01:03:51,600 and they were like, you know, what do you think are the problems in the networks that you work in, 680 01:03:51,600 --> 01:03:54,480 from your perspective? And I said, oh, you know, this and this and this and this. And a lot of it 681 01:03:54,480 --> 01:03:58,560 was like that kind of stuff, like tragedy of the commons blah, blah, blah. And these people were 682 01:03:58,560 --> 01:04:02,080 computer scientists, right? That was kind of their background. And they were like, these are all 683 01:04:02,080 --> 01:04:05,680 economic problems. These are the economics. They're not computer science. I'm like, well, 684 01:04:06,240 --> 01:04:11,360 yeah, but they're, they look like economic problems because there are problems about incentives. But 685 01:04:11,360 --> 01:04:16,400 who decided the topology of the system was that RPCs were going to be free? That is a computer 686 01:04:16,400 --> 01:04:19,760 science problem. That is a, well, it's an architecture problem, perhaps like a software 687 01:04:19,760 --> 01:04:24,320 design problem, maybe more than it is a computer science problem. But, you know, this is, this 688 01:04:24,320 --> 01:04:28,960 is programmable, a system for programmable money in some way, shape or form. And actually, yeah, 689 01:04:28,960 --> 01:04:33,200 it'll rebuild the incentive system where we've commodified a bunch of stuff and just throw it 690 01:04:33,200 --> 01:04:40,800 over to the tragedy of the commons and gone. Yeah. Decentralization. Yeah, it's, I think it's an, 691 01:04:40,800 --> 01:04:44,000 I don't know, even a word that comes from, but I don't know if it's cosmopolistic or it's just a 692 01:04:44,000 --> 01:04:50,560 DPS, distributed or the decentralized proof of stake component where you have validators fighting. 693 01:04:50,560 --> 01:04:57,040 So therefore fighting for a no try for, for notability and fighting for delegations and 694 01:04:57,760 --> 01:05:01,600 that's why RZ. So it ends up becoming what can I offer and then who are those groups I'm going 695 01:05:01,600 --> 01:05:05,920 to offer it to and RPC becomes one of those things. And then there's so many chains I need to have 696 01:05:05,920 --> 01:05:09,680 visibility for. We got to keep track of all this shit. So therefore we have a website that tracks 697 01:05:09,680 --> 01:05:12,400 all this stuff. And then I got to, well, if we're going to track all this, we should track who's 698 01:05:12,400 --> 01:05:16,720 offering free RPC. And then now there's one centralized place to get all free RPC. And so 699 01:05:16,720 --> 01:05:21,760 like it's just a set of small, small decisions that then create this idea that RPCs are free. 700 01:05:22,880 --> 01:05:27,280 Is that, are they free forever? I don't know. I don't know what, I don't know what the long term 701 01:05:27,280 --> 01:05:31,600 is there. Like as people get out of chains and they have validators leave chains, those RPCs 702 01:05:31,600 --> 01:05:34,880 are going to disappear as well. But like we said before, there's going to be somebody else who's 703 01:05:34,880 --> 01:05:38,320 going to come in to fill that gap too. So I think that 704 01:05:38,320 --> 01:05:42,560 a cash problem, isn't it with the providers, which we talked about like at length, like there was 705 01:05:42,560 --> 01:05:48,000 that big conversation that, because you were looking into being a provider and a cash, right? 706 01:05:48,000 --> 01:05:53,120 And so was polkachute. So we had that, a variation on the same discussion about the economics of that. 707 01:05:53,760 --> 01:05:58,000 Well, so I think one of the really interesting things here also is that whenever I first joined 708 01:05:58,000 --> 01:06:06,640 the Cosmos as a validator, I think it was in early 2021, maybe 2020. And back then you had, 709 01:06:06,640 --> 01:06:11,840 you had Everstate, you had Figment, and you had, I want to say, course one, that all had very 710 01:06:11,840 --> 01:06:16,960 large products around providing RPCs. And I know many teams used those specific RPCs because I 711 01:06:16,960 --> 01:06:22,720 talked with them. And those teams, especially Figment, but Figment's another conversation, 712 01:06:22,720 --> 01:06:28,400 like I've noticed those RPC provisions have actually gone away to the exclusion of maybe 713 01:06:28,400 --> 01:06:33,920 Block Damon. So it's like, because of the tragic commons of all of us, it's also eaten away into 714 01:06:33,920 --> 01:06:39,200 like the really large entities, of course, because that's what happens whenever all of us are providing 715 01:06:39,200 --> 01:06:43,120 it, then the big guys are like, oh, well, I guess, would you get out of it? So it's interesting 716 01:06:43,120 --> 01:06:48,240 that it's eating away from profit sectors of everyone, not just the people that are, 717 01:06:48,240 --> 01:06:51,360 you know, for lack of a better term, like clawing at the bottom. Yeah. 718 01:06:51,920 --> 01:06:58,160 So we've also got some stuff in the comments, which it's lively, it's lively, it's lively 719 01:06:58,160 --> 01:07:05,440 placed here tonight out there, out there in the coin section. So Ben Davis has called out, 720 01:07:05,440 --> 01:07:11,680 by phrase logic, internet search is immature. No, I'm saying they're a little bit different because 721 01:07:11,680 --> 01:07:17,280 Web 2 tends towards natural monopoly, right? And the whole point of Web 3 is that you design a system 722 01:07:17,280 --> 01:07:23,600 in which you enforce a separation of economic systems that are all sort of not mutually exclusive, 723 01:07:23,600 --> 01:07:28,960 they're all specialized economic systems that are all federated. That's the App Chain Thesis. 724 01:07:30,320 --> 01:07:35,040 But if you have all of your economic systems are federated, but all of your infrastructure is 725 01:07:35,040 --> 01:07:40,400 centralized, then that may be the intention of the cosmos, right? In which case, fine, 726 01:07:40,400 --> 01:07:46,880 I'll, you know, I'm a neck in, but it seems to me like, if you can't sustain any more than one copy 727 01:07:46,880 --> 01:07:51,680 of the infrastructure that supports your network, then you have a single point of failure, 728 01:07:51,680 --> 01:07:57,040 and your system topology was not designed. It's just an element of the puzzle that you didn't 729 01:07:57,040 --> 01:08:01,600 consider, which, you know, it's very, very hard to consider a complex system and get everything 730 01:08:01,600 --> 01:08:07,200 right. So like, it's not like a shit talk or shit post on the cosmos, it's just an observation that 731 01:08:07,200 --> 01:08:14,000 it strikes me as immature or as a point of failure that those additional, there isn't enough incentive, 732 01:08:14,000 --> 01:08:18,000 there isn't enough liquidity, whatever it might be to support multiple projects in the same way 733 01:08:18,000 --> 01:08:21,600 that you expect to see different, you know, infrastructure provision, I suppose. 734 01:08:22,720 --> 01:08:23,200 Resets. 735 01:08:23,200 --> 01:08:26,960 Let me start moving in there really quick before you go in. One interesting thing about that is, 736 01:08:26,960 --> 01:08:31,040 I think that it sets up teams for failure as well. Like, I've been checking around at 737 01:08:31,040 --> 01:08:36,400 archive nodes lately, just out of my own curiosity, and a lot of networks that I can find don't have 738 01:08:36,400 --> 01:08:42,000 a known archive node, because teams like aren't, aren't looking for archive nodes, right? So then 739 01:08:42,000 --> 01:08:47,040 they just expect that to be a commodity. And so if there's no archive node provided, then 740 01:08:47,040 --> 01:08:52,000 who has block one? How do we know any of this is even true? As validators, we ensure that the next 741 01:08:52,000 --> 01:08:57,440 block is true. We're not ensuring that the previous block is true. But anyway, that anyway, we're 742 01:08:57,440 --> 01:08:59,840 setting teams up for failures with all this modifications, what I'm saying. 743 01:08:59,840 --> 01:09:03,120 I mean, clearly the past is for nerds and only the future. 744 01:09:06,000 --> 01:09:06,720 Fuck yesterday. 745 01:09:07,920 --> 01:09:10,720 What's the Henry Ford history is bunk? 746 01:09:10,720 --> 01:09:17,840 Yeah. I need to get the screen grab of the scene from the death of Stalin where 747 01:09:19,040 --> 01:09:24,400 Steve Buscemi says, you've been convicted of anti-Soviet behavior will be shot. That's this 748 01:09:24,400 --> 01:09:32,000 moment. So Reese says every user should run their own RPC chain and wallet. 749 01:09:32,720 --> 01:09:33,120 Agreed. 750 01:09:35,680 --> 01:09:38,560 He forgot relayers. They should be running their own relayers. 751 01:09:38,560 --> 01:09:40,640 They should build their own ledgers as well. 752 01:09:41,120 --> 01:09:52,480 Well, so I was going to say the thing is, right, in episode 66, we obviously had Henry from 753 01:09:52,480 --> 01:09:57,520 Pernumbra here. And the interesting thing is that Pernumbra is sort of, to my understanding, 754 01:09:57,520 --> 01:10:03,040 anyway, works a little bit like that, that you are running a client as a user in order to do some 755 01:10:03,040 --> 01:10:07,760 of, well, because there's a pretty complicated architecture, who would support the zero knowledge 756 01:10:07,760 --> 01:10:12,080 architecture of the overall system, right? Because you're not persisting like any of your 757 01:10:12,080 --> 01:10:15,920 transactions. Well, you are persisting transactions to the chain, so you're persisting proofs, I 758 01:10:15,920 --> 01:10:21,440 suppose, but the entire system topology is very, very different. So I know you're being sarcastic, 759 01:10:21,440 --> 01:10:29,200 but the thing is maybe we should be, right? Maybe we should be. Maybe that actually is the 760 01:10:29,200 --> 01:10:38,560 future. Don't know. Anyway, there are a bunch of other good comments. Yeah, but 761 01:10:38,560 --> 01:10:44,320 they're not going to show. Yeah, definitely. There's the comments that we're going to show. 762 01:10:44,320 --> 01:10:50,560 If you want to hear more great comments, and you're listening back on a podcast player, 763 01:10:50,560 --> 01:10:54,720 then you should check in 2100 every Wednesday on YouTube. 764 01:10:54,720 --> 01:10:59,360 That's what we're not going to share about this guy. Game of Nodes, and enjoy, get involved in 765 01:10:59,360 --> 01:11:05,200 the chat, get involved with some of these characters. Maybe you can even become part of the show. 766 01:11:05,200 --> 01:11:10,400 This is a part of Game of Nodes, as if you hang around long enough, eventually you get to actually 767 01:11:10,400 --> 01:11:14,720 be on the podcast. It wouldn't be the first time we've had absolutely nothing to talk about and 768 01:11:14,720 --> 01:11:19,760 board up a community member to save our us. I tried to do it even today with Rama, 769 01:11:19,760 --> 01:11:27,200 because he knew what a streamstrap was. I just work here, man. I just work here. 770 01:11:28,640 --> 01:11:38,080 So it's an hour and 15 in, but it is time for the whole tweet of the week. A section that's 771 01:11:38,080 --> 01:11:52,080 like a cockroach refuses to die. Well, of course, I picked the most toxic page, possibly the entire 772 01:11:52,080 --> 01:12:01,760 book. Book market. I just got a little doggy around it. So the one that I think I landed on, 773 01:12:01,760 --> 01:12:10,160 I want to switch off it because it's, but I'm committed to. So it's in the section girls. 774 01:12:11,280 --> 01:12:21,040 And the drill tweet is hashtag to the girls 2016. I'm intelligent, ampersand, clean boy. 775 01:12:21,040 --> 01:12:27,680 I have the trigger discipline of a lion. Discipline is about wrong. I've used torture, 776 01:12:27,680 --> 01:12:33,680 capital T to cure myself of all mental illness. Okay. That was a little dark. 777 01:12:34,400 --> 01:12:40,400 Yeah. I'm intelligent. I have the trigger discipline of a lion. I've used torture 778 01:12:40,960 --> 01:12:45,280 to cure myself of all mental illness. There is a lot going on in that one. That is 779 01:12:46,000 --> 01:12:54,240 an unusually dark and strange drill tweet. I'd say. Well, I think that's a grab bag of concepts 780 01:12:54,240 --> 01:13:00,880 that has gone into that drill tweet. It's not that is. Some of these really are. 781 01:13:02,880 --> 01:13:07,120 Firstly, I think you lost our entire audience base when you said for the ladies. 782 01:13:08,160 --> 01:13:13,520 They're like, what the fuck is that? Well, I think that for the ladies 2016 is the really 783 01:13:13,520 --> 01:13:18,960 interesting bit, right? Because 2016 is like such a specific year, at least in American politics. 784 01:13:18,960 --> 01:13:24,720 It's a long time ago. It's a long time ago. I got to pull it up. I need to pull this tweet now. 785 01:13:24,720 --> 01:13:28,240 But what are the fuck does it all mean? It's a great place. 786 01:13:29,360 --> 01:13:36,720 So back on the explorers, back on Mintsgan specifically, has anyone else noticed for the 787 01:13:36,720 --> 01:13:45,280 longest time, the chain selection little box that pops up used to have Cosmos Hub and Osmosis 788 01:13:45,280 --> 01:13:51,600 only, right? Being like, you know, the two chains that should be emphasized. 789 01:13:52,320 --> 01:14:00,800 And now I've seen that Neutron has appeared there with its own little cheerleader banner 790 01:14:00,800 --> 01:14:07,600 on the side, decreeing that it's part of ICS, right? But in addition to, this is what I find 791 01:14:07,600 --> 01:14:15,840 interesting. Kava has rocketed to the to the emphasized chains line, and it's got the little 792 01:14:15,840 --> 01:14:22,960 tether banner there, right? Now, what's funny about this is that when you look at Noble, 793 01:14:22,960 --> 01:14:27,760 it's relegated to the fucking the normie list, right? Are they listed in there? Oh, they are. 794 01:14:28,320 --> 01:14:30,880 But so you didn't even notice that. I didn't even notice that. 795 01:14:30,880 --> 01:14:38,480 Their little cheer banner is like gray. Yeah, it's called grayed out. Like, do you think there's 796 01:14:38,480 --> 01:14:46,720 been some cash exchange to make this Kava thing more prominent? I mean, they announced later. 797 01:14:46,720 --> 01:14:52,960 I don't think they're live with UST yet. I don't know. I'm just saying. 798 01:14:53,760 --> 01:14:58,320 Cosmos Station, I mean, yeah, I don't know. That's really where I even noticed they were in 799 01:14:58,320 --> 01:15:04,240 that list, actually. Yeah. And you're right. This little banner is like all completely grayed out, 800 01:15:04,240 --> 01:15:09,920 like this little tiny thing. Yeah, they've like, I think that he, look, don't quote me. I think it 801 01:15:09,920 --> 01:15:15,920 used to be not grayed out. Oh, yeah. I wonder why they picked tether, not USDT, also as a banner, 802 01:15:15,920 --> 01:15:20,080 right? Like, that's why I wouldn't say circle. Like, that's a weird district, like a weird 803 01:15:20,880 --> 01:15:24,800 station. So I appreciate that question, but I feel like you're getting too much into the weeds. 804 01:15:24,800 --> 01:15:29,120 I'm on a product question. Like, if I were the product guy, I surely would be like, okay, 805 01:15:29,120 --> 01:15:34,400 you said USDC, obviously you're going to say USDT. I just don't think they put that much thought 806 01:15:34,400 --> 01:15:38,000 into it. Like that, I think that's what it boils down to. It could be. I always like to look, 807 01:15:38,000 --> 01:15:42,000 I always like to see if there's like a little, like a little jab in there for some reason. I don't 808 01:15:42,000 --> 01:15:49,840 know why. I appreciate it. I'm all about it. I think it's more likely that there's been an exchange 809 01:15:49,840 --> 01:15:57,520 of some type of, you know, medium for a more prominent and branded little cheer banner. 810 01:15:57,520 --> 01:15:59,920 They should do more cheer betters like rug. Fucked. 811 01:16:02,720 --> 01:16:06,640 Ponzi. You get like a little wrecked badge. Little NGMI badge. 812 01:16:10,720 --> 01:16:15,920 Wouldn't that be like most of them is not the problem. You gotta have a little bit of cheer 813 01:16:15,920 --> 01:16:20,080 banner though. Yeah. Well, they need some more headings. Like they've got Cerberus under its 814 01:16:20,080 --> 01:16:24,480 own little archived heading. They need some more headings there with like really opinionated 815 01:16:24,480 --> 01:16:28,560 headings. How long do you think Cerberus hangs out in there? What's the, what's the, 816 01:16:28,560 --> 01:16:33,840 uh, how long is the body in display? What's the archived duration before it just fucking? 817 01:16:34,960 --> 01:16:37,440 How long is the casket open? Is really what we're asking here. 818 01:16:39,520 --> 01:16:44,960 I still think that there should be a like six month or even three month like dead man switch. 819 01:16:44,960 --> 01:16:48,320 There's no get commits. Boom. Proc goes up. Kick it out. 820 01:16:48,320 --> 01:16:55,600 All right. But here's the thing, right? Somebody somewhere has an archive of Cerberus, right? 821 01:16:55,600 --> 01:16:59,120 Up the last blog. Yeah. It's not bad. We're talking to you. 822 01:16:59,680 --> 01:17:04,160 It's not fucking dead. So here's my prediction. Right. Here's a prediction straight from Game 823 01:17:04,160 --> 01:17:09,680 of Notes. From our opinions to your ears. Next bull run, Kerb's coming back. 824 01:17:09,680 --> 01:17:15,120 You think somebody's going to relaunch? They're going to grab that, that day, 825 01:17:15,120 --> 01:17:18,400 that snapshot from Polkachu, which I'm sure exists. 826 01:17:18,960 --> 01:17:21,520 Sitting in the chains going back. S3 bucket and glacier. 827 01:17:22,240 --> 01:17:27,440 Well, I mean, you only need like a Regenesis, right? I'm sure that someone's going to stay. 828 01:17:27,440 --> 01:17:30,400 Yeah, sure. Yeah. Just regen it. Yep. 829 01:17:30,400 --> 01:17:35,040 There's some fucking DJ out there sitting on the trigger ready to go to. They're probably like 830 01:17:35,040 --> 01:17:40,480 rekeyed all of the validators too, so they can run it completely by themselves. 831 01:17:42,000 --> 01:17:45,600 I thought Polkachu got like a last transaction on here. I was trying to find it because you can 832 01:17:45,600 --> 01:17:50,400 actually still look up those blocks. I remember him having like a last send or something else like 833 01:17:50,400 --> 01:17:59,120 that. I forget. I'm on the Tenement Snaptrots section of Polkachu site. It just reminds me, 834 01:17:59,120 --> 01:18:03,760 Jesus Christ, there are a lot of cross chains. So many chains. 835 01:18:03,760 --> 01:18:08,640 Genuinely a little bit overwhelming as a Cosmos validator. So look at this and go. 836 01:18:10,640 --> 01:18:14,480 We added it up and we are on 71 networks right now, including test nets. 837 01:18:15,200 --> 01:18:17,040 In the Cosmos. In the Cosmos. 838 01:18:17,600 --> 01:18:21,040 I mean, you got to stop. You really need a moment of reflection. 839 01:18:24,480 --> 01:18:26,160 So we were reflecting then? 840 01:18:26,160 --> 01:18:30,880 No, no, no. I'm not saying. I'm saying if you're running 71 chains in your stream of production. 841 01:18:30,880 --> 01:18:34,640 Yeah, you have to look back and say like, all right, what are we doing? 842 01:18:35,280 --> 01:18:37,840 You're actually caught like 12. 843 01:18:37,840 --> 01:18:42,480 Yeah, you really need to stop and think. Is this going anywhere? 844 01:18:42,480 --> 01:18:45,600 I did find I did find Polkachu's last, I put it on wrong, 845 01:18:46,320 --> 01:18:48,560 Polkachu's last transaction, which was pretty funny. 846 01:18:49,520 --> 01:18:54,720 Is six chain not archived? Didn't it die? No, it came back. 847 01:18:54,720 --> 01:18:55,760 It's not going, is it? Yeah. 848 01:18:55,760 --> 01:18:59,680 Huh. Meme. Is it dead yet? 849 01:18:59,680 --> 01:19:01,040 Nope. Still making blocks. 850 01:19:01,600 --> 01:19:02,880 Well, do they have transactions? 851 01:19:02,880 --> 01:19:05,840 You got to find dead. Yeah. Good point. 852 01:19:06,640 --> 01:19:10,240 Meme is that they were never on min scan though. So I can't tell. They have another one. 853 01:19:10,800 --> 01:19:15,360 That's what I'm saying. If you're not on min scan, like, how do you even know? 854 01:19:15,360 --> 01:19:20,160 Like Galaxy. Galaxy is another one. They went into the discord and they're like, 855 01:19:20,160 --> 01:19:22,320 hey, we're not doing any development anymore. 856 01:19:22,320 --> 01:19:26,240 Is that what they said? Basically, yeah, they're like, we're like, 857 01:19:26,240 --> 01:19:30,880 we would like help because we're done and everyone's left. And is it still running? 858 01:19:30,880 --> 01:19:33,840 I don't know. Let's see if I can pull it up. Let's see. 859 01:19:33,840 --> 01:19:35,680 It might still be going, but it shouldn't be. 860 01:19:36,720 --> 01:19:40,400 The interesting thing about Juno is that everyone rags on Juno, right? 861 01:19:40,400 --> 01:19:45,200 About being dead, fucking, you know, lost all its value, all that shit. 862 01:19:45,200 --> 01:19:49,600 Funny thing is that like, I think it still probably has one of, 863 01:19:49,600 --> 01:19:52,800 like one of the highest transaction, transacted chains. 864 01:19:53,920 --> 01:19:59,360 It's all those original airdrop recipients. 865 01:19:59,360 --> 01:20:00,320 It's just dump cell. 866 01:20:04,560 --> 01:20:09,760 That's why like, if you take those people out of the picture, the number of transactions 867 01:20:09,760 --> 01:20:16,400 that go down and the value go up. But this is the thing. This is the problem if you 868 01:20:16,400 --> 01:20:21,760 launch something on, on, when to found any chain that's done an airdrop as a team. 869 01:20:22,720 --> 01:20:27,280 The tokenomics, if there have been a large airdrop in the early days, are going to be heavily 870 01:20:27,280 --> 01:20:31,600 weighted towards those people who a lot of them are not even going to interact with your protocol. 871 01:20:31,600 --> 01:20:35,840 If you launch a smart contract protocol, they're just going to continue jumping coins and 872 01:20:36,640 --> 01:20:41,520 shitting on the protocol. They're just farming and it's going to affect any, 873 01:20:41,520 --> 01:20:46,880 any second order protocol that you write as a smart contract engineer. It's kind of like, 874 01:20:46,880 --> 01:20:51,520 back to the piece of the puzzle, which is that you really do need like, if you're like a smart 875 01:20:51,520 --> 01:20:56,240 contract developer, you need to really, really be happy with the economics of the underlying 876 01:20:56,240 --> 01:21:00,800 chain that you deploy on. And I think like, this is one thing to be fair, is actually addressed 877 01:21:00,800 --> 01:21:05,280 to some extent in Juno Evo. And it is also one of the things that I know folks are working on. But 878 01:21:06,320 --> 01:21:11,040 the underlying tokenomics of the chain like a just mad important for actually attracting 879 01:21:11,040 --> 01:21:16,000 developers. And I think people are beginning to understand that. But we've talked about that 880 01:21:16,000 --> 01:21:27,920 on the show before. Cool, man. Cool, man. Well, sometimes when it gets to like one hour to 60 881 01:21:27,920 --> 01:21:34,560 minutes, I just kind of idly hover about daydream over, overrugging early. Like that time you 882 01:21:34,560 --> 01:21:44,000 joined and you just rocked you like, and then left. That was really funny. That was to be fair, 883 01:21:44,000 --> 01:21:48,480 a complete fucking accident. Well, yeah, and it ended on you being like our deuces. 884 01:21:52,080 --> 01:22:00,640 If I can't be here, no one can be here. Fuck you all. Yeah. Nice to have race here. Definitely. 885 01:22:00,640 --> 01:22:06,960 So the great, yeah. I mean, there's I think, you know, it's all about the key bono, though, 886 01:22:06,960 --> 01:22:11,760 isn't it? Like, I think Archway and others, not there's actually any conspiracy here. I just 887 01:22:11,760 --> 01:22:17,920 think that there's a lot of people who bono if Juno is perceived as dead, right? Yeah. And 888 01:22:18,640 --> 01:22:25,040 the reality is like, like anything else, it's just every alt is fucked at the moment. And 889 01:22:25,040 --> 01:22:30,000 I'll go counter to the chat right now. The chat they're making jokes about Juno being dead. 890 01:22:30,640 --> 01:22:35,040 But and we've had this conversation multiple times before, I still think there's a place for Juno. 891 01:22:36,160 --> 01:22:41,840 I think that if Juno could reclaim its, its community stands, it has a place. We've said 892 01:22:41,840 --> 01:22:46,560 before that like, it's so easy to start a network now that why not just start your own network 893 01:22:46,560 --> 01:22:51,920 rather than building on Juno. And one, I can make an argument for building on terror instead of Juno, 894 01:22:51,920 --> 01:22:54,800 but I'm not going to make that argument right now. But I think there's a lot of really interesting 895 01:22:54,800 --> 01:22:58,400 things happening, not necessarily on terror, but like within the terror community that is 896 01:22:58,400 --> 01:23:04,160 worth discussing at some point. But running a chain isn't the same thing. It doesn't, it affects your, 897 01:23:05,120 --> 01:23:11,200 your, your perspective and your priorities differently than trying to build to create 898 01:23:11,200 --> 01:23:17,360 something for a chain that you can then bounce off from. Like with how maybe that should have been 899 01:23:17,360 --> 01:23:22,400 its own chain, right? But there's a reason why you chose to do it on Juno rather than creating 900 01:23:22,400 --> 01:23:26,480 the how chain. And part of that, I'm sure is creating a chain is a completely different ball 901 01:23:26,480 --> 01:23:31,600 game. If you had to have, have created the how chain, there's so much more overhead to it. You 902 01:23:31,600 --> 01:23:34,720 have to create, you have to coordinate those values. You need to do those full upgrades. You 903 01:23:34,720 --> 01:23:40,240 need to do upgrade handlers. And why, why bother with that? There's so much simplicity in just 904 01:23:40,240 --> 01:23:46,640 joining a, a unpermissioned chain. But anyway, that's a bit serious to be jumping into in the 905 01:23:46,640 --> 01:23:53,040 last minute of the show. It's usually, it's usually when the best comments come actually. I 906 01:23:53,040 --> 01:23:56,160 mean, isn't the best comments usually come immediately after the show? 907 01:23:57,520 --> 01:24:02,400 Second, the second the shit finishes rolling, especially when we have a guest, they're just 908 01:24:02,400 --> 01:24:07,760 like, Hey guys, that, that was a load of fun. So anyway, here's what I was thinking about 15 909 01:24:07,760 --> 01:24:11,040 minutes ago. And you're like, why didn't you just say it? And then they're like, well, 910 01:24:11,040 --> 01:24:16,400 then it's really our shit questions. So at the end of the day, it's our fault. Like it was, 911 01:24:16,400 --> 01:24:22,240 obviously our fault as the, as the hosts that we have a better after show quite often. So 912 01:24:23,440 --> 01:24:28,160 that's now a really, really weird tone to end on. And now I know that now there's literally 913 01:24:28,160 --> 01:24:44,080 hovering over the button, just waiting to send me to the dark dimensions. So