Ethereum Classic Community Call #50
Fifty and Counting
Key Points Discussed
- Diego’s go-ethereum#34642 fix has merged upstream; awaiting 1.17.3 release to promote go-ethereum-classic to testing, with early benchmarks showing performance improvements over CoreGeth
- Nethermind plugin fully synced on ETC mainnet (full archive in under 2 days, ~500GB); Diego recommends it for client diversity
- Besu plugin blocked on two upstream PRs for full sync issues; a combined test build with fixes and ETC plugin abstractions is performing well
- Olympia authors remain unresponsive to community discussion but have made ~400 commits across five websites in two weeks, claiming mainnet activation before 2027
- Fukuii (IOHK Mantis fork) is positioned as the “primary client” for Olympia, with CoreGeth labeled as “legacy” on olympiadao.org
- New participant Citrullin (ex-IOTA Foundation) proposed based rollups as a compromise for DAO/treasury functionality without modifying L1
- Community debated ossification, fixed monetary supply, and whether ETC’s value proposition requires protocol-level innovation or benefits from stability
- Concern raised that a contentious chain split with shared chain ID could trigger exchange delistings, replay attacks, and ecosystem damage
Full AI Summary and Transcript ↓
Preamble
Hello, and Welcome!
This community call is an open voice chat discussion about Ethereum Classic. Everyone is welcome.
The call will be published on YouTube. We kindly ask that discussion stays focused on ideas rather than individuals. Let’s keep it classy.
The Next Call is Scheduled for 1st May. Join us in the Green Room on Zoom 1 hour before the call for an unrecorded hangout — same time, same place.
Find past episodes, transcripts, subscribe to calendar, and more at https://cc.ethereumclassic.org.
Today’s Agenda
Last call was a bit tech-heavy, so this week we’re keeping things more open — a free-flowing discussion on some of the more philosophical aspects of ETC and longer-term strategic questions.
Introductions
Quick round of introductions for everyone on the call, and if there’s anything you want to talk about.
ETC in the News
ETC was added to Japan’s official FSA/JVCEA Green List of ~30 regulated crypto tokens on April 4, 2026. Inclusion means fast-tracked exchange listings, regulatory recognition, and easier access to banking relationships for compliant platforms operating in Japan.
Pull Request Corner
- No merges in the main repos since last call
- Development updates covered below in ETC Cooperative Development Update and Olympia Development Update
- PR #1661 (ECIP-1120 article) has been closed; another update article will be published next week instead
- Dropping EIP-7935 and replacing ECIP-1121 has been discussed with Cody over many calls but there has been no movement; a couple of new ECIPs will be raised before call 51, including a 1121 alternative without Olympia
ETC Cooperative Development Update
- go-ethereum#34642 has merged — awaiting the 1.17.3 upstream release to rebase go-ethereum-classic and promote it to testing
- Waiting for Safe to merge and release the next version (safe-deployments#1455, safe-deployments#1456) before testing the 1.4.1 Safe Wallet contracts with the Catacomb interface
- Besu sync improvements in progress (besu-eth/besu#10220, besu-eth/besu#10235) — Besu currently cannot complete a full sync of ETH Mainnet using the Bonsai database, which also affects ETC as a plugin. Awaiting upstream merges before submitting the ETC plugin abstractions PR. A combined build of upstream + both fixes + plugin abstractions + besu-etc-plugin is testing well.
- Nethermind plugin is now synced and working (action item from call 49)
- Notable finding shared by the ETC Cooperative about Uniswap v3: link
Olympia Development Update
Since the last call there has been notable activity around the Olympia-affiliated websites discussed in The ETC Fee Market Debate. Even though the Olympia authors are not engaging in ECIP discussions, they are nonetheless continuing active development. All repos show heavy AI-assisted co-authoring.
fukuii - 169 commits
Scala-based EVM execution client forked from IOHK’s mantis. Work focused on fast sync and SNAP-based state download, Engine API support (V1-V4), and Sepolia testnet compatibility. Listed as the primary client for the Olympia upgrade, with Core-Geth described as “legacy” and “scheduled to phase out”.
Primary client for the Olympia upgrade. — olympiadao.org/clients
ethereumclassicdao.org - 220 commits
Building out a three-tier governance model and refining messaging around the DAO’s relationship with the ETC Cooperative. Frames the Cooperative as a temporary placeholder whose role is being superseded by the DAO LLC.
Every client decision, network upgrade, and emergency response has been coordinated through us. (referring to Ethereum Classic DAO LLC) — ethereumclassicdao.org
olympiadao.org - 109 commits
Marketing site promoting the Olympia upgrade, with governance pages, EVM compatibility deep-dives, and client implementation listings. Positions ETC as proof-of-work with full EVM parity and claims development will be open to any developer through the DAO.
Olympia is targeted for mainnet activation before 2027. — olympiadao.org/governance
olympiatreasury.org - 87 commits
Treasury-focused site with a dedicated upgrade page, countdown timer targeting January 2027, and ECIP-1111 treasury messaging. Frames Ethereum’s basefee burn as wasteful and ETC’s treasury redirection as the superior design.
Olympia is in final testing on the Mordor Testnet. — olympiatreasury.org
ethereumclassic.com - 20 commits
New ETC landing site replacing stub pages with real content on trading, DeFi, and philosophy. Heavy Olympia promotion and institutional positioning with investment product and regulation pages. Claims ETC maps directly to Bitcoin’s commodity precedent.
Olympia is Ethereum Classic’s most significant protocol upgrade. Three changes arrive in a single activation: Fusaka EVM alignment, EIP-1559 fee market, and a protocol-managed treasury. — ethereumclassic.com/olympia
Agenda
These are just some ideas for topics to get the conversation going — feel free to jump in at any time.
1559 Funding Mechanics
At ETC’s current transaction volume, would a fee-based treasury actually receive meaningful funds — or does it only generate revenue once the chain reaches saturation? Is this a chicken-and-egg problem: the treasury needs a busy chain to function, but a busy chain may not need a treasury?
Miner Signalling Tools
What tools exist or could be built to better capture miner sentiment on proposed protocol changes before they reach a hard fork decision point?
Agentic Future
PoS chains require identity and permission layers that limit autonomous use — does ETC’s permissionless PoW architecture offer a better foundation for agent-driven applications? What would ETC’s role look like in a Web 4.0 / agentic computing future?
Mythos / Security Audit
Updates and discussion on the Mythos security audit. What were the findings, and what actions should the community take in response?
Ossification
Should ETC adopt an explicit ossification stance — prioritising protocol stability over further upgrades? What are the trade-offs, and does the current fork debate change the calculus?
Network Value Index
Market cap alone may not reflect ETC’s health or progress. Could the community develop a composite index — incorporating factors like node count, developer activity, or chain security — that better represents real-world network value?
Being Small as Strength
Is ETC’s smaller size a liability, or does it provide resilience and focus that larger chains lack? What’s the case that staying small is a long-term advantage rather than a problem to be solved?
AI Summary
ETC Cooperative Development Update
Diego provided updates on client diversity and infrastructure progress.
- Details
- Diego: go-ethereum#34642 fix merged upstream; waiting for 1.17.3 release to rebase go-ethereum-classic and promote to testing
- Diego: Early testing shows go-ethereum-classic has better performance than CoreGeth due to path-based database schema and parallel sync improvements
- Diego: Plans to publish benchmark numbers once the new upstream release is available
- Istora: Fully synced Nethermind as a full archive node (~500GB, under 2 days); recommends it for client diversity
- Diego: Recommends trying Nethermind for those looking to run an ETC client
- Diego: Two Besu upstream PRs under review for full sync issues affecting both ETH and ETC; once merged, will submit plugin abstraction PR
- Diego: Running upstream Besu + fixes + plugin abstractions + besu-etc-plugin with good performance; estimates another month or two for readiness
- Diego: Submitted PRs to Safe for 1.4.1 contract support; one merged, awaiting second for Catacomb multi-sig upgrade
- Diego: Discovered fake Uniswap V3 contracts deployed on ETC at the same addresses as legitimate Ethereum contracts, using leaked deployment keys to drain funds; published warning via ETC Cooperative X account
- Istora: Clarified that existing ETC Swap and Hebe Swap contracts are unaffected; users should verify contract addresses
- Conclusion
- Multiple client alternatives (go-ethereum-classic, Nethermind, Besu plugin) are progressing toward production readiness
- Nethermind is ready for community testing and miner adoption
- Users should not interact with Uniswap V3 addresses on ETC as they contain malicious contracts
Olympia Development Activity and Websites
Istora presented findings on Olympia-affiliated GitHub activity and website content.
- Details
- Istora: Approximately 400 commits across Olympia-affiliated repos in the two weeks since last call, heavily AI-assisted
- Istora: Fukuii client (IOHK Mantis fork) being developed by realcodywburns as the intended primary client for Olympia
- Istora: olympiadao.org labels CoreGeth as “legacy” and “scheduled to phase out” in favor of Fukuii
- Istora: ethereumclassicdao.org claims “every client decision, network upgrade, and emergency response has been coordinated through us” (referring to the DAO LLC)
- Istora: olympiadao.org states “Olympia is targeted for mainnet activation before 2027”
- Istora: olympiatreasury.org claims “Olympia is in final testing on the Mordor Testnet”
- Istora: ethereumclassic.com positions Olympia as “Ethereum Classic’s most significant protocol upgrade”
- Istora: Olympia authors remain unresponsive to community discussion despite active development
- Conclusion
- Olympia development is proceeding without community engagement or consensus
- Claims on the websites are disputed by call participants
- The community needs to inform exchanges, miners, and infrastructure providers about the situation
Chain Split Risks and Ecosystem Impact
The group discussed practical implications of a potential Olympia chain split.
- Details
- Lunar: Asked how RPCs and exchanges would handle two chains sharing the same chain ID
- Istora: Explained miners determine the longest chain; exchanges and RPC providers would need to choose which fork to follow
- Istora: Warned that sharing a chain ID without replay protection could cause financial losses
- Citrullin: Argued exchanges would likely delist ETC entirely rather than deal with the confusion, as ETC is not large enough for them to bother
- Lunar: Suggested informing exchanges and miners proactively rather than treating it as a war
- Istora: Emphasized that without pushback, Olympia could succeed by default
- Istora: Noted there is no official ETC entity, so Olympia authors have equal standing to claim the brand
- Lunar: Argued the legitimacy question ultimately rests with individual participants
- Conclusion
- A contentious chain split with shared chain ID poses serious risks to holders, exchanges, and miners
- Proactive communication with ecosystem participants is necessary
- The community should continue documenting opposition via nolympia.dev
Based Rollups as Alternative to L1 Treasury
Citrullin proposed an alternative approach to funding that avoids L1 protocol changes.
- Details
- Citrullin: Suggested running DAO/treasury functionality on a based rollup anchored to ETC L1, allowing miners to cut funding if the DAO fails
- Citrullin: Argued this preserves L1 simplicity while enabling governance experimentation at higher layers
- Istora: Asked how miners would vote in such a system
- Lunar: Supported keeping L1 clean and simple, with innovation happening on upper layers
- Conclusion
- Based rollups could offer a middle ground between protocol ossification and treasury functionality
- The idea needs further development but aligns with ETC’s layered architecture philosophy
Ossification and Monetary Policy Debate
Extended philosophical discussion about ETC’s long-term direction.
- Details
- Lunar: Argued ETC’s only advantage over ETH is transaction finality and immutability; protocol changes undermine this
- Lunar: Questioned whether any more hard forks are needed beyond basic EVM alignment
- Citrullin: Argued that scarcity leads to reduced velocity, reduced network activity, and eventual network death
- Istora: Countered that injecting subjectivity (inflation changes, treasury decisions) into the protocol breaks all other assumptions about its neutrality
- Istora: Drew analogy to IPv4 as a stable, unchanging protocol that remains extremely useful
- Lunar: Compared ETC to “Bitcoin plus smart contracts” with golden enforceable contracts
- Istora: Emphasized that Bitcoin-style organic funding from profitable businesses is more aligned than DAO treasuries
- Citrullin: Acknowledged DAO governance issues but argued pure ossification leaves no path to sustainability
- Istora: Noted that Olympia’s 1559-based treasury generates zero revenue until ETC reaches block saturation (requiring ~50x current transaction volume)
- Conclusion
- The community broadly supports minimizing protocol changes while maintaining EVM compatibility
- Fixed monetary supply is considered non-negotiable by existing community members
- The 1559 treasury’s chicken-and-egg problem undermines Olympia’s funding rationale
- Innovation should happen on layers above the base protocol
Action Items
- Istora: Publish new ECIP as alternative to ECIP-1121 (without Olympia) before call 51
- Istora: Update ECIP-1120 and publish new article on ethereumclassic.org
- Diego: Publish go-ethereum-classic testing release once upstream 1.17.3 is available
- Diego: Publish performance benchmarks comparing go-ethereum-classic and CoreGeth
- Community: Inform exchanges and miners about potential Olympia chain split risks
- Codeaholic: Prepare quantum security ECIP discussion for call 51