The Ethereum Core Developers Conference #82, held on March 6, 2020, brought together key contributors and decision-makers in the Ethereum ecosystem to discuss pivotal upgrades and governance challenges. Spanning over three hours—longer than initially planned—the meeting delved into two major topics: BLS signature integration for Ethereum 2.0 and the contentious ProgPoW (Programmatic Proof-of-Work) proposal. These discussions reflect the ongoing balance between technical advancement, network security, and community consensus in Ethereum’s evolution.
BLS Signatures and EIP-1962: Advancing Ethereum 2.0 Cryptography
The meeting opened with a focused discussion on BLS (Boneh-Lynn-Shacham) signatures, a critical cryptographic component for Ethereum 2.0’s Phase 0. James Hancock led the segment, emphasizing that BLS signatures would underpin validator operations in the new proof-of-stake system.
Alex Vlasov presented three related EIPs:
- EIP-2537: Introduces precompiles for BLS12-381 curve operations.
- EIP-2539: Covers BLS12-377 curve support.
- EIP-2541: Proposes optimizations for contract creation costs.
These proposals aim to standardize elliptic curve cryptography within Ethereum’s execution layer, enabling more efficient zero-knowledge proofs and cross-chain interoperability. While BLS12-381 is the primary curve used in Eth2, including alternative curves like BLS12-377 offers flexibility for future privacy-preserving applications.
👉 Discover how advanced cryptography powers next-gen blockchain networks.
A central debate emerged around complexity versus utility. Martin Köppelmann questioned whether supporting multiple curves added unnecessary risk. Alex acknowledged that while implementation effort was minimal, maintaining multiple cryptographic standards could increase attack surface and developer confusion.
Vitalik Buterin highlighted the long-term value: "BLS curves are foundational for zk-SNARKs and verifiable computation—technologies that will drive scalability and privacy." The group agreed that starting with a single precompile (BLS12-381) in the Berlin hard fork was prudent, with other curves deferred to future upgrades aligned with Eth2 progress.
ProgPoW: Technical Merits vs. Community Division
After addressing BLS, the conference shifted to ProgPoW, a proposed modification to Ethereum’s mining algorithm designed to resist ASIC dominance and preserve GPU mining fairness.
Technical Update from ProgPoW Advocates
Kristy-Leigh Minehan, author of EIP-1057, outlined recent developments based on the Least Authority audit:
- Increased DAG size: Ensures memory-hardness remains effective against specialized hardware.
- Keccak implementation clarity: Confirmed alignment with official NIST standards.
- Seed reduction: Suggested using only 64-bit seeds in Keccak mixing to maintain 256-bit security without performance loss.
She emphasized that ProgPoW isn’t just an anti-ASIC measure but a step toward fulfilling Ethereum’s original vision of decentralized mining. Michael Carter (BitsBeTrippin), representing GPU miners, noted that many had already upgraded to 6GB+ GPUs, showing community readiness.
However, concerns persisted. Martin Köppelmann warned of potential 40% hash rate drops due to increased memory demands, which could destabilize network security during transition.
Community Sentiment: Growing Opposition
Despite technical feasibility, ProgPoW faced strong resistance:
- Martin Köppelmann argued that even if ProgPoW delayed ASICs, it risked alienating existing stakeholders and fracturing trust.
- Matt Luongo stressed that perceived benefits didn’t outweigh the danger of community split, especially given Ethereum’s growing number of stateful dApps.
- Multiple teams indicated plans to support clients without ProgPoW activation, raising fears of a de facto chain fork.
A recurring theme was the lack of inclusive dialogue. Many felt decisions were being made without broad consensus, undermining Ethereum’s decentralized ethos.
A Path Forward: Compromise Through Governance
Ben DiFrancesco proposed a pragmatic compromise:
- Implement ProgPoW fully across all major clients (Geth, Parity, etc.).
- Add a runtime toggle, allowing node operators to enable or disable it.
- Launch a separate testnet for ProgPoW experimentation.
This approach treats ProgPoW as a contingency or testing mechanism, not an immediate upgrade. It preserves network unity while keeping options open for future adoption if conditions change.
Tim Beiko supported this model, noting: "We’ve spent too much time debating; let’s build first and decide later." Others echoed that endless discussion could stall progress on more urgent upgrades like Eth2 integration.
Hudson Jameson concluded that while no timeline was set, ProgPoW would not be rushed into any imminent hard fork. Instead, developers committed to deeper community engagement before revisiting the decision—possibly weeks or months later.
👉 Explore how blockchain governance shapes the future of decentralized networks.
Key Takeaways and Ongoing Challenges
While no final decisions were made on ProgPoW, several insights emerged:
- Ethereum’s strength lies in its cautious upgrade philosophy, prioritizing stability over speed.
- Technical solutions must align with social consensus—no change is purely mechanical.
- The ecosystem values inclusive decision-making, especially when core principles like decentralization are at stake.
The meeting also briefly touched on other EIPs:
- EIP-2315 (Simple Subroutines): Still under development.
- EIP-2416 & EIP-2515 (Difficulty Bomb Adjustments): Updates pending; vital for managing the Eth1-Eth2 transition timeline.
Frequently Asked Questions (FAQ)
Q: What is ProgPoW and why was it proposed?
A: ProgPoW (Programmatic Proof-of-Work) is an Ethereum mining algorithm upgrade designed to reduce the efficiency gap between ASICs and GPUs, promoting fairer and more decentralized mining participation.
Q: Why was ProgPoW ultimately delayed?
A: Despite technical readiness, significant community opposition and concerns about network fragmentation led developers to pause implementation. Consensus-building became a higher priority than technical deployment.
Q: Are BLS signatures now part of Ethereum?
A: Yes—EIP-2537 (BLS12-381 precompiles) has since been included in the Altair upgrade and is actively used in Ethereum 2.0 for validator signatures.
Q: Does Ethereum still plan to move away from ASIC-dominated mining?
A: With the full transition to Ethereum 2.0 and proof-of-stake completed in 2022, mining—including ASIC vs GPU debates—has become obsolete. ProgPoW was rendered irrelevant post-Merge.
Q: How do developer conferences influence Ethereum’s roadmap?
A: These meetings serve as critical forums for technical alignment, risk assessment, and social coordination among core contributors, directly shaping upgrade priorities and timelines.
Q: What role do audits play in Ethereum upgrades?
A: Independent audits—like the one conducted by Least Authority on ProgPoW—are essential for identifying vulnerabilities, validating design assumptions, and building trust across the ecosystem.
The Ethereum Core Developers Conference #82 exemplified the complex interplay between innovation and governance in open-source blockchains. While technical paths may be clear, the true challenge lies in aligning diverse stakeholders around shared goals—ensuring Ethereum evolves securely, inclusively, and sustainably.
👉 Stay ahead of blockchain innovation with real-time insights and tools.