Ethereum Classic Community Call #48
Spring ETC-Quinox
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 topics rather than personalities, and that we avoid personal attacks. Let’s keep it classy.
The Next Call is Scheduled for 3rd April. Join us in the Green Room on Zoom 1 hour before the call for an unrecorded hangout.
Find past episodes, transcripts, subscribe to calendar, and more at https://cc.ethereumclassic.org.
Key Points Discussed
- EIP-7935 (60M gas limit) should be deferred from ECIP-1121, as ETC does not need increased block space — agreed by Cody, Istora, and Diego
- ECIP-1121 should not use the “Olympia” fork name to avoid confusion with the Olympia Treasury proposal (ECIPs 1111–1115)
- Diego (core client maintainer) opposes any discretionary base fee usage, and cannot support the ECIP 111X family (Olympia Treasury)
- Significant debate on ossification vs. continued protocol upgrades, with a new participant (Lunar Warden) advocating strongly for minimal changes
- New ECIPs 1116–1119 introduced by Cody, addressing miner alignment, futarchy governance, accountability, and sanctions compliance for a potential treasury
- Istora published a Maintainer Pledge blog post PR to formalize maintainer conduct aligned with ETC founding principles
- Bitmain ETC AMA announced for March 23/24
Pull Request Corner
ECIPs
Merged since last call:
- PR #573 - Create ECIP-1117, ECIP-1118, ECIP-1119 (realcodywburns) — merged Mar 18
- PR #572 - Add ECIP-1116 for BASEFEE miner distribution (realcodywburns) — merged Mar 17
Open:
- PR #570 - ECIP (draft) - Elysium Logtrees Settlement Overview (GravityLabLLC)
- PR #569 - ECIP (draft) - Elysium Revenue Routing Destinations (GravityLabLLC)
- PR #568 - ECIP (draft) - Elysium Basefee Split Routing (GravityLabLLC)
- PR #557 - ECIP-1122: Quantum-resistance for ETC via ML-DSA verification precompile (GravityLabLLC) — draft, 1 comment
ethereumclassic.org
Merged since last call:
- PR #1676 - Revert GitHub client link in footer (Istora) — merged Mar 17
- PR #1674 - Add Application: ETCMCv2 (Nowalski) — merged Mar 13
- PR #1659 - Market Infrastructure Behind Ethereum Classic blog post (realcodywburns) — merged Mar 6
- PR #1656 - Add disclaimer: debate and disclaimerLink options (Istora) — merged Mar 17
Closed:
- PR #1675 - Precautionary revert of “Discord Update” (GravityLabLLC) — closed without merge
- PR #1673 - Bump ajv from 6.12.6 to 6.14.0 (dependabot) — closed without merge
- PR #1672 - Bump minimatch from 3.1.2 to 3.1.5 (dependabot) — closed without merge
Open:
- PR #1677 - Add maintainer pledge blog post (Istora)
- PR #1669 - Update non-Gatsby dependencies and add Playwright smoke tests (Istora)
- PR #1661 - Add article about ECIP-1120 being published (Istora)
- 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 47:
-
Implement ECIP-1121 into ETC Nexus - Create custom ETC Nexus testing framework for ECIPs
- Automate Twitter Together as a GitHub action before calls
- Follow Bitmain for details on the upcoming X Spaces call
Agenda
Bitmain ETC AMA
An ETC AMA has been announced for March 23/24. Event details.
- San Francisco: Mar 23, 5PM PDT
- Buenos Aires: Mar 23, 9PM ART
- Milan: Mar 24, 2AM CET
- Beijing: Mar 24, 8AM CST
- Tokyo: Mar 24, 9AM JST
Questions can be raised on this call or posted as replies to the announcement tweet.
Before we get to Olympia, some things to sort out with 1121
EIP-7935: Set Default Gas Limit to 60M
EIP-7935 proposes increasing Ethereum’s default gas limit from 36M to 60M via client configuration changes. This is currently included in the ECIP-1121 spec. Should it be deferred from ECIP-1121?
Relay Diego’s thoughts
ECIP-1121 Fork Naming
ECIP-1121 currently references the name “Olympia,” which conflicts with the ECIPs 1111–1115 proposal that already uses that name. Should 1121 have its own distinct fork name? Seeking input from the community and ECIP authors.
Relay Diego’s thoughts
Governance Clarification Request
A discussion (#558) has been opened requesting formal clarification on several governance and procedural topics: repository merge authority, community call hosting, domain and communication control, ECIP advancement standards, and norms around dissent versus obstruction. How should these questions be addressed?
Olympia Discussion
The Olympia upgrade discussion (#530) has continued since the last call. A key development is the discovery of a contract deployment with admin key control over 1559 fund distribution — previously undisclosed information. The Olympia authors have not yet presented a solution to the bootstrap problem raised in earlier calls. How should the community evaluate this?
Relay Diego’s thoughts
Several new repositories have been published by the Olympia DAO:
- https://github.com/olympiadao/olympia-treasury-contract
- https://github.com/olympiadao/olympia-governance-contracts
- https://github.com/olympiadao/olympia-framework
New ECIPs: 1116, 1117, 1118, 1119
Several new ECIPs were recently merged. ECIP-1116 proposes a BASEFEE miner distribution with a 95/5 split. ECIPs 1117–1119 cover futarchy DAO governance, funding and streaming mechanisms, and treasury sanctions compliance. What are the community’s initial thoughts on these proposals?
ETC Nexus Updates
ECIP-1121 is now implemented on Core Geth with all 12 EIPs feature-complete (except EIP-7935). Activation block numbers are placeholders. Full Hive test suite runs are pending.
Current sitrep: https://github.com/IstoraMandiri/etc-nexus/blob/claude/ecip-1121/SITREP.md
Sign Off
The Next Call is Scheduled for 3rd April at 0200 UTC. Join us!
AI Summary
Discussed topics
EIP-1559 and ossification debate
A wide-ranging discussion on whether ETC should implement EIP-1559 and how aggressively the protocol should be updated.
- Details
- Lunar Warden: Argued strongly for ossification, stating ETC’s value comes from its unchanging, neutral codebase rather than competing on features
- Cody: Explained that 1559 provides fee market efficiency and tool compatibility, as all major wallets and DeFi front-ends now assume 1559
- Lunar Warden: Countered that many EVM chains (e.g., BSC) do not use 1559, so it is not essential for compatibility
- Istora: Acknowledged the ossification argument but noted that premature ossification could leave ETC vulnerable (e.g., quantum threats) or cause it to miss important features like L2 support
- Codeaholic: Expressed interest in the base fee component specifically, noting it could be separated from other 1559 changes and potentially used for maintenance funding
- Lunar Warden: Emphasized that ETC cannot compete with Solana or BSC on throughput, and its value comes from being “the truth” — the original, unchanging Ethereum
- Istora: Distinguished between immutability of contracts (the core value) and immutability of the protocol, arguing the former is the ultimate goal and the latter may need to change to protect it
- Conclusion
- Multiple perspectives emerged: full ossification, minimal upgrades, and active development
- Broad agreement that contract immutability and transaction finality are ETC’s core value proposition
- The debate will likely continue at future calls
EIP-7935 deferral from ECIP-1121
Discussion on whether the 60M gas limit increase should remain in the 1121 spec.
- Details
- Istora: Relayed Diego’s view that the network is not struggling for block space, so this change is unnecessary now
- Cody: Agreed to defer, noting it adds surface area for debate without practical benefit and that miners set gas limits anyway
- Conclusion
- Consensus to defer EIP-7935 from ECIP-1121
ECIP-1121 fork naming
Should the next hard fork still be called “Olympia” if it only contains 1121 (without the Treasury)?
- Details
- Istora: Relayed Diego’s position against using “Olympia” unless the 111X Treasury ECIPs are included, as it would cause public confusion; Diego suggested continuing the X-Men villain naming convention
- Cody: Agreed the naming collision is a real problem, not just cosmetic, especially given EIP-7910 (eth_config RPC) which returns fork names at the protocol level
- Lunar Warden: Noted that “Olympia” carries controversial associations and should only be used if the Treasury is included
- Istora: Proposed that 1121 should proceed independently with a distinct name, and Olympia discussion should continue on its own timeline
- Conclusion
- Agreement that ECIP-1121 should not use the “Olympia” name
- A new fork name needs to be decided before implementation, especially due to EIP-7910 requirements
Olympia Treasury discussion
Continued debate on the Olympia governance and treasury proposals (ECIPs 1111–1115).
- Details
- Istora: Relayed Diego’s position that he is against any discretionary base fee usage and cannot support the ECIP 111X family
- Cody: Confirmed that the Treasury contract should be pre-computed and hard-coded via CREATE2 into any fork that includes ECIP-1112, acknowledging the hard dependency between 1112 and 1113
- Istora: Expressed frustration that this dependency was denied for 4 months, and noted that the Olympia upgrade discussion thread on GitHub has hidden comments and restricted posting for some participants
- Codeaholic: Confirmed being unable to post further comments on the discussion thread after a single non-inflammatory comment
- Lunar Warden: Opposed the Treasury on principle, noting it would centralize ETC
- Justjin: Previously favored a treasury but now believes it would centralize ETC
- Istora: Raised concerns about bootstrapping voting rights, OFAC compliance creating unequal footing, and tying a US LLC to the protocol
- Cody: Argued compliance is necessary to prevent the chain from being shut down, and that oracles provide human oversight required by OFAC guidance
- Conclusion
- The core client maintainer (Diego) and multiple community members oppose the Treasury
- Agreement that ECIP-1121 should proceed separately to avoid delays
- The bootstrap problem and governance capture concerns remain unresolved
- Risk of a chain split was acknowledged by multiple participants
New ECIPs 1116–1119
Cody introduced four new draft ECIPs addressing objections to the Olympia Treasury.
- Details
- Cody: ECIP-1116 addresses miner alignment with a 95/5 base fee split (95% to miners); ECIP-1117 replaces token voting with a prediction market (futarchy) mechanism; ECIP-1118 introduces payment gates and milestones for treasury accountability; ECIP-1119 addresses OFAC/sanctions compliance through competitive oracle marketplace
- Istora: Found the concepts interesting in isolation but expressed concern about tying them directly to the ETC protocol, creating additional risk
- Istora: Questioned whether OFAC compliance violates ETC’s neutrality principle — why US compliance over Chinese?
- Conclusion
- The proposals attempt to address key objections to the original Olympia Treasury design
- Community feedback is needed; these remain early drafts
Maintainer pledge and governance clarification
Istora introduced a maintainer pledge blog post and discussed the state of community governance.
- Details
- Istora: Created PR #1677 for a Maintainer Pledge aligned with ETC founding documents (Declaration of Independence, Cypherpunk Manifesto), covering decentralization, censorship resistance, permissionlessness, neutrality, and immutability
- Istora: Noted that PR #1658 (1559 debate article) has been blocked for months and called for honest representation of the current state of affairs
- Cody: Agreed to review PR #1658 this week and suggested writing something new that lays out all the options plainly
- Lunar Warden: Emphasized that fair and open discussion with kindness and respect is the way forward
- Conclusion
- The maintainer pledge aims to establish shared conduct standards
- Cody committed to reviewing the blocked 1559 debate article PR
- All participants expressed desire to avoid a chain split and maintain open dialogue
Elysium proposals and quantum resistance
Brief mentions of new proposals from Codeaholic/Gravity Lab.
- Details
- Codeaholic: Invited the community to review the Elysium ECIPs (PRs #568–570), which explore routing base fee through a utility-generating mechanism as an alternative approach
- Istora: Suggested dedicating time on the next call for Elysium and quantum resistance (ECIP-1122) discussions
- Conclusion
- Both topics were deferred to the next call for deeper discussion
Action items
- Cody
- Review PR #1658 (1559 debate article) and incorporate feedback from this call
- Istora
- Submit PR to drop EIP-7935 from ECIP-1121 spec
- Submit PR to remove “Olympia” name from ECIP-1121
- Community
- Join the Bitmain ETC AMA on March 23/24
- Review Elysium ECIPs (PRs #568–570) and ECIP-1122 (quantum resistance) ahead of next call
- Lunar Warden
- Read through ETC hard fork history and prepare notes on ossification criteria for next call