Year of the Horse

0:01Istora MandiriOkay. Hello and welcome to Ethereum Classic Community Call number 45. Today is… Friday, January 16th, 2026. It's the first call of the year in 2026, so Happy New Year to everyone that's listening. This is a community call, and it's a voice discussion about Ethereum Classic. It's open to everyone, so please come and join. The call be published on YouTube, so let's be nice to each other. You can join us one hour before the call every week in the green room, if you want to chat offline. You'll find us in the Discord at the dev meeting voice channel. We have a community calls website, which you can browse past episodes, subscribe to the calendar, and read AI summaries at cc.etheriumclassic.org. And I wanted to mention the ETC Grants Dow, who are able to help you find funding for your ETC project. You can find more information at etcgrantsDown.io, and this is also for Ambassadors for ETC, helping spread the word. I'm gonna start the… call this week, with a bit of a sad note. Unfortunately, last year, November 2nd, 2025, a prolific contributor to Ethereum Classic, Donald McIntyre, passed away, And I'd like to just take a moment to… Respect his contributions, and say thanks to him. and he's been one of the major contributors to Ethereum Classic, so… I think, We all respect his contributions. So, thanks, Donald. And if you open the show notes, you'll find a link to Bob Summerwell's tribute to Donald McIntyre on the bobsommerwill.com website. If you're… looking to find more information and pay tribute to Donald's contributions. So, with that, let's move into the… the main content. I'm gonna be starting the call each month now with a pull requests corner to mention the open and pending pull requests that need attention, and or things that have changed in the main repositories, like Ethereum Classic. The main thing that's happened since the last call is that… ECIP1120 has now been merged. This is now part of the eSips repo, and we've, we were able to get that published, so now we have this as a starting point. And we can then move on to the, the next stages of the research required for both ECIP 1120 and potential, mechanisms within Olympia proposal. So that would be the, The… The smoothing mechanism and the number of blocks, for the distribution. that we talked about in previous calls. So, stay tuned for updates on that. And we're… I think potentially gonna be figuring out a research plan. To make sure we get everything Needed, and maybe on this call we can discuss the details of that, and what needs to be done there. With regards to, The different stages and the client code work that needs to be done to test. what the future parameters might be. There's a number of other PRs that need to be addressed, one being ECIP 1121, author, real Cody Burns on the call. Cody, would you like to, talk a bit about 11.21? 3:55Cody Burns | >Yep. Happy to, so the motivation behind 1121 is to get Ethereum Classic up with the rest of, Mainnet Ethereum and the other EVMs. So this is all of the, op codes and, Codebase changes that are, setting gas limits in blocks that are aligned with the current version of Ethereum Mainnet. And so, all of these are already in the, CoreGep client, since it's been, merged from upstream, so it would require testing on, the Mordor network, but these would all, be configuration changes that could be pushed, and, setting block numbers. And, with no additional, development effort, like it would take with 1559 or, a DAO or any of that. These are, code that's largely already in Geth, and it's a matter of setting configuration. So it's similar to Spiral and the other ones that we've done before. 5:01Istora MandiriAwesome. So… This would be a nice, I guess, low effort. Progress to be made this year, if this gets… Part of a… a hard fork. that would not affect the other, research and Olympia slash… I guess it depends how we describe Olympia, but the set of ECIPs, 1111 to 1115, And the… 11.20. Debate, notwithstanding. This can still move ahead, basically. And they could be deferred to a separate hard fork. 5:47Cody Burns | >Yeah, I think that this would give us everyone the modern features that, are across the other EVMs without Potentially burning it down with us. Or… I think we should decouple the two, because 1559 is going to require research and work and development. I think it's… either, we can set a date, say March, of if significant progress hasn't been made, then these can, we can go ahead with the, 1121. Elements on the testnet, and then… Continued research on, 1559 and, 1120. 6:32Istora MandiriYep. Awesome. Are there any notable EIPs? That think need to be mentioned, or is it all pretty much… smooth sailing? Is there anything that… Is specifically, requiring additional thought? When applied to a Thrum Classic. 6:54Cody Burns | >There is. So with the mainnet Ethereum, a lot of the improvements were around, the blobs and the blob sharding and PureDOS. And so… there's… 1, 2, 3, 4, 5, 6, 7… 8 or 9 that are, blob-specific that are deferred for Ethereum Classic, since we haven't decided what we're doing with With blobs, or if it's something that's interesting or useful for the L1. And then there's also, Some that are around the 1559, or, that were… Specific for proof of stake that don't really translate over. But for the ones that are actually, useful, I guess, to Ethereum Classic. There's some that are in the execution context, so memory improvements and saving historical block hashes, are in there. There's also, cryptography and some new precompiles, so the BLS12381 curves, these are for, zero-knowledge proofs and BLS signatures, verifying them on-chain. And there's also the, precompiles for, elliptic curves, so the algorithms that are used for, like, the pass keys in your phone, those precompiles are now in Ethereum. It's EIP7951, so this allows things like, account abstraction to use cryptography that's other than, just externally-owned account, and it makes wallets safer and more accessible to, the masses, so that's a… would be a real big win to have. 8:39Istora MandiriAwesome. Are any of these cryptographic pre-computes related to, L2? Does this open possibilities for… Any L2 technologies? 8:52Cody Burns | >Any that would use the BLS signatures for their verifications? I can't… Recall off the top of my head, if it is, which ones… Dude, but Yes, essentially. I mean, this makes it cheaper in general, to verify these signatures on-chain and proofs by them, so… all in all, I guess, a big win. The precompiles, in general, I guess, for the audience that might not be aware, their, Ethereum has been It's a world computer, as everyone knows. There's also, inside of that world computer, there's, operation codes, so, like, add, subtract, or, store this data bit. And these are all how gas is measured, and each one of those operations has a cost that, in microseconds on a compute… And so, this is how, in the back end, everything gets weighted, to figure out how much, transaction cost. We go off how many operations it does. And so, some of the operations that are really useful, like validating signatures, or doing SHA-256 hashes, or GICK hashes, are really computationally expensive as far as how many operations they take on a computer, but they're something that Ethereum and Ethereum Classic do as just part of the system operations. So, there are certain contract addresses that are set aside. Ones that start with zeros, All zeros, and then, a single digit at the end, so 1 through… I'd be lying if I said off the top of my head, I think we're up to, like, 10, maybe? pre-compiles, and so these are operations that we know are commonly used across, Ethereum, and, so adding the BLS signatures and the precompiles for, the, SECP256R1 makes these, we get to set the price for them, basically, or the system sets the price for them. So instead of being 2,000 operations in the system that would cost an inordinate amount of gas. you can use the precompile address, and then it only costs whatever the fixed amount is. And so this makes it easier for us to bring, cryptography on-chain. Without having to sacrifice, gas costs or make everything enormously expensive. 11:22Istora MandiriAwesome. And the actual gas costs for these… Operations. That we're just gonna follow upstream. Ethereum. 11:35Cody Burns | >That's been the plan so far, yes. Just go with the defaults. There are, occasionally the gas does get reset for some of the fields. So, whenever there was, Years and years ago, there was an attack on the network that was, during Hong Kong, one of the Hong Kong consensuses, and It was… one of the gas operations was, priced too low. It was, Storing data in a… or doing a delegate storage, or something like that. And an attacker had figured out how to exploit that, and they were just creating a ton of bloat on-chain of… they were creating contracts that just had, their storage filled up with… with just garbage, basically. And so, to fix that, the hard fork was coordinated And, it changed the gas price on that. And so, historically, gas prices are changed through that method. And there are… so, in ECIP 1121, there's, 6 different, EIPs that are just around gas accounting and, state access. So, Those are in there, too, and we are pulling from upstream, and it's more, I guess, about… It's a safety, constraint of… 12:58Istora MandiriThis is what. 12:59Cody Burns | >everyone's using. There's not a better reason for, for pricing these different on ours yet that has presented itself, so staying with this, it's one less variable to mess with. 13:10Istora MandiriInteresting. Looking at the gas accounting and state access, EIP7A25. This would introduce a protocol-level gap cap on the maximum gas used by a single transaction. Are you familiar with the rationale behind that? 13:34Cody Burns | >From, I mean, from the Ethereum side, or just in general, the concept of fly capping the gas? Yeah, it's, because it's a denial-of-service vector, so, whenever… for Ethereum Classic, it would be really important, because as this comes in, all the miners process every transaction that they get, or every node does before they pass it, in theory. But, so, capping the gas prevents An attacker could create a contract that just does a million loops, and uses up all the gas in a block, and but then fails on the last operation. And so, that would… they could flood the network with those, and it would, just exhaust the miner's time, or the validator's time in the case of Ethereum. And so, capping the gas, prevents that from happening, and makes the network a little more stable. Because we know what size transactions come. There's a gas cap right now. On Ethereum Classic. Again, don't, I should have written some numbers down before this. I want to say we're capped at 8 million right now. 14:41Istora MandiriYeah. 14:42Cody Burns | >Or we were at one point. And that, prevents things like, submitting really big contracts on-chain is where you run into this the most. So, it causes, developers to play kind of a game of golf whenever they're making contracts. Before they split out into a library and have a different contract for? What do they have for? And so… It ends up with really fragmented code, and Or modular code, I guess, depending on how you want to think about it. 15:12Istora MandiriYeah. 15:13Cody Burns | >And so this just makes it easier to make, more complex logic in one place. And, raises that limit that we've already had. 15:21Istora MandiriSo the… The 8 million gas is the block limit, is that what you're referring to? Like, the total gas limit for a block, or is that on a transaction basis? 15:34Cody Burns | >This is a single transaction. 15:38Istora Mandiri7… EIP7825 introduces on a single transaction, but the current Ethereum Classic block limit… is there a single transaction limit, or is that just a block limit? 15:52Cody Burns | >I'll have to check and get back with you, actually, now that you've mentioned it, and put me in the hot seat. 15:58Istora MandiriOkay. 15:59Cody Burns | >Yeah. Not intentional. I'm typing it back, yeah. 16:02Istora MandiriAs long as I understood, there was no, like, single transaction limit on Ethereum Classic, other than, like, the block limit, which… de facto transaction in it as well. But, this kind of… this is interesting because it plays into the 1-1 The 1559 discussion. And if there is a transaction gas limit, it kind of nullifies the point of having Very stretchy blocks. Because we are, like, intentionally capping. The… the transaction limit. So, there's no need to have those extra large transactions. There was some discussion in the past about the idea of it being beneficial to have massive transactions, but if Ethereum mainnet is intentionally limiting them, then I don't see any need for Ethereum Classic to have bigger than whatever Ethereum has, because that will become a de facto standard. 17:02Cody Burns | >Yeah, and 8 million is what our block limit is. 17:06Istora MandiriYep. 17:06Cody Burns | >So… Interesting. 17:12Istora MandiriAnd in that case, like, double… if we follow Ethereum's path for having double if the stretchiness is basically double, which is what a theorem's doing, then 8 million times 2 is basically… This transaction gas limit cap. with… A bit of… additional, wiggle room for miners to increase or decrease the gas limit, I guess. But. 17:40Cody Burns | >Because miners set the gas limit themselves. 17:42Istora MandiriYep. 17:43Cody Burns | >But this… I guess would limit the actual transaction limits. 17:48Istora MandiriYep. But that's actually quite a nice feature, I think, and… Yeah, for the anti-denial of service, but also… given that Ethereum is using this standard, then… there's really no advantage for Ethereum Classic to try and have, like, some special standard in this case, like… 18:12Cody Burns | >We're also a lot smaller block size than Ethereum, as Ethereum's 45 to 60 million, or 45 to 60… So… they're… almost 10x us. 18:28Istora MandiriOne of the… one of the research… questions with… 1120, was, shall we have, like, a 4X or a 16x stretchiness to blocks, which would mean an effective gas limit of potentially, like, a million, like, sorry, 100 million gas, or something like that. 18:45Cody Burns | >Yeah. 18:46Istora MandiriTemporarily. But there's li- there's, like, no advantage to that if… the transactions are capped to 16 mil. So, a much more… in line with Ethereum, Block elasticity seems to be more appropriate then. if, if this, if this, set of ECI sorry, EIPs is adopted. Which I think seems very reasonable. 19:12Cody Burns | >Yeah, and… I can't… I've been deploying contracts a lot lately. 8 million's… It's tight, but, it's not… incredibly restrictive. A lot can still be deployed, so 16 million's… . 19:28Istora Mandiria really safe buffer on top of that, because it's, what, double? 19:32Cody Burns | >Right. And then the block elasticity would let the miners, expand up to however much they need. 19:41Istora MandiriYeah, and with 1559, then they would get that 16mm if needed. 19:46Cody Burns | >Yep. 19:48Istora MandiriCoke, that's, it's a nicer… Coincidence that that is almost exactly perfect for a single classic. Cool. Yeah, I'll need to have a closer look, on all of these particular EIPs, but… I don't see… At least at first glance, any reason why this… should not… be, acceptable. 20:21Cody Burns | >Yep, and… It's in the, we can share the link out in the call notes for this, so we can get comments on it. It's in the repo. It'd be good to have discussions on it, too, and just get everyone's… Just overall thoughts, 20:37Istora MandiriYep. 20:38Cody Burns | >Because, yeah, as we discussed, I mean, 1559, it is important. It's one of those things we want to get right, and take time to develop, and… But we also don't want to fall too far behind, the rest of the Ethereum world while we're doing it as well. our gas works as it works today. So, yeah. 20:58Istora MandiriAnd I've just approved the… The pull request for 1121, so… You can go ahead and do the honors of merging those. You're okay with that? Yeah. 21:13Cody Burns | >Sending it in now, and we'll open it up… I'll create a discussion thread on it also in the ECIP. world. 21:37Istora MandiriIt mentions that this ECIP introduces no new protocol changes and does not affect backwards compatibility. 21:45Cody Burns | >That's probably not true. That was a… let me edit that, before we merged that. Yeah, that's boilerplate, Good call out. Sure. Okay, so I'll get that edited and, merged and open for discussion. 22:17Istora MandiriAwesome. I'm glad we're able to discuss that. And yeah, that would be a nice win for Ethereum Classic this year. That seems like it's not too… like, controversial. Okay, There's a couple of lingering PRs open. One is… an external ECIP validator gem that was causing issues. It's not pressing, but… if I could remind, Maintainers to take a look at that, and also 5551. I was hoping Chris might be able to join the call again, but, This is the one… 23:11Cody Burns | >reclassifying Olympia? 23:14Istora MandiriYeah. 23:14Cody Burns | >is that… 23:16Istora Mandiribasically, I think Olympia should be standard track core. In… in line with the… the other conversation we had with 1120. But neither of those are, like, super pressing, so… I basically just wanted to flag the PRs that need attention at this point in the call. And we can look at… 23:41Cody Burns | >Yeah, this is good. 23:42Istora MandiriIn the coming week. Cool. Well, I guess we can move into the main topic. And Freebirds, Chris Mercer mentioned a… a comment in the Discord, which I wanted to… maybe… address? And, yeah, he's basically bringing up the funding issue, which we have talked about in previous calls. and to… Kind of trim things down, concretely, the risks he's watching Are client maintenance slowing down and stalling? consensus EVM compatibility risk over time. Public RPC, availability degrading. Explorer indexing funding degrading. if infra… And maintenance slip exchanges miners' users feel at first via liquidity and integration friction. And his question is, how do other networks keep core maintenance and critical infra predictable and sustainable without becoming permanently dependent on a single sponsor? So I think there's a number of… Points in there. And… With regards to, like, the… exchanges and… Block explorers and that kind of stuff. I'm not sure if that is something that… Can really ever be covered by… a protocol layer. funding mechanism for a project like Ethereum Classic. I think if the argument were to be refined to client maintenance, I think… There's more of an argument there. I… The problem, I think, is that the risk of like, introducing… I mean, we've had this conversation many times with the Treasury. 25:46Cody Burns | >safe. 25:47Istora MandiriIt's the whole, kind of, debate that's going on, but… 25:55Cody Burns | >It's a very hard problem, and… for, from the co-op's point of view, I am on the board of the co-op, the… The co-op is still, alive and funding things. Right now, the focus is on, supporting ecosystem partners, like, I've been doing a lot of outreach with the custody providers that are, servicing, pretty much all of the industry right now, so the fire blocks, anchorages, DF&S, all of the ones that are providing custody as a service for banks and businesses and users who don't want to manage keys are now all supporting Ethereum Classic, and continue to keep up that relationship with, All the exchanges and liquidity providers as well. So, that outreach is still going on. Ethereum Classic is still well supported. We're, still the Pepsi to Ethereum's Coke of… in the… fullness of time, whenever block rewards run out and everyone's transactions are paying for themselves. Proof-of-work is a more efficient version than proof of stake for a blockchain system, transactionally. And proof of work is still the most fair distribution system of coins while, the block reward is going on. So, none of that changes. It's still the narrative that's there in the world. The… client maintenance is, definitely a concern of mine. We have CoreGath as our main client, and, the ETC grant style is Funding, some developers to come on board to continue with the maintenance of that, as… the… development teams, who will be taking over long-term, come, but, Diego's also been doing a lot of work with, other clients, so the Nevermind client and the, Basu client. Finding ways of, they have… toolkits that allow us to build on top of them, so Ethereum Classic is a lightweight plugin that lets you use these other clients. Which is, I think, a more sustainable long-term plan, then, the co-op. Or any entity, funding long-term the… the note itself. it's… I said it's a common problem across open source. Bitcoin is the only one who's somehow managed to figure it out. People fund the developers, just Because… or the developers were there early enough and got all the funding they ever needed. But, other projects aren't so lucky. And… I think most blockchain projects, whenever you pull back the covers, are… it's really a team who's there, and they're dedicated, and they're putting in the work. So, not to… Downplay what any of the blockchain networks or teams are doing, but it's… A lot of the decentralization is in the spirit and their heart, rather than the network itself, as far as funding and development goes. And so… We are seeing the ones that were more centrally funded, so the Hederas, Ripples, Solana, those are the ones that are… In the news cycle right now, they still have their huge war chests, and they're entirely centralized, pretty much, from the development and roadmap point of view. And so, that's the risk you run. You do have funding, you do have support, you have people in Congress doing lobbying, but you also are kind of locked in on a mission. of… whatever your chain's doing, whatever the company's doing, that's the mindset of it. Zcash recently, has… Been in the news of… they're famously funded by their block reward. And, they've… They were non-profit companies, or all the entities were set up as non-profits. And, so they're… governance funding right now is going through a transition, and so the companies that were nonprofits have been funding themselves in the meantime. And if you're a development company that has developers who are doing really niche things, like building zero-knowledge proofs and wallets that incorporate all of this stuff. That's… an expensive skill set to keep on staff. And so, their… the ECC made a big announcement of, all their developers had quit, and that, There was a cycle of that in the news, but what had happened was they moved… they had moved from being a non-profit to being a for-profit company, so that they could find out how to actually get funding through their wallet. 31:11Istora MandiriI see. 31:12Cody Burns | >And… 31:13Istora MandiriFruit through their wallet, not their grants? 31:16Cody Burns | >Right, through their wallets and not their grants. So the ECC, the electric coin company. was the group that originally started Zcash, and they had built the Zcash node, and they had built a wallet. But during the life of Zcash. The Zcash Foundation, which was another non-profit group that was, managed the IP, built a node as well, and so now they maintain the core node software, and the electric coin company had the Zashi wallet, was what their product was. And, they did outreach in Washington, D.C, and were active in the community and other things as well. But their big, product was the Zashi wallet. And so, wallets are, like I said, one of those things that takes a lot of development, a lot of effort to keep up with. It's a non-trivial task, and so, Everybody else in the blockchain ecosystem gets paid as you send a transaction, so the other side gets paid, the miners get paid, but the software that you use, is one of those things that is, for some reason, burboding to get paid for in blockchain. So, the, Geth nodes and the wallets themselves are not something people traditionally pay for. And, that is where I think a lot of development teams are right now, is they're trying to figure out, they love the space, they love the technology, but how do they get paid for it? And that's where the custody providers, are… coming in for businesses, because they, handle all the complexity of key management and accounts and all the weird stuff that banks and businesses don't want to deal about when they're doing crypto. And, they provide just an easy interface for that. And so wallets do a similar thing for, For everybody who uses blockchain, and for most people, their wallet is… their entire life on the blockchain. They're not gonna run a node, they're not ever gonna build an application on top of it. They want their Brave wallet, or their Brave browser to take them to a website, and they can play with their crypto cats, or log in and make predictions on what the weather's gonna be. So… Or even just… 33:40Istora MandiriSorry. 33:42Cody Burns | >No, go ahead. Sorry, I'm on a log. 33:44Istora MandiriYeah, I… You, you're talking about… basically Zcash moving to this wallet model, and, like, the co-op already does operate a multi-sig wallet, right? So, is that something that could be… Turned into a monetizable thing that helps sustain development in other areas. 34:07Cody Burns | >It… yes, it could. The co-op runs, the Gnosis Safe software. As a service. And so, one of the things, I guess, one of the goals from me this year would be to get that, fully integrated with Gnosis, so whenever that was stood up, it was… Early on in the, multi-sig or Gnosis Safe Journey. And so, since that… implementation on Ethereum Classic. Gnosis has moved to a more modular architecture, and they support multi-chains, and so now there's a process of, deploying contracts on-chain using their, Safe singletons and registering with them so that, Ethereum Classic could be fully supported in the Gnosis Safe app as a first-party chain. 34:54Istora MandiriAnd so, I think that… 34:55Cody Burns | >That's the best route for that. 35:00Istora MandiriBut there could still be, like, a CASA node style. like… third-party safety… I don't know how to describe it, but, like, one of the signers being, like, a trusted party. That provides, like, recovery mechanism, for example. 35:19Cody Burns | >Yeah. 35:20Istora MandiriAlso, just the whole onboarding process is complicated and scary for a lot of people, so having hand-holding there would be an opportunity. And I guess, also, I think there's some other, like, fallback, because one of the issues with… Gnosis system is that it's very heavily leaning into their architecture. And I believe that there's other… like, less… Complicated, or, like, low… low… PHY versions that are still compatible. with. The notice contracts, but use, like, a standalone front-end, for example. That don't require their whole backend system. 36:02Cody Burns | >Yeah, that's… 36:04Istora MandiriHaving that redundancy of the front end as well as the additional services that help onboard people could be a package in itself that is valuable, and people might be willing to pay for, and might even be able to pay a percentage of what they're holding. 36:21Cody Burns | >Well, that's… that's where the nonprofit side gets kind of tricky. The co-op exists because, it exists entirely on donations, and, the money that it's running on right now was, generously donated by the Grayscale Ethereum Classic Investment Trust. It had set up a fund for Ethereum Classic, and as part of the investments, it funded the ecosystem. And so, that money has been what the co-op's been running on. There is a, Community Multisig that's still out there that… We haven't ever decided what to do with as a community that could be used for this if the co-ops, providing value, To the community, and it is, but the co-op is designed to, work off donations or work off, projects in the ecosystem that find value donating back into them. 37:16Istora MandiriYeah. And. 37:18Cody Burns | >So, running, a service or doing consulting work out of the co-op is, Would jeopardize what its, charter is, as far as, Taxable entity and things like that. 37:33Istora MandiriUnderstood. 37:34Cody Burns | >Which is the conundrum that the ECC found itself in. 37:38Istora MandiriRight, exactly. I'm seeing the parallel. 37:43Cody Burns | >Yes, and so. 37:43Istora MandiriI guess… 37:47Cody Burns | >One way that could be helpful would be if the co-op was valuable to projects that are actually running in the Ethereum Classic ecosystem, and then those groups We're able to give back, because there are, projects that are running and live, and people are making a living out in the space, so getting the co-op connected with those people and bringing value to them, and having them donate back would be helpful. 38:16Istora MandiriI see, yeah. And it would… I mean, that's basically kind of already happening with the Bitmain. 38:28Cody Burns | >It is. Yeah, Bitmain and the ETC, grant-style, are separate from the co-op, they have their own, grants process, and, yeah, no, I think that that's great as well, of… People just investing in the space on their own, or, yeah, it doesn't have to be through the co-op. 38:48Istora MandiriAnd they're not… they're not focused on client maintenance at all, really. It's more for… ecosystem expansion and education, I suppose. And the client maintenance being the key thing. still can be… basically… solved by the co-op for the foreseeable future, as far as I understand. 39:15Cody Burns | >Yes. Nodes are safe, they're on… they're online and maintained for the foreseeable future. 39:23Istora MandiriCool. This might be a good time to shift into the next, topic, which we kind of had a bit of a chat in the green room about. Which is related to… A research plan, and how things might actually How we can write some code, at least, for potential options for 1559. And as a non-Go developer. I don't see, like, a massive… barrier anymore due to AI tools, in terms of actually implementing Like, relatively simple. features, especially if there's reference implementations already in other clients, like BESU, which there is, for the… for the block. Subsidy return to minors. System. That 15… that, sorry, 1120 proposes? And that would be, like, one of the requirements in the research phase to determine whether or not the client will be able to handle it. Obviously, I would not, as you signalled, be comfortable with Publishing production code. Without having, like, someone that knows what they're doing, at least take a look at it first. So maybe this could be a model whereby we can… Cobble together something that's kind of working. And… Only at the final stage get some more expensive and trusted eyes on it to get it past the finish line. into production. This may be a more, like. Economical way of doing development going forward. 41:17Cody Burns | >Yeah, I'm definitely, like… Before the… before the show, we were talking, and Cloud Code is amazing. It blows my mind, every time I use it. So it's… definitely within the next 5 years, gonna completely replace development. We're coming up really close, I think, on that, too. So the FACUI client, that I've been testing with is, that's… was kind of my testbed for the same thesis that you had. I don't write Scala, I don't write Java code, and that Mantis client was entirely written in it, and so… using, the AI tools, able to add all the features that were, missing from, between the Magneto fork and, the latest spiral fork, so… Yeah, Claude Codes. Amazing at reading codebases and knowing how to do patches, and having well-written specs. is… really helpful with the code, so you can give the AI the spec, the code base, example, implementation. So, since we have CoreGeth running, I was able to point to it and say, this is the reference implementation as we're building, this function, we need to validate that, we're following the same pattern as it is. And then, so yeah, the… the space we're in and the open source side of it has, lends itself really well to AI development. The… the safety part and the… All the slop is, still an issue, but, For getting a privacy out the door, this is hands down, the way to go. 43:11Istora MandiriThere may be some… some useless code paths introduced, but at least it works. 43:16Cody Burns | >And that's where the… that's where the final editorial from, like, a… 43:21Istora Mandirian actual seasoned Go, or whatever language, or… writing in is extremely useful. But I think a lot of the… the work… Can be done by anyone at this point… at this point, as long as they're somewhat… competent developer, And… Knows how to create the validation. that's required for the AI to… to kind of… to progress. And I'm thinking that having multiple reference clients, sorry, multiple implementations. is super useful for enhancing that validation loop. So if you can have a monorepo with 3 different code bases, and they can all sync. And you can run a set of tests, and they all behave as expected. It's… Highly likely that… At least they will sink in real life. 44:18Cody Burns | >Yeah, I find that what I'm doing most of the time is defining the constraints on the system, rather than the actual code itself. I'm writing the… The tests, that it has to pass for, just part of the software lifecycle of… it writes the test, or I write the test, it writes the codes, so I can tell it what it needs to do to pass, and… The code may have a million different paths that aren't actually used, and fun comments in it, but as long as it can pass the test and do what it needs to do, and it can fail in a predictable, deterministic manner, then The constraints work and the code works. So… Right. 45:02Istora MandiriAnd you can tidy things up at the end. 45:05Cody Burns | >Yeah. You know, make sure it does what it's supposed to do, and not do what it's not supposed to do. And then, The cleanup and pretty part of it is… A human task. 45:18Istora MandiriCool. And I think one of the… It'd be really nice to have, like, a… An environment set up where we can quite easily implement these things as non-Go developers, and test them. and have, like, A set of tests, and a suite that we can run. To… to move fast on. 45:42Cody Burns | >book. 45:43Istora MandiriThis kind of development, and… For both… for whatever is implemented in 1559, there's a number of things that… Will need to happen. So… That seems like a really good starting point to set up. some kind of, staging ground for that in Go. Maybe a full coat. 46:06Cody Burns | >Yep. 46:07Istora MandiriYep, go ahead. 46:08Cody Burns | >Oh, no, I was gonna say, there is an Ethereum test harness that's used for their clients. It's a Hive. It's an end-to-end testing suite that all the, execution clients run through. That might… could be… something like that could be adapted, probably. 46:29Istora MandiriYup. 46:29Cody Burns | >and GitHub at, Ethereum slash Hive. And that's… that's its whole function, is making sure that, it kind of fights the nodes against each other. For Fukui, I had, the Gorgoroth testnet that I was using. Which is a similar thing. It would spin up, Basu nodes, Geth nodes, or the Fukui nodes, and, Make sure that they sync, make sure that they're able to pass transactions, and And all of that. 47:00Istora MandiriWoof. 47:01Cody Burns | >Let me… let me see, I… Mike can… I'll see what the effort is to break that out and merge it into the Ethereum Classic so we can have… Kind of a testing bed that's not in any one project. 47:16Istora MandiriThat'd be awesome. And how does it work with… Importing the different client. versions. Are they, like, submodules? to get billed. 47:26Cody Burns | >It pulls them in as, Docker images, so, just from the Docker Hub. Or it can build them from the latest version, in your repo, and then store them in GitHub Container Registry, if we wanted to do it like that. 47:44Istora MandiriRight. 47:48Cody Burns | >And that way, we can keep it up to date, because anytime there's a push to one of the repos, it would, could automatically rebuild. 47:54Istora MandiriYeah. The Ethereum Classic? 47:59Cody Burns | >Take a pass at it. 48:01Istora MandiriOkay, does Ethereum Classic have any… Images pushed? To the container thing. on GitHub. 48:11Cody Burns | >the get node is in the ETC Labs core, Docker Hub. I don't believe we have one in… or an official Ethereum Classic, docker Hub repo? I do think we have it provisioned, I don't know if we've ever used it. I know we have one for the… app, repo as well for Linux, but we've never pushed code to that either. Everything's just always come out of whichever Group was doing the nodes at the time. 48:59Istora MandiriThis might also be a nice thing to… Set up with… 11.21. If it's just a case. Flipping some switches. As a, as a kind of sample. It'd be nice to… it'd be nice to get, Bessu and go… Cool gift. 49:29Cody Burns | >We're gonna take a passive this weekend. 49:30Istora MandiriCool. 49:32Cody Burns | >I have some cycles. cool. I do have to drop here shortly, I'm getting pinged. Alright. 49:41Istora MandiriYep, we're coming up to the hour, so… Yeah, thanks for joining. I can… I can bump the… the other topic to a later call, as it's not super pressing anyway. So… Yeah, I'll try and organize another call for next month, in February. And… Until then… Take care. 50:04Cody Burns | >Yeah, take care. 50:06Istora MandiriAlright. Thanks, Cody. See you next time.

Year of the Horse

Preamble

Announcements

In Memoriam: Donald McIntyre

Pull Request Corner

Let’s Dive In

Freebird Comments

Research Plan

Consensus & Signaling: Lessons from Bitcoin

Bonus 1: What’s Next for ETC?

Bonus 2: Quantifying ETC’s Distribution

Call References

AI Summary

Key takeaways

Discussed topics

ECIP1120 and Olympia Proposal Update

ECIP1121 - Ethereum Mainnet Compatibility

Specific EIPs in ECIP1121

Tribute to Donald McIntyre

Funding and Sustainability Discussion

AI-Assisted Development Approach

Testing Environment Setup

Community Call Schedule

Action items

Full Transcript