Ethereum Core Developers Still Undecided on Move to ASIC-Resistant PoW Algorithm

Siamak Masnavi

On Friday (February 1), Ethereum's core developers held a meeting during which they discussed a change to Ethereum's Proof-of-Work (PoW) algorithm that would have reduce the efficiency of ASIC miners, thereby improving decentralization by increasing the attractiveness of GPU miners.

During Ethereum Core Devs Meeting #54, which was hosted by Hudson Jameson (a communications officer at the Ethereum Foundation), and included core developers such as Afri Schoedon ("Hardfork Coordinator"), Martin Holst Swende ("Security Lead"), Antoine Toulme, and Brett Robertson, one of the main topics discussed was ProgPow, a shorthand form of "Programmatic Proof-of-Work" that "can be seen as the successor of the Ethash algorithm with enhanced ASIC resistance."

Here are a couple of the things said about ProgPow at the core developers meeting on January 4:

  • Hudson Jameson said that he had heard "very little dissent" to implementing ProgPow;
  • Martin Holst Swende said that moving to ProgPow would "postpone the level of ASICs on our network for at least a year on our network, or perhaps more" and that he "would like to switch as soon as possible to give us time to move to proof-of-stake"

The developers said that they were considering moving to ProgPoW (which would be implemented as a hard fork) sometime before the launch of the Istanbul hard fork (which comes after the Constantinople hard fork).

At yesterday's core devs meeting, Jameson, started the discussion of ProgPow by saying:

"There is a group forming or multiple groups forming to perform a third-party audit on ProgPow with the intent to get an audit done before we stop accepting EIPs for Istanbul. The reason for that is to test the viability of the claims that were made about ProgPow such as that it is even across all types of cards like AMD and NVIDIA and ASICs and FPGAs, that it has the same hash rate and performance, and also that there is not going to be any problems once we launch it on mainnet." 

Unfortunately, there is no funding yet for such an audit. 

The problem with ProgPow is that although there is a general consensus amongst the core developers to eventually implement ProgPow, there has been some pushback by some members of the wider Ethereum community, who are concerned that it will reduce security (since eliminating the advantage currently enjoyed by ASIC miners might signficantly reduce the cost of an attack on the Ethereum network), that it is an anti free-market measure (since it hurts manufacturers such as Bitmain who have spent a lot of time and money creating ASIC miners for Ethereum), and that it could result in a chain split if some nodes decide to upgrade to ProgPow and the rest decide to stay with Ethash.

It was easy to see that some core developers feel that there is not enough information yet to make a decision on ProgPow, while some feel that too much time has been wasted already.

At one point, Swende asked: 

"We've been trying to come [up] with a decision for several months... So, I'm wondering how will this be resolved."

Greg Colvin (who some have nicknamed "Ethereum's Gandalf"), one of the core developers of the Ethereum Virtual Machine, answered:

"It's resolved by us making a fxxxing decision!"

Jameson then asked:

"Do we need more data to make a decision or can we just make it?"

Colvin replied:

"We can just make it! It's our job!"

Lane Retig, an eWASM core developer added:

"I am glad that some folks have strong opinions about it. I just feel that a number of core devs kind of have said the opposite, that they don't make qualified to make this decision." 

Jameson feels that an audit will help to answer a lot of questions about ProgPow:

"So, I think personally that having a third-party, as neutral, as it can be, ... assess some of the claims of ProgPow, if we can get to a point where we can say 'this will work and this is why it will work if we put it in,' that will help a lot."

After another developer, "Piper", said that this was a decision that he did not want to make, Jameson said:

"We still haven't explored all the possibilities about getting community feedback before we're forced to make a decision, including stuff like this audit which I consider a piece of community feedback."

Colvin replied:

"I am happy to get more information. I just want some decision that says this is the information we are going to get, and then we are going to decide, and I'm very opposed to the notion of we can't decide so we... will let the hashpower decide... I don't see risking a split in the network just because wen't make our mind up."

 

Featured Image Credit: Photo via Pexels.com