WEBVTT 00:00.289 --> 00:02.271 Yeah. 00:02.471 --> 00:03.312 Yeah, sick. 00:04.793 --> 00:05.373 Fuck, man. 00:05.393 --> 00:07.335 What if I... Oh, shit. 00:08.916 --> 00:11.878 What if I... I need a second opinion from Serp, maybe. 00:29.366 --> 00:34.610 Welcome to Game of Nodes, the most timely weekly podcast from independent validator teams. 00:35.390 --> 00:37.091 Most punctual, certainly. 00:37.131 --> 00:37.872 Who fucking did that? 00:39.693 --> 00:40.173 Was that you? 00:41.334 --> 00:42.555 I'm just very, very funny. 00:43.115 --> 00:44.676 You weren't even in the fucking screen. 00:44.696 --> 00:46.497 You were like remotely doing that. 00:46.517 --> 00:47.958 Were you in the screen? 00:48.299 --> 00:50.240 I've got one word for you now. 00:50.520 --> 00:52.001 Bluetooth peripherals. 00:52.521 --> 00:53.182 That's two words. 00:55.977 --> 00:56.357 Touche. 00:56.377 --> 00:57.958 Touche. 00:58.579 --> 01:02.983 This would probably be the most punctual we've been in at least six months. 01:03.003 --> 01:05.585 I know, I barely sat down. 01:06.006 --> 01:06.306 What the hell? 01:07.427 --> 01:17.156 It would have been actually... I should have done the timing so that the second I saw Serp's door starting to open, we hit the intro. 01:17.996 --> 01:18.357 And then... 01:20.328 --> 01:44.931 between walking that i think the intro would be about long enough for you to walk from the door to your desk put your headphones on realize that it was live and it would look like you just teleported just kind of slid right in there so that would have been that would have been a truly magic moment but you know nothing's perfect this is real life truly magic we're so we're so i think we've trained our viewers so well that we're the only ones here 01:45.852 --> 02:10.055 because i think i think all the viewers actually show up every hour 10 after as well exactly why would i get there early there's no reason to get there early that's why we have new viewers right right right right jesus i guess that's consensus shelter your mark phone is loud yeah i didn't i didn't touch the game all right let's see 11 is what that is all right is this better better better there you go 02:13.891 --> 02:26.845 All of the people who've got external audio interfaces running and they've got a little monitoring set up, it's like, I think you're at the red there, my bad. 02:26.865 --> 02:31.310 There's your little light on your thing, like hanging off the... 02:33.863 --> 02:53.392 yeah exactly so we're doing a podcast today is that what we're doing so oh we're live right is that what it says we're already live yeah okay we've been live for some time all right just check it she'll see your microphone was so loud that when you talked in it it was making my meter go right 02:56.713 --> 03:21.657 that's good that's important that's like actually one of my peak uh podcast peeves if you like whenever i listen to a podcast and i can hear that the other like somebody's mic is so hot and somebody's monitoring setup is so bad that you can hear it pinging to the other one that oh because it's usually just like a very very small artifact and like 03:23.214 --> 03:23.614 I don't know. 03:23.974 --> 03:25.535 Maybe most people wouldn't notice it. 03:26.075 --> 03:28.396 I think people will, though, like a small one. 03:28.536 --> 03:30.177 It does... Oh, that really does my head in. 03:30.197 --> 03:31.858 I'm just like, oh, could you just not? 03:33.899 --> 03:34.319 Can you not? 03:35.299 --> 03:35.699 Yeah. 03:37.180 --> 03:38.301 Yeah, so... Can you not? 03:38.821 --> 03:39.821 Okay. 03:41.182 --> 03:41.882 Drill tweet of the week. 03:41.922 --> 03:44.103 We missed last week's, but we'll only do one. 03:44.163 --> 03:45.424 We'll do a standard. 03:45.444 --> 03:47.545 We haven't done a drill tweet in a long time. 03:47.765 --> 03:49.225 We've not done it for several weeks. 03:49.285 --> 03:51.206 It's before Christmas, but that's okay. 03:51.286 --> 03:52.267 Short C, you're up. 03:53.208 --> 03:54.668 Would you like to say when? 03:56.049 --> 03:56.229 Now. 03:58.529 --> 03:59.009 Okay. 04:00.890 --> 04:01.630 Which page? 04:03.070 --> 04:04.071 Right page halfway down. 04:07.752 --> 04:15.133 I'm the guy who is famous at the hospital because I have to have two catheters put in since I piss so much. 04:19.355 --> 04:19.915 There you go. 04:20.055 --> 04:20.535 There you go. 04:21.543 --> 04:23.444 And there's actually a picture. 04:23.464 --> 04:26.085 That doesn't seem real. 04:26.985 --> 04:28.906 This is in the section entitled Piss. 04:30.167 --> 04:41.731 And the picture appears to be of a man with a pimp cane walking down a hospital aisle with two catheters presumably under his hospital robe. 04:41.811 --> 04:42.091 Anyway. 04:44.732 --> 04:45.573 There you go. 04:45.593 --> 04:45.793 Okay. 04:46.213 --> 04:46.593 Moving on. 04:47.233 --> 04:47.754 Okay. 04:47.934 --> 04:48.594 Moving on. 04:49.394 --> 04:50.795 Now that we've gotten that out of the way. 04:51.563 --> 04:58.185 Has anybody seen that fucking, that fucking, what's the, I've massively demonetized. 04:58.245 --> 04:59.105 Demonetized again. 04:59.325 --> 05:00.865 Fuck twice. 05:00.885 --> 05:01.985 They're the sad side. 05:02.005 --> 05:03.466 They're the word fuck. 05:05.526 --> 05:06.466 Shit, what's that film? 05:06.806 --> 05:13.708 The one that's just come out that's all like, oh, we really want to win an Oscar for this with Bradley Cooper. 05:16.354 --> 05:17.034 No, not Offenheimer. 05:17.054 --> 05:17.554 Bradley Cooper. 05:17.614 --> 05:19.195 He probably will actually win an Oscar. 05:19.655 --> 05:20.135 Barbie? 05:20.355 --> 05:21.956 Man, Bradley Cooper. 05:22.176 --> 05:23.076 I mean, that might as well. 05:23.176 --> 05:23.517 Who knows? 05:23.557 --> 05:24.297 Fucking knows. 05:24.497 --> 05:25.257 No, no. 05:25.337 --> 05:28.458 The one about Maestro, about Leonard Bernstein. 05:28.538 --> 05:28.958 You seen it? 05:29.859 --> 05:30.039 No. 05:31.839 --> 05:32.600 Not going to lie. 05:32.900 --> 05:38.862 If I saw that particular name on a movie, I would not watch it. 05:41.359 --> 06:02.612 no yeah it's an automatic no from me that's a very that's very surprising now i thought you'd have gravitated towards um well no i mean the irony is right it's kind of um i guess i guess because of its adjacency to higher it considers itself higher when it is in fact just 06:05.256 --> 06:06.857 It is what it is. 06:06.897 --> 06:15.580 The main thing is, it feels like the whole point of the film is that you are supposed to like and identify with Lana Bernstein. 06:16.520 --> 06:17.420 I think that's the point. 06:19.161 --> 06:20.041 You would think, right? 06:20.542 --> 06:21.622 Yeah, I think that's the point. 06:21.762 --> 06:26.964 It's super well acted, but you're just like, he's a fucking prick. 06:28.410 --> 06:32.055 He's got some kind of narcissistic personality disorder. 06:32.095 --> 06:36.661 And to be fair to Bradley Cooper, literally, I was just like... 06:37.872 --> 07:03.105 his acting is good enough that you're like wow that that that is somebody with a narcissistic personality disorder and then right at the end of the film you're like oh yeah that was played by uh what's his face um and and he directed it and he wrote it yeah i mean like fair game to him it's like it's like well put together but it's just such a it's about 20 minutes too long you're obviously supposed to care about him a lot and i think most people probably don't 07:05.481 --> 07:09.583 How many movies do you really need to have about narcissistic assholes, geniuses? 07:10.563 --> 07:12.764 It's like every fucking one, right? 07:12.784 --> 07:14.224 Apparently fucking lots, right? 07:14.324 --> 07:14.544 Yeah. 07:15.345 --> 07:17.585 He's just such an asshole. 07:17.905 --> 07:18.105 Right. 07:18.746 --> 07:20.666 Everybody thinks he's an asshole, but he's a genius. 07:20.766 --> 07:22.487 Then let me guess, at the end, everybody loves him. 07:23.007 --> 07:26.188 It's the same fucking arc for the rest of their lives. 07:26.848 --> 07:31.570 He's an asshole and a genius. 07:32.366 --> 07:33.507 He's an asshole and a genius. 07:33.607 --> 07:42.952 And, like, because his wife gets cancer and he, like, takes time out of his schedule to not let her die alone, he's a fucking legend. 07:43.052 --> 07:50.697 It's like, well, maybe you should have not been an asshole for, like, before the cancer, you fucking idiot. 07:51.818 --> 07:52.258 I don't know. 07:52.338 --> 07:55.642 Like, obviously, it's probably sensationalized or whatever, but it doesn't. 07:56.342 --> 07:58.104 It's super weird because it is written. 07:58.124 --> 08:04.051 It is written like you're supposed to really like and really like and respect Leonard Bernstein. 08:05.352 --> 08:06.373 But it's acted. 08:06.393 --> 08:12.760 It is acted like you are supposed to find him a domineering narcissistic bully. 08:12.780 --> 08:13.521 Yeah. 08:14.048 --> 08:24.435 like an emotionally manipulative, distant father figure, weird, bullying, egomaniac, which is maybe the point. 08:24.695 --> 08:24.976 I don't know. 08:26.136 --> 08:36.964 However, I would say just for the acting, it is actually, you know, the fact it provoked this irritated response for me is probably an indication that it is worth seeing film anyway. 08:37.024 --> 08:37.744 It sounds like it, yeah. 08:38.065 --> 08:39.045 Oh, is this a response? 08:40.666 --> 08:41.187 Have you seen it? 08:42.812 --> 08:42.993 Maestro. 08:43.053 --> 08:43.375 It is it. 08:43.918 --> 08:44.059 Yeah. 08:44.099 --> 08:45.126 Yeah, I had no idea. 08:49.039 --> 08:52.382 I've been trying to watch up the things that are kind of up for thing. 08:52.782 --> 08:55.464 Like my other half is really into movies. 08:55.884 --> 08:57.826 They're like the worst ones to watch. 08:58.907 --> 09:01.609 What, the ones that are up for heavy or whatever else? 09:01.729 --> 09:02.249 That depends. 09:02.930 --> 09:06.732 I mean, you can't be just like every single one, but you can sort through them a little bit. 09:06.752 --> 09:08.093 Yeah, yeah, yeah. 09:08.714 --> 09:17.461 I mean, to be honest, quite often the ones that are in slightly weirder categories, not weirder, that's not fair, but like the foreign language category and stuff like that, 09:18.161 --> 09:31.916 animated category stuff like that they're often because they're like the creme de la creme of like an entire sub genre you know potentially yeah um it's like the portal works yeah 09:34.744 --> 09:34.904 Yeah. 09:35.545 --> 09:38.005 I don't know what to do with that. 09:38.025 --> 09:39.306 Yeah, same thing. 09:39.386 --> 09:40.406 Yeah, sure. 09:40.446 --> 09:41.567 Yeah, sure, whatever. 09:41.827 --> 09:43.127 Yeah, let's go with it. 09:43.147 --> 09:46.228 So is everybody doing Cosmosm upgrades or what? 09:47.008 --> 09:47.729 Yeah. 09:47.929 --> 09:49.689 So are we all upgrading or what? 09:50.670 --> 09:53.230 I had so many alarms overnight. 09:53.670 --> 09:57.932 I had some good news yesterday and then I thought, yeah, it's going to be a great, great night. 09:57.972 --> 09:59.072 I'm going to sleep well on that. 09:59.132 --> 10:01.173 And there's just fucking alarms all night. 10:01.684 --> 10:02.084 What did you have? 10:02.264 --> 10:02.765 Oh, Juno. 10:02.825 --> 10:03.585 Well, Juno halted. 10:03.985 --> 10:08.248 Well, Juno halted, and then I had an issue with some other ones. 10:09.948 --> 10:12.050 Everything upgrade-related. 10:12.070 --> 10:15.792 I don't know about this. 10:15.872 --> 10:21.194 So when's the injective upgrade, the normal upgrade, not like the wasn't upgrade? 10:21.214 --> 10:24.296 Because it's a little bit funny with those frigging libraries. 10:24.756 --> 10:27.118 Tomorrow at 3 p.m. 10:27.198 --> 10:27.578 UTC. 10:29.142 --> 10:31.263 So whatever the hell that is. 10:31.904 --> 10:33.044 That's 2 a.m. 10:34.325 --> 10:34.625 Figures. 10:35.926 --> 10:36.206 3 a.m. 10:36.667 --> 10:42.150 So running with the library in the Cosmovisor. 10:42.210 --> 10:43.451 I just rewrote that too, actually. 10:43.531 --> 10:44.311 Yeah, I did the same thing. 10:44.331 --> 10:53.517 The only thing that's annoying is I don't know if I should leave one in a regular library location since you can't really run off the command line unless you're actually specifically calling up the library. 10:54.037 --> 10:56.258 Well, you can't copy it there because of the fucking... 10:57.919 --> 11:17.732 fucking what it's in use like you can't put it in the regular library because it's in use unless you put it in like one of the other paths i guess but then it'd be a conflict right it's going to pick one like whichever is the precedent what are you talking about i'm just talking about having one of the default as well because if you want to run up the command line without calling out the library on the command line 11:18.243 --> 11:19.764 it would actually just use the one that's sitting there. 11:19.804 --> 11:23.747 Like if you want to use CLI commands or do a vote or do this or do that, like having one separate. 11:24.547 --> 11:25.488 Yeah, I just meant. 11:26.329 --> 11:29.251 So you rewrote your Ansible for just the injective, did you? 11:29.611 --> 11:29.791 Yeah. 11:30.151 --> 11:36.055 Well, I mean, anything that has that WASM X, I think that it looks for that file. 11:37.136 --> 11:44.101 And then if it has that file, if it's WASM related, then it adds a service line in the service config and it also moves it to the folder and all that kind of shit. 11:44.758 --> 11:46.078 Yeah, that does all that. 11:46.158 --> 11:48.399 But this doesn't run off the command line. 11:48.979 --> 11:59.302 And also I run like checks in that Ansible and those all fail because there's nothing, unless I'm calling out the library file, but then I got to deal, like it's like a fucking circle of how deep do I want to go with this and how much do I care? 11:59.322 --> 12:01.363 Checks, who does checks? 12:02.183 --> 12:06.964 I do checks and like upgrades and make sure that the version that's upgraded is in the right folder and like all that shit. 12:06.984 --> 12:07.624 Spray and pray. 12:10.565 --> 12:13.726 Have you guys, who's the one that asked you this? 12:15.620 --> 12:39.800 shit it was something about ansible um ah fuck it i'll remember later on it's good podcast stuff yeah good podcast so far yeah injectives tomorrow evmos i guess is coming oh did you did you do something for um eight did you do some ansible for dy dx you need some they're they're like um 12:41.604 --> 12:42.384 What would you say? 12:42.604 --> 12:54.428 Like names, the naming of their branches is kind of annoying when you want to check out their node versions because it's got that protocol slash in front of it. 12:54.448 --> 12:56.449 What would you guys do for that? 12:57.449 --> 12:58.290 I don't know. 12:58.350 --> 12:59.890 I don't even remember. 13:00.650 --> 13:05.752 Well, the chain registry only registers the... 13:09.488 --> 13:15.917 like the name, like V 3.1.0, for example, whereas it's protocol slash V 3.1.0. 13:16.918 --> 13:19.662 So presumably you just handle that differently. 13:20.844 --> 13:21.004 Yeah. 13:21.024 --> 13:24.288 If it's DYDX, just CD into protocol and do that instead. 13:25.140 --> 13:51.521 yeah so you just got like a separate handler for dydx or something yeah separate uh yeah well i built the handlers to i helped i built handlers for build arguments and folder source so if those variables exist in the definition file for that chain then it'll it'll use those because i think there was something else that had like it couldn't use make install it hey use make build with something other bullshit and blah blah like i hate that stupid shit that 13:52.409 --> 14:03.037 So I like pain more than you guys, obviously, because the way I would do it or do it is I would not have a separate like thing for it. 14:04.178 --> 14:06.039 I would have like I wouldn't have a separate task. 14:06.179 --> 14:09.922 I have like, you know, if you specify a variable. 14:09.942 --> 14:11.043 That's what I have. 14:11.643 --> 14:14.746 Like if it's no, no, but it doesn't go to a different thing. 14:16.368 --> 14:35.842 thing like if you specify a variable for example like um you know build directory or or uh you know prefix the bin prefix or something um then in it would just like i would have a default which is nothing and then 14:36.522 --> 14:36.942 That's what I have. 14:36.982 --> 14:38.083 Like have that in the chain. 14:38.123 --> 14:39.303 So you don't have like a separate. 14:40.364 --> 14:41.484 Like a separate wet. 14:41.664 --> 14:42.945 Like a separate, like a conditional. 14:43.005 --> 14:43.705 There's no conditionals. 14:43.985 --> 14:44.245 It's just. 14:44.265 --> 14:44.486 Yeah. 14:44.526 --> 14:46.847 Like, you know, like a, when do this other. 14:47.067 --> 14:48.307 No, it's just the same thing. 14:48.327 --> 14:49.528 You just, if the variable is there. 14:49.748 --> 14:50.048 Yes. 14:50.108 --> 14:52.069 And if not, then the default is that it's not there. 14:52.109 --> 14:52.369 That's all. 14:53.221 --> 15:01.065 I find myself adding tons of shit like that, especially in Zabbix, because you've got the different chains handle some things different, like I was saying the other day with that. 15:01.945 --> 15:07.948 Fucking C. Yeah, they took away the result. 15:08.128 --> 15:13.870 So now, stuff like that, you have to add in a little bit extra for each chain. 15:14.070 --> 15:14.971 You know what's got me fucked? 15:15.131 --> 15:19.593 The commission. 15:19.633 --> 15:19.753 So... 15:21.266 --> 15:26.549 I made a, like a, what do they call them? 15:26.589 --> 15:27.690 The discovery rule? 15:28.070 --> 15:28.570 Yeah. 15:29.011 --> 15:37.156 To find all the denoms of commission and then add all of those individually into the validator. 15:38.777 --> 15:41.758 Bloody, fuck, why is my brain not working today? 15:41.778 --> 15:45.541 You mean to be able to source all commissions across all denoms of commission? 15:46.437 --> 16:08.150 yeah on that on that chain it'll put up all the commissions and all denoms but there's a problem with um what is it dydx because the usdc is like got 18 decimal places and the dydx has six yeah so 16:09.898 --> 16:23.529 Like I do have... I already had before DYDX like a multiplier for the denom. 16:23.569 --> 16:25.410 So if it was base 6, you'd just put like 6. 16:25.610 --> 16:26.991 If it was base 18, you'd put 18. 16:27.031 --> 16:27.111 But... 16:29.364 --> 16:48.372 now that there's both and it's the same discovery rule i've been struggling to figure out how to actually have different ones so i actually looked in the in all the registries everywhere to see if they had the denoms on the chain with their um 16:50.839 --> 16:53.301 They're, you know, multipliers on there. 16:53.781 --> 16:59.046 And they do, except they're in different places. 16:59.586 --> 17:01.848 Well, some of them have them, but they're in different places. 17:02.268 --> 17:04.910 And if you query them on chain, they're in different places as well. 17:04.990 --> 17:07.292 So there's like, you have to query the native chain 17:07.452 --> 17:09.614 And then you can query like other ones. 17:09.654 --> 17:10.294 I can't remember how. 17:10.314 --> 17:15.779 The bank denoms are different to like the, you know, WASM denoms or whatever. 17:15.799 --> 17:17.860 They're in different places and some don't exist. 17:18.521 --> 17:27.768 So I've been struggling to find a place where I can get all of them in one place unless I write like a third-party API to go and collect them from all the different places. 17:28.489 --> 17:30.891 Zabbix won't be able to get them from different places. 17:30.911 --> 17:34.213 They have to be from the one source if you're using discovery rules. 17:35.166 --> 17:37.888 So anyway, that's my current dilemma. 17:38.128 --> 17:41.890 Did you figure out my little data folder thing that you're going to do? 17:42.410 --> 17:42.870 What was that? 17:43.751 --> 17:44.471 Size of the folder. 17:45.452 --> 17:45.892 Oh, I know. 17:46.012 --> 17:50.194 Like I had that implemented previously, but it would literally crash nodes. 17:50.734 --> 18:01.100 It was just, I don't know why, because when you do it in the CLI, if you use DU in the CLI, it doesn't seem that strenuous on the hardware, on the node. 18:02.961 --> 18:03.761 or on the server. 18:04.222 --> 18:11.885 But when you use the built-in Zabbix one for a directory, it just strains the shit out of it. 18:11.985 --> 18:12.985 I don't know what it's doing. 18:13.966 --> 18:15.567 It's got a couple of options that it adds. 18:15.907 --> 18:21.069 Well, it says that the operation it's doing is like DU, it says. 18:21.089 --> 18:22.470 Okay. 18:22.830 --> 18:28.712 But I've never gotten an accurate... Even when I've let it go, I've never really gotten an accurate result out of it anyway. 18:29.633 --> 18:29.833 But... 18:31.139 --> 18:36.020 I think we have to make a user param for it and just use DU is probably the answer. 18:36.620 --> 18:37.740 Okay, we'll figure it out. 18:38.201 --> 18:39.381 Yeah, I mean, it's not too hard. 18:39.681 --> 18:42.642 It's a pain using user params. 18:42.802 --> 18:46.542 It's much nicer to not use them if you can use built-in things. 18:46.662 --> 18:49.163 I've never used either. 18:50.043 --> 18:51.583 Well, I mean, I've got user params anyway. 18:51.603 --> 18:53.724 Do you not use the validator user params? 18:55.784 --> 18:57.205 You mean like, I think I do. 18:57.405 --> 18:58.465 Yeah, I must somewhere. 18:59.639 --> 19:09.022 Well, I just added to my Ansible to pull a public user params for the ZFS stuff. 19:09.262 --> 19:12.063 So you can expose the arc and Z pull stuff. 19:15.744 --> 19:15.984 Yeah. 19:16.004 --> 19:16.204 Okay. 19:16.364 --> 19:17.445 I don't know what that means. 19:17.765 --> 19:20.886 Well, so you can monitor your ZFS. 19:21.106 --> 19:23.987 You just said you started using ZFS on Stargaze, right? 19:24.527 --> 19:27.268 No, we've been using it for a while, but just on the new machine too. 19:28.470 --> 19:38.486 yeah okay well you can you can monitor the zfs pools in um in zabbix if you use like there's no built-in 19:39.981 --> 20:04.822 um thing for it so you got to use a third party one which is kind of a pain gotcha trust someone else yeah yeah yeah anyway i can see that everyone's thoroughly enthused with this line of questioning so yeah so anyway so it looks like we're just doing a bunch of node upgrades and then we'll try what else is going on that's that's somewhat validator opportunity we're just doing we're doing right now i'm just helping out with a ton of 20:05.723 --> 20:14.335 uh, mints on the, on the say side, um, which has been taking us a lot of time, but that's been really kind of interesting with the projects that are minting. 20:14.655 --> 20:14.776 Yeah. 20:14.796 --> 20:14.976 Yeah. 20:15.417 --> 20:20.984 Cause I think I've sent a few your way when they come asking for like RPC just for the mint. 20:21.265 --> 20:21.645 I'm like, yeah, 20:23.046 --> 20:23.547 Yeah. 20:24.127 --> 20:24.587 Yeah. 20:24.948 --> 20:25.208 Yeah. 20:25.528 --> 20:30.291 So we've had it's actually been pretty interesting because we've had some really high. 20:30.311 --> 20:37.595 I mean, those those teams get a lot of eyeballs and there's a lot of like unique users that hit those things. 20:38.295 --> 21:01.882 um there's just like they go very fast though like there's usually like an og and a you know a small white list type of thing and that takes half of it and then the other half goes within i don't know three four minutes tops so yesterday we were serving we were serving rbc requests off the say array at like 30 000 requests a second that's the most requests we've ever served like all 200s like hauling ass yeah and um 21:02.822 --> 21:04.343 And which is totally inefficient, I understand. 21:04.363 --> 21:08.065 But like it is it was that's the most we've ever served on any chain anywhere. 21:08.826 --> 21:14.349 Is that still you've got nine behind that one still? 21:14.369 --> 21:14.349 11. 21:15.770 --> 21:16.691 Oh, 11 now, Jesus. 21:17.011 --> 21:17.251 Yeah. 21:17.451 --> 21:18.532 But that depends on where it is. 21:18.592 --> 21:24.776 And like also each each mint kind of goes in different a little bit slightly different regionally, which changes the traffic to each of those. 21:25.479 --> 21:28.121 But yeah, that's been a lot of fun. 21:28.141 --> 21:29.622 And they've been actually going very, very well. 21:29.682 --> 21:31.103 So that's been really good. 21:31.143 --> 21:41.649 And so now there's a ton of teams launching and whatever else, which is- Are these all, these sayments, are they all- Yeah, these are all say. 21:42.590 --> 21:46.533 They're all just their own things, or are they all on one particular launchpad? 21:47.435 --> 21:49.075 They're all, so they all mint. 21:49.676 --> 21:53.257 There's a launchpad called Lighthouse, which is done by the WeBump guys. 21:53.277 --> 21:54.917 It's WeBump.xyz. 21:55.497 --> 22:02.299 And they have a Lighthouse, which I guess is kind of, it's a tool set. 22:02.439 --> 22:04.220 I guess it's basically a minting tool set. 22:04.520 --> 22:05.700 I think that's maybe what it is. 22:06.240 --> 22:13.182 Yeah, it's like a all-in-one sort of NFT launch thing. 22:13.422 --> 22:16.143 And it's just like you put your own pictures in there, change the format. 22:17.023 --> 22:18.784 The fees and everything else. 22:19.365 --> 22:21.066 Aim and fees and all that type of bullshit a little bit. 22:21.126 --> 22:21.806 Yeah, yeah. 22:22.407 --> 22:24.628 And so those have been primarily launching through those. 22:24.648 --> 22:27.570 So they run their own either Vercel sites or wherever they sit, right? 22:28.891 --> 22:35.256 And then after the Mint, then I think the largest NFT infrastructure. 22:35.336 --> 22:38.518 I know Stargaze is building an outpost, or at least they've been talking about, which would be really cool. 22:39.227 --> 22:43.268 Um, but, um, I think right now it's pallet exchange is probably the largest. 22:43.848 --> 22:48.569 And so they ended up in pallet and then we're, we're servicing pallets, pallet requests as well, um, behind the scenes. 22:48.629 --> 22:53.110 And so that, that also then after that, then that turns into, you know, a regular marketplace type of thing. 22:54.171 --> 23:00.732 Um, so, but w what, uh, wait, hang on smart. 23:00.832 --> 23:02.453 There are smart contracts on say, right? 23:03.093 --> 23:05.754 Are they EVM smart contracts? 23:06.854 --> 23:07.594 Uh, no, there wasn't. 23:09.935 --> 23:38.014 right well which which version which okay if there wasn't but which which wasn't i don't know all right like one of these two would know schultz he knows schultz he doesn't know i mean like is it because because the evm is wasm eventually right but is it solid is say solidity i don't know i'll look it up i'm not really sure 23:40.339 --> 23:51.108 So I won't talk commercially, but these projects, are they giving you a plug? 23:51.128 --> 23:52.469 Yeah. 23:52.789 --> 23:54.070 Is that part of the deal, a plug? 23:54.090 --> 23:56.512 Yeah, sure. 23:56.992 --> 24:01.256 You are doing exceptionally well in unique delegators. 24:02.065 --> 24:22.681 am i yeah well that's good by a fair margin compared to you're like 5x your closest uh really where do you get that where do you get that type of number uh is that in the notes guru thing no no that's in that's on min scan all the way to the right you kind of have to expand your screen out a little bit all the way to the right but you have 24:23.201 --> 24:38.788 So your closest rival, besides the SayZero, which was at the top of the list for a long time, but your closest rival is Stakesedo at about 5,000 unique delegators, and you've got closer to 16,000 unique delegators. 24:39.149 --> 24:42.230 Which is weird because our overall VP, I don't think, has moved. 24:43.351 --> 24:45.212 So it must be a decimals. 24:45.452 --> 24:46.192 Which is totally fine. 24:46.372 --> 24:46.892 It does. 24:46.972 --> 24:47.292 It does. 24:48.693 --> 24:49.714 Yeah, no, it's all good. 24:50.095 --> 24:50.956 It's Microwale. 24:51.236 --> 24:52.477 It's all the Microwales. 24:52.617 --> 24:54.659 Yeah, that's okay. 24:54.679 --> 24:55.460 16,000 wallets for one. 24:56.221 --> 24:56.621 That's cool. 24:56.701 --> 24:58.923 Yeah, the Microwale is coming for you, my friend. 25:01.646 --> 25:07.572 Keep up these mini mints and, you know, you might have like 100,000 in a week. 25:07.592 --> 25:08.032 Who knows? 25:08.432 --> 25:09.834 Yeah, they've been doing pretty well. 25:09.854 --> 25:10.434 So... 25:13.837 --> 25:17.200 Yeah, it's, it's, it's, uh, it's anyway, it's been fun. 25:17.240 --> 25:29.312 Like we've, you know, this say ray has been around for a while and it's been doing well, but, um, it's cool to actually, I mean, it's actually really focused us on engineering, at least in terms of the balancers and like rewriting a bunch of shit and like how to work queuing and all that kind of stuff. 25:29.332 --> 25:30.994 So that, that's been actually really interesting, uh, 25:31.654 --> 25:33.036 So, no, we can do more with that too. 25:33.056 --> 25:36.278 Cause I know you run some of the same stuff that we do on the HA proxy side. 25:36.318 --> 25:39.021 So I've totally rewritten all that and how we approach it. 25:39.361 --> 25:39.621 So that's. 25:39.641 --> 25:40.002 Oh, really? 25:40.622 --> 25:42.824 Well, that'll be interesting to see. 25:42.844 --> 25:44.385 Yeah. 25:44.425 --> 25:56.196 Cause I remember you had like problems straight off the bat with like when injective came over with too many connections and and then, yeah, but the queuing stuff is interesting. 25:56.896 --> 26:00.118 Well, injective also like that for some reason that node like locks up, it gives up. 26:00.198 --> 26:07.102 I think we talked about a couple weeks ago, but like after like so many like if it gets overwhelmed with RPC connections or something, the thing just it just stops. 26:07.122 --> 26:09.824 It's just it gives up, which say does not do. 26:10.524 --> 26:11.785 But we still I still limit it. 26:12.645 --> 26:13.206 So then I can. 26:13.826 --> 26:14.726 That's why I start then. 26:14.906 --> 26:17.368 Then actually that allows HAProxy to queue those. 26:18.018 --> 26:21.821 And HAProxy can queue like 50, 100,000 requests, right? 26:21.881 --> 26:26.725 It'll just queue them up and then just do them, you know, it'll just fight for them out, which is cool. 26:26.745 --> 26:27.865 So you don't kill these nodes. 26:28.666 --> 26:39.754 I remember in the say test net, like, yeah, man, the, like they were doing 300 million a day or something. 26:40.275 --> 26:42.577 The, the RPCs on that. 26:42.597 --> 26:45.679 Well, my RPCs anyway, there's 300 million a day. 26:46.561 --> 26:48.442 Like 200 million or 300 million or something like that? 26:48.462 --> 26:49.603 That's a lot. 26:49.623 --> 26:49.783 Yeah. 26:50.903 --> 26:52.564 There's a lot of requests coming through there. 26:52.805 --> 26:53.845 Like heaps. 26:54.546 --> 27:03.130 And that was not... Like what I'm saying is that the say daemon seems to be like really pretty good for answering requests. 27:03.571 --> 27:05.572 I'm not sure if they've done some tweaks in there or something, but... 27:06.454 --> 27:08.615 it's definitely like can handle a lot. 27:09.115 --> 27:10.216 Yeah. 27:10.236 --> 27:10.536 11 nodes. 27:10.556 --> 27:11.116 That's a lot. 27:12.336 --> 27:12.577 Yeah. 27:12.697 --> 27:12.857 Yeah. 27:13.357 --> 27:15.678 But right now we're doing, we're doing 2 billion a week. 27:16.918 --> 27:17.238 That's insane. 27:17.258 --> 27:20.020 So, I mean, that's, that's, that's still less than 300 million a day. 27:20.860 --> 27:21.040 Right. 27:21.100 --> 27:27.583 So, um, but 2 billion a week, like actually is like, it's a lot. 27:28.063 --> 27:33.145 And over, even overnight, like it's overnight, it gets down to only, you know, under a thousand a second, but, um, 27:33.585 --> 27:38.914 But like get up to 3000 or I'm sorry, 30,000 for a mint is, is, uh, is not. 27:38.934 --> 27:47.989 So what's crazy is that that is like, um, it's just night and day compared to, for example, a month ago, right? 27:49.096 --> 27:49.296 Yes. 27:50.177 --> 27:50.337 Yeah. 27:50.437 --> 28:04.272 It's probably, it's probably four X that, but, but also Astroport drove a lot of traffic and then a couple other projects drove a lot of traffic, but yes, it is, it is night and day, but mint traffic is very different than like, then, you know, like Astroport, 28:05.533 --> 28:11.675 Really, if you have a good DAP or if you have a NFT marketplace, you really should not have that much traffic. 28:11.795 --> 28:14.316 Like NFT marketplace should be indexed. 28:14.536 --> 28:16.396 It should be hitting indexers with the caches, right? 28:16.436 --> 28:21.318 There's nothing there that's changing that fast where you really need to pound this fucking blockchain all that much. 28:21.898 --> 28:27.262 So yeah, like a good DAP on the back end uses your GRPC and does some indexing. 28:27.642 --> 28:27.922 That's right. 28:28.122 --> 28:30.824 As long as the indexer and the indexer traffic is very small, right? 28:30.884 --> 28:35.788 As long as it's as long as it's keeping up with with all transactions and all blocked data, like that's not much, right? 28:35.948 --> 28:42.532 And so and then the indexers get built and the caches are in there and like that's where the logic is and the smartness is similar to the NFT side. 28:42.552 --> 28:45.634 Like there's so much there could be cached that. 28:45.674 --> 28:50.558 Yeah, but then it's not going to be cached by most people unless that's a function of the launchpad, because 28:51.590 --> 29:00.457 all NFT mints make all their money in the mint, and then they have no business model after that, so why would they index? 29:00.677 --> 29:02.218 Why would they go to the effort of indexing? 29:02.438 --> 29:03.279 Yeah, that's what I'm saying. 29:03.339 --> 29:04.159 Mints are totally different. 29:04.420 --> 29:09.183 It's kind of like all of yours, Ansible. 29:09.603 --> 29:20.412 If there's something super custom, I tend to just write a single block of YAML in the Ansible file and then just comment it out, put a comment above it saying... 29:21.770 --> 29:36.856 only enable this for xyz special case that you want to do yeah uh i mean i guess we're like we're only maintaining like six chains so it's like a very different like scale to especially like short c i suppose or null but 29:38.729 --> 29:42.772 there's a very strong tipping point where you get to, okay, need to template everything. 29:44.433 --> 29:50.137 Well, I think like, I think that would become an issue if it was more of a team environment. 29:51.058 --> 29:57.883 Just, you know, for documentation and usage, like it's easier to add a variable and document it. 29:57.923 --> 30:05.309 So if the chain has this, then add this variable under the vars and put this, this is the, you know, the options it can take. 30:06.277 --> 30:11.581 And then that way, you set it in your inventory and then it's done. 30:11.601 --> 30:15.983 There's no changing it. 30:16.023 --> 30:22.248 Yeah, but Ansible doesn't, in my experience, scale particularly well with a team bigger than two anyway. 30:23.088 --> 30:32.494 It seems to work okay for two or so people who have all the configuration stuff on their laptops and know how it works. 30:33.295 --> 30:34.075 And more than that... 30:36.940 --> 30:39.623 There's no reason why you couldn't use it with more people if you documented. 30:40.824 --> 30:48.113 Yeah, no, but you're forgetting software is completely social and documentation doesn't mean it doesn't mean a rat shit. 30:49.394 --> 30:56.602 What happens is that because Ansible is like giving a toddler a gun, what somebody has is a deadline. 30:58.487 --> 30:58.727 Right. 30:58.928 --> 31:02.631 And the deadline is in two hours and they installed the code. 31:02.691 --> 31:06.035 They read the readme in the repo for your Ansible stuff and they go, cool. 31:06.295 --> 31:07.176 I understand it. 31:07.696 --> 31:08.817 Check the inventory file. 31:08.837 --> 31:10.379 It's the example inventory file. 31:10.419 --> 31:12.381 They rename it to whatever. 31:13.042 --> 31:16.245 They run that shit and they wipe all the fucking stuff on the server. 31:18.264 --> 31:39.777 this has happened in production you know it was actually why a company i worked for backed out of using ansible for anything but the the only thing there was an ansible file for after that was literally bootstrapping a box hardening ssh and adding all of our public keys to the box like all the employees there were like 10 people there um 31:40.989 --> 31:42.610 After this incident, basically. 31:43.470 --> 31:59.918 But it's why something like Terraform becomes a better fit for a larger team because the state is much more transparently held at an external location that's not really tied to any one place, if that makes sense. 32:01.318 --> 32:07.141 The arbiter of whether or not the thing is what it says it is, is not the server or... 32:08.467 --> 32:10.748 the hardware resource that you're connecting to. 32:10.768 --> 32:14.210 It's actually like a third source of truth. 32:15.591 --> 32:27.697 But in Ansible, like you can, you can, for example, create a dynamic inventory in the, like a dynamic inventory script in Ansible that you could make, go look at a, 32:29.710 --> 32:53.170 git repo or something for the actual inventory and have it centrally maintained like you don't necessarily have to have it individually on yeah i mean that's fair but it just doesn't do that as well as terraform it just doesn't yes like terraform is like the immutable infrastructure thing and it does that one thing super super well like i don't get it wrong i like ansible i use it all the time for loads of bits and bobs but 32:54.210 --> 32:55.911 The dynamic inventories are really cool. 32:56.711 --> 32:59.632 If you can be fucking bothered scripting out a Python script. 32:59.992 --> 33:00.712 Ding, ding, ding. 33:01.312 --> 33:02.192 If you can be bothered. 33:02.212 --> 33:03.213 No, I can't. 33:03.233 --> 33:05.913 Well, I mean, the built-in ones for like me and Serp, right? 33:05.973 --> 33:06.674 Oh, and Schultz. 33:07.214 --> 33:10.715 The built-in ones are great because you can pull shit straight out of Zabbix. 33:11.195 --> 33:11.535 You just... 33:12.415 --> 33:13.256 query your Zabbix. 33:13.997 --> 33:14.618 I know I should do that. 33:14.638 --> 33:15.098 I don't do that. 33:15.659 --> 33:16.160 It's a good idea. 33:16.900 --> 33:19.784 Yeah, well, you use it to put shit into your Zabbix. 33:19.804 --> 33:21.786 So why don't you use it to pull shit out of you? 33:22.187 --> 33:24.609 Particularly useful when you're deleting shit. 33:24.649 --> 33:29.375 So if you've got clean up Ansible to get rid of nodes, you can just call it a 33:30.439 --> 33:48.077 can call it up out of your um your zabbix inventory like from your host names and then it'll just destroy everything associated with those tags and then and then kill that actual uh item as well or disable it or whatever yeah i have like i have like no destroy ansible 33:50.042 --> 33:50.462 I should do that. 33:50.943 --> 33:53.084 It's a good idea. 33:53.924 --> 33:55.085 It's a good idea. 33:55.105 --> 33:55.365 Good idea. 33:55.445 --> 34:02.368 Or even detect if the inventory changes in your 34:03.843 --> 34:22.902 in your well you could have um you could actually use this there's a event-driven ansible you could use your zabbix you could change a tag to delete for example and then use um alerts to your event-driven ansible when there's a tag 34:23.803 --> 34:33.348 delete shows up, it can tell the event-driven Ansible to then take that inventory item, delete everything associated with its tags, and then fuck it off out of Zabbix. 34:33.968 --> 34:34.148 Right. 34:34.869 --> 34:43.413 It's just occurred to me, number one, if we take on one more chain, I'm going to have to finally cave and set up Zabbix. 34:44.254 --> 34:50.317 Number two, we are officially now 34:51.664 --> 35:19.481 more than the validator podcast i think we're just the bare metal operations neckbeard podcast aren't we it's not like because it's not even it's not even like this isn't i tried to get a neckbeard it's it's not an infrastructure podcast it's not an enterprise infrastructure because it's much too yolo for that it's much too dgen but it's something it's something not officially sanctioned i don't know and it involves neckbeards um 35:21.693 --> 35:22.854 Shall we talk about some news? 35:23.394 --> 35:31.521 Yeah, actually there is, um, I think there's, there's one in for you at the top now. 35:34.633 --> 35:57.485 uh okay he's not got the spreadsheet up fucking sim swap i think i think all that piece is the sim swap that was a bit of a guess i think but the end result is the same i was at the bank yesterday right before we did the news oh were you having a bank run no it was kind of cool when you participate one aren't they 35:58.339 --> 36:03.882 I have a problem with like none of the banks will do all of the things I want to do. 36:04.003 --> 36:05.724 Some do some things, some do others. 36:06.264 --> 36:15.269 Some you have to like go into the bank and make a phone call or go into the bank and see someone and then they'll have someone from the corporate people call you back. 36:15.370 --> 36:20.052 I just want a bank that I can go into and do shit at or just do everything on the web app, right? 36:20.993 --> 36:24.855 And so I was at this bank and they're like, man, you can do all of this shit that you want to do on the web app. 36:24.975 --> 36:25.656 And I'm like, all right. 36:26.365 --> 36:27.205 Let's talk about that. 36:28.206 --> 36:34.829 And I said, first of all, what are your security procedures for your web app and your phone apps? 36:35.689 --> 36:36.489 And they're like, oh. 36:36.749 --> 36:37.670 Who the fuck did you ask that? 36:39.209 --> 36:39.970 Who'd you ask that to? 36:42.071 --> 36:43.932 Somebody randomly works there. 36:44.612 --> 36:46.594 No, the business banker. 36:46.674 --> 36:48.034 How the fuck is that person going to know? 36:48.054 --> 36:50.816 That person's not going to know fucking shit. 36:50.856 --> 36:52.417 Fucking shit. 36:52.757 --> 36:55.979 So she told me, she's like... It's very secure. 36:57.140 --> 37:00.461 She's like, oh, we've got SMS security and fucking you can get a token. 37:02.202 --> 37:30.811 in some cases you can get a token i'm like you've got sms security for your fucking your money okay so what we've established is noel's big and clever and the poor person that's exactly right it's more than stupid he asked the question goes cms cms cms they said that's the best did you know probably that was gonna be the answer yeah exactly uh so anyway i walked out i said i'm not having that 37:33.554 --> 37:40.262 So my current bank has a, you know, like an app locked to your hardware identity on your phone. 37:40.282 --> 37:43.165 I mean, that's probably the best you're going to get out of a bank at this point. 37:44.086 --> 37:46.069 And so I have a YubiKey for my bank. 37:48.331 --> 37:49.071 You have a YubiKey? 37:49.331 --> 37:49.491 Yeah. 37:50.512 --> 37:51.092 Yeah, that's nice. 37:51.632 --> 37:52.293 Yeah. 37:53.133 --> 38:00.236 So, yeah, I mean, some banks will send you the old ass token that you carry around with you. 38:00.316 --> 38:02.697 It's like it's the same as the other shit. 38:02.997 --> 38:04.898 It's a hard TOTP token, right? 38:05.138 --> 38:05.898 Which is not bad, actually. 38:05.918 --> 38:06.518 That's okay, too. 38:07.039 --> 38:08.579 No, but it's a fucking pain in the ass. 38:08.959 --> 38:09.139 Yeah. 38:09.580 --> 38:10.180 It's secure, though. 38:11.720 --> 38:13.781 Until someone just looks at the screen on it. 38:15.082 --> 38:15.302 Sure. 38:15.382 --> 38:17.843 If all those things are together, then yes, exactly. 38:18.479 --> 38:24.660 Yeah, so they're pulling your fingernails out for your password and then just look at your little thing and you're like, I'll be there then. 38:26.141 --> 38:28.801 But anyway, it's just a pain to carry around. 38:28.861 --> 38:29.902 It's like a ledger, right? 38:29.942 --> 38:31.562 No one wants to carry around a ledger. 38:32.522 --> 38:35.923 Well, you just leave one in the office and you leave one at home and you're done. 38:36.963 --> 38:37.523 Yeah, you can. 38:37.543 --> 38:40.364 You can register the same one originally. 38:40.958 --> 38:44.741 At least you can't get the TOTP code out of it. 38:45.041 --> 38:47.743 I'm not talking about an RSA key fob. 38:47.803 --> 38:53.628 I'm talking about one of those two-factor number generators. 38:54.008 --> 38:58.912 It's got the ones with a little keypad. 39:00.362 --> 39:00.882 The keypad? 39:01.262 --> 39:03.023 No. 39:03.043 --> 39:05.444 It's super common over here for like 15 years. 39:06.404 --> 39:08.564 Your bank gives you one for getting into your online banking. 39:08.865 --> 39:23.369 When it says, oh, verify this, you'll turn it on, you'll put verify in, then you'll put like a... It's situational for like a payment. 39:23.449 --> 39:26.410 It might be the receiving account if it's your... 39:27.366 --> 39:34.451 If it's subject to your account, it might be your account number or something like that. 39:35.672 --> 39:37.694 I mean, it's presumably just a one-way hash, right? 39:38.114 --> 39:41.476 And then it's just going to hash some element of that and then check it against something in their system. 39:42.277 --> 39:43.498 Yeah. 39:43.518 --> 39:50.423 I think it must be something like RSA or proprietary under the hood. 39:51.252 --> 39:57.078 Because the whole point is that you can't an attacker shouldn't have the ability to take 39:58.522 --> 40:06.106 the number that they read off of your screen, but over your shoulder in a coffee shop, and then be able to hash that into something that would be acceptable to the bank, right? 40:08.087 --> 40:08.287 Yeah. 40:08.307 --> 40:13.249 I mean, you're, you're reading a code and using that code input and it's generating an output, right? 40:13.269 --> 40:17.732 It's like a, it's a salt and a, and some sort of hash or something like that. 40:17.772 --> 40:17.912 Yeah. 40:17.932 --> 40:19.332 It's a key salt type structure. 40:19.352 --> 40:21.193 And then it eventually kicks out of code. 40:21.213 --> 40:21.353 Right. 40:21.413 --> 40:22.254 But I mean, back to, 40:22.894 --> 40:42.991 back to null's lead pipe situation still fucking works right yeah exactly yeah so the the news is yes you ask the person at the bank then what do you do if somebody hits me with a hammer and asks me for my password i thought is this the same bank that was going to walk you down the street 40:44.480 --> 40:46.521 No, that's the bank with the actual good security. 40:46.541 --> 40:46.901 Okay. 40:46.941 --> 40:47.581 All right. 40:48.642 --> 40:50.022 This one, they don't walk you down the street. 40:50.042 --> 40:51.483 They're like, here's a phone. 40:52.043 --> 41:03.367 So the problem with this other bank that's got the actual good security and walks you down the street is that they're like customer service from the corporate sucks and their procedures suck. 41:04.227 --> 41:17.571 Like, why would you have to go into a bank, ask to do something and then wait for someone from corporate to call you back and then have to go into the fucking bank again to sign the piece of paper or do the transfer or whatever? 41:17.591 --> 41:19.012 It's just dumb. 41:20.812 --> 41:23.293 Like, identify me and then just do it. 41:25.746 --> 41:35.671 Well, we have to do that for one of our banks, except the only difference is the corporate person, I guess, in that description is the business banking person at the branch. 41:36.611 --> 41:41.513 Yeah, well, when I say corporate, I mean the business bank is from the building in Sydney. 41:42.574 --> 41:44.495 Bank Security Talk, only here on Game of Nodes. 41:45.245 --> 41:48.227 Yeah, I mean, this has been a real hot episode. 41:48.467 --> 41:52.670 At least 30 minutes of full-on Ansible chat. 41:52.710 --> 41:55.311 Those subscriber numbers have been wheeling down. 41:55.331 --> 41:58.813 Yeah, we've gone from five viewers to four. 42:01.275 --> 42:13.042 So the news is that Gary Gensler from the SEC was hacked on Twitter or on X in some fashion. 42:13.122 --> 42:13.362 I mean... 42:14.724 --> 42:15.205 Wait, hold on. 42:15.245 --> 42:18.227 I thought it was just SEC account, not Gary Gensler. 42:18.287 --> 42:18.608 Correct. 42:18.628 --> 42:19.869 It was SEC Gov. 42:20.289 --> 42:23.352 But was it not Gary Gensler's thing? 42:23.372 --> 42:23.412 No. 42:24.113 --> 42:24.634 Well, anyway. 42:24.694 --> 42:29.839 I mean, I suppose technically Gary Gensler is the head of the SEC, but I don't think that really... Doesn't matter. 42:30.740 --> 42:37.186 So the SEC Gov X account was hacked in some fashion, and then they... 42:39.008 --> 42:44.952 put out news that the Bitcoin ETF was approved, which was bullshit. 42:45.293 --> 42:51.437 The markets went up real quick and then they had a clarifying tweet from another account or the same account. 42:52.038 --> 42:54.439 And then the markets went down. 42:54.459 --> 42:56.181 A clarifying tweet from Gary Gensler. 42:56.621 --> 42:57.742 It was from Gary Gensler. 42:57.782 --> 42:58.502 Yeah, that's it. 42:58.542 --> 43:00.904 Yeah, he just read the SEC account has been compromised. 43:01.544 --> 43:02.625 Okay, there you go. 43:02.805 --> 43:04.467 Which is a bunch of bullshit, right? 43:04.547 --> 43:05.828 Like that has to be bullshit. 43:05.848 --> 43:06.328 Yeah. 43:06.664 --> 43:11.529 So Rama is saying that someone was sim swapped, but I don't know. 43:11.549 --> 43:13.591 I didn't see any evidence of that. 43:13.812 --> 43:17.876 And due to no 2FA on the account, I could probably believe that. 43:20.639 --> 43:22.381 Did Elon talk about this at all? 43:22.501 --> 43:26.165 If somebody actually comes out and says... Gary coming out and saying... 43:27.409 --> 43:28.610 Oh, wait, there is a safety thing. 43:28.670 --> 43:33.713 We can confirm that the account SCC gov was compromised and we have completed a preliminary investigation based on our investigation. 43:33.733 --> 43:40.016 The compromise was not do any breach of access systems, but rather due to an identified individual obtaining control over a phone number. 43:40.036 --> 43:40.737 Oh, he's right. 43:41.537 --> 43:44.319 Sims associated to this SCC government account to the third party. 43:44.719 --> 43:47.040 We can further the continent did not have to factor off. 43:47.620 --> 43:48.681 No time was compromised. 43:48.721 --> 43:51.423 We encourage all users to enable this extra layer of security. 43:51.923 --> 43:53.864 There's more information, blah, blah, blah, blah, blah. 43:54.024 --> 43:55.465 This is from the safety. 43:56.676 --> 44:05.181 I mean, I'm really shocked that that's also a CYA, not to not to too much conspiracy theory, but that whole story sounds like a bunch of bullshit. 44:06.422 --> 44:07.382 The SEC. 44:07.422 --> 44:07.943 I agree. 44:08.563 --> 44:09.664 No to FAA. 44:10.284 --> 44:12.445 This is a way that you're in insider trading. 44:13.786 --> 44:22.351 The way the tweet was written, the response, the response time, like it all seemed a bit oops, somebody hit the button on something. 44:22.731 --> 44:23.412 But who knows? 44:24.332 --> 44:25.592 Very convenient, for sure. 44:25.872 --> 44:30.573 And just to call out the whole idea about being compromised, I don't know, it just seems a little bit whatever. 44:30.733 --> 44:31.934 But there you go. 44:31.994 --> 44:34.274 I'll put that in the show notes as well about from the safety. 44:34.314 --> 44:34.674 I don't know. 44:34.694 --> 44:37.575 Occam's Razor, I reckon they got compromised. 44:37.735 --> 44:52.238 And I reckon if you did some forensics of who became a very, very, very, very, very, very wealthy person in the period between the SEC tweet and Gary Gensler's tweet, you would find... 44:53.358 --> 45:13.299 uh i don't know but did it did the motive did the markets move that much though about four percent yeah there you go a few percent it's a lot for bitcoin anyway leverage that's enough that's enough that's enough to get rich and go live in the caverns i'm almost certain a lot of people got wiped out on uh on leverage as well at the same time so 45:14.600 --> 45:37.267 yeah i don't actually understand why the bitcoin etf is so important can anyone speak to that because you can already invest in bitcoin using your retirement accounts right like vanguard offers it fidelity offers it so well it is just like the big boys can flog it and you know that it's easily acts like using your 401k or or in the case of like 45:39.648 --> 46:06.103 you know super over here it's a little bit of a pain in the ass to do right there's you know you have to do things to be able to use it but in the case of like well with an etf it's just retail right people can just fucking ape in and out of that shit all day long so i think they just expect that once it hits retail in that fashion and there's just going to be volume so i mean hot take fucking you should not be able to invest a pension fund in bitcoin 46:08.688 --> 46:11.771 Oh, I think you should be able to do whatever the fuck you want with it. 46:11.891 --> 46:13.112 It's your money. 46:13.212 --> 46:13.592 Yeah. 46:13.713 --> 46:14.713 Yeah. 46:15.074 --> 46:17.175 Well, no, but I can buy Bitcoin. 46:18.877 --> 46:19.737 Like it doesn't. 46:20.318 --> 46:20.878 What the fuck? 46:20.938 --> 46:23.160 Like why? 46:23.761 --> 46:24.021 No, no. 46:24.121 --> 46:25.162 If you let people. 46:25.897 --> 46:42.085 well over here right the reason this is the reason this is important hill to die on right is because everybody not everybody most people overwhelmingly ordinary people have a pen have a pension and overwhelmingly ordinary people make billions 46:42.452 --> 46:44.313 fucking stupid investment decisions. 46:44.753 --> 46:51.076 If you let ordinary people buy Bitcoin and other shit coins, because that is where it would go. 46:51.096 --> 46:54.058 Once you open the door to Bitcoin, it will be other shit coins. 46:54.438 --> 46:56.779 They're going to get their pensions fucking liquidated. 46:57.199 --> 47:00.041 And then we're going to be in a whole fucking world of pain. 47:00.701 --> 47:00.861 Like, 47:03.072 --> 47:09.234 Pensions need to operate in the way that pensions currently operate, which is just beating inflation and being boring. 47:09.674 --> 47:11.054 That is the way they need to operate. 47:11.294 --> 47:13.155 There's a reason they're so heavily regulated. 47:13.535 --> 47:18.677 If you want to go to the crypto casino, fucking be my guest. 47:18.997 --> 47:26.779 I think a lot of that stuff where people are trying to restrict it to high net worth individuals or whatever, to me, it's a little bit like trying to regulate gambling. 47:27.219 --> 47:30.200 Regulating gambling is always kind of a losing thing because... 47:31.482 --> 47:56.375 i don't know people will find a way to gamble right it's an it's an impulse it's an addiction it's many different things to many different people but like introducing that kind of systemic risk with something that is fucking volatile is fucking insane and despite the brand you know notoriety and longevity up to this point it's only a fucking 10 year longevity well 15 year longevity i 47:58.661 --> 48:02.483 Good thing you're not building your whole life around this crypto thing. 48:03.283 --> 48:12.187 Yeah, but I don't fucking, there's no way I would ever put a cent of my retirement fund into crypto. 48:12.347 --> 48:20.911 Away from the retirement or not retirement, the one thing it does, and I think to answer Schultz's question, I think it provides some legitimacy, I think is what it does, right? 48:20.931 --> 48:27.334 And it creates some financially managed and 48:28.883 --> 48:38.287 high optic roads for many more people to invest in crypto who do not want to hold on to their own keys or deal with that bullshit. 48:38.962 --> 48:49.347 So I think it does allow my parents or your parents or somebody who would not typically be a key holder to be able to get involved in something in a small type of area. 48:49.467 --> 48:50.488 And I understand the risk of that. 48:50.928 --> 49:05.275 The other piece of it is that there's so much fucking scammy bullshit around there that it does provide at least some routes that are not necessarily safe from price dropping to zero, but they are safe from necessarily being scammed. 49:06.021 --> 49:06.201 Right. 49:06.221 --> 49:07.202 Like that's a different thing. 49:07.242 --> 49:09.683 So somebody goes to Bitcoin dot com. 49:09.703 --> 49:10.784 I don't think that fucking exists. 49:10.804 --> 49:10.944 Right. 49:10.964 --> 49:21.109 But whatever it is and siphons keys off because they don't the fuck they're doing, it does get rid of those risks like those go away because now I'm literally going to fidelity and fidelity is in charge of all that shit. 49:21.129 --> 49:23.891 And fidelity has a fucking controls to be able to manage keys. 49:24.511 --> 49:41.598 right um so right are fidelity gonna if fidelity do lose their keys right and all that money evaporates overnight it's like that it's like that hard drive that end up in that dump right i mean you can see the same thing for stock ownership right there's those type of things still 49:42.558 --> 50:09.531 fidelity has a record of my owning xyz and so do i but but they're the ones that are really the holders of that so like you're sure you're always going to have that piece of it most financial products like that there if it's their fault and they up they're regulated then they have to you know make good the losses yeah i don't know maybe maybe they do here too i don't even i have no idea because they're responsible for for like loss due to incompetence i have no idea 50:10.495 --> 50:12.936 Yeah, I mean, I think that's the case here. 50:14.476 --> 50:19.617 The whole banking regulation stuff is pretty... I guess, you know what, though? 50:19.757 --> 50:29.700 It is, now I think about it, is overwhelmingly about the difficulty of starting up and moving into that space than it is the actual... I'd have to look that up. 50:30.320 --> 50:33.881 Because I know fund tokenization is an issue at the moment. 50:33.981 --> 50:35.442 It's currently in review. 50:35.482 --> 50:36.302 There's a whole bunch of... 50:37.606 --> 50:51.119 There's like a policy document from the Investors Association, I talked about it on the podcast a few weeks ago, about fund tokenization, but that's for two main use cases, one of which is representing... 50:52.978 --> 51:17.229 real world funds as a crypto asset which is like representing an etf of blah like aberdeen or something like that as a crypto asset so so actually the fact it's a smart contract means nothing it's just allowing it to be traded in a d5 context potentially i don't know that that side of it i don't know why but that 51:18.732 --> 51:40.659 that that's part one one half of it and the other half of it is of it is i guess implicitly bringing um a basket of crypto assets into some kind of a fund uh framework right and like to be clear like fine i'm cool with that it's just the pensions piece i'm i don't know 51:41.755 --> 51:55.528 there are some, there are some situations where you just like, like if you want to invest in that fund in a investment ISA or whatever, while they're working age and they can shoulder the loss and go, fuck, that was a bad decision. 51:55.548 --> 51:57.990 Oh, well, at least it wasn't my pension account. 51:59.492 --> 52:02.775 Well, I mean, that that's, 52:03.442 --> 52:06.824 people can make stupid fucking decisions in any pension account, right? 52:06.904 --> 52:11.587 So like there's plenty of, they can buy all sorts of stupid shit in their pension account. 52:11.607 --> 52:12.348 It doesn't make a difference. 52:12.408 --> 52:14.249 Like, like that's this risk management, right? 52:14.309 --> 52:22.435 So, so I don't think you can, I don't think you necessarily need to protect people from making bad decisions to those points or it's fucking capitalism. 52:22.455 --> 52:23.175 They make bad decisions. 52:23.676 --> 52:27.378 Maybe this is, maybe this is just a bit of a cultural difference that I've stumbled upon. 52:27.418 --> 52:31.841 Like how actively do you manage pensions in the U S like, do you just 100%? 52:35.184 --> 52:38.128 Well, it's also worth mentioning that pensions aren't really used anymore. 52:38.148 --> 52:40.010 Pensions are quite rare nowadays. 52:40.451 --> 52:43.875 So like you mentioned that pensions are the overwhelming majority of retirements. 52:44.476 --> 52:45.758 That's really not true anymore. 52:45.778 --> 52:49.643 I know zero people that use a pension at this point. 52:49.983 --> 52:53.765 Now, a lot of people do consider social security pension, but it's really not. 52:53.826 --> 53:01.010 Social security is really an insurance policy on elders not living a horrible destitute life. 53:01.070 --> 53:01.691 That's all it is. 53:02.851 --> 53:05.333 All social security is invested in treasury bonds. 53:05.573 --> 53:06.914 They don't go into the market at all. 53:07.855 --> 53:09.636 So pensions are quite rare. 53:09.656 --> 53:10.736 Yeah. 53:10.756 --> 53:14.639 Usually like teachers, first responders, 53:16.809 --> 53:20.311 government workers, like those are like things that you get a specific pension for. 53:20.351 --> 53:22.332 And usually it's not them managing that pension. 53:22.352 --> 53:26.534 It might be just terminology, I think too, Frey, because it's usually not them managing that pension. 53:26.554 --> 53:29.335 It's usually a pension fund that's managed by that organization. 53:29.355 --> 53:29.475 Right. 53:29.515 --> 53:32.716 And then they have obligations and a board on what they're investing in. 53:32.736 --> 53:33.617 So nobody's throwing it. 53:33.777 --> 53:35.298 Nobody's YOLOing into that. 53:35.338 --> 53:35.458 Right. 53:35.478 --> 53:38.399 And then everybody, then they have a payment structure based off of that pension. 53:38.759 --> 53:44.342 Now, a regular retirement account, people usually manage their own retirement accounts or they're picking 53:44.975 --> 53:48.056 a set of funds or target date funds or other types of things that exist. 53:49.797 --> 53:52.138 But that is usually usually personally managed. 53:52.158 --> 53:53.699 So it's a terminology thing. 53:53.719 --> 54:01.603 So your retirement account is what we would call a sip, which is shit was that stand for doesn't matter. 54:02.663 --> 54:03.243 It's a sip. 54:03.503 --> 54:08.146 And sips are really uncommon, because everybody has to have a pension. 54:08.926 --> 54:09.086 Yeah. 54:09.645 --> 54:31.827 um we're not has to have a pension but if you're in full-time employment your employer has to provide with you the pension is the law yeah it could be a really shit pension but they have to provide you with some kind of a pension and from memory up to four percent of it you can contribute pre-tax in from your income and they have to match it it's something like that um 54:32.828 --> 54:36.790 So everybody kind of, even if it's not worth much, everybody kind of has a pension, right? 54:37.170 --> 54:37.851 Yeah. 54:38.651 --> 54:40.512 Although they're not as good as they used to be. 54:40.552 --> 54:48.596 Like it used to be the case here until relatively recently, like just before I entered the workplace, that people got final salary pensions. 54:48.656 --> 54:49.897 That was like the common thing. 54:50.557 --> 54:51.338 And that's insane. 54:51.498 --> 54:59.702 Like you would say work a place 10 years and then your pension is your final, you get final salary when you retire. 55:00.728 --> 55:01.549 And it's just a number. 55:01.589 --> 55:03.591 They'll pay you until you die every year. 55:03.851 --> 55:04.592 Right. 55:04.652 --> 55:05.072 Yeah. 55:05.753 --> 55:08.256 That's like a government type of thing or a school pension or something else. 55:08.316 --> 55:08.556 Okay. 55:08.576 --> 55:09.897 Because that's not how pensions work anymore. 55:09.917 --> 55:13.261 That's insane from a fucking private company though. 55:13.281 --> 55:18.246 Well, that's why they're falling apart here is because there's not enough people going into that. 55:18.286 --> 55:22.090 There's not enough funds and they have so much debt or not debt, but they have so much. 55:22.529 --> 55:44.449 obligation to past employees that unless that unless that group is growing and the value obviously the value of the dollar is dropping and the amount people save changes that those things are running out of money that's really a problem and then there's fraud in those as well because because somebody makes a deal and takes two percent or something off the top and blah blah blah or they make bad decisions they don't invest that wisely like it's a it's a mess 55:45.149 --> 55:55.654 So the way they did that in Australia is they have a super fund instead, which is basically during your employment, there's a percentage of each pay has to go into the super fund. 55:56.254 --> 56:01.036 And then that super fund is managed by an investment manager, big investment managers. 56:01.656 --> 56:03.617 For the country? 56:03.877 --> 56:05.578 For the whole, for everyone? 56:06.018 --> 56:07.519 You can choose your fund, right? 56:07.619 --> 56:12.381 But it's a legal requirement that if you hire someone, 56:14.081 --> 56:21.984 If they earn $100,000, then on top of that, you have to pay 9.5% of that into a super fund. 56:22.204 --> 56:25.245 So they get $9,500 a year into their super fund. 56:25.905 --> 56:29.826 And then those super funds, any profits that are made in your super fund account is tax-free. 56:30.586 --> 56:36.872 But you can only put – like you can't just put your whole net worth in there and get tax-free income that you can get when you retire. 56:37.072 --> 56:45.259 So when you're like 75 or whatever the retirement age is, you can withdraw it all if you wanted to or you can leave it there and just take income out of it each year tax-free. 56:45.280 --> 56:45.640 That's awesome. 56:45.660 --> 56:46.020 That's close. 56:46.200 --> 56:48.002 That's basically Social Security, right? 56:48.142 --> 56:48.302 Yeah. 56:48.362 --> 56:49.223 Except for – Go ahead. 56:49.724 --> 56:49.944 Go ahead. 56:49.964 --> 56:51.085 No, we're going to say the same thing. 56:51.983 --> 56:55.205 Okay, so yeah, Social Security is quite similar, except you can't really withdraw all the way. 56:55.225 --> 56:59.508 It's kind of like a ladder that you pull from, but it's really quite different. 56:59.528 --> 57:02.230 It's not intended as a retirement program. 57:02.671 --> 57:07.694 It's really intended as insurance from old folks. 57:07.734 --> 57:17.301 One of the really interesting stats about Social Security is that something like 18% of withdrawers are actually for underage kids because the parents die or something, right? 57:17.641 --> 57:19.443 So it's intended to be a much wider berth 57:20.623 --> 57:22.324 than people are actually aware of. 57:22.344 --> 57:29.749 A lot of the reasons why we don't have like insane child poverty is explicitly due to social security. 57:29.769 --> 57:33.871 But otherwise it's actually managed quite well. 57:33.911 --> 57:36.613 Like the management fees over time are actually quite low. 57:38.233 --> 57:38.394 Yeah. 57:39.654 --> 57:44.157 So while we were on this call, the spot BTC ETF was approved. 57:45.495 --> 57:47.596 So it's actually like an official thing. 57:47.636 --> 57:48.637 Yep, it was approved. 57:48.657 --> 57:55.562 And then Kintzler came out and said, he said, while it's approved, you know, it's still pretty risky. 57:55.602 --> 57:56.242 So like, you know. 57:57.623 --> 57:58.283 Thanks, Gary. 57:58.303 --> 58:00.385 Only take you two years to come up with that. 58:00.405 --> 58:01.045 Yeah, right. 58:01.085 --> 58:01.425 No shit. 58:02.646 --> 58:05.467 Anyway, it was kind of like a hashtag Yolo peace out. 58:05.707 --> 58:06.388 You know, that was it. 58:06.488 --> 58:07.968 But we did have it. 58:09.389 --> 58:10.089 But no, it was. 58:10.129 --> 58:10.990 Well, but they did. 58:11.230 --> 58:13.171 It does look like it's an actual official release. 58:14.291 --> 58:17.293 And so that's that's good. 58:18.233 --> 58:29.738 And the first news article I see after that is Bitcoin price unfazed by SEC approval, which kind of means it's already priced in, which does make sense because there has been talking about it for fucking ever. 58:29.798 --> 58:31.059 So the idea that it's going to do that. 58:32.300 --> 58:35.843 But I'm hoping that it lifts some specific altcoins. 58:36.703 --> 58:37.984 I don't see it on Twitter though. 58:38.024 --> 58:40.586 And I bet that a lot of people track Twitter specifically for it. 58:40.887 --> 58:44.149 Like I'm looking on Twitter right now and I can't find a reference to that at all. 58:44.189 --> 58:44.710 Full stop. 58:45.430 --> 58:45.911 At all what? 58:46.091 --> 58:47.012 You can't find a reference to what? 58:48.103 --> 58:49.263 Bitcoin is getting approved. 58:50.343 --> 58:51.704 It's not on SEC or Gov. 58:52.104 --> 58:52.864 It's not on SEC or Gov. 58:52.924 --> 58:56.845 It's on every other news outlet. 58:57.005 --> 58:58.445 The Block is reporting it. 58:59.305 --> 59:00.445 Helium is reporting it. 59:00.505 --> 59:02.326 So, ETH is pumping? 59:05.266 --> 59:06.726 It's up 10% today. 59:06.866 --> 59:08.247 Yeah, it's doing well. 59:10.367 --> 59:15.808 And, oh, well, I mean, there's only some very specific coins that we can't remember. 59:16.795 --> 59:23.559 If we'd known about this insider trading opportunity, we could have held on to some of those rewards to sell. 59:24.379 --> 59:34.705 Well, we did know about the insider trading opportunity because it was pre-released accidentally to the degens on Twitter. 59:35.665 --> 59:38.187 Someone fucked up the time on that. 59:39.582 --> 01:00:07.418 yeah that's i mean it could it so maybe somebody did compromise that thing and just literally published a draft tweet yeah it might have been exactly what it was i think that's like the likely it's like oh i was gonna i was gonna write it but it's already here so i'm just gonna undraft this thing and push it yeah yeah it turns out okay well that was super weird that literally happened during the show okay zach voll says now that the etf is approved the normal people will be able to invest in crypto instead of just the mentally ill 01:00:08.311 --> 01:00:11.432 This was a pretty good tweet. 01:00:11.932 --> 01:00:12.793 Maybe that's the issue. 01:00:12.813 --> 01:00:19.775 Maybe that's why the ETF is so important because not a lot of people realize that you can invest already in investment accounts because you can. 01:00:21.356 --> 01:00:22.376 Yep, sure can. 01:00:22.636 --> 01:00:24.497 So it's all false, basically. 01:00:24.617 --> 01:00:31.940 But do I really have to point out, you know, not your keys, not your crypto? 01:00:31.980 --> 01:00:35.841 Like, have we come this far that we have to remind ourselves, like, 01:00:39.358 --> 01:01:01.993 you know maybe maybe they should use dow dow maybe find out there should be like a fidelity dow dow oh well did you um i i noticed in so we we've got a a piece here about um about some more shenanigans with dow dow um but okay so we'll go with the news piece first so 01:01:03.772 --> 01:01:07.341 And then I'll get back to, I'll ring back around to what Shorty said there. 01:01:07.361 --> 01:01:10.870 So I'm going to read it out as Rama's written it. 01:01:13.291 --> 01:01:16.093 you know, the literary flair should be respected. 01:01:16.533 --> 01:01:19.255 It's upset when you don't. 01:01:19.535 --> 01:01:34.025 In a turn that shocked all 15 Juno community members, Dao Dao renegs on the Dao Juno token swap, citing a multitude of reasons to cancel, but the primary ones, perhaps unsaid, Rama, please tell us what they are. 01:01:34.726 --> 01:01:36.927 Our money! 01:01:37.007 --> 01:01:37.828 With a lot of Ys. 01:01:38.925 --> 01:01:43.429 but also giving Juno an overwhelming size of the token allocation and therefore voting power. 01:01:43.449 --> 01:01:46.772 So this was interesting. 01:01:46.792 --> 01:01:48.173 It was a little bit of back and forth about it. 01:01:50.415 --> 01:01:57.521 Dowdao basically canceled it unilaterally from their end and then GrowJuno sort of responded to it with a post. 01:01:59.342 --> 01:02:02.305 Can you back up and tell me, like, I don't even know if I understand the... 01:02:03.598 --> 01:02:22.615 the party relationship here what what was in place and what's what's getting dumped i don't know if anybody else does either juno funded dow dow right right um the agreement was that dow dow would give a significant portion of its token treasury to juno in exchange for juno tokens okay um 01:02:23.792 --> 01:02:26.514 they were vesting to the Juno community pool. 01:02:26.754 --> 01:02:29.656 Dowdao's canceled that from their end. 01:02:30.137 --> 01:02:31.898 Well, there was two vestings. 01:02:31.938 --> 01:02:38.643 There was the Dow tokens were vesting to the community pool, but also Juno tokens were vesting to Dowdao. 01:02:39.143 --> 01:02:47.389 So GrowJuno canceled the Juno side after Dowdao unilaterally canceled their side. 01:02:47.409 --> 01:02:50.191 Oh, so they both stopped this vesting schedule, right? 01:02:50.571 --> 01:02:53.133 Is it fair that they both stopped this vesting schedule? 01:02:53.913 --> 01:03:19.311 or well i guess there wasn't a discussion about it there was just uh it was just action from the dowd outside i think this is actually an interesting case because right that the whole point was that this would happen because of the funding that was given essentially at the inception of the project so i don't know to me it kind of smacks a little bit like the issue is that the 01:03:20.461 --> 01:03:21.382 It shouldn't have been a vest. 01:03:21.442 --> 01:03:24.664 It should have just been like, you hand over your tokens, we hand over our tokens. 01:03:24.744 --> 01:03:26.264 But hey, whatever, man. 01:03:26.865 --> 01:03:31.948 Anyway, in the post, getting back to Schultz's thing, should we just use DAODAO for everything? 01:03:32.088 --> 01:03:49.198 In the post where DAODAO basically broke the contract, they posted, amongst a bunch of other stuff, we seek nothing less than a world in which all businesses, non-profits, clubs, protocols, chains, AI, and even governments are governed using DAO tooling. 01:03:51.339 --> 01:03:56.201 So the whole world can cancel vesting contracts whenever the fuck they want to. 01:03:58.221 --> 01:03:59.342 It's a good precedent, isn't it? 01:03:59.482 --> 01:04:00.282 It's a good precedent. 01:04:00.882 --> 01:04:09.765 We're going to put that in the liner notes of breaking a contract and proving once and for all why this is a zero trust ecosystem. 01:04:11.058 --> 01:04:20.573 So last piece, unsurprisingly, the only people upset about this are Netta Dao, who are now saying that they will be taking actions to sue Dao Dao via the Juno governance for whatever Dao-ified reason they can come up with. 01:04:21.294 --> 01:04:22.876 So that's pretty funny, actually. 01:04:23.697 --> 01:04:24.318 Dao-ified reason. 01:04:26.829 --> 01:04:47.151 yeah so so i guess the what's i don't even know from a value perspective this this happened a few years ago right when this was created like data yeah it was like last year was it so so the value of those juno tokens that are being invested are obviously lower now significantly less what about what about the value of the dowdow token they don't have a value 01:04:47.731 --> 01:04:48.191 Oh, okay. 01:04:48.452 --> 01:04:50.753 So, so, okay. 01:04:51.694 --> 01:04:53.615 They're like pre-release. 01:04:54.775 --> 01:04:56.296 Yeah, yeah, yeah. 01:04:56.376 --> 01:04:56.997 I think they did. 01:04:57.017 --> 01:04:58.257 All right. 01:04:58.898 --> 01:04:59.058 Yeah. 01:05:01.192 --> 01:05:27.083 too funny i mean like as a business i believe we own we have a few for helping out dao dao in the early days and they are currently written off on our tax return as having zero value so yeah we have the same i think i have some too actually now that i'm talking about we have some but they do not exist on our ledger well they don't have any value so what were they they don't add to the number so no one cares 01:05:31.407 --> 01:05:31.627 Yeah. 01:05:32.267 --> 01:05:35.169 I mean, oh, it's certainly the same thing. 01:05:35.250 --> 01:05:45.177 I remember it is Cosmos because this was all of the shenanigans when Say was coming along and Neutron was coming along. 01:05:45.217 --> 01:05:45.898 Everybody was like, 01:05:46.877 --> 01:05:47.758 losing their minds a bit. 01:05:47.978 --> 01:05:49.839 And obviously Dowdow's on Neutron. 01:05:50.739 --> 01:05:53.981 So Say is on Wasm, but I'm pretty sure they've got their own fork of it. 01:05:54.482 --> 01:05:55.582 I think they might have their own fork. 01:05:55.722 --> 01:05:57.043 Heavily modified, probably. 01:05:57.063 --> 01:05:59.765 Like all of their other modules. 01:05:59.785 --> 01:06:00.545 That would be on brand. 01:06:00.565 --> 01:06:01.186 I was going to say. 01:06:01.286 --> 01:06:01.626 That's right. 01:06:01.846 --> 01:06:02.106 Yeah. 01:06:02.286 --> 01:06:05.128 The one module you probably don't want to heavily modify. 01:06:05.148 --> 01:06:07.510 But hey, yeah, though. 01:06:07.530 --> 01:06:08.931 I don't know. 01:06:08.951 --> 01:06:13.934 We're not... There was a lot of concurrency issues with Wasm, which I think they had to fix. 01:06:14.194 --> 01:06:14.334 So... 01:06:15.111 --> 01:06:41.304 sure but they probably introduced a lot of security issues as a result like you you very much want the original authors of that library helping you out when i think that i think they i think they're in cohorts yeah i guess that's true the cahoots they probably have the money maybe they have the money to pay for confio i don't know i would say they do how much money how much money to say raise 01:06:42.825 --> 01:07:06.101 oh like quite a lot 40 40 45 million yeah but not only not only that the token's been live for a while now and the foundation has a lot of it so they have it so much no wow have they i have no idea actually you would think right that's not right so how else do you fund the foundation 01:07:06.829 --> 01:07:08.311 It wasn't the amount that they raised. 01:07:08.351 --> 01:07:10.114 I remember it was the valuation that they raised at. 01:07:10.274 --> 01:07:13.039 I know that was... Yeah, it was $800 million that they raised. 01:07:13.059 --> 01:07:15.923 Yeah, they raised like a huge value, like a massive valuation. 01:07:16.644 --> 01:07:19.910 In saying that, the valuation is now pretty... 01:07:20.404 --> 01:07:21.486 Pretty, pretty big. 01:07:21.806 --> 01:07:23.068 The chain is going well, though. 01:07:23.108 --> 01:07:28.576 I mean, it's doing what it needs to do and it's moving fast and like all the value that is there. 01:07:28.596 --> 01:07:31.500 And now with the CVM thing that's coming up, I think that's pretty exciting. 01:07:31.801 --> 01:07:33.904 So I know that's supposed to be 2024. 01:07:33.944 --> 01:07:34.585 That's going to be cool. 01:07:34.685 --> 01:07:36.908 So I'm really excited about what's coming there. 01:07:37.791 --> 01:08:03.526 it is it's it's it's pretty quiet on the on the dev front in the discord but that is like i've talked to phil a couple of times and they are just like sprinting hard on that on the evm only so i think it's all internal right once they get to the point of because i think they're gonna i think they even said that they wanted to keep atlantic 2 mirroring pacific one so there'll be another test net um there'll be another test net that launches with the cbm thing so that'll be more 01:08:05.080 --> 01:08:08.562 Ben Davis says, I'm not even sure Game of Noses realized it's a bull market. 01:08:08.582 --> 01:08:14.846 We were joking about that this week because they always say, I can't wait. 01:08:15.327 --> 01:08:17.448 The next bull, I'm going to do X, Y, Z. I'm like, dude, you're in it. 01:08:17.748 --> 01:08:18.969 This is it. 01:08:19.149 --> 01:08:21.491 This is it, brother. 01:08:21.511 --> 01:08:26.614 This is the bull market, and it's time to unbond everything and sell while things are not worth zero. 01:08:26.634 --> 01:08:27.775 A little FYI, you're in it. 01:08:29.778 --> 01:08:51.842 yeah but i mean a run i mean there hasn't been the the post um what is it the post harvening run yet yeah this is i mean the the ridiculously silly season yeah it's not app chain it's not app chain winter but then again we're probably not ever going to see another app chain winter in the cosmos ecosystem so what 01:08:53.613 --> 01:08:57.617 You know, like AppChain Winter when all of the chains launched and everything went crazy. 01:08:59.018 --> 01:09:00.800 Isn't that AppChain Summer? 01:09:02.942 --> 01:09:03.883 It wasn't in the summer, though. 01:09:03.903 --> 01:09:05.044 It started in fucking October. 01:09:05.144 --> 01:09:06.145 Although it was your summer. 01:09:07.523 --> 01:09:34.753 kangaroo man i think like so it's a literal winter that figurative like literally yeah yeah i think the same no one just looks so tired he's just like i don't even know like summer which is summer for no so it is it is well i feel like summer i feel like the expression is more based around like oh it's summertime in the i i 01:09:35.797 --> 01:09:36.258 I agree. 01:09:36.278 --> 01:09:42.884 Yeah, I definitely thought you were saying actually winter meant... Not that it happened during a literal American winter. 01:09:42.904 --> 01:09:45.687 DeFi summer happened in the summer. 01:09:46.288 --> 01:09:48.150 It's like, oh, it's fucking DeFi December. 01:09:48.190 --> 01:09:50.111 DeFi summer happened in the fucking summer. 01:09:50.172 --> 01:09:52.013 That's why it was called DeFi summer. 01:09:52.033 --> 01:09:55.116 I don't think so. 01:09:55.177 --> 01:09:56.618 I think it's meant to be figurative. 01:09:57.259 --> 01:09:57.459 Yeah. 01:09:59.093 --> 01:10:00.995 Can you pick something else that would be more complicated? 01:10:01.415 --> 01:10:10.562 Like maybe it just coincidentally happened in summer enough times that you're like, well, sleep by summer. 01:10:10.682 --> 01:10:20.629 If you radically object to that, viewers and listeners, then write it in the comments and I'll probably ignore it and continue using that term. 01:10:20.649 --> 01:10:23.050 What about this last piece? 01:10:23.070 --> 01:10:27.233 So while we're on Juno, their lead developer, which I think is, we're talking about Reese, right? 01:10:27.253 --> 01:10:27.353 Reese. 01:10:28.354 --> 01:10:36.938 Uh, looks like he is being fired by someone via governance, citing to need to focus on developing, uh, DAPs rather than core chain features. 01:10:37.479 --> 01:10:40.520 Little do they know Reese has already quit two weeks prior to the on-chain proposal. 01:10:41.981 --> 01:10:45.302 So I did, I did see a little bit of drama in Twitter this week about that. 01:10:45.382 --> 01:10:53.706 And I saw that proposal that was on Juno last, was it this week or last week related to the chain direction or other types of things. 01:10:53.986 --> 01:10:55.507 So what the hell's going on here? 01:10:56.488 --> 01:10:57.008 Juno people. 01:10:59.284 --> 01:11:08.211 So this all happened while I was on my Christmas break and so wasn't looking at notifications. 01:11:10.092 --> 01:11:20.780 From what I gather, block creators put up that post saying Juno needs to refocus on building dApps. 01:11:22.299 --> 01:11:24.521 rather than core development and upgrades. 01:11:26.723 --> 01:11:30.366 Which obviously comes across as very passive-aggressive against Rhys. 01:11:30.546 --> 01:11:33.889 Rhys and Block obviously fucking hate each other anyway. 01:11:33.909 --> 01:11:40.855 But then Rhys had already quipped. 01:11:41.974 --> 01:11:42.555 But did he quit? 01:11:42.775 --> 01:11:44.497 Is that, is that, is that, that happened? 01:11:45.178 --> 01:11:45.278 Yeah. 01:11:45.318 --> 01:11:47.280 I didn't realize he actually officially quit now. 01:11:47.300 --> 01:11:48.321 I think so. 01:11:48.762 --> 01:11:49.022 Maybe. 01:11:49.062 --> 01:11:51.085 I mean, he's still, he's still, he's still working on stuff. 01:11:51.105 --> 01:11:51.365 So, uh, 01:11:55.339 --> 01:12:13.648 yeah i'm not sure he was just did the the security upgrade literally like today yeah i think he might be contributing but maybe he's no longer fully on kind of juno stuff i mean i know he's been working for strange love for a little while and splitting time so maybe he's just fully gone over to strange love 01:12:15.430 --> 01:12:16.491 So who put up this proposal? 01:12:16.611 --> 01:12:19.073 Who put up 331 with this shift focus thing? 01:12:19.853 --> 01:12:21.715 You said that was blocked. 01:12:21.775 --> 01:12:23.716 So, I mean, honestly, I voted abstain. 01:12:23.996 --> 01:12:24.837 I should just vote no. 01:12:25.117 --> 01:12:26.398 It's just a bunch of rambling bullshit. 01:12:26.438 --> 01:12:28.299 Like, there's not even, like, an actionable thing here. 01:12:28.339 --> 01:12:29.860 It's just like, hey, guys. 01:12:30.381 --> 01:12:31.802 It's like, it just seems like it's a... 01:12:33.177 --> 01:12:41.245 general... It's a kind of quite classic block creator's post in that it's sort of broadly correct, but it's completely unactionable. 01:12:41.885 --> 01:12:42.746 There's no actions at all. 01:12:44.108 --> 01:12:45.829 Why do you need to refocus? 01:12:45.949 --> 01:12:47.571 It's a shower thought. 01:12:47.831 --> 01:12:48.572 It's a shower thought. 01:12:48.832 --> 01:12:49.672 It is. 01:12:49.992 --> 01:12:52.253 It's a discussion topic, which is great. 01:12:52.453 --> 01:12:55.094 So even if it passes or not, it doesn't change anything. 01:12:55.734 --> 01:12:56.374 So what the fuck is this? 01:12:56.394 --> 01:12:56.994 It's not binding. 01:12:57.034 --> 01:12:57.855 It doesn't mean anything. 01:12:58.015 --> 01:13:01.936 There are no developers to build dApps anyway. 01:13:02.476 --> 01:13:06.337 You can encourage people through a blog post. 01:13:06.877 --> 01:13:08.638 There's no developers to build dApps anyway. 01:13:09.058 --> 01:13:10.038 So it's kind of moot. 01:13:11.798 --> 01:13:11.958 Right. 01:13:12.598 --> 01:13:14.399 But like, who are you going to get to build stuff? 01:13:15.279 --> 01:13:18.241 Like, I'm going to put a proposal up, says this token should be go up in price. 01:13:18.821 --> 01:13:19.441 Yeah. 01:13:19.461 --> 01:13:20.101 Totally go up in price. 01:13:20.141 --> 01:13:21.642 It would be way better vote. 01:13:21.662 --> 01:13:21.862 Yes. 01:13:21.902 --> 01:13:23.983 The signal that you want this broken to go in price vote. 01:13:24.023 --> 01:13:24.123 No. 01:13:24.163 --> 01:13:27.184 If you disagree with this proposal, like it's the same fucking actionable type of thing. 01:13:27.204 --> 01:13:31.205 Like it doesn't teams have to come here to be able to build those dapps. 01:13:31.245 --> 01:13:31.406 Right. 01:13:31.606 --> 01:13:35.167 And, and if Juno is going to build, build what, like what, 01:13:36.949 --> 01:13:43.532 Yeah, I mean, it's just kind of back to the... Oh, so the other thing that's happened is Core 1 is formally dissolved as well now. 01:13:43.552 --> 01:13:49.255 I gather that... I think the knives are out again in Juno. 01:13:49.275 --> 01:13:49.935 I don't know. 01:13:49.955 --> 01:13:56.499 I had people kind of... I had some messages being like, oh, we're trying to work out who gets what. 01:13:56.539 --> 01:14:01.881 Like, we need to know where your Core 1 vesting blah, blah, blah is for transparency. 01:14:01.901 --> 01:14:02.622 And I was like, fuck off. 01:14:02.662 --> 01:14:03.282 I never had one. 01:14:04.659 --> 01:14:12.422 I specifically declined ever getting paid for Core 1 stuff because I knew eventually I'd have... Fuck off. 01:14:13.343 --> 01:14:13.503 Yeah. 01:14:15.063 --> 01:14:21.526 So is this the new group of like the... Is it like the new group people that are saying this to you? 01:14:21.546 --> 01:14:22.346 It was the charter. 01:14:22.366 --> 01:14:24.067 It was the charter thing. 01:14:24.707 --> 01:14:25.127 Yeah, right. 01:14:27.093 --> 01:14:30.157 Well, I mean, they would be able to see you just by looking at the data history, right? 01:14:30.197 --> 01:14:31.038 I don't really need to. 01:14:31.098 --> 01:14:33.460 No, no, it's just random DJs, I think. 01:14:34.962 --> 01:14:40.188 But back to back to Reese's involvement in this is is I guess maybe I don't understand his role. 01:14:40.248 --> 01:14:42.511 Is he is going to sound worse than I want to say? 01:14:42.551 --> 01:14:46.735 Is he an employee to Juno and taking direction from the larger collective? 01:14:46.795 --> 01:14:47.977 Like, what's his role? 01:14:48.911 --> 01:15:16.198 where he where he would be fired like being fired by government by governance that doesn't make any sense well previously he was essentially hired employed by core one on behalf of juno and his salary was paid from core one um i don't know how that works now no like yeah you know uh i'll i'll be honest like the 01:15:19.554 --> 01:15:32.063 Yeah, I mean, my focus with Quorum was always just getting to the point, getting to this, just doing a little bit of work to smooth over the transition period to this charter, what we all knew was sort of coming. 01:15:33.103 --> 01:15:34.424 And now it's done. 01:15:36.145 --> 01:15:39.988 Well, I mean, it's opened the door, right, for you to go back and do this role if you want to. 01:15:42.683 --> 01:15:43.983 I don't work for Juno anymore. 01:15:44.843 --> 01:15:45.864 You could. 01:15:47.164 --> 01:15:47.704 Are you applying? 01:15:50.384 --> 01:15:50.705 No. 01:15:50.725 --> 01:15:50.765 No. 01:15:56.686 --> 01:16:01.487 The problem is, genuinely, I think that Juno had a time. 01:16:01.507 --> 01:16:02.867 It had an opportunity. 01:16:02.887 --> 01:16:04.867 It missed its time. 01:16:04.887 --> 01:16:06.287 It missed its opportunity. 01:16:06.868 --> 01:16:08.408 It fucked itself over with Prop 16. 01:16:10.121 --> 01:16:11.662 Um, that's it. 01:16:12.062 --> 01:16:13.163 That's the end of the story. 01:16:15.204 --> 01:16:21.428 You know, the timing, timing and luck are everything in, in business and life. 01:16:21.488 --> 01:16:29.133 Like, um, and a good idea, which is what Judo was at the time at the right time. 01:16:30.233 --> 01:16:31.254 That's worth something. 01:16:31.334 --> 01:16:33.515 A good idea on its own is worth nothing. 01:16:33.695 --> 01:16:34.836 Execution is everything. 01:16:35.497 --> 01:16:35.597 And. 01:16:36.713 --> 01:17:00.468 they had the good idea and the right timing and dog shit execution and that's that's the story really i hope that the charter folks who are well-meaning smart people i hope that they do a better job than core one did i hope they managed to put some things back on track you know um 01:17:02.105 --> 01:17:03.825 That would be that would be great. 01:17:03.905 --> 01:17:06.026 That would be a nice there be a good. 01:17:07.926 --> 01:17:10.627 It would be nice to believe that could happen from where things are now. 01:17:11.227 --> 01:17:11.787 Yeah, yes. 01:17:12.207 --> 01:17:22.589 I wonder if, like, what if, if this Juno idea came forward today, if it didn't exist in the past, and it launched, could that could that chain launch in 2024? 01:17:24.650 --> 01:17:26.310 And try to deliver on that original promise? 01:17:27.737 --> 01:17:32.321 Or is that, is that, is it, did we miss, is the whole window closed? 01:17:32.681 --> 01:17:33.322 You know what I mean? 01:17:33.442 --> 01:17:34.463 Like, is there a possibility? 01:17:34.503 --> 01:17:35.744 Like, could it be a, 01:17:36.713 --> 01:17:39.115 obviously some significant event needs to happen. 01:17:39.255 --> 01:17:41.677 There needs to be some sort of life-changing event, right? 01:17:41.717 --> 01:17:47.921 A specific Dapp comes on board or specific development or some sort of event that brings people back in, right? 01:17:47.941 --> 01:17:56.988 Because right now it seems like, or maybe Dadao is that event that completely grows and somehow yada yada. 01:17:57.629 --> 01:18:02.352 But could a Juno 2 launch today with that same functionality set and be successful? 01:18:03.153 --> 01:18:04.313 No, absolutely not. 01:18:04.494 --> 01:18:05.014 Yeah, I don't think so. 01:18:06.308 --> 01:18:27.595 no that's what i was gonna say and and even juno couldn't launch when it launched and be successful yeah and that was kind of i think relatively obvious at the time it was obvious even before launch because there was a drive to incentivize um apps being built it's just that the 01:18:33.709 --> 01:18:53.871 building complex things takes time people patience and money and it also takes good planning good road mapping and like an idea of how delivery works and very few teams were able to deliver and very few teams were then able to maintain any momentum i mean like 01:18:55.560 --> 01:18:55.720 Yeah. 01:18:55.760 --> 01:19:05.691 I mean, like we, we went through that with how we managed to deliver in the end late and very tired and we had no momentum and we were just no momentum, no money left. 01:19:05.771 --> 01:19:07.873 And we were just like, fuck, we're just done. 01:19:09.255 --> 01:19:16.903 If, if projects, I mean, and I guess this is like, you know, how it was a bit different, maybe because it required Dowdow to even work. 01:19:18.157 --> 01:19:26.262 But there were other projects, I guess, that didn't have requirements that required them to be that far in the future from Juno's launch. 01:19:26.282 --> 01:19:32.166 It could have been built in June, July, August, 2021 before it launched. 01:19:32.407 --> 01:19:33.167 And I think. 01:19:39.588 --> 01:19:42.769 The difficulty is just like, it's just finding developers. 01:19:43.409 --> 01:19:44.529 There is just so few. 01:19:44.589 --> 01:19:45.529 It's such a small pool. 01:19:45.689 --> 01:19:51.731 It's hard to find devs at the best of times in any sub-industry of tech. 01:19:52.251 --> 01:19:53.871 Yeah, it was also early then too, right? 01:19:53.971 --> 01:19:54.511 It's different now. 01:19:54.711 --> 01:19:54.811 Yeah. 01:19:55.371 --> 01:19:57.012 Just in terms of that tool set. 01:19:57.972 --> 01:19:58.452 Yeah, exactly. 01:19:59.052 --> 01:19:59.332 I'm sorry. 01:19:59.352 --> 01:20:00.612 We spent a lot of time at Juno. 01:20:00.772 --> 01:20:03.713 It's kind of like talking about an ex-girlfriend. 01:20:05.914 --> 01:20:08.034 Skip reminiscent and start, what could have been? 01:20:10.788 --> 01:20:12.670 It could have been great, but anyway. 01:20:13.191 --> 01:20:13.911 It could still be great. 01:20:15.693 --> 01:20:16.314 Lightning could strike. 01:20:16.474 --> 01:20:17.034 Something could happen. 01:20:17.054 --> 01:20:18.636 Let's see what the charts are doing with it. 01:20:18.676 --> 01:20:19.297 Good luck to them. 01:20:20.638 --> 01:20:21.379 There's a lot there. 01:20:21.399 --> 01:20:22.300 It's a cool chain. 01:20:24.002 --> 01:20:24.602 There's opportunity. 01:20:25.944 --> 01:20:27.085 Here's what I'll say about Juno. 01:20:28.726 --> 01:20:33.992 Junoapi.lavender5.com is the first place I go whenever I want documentation for Swagger. 01:20:38.001 --> 01:20:39.322 Wait, now I need to look it up. 01:20:40.202 --> 01:20:41.043 It is quite complete. 01:20:42.284 --> 01:20:43.084 It is quite complete. 01:20:43.504 --> 01:20:44.445 It is the default. 01:20:44.925 --> 01:20:46.686 It just goes right in other places. 01:20:46.707 --> 01:20:47.507 You need to look elsewhere. 01:20:47.527 --> 01:20:48.207 I don't know. 01:20:48.368 --> 01:20:49.168 It's actually really nice. 01:20:50.829 --> 01:20:51.510 Swagger is nice. 01:20:51.630 --> 01:20:52.290 I like swagger. 01:20:54.792 --> 01:20:55.312 It's not loaded. 01:21:00.922 --> 01:21:02.723 Link in the show notes to read all your swagger. 01:21:03.684 --> 01:21:05.505 JunoAPI11.5.com doesn't work. 01:21:05.746 --> 01:21:06.286 Slash swagger. 01:21:06.406 --> 01:21:06.946 Slash swagger? 01:21:07.927 --> 01:21:08.227 No, no, no. 01:21:08.267 --> 01:21:09.428 You don't add slash swagger. 01:21:09.848 --> 01:21:10.609 It's just slash. 01:21:10.909 --> 01:21:12.190 And that's, I think, why I like it. 01:21:13.371 --> 01:21:13.771 Oh, there it is. 01:21:13.851 --> 01:21:14.192 It's working. 01:21:15.012 --> 01:21:17.114 So everything else requires a slash swagger. 01:21:17.234 --> 01:21:19.415 But the fact that JunoAPI skips the swagger bit. 01:21:19.435 --> 01:21:21.237 Yeah, that's the way it should be, right? 01:21:21.257 --> 01:21:21.737 It's amazing. 01:21:21.897 --> 01:21:22.498 Totally agree. 01:21:23.098 --> 01:21:24.179 Wait, did you change? 01:21:24.299 --> 01:21:24.799 Is that your? 01:21:25.159 --> 01:21:26.701 Did you change that path or that's just part of Juno? 01:21:27.506 --> 01:21:29.487 I think that the Juno thing, it's really nice. 01:21:30.208 --> 01:21:32.509 You should have taken that. 01:21:32.529 --> 01:21:38.453 That's going to hold onto this because a lot of people always ask us about, cause say, say doesn't have any of this. 01:21:38.493 --> 01:21:40.354 Like they don't, they don't post anything like this. 01:21:40.395 --> 01:21:40.535 Right. 01:21:40.575 --> 01:21:43.877 Even though they have, I think there's some other specific modules, but this is a good, it's a good starting point. 01:21:45.058 --> 01:21:45.238 Yep. 01:21:45.618 --> 01:21:50.241 I do Juno and then Akash if I need to some, cause there's some crossover there that isn't the same. 01:21:51.782 --> 01:21:51.962 Yeah. 01:21:54.464 --> 01:21:54.604 Well, 01:21:57.335 --> 01:21:58.075 That's it for Juno. 01:22:00.476 --> 01:22:01.476 Four out of 40. 01:22:04.116 --> 01:22:05.917 So, there's one more. 01:22:05.937 --> 01:22:08.717 There's one other news item. 01:22:09.318 --> 01:22:10.978 I still don't even fucking know what Newt is. 01:22:10.998 --> 01:22:12.958 A token. 01:22:12.978 --> 01:22:17.559 Fucking Ben and Ron are going to come after you. 01:22:18.259 --> 01:22:19.020 Whatever, man. 01:22:19.040 --> 01:22:22.020 It's literally a lighter than talking about. 01:22:22.360 --> 01:22:23.641 A D-Gen token. 01:22:25.861 --> 01:22:28.183 I think Rama gets paid by the Newt reference. 01:22:28.823 --> 01:22:30.084 Yeah, per Newt reference. 01:22:30.164 --> 01:22:31.665 Is Rama the biggest Newt holder? 01:22:31.685 --> 01:22:32.566 That probably makes sense. 01:22:32.946 --> 01:22:33.467 On Twitter. 01:22:35.228 --> 01:22:37.069 Oh, it's definitely golden ratio staking. 01:22:37.129 --> 01:22:39.391 He's definitely the biggest Newt whale. 01:22:40.452 --> 01:22:41.032 Maybe Don? 01:22:41.512 --> 01:22:41.873 I don't know. 01:22:43.954 --> 01:22:44.735 Yeah, maybe. 01:22:46.636 --> 01:22:50.459 I'm sure I asked this last week. 01:22:54.142 --> 01:22:58.145 I'm quite often tired on Wednesday because I spent all day bouncing a baby in one knee. 01:22:59.687 --> 01:23:02.689 It's just like a CW20 or something, isn't it? 01:23:02.909 --> 01:23:09.555 It's not some other chain that I've just missed because I live under a fucking... You are precisely correct for Neutron. 01:23:09.575 --> 01:23:10.355 It's on Neutron. 01:23:10.956 --> 01:23:11.556 Right, right. 01:23:11.676 --> 01:23:12.537 Okay, cool. 01:23:12.877 --> 01:23:14.058 Okay, good. 01:23:15.960 --> 01:23:17.801 It's the future of all decentralized finance. 01:23:19.362 --> 01:23:19.823 Cool. 01:23:20.463 --> 01:23:20.944 Soon to be. 01:23:21.564 --> 01:23:23.386 It's the next target for the SEC, I'm sure. 01:23:24.383 --> 01:23:25.563 I really thought that went without saying. 01:23:25.583 --> 01:23:28.224 He's ever going right for it. 01:23:29.364 --> 01:23:29.504 Right. 01:23:29.764 --> 01:23:31.125 That's this Bitcoin thing. 01:23:31.145 --> 01:23:32.165 We're going right. 01:23:32.185 --> 01:23:33.165 Not worried about that yet. 01:23:33.926 --> 01:23:34.466 Neutron. 01:23:35.046 --> 01:23:36.026 We're straight on the case. 01:23:36.806 --> 01:23:37.166 Neutron. 01:23:37.186 --> 01:23:37.466 Neutron. 01:23:38.467 --> 01:23:39.227 Neutron. 01:23:39.287 --> 01:23:39.627 Neutron. 01:23:40.667 --> 01:23:41.207 Neutron. 01:23:41.247 --> 01:23:41.628 Neutron. 01:23:45.365 --> 01:23:46.347 I don't give a shit about Newt.