Focusing on ECIP-1121

0:01Istora MandiriHello, and welcome to Ethereum Classic Community Call, number 46. Today is Friday, the 20th of February, 2026, or February 19 if you're in America. This community call is an open voice chat discussion about Ethereum Classic. Everyone is welcome, so please be excellent to each other. The call will be published on YouTube. You can browse all past episodes at cc.etherumclassic.org, subscribe to the calendar or RSS to never miss a call. It has a handy time zone converter, and you'll be able to find AI summaries of all the calls. We'll start off with a few announcements. As you may be able to tell, we have a new call time, and going forward, community calls will be held at this new time, which is 0-200 hours UTC. This schedule better accommodates recent active participants and reduces the scheduling burden. For US participants, this means it's on Thursday evening. For Asia, it's Friday morning. In future calls, we're gonna move the green room over to Zoom, just for… ease of preparation. It simplifies setup and allows China IPs to join, as Discord is blocked there. If you haven't seen, DEFCON 8 is going to be in Mumbai, India, November 3rd to 6th, 2026. And this might be a good opportunity for us to meet in person, and maybe organize an ETC side event. So, I just wanted to put this out here now, and if any ETC people are interested in meeting up there, I'm strongly considering going to Mumbai in November, so… Let me know if you'd like to, join forces, and maybe do a presentation or something. Discord is introducing Face ID requirements soon, so I just wanted to put this on people's radar, that we might need to migrate to a different server if they're going to force us to do things we don't want to do, but… We'll see how things go. I would also like to announce that I was just informed of a new website called EthereumclassicDAO.org, which is covering the progress of the Olympia proposal, so you can follow that URL to track progress and read more about Olympia. There was also a user… in Argentum Veritas, who this week published a new app in Discord, and I mentioned I should mention it in the announcements of this call. So you can find that app at chat.inargentum, veritas.app.com. And I think… Maybe IAV is on the call right now. Are you able to speak to that IAV? Is this you? You're currently muted. Okay. I think he's still muted, but if at any point you want to jump in IAV, then please do unmute yourself. Okay, so let's start off with the pull request corner, which is just covering the pull requests that are currently open, that may need attention from maintainers. In the ECIP's repo, we've got ECIP1122. This is a new ECIP about quantum resistance, and I had a chat in the green room with the author of this, so I can… vouch that it's a real person, and it's a real PR, and I think next week he's planning to… sorry, next call, he's planning to do some more, preparation to discuss this PR. Basically, it's a proposal of how to provide quantum resistance for Ethereum Classic via ML DSA verification. We have ECIP1122, which we're gonna drill down to into this Cool. That ECIP was merged last time, so that's available on the ECIP website. We also have two open PRs from me. That were basically maintenance tasks that still need attention from maintainers, so… PR553 and 551. any maintainers, if you could get round to approving those, that would be great. If you disagree with them, please let me know. On Ethereumclassic.org repo, we have PRs about… announcing… ECIP 1120, there's an article there that was… Created. Still no response on that. There's an article about market infrastructure, these kind of… Should be merged together, I think. I've added a 1559 debate article as well, still needs merging, and we have two Olympia development series that need merging. So… I don't know how we can move forward on this, we seem to have some kind of deadlock on the… maintenance of the… org website? It's not gonna be good for anyone if we're just, like, not… helping each other out in these, and I think all of these should be published, and we shouldn't be, like, selectively… Not publishing certain things. So… I don't know how we can… as maintainers of these repos come together on some agreement, but it's not a good state to have these open PRs lasting for so long. If anyone would like to comment on that, now would be the time, or we can move on to the next Main meat of the call. I just heard. 5:54CodyAre any of them me that's blocking it? 5:59Istora MandiriI… 6:01CodyOff the top of your head, I'm looking, it could be, on some of them. I'll go through and clear them out on my side. 6:06Istora MandiriYeah, I don't think you're intentionally blocking, they just need approvals. ESIP validators. Yeah, the eSIP repo PRs, I think, a pretty… I don't know. they're touching on Olympia, so they're necessarily controversial. But… I really think putting… putting Olympia on standard track core is… is sensible. 6:49CodyYeah. Great. This one's been blocked for a while. 6:55Istora MandiriYep. Since January. So really, we need maintainers to, perhaps. It would be great if we could use these calls to… Try and organize with maintainers and come to some agreement, because it seems like Doing it fully asynchronously isn't effective. via this… via Discord, so having this opportunity to come together and have this… Communication. It would be great if other maintainers could commit to coming, Chris Masa. 7:33CodyYeah. I agree. Or we need people who are active, I guess. 7:41Istora MandiriYep, yep. That might… may require, like, rotating people, or reducing, or increasing… The number of requirements to merge stuff, but the current situation is that nothing's happening, so… This is not working. 7:55CodyIt's a great call out to anyone in the audience who, is looking for something else, another great way to contribute to the Classic, volunteering your time. 8:05Istora MandiriYep. I believe, Wiedergarden previously, suggested that he would be interested in doing that. I know that Diego is, now a maintainer. So… I think I can do a better job at trying to… Encourage people to join the course? I try and annoy people more, I guess, and remind people to join these calls, but especially for maintainers, I think it's really important to have this continual… engagement. But, yeah, let's move on to the… the main topic of the call. So, just to recap on the last call, we kind of chatted about 1121 for the first time, and… We kind of came between the two of us. to agreement that it's pretty low effort compared to, like, Olympia or 1120, and this would be a nice, easy win to achieve this year as a hard fork solution for a thin plastic. For this call, there are 3 topics to cover, or that I wanted to cover. Of course, we can cover other things. First one being ETC Nexus, which is a project that I've been working on since the last call, and have just opened sourced. So, that's available at historamandiri slash etc dash nexus. And basically, it was the Ethereum Hive testing system. That we previously mentioned on the last call. And… actually testing the ETC clients against that. So, I'm happy to announce that… Let me just pull up the… the README. There's a SIT rep and a README. In that repo? And basically, There's 62,000 tests that… Korgeth, Bessu, and Nethermind were tested against. There's a 99.9% success rate on the active clients. the… The clients that failed were some edge cases that were… the test that failed were some edge cases that I discussed with, Diego with, and… Rely on a… an ECI… sorry, an EIP to be implemented on those… on those clients that I believe will be coming in the future. Diego mentioned that this is not Concerning with regards to consensus, and is, in fact. something that was being discussed upstream as well. So these are just, like, extreme edge cases for Create 2. Collision that is extremely… well, it's basically not a problem. So, essentially, we have of… the… the two… in use, Ethereum Classic clients. full test coverage passing. So, that's the ETC Nexus that we talked about. The other benefit of this project is that it's obviously forkable, and we can use it to implement and test other ETC clients. For example, implementing 1121, And it's geared towards agentic development, so… The whole point of this repo was to have a single repo that you could run your agents in and implement changes within submoduled clients, and then run tests against them in a single place, instead of having, like, separate Repos everywhere. So… This has been my, contribution to… Ethereum Classic Client Maintenance for the first time, and it's been… Pretty interesting. We also have NetherMind, in that repo, and hopefully, maybe, Cody, you might be interested in adding Fukui to that. 12:16CodyYeah. 12:17Istora MandiriNo, it's very cool. 12:19CodyHow about me? been watching along. It's good that the… both clients are passing, so… Hope everyone sleeps at night. 12:28Istora MandiriI was a little concerned when those… Tests were failing, but with the explanation, and double-checking by… By Diego, I'm… I think we can be, fairly confident it's not a problem. So, yeah, that's ETC Nexus, and… it's kind of boring tech, but useful, and I think that's something that… was just an easy win, especially with AI, that we can now leverage for future work, and… Ensure client compatibility, and actually making it easier to do development on clients at lower cost. Right, so implementing these… Maintenance updates, or just general… Forking, testing, all that kind of stuff. It's a lot easier now. Do you think that would… 13:27CodyDo you think it'll speed up our… our, our hard fork time, then, I guess? Of, because… 13:34Istora MandiriYup. 13:34CodyAs we'll talk about soon, the 121's already in the client, so we'll be able to test. 13:39Istora MandiriExactly. 13:40CodyGood luck. 13:42Istora MandiriMy main… task before the next call will be to implement 1121. And test it against the two main clients. And ensure that that's working, at least as far as I can interpret from my AI agent, as I'm not a go or… Java engineer? But of course, once that's implemented, we can then do the… Like, the hard work of… Running the test and checking that the… code is turned on correctly, I guess, can be… can be done, and then someone that actually is a developer of… Those languages can double-check and ensure that Things are the way they should be. And then that should speed up the process. 14:39CodyAnd is that because, I guess, they haven't been the upstream from Gep hasn't been merged into the Ethereum Classic client for those? Basically, it seems like it would be… these are already, live on Ethereum, so it should just be, The configuration setting on it. 14:55Istora MandiriYep, that's basically… my understanding. I haven't dived deep into it yet, but… Yeah, that's… That's the hope, and both for Bisu, for Bessu, and for Geth, we can just flip some switches. Run the tests, and then have, like, a release candidate. 15:16CodyCool. And I guess, is the plan still, if we don't have a… Solid view on how… I forget the number off the top of my head. That's, olympia. Olympia. Moving ahead with this in March. Or starting this… starting the clock for, a hard fork. 15:38Istora MandiriYeah, yeah, I think we could even be in a position where This may be too fast, but… It could be in the position where, next call, we can, like, decide a block number. 15:56CodyYeah. 15:56Istora MandiriBut yeah, I really would like to have other maintainers. weigh in at this stage, or at least… before we decide a block number. Ideally, it's not just me and you picking a number out of the blue, and . 16:11CodyI'm a good number picker. I have some dice. But… but yeah, it… We definitely need to also get socialization and support. You're all set. 16:21Istora MandiriYep. 16:22CodyIt would require, the, I'm not doing good with names tonight. The… main project that's running all of the nodes on Ethereum Classic right now. ETCMC. No, not the API. The, ETCMC, the, client that was. 16:45Istora MandiriHmm. 16:46CodyRecently migrated from version 1 to version 2. We're in the process of it. I'm pulling up ETC, nodes.org. 16:55Istora MandiriYep. 16:56CodyRight now, there are, 349 ETCMC GET nodes. And 63 of the version 2, that are online. So, making sure that, we coordinate across them and, the major pools and, exchanges and… Especially providers that are out there. 17:19Istora MandiriYeah. I think probably before we decide a block number, we should… Ensure that we have that… Systematic… communication with all the important players, and that they are responsive, so that We know how long How much lead time they need. 17:38CodyYep. Yeah, no need to surprise anyone with it. 17:43Istora MandiriYep, yep. 17:44CodyI think the hard part's always been the coding and making sure everything was up to speed, but if this one is just the… Already implemented ones, then… that should speed up. There's no development cycle, and it's a matter of communicating and. 18:01Istora MandiriYeah. 18:01Codytesting and… 18:02Istora MandiriMake sure everyone's on board. The other thing that I should mention is that this current ETC Nexus project does not implement any, like, ETC-specific tests. It's just a subset of the Ethereum tests, so for the… Things like the fixed supply and, Thanos, etc, will need to be… I'll try and… Get the AI agent to implement some tests. And… Hopefully, that will improve the… the quality of the test suite we have for ETC. And hopefully the transcription of this call will… Create some… Actionable items at the end. Okay, the other thing that I wanted to mention on this call was the… there was some more feedback on Olympia from a community member. in that, in the thread. In the discussion thread? Currently, no reply, and I'm not sure if Chris Mercer is active on that thread, as I also had some questions that have remained unanswered. So… I'm hoping that the… The maintainers might be able to, like, address some of these… But, in summary. Let's see… So the… this, guy kind of came out of the blue, Ro… Romaine? Blatch here, an ETC miner. and institutional communications professional, based in France, made a post. Basically agreeing with my five questions, meaning responding to, and raised concerns about early governance dominance by large holders. minor representation And… The communication gap left by the co-op's reduced capacity. And… should minor interests be represented in the government's bootstrap? And what anti-civil and fair distribution mechanisms addresses these concerns. So… I just wanted to mention that as an update from the community about Olympia. And hopefully we can… Continue the discussion somehow. But given the nature of the The debate between… having a treasury or not having a treasury in the future, it seems like it makes the most sense for us to focus right now on 1121. So… Yeah. 21:06CodyI'm reading through the comments, too. Yes. Has the Ethereum cooperatives, collapsed, affected anything? I guess that's… The podcast still runs, the Discord's still alive. The challenge will be whenever we have to start socializing for the hard fork, I think. 21:48Istora MandiriRight. That's something we could… try and figure out during this call. I know that… In previous hard for walks. There's been, like, a dedicated communications person. I know previously AFRI was helping with that. I'm not sure… Who was helping with the last Hard fork, and whether or not that person can either do it again, or help with formalizing. A process that we could follow to reach out to all the relevant players? 22:25CodyBecause, basically. 22:26Istora MandiriI… I don't think this is documented much. And we'd be starting from scratch, or at least I would, so… 22:33CodyWell, I would assume that it would be, Diego would have that list still, from the co-op. He's still… The sole developer there. 22:43Istora MandiriCool. 22:44CodyAnd we could leverage the ETC, DAO RETC grant style. 22:50Istora MandiriRight. 22:51CodyFor custody providers in exchange, I work with a lot of them. pretty often, so I have… I have a lot of contacts across those that we could leverage. For getting coordinated in, their ecosystem partners. 23:10Istora MandiriAwesome. Do you think it would make sense to create, like, a… a fork. coordination repo in the main org, so that we can sort of formalize and create a a reference point. 23:24CodyYeah, that way everyone can have a single point to go to to… 23:28Istora MandiriYep, and we can use it for discussion, and just making sure everyone's on board. 23:36Codysense. 23:39Istora MandiriCool. And how… do you have any ideas in mind about… How much lead time? Do you think we should give for… Gathering consensus over the… The contents of the fork? like, personally, It seems pretty non-controversial, so I don't think it should take as long as others. And then… Typically, how long is given in previous hard forks as a reference point for the Client update. Versus the block activation number. And giving enough time to push that out, and ensuring everyone's updated. And there's a… is there any need to, or way for us to ensure that All the clients are up-to-date. before. the… The hard fork actually… is activated. 24:50Codythe last couple times, from what I remember, it was around 6 months from the time a block was decided, implementation and testing and, go live on The testnet was 3 to 4 months. Or by the time the block was already decided, it was… Already in the clients, it was already pushed, ready to go in the testnets, and then… After it was validated there, then it would go to the mainnet. 25:23Istora MandiriSo, it's… 25:24CodyIt… Was about a 6-month period of… A lot of it's the coordination, making sure that all the clients are their, In the repo, there is… Either in ours or in the ETC, dev one. The, the fork monitor software, for dashboards, and… So all of that's still in place. That's… I believe part of ETC nodes as well. So we can see which nodes are on which versions and, what forks they are able to… Or what they think is the next forked version. 26:00Istora MandiriOkay. 26:00CodySo, it's all… very monitorable. 26:07Istora MandiriAwesome. Is that live at the moment? 26:14CodyYeah, et ccnodes.org. It shows you this. This is run by, the co-op. And so it shows all of the nodes that are online, or that are… tagged up with the boot nodes in the last, couple minutes, at least. And so it keeps track of everyone there. 26:38Istora MandiriETCMC. Is it, is like… yeah. Huge. And, what's the strategy, then, for… Activation. Let's say there's, like, a new version. We set a block number for activation. But not that many clients have updated. What happens? 27:07Codythen it just wouldn't happen. The nodes that did upgrade would upgrade, and Become their own chain, and the other network would continue on without ever knowing the other one existed. So it would be a… 27:22Istora MandiriThat would be… that would be the case for minors, but… in terms of… clients themselves. They're just gonna… drop off. from… The actually mined chain, right? 27:36CodyYeah, the ones that have the new node upgrade wouldn't be able to see the other ones. Part of the network discovery is trading which forks you know, and which, or what the hashes of them are, so they would say whatever the new fork block is, and the other ones would just say, okay, that's. 27:54Istora MandiriNot my block, so… 27:57CodyThey'd just continue on, as if it was a different chain altogether. 28:01Istora MandiriRight, so the key, I guess. Group to ensure that's on board is the… the mining pools, right? 28:10CodyYeah, the mining pools, for sure. But, node providers, I mean, service providers as well, like, the APIs, We need to make sure that their nodes are on the right one, as well. So, Rivet and, all of those that are… maintain. Wallet providers, a lot of them run their own. Quicknode runs, APIs for people. Impura has one. 28:41Istora MandiriYep. 28:42CodyOne of the, I guess, benefits and bad things about being a chain that's been around so long is we're Everywhere, lots of people use it, and… 28:50Istora MandiriRight. Deeply embedded. 28:51CodyDoesn't change very often. 28:53Istora MandiriYeah. But it'd be good to, kind of. I don't know how to describe it. Like, rev up the engine once in a while, so it doesn't get completely… Ossified. 29:06CodyNo, that's… That's why I'm a big fan of If… even if we don't do the, the base fee, gas mechanics this time, getting something in the pipeline just to show that we can still do it. Everyone's still paying attention that they're plastic, and it's running the… all the latest still. 29:24Istora MandiriYes. Cool. Yeah, I think this is something we should all… Council Prima on, and I hope we can… 29:33CodyThe mainnet Ethereum itself is actually moving to a much more aggressive cycle, too. From what I remember, they were looking at every 6 months. Having a fork. 29:44Istora MandiriI kind of see it as, like, the different Linux distros. Right, where you have the Ubuntu. Once in a while. And then you have the bleeding edge. And Fedora upstream. Debian. So maybe, ethereum really is the testnet. incentivized testnet. 30:08CodyYeah, incentivized testing. 30:16Istora MandiriSo I think we have some things to work on for the next… Cool, and getting… largely… Laying the groundwork for hard-forward coordination. Would be the theme, I think. 30:33CodyYeah, and… Going through the EIPs, have you seen any that stand out as, Strange, or, something that wouldn't be directly beneficial to us. 30:56Istora MandiriI'm just scanning them again now. 31:00CodyThere was one, I remember, that was… I'll find out in a second. 31:07Istora MandiriI think the new smart contract features, generally, I can't see them… having any incompatibility with ETC? On a protocol layer. They're all pretty much positive. 31:28CodyThe one that… Was… might be concerning, or that… Diego would probably want to look at is EIP7642 that removes the… History serving window or changes it? 31:47Istora MandiriRemoves legacy bloom filter from receipts and defines a history serving window. Okay. 31:54CodyYeah, and where this was concerning, from what I remember reading through it, was, it removed the difficulty or one of the fields that we've… Potentially still use as a proof-of-work chain. 32:08Istora MandiriI see. Yeah, an abstract. 32:12CodyThe EIP modifies the peer-to-peer protocol to announce the historical block range served by the node. It also simplifies the handshake To remove the total difficulty information, which isn't. 32:23Istora Mandiriexcuse me. 32:24Codyor after the merge. And since we're a proof of work, we actually do use total difficulty as a key mechanic. 32:33Istora MandiriSo we need to… Research more into this. EIP. And either we drop it, or we can… Modify it. And what's the main advantage of this? Just reducing bloat. 32:57CodyYeah, I think so. 32:58Istora MandiriOkay. So it's a non-essential thing. It could be just… Deferred to a later… a later… . 33:20CodyPotentially. Yeah, it would… we need to look into it deeper, I guess, because, right now our… our nodes do, the F68 messages. And so, In the network protocol, whenever the nodes are through their handshake, if they defer to whatever the lower number is. So, if ours are 68, and they would just stay 68, I guess the majority of them would. But… So yeah, I don't… I don't know if we need this one at all. If it's part of the F69… Message format. We could just stay 68, and… that we'd still have SNAP, we'd still have, everything that we have today. We just have the… we wouldn't use the new Message format, or history window, so… something really worthwhile, I guess. 34:24Istora MandiriRight. And to end users, this has no effect on… It's really just, like, under the hood changes, optimization. 34:34CodyYeah. 34:37Istora MandiriOkay. My instinct is that it's better to just defer it if we can, such that we can… Focus on, like, a zero effort. Fork, or a low-effort fork. 34:51CodyI agree. 34:56Istora MandiriCool. We already have a bunch of deferred EIPs relate to blobs. 35:06CodyYeah, so I… we can probably push that one, or… Unless… Look at it, make sure. 35:13Istora MandiriYeah, maybe… maybe Diego has a sense for whether or not it would be… worth… Attempting to include it with some modification? If it's an easy one, but… My instinct is just to defer. 35:35CodyYep. Shall we go from the top, then, on the new smart contract feature ones? Or. 35:50Istora MandiriOkay. 35:53CodyShall I just… shall I just read the… 35:56Istora MandiriDescription, and if you have any comments, You can jump in? 36:01CodySure. Okay. I can try to give color to it. 36:04Istora MandiriCool. So we have some, In the upcoming ECIP 1121, this will be turning on some features that exist in upstream Ethereum right now, and they should just be easy to switch on. In batches of three, starting with new smart contract features, we have EIP1153, which is a temporary scratch space for smart contracts that reset after each transaction, enabling cheaper DeFi operations. 36:36Codyyou want me to go now and… 36:41Istora MandiriNot sure, right? I mean, if you… Shall I just… I'll read out all the smart contract features, and then if there's anything that you can… Yeah, alright. So, we also have… EIP5656, new instruction for copying data within memory more efficiently, reducing gas costs. We have 6780, disabling the ability for contracts to delete themselves, removing long-standing security footgun. 7702… Letting regular wallets, externally owned accounts, behave like smart contracts, unlocking features like transaction batching and gas sponsorship. That sounds very… Very, useful. Eip2537 adds fast built-in cryptography for ZK zero-knowledge proofs, and BLS signatures, enabling privacy and advanced verification on-chain. 7951, adding built-in support for the cryptography used by phones and hardware keys, enabling passkey-based wallets. Also sounds pretty cool. Cody? 37:51CodyAll super useful things. So… The first two are… I guess the least sexy of all of them. But it's… it's necessary, it makes… it easier for developers who are trying to build on the, Ethereum Classic to actually do things. So 11, or 1153, the temporary space, is, whenever you submit a transaction to the EVM, It's, you're running a computer program inside of the transaction, so what you put into it If it calls multiple contracts or does multiple operations, it has to keep memory of… whatever the temporary variables are as it does its operations. And so right now, the way that that happens is it uses… it loads it into memory, and this, costs some amount of gas, and so it's… It's inefficient, from… a development point of view to use a lot of memory, or do a lot of memory operations, that are just going to be done away with at the end of the transaction anyway. So this scratch pad, changes the pricing dynamic around that, so that It allows… The execution in just a temporary memory space that is thrown away at the end of the transaction, so there doesn't need to be kept a long-term record of every intermediate step. So it's, it's useful, it's, It makes it cheaper to do a lot of the… Things, In the future, as far as swaps or, loans or anything like that on-chain. It's… so it's… It's kind of… Builds for the future, but it's not something that anyone would really get excited about. I've been talking about it in a bar. 39:45Istora MandiriIs this a… is this transparent process for contract developers, or is it something they, like, explicitly opt into? 39:53CodyIt's, it would be transparent to them, it's not something that… That you would know, because this is at the opcode level. It's… Depends on, I guess, the syntax and solidity of how it's implemented with the new versions. But it's… it's not something that they would… Anyone's gonna go deep down and be… Programming one opcode versus the other one. 40:20Istora MandiriOkay. 40:25CodyAnd, the… 5656. is, a similar thing. It's working with memory, so this is, changes the… some pricing dynamics inside of it, if I remember correctly. I'm trying to pull up my notes on… on this one. 40:51Istora MandiriYeah, it's a repricing of… 40:55CodyCopying bike codes. Inside of, the EVM. So it's, changes the gas dynamics as… on contracts, or as you make operation calls, so it's… not consensus-related, but it's more about EVM operations and getting in line with the best practices of the… Latest. 6780, this is, probably the third in a series of, EIPs that have been trying to get rid of the, self-destruct feature in contracts? So whenever you deploy a smart contract to a blockchain, it lives there forever, and it does have a feature that you can call that, lets you clean it up, so… all the nodes will know to remove it from the memory, and it won't be used anymore. Any calls you send to it will be, just removed. So, it is a good idea. It's only hurt people in the real world of, the biggest incident that happened was the Polkadot wallet, where someone, Self-destructed the, the actual library that they were using, so, the… This one… prevents that kind of thing from happening, so you wouldn't be able to call self-destruct on a wallet, or any… a contract that's already been deployed. You could only call self-destruct, while you're creating a contract. which… sounds like a weird thing to do, but if you're doing DeFi things like creating flash loans or things like that, you can deploy a contract and destroy it all in the same transaction, and it… It's… works efficiently that way. So, it is something that needs to be done, but it's not something that, anyone needs to care about, long-term storage-wise, because that was, I guess, the real reason for implementing in the first place. If you run an archive node that keeps the state of all contracts and, that eventually grows to the size, exponentially as the chain gets longer and longer, so… If that was the use case, then clearing out contracts eventually Would be a good thing, or the polite thing to do as a developer, but that's… never been a problem so far. Nodes have, do pruning, and they do other things to make their state more efficient, so having contracts Unused contracts don't really take up space. It's a hash in a tree that just isn't cold. 43:50Istora MandiriC. 43:51CodySo, there have been other workarounds on the node area that, so… I say that to say that this is kind of the slowly decommissioning of that process of, They were… Upstream was just gonna do away with the self-destruct altogether, but this way, it keeps some of the functionality around with it. And that's the security footgun note, also, is the polka dot one. 44:19Istora MandiriRight. 44:21Cody7702 is kind of an interesting one. It's, every account in, if you think of the Ethereum, state, like, the snapshot of it is like a spreadsheet. There's 4 or 5 columns in it. It has, like, the nonce, the, public key, the… balance of ETC and an empty block where it can store, some kind of state if it's a smart contract, or if it's a… Just an account that you created yourself as a wallet, then there's no state there? It's just always been empty, and so what… 7702 lets you do, as someone who owns a private key or a public key, is you can, deploy, You can deploy something to that state and make use of it. So, if you want your wallet to act as a smart contract, or if when someone sends you funds, you want it to do XYZ like a smart contract would? This lets you do that without having to do the… Wonky, normal contract deployment of Of how they derive their addresses. This lets you turn your address into a… the magic smart contract automatically. 45:34Istora MandiriHmm. So… Okay, that's interesting. How… How do you… sort of… Decide the state of your contract. 45:52CodyYou mean the… for your address, what you deploy there? 45:55Istora MandiriYeah. 46:01CodyIt's a… complicated process. Can it become an arbitrary contract that just has the ability to initiate transactions? 46:12Istora MandiriIs that what? Is that what's done? Yes. 46:13CodyYeah, so you deploy it the same way as you would a contract. So there's a… there's a process, there's a format to it as you… when you send it to the chain, but it's the same… same concept of it works exactly like a contract would. 46:26Istora MandiriCool. And what's the idea of gas sponsorship? Is that like a gasless transaction, where you don't have to pay for the fee yourself? 46:37CodyYeah, it's where account X pays for transaction on behalf of another account. So this… So if you had an ERC20, yeah. 46:46Istora MandiriGo ahead. 46:48CodyYep, I was gonna say, for… the classic problem that everyone has with stablecoins right now is that if someone sends you a US dollar coin to your wallet, and you've never used your wallet before, that coin's essentially stuck there until you get some Ethereum or Ethereum Classic, because to send a transaction, you need something in your account. You have to pay for gas. And so, this would, allow for, If you deployed this, you could do… your ERCs could, pay for somebody else's gas. So if you were a Fidelity that just launched their stablecoin, or USDC, or Braille on Ethereum Plastic, they could Set it up where it's a gasless payment if you're using their coin, so you don't have to worry if, Your customer, or whoever you're sending it to can't ever move the dollar again, because their contract could always pay for it. 47:45Istora MandiriCool. That's super useful, and… Really… beneficial for onboarding. as well. 47:57CodyYep. And, the 2537 is… the, Bls12381 curves. Which are, this one and the other one you mentioned, 7951, are precompiles. So there are certain functions that we know cost more than they should, or more than, people would want to pay for transactions, because… and they're normal operations that we do all the time. The core ones that originally shipped with Ethereum were around the hash functions that you have to use for everything. So it's… it would be really expensive to implement that in, every contract. So, the first… 0x0012345 are all set aside for pre-compiles, because… Would be nearly impossible for anyone to… Get those private keys or public addresses. Either way. So those are… considered safe places to put these, smart contracts, or pre-compiled contracts. And so, whenever a contract or a transaction uses one of these, the execution clients know to just run the code, and charge a set fee. the BLS12381. as… implements the curves that are used on the latest versions of, SNARCs, and lets us do things like, point addition and, multiplication. So… A long time ago, there was a project called Zoe, it was Zcash on Ethereum. And… A lot of the precompiles for, Blake 2 and, the BLS Curbs that are in now were… From that project, and so… If you wanted to, and, you could implement the, the Blake2 lets you, validate the proof of, the Zcash chain, so their proof of work uses, Blake 2, so you can validate it the same way that you would, any other… Proof of work. And then the curves, the first set were for the Sprout, zero-knowledge. system. And so… this latest, the BLS curves, are the latest version that, SNARCs are using, where Halo 2 and the Orchard, pool on Zcash are all built around these curves, and they're more efficient, and recursive, so you could, in theory, do a lot more efficient, roll-ups If you were… doing a Layer 2. Or you can, implement really cool privacy-preserving stuff, as well, with these, so… There's not a, I guess, real trade-off. It is a pre-compile, so all the clients would need to implement it. If they hadn't implemented it already. Or know how to process it when they get these, codes called in. Other than that, it's… No impact to normal users. 51:25Istora MandiriAnd Bisu and Geth already have this. 51:30CodyYes. 51:31Istora MandiriCool. And this is, use cases, including Layer 2, as well as the, like, zero-knowledge circuits. Is that correct? 51:43CodyThat's correct. Proving the… 51:46Istora MandiriYeah, creating the proofs for the Layer 2s, or validating the proofs for the Layer 2. 51:50CodyAnd, and being able to do it cheaply on the Layer 1, is… always the goal, I guess. Because Layer 2s are nice, they do help with scaling, but if you can do it on Layer 1 that… Brings the value back to the main chain. So, makes it a lot better for interoperability and things like that as well. 52:13Istora MandiriCool. 52:17CodyAnd the last one, 7951, as… Cool one as well. It's another precompile, so this is for the… SECP256R1. Which is the… the other flavor of the SECP256, curve. So K1 is, one that's… used, and the R1 is the NIST standard curve, so this is What's, whenever you do the pass keys on your phone now, or, web authentic… 52:55Istora MandiriHmm. 52:55CodyIt's a lot of places for, authentication and, So what this would allow is, smart contracts would be able to use this opcode and, Use it for, validating signatures. I know the, Coinbases account abstraction, uses signatures and signature validation, and so this would allow, things like people to use their passkey instead of having to do an actual, externally owned account. You wouldn't have to… do the… public-private key pair, you could allow… you could write a smart contract that could just use these authorizations instead. For the transactions, for instance. 53:44Istora MandiriInteresting. In that system, would there be an address associated with it, or is it just some kind of meta… Custom… Yeah. Yeah. 53:54CodyYeah, there is, it's… there's still public keys, private keys, and so this is, just another option that you could use for account. You could do this today, I guess. With the… the current, algorithm that we use for signatures. You could, write your smart contract to validate the signature, and, And the way that they do it with the counter structure is they have a paymaster that everyone sends all these signed transactions to. And then the Paymaster's the one that submits it on-chain and pays the gas fee. But it's one batch transaction, and all the signatures that come in at once can get validated. And so it works the same way with this. You would just All the transactions that happen off-chain get signed with, The algorithm, and then whenever they get pushed on-chain in a batch. Whoever's putting it on-chain pays for the gas, and it covers all of the transaction fees. And so this just allows for another method of doing that as well. 54:58Istora MandiriVery cool. 55:00CodyIt's, I guess an alternative to this, if we didn't want to do a precompile, would be to add it at the base layer, and have another type of public-private key pair, and somehow parse through the transactions as they came in. That would be a huge engineering undertaking, though, so this kind of… Gives you that, benefit for free, and keeps the same mechanics. 55:23Istora MandiriRight, and this is… Standard upstream. 55:30CodyYeah, well, it's new now, and everyone hasn't got excited about it yet, because everyone's kind of bummed about the whole crypto winter coming back. 55:39Istora MandiriOkay. But it's, it's… 55:41CodyUnless they realize that it's there. 55:43Istora MandiriIs it merged? 55:45CodyIt is. This was part of the, Osaka? I think is what it was called. Okay. Their latest, their latest fork. So this is live now, and there are, projects that are taking advantage of it, but You said it's… Hasn't hit the way that it should yet. 56:05Istora MandiriOnce it catches on and people realize that it'll be really big. Yeah. Passkeys themselves are starting to gain traction as well, so it's great timing. 56:15CodyYeah. That's… I think everything has a pesky now, it feels like, so… It's, it gets the users used to the, the dynamic. If they know that that's secure, they know that that's what they do when they want to secure stuff, and… It'd be really hard to ever steal my phone from me. 56:35Istora MandiriAnd it's actually, like, a superior user experience, whilst also being more secure. 56:41CodyYeah, definitely. There's no… nothing to forget. 56:49Istora MandiriOkay, Do you have time to go through the rest? Or we can defer the other sections to the next call if you don't? 57:00CodyYeah, well, when's the next call? Is it a month from now, or two weeks from now, or one week from now? I guess I should have… Also, I have an extra front of me. 57:09Istora MandiriYeah, I'm not sure yet. Let me… let me quickly check my calendar. I was hoping to increase the cadence of these calls, so… Maybe we can do it. Sooner. Let's see… Friday, next Friday, is… Not possible for me. So maybe we can… Do… 2 weeks? At least for the next call. So, I'll aim… I'll aim to have that announced on the 6th. Of March, Friday 6th. 57:44CodyOkay, yeah, that sounds good. I'll consolidate my thoughts better next time. Endall. 57:50Istora MandiriAwesome. So, I'll add that to a… an action item for the next call, and we can finish going through those EIPs in preparation for the… 1121, hard fork. Whatever that becomes known as. 58:09CodySounds good. 58:11Istora MandiriAwesome. Thanks again, Cody, for joining the call. Always good to catch up and keep this, this heartbeat going. 58:23CodyYeah, definitely. Pleasure. Thank you for hosting, and… And keeping this going. 58:29Istora MandiriMy pleasure. So, let's wrap up now, and say goodbye to all those listening on YouTube, thanks for joining us, and see you again in two weeks for ETC Community Call number 47. Thanks, everyone, for joining. Take care. Bye-bye.

Focusing on ECIP-1121

Key Points Discussed

Preamble

Announcements

New Call Time

Green Room Moving to Zoom

Devcon 8 Mumbai

Discord Face ID Requirement

ethereumclassicdao.org

InArgentumVeritas: Web3 Chat & Poker App

Pull Request Corner

ECIPs

ethereumclassic.org

Last Call Recap

Let’s Dive In

Olympia Community Feedback

ETC Nexus Testing Project

Main Topic: ECIP-1121 Deep Dive & Next Steps

New Smart Contract Features

Network Safety & Limits

Infrastructure & Tooling

Next Steps

Other Discussion

References

AI Summary

Discussed topics

ETC Nexus Project

ECIP 1121 Implementation

New Smart Contract Features in ECIP 1121

Community Call Schedule

Pull Request Status

Olympia Proposal Update

DevCon 8 Announcement

Action items

Full Transcript