Blockchain
Mining
Tech
Tokens
Top 100 Crypto
EthereumPoW splinter developers Announces Ethereum Fork

EthereumPoW splinter developers Announces Ethereum Fork

Sep 14, 2022
Read in 3 mins
Share!
Share!

A group of “geeks and crypto investors who believe in proof-of-work (PoW)” will mainnet 24 hours after the Merge.

A few days after the protocol update that will change the Ethereum consensus system from Proof-of-Work (PoW) to Proof-of-Stake (PoS), the group of EthereumPoW splinter developers – who would like to fork Ethereum and maintain a chain in Proof of Work – has finally announced plans to launch its hardfork soon after the Ethereum Merge on September 15.

ETHW mainnet will happen within 24 hours after the Merge. The exact time will be announced 1 hour before launch with a countdown timer and everything including final code, binaries, config files, nodes info, RPC, explorer, etc. will be made public when the time’s up,” announced the group on its official Twitter and a blog post to the ETHW community. According to the group, the mainnet will start 2,048 empty blocks beyond the Merge block and therefore “the Merge block + 2049 will be the 1st block on ETHW that may contain any transactions.” 

Ethereum Foundation is shifting to a PoS fork, while we decided to stay with the PoW Ethereum” declared the community, composed by a bunch of “geeks and crypto investors from all over the world who believe in proof-of-work (PoW)”, guided by the chinese crypto miner Chandler Guo, who announced the proof-of-work hardfork on Twitter on July 27, 2022.

Some mining pools (f2pool, poolin, BTC.com, etc.) have confirmed their support of ETHW mining and the community has also partnered with Ethwmine which will be committed to providing long-term mining pool services for ETHW.

If the birth of a new ethereum-styled fork will be successfull and whether there will actually be nodes and miners willing to put resources on the project, everyone who owns ethereum (ETH) will be able to maintain ETHW.

WHAT DO YOU THINK ABOUT THIS CONTENT?
cool.svg cool_white.svg COOL!
notbad.svg notbad_white.svg NOT BAD!
notcool.svg notcool_white.svg NOT COOL!