Ethereum Classic Community Call #60
Decentralism
Key Points Discussed
- An extra call in the fortnightly cycle. The next call is in two weeks, with a special call to be announced.
- Green-room topic carried over: the Clarity Act was blocked in the US Senate. Lunar argued news follows price, Kevin noted its DeFi developer protections, and Istora read out that it would have classified Bitcoin and Ethereum, and presumably ETC, as commodities.
- Tron’s USDT dominance in emerging markets led to a discussion of ETC as a neutral EVM bridge and a proof-of-work backstop for proof-of-stake chains facing quantum migration. Lunar called the quantum threat a boogeyman; codeaholic pointed to the money and AI progress behind it.
- codeaholic presented early gas results for the ML-DSA precompile: about a 26 percent gas premium with reasonable batching, 100 to 200 percent unbatched, amounting to cents per transaction, all opt-in. Multi-machine tests and a Mordor plan are next.
- Istora asked how the precompile’s gas price should be calibrated to the real validation work on target hardware such as a Raspberry Pi. codeaholic has a benchmark and will run it.
- The rogue core-geth release: a dormant
ethereumclassic/core-gethfork gained about 200 commits over a weekend and shipped a “security fix” that patched nothing exploitable but added MESS and changed the boot nodes, pushed to mining pools from an official-looking address. One pool switched for a few hours and switched back. Istora recommendsetclabscore/core-gethv1.12.23 Argos. - Kevin asked for confirmation that the Argos release has the CVEs patched. Istora said all cited CVEs are patched, one is not applicable to ETC, and the rogue release adds regressions. Lunar offered to look at a full audit of core-geth.
- The group discussed the ethereumclassic org admins, Istora’s ban from the Olympia Discord, and Kevin noted the rogue README tells operators core-geth is sunsetting when Classix has pledged to maintain it, with ETC Grants DAO backing.
- codeaholic closed with the question of what decentralization means for ETC’s process, not only its technology. Lunar argued any formal process is the start of a government; Istora pointed to the ECIP process, miners as the final check, and the Why Classic Decentralism article.
Full AI Summary and Transcript ↓
Introductions
Quick round of introductions for everyone on the call, and if there’s anything you want to talk about.
Agenda
This was an extra call with no set agenda. The topics came from the green room discussion: the blocked Clarity Act and crypto markets, Tron, proof of work and the quantum threat, early gas results for the ML-DSA precompile, the rogue core-geth release, and decentralization.
AI Summary
Call 60 was an unscheduled extra call with no set agenda, so the topics came from the green room. Istora, Lunar, codeaholic, and Kevin started with the blocked Clarity Act and the state of crypto markets, drifted through Tron’s stablecoin dominance into the case for proof of work under a quantum threat, and then heard codeaholic’s first gas measurements for the ML-DSA precompile. The second half turned to the rogue core-geth release pushed from the ethereumclassic org over the weekend, what it did and did not fix, and what it means for the org’s admins. The call closed with a long exchange on what decentralization should mean for ETC’s process.
Welcome and Introductions
Istora explained the extra call and welcomed the regulars.
- Details
- Istora: This is an extra call. The schedule is being adjusted so the next call is again in two weeks, with a special call to be announced
- Lunar, codeaholic, and Kevin introduced themselves. Kevin counted it as his second call; Istora reminded him it is the sixtieth
- Lady Rose joined as a listener and said hello in the chat
- Istora: Listeners on YouTube can join the green room an hour before each scheduled call
- Conclusion
- No agenda this week, so the green room topics set the order
Clarity Act, Markets and Tron
The group picked up the macro conversation from the green room.
- Details
- Lunar: Most market news is post hoc. Price moves first and people find a news event to explain it afterwards
- Kevin: Tokens pumped ahead of the Clarity Act vote, dropped when cloture failed, and Uniswap and Zcash were up again days later, possibly on the CFTC and SEC saying they will proceed with regulation regardless
- Kevin: The bill covered stablecoins, token issuance, and exchange registration, with bank pushback over stablecoin yield. It would also have classified writing code, running nodes, and validating transactions as non-regulated activity, protecting DeFi developers and projects like ETCswap
- Istora: Read a summary. The act would split jurisdiction between the SEC and CFTC and classify Bitcoin and Ethereum, and presumably ETC, as commodities. It was blocked partly over conflict-of-interest concerns around Donald Trump’s crypto ventures
- Istora: Staying truly decentralized is what keeps a layer one a commodity rather than a security
- Lunar: Fiat currencies are slowly abolishing themselves. A pro-Bitcoin politician’s first move is to weaken the dollar, and other countries will follow El Salvador
- Istora: Possible stimulus cheques could repeat the COVID-era pattern of retail buying crypto
- The conversation moved to Tron, which carries most USDT use in Asia and South America. Lunar saw it used everywhere in Dubai. Istora called it an Ethereum copycat with TRC-20 in place of ERC-20, and Kevin recalled its 2017 plagiarism accusations
- Lunar: Justin Sun could probably shut Tron down if he wanted but never would. Istora asked whether he could be coerced, and doubted Tron is very decentralized
- Conclusion
- Would clearer commodity classification help ETC, and does Tron’s traction point to a role for ETC as a neutral EVM bridge?
Proof of Work and the Quantum Threat
Istora pivoted from Tron to the argument for proof of work.
- Details
- Istora: ETC could bridge between EVM chains and act as a proof-of-work backstop for proof-of-stake chains, whose quantum migration may be orders of magnitude harder, a point also made on the Bitmain panel
- Lunar: If quantum is the best argument for proof of work, pack your bags. The real argument is that the other chains will slowly be revealed as fraud. Quantum computers have still not factored 35
- Istora: Narratives matter, and many people who believe in the threat are on proof-of-stake chains, so it can still bring users to ETC
- codeaholic: The US Department of Energy is putting large prize money into quantum computing, and AI is accelerating research, so it is a real thing to prepare for before a breach, which would be far harder to fix afterwards
- codeaholic: Last session’s qubit and Toffoli gate counts show it is not immediate, and nobody needs to panic like Y2K, but anyone building for the long term should think about it now
- Istora: Y2K was fixed precisely because people worked on it in time, which is the outcome to aim for. Recursive self-improvement in AI could compress the timeline
- Istora, answering Kevin: The risk is not to hashing but to signatures. Any address that has transacted has exposed its public key, so old Satoshi coins are a bigger problem for Bitcoin. Proof-of-stake chains rely on quantum-insecure signatures for consensus itself and need larger signatures, whereas proof of work just hashes and draws security from energy outside the system
- Kevin asked which is the bigger threat. Istora: Quantum for ETC, recursive self-improvement for humanity. Lunar: AI safety advocates who want a world government to ban models are a bigger threat than either
- Conclusion
- Should ETC lean on the proof-of-work quantum narrative, or is that a distraction from its core case?
ML-DSA Precompile: Early Gas Results
codeaholic shared his screen with preliminary findings posted on the pull request.
- Details
- codeaholic: He is testing the ML-DSA precompile against a production smart contract whose users care about their data structures for a very long time, so unauthorized writes must be prevented
- codeaholic: On a three-node local setup, batched transactions showed about a 26 percent gas premium, unbatched 100 to 200 percent, which works out to cents per transaction at the current ETC price. Millions of events were generated across both contract versions, with the largest run taking almost 11 hours plus auditing
- codeaholic: It is opt-in. A contract only pays if it implements the precompile check, and the integration is a small code delta. Next are multi-machine, multi-node runs, a Mordor deployment plan, published artifacts so others can replicate, and a proposed community standard for testing pull requests like this
- Istora: Asked how the precompile’s gas cost is determined relative to other opcodes. Imagine a block full of these verifications on target hardware such as a Raspberry Pi. If validation takes longer than a block, the chain has a problem, so the price must be calibrated to the real work
- codeaholic: His tests measured the gas the calls consumed rather than setting a price. He clarified the verification lives in the client via Cloudflare’s CIRCL library rather than in Solidity, unlike the large pure-Solidity implementation Istora had linked previously, and he will confirm where execution happens
- codeaholic, returning later: The current base cost is a small adjustment by input length. He has a benchmark and will run it for next time
- Conclusion
- The precompile’s gas price still needs benchmarking against validation cost on target hardware before it can be set
The Rogue core-geth Release
Istora explained the weekend’s incident for listeners.
- Details
- Istora: A dormant
ethereumclassic/core-gethrepository, sharing its name with theetclabscore/core-geththat nearly all nodes run, suddenly gained a burst of commits and a release. It was pushed on social channels and to mining pools from an official-looking email as a critical security update - Istora: It fixed none of the cited security problems. It changed the root DNS and boot nodes and enabled MESS, which changes how nodes reach consensus. One mining pool switched for a few hours and switched back after the core-geth maintainer contacted them
- Istora: Had pools split across consensus rules, ETC risked a permanent chain split and double spends. The full incident report is on classix.dev. The repository also carried a donation address. Forking is fine when people are informed; presenting something as what it is not is the problem, and the org admins are responsible for the namespace
- codeaholic: Realized his quantum hardening pull request had been opened against that repository in January and asked which is the right one
- Istora: Recommends
etclabscore/core-geth. The three org admins are Elaine, Miko, and Cody. Cody co-authored Olympia, says he is neutral, and also opened the website pull request to point at the new repository - Istora: Nothing in ETC is official. bitcoin.org and ethereumclassic.org both carry that disclaimer. Using the official-looking org name is what makes this deceptive
- Lunar: Deception is self-defeating. One person was tricked for an hour, so there is no need to call it an attack, just explain it openly
- Istora: A dormant
- Conclusion
- Is this an attack or a failed fork, and who is responsible for the ethereumclassic namespace?
CVE Claims and Auditing core-geth
Kevin asked for the security facts on the record.
- Details
- Kevin: Their main contested claim is that the CVEs are not patched. Can the call confirm v1.12.23 is safe to run?
- Istora: Based on the maintainer and his own review of both diffs with agentic tooling, all the claims are incorrect. The CVEs were patched. CVE-2026-22868 concerns blob transactions, which ETC does not have. The GraphQL issue was neither a CVE nor critical. The rogue release fixes nothing exploitable in Argos and introduces regressions he will not detail publicly
- Istora: Calling a release a security fix that fixes nothing but changes consensus and boot nodes is not transparent. codeaholic agreed it is a smell if true and will review the code
- Lunar: Regardless, someone should do a full audit of core-geth. Istora: The repository is under continuous security scanning, including with frontier models, and a full audit would be welcome. Lunar may take it on
- Istora: The wider question is whether one person with no client history should vibe code 200 commits in a weekend and push it to node operators as a security update. That undermines the website pull request’s own argument, which is why he closed it
- Istora: About 530 nodes in total. Fewer than 1 percent run the rogue fork, and those are three boot nodes, three fresh nodes, and three hobbyist nodes. No large pool has switched. Anyone on 1.13 from
ethereumclassic/core-gethshould switch back
- Conclusion
- The Argos release is the recommended client. Does core-geth need a full independent audit?
Forks, Funding and the Org Admins
The discussion widened to what happens next.
- Details
- codeaholic: Hopes to synthesize the best of Olympia and other ideas and build together. He will review the report and the code, talk with Cody, and suggested a GitHub issue to summarize the facts
- Istora: Reports take more effort than creating the problem. He has contacted the admins, only Cody is active, and he is banned from the Olympia Discord without explanation, though DMs with Cody continue
- Lunar: If they want their own chain, that is their prerogative. Losing the ethereumclassic name would not be the first time the name was lost. This will be a minority fork of two or three people
- Lunar: Their argument is that developers need funding, and they are mimicking what Ethereum did to ETC, but the ideology is wrong and the community is now clearer on it
- Istora: Agrees developers should be funded. The question is how, and forking to tax miners into a DAO and an LLC controlled by the proposal’s authors is not decentralized
- Kevin: The rogue README says core-geth is sunsetting and directs operators to Fukuii, the Mantis fork, which is untrue since Classix has pledged to maintain core-geth
- Istora: Cody cannot stay neutral when resources he administers are used this way. Now is a good off-ramp to move on from the drama and build again. Funding for core-geth is secured through ETC Grants DAO, as confirmed on the last call
- Lunar: The group is spending too much time on this, though it is the only drama happening
- Conclusion
- Should the org admins act on the ethereumclassic/core-geth repository, and can both sides still build on one chain?
What Does Decentralization Mean for ETC?
codeaholic left a question that became the closing discussion.
- Details
- codeaholic: A recurring theme is what decentralization means for ETC beyond the technology. Can a decentralized technology have a process that is also decentralized and protects itself, given that there is only one Istora and one codeaholic?
- Lunar: As soon as there is a process, a government is forming. No processes, no official anything, no rules beyond the code. These calls should stay a fan club, and developers or large investors could each become a government
- codeaholic: Decentralization is not against process. Solar panels are decentralized and governments like them. A system growing in complexity needs brains and a space to manage it
- Lunar: The moment something is formalized it starts to die
- Istora: The closest thing to a formal system is the ECIP process, and even that is a suggestion. Miners decide what to run, and the balance between miners, developers, and philosophers makes ETC conservative by default. EVM compatibility upgrades pass because nobody sees them as breaking code is law
- Istora: Recommended the Why Classic Decentralism article he co-wrote with Donald. No foundation or leadership is a strength. Anything that crowns a group to distribute funds tends toward centralization and makes the chain capturable by sovereign actors, which is the objection to Olympia
- codeaholic: Miners cannot run just anything; blocks still have to fit the shape the network accepts, which is itself a limit on the Wild West
- Conclusion
- Can ETC keep its process as informal as its technology is decentralized? The discussion will continue
Wrap-up and Scheduling
- Details
- codeaholic: The 0200 UTC slot works for him. Lunar would prefer one or two hours earlier
- Istora: The call may eventually run weekly with rotating time slots. The next call in two weeks may move because he will be in Europe, unless someone else hosts
- Istora: Participation is growing, and thanked everyone
- Conclusion
- Next call in two weeks, time to be confirmed
Action Items
- Istora: The incident report on the rogue core-geth release is published on classix.dev
- codeaholic: Review the rogue release’s commits and the incident report, talk with Cody, and report back next session
- codeaholic: Run the precompile gas benchmark against input size and validation cost, repeat the tests multi-machine, and share artifacts and a Mordor plan
- Lunar: Consider a full audit of core-geth
- Node operators: Run core-geth v1.12.23 Argos from
etclabscore/core-geth; anyone on theethereumclassic/core-geth1.13 release should switch back - Istora: Confirm the time of the next call and the special call