Over 10 years we help companies reach their tech goals. Devonfertech is a value-driven technology agency dedicated.




+1 -868-37-DEVON

Crypto News

Ethereum Devs Successfully Complete Merge Shadow Fork With No ‘Client Incompatibility Issues’ – Technology Bitcoin News

Next week or roughly around four days from now, The Merge is expected to be implemented and Ethereum will transition from proof-of-work (PoW) to proof-of-stake (PoS). According to Ethereum developers, prior to the Paris upgrade, programmers successfully completed the 13th and last shadow fork.

Ethereum’s 13th and Last Shadow Fork Is Complete

On Friday, social media has been abuzz with chatter about The Merge and Ethereum’s transition from PoW to PoS. Furthermore, ETH developers and the Ethereum research and engineering company Nethermind revealed the last shadow fork is now complete. Basically, a shadow fork is an upgrade applied to the existing version of Ethereum’s mainnet, and the public, in general, is unaware of the testing phase.

So far, with the last shadow fork, ETH developers have executed 13 successful shadow forks. “Transition in Mainnet-Shadow fork-13 (the last shadow fork before The Merge) was successful for all Nethermind nodes,” the researchers from Nethermind said on Friday. Moreover, there’s a shadow net scanner, a shadow net mainnet explorer, and a shadow net Beacon Chain explorer as well, to help with testing.

Bitcoin.com reported on the pre-Merge upgrade called Bellatrix on September 6, which was the final pre-Merge transition before the Paris Upgrade. Paris will trigger The Merge and after the last PoW block is mined, an Ethereum validator will mine the following block. If that block is successfully mined by a validator, The Merge will be 100% complete.

“MSF13 merged earlier today, we saw attestation rate drop to -97%,” an Ethereum developer wrote after the shadow fork. “This was due to some stale data on one node that I forgot to clear up, the node thought it was on the wrong shadow fork. No other client incompatibility issues were seen.”

With the shadow fork completing successfully on Friday, it signals the readiness for The Merge, and entities running ETH software will need to upgrade. While some people celebrated the shadow fork, others criticized Ethereum and called it “centralized.” On Saturday, following the 13th shadow fork, the test was discussed a great deal on social media channels like Twitter and Reddit.

The Merge will execute when the network hits a Total Terminal Difficulty (TTD) value on the execution layer, which will be 58750000000000000000000. This is estimated to happen on September 14, 2022, or roughly four days from when this post was written.

Tags in this story
13th Shadow Fork, Beacon Chain, Beacon Chain validators, Bellatrix upgrade, Block Production, Code, Codebase, ETH dominance, Ethereum (ETH), Ethereum Developers, Final Shadow Fork, Last Shadow Fork, Nethermind, Paris Upgrade, PoS, PoW, ruleset change, Shadow fork, Software, technology, The Merge, The Merge transition, Vitalik Buterin

What do you think about the completion of the 13th shadow fork and the upcoming Paris upgrade? Let us know what you think about this subject in the comments section below.

Jamie Redman

Jamie Redman is the News Lead at Bitcoin.com News and a financial tech journalist living in Florida. Redman has been an active member of the cryptocurrency community since 2011. He has a passion for Bitcoin, open-source code, and decentralized applications. Since September 2015, Redman has written more than 6,000 articles for Bitcoin.com News about the disruptive protocols emerging today.

Image Credits: Shutterstock, Pixabay, Wiki Commons

Disclaimer: This article is for informational purposes only. It is not a direct offer or solicitation of an offer to buy or sell, or a recommendation or endorsement of any products, services, or companies. Bitcoin.com does not provide investment, tax, legal, or accounting advice. Neither the company nor the author is responsible, directly or indirectly, for any damage or loss caused or alleged to be caused by or in connection with the use of or reliance on any content, goods or services mentioned in this article.

(function(d, s, id) {
var js, fjs = d.getElementsByTagName(s)[0];
if (d.getElementById(id)) return;
js = d.createElement(s); js.id = id;
fjs.parentNode.insertBefore(js, fjs);
}(document, ‘script’, ‘facebook-jssdk’));

Source link



Leave a comment

error: Alert: Content is protected !!