EthereumPoW has made no GitHub code updates to Geth fork since launch

Quick Take

  • EthereumPoW has made no software commits to improve the Geth client on its GitHub since launching in September 2022.
  • Although a lack of code updates doesn’t inherently imply a problem, it could suggest that the EthereumPoW team is not making any attempts to enhance the main client software for the network.

EthereumPoW, a fork of Ethereum that preserved the original energy-intensive proof-of-work consensus mechanism, appears to have made no updates to its fork of the Go Ethereum client — commonly called Geth — since launching in September alongside The Merge.

EthereumPoW calls itself "the original PoW-based Ethereum network" that decided to remain proof-of-work when the Ethereum Foundation shifted the primary blockchain to a more environmentally friendly proof-of-stake consensus mechanism. However, EthereumPoW's Geth code on GitHub shows no commits — a software development term for how a code update is confirmed and implemented — in over seven months.

That apparent lack of action drew criticism yesterday from Bob Summerwill, the executive director at ETC Cooperative, who tweeted: "That such a low-effort affinity project has over $300 million market tells us how little 'signal' there is in price."

ETC Cooperative is the primary contributing team behind the original Ethereum fork that resulted in the creation of Ethereum Classic in 2016 and serves as a competitor to EthereumPoW. 

One EthereumPoW coin is currently trading under $3. Ethereum's native coin is trading above $1,900 per coin.

The price of EthereumPoW is down 80% from its all-time high. Source: TradingView


Keep up with the latest news, trends, charts and views on crypto and DeFi with a new biweekly newsletter from The Block's Frank Chaparro

By signing-up you agree to our Terms of Service and Privacy Policy
By signing-up you agree to our Terms of Service and Privacy Policy

Is EthereumPoW trying?

Although a lack of commits posted on GitHub doesn't inherently imply a problem, it could suggest that the EthereumPoW team may be facing challenges — or not making any attempts to enhance the Geth code.

In September 2022, the team experienced issues while trying to create a new chain ID for their forked chain. Due to the unavailability of a new chain ID, the Coinbase protocol team stepped in and started submitting pull requests to the EthereumPoW repository to address the problem.

The EthereumPoW team did not immediately respond to a request for comment.

The development comes at a time when the core Geth client team is removing support for all proof-of-work chains — a move that will further make it harder for forked chains like EthereumPoW to implement open source updates to their client.

© 2023 The Block. All Rights Reserved. This article is provided for informational purposes only. It is not offered or intended to be used as legal, tax, investment, financial, or other advice.

About Authors

Adam is the managing editor for Europe, the Middle East and Africa. He is based in central Europe and was a managing editor and podcast host at the crypto exchange OKX's former research arm, OKX Insights. Before that, he co-founded, which he elevated into one of the leading crypto media brands at its peak as the editor-in-chief. Earlier, he served as the editor-in-chief at Before joining the blockchain and crypto industry, he worked for, and He tweets via @XBT002 and can be emailed at [email protected].
Vishal Chawla is The Block’s crypto ecosystems editor and has spent over six years covering tech protocols, cybersecurity, artificial intelligence and cloud computing. Vishal likes to delve deep into blockchain intricacies to ensure readers are well-informed about the continuously evolving crypto landscape. He is also a staunch advocate for rigorous security practices in the space. Before joining The Block, Vishal held positions at IDG ComputerWorld, CIO, and Crypto Briefing. He can be reached on Twitter at @vishal4c and via email at [email protected]


To contact the editor of this story:
Andrew Rummer at
[email protected]