Ethereum to Integrate ASIC-Resistant Algorithm ProgPoW

by Arnab Shome
  • This is the second time the devs approved this algorithm as the first one got delayed.
Ethereum to Integrate ASIC-Resistant Algorithm ProgPoW
Reuters
Join our Crypto Telegram channel

Ethereum developers have approved the implementation of the Application Specific Integrated Circuit (ASIC)-resistant algorithm ProgPoW.

In the weekly meeting on March 15, the core devs of the Blockchain project reached an overall consensus for the integration of the algorithm. However, the team did not provide any specific timeline.

This is the second time, the core devs have approved ProgPow, as in a similar meeting in January, they approved the same algorithm. However, later, the developers decided to wait and delay the integration until the algorithm is audited by a third-party.

In the latest meeting, the developers argued about the effectiveness of the algorithm and its advantages over others to suppress the efficiency of ASICs.

“We’re going back to stuff we were tired of talking about months ago! We Decided that the only issue is whether there were errors in the algorithm, backdoors in the algorithm, anything like that. [...] Not arguments between the GPU people and the ASIC people. That will unroll over time,” Greg Colvin, one of Ethereum core developers, said.

Hard Forked

Ethereum, last month, pushed two hard forks - Constantinople and St. Petersburg - on the blockchain. Constantinople was a much-anticipated update for the blockchain which implemented five different Ethereum Improvement Proposals (EIPs) to permanently alter the blockchain with a host of new backward-incompatible upgrades.

The fork changed the blockchain’s economic policy and fee structure, paving a more straightforward way towards its goal to be a highly scalable platform. However, the hard fork did not change any services provided to end-users, as it was mostly a “maintenance and optimization upgrade.”

Can Ethereum Achieve Its Desired Scalability?

Last month, Craig Wright, the self-proclaimed creator of Bitcoin , has attacked Ethereum blockchain for its scalability issues in a document submitted to the Commodity Futures Trading Commission (CFTC).

Ethereum developers have approved the implementation of the Application Specific Integrated Circuit (ASIC)-resistant algorithm ProgPoW.

In the weekly meeting on March 15, the core devs of the Blockchain project reached an overall consensus for the integration of the algorithm. However, the team did not provide any specific timeline.

This is the second time, the core devs have approved ProgPow, as in a similar meeting in January, they approved the same algorithm. However, later, the developers decided to wait and delay the integration until the algorithm is audited by a third-party.

In the latest meeting, the developers argued about the effectiveness of the algorithm and its advantages over others to suppress the efficiency of ASICs.

“We’re going back to stuff we were tired of talking about months ago! We Decided that the only issue is whether there were errors in the algorithm, backdoors in the algorithm, anything like that. [...] Not arguments between the GPU people and the ASIC people. That will unroll over time,” Greg Colvin, one of Ethereum core developers, said.

Hard Forked

Ethereum, last month, pushed two hard forks - Constantinople and St. Petersburg - on the blockchain. Constantinople was a much-anticipated update for the blockchain which implemented five different Ethereum Improvement Proposals (EIPs) to permanently alter the blockchain with a host of new backward-incompatible upgrades.

The fork changed the blockchain’s economic policy and fee structure, paving a more straightforward way towards its goal to be a highly scalable platform. However, the hard fork did not change any services provided to end-users, as it was mostly a “maintenance and optimization upgrade.”

Can Ethereum Achieve Its Desired Scalability?

Last month, Craig Wright, the self-proclaimed creator of Bitcoin , has attacked Ethereum blockchain for its scalability issues in a document submitted to the Commodity Futures Trading Commission (CFTC).

!"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|} !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}