Recorded

Ethereum Classic Community Call #40

Community Pulse Check

Friday, April 25, 2025 at 15:00 UTC (Saturday, April 26 in Asia)
UTC 15:00
ESTNYC
10:00
GMTLondon
15:00
CETBerlin
16:00
GSTDubai
19:00
ISTNew Delhi
20:30
ICTBangkok
22:00
CSTBeijing
23:00
JSTTokyo
00:00+1 SAT
AEDTSydney
02:00+1 SAT

It’s been a while—let’s catch up.

Join us on Friday, April 25th at 1500 UTC in the ETC Discord for a casual voice chat. Whether you’ve been around or just checking in, this is an open space to reconnect, hear what folks are working on, and share what’s on your mind.

No formal agenda, just a chance to get a read on the community and talk about where ETC is headed. We’ll keep it light, respectful, and productive.

The call will be recorded and uploaded for anyone who can’t make it live.

Meet us in the ETC Discord’s #meetings channel Calendar Link


Full Transcript

0:42sure. Hello everyone. 0:42Thanks for taking the time to join today. 0:45This is This call is meant to be informal. 1:00It's We haven't had one of these in a while. 1:03It's a chance to catch up, talk about where etc stands, talk about the ideas we've been thinking about or we've been kicking around in the channels and in email threads. 1:11So this is kind of bring everyone together so we can discuss big picture is etc still here to stay if we want it to not just survive and be a coin that's kind of moving sideways for the last couple years and we keep coming to the 1:31chat rooms and just so we can troll each other. 1:33I mean, it's if it's going to survive, it's going to be because people that like this that show up to meetings, stay engaged, help shape the future. 1:43So, these are people in this call are the ones that uh I guess we need to talk to. 1:47So, I mean, there's big things that we need to talk about as a group, as Ethereum Classic, like core infrastructure, how we want to manage GT or what long-term view is on that if we want to keep chasing the latest updates of Ethereum or whether 2:07it's um we do other engineering on our own or how we decide on which forks happen. 2:16It's uh there's not a clear path right now or clear clear process on that. 2:18So coming together around that, how we make those decisions, funding and grants, how we engage with uh people who are wanting to build on the network, how we can have sustainable funding for all the things that aren't the sexy parts of cryptocurrency like running block explorers or uh 2:38keeping communication channels open, uh running test nets, things like that. 2:52as a cryptocurrency how we want to talk about it uh as a group still is the world shifted today from where it was even a year ago on uh standards around cryptocurrency. 3:07we're getting a lot more uh legal clarity around what rules will be in place around crypto and things involved in it. 3:16So defining what Ethereum Classic means in a world where there's thousands of L2s now there's uh tons of alternatives and block space is mostly unlimited. 3:30How do we get people to realize the real value of etc? 3:32The philosophical thing that keeps us all tethered to come to these chat rooms and the community. 3:42There's only what seven of us here of a top 20 community is probably the most important for this whole thing to work. 3:55We need to bring people in, the people that are here, engaged with them. 4:00We got to figure out how to get everyone doing something productive. 4:07Uh I mean, you're if you're here today, you're already part of the story of what's current with etc., what's the latest voice? 4:14What's the who's driving the changes in it? 4:17This it's this group. 4:19This is the people who have come together. 4:20We want more builders. 4:20We want more node runners. 4:22We want more people testing and translating and spreading word. 4:25But there's there's no central company or no foundation that's going to be able to step in and run everything and just give Athereum Classic everything it needs. 4:38It's ours. 4:38It's so what we do next depends on all of us here in this call. 4:43So uh thank you for coming everyone. 4:45Uh and yeah, let's uh let's start the conversation I guess. 5:03tackle each of these or or how to discuss them. 5:04Uh, so feel free to come up to you, chime in. 5:06Um, I guess if no one else has any topics they want to discuss, we can just run through the ones I just hit. 5:22talk about uh what we need on core uh core GU moving forward. 5:26Um I think that's probably a good start. 5:29Uh just in the sense that it's such critical software. 5:34Um generally the public doesn't really know where that stands after recent announcements of funding and things like that. 5:44Um, in fact, we don't even know who's working on it. 5:46We don't know if there's anyone staffed to work on it, uh, my understanding is that uh, the two developers that actually were, uh, able to work on it, uh, have left ETC co-op. 6:00So, um, and then I know that there's another developer there, Diego, but my understanding was that Diego was a Bezu developer. 6:09So, I don't know what he's been doing since uh Bezo has been dep deprecated for Ethereum Classic for I mean I I thought it was like 2023. 6:17Um I I forget the date, but um but if you could just fill us in maybe in what's going on with that. 6:25Definitely the last call we had was a community call on this stream and it was essentially uh etc co-op uh stating that they were running out of money. 6:35So, um, that's kind of where the conversation has left in this series of calls. 6:42So, I hope that's helpful. 6:47That's helpful. 6:49Uh, yeah. 6:49And right now, Diego's the uh core developer that's still with the co-op. 6:56So, he's still here. 6:56He's still doing patches as they come in from upstream. 7:03Uh, Basu still connects to Ethereum Classic. 7:07Uh, it's just not the preferred client. 7:09So, it it does exist. 7:09It it works. 7:13It's there. 7:13Uh, and Diego's work there is probably one of the things that will help us. 7:20Um cuz while we were doing whatever we were doing in ETC land, the rest of Ethereum moved on from the monolithic client standpoint of they have one node that does everything. 7:34They've moved to a modular architecture. 7:36Around the time of the merge, they split out all the consensus logic from the execution clients. 7:43So, GE got its uh or GE can run with any of the consensus clients. 7:48It's a separate node. 7:50Bas can run with any of the consensus clients because the execution is separate from consensus. 7:56But with ETC, we're still have a everything's all in one box. 8:00Our multiget has our mining, it has uh the execution, everything's all packaged in one. 8:07So we're always kind of tied to whatever changes are coming through from upstream on it. 8:14I mean I guess longterm the ideal would be to have something similar to the proof ofstake validator nodes for proof of work have a separate uh consensus node that manages etc's custom logic that isn't from upstream. 8:32So our handling of the bomb, handling how we do difficulty adjustment, uh the happening or piffning onchain, all of that would be in a consensus node and then all the changes from upstream Ethereum to the EVM would just be directs to whatever execution clients running. 8:50So we could use this consensus client with any execution client. 8:54It wouldn't just be tied to G or BU. 8:56It would be um any of them would be available to us. 9:01Hey, can I just jump in here? 9:01Hi guys. 9:03Um, I just want to let everyone know that Diego uh since the other devs joined at the beginning of 2023, he's been working with them uh with Corg. 9:10So, he has he may not have as much experience as they had, but he is able to do what's necessary with Corg as well. 9:22So don't be concerned that he's just been there on his own doing stuff with Beu and doesn't have the ability um to do what's necessary now because he does. 9:31So he's had, you know, two years of experience working with those guys. 9:35They were working as um a really tight team. 9:37So uh he was able to pick up all that knowledge over the last couple years. 9:43Cool. That's very helpful. 9:43Thanks. guess the where we're at on development. 9:54I mean, talking about, Cody, um do uh is Diego competent to do that development work? 10:07Is that what he's tasked with doing now or um is that something that we will need to staff for? 10:13And you know, and it sounds like a pretty deep plan to split those apart. 10:20Um, has another team already done this for proof of work? 10:22Uh, you mentioned that it's it's happened for proof of stake, but has that been done by any different network that uses Gath? 10:32Uh, so so we maybe have some audits or source source code to work with? 10:37Um, do you know any of that stuff by 10:39chance 10:39or 10:39is 10:39it 10:39still 10:39too 10:39early? 11:06anyone talking. 11:06This is some of the old issues we had with Discord. 11:08So, I'm going to re I can't hear either. 11:10So, happened in the past where this is why we were kind of moving to Twitter spaces for these type of go 11:32on my phone. 11:32Maybe go on your phone if 11:34you're 11:34on 11:34your 11:34laptop. 12:24I guess I dropped out. 12:24Sorry. Where did Where did I leave off at? 12:26You dropped out before you started talking. 12:29Like right as I was finishing talking. 12:30Oh man, that's crazy. 12:33So y'all have just been listening to silence for the last Okay, honey. 12:41Uh yeah. 12:44So I guess was Allison audible. 12:54but I think Okay, cool. 12:58Yeah. So uh what I had said I guess out of the whole thing. 13:03Sorry. We could hear you up until uh I was asking you. 13:08I was doing a follow-up and I had just asked you uh if you had done the research on it like do we need to staff up for it? 13:14Any of those things? 13:17Did you hear that part? 13:17No, I didn't hear that part. 13:19I think got dropped. 13:22Okay. So, I had we heard you uh kind of explain the the uh core guest stuff and splitting the proof of work out and everything. 13:29Um is Diego capable of doing that? 13:32Uh is do we need to find staff for that? 13:38Um, is there already source code? 13:38Has another team already built the uh split out the core gath for proof of work? 13:47Um, or is it just too early in the research? 13:49What kind of what's what's the situation with everything you just talked about? 13:55I would say probably too early in the research right now. 13:57Uh, I don't think we would do this on his own. 14:01I mean, he'd be a great candidate for coordinating teams. 14:06Whenever Ethereum mainet did this, it took a effort of several teams building this out uh over months to get it put together. 14:16It's u it's not a small effort, I guess, is the I don't want to trivialize it and say we can just copy and paste some code. 14:24This would be actual engineering work that would have to be get done. 14:27We'd have to define how the protocol works together. 14:32make sure we're matching up with the API spec that they have for the consensus nodes on mainet for um for their proof of state. 14:41So, we'd have to use the same interface. 14:44We'd have to out I'm sure there's a ton of trip wires along the way. 14:53So the short answer is it's it's a decision we have to make as a community that we have to commit to and figure out the work that needs to be done and start going down that path. 15:05It's not a a quick way or something we can just throw over the fence and hope that one or two developers pick it up and run with it. 15:18Yeah. And so from my understanding, it sounds like this is going to be a necessity as we continue to maintain uh protocol parody with the EVM standard, right? 15:26Um as it's just going to keep getting worse if we don't make this this change to the client. 15:35Yeah, it's we're on a limited timeline with how long we can use the current Ethereum clients. 15:40They've all moved to proof of stake or mainet's proof of stake now. 15:45So anyone who's building a client for Ethereum is just building an execution client or they're just building a consensus client. 15:50It's there's G itself has started to chop all the code out for proof of work. 15:56Uh Basu did the same. 15:59So it's if we don't commit to figuring how to make this work, then we're going to have to fully maintain our own code in the future going forward, which is an option. 16:15Uh just keep the lights on, keep doing what we're doing, evaluate forks as they come, and hope there's no breaking changes. 16:24Um but that's I guess that's what we kind of need to decide as a group. 16:29Is this something worth engaging on or is this are there other things that are a higher priority right now in the overall development pipeline? 16:48continue with or is this a moment where um there might be another client out there that you know has more features or is more performative uh that it would make sense to maybe uh perform this work on instead of the guest 17:06stack? How do what what's your view on that? 17:08Or is guest still the upstream of choice? 17:15It would be more of a choice of which uh execution client you want to use. 17:18Right now we're tied together because that's where everything any questions about this? 17:33Anyone Anyone else in the chat? 17:44potential beforeation of the node into an execution client and and into a consensus client mean that there's going to be a layer 1 and layer two within the network or 18:00some analogy of that. 18:22and miners running only the consensus client and other people in the world running only the execution client and they have to connect over the internet to to integrate information and things like 18:36that? Yeah. 18:51Cody, I don't think we can hear you again. 19:03We can we can fire up uh Twitter spaces real quick and probably share a link and get a recording going there and then LOL can can participate as well. 19:10I think that's something maybe. 19:13Yeah, I think so. 19:14This 19:14obviously 19:14is 19:14not 19:14working. 19:50that answer your question? 19:50We're not hearing you. 19:52Um I think I think Freeird said he's going to just start a Twitter spaces and then also LOL can take part because 19:59this is not working well. 20:21we wait for the link there. 20:33good. Pretty good.