WEBVTT 1 00:00:00.220 --> 00:00:06.320 A new person was added to the list of what are called Bitcoin Core maintainers. 2 00:00:06.760 --> 00:00:21.320 Each person kind of has, like, a special domain that they focus on, and so the most recent addition focuses on something called the Bitcoin kernel and the consensus code, which is, I think, one of the most interesting things about this. 3 00:00:21.400 --> 00:00:32.460 At the heart of a lot of this d- discussion, and I think a lot of existential questioning in Bitcoin is, is Bitcoin Core, which is a client, should Bitcoin Core be the only dominant client? 4 00:00:32.680 --> 00:00:42.260 And there's a lot of people who disagree. I have publicly said I want different clients which run Bitcoin. Bitcoin Core is a bunch of code, it's a client, and it's a whole thing. 5 00:00:42.280 --> 00:00:45.460 It's got libraries, it's got a wallet component, it's got all these things to it. 6 00:00:45.620 --> 00:00:55.580 But what is actually absolutely essential for it to remain in consensus with the other nodes on Bitcoin is this concept of it has to be consensus compatible. 7 00:00:55.640 --> 00:01:03.360 So it has to validate the same blocks as all the other nodes, and it's got to have the same opinion about what is Bitcoin. 8 00:01:03.390 --> 00:01:21.100 And it's much harder said than done because it's actually, when you write all this code and y- and you, and you pull it all, it's actually not clear sometimes what is a peculiarity of the actual client, Bitcoin Core, and what is actual, actual Bitcoin consensus. 9 00:01:21.420 --> 00:01:35.120 This is a, a project to define what even is Bitcoin consensus and separate it so that you can take these rules and this code and build a different client with it. 10 00:01:37.400 --> 00:01:49.700 A mysterious new person was just added to the elite six people who control Bitcoin. Yeah, you heard that right. There's a conspiracy, and only a few people control the fate of a $2 trillion network. 11 00:01:50.020 --> 00:02:02.850 This is inside the rabbit hole of how Bitcoin code is governed. [upbeat music] Charlie, is that intro true? 12 00:02:03.300 --> 00:02:15.080 No, the intro is total bullsh- I'm only saying that because, uh, it hooks people in, ev- you know, especially Bitcoin critics, and it's been, like, the subject of Bitcoin criticism over the past year. 13 00:02:15.160 --> 00:02:20.400 We've done endless conversation about the filter debates and Bitcoin Core, yada yada. We won't get into, get into it. 14 00:02:20.440 --> 00:02:38.200 But some news happened over the past week, Colin, where, uh, a new person whom most people who aren't in Bitcoin development don't know, a new person was added to the list of what are called Bitcoin Core maintainers. 15 00:02:38.620 --> 00:02:53.060 Now, inside of explaining what this is, uh, is a little bit of h- history lesson. It's a little bit of time explaining how GitHub works and also kind of talking about the social layer of, like, Bitcoin code. 16 00:02:53.120 --> 00:02:56.680 And then we can sit back and be like, "Okay, so who's this new guy?" 17 00:02:57.300 --> 00:03:09.480 Um, if you're listening to this, uh, you can already go and read, uh, a, a modest profile that we published yesterday, on Friday, about the new Bitcoin Core maintainer, but we'll get into that in a second. 18 00:03:09.540 --> 00:03:25.549 So first of all, Colin, do you know what GitHub is? [laughs] I do know what GitHub is, for sure. But it seems like, uh, we might not know everything about the Bitcoin Core GitHub repo- Yeah... 19 00:03:25.560 --> 00:03:33.320 per what you were saying before we hopped on the horn here. Yeah. There's a lot in, there's a lot in this. And so, um, I think it's expl- simple to explain what GitHub is. 20 00:03:33.380 --> 00:03:46.580 It's basically where, it's like the premier place that people go to post and work on and talk about code, um, and reference code. Uh, but I- you don't actually really need to know all that. 21 00:03:46.600 --> 00:04:01.160 It's actually, what, what's more important now is that, um, uh, is to explain, like, the accounts hierarchy system of how GitHub works. And so you can just know that GitHub is where code goes to live. 22 00:04:01.180 --> 00:04:12.940 It's like, you almost might call it, like, social media for code/work. Uh, like, uh, work for code. That's what I think is interesting about GitHub, is it's simultaneously a database and a social media platform. Yeah. 23 00:04:13.340 --> 00:04:18.880 It's all of that. And, um, so you can have code live in a certain place. 24 00:04:18.899 --> 00:04:28.650 So if you just got, like, a certain project, like a personal project, you can have your profile, you can have different open source projects or, like, professional, your company projects you can contribute to all those. 25 00:04:28.680 --> 00:04:40.640 Bitcoin Core, which is a client that runs Bitcoin, um, the effective, like, the, the only client that really matters right now, that is where all the code for Bitcoin Core lives. 26 00:04:40.700 --> 00:04:52.920 And the organizational structure of who the actual accounts are that coordinate, like, this big project that is Bitcoin Core, that is what we're gonna have to explain. 27 00:04:53.100 --> 00:05:01.700 So because it's open source, and all this stuff happens out in the open, um, you have, it means anyone can walk in and say pretty much anything. 28 00:05:01.860 --> 00:05:10.820 Now, there is a moderation system, but, like, people post code, post ideas, people comment on that, and they make revisions, and people comment on those and give feedback. 29 00:05:11.120 --> 00:05:28.740 But there have to be, like, janitors, like, moderators of this process, and there have to be people, um, who, like, push the big red button to turn the proposed code into the official code that is, that you download the file and you run the client for. 30 00:05:29.420 --> 00:05:42.320 And so really, these, this is, these are like key holders, but they're more like janitors with keys, is what I would- Dare we say custodians? Custodians. [laughs] But not in the way that most people think. 31 00:05:42.820 --> 00:05:48.420 It was there all along. [laughs] It was right under our nose. Yeah, I mean, they're like, um... 32 00:05:49.000 --> 00:06:13.048 So a lot of what they do is just make sure that conversation stays on topic, that the, uh, process of, like, the code review is clean and orderly, and that when it's time to, like-Take code and merge it into the official, like, uh, program that everybody downloads and runs. 33 00:06:13.088 --> 00:06:16.468 They're the ones who have the keys which, like, officially, like, do that. 34 00:06:17.068 --> 00:06:32.048 There are a only a select few people who they're known, they're pre- they're well known to the developer community, and men- most of them are pretty doxxed, but not fully doxxed depending on their own preference. 35 00:06:32.128 --> 00:06:44.388 And, um, they use PGP keys, cryptography, to basically prove that, "Hi, it's me, Ava Chow," "Hi, it's me, Gloria," and we're, like, the ones who are turning the keys and merging this code. I'll also make a point. 36 00:06:44.868 --> 00:07:00.608 GitHub is an, is a product that's owned by Microsoft, so, like, you're ki- there's an element of trusting the actual platform you're hosting all this on, and there is a different account which owns the repository. 37 00:07:01.348 --> 00:07:05.128 So we'll get into that in somewhere down the road. 38 00:07:05.728 --> 00:07:22.528 But, um, right now, the most important thing is there's a lot of people contribute code, but there's only a few people who have the keys to merge it, and that is the significance of the news this past week is that for the first time since February 2023, um, there had been five maintainers. 39 00:07:22.788 --> 00:07:35.747 There are now six, and the sixth maintainer, um, Sedated or The Charlatan, The Charlatan are his two pseudonyms, um, has been a longtime contributor, and he's well-respected in Bitcoin developer community. 40 00:07:36.228 --> 00:07:47.908 And so the other developers and a lot of the folks who talk in the various channels about Bitcoin Core all unila- you know, pretty much unilaterally agreed, um, yeah, this person's trusted. 41 00:07:47.968 --> 00:08:00.928 This person should be given a key to merge the code and make decisions. Why did they decide to add a sixth maintainer, and who's the current lead maintainer? Those are both good questions. 42 00:08:01.788 --> 00:08:10.408 As far as, like, a sixth maintainer, there's a, uh... I actually don't [laughs] I don't know if it's super clear. 43 00:08:11.048 --> 00:08:30.758 It's kind of one of those things where everybody kind of agrees that, uh, this person has earned enough trust, and then there's another dimension which is of the existing, the previous five and now six, each person kind of has, like, a special domain that they focus on. 44 00:08:31.068 --> 00:08:43.848 Mm. This may not be as well, this not be as well known. Um, the most conspicuous and controversial one is, uh, of recent is Gloria Zhao, who is, her specialty and domain has been mempool and relay policy- Yeah... 45 00:08:43.878 --> 00:08:56.088 which is at the heart of the spam debate. But you have other people who are not as well known. Ryan Oakes who's, who does the IPC. You have Ava Chow who's more on the wallet side. 46 00:08:56.128 --> 00:09:10.228 You've got, uh, uh, Marco Falke who's, like, on testing, and, uh, you've got Hannity Stepanov who's kind of like the GUI and the build person. Um, and these people have been doing this for years. 47 00:09:11.008 --> 00:09:24.708 Uh, and so the most recent addition, uh, Sedated or The Charlatan, um, focuses on something called Libbitcoin kernel and the consensus code, which is, I think, one of the most interesting things about this. 48 00:09:25.148 --> 00:09:36.708 Um, if I could speculate why they're added, um, at the heart of a lot of this d- discussion, and I think a lot of existential questioning in Bitcoin is, um, is Bitcoin Core, which is a client, 49 00:09:38.228 --> 00:09:51.388 should Bitcoin Core be the only dominant client? And there's a lot of people who disagree. I have publicly said I want different clients which run Bitcoin, um, which are competitive, uh, to Bitcoin Core. 50 00:09:52.108 --> 00:10:01.348 Um, I think that's good for the health of the ecosystem and decentralization. But to be able to, to make that really easy, not everybody agrees on this, by the way. There's a long history of debating this. 51 00:10:02.148 --> 00:10:08.408 Um, when you have a- I don't know if I agree on it. Yeah, we-- maybe this is another debate. I gotta, I gotta finish this thought. 52 00:10:08.488 --> 00:10:20.908 So, um, one of the things, uh, that's, that's really difficult to communicate, I think, to average people who don't, like, live and breathe this is that, um, Bitcoin Core is a bunch of code. 53 00:10:20.968 --> 00:10:26.348 It's a client, and it's a whole thing. It's got libraries. It's got a wallet component. It's got all these things to it. 54 00:10:27.008 --> 00:10:37.308 But what is actually absolutely essential for it to remain in consensus with the other nodes on Bitcoin is this concept of it has to be consensus compatible. 55 00:10:37.648 --> 00:11:13.688 So it has to validate the same blocks as all the other nodes, and it's got to have the same opinion about what is Bitcoin, and it's much harder [laughs] said than done because it's actually, when you write all this code and you, and you, and you pull it all, it's actually not clear sometimes what is a peculiarity of the actual client, Bitcoin Core, and what is actual, actual Bitcoin consensus, and that is where there has been a multi-year project originally started by a guy named Carl Dong and, and he left and gave up on that and went to go build VPNs. 56 00:11:14.248 --> 00:11:25.548 Now, Sedated or The Charlatan, the new maintainer, has actually been working on that a long time and is probably the domain expert in that category. Are you talking about the great consensus cleanup? No. 57 00:11:26.188 --> 00:11:31.208 I'm talk- That's a, that's a PR to, like, improve the rough edges around consensus. 58 00:11:31.828 --> 00:11:52.868 I'm saying that this is a, a project to define what even is Bitcoin consensus and separate it so that you can take these rules and this code and build a different client with it, and this is one of the reasons that it's, like, really confusing to explain, like, what Luke Dash Jr. 59 00:11:53.148 --> 00:12:13.208 Knots is or what, um, Libbitcoin by Eric Voskuil is, and, um, that's because it is really difficult to build a node implementation, a client which, um, under all sorts of s- scenarios remains in consensus with all the other clients from the ground up, if you're building it from the ground up. 60 00:12:13.228 --> 00:12:24.112 And so this would basically say-Here are actually the rules, uh, for what Bitcoin Core considers consensus, and you can take those and go build your own thing. 61 00:12:24.172 --> 00:12:36.712 This is, in a way, almost like an admission that this is perhaps a healthy initiative, even if it's not agreed by everybody. So, so this is interesting. I, I, two parts to my response to that. 62 00:12:36.792 --> 00:12:52.062 So it's, you could almost view Charlatan's, uh, ascension as a maintainer as a way to mollify the fire eaters amongst the, uh, how should we say, the anti-core crowd, right? Those who want, uh, [laughs] 63 00:12:52.132 --> 00:13:06.222 those seditious, uh- [laughs]... filter boys who want to peel away from Core and start their own, you know, movement behind something like Knots, right? Which is Luke Dash's, uh, or Luke Dash Jr.'s client. Yeah. 64 00:13:06.252 --> 00:13:13.332 You could, so you could- Exactly... almost view that as saying, "Okay, you guys are saying that we are trying to concentrate power within Core. 65 00:13:13.392 --> 00:13:20.592 Well, we're gonna give you a template for building your own client that will be compatible with what we're doing." It is very much like a template. You can think of it like that. 66 00:13:20.632 --> 00:13:26.332 It's a template where we're not defining what the template is. We're just saying, like, here's like the basics, so you can go do that if you wish. 67 00:13:26.532 --> 00:13:46.792 Yeah, and so within my second part of this, to play devil's advocate on the other side, you could still see someone taking qualm with this in the sense that, well, this is what Core defines as consensus, and they're still the ones dictating what should or should not be followed so that every client is in consensus. 68 00:13:46.972 --> 00:13:47.422 I don't- Oh, yeah... 69 00:13:47.482 --> 00:14:03.402 agree with that necessarily, because going back to what I was gonna say about client diversity, I mean, yeah, in a perfect world, you do have alternate clients that are at least maintained enough to where they can be used in a nuclear scenario where you need to change over. 70 00:14:03.432 --> 00:14:13.712 Like, if Core really was compromised and Libbitcoin or, uh, Libbitcoin and, uh, Knots were- Libbitcoin, yeah... viable, it, it's good that those exist, right? 71 00:14:14.352 --> 00:14:19.052 Um, but, you know, going back to, like, we should have these things or we ought to, 72 00:14:20.532 --> 00:14:28.151 you know, I, I just go back to we let the market decide kind of, and the fact of the matter is the mind share and the competency is on, is in Core. 73 00:14:28.572 --> 00:14:35.952 They're the ones pushing out the best code, so- That is absolutely true... of course we're gonna go with that, right? Um- Yeah, that is absolutely true. 74 00:14:36.052 --> 00:14:45.412 There's, it's really an unparalleled, Core is the standard and should be the standard until other clients demonstrate themselves, like, resilient and robust. 75 00:14:45.612 --> 00:14:55.332 Um, but a step towards that, it's almost like Core, like, offering an olive branch to m- the, the kinda folks like me who think I would love to see a more diverse client set. 76 00:14:55.832 --> 00:15:03.252 But it's just so much work, and, like, nobody pays. It's just hard to get money for it. It's thankless. It's such a weird skill set. 77 00:15:04.452 --> 00:15:10.532 It's like if you've got the skills to do that, you could go make half million base salary, like, working for some AI company. 78 00:15:10.612 --> 00:15:20.972 So, like, are you gonna go work for free and have people, like, hate you [laughs] 'cause you're, like, very being criticized? Anyway, so, like, uh, this is a- That's a really good point. Yeah. 79 00:15:21.072 --> 00:15:31.322 You're already making pennies compared to what you could be making at a Coinbase or another, like, public company or a private company that deals with Bitcoin. Yeah. 80 00:15:31.332 --> 00:15:38.932 And so it's pretty amazing the ones who have stuck around are dealing with abuse. You know, like, shout-out to Gloria Zhao, for instance. 81 00:15:39.372 --> 00:15:47.412 She got put under fire from the filter crowd with some absolutely baseless and disgusting accusations. Absolute vile things, yeah. 82 00:15:47.472 --> 00:15:56.952 Yeah, and, and she's out here still just trying to improve the relay so, you know, uh, amending pool relay policies- Yeah, so- So shout-out. [gentle music] We are CleanSpark, 83 00:15:57.872 --> 00:16:13.912 America's Bitcoin miner, a publicly traded company with the largest operating hash rate, powered entirely by self-operated infrastructure across four states. This is our proof of work. 84 00:16:14.772 --> 00:16:23.612 We are setting the standard for what's next. Learn more about the intersection of energy and Bitcoin at cleanspark.com. 85 00:16:24.472 --> 00:16:33.872 The, uh, second question, which I took a really long time to get to, is you asked who's the lead maintainer, and the answer is Bitcoin Core no longer has a lead maintainer. 86 00:16:33.972 --> 00:16:44.152 Um, I, myself also actually kind of thought there was until I verified and I, I was trying to check up why. I guess I forgot who the lead maintainer is. But there, there is none. 87 00:16:44.232 --> 00:16:57.352 In fact, um, the, we have to get into the history of this and why that's the case. So there is no person who runs point, uh, officially in title. As we all know, with social circles, 88 00:16:58.632 --> 00:17:08.252 you can intuit what you want on, like, social hierarchy and dominance, but in title there is no official lead maintainer. So let's, like, roll the clock back. 89 00:17:09.332 --> 00:17:16.132 Where did the code originally live for Bitcoin back when Satoshi was writing it? And I had to jog my memory. 90 00:17:16.352 --> 00:17:27.702 It was originally posted on SourceForge, which is kind of like a pr- like a message board, but proto, like proto GitHub. Um, and Satoshi and other contributors worked on this. 91 00:17:27.732 --> 00:17:37.752 They would email it back and forth and, like, work on the code and run the clients and stuff. But then Satoshi left, and that's when Gavin Andresen took formal lead of the project. 92 00:17:38.032 --> 00:17:50.032 There was kind of that hand, that torch handoff that Satoshi had to Gavin Andresen, and Gavin led the migration of the code and the re- and creating a Bitcoin repository on GitHub. 93 00:17:50.432 --> 00:17:57.772 So in 2014, that repository and the project officially comes, uh, becomes, like, referred to under the name of Bitcoin Core. 94 00:17:58.332 --> 00:18:09.832 Then Gavin hands it to Wladimir van der Laan, who most people don't know, but then Wladimir has, was the lead maintainer for the next nine some odd years. Legend. Um, yeah, legend. 95 00:18:10.372 --> 00:18:22.476 And, uh, they did it with relative, like, inconspicuous, inconspicuity.Whatever. Low profile. They did it with a relatively low profile in a relatively neutral manner. Think about it. 96 00:18:22.516 --> 00:18:32.616 That's the block size wars in the middle of all that, um, and the, the Bitcoin Core conspiracies. Then we have what I think is the, an underappreciated shift in how 97 00:18:33.576 --> 00:18:47.736 the governance of the Bitcoin GitHub repo works, which happens when, um, he who must not be named, but we will on this podcast, Craig Wright. 98 00:18:48.676 --> 00:19:08.616 Craig Wright, backed by billionaire Calvin Ayre and head of the fork Bitcoin Satoshi's Vision, leverages the tools of the state and the, and the courts to, uh, sue people with their giant treasure trove, uh, with- or whether with, with, uh, um, Calvin's giant, um, war chest, 99 00:19:09.656 --> 00:19:18.676 uh, sue people. And it, like, created incredible stress and friction for anyone who was in any kind of ca- leading capacity for Bitcoin. 100 00:19:19.416 --> 00:19:36.636 And Vladimir, uh, kind of through, for a bunch of reasons, uh, decided to resi- uh, just step back and no longer be the main guy. And so there has honestly been a bit of, like, wandering the desert since then. Um, 101 00:19:37.736 --> 00:19:48.496 it was understood that Vladimir was the one who, like, had the, owned the Bitcoin account which owns the actual repository where Bitcoin Core lives. 102 00:19:48.516 --> 00:19:55.236 And then under that account, you can de- you're the owner, but you can designate admins and people with, like, certain access privileges. 103 00:19:56.356 --> 00:20:06.286 And so, um, uh, it is not known who Vladimir, if a person or an entity or a group of people or a network of people, how that account was handed off. 104 00:20:07.256 --> 00:20:14.996 Um, uh, it- we just know that it, it was that Vladimir was no longer the guy. And, uh, so 105 00:20:15.976 --> 00:20:45.876 now we have no lead maintainer, and this is specifically, uh, or this, the stated reason for this is be- is because there will be more Craig Wrights out there, whether it be the state or individuals or wealthy, insane billionaires, who seek to, uh, you know, use what is really a comparatively small amount of money to inflict huge friction and pain on the project of Bitcoin and to leverage particularly the social and legal layer to make people's lives difficult. 106 00:20:46.436 --> 00:21:00.116 And so, um, part of, that's part of why, um, uh, the structure has kind of evolved the way it is. Now, I personally, I'll make the assessment, I feel like it's a pretty, like, fair, egalitarian... 107 00:21:00.156 --> 00:21:14.456 It's in a pretty good place as it is. Um, but there is some warranted, uh, conspiracy and speculation about how neutral is the project if we don't actually know who owns the GitHub repo. 108 00:21:14.736 --> 00:21:25.616 Because the GitHub repo itself, I will push back really h- really hard and say that itself is not Bitcoin. It, however, is the absolute clear guiding light of what Bitcoin is. 109 00:21:26.496 --> 00:21:40.656 So the Bitcoin network itself is the code people choose to run. Um, but the, uh, like, the repo that people download all their code from, the ownership of that is actually ki- surprisingly murky. 110 00:21:40.686 --> 00:21:46.426 And this is one of the, the criticisms and subject of conspiracy that the Notts camp had, which was, 111 00:21:48.616 --> 00:22:00.956 "We don't know who it is, the banks, the spammers, the CIA, Mossad, they own, they're in charge, everybody's, like, working for them." And while we cannot prove that's not true, um, 112 00:22:02.056 --> 00:22:15.036 you know, they don't seem to be behaving like that. I think accusations of, like, um, complacency and, um, appeal to process are good accusations for another time. But, um, 113 00:22:16.096 --> 00:22:34.246 but that's ki- that's actually kind of, like, how we got to where we are today and why we don't have a lead maintainer, and it's also why, like, talking about this to the average pleb or even, like, trying to explain this to your dad is just so confusing. 114 00:22:34.276 --> 00:22:43.816 And this is why, like, you know, if a, if a, if a dumb little reportal- reporter dawdles along and, like, Googles a couple things and is like, "What? 115 00:22:43.976 --> 00:22:53.256 We don't know who owns this," they can spin up some conspiracy, and it can take on legs of its own and run a really far... and run really far. And, um, 116 00:22:54.756 --> 00:23:00.516 uh, so we could go a few other places after this if you wanna, unless you have a couple questions. 117 00:23:00.576 --> 00:23:11.645 I was thinking maybe we could, like, give you a little TLDR on this, uh, the new guy, uh, 72 or whatever his- Yeah, I'd love to learn more about charlatan. I just wanted to double tap what you said. Yeah. 118 00:23:11.656 --> 00:23:21.536 It's hard enough to explain how Bitcoin works without explaining how it's maintained and how upgrades are pushed and how they're integrated into the system. Yeah. 119 00:23:21.576 --> 00:23:28.696 You know, and if you start explaining this, you almost sound like a crazy person, and you- Yeah... almost sound... You know, you try to... 120 00:23:28.736 --> 00:23:38.626 This is why my father-in-law will never touch it, because if I tried to explain any of this, he'd say, "This is a $2 trillion asset, and the code base, you don't even..." First of all, he wouldn't even know what that is. 121 00:23:38.956 --> 00:23:51.656 Yeah. But he would say, "And no one knows who actually operates the code base?" That, that just breaks a lot of people's worldview, especially I think older, uh, generations with institutional trust. 122 00:23:52.056 --> 00:23:57.316 I think this is part of the reason why Bitcoin has been such a younger person's game. 123 00:23:58.096 --> 00:24:17.276 If you grew up in a time where every world event just chiseled away your trust in institutions, and you have the internet to kind of augment that feeling and show you all the reasons why those institutions no longer deserve your trust, you're going to think something like Bitcoin is actually not that crazy. 124 00:24:17.336 --> 00:24:27.284 It's also why for the older folks who are into it-They, they tend to be more of the Austrian camp, right? Or, you know, gold bug adjacent. So... Yeah. And you make up a really good point. 125 00:24:27.364 --> 00:24:31.024 I actually think your dad's hypothetical criticism is a pretty good one. 126 00:24:31.344 --> 00:24:42.364 Uh, and this is also [chuckles] why I would say, what if there are multiple clients that, uh, influence a Bitcoin and, uh, we had different risk profiles we could assign to them? 127 00:24:42.524 --> 00:24:53.984 Maybe Bitcoin Core, you know, I'm thinking hypothetically, make up Bitcoin Core, is one of the most, like, technical legitimacy, mind share, history review, but the actual ownership of the repo itself is a little ambiguous. 128 00:24:54.064 --> 00:25:00.164 Now, anyone could go fork that repo, copy that, start their own exact copy of Bitcoin. 129 00:25:00.174 --> 00:25:07.384 It's like, it's really more of, like, um, you- it's almost like you have a Facebook page, and, like, everyone can download the Facebook page. 130 00:25:07.524 --> 00:25:18.404 But, like, if you post something fake on the Facebook page, it can do a lot of damage. Doesn't mean that, like, you own what is reality in the information, but it's like you, you have a lot of influence. 131 00:25:18.444 --> 00:25:31.664 And so the ambiguity and unknown, like, kind of like, nature of that hierarchy and that, uh, governance structure, which is GitHub and platform specific, could be an issue. 132 00:25:32.284 --> 00:25:39.414 So other clients, uh, could say, you know, we have a different team. Maybe it's a private company. Um, 133 00:25:40.504 --> 00:25:54.024 you know, it can allow users to, uh, assess risk better, and I think investors will like this, but I, I know that's a toxic word for a lot of [chuckles] the technical folks. Um, so that's it. 134 00:25:55.084 --> 00:26:06.504 Um, or, or it could be, like, other Luke Dash Jr.'s who aren't insane, maybe other, like, you know, uh, crusaders who wish to take upon themselves, like, infinite work, uh, for personal vision. 135 00:26:06.964 --> 00:26:15.784 There's a few of those out there. And they-- It makes that-- It makes it more feasible for them to do it, and they can accumulate acolytes to, uh, you know, run their code for them. 136 00:26:15.984 --> 00:26:23.864 I think this actually can be a good thing. Okay, so this new guy. Again, he has two pseudonyms, Sedated and The Charlatan. 137 00:26:24.264 --> 00:26:29.204 I think I'm gonna just refer to him as The Charlatan 'cause that's what his, um, IRC chat name is. 138 00:26:30.044 --> 00:26:40.194 Uh, longtime comp sci guy, uh, from Europe, went to university, studied, you know, your sciences and your computer sciences. 139 00:26:41.004 --> 00:26:56.804 Um, and he worked on a lot of, like, wallet vulnerabilities, um, including wallet vulnerabilities in other ecosystems, namely Monero, um, which is the only, like, somewhat okay blockchain to have feelings for if you're a Bitcoiner these days. 140 00:26:57.544 --> 00:27:11.274 Um, and because it's really difficult and because, like, Sedated or, I'm sorry, The Charlatan, I would say might be a little bit like of an outsider in terms of, like, his, like, entrance into Bitcoin contribution. 141 00:27:12.324 --> 00:27:27.144 I think that might be why he had been working on separating the consensus out and contributing to that project. And that's-- And it also just requires a lot of very specific, domain-specific knowledge, um, and so 142 00:27:28.184 --> 00:27:38.944 years go by, lot of contributions, regularly hanging out in IRC, and I assume some in-person meetings to, you know, um, grab a beer and be like, "Hey, I'm a real person. 143 00:27:39.024 --> 00:27:51.474 I actually, you know, I'm not some AI model on the other side of the screen." Um, that has garnered a lot of trust. I've got some quotes from it. I'll kinda, like, wrap up with a couple quotes here, which is, 144 00:27:52.424 --> 00:28:04.544 um, I asked him in an interview recently, pretty directly, um, why he is working on this and his view on other client implementations besides Core. 145 00:28:04.564 --> 00:28:17.984 And he said, quote, "I would be fine with other alternative clients competing with us, hopefully reusing the kernel library to at least guarantee they can stay in consensus with us. I kind of welcome the competition." 146 00:28:19.004 --> 00:28:32.933 And I personally, I really like that. I really want folks like that to have, um, kind of a little bit contrarian views for, for the project. 'Cause a lot of people, like, they, you know... 147 00:28:32.964 --> 00:28:40.093 This is the thing with these open source projects. There's, like, this implicit kind of loyalty that, um, it, that is expected. 148 00:28:40.264 --> 00:28:51.184 Um, and that's because there's been a lot of enemies which try to subvert the p- the goals of the project. And so, like, you know, when it's something like Bitcoin Core, uh, 149 00:28:52.264 --> 00:29:08.844 you know, they're obviously anxious about people who have, like, non-core, uh, conventional views. So this really is honestly a bit of, like, a letting down of the guard by Core, um, 150 00:29:09.844 --> 00:29:23.164 not in, not for, like, a bad reason of, like, they're, they're, they're slacking on their duty, but rather, um, they're not circling the wagons as tightly because they're like, it, you know, Bitcoin is in a new era. 151 00:29:23.244 --> 00:29:35.084 It's much bigger than a s- than, um, you know, uh, a small conference room software project. It is now multiple trillion dollar asset, and it's on a path to become a hundred trillion dollar asset. 152 00:29:35.644 --> 00:29:43.134 And so I love to see this. We'll see how it goes. I don't know, like, [chuckles] how far along we are on the project. 153 00:29:43.644 --> 00:29:54.344 One of the things The Charlatan told me is that, 'cause I didn't know, like, where this, what the state, the status of, like, the Libbitcoin kernel consensus separation was, 'cause I just honestly cannot figure it out. 154 00:29:54.584 --> 00:30:02.784 He's like, "Well," uh, quote, "we need to do a bit better at public engagement and communication." To which I say, damn straight. 155 00:30:02.824 --> 00:30:15.704 Like, [chuckles] if the Core and a lot of the Bitcoin devs have a communication crisis problem revealed so clearly over the past year and, um, uh, yeah. So I'm excited. 156 00:30:15.824 --> 00:30:32.558 Uh, what I, I almost feel like this didn't have to be a news item, but because it's kind of our beat, it's a news item, and we're, it's almost like we're making it a news item.But I don't really see other, other people covering this, and it, because it's so, like, deep in the weeds of, like, how Bitcoin works, 157 00:30:33.708 --> 00:30:40.028 I just, I don't, I don't know if anybody, like, outside of the weird dev circles even follow this. But this is so important. 158 00:30:40.088 --> 00:30:51.758 Like, it's wild to me that I guarantee you Michael Saylor doesn't know any of this sh- Most executives probably don't, outside of the ones that you would expect to care about this. You know- Exactly... 159 00:30:51.768 --> 00:30:56.628 maybe your Jamison Lopps, maybe Dorsey, you know? But maybe not even him. 160 00:30:57.168 --> 00:31:04.908 Yeah, the thing that really makes this notable for me is it's not necessarily that we added a new maintainer, although congratulations to Charleton, it's why we added him. 161 00:31:05.508 --> 00:31:13.138 Uh, I say we, you know, like, like this is a sports team that I'm a part of. I didn't oppose it- You-... but also, yeah, I, my vote wasn't- But, you know-... even counted... 162 00:31:13.188 --> 00:31:19.228 my point being the rationale behind, okay, he specifically 163 00:31:20.268 --> 00:31:31.968 is m- he's specifically being appointed as a sixth maintainer partly because we want to give other Bitcoin clients the opportunity to stay in consensus with us and encourage competition. 164 00:31:32.548 --> 00:31:43.158 Think it's a good thing after all of the shit storm that we went through last year, and to, uh, just to get the monkey off of Core's back, right? And kind of put some of those, 165 00:31:44.248 --> 00:31:57.948 put some of that scuttlebutt to rest that they're out to just dominate Bitcoin, right? Yeah. Or that there's some grand conspiracy. And the thing is, uh, I- I think most of the grand conspiracy claims are really weak. 166 00:31:57.988 --> 00:32:09.668 They're, they're weak as heck. Um, give me some real conspiracies about Bitcoin 'cause I bet you could concoct them. And 'cause I, I'm all about informed conspiracy mongering. 167 00:32:09.748 --> 00:32:23.368 Um, none of this, like, half in the bag, like, bullshit. Um, like, Gloria Zhao, uh, you know, did these things to get maintainer, uh, appointment, 'cause that's very not, that's very absolutely not clear. 168 00:32:23.448 --> 00:32:33.408 It was very much a merit-based appointment. So, like, um, get good, we give- Including by Luke-... criticism. I-... who asked her appointment and said she doesn't have a choice because she's too good. Bro. 169 00:32:33.528 --> 00:32:39.088 Anyway, um- Bro. Well, we should end it there. Yeah. Um, I want a CTA, uh, call to action. 170 00:32:39.168 --> 00:32:49.728 If you, if you got this far, go make sure to, uh, read the, uh, newsletter, the profile piece I put out yesterday, Friday, on the Block Space Podcast. 171 00:32:50.428 --> 00:33:01.328 Um, otherwise, make sure to like and subscribe, and tell your friends, tell your mom, tell your dad about this episode 'cause the next one next week is gonna be spicy. [upbeat music]