Ethereum Classic Community Call #47
1121 Testing & Coordination
Preamble
Hello, and Welcome!
This community call is an open voice chat discussion about Ethereum Classic. Everyone is welcome. Please be excellent to each other.
The call will be published on YouTube.
If you are interested, you can join us in the Green Room 1 hour before the next call, in a hangout that will not be recorded. Find us in the Zoom meeting.
Key Points Discussed
- The community is divided over the Olympia upgrade proposal, with significant tension between supporters and opponents
- Diego has been working on multi-client strategies with plugins for Nethermind and BESU to make ETC maintenance more sustainable
- ECIP 1121 implementation is progressing, with Istora planning to implement it in ETC Nexus
- A new repository called ECUP (Ethereum Classic Upgrade Process) has been created to track hard fork progress in a decentralized way
- Bitmain will be hosting an X Spaces call at the end of March to discuss the future of ETC
Announcements
https://cc.ethereumclassic.org
You can browse all past episodes. You can subscribe to the Calendar or RSS to never miss a call. It has a handy timezone converter. You can find AI Summaries of all the calls.
Upcoming: Bitmain will be hosting an X Spaces call at the end of March with prominent stakeholders discussing future ETC fork. Watch this space for details.
Pull Request Corner
ECIPs
Merged since last call:
- PR #563 - Drop EIP-7642 from ECIP-1121 spec (realcodywburns) — merged Mar 5
- PR #562 - Add GitHub PR template for ECIP submissions (Copilot) — merged Mar 5
- PR #561 - Modernize Jekyll build workflow and fix Superseded status visibility (Copilot) — merged Mar 5
- PR #553 - Replace external ecip_validator gem with local implementation (Istora) — merged Feb 26
- PR #551 - Fix Olympia ECIPs categorization (Istora) — merged Feb 26
Closed:
- PR #565 - Fix: update Jekyll workflow to resolve Ruby version mismatch (Copilot) — closed, superseded by #561
Open:
- PR #557 - ECIP-1122: Quantum-resistance for ETC via ML-DSA verification precompile (GravityLabLLC) — draft, 1 comment
ethereumclassic.org
- PR #1669 - Update non-Gatsby dependencies and add Playwright smoke tests (Istora)
- PR #1661 - Add article about ECIP-1120 being published (Istora)
- PR #1659 - Market Infrastructure Behind Ethereum Classic blog post (realcodywburns) — 12 comments, approved, waiting on Cody to merge
- PR #1658 - Add 1559 debate article (Istora) — 8 comments
- PR #1652 - Olympia Development Series Part 1 (chris-mercer) — 7 comments
- PR #1649 - Olympia Development Series Part 0 (chris-mercer) — 13 comments
Last Call Recap
Action items from call 46:
Istora to implement ECIP-1121 in ETC Nexus and test against main clients— Done, implementation plan drafted in ETC NexusIstora to create a fork coordination repository— Done, ECUP createdCody to review and clear blocked PRs— Done, ECIPs PRs unblocked and merged; website PRs still pendingDiego to provide input on whether EIP-7642 should be included or modified for ETC— Resolved, EIP-7642 dropped from ECIP-1121
Let’s Dive In
Olympia Update
From Chris Mercer: The Olympia upgrade client work is functionally complete and currently undergoing internal testing. Local network tests are running now to identify edge cases and bugs before moving forward with Mordor testnet deployment. Once that phase is complete, block numbers will be set and broader testing coordinated.
Chris Mercer also responded to long-unanswered questions in the Olympia upgrade discussion, addressing governance interdependency concerns around ECIPs 1111-1113 and bootstrap mechanisms.
ECIP-1121 Status
EIP-7642 has been dropped from the spec (PR #563).
An etc-nexus AI guided implementation plan has been drafted: https://github.com/IstoraMandiri/etc-nexus/blob/ecip-1121/tasks/ECIP_1121.md
Summary:
- 4 EIPs already implemented in core-geth (EIP-1153, EIP-5656, EIP-6780, EIP-2537)
- 9 EIPs require implementation, ported from upstream go-ethereum (Pectra v1.15.x / Fusaka v1.16.x)
- Phased approach:
- Phase 0: Build out ETC-specific Hive test coverage before changes
- Phase 1: Low-complexity gas/protocol changes (EIP-7623, EIP-7825, EIP-7883, EIP-7934, EIP-7935)
- Phase 2: Medium-complexity features (EIP-2935, EIP-7951, EIP-7910)
- Phase 3: EIP-7702 (Set EOA Account Code) — highest complexity, new tx type
- All implementations to be tested via Hive consensus suite and Mordor testnet before mainnet
Discussion:
- Does the phased approach and testing strategy look right?
- Should etc-nexus be moved to the ethereumclassic organization repo?
- Is ECIP-1121 ready to move forward with a block number decision?
Updates from Diego
Diego couldn’t join the call but shared the following updates on what he’s been working on.
1. Multi-client strategy — two plugins
- Nethermind ETC Plugin (repo): Fully functional plugin supporting ETC Mainnet and Mordor, with Ethash PoW, ECIP-1017 rewards, local/remote mining, and MESS artificial finality.
- Besu ETC Plugin: Positive feedback from fab10 (Besu core dev). After his question about performance impact on hot paths, Diego pivoted to test the Engine API path — all PoW logic stays in the plugin, zero impact on hot paths.
2. CL/EL separation — a modern architecture for PoW
To prove the Engine API approach, Diego built etc-cl, a standalone Consensus Layer client in Rust that handles all PoW consensus (ethash validation, difficulty calculation, uncle rules, devp2p) and talks to the Execution Layer through the Engine API — the same architecture Ethereum uses for PoS, adapted for PoW.
The minimal EL changes needed: ~860 lines of non-test code across 58 files in go-ethereum v1.16.8. This demonstrates that the CL/EL split keeps the EL very close to upstream, making long-term maintenance feasible.
3. Go Ethereum Classic — next-generation core-geth
A full-featured standalone ETC client (full-node branch) bringing core-geth’s functionality up to go-ethereum v1.16.8: ~8,370 lines across 98 files (excluding tests), covering full PoW sync (initial + live), devp2p protocol, mining, and MESS artificial finality. The wiki catalogs 85 integration points across 39 upstream files — a roadmap for keeping ETC aligned with upstream.
4. Protocol research — ECIP-1120
Progress on ECIP-1120 with input from Łukasz Rozmej (Nethermind core dev), who proposed using a system contract for historic coinbase tracking — the same approach Ethereum uses for blockhashes.
ECUP: ETC Upgrade Process
ECUP is a draft proposal for formalizing the ETC upgrade coordination process.
- Request for comments on the proposed process
- Should ECUP be moved to the ethereumclassic community organization if all agree?
- Discussion on stakeholder notification workflow (miners, exchanges, node providers)
ECIP-1122: Quantum Resistance
PR #557 introduces ML-DSA verification precompile for quantum hardening.
- Overview of the proposal from GravityLabLLC
- Is this a candidate for inclusion in a future fork?
Community Calls Process
- Should future calls include full transcripts alongside AI summaries?
- Should we alternate call times to ensure all participants can join?
- Should we automatically generate tweets to announce upcoming community calls?
- Any other process improvements?
Open Floor
- Other topics from attendees
References
- ECIP-1121: https://ecips.ethereumclassic.org/ECIPs/ecip-1121
- ECIP-1122 PR: https://github.com/ethereumclassic/ECIPs/pull/557
- EIP-7642 removal PR: https://github.com/ethereumclassic/ECIPs/pull/563
- ECUP: https://github.com/IstoraMandiri/ECUP
- ETC Nexus: https://github.com/IstoraMandiri/etc-nexus
- Call 46 recording: https://cc.ethereumclassic.org
AI Summary
Discussed topics
Olympia upgrade status
Chris Mercer provided an update on Olympia that was shared during the call.
- Details
- Istora: Shared Chris Mercer’s message that Olympia client work is functionally complete and undergoing internal testing before Mordor testnet deployment
- Istora: Questioned whether implementing ECIP 1112 makes sense if 1113 (Treasury proposal) isn’t viable
- DirtyRusski: Strongly opposed to Olympia, claiming it’s being pushed without proper community consensus
- Cody: Defended the Olympia development process
- DirtyRusski: Claimed Bitmain will not support Olympia
- Cody: Requested an official statement from Bitmain rather than secondhand information
- Conclusion
- The Olympia upgrade remains contentious with strong opinions on both sides
- Bitmain’s upcoming X Spaces call may provide clarity on miner support for the proposal
Discord community management
Discussion about changes to the official ETC Discord and community management.
- Details
- DirtyRusski: Criticized the creation of a new Discord and removal of the old one from the website
- Cody: Explained the old Discord had bot problems and was unsafe
- Justjin: Noted the transition could have been handled better
- Istora: Clarified that both Discords are currently listed on the website footer
- Conclusion
- The community remains divided over Discord management
- Having multiple Discords provides redundancy but may cause confusion for newcomers
Multi-client strategy with plugins
Diego’s update on client development was shared by Istora.
- Details
- Istora: Shared Diego’s update about Nethermind ETC plugin and BESU ETC plugin development
- Cody: Explained that the plugin architecture allows ETC to maintain its specific features while leveraging the main clients’ EVM maintenance
- Istora: Noted this approach extends the runway on existing funding by requiring less manpower
- Conclusion
- The plugin approach makes long-term maintenance more feasible
- This architecture keeps ETC clients closer to upstream, making updates easier
CL/EL separation for proof of work
Diego’s work on separating consensus and execution layers.
- Details
- Istora: Shared that Diego built ETC-CL, a standalone consensus layer client in Rust
- Cody: Explained this makes porting from upstream easier as Ethereum has split into consensus and execution layers
- Conclusion
- This modern architecture for proof of work demonstrates that minimal changes are needed to maintain ETC
ECIP 1120 protocol research
Update on research for ECIP 1120 co-authored by Diego and Istora.
- Details
- Istora: Shared that a Nethermind core dev proposed using a system contract for historic Coinbase tracking
- Istora: Discussed the possibility of creating a “reservoir” of transaction fees to smooth out rewards during low-activity periods
- Cody: Acknowledged the challenge of blockchain sustainability when block rewards run out
- Conclusion
- Research continues on how to implement miner rewards effectively
- A system contract approach could potentially solve emission curve problems
ECUP repository creation
Istora created a new repository to track hard fork progress.
- Details
- Istora: Created ECUP (Ethereum Classic Upgrade Process) to coordinate hard forks in a decentralized way
- Cody: Expressed support but raised concerns about publishing private contact information
- Istora: Clarified it would only include publicly available contact details
- Conclusion
- ECUP could serve as a coordination tool for tracking implementation details and gathering consensus
- The repository is a starting point that will evolve over time
ETC value proposition
Discussion about ETC’s unique position in the cryptocurrency space.
- Details
- DirtyRusski: Described ETC as fertile ground waiting for the right developers to build on
- DirtyRusski: Highlighted that unlike Bitcoin, ETC remains accessible to small miners with regular graphics cards
- Istora: Noted ETC’s decentralized nature and lack of a founder as strengths
- Conclusion
- ETC’s commitment to proof of work and “code is law” principles gives it a unique position
- The current low price represents a potential opportunity
Action items
- Istora
- Implement ECIP 1121 into ETC Nexus
- Create custom ETC Nexus testing framework for ECIPs
- Run tests on new self-hosted hardware instead of cloud infrastructure
- Include full transcripts of future calls in post-call updates
- Istora/Cody
- Automate Twitter Together as a GitHub action before calls
- Set up GitHub actions to push merged PRs to Twitter
- Community
- Follow Bitmain for details on the upcoming X Spaces call at the end of March
- Istora
- Confirm and announce the date for the next community call