Ethereum’s London Hard Fork Scheduled to Commence on August 4
The highly anticipated Ethereum hard fork is expected to launch on August 4 at block height 12,965,000 according to Ethereum core developers. The London hard fork will add five Ethereum Improvement Proposals (EIPs) that aim to enhance the blockchain. However, the Berlin hard fork was postponed after a vulnerability was identified by the audit company Chainsecurity and the London hard fork could be delayed as well.
London Hard Fork Scheduled for August 4, 2021
Ethereum’s London hard fork is one of the most long-awaited changes in quite some time and will follow the recently implemented Berlin hard fork. The London upgrade is meant to complement the Ethereum 2.0 transition which will change the ETH chain from proof-of-work (PoW) to proof-of-stake (PoS).
— banteg (@bantg) July 6, 2021
Just recently, Bitcoin.com News reported on three Ethereum testnets preparing to leverage the London hard fork. Now that the implementations have been successful following adaptations to the testnets Goerli and Ropsten, pull request #223 was officially merged.
“This pull request proposes block 12965000 for the mainnet activation of the London network upgrade,” explained Ethereum core developer Tim Beiko. “The ETA for this block should be between 13:00 UTC and 17:00 UTC on August 4, 2021. We had agreed on ACD116 to decide the block async and try and get client releases done for ACD117 (July 9).” Beiko added:
If we can roughly hit that timeline, then August 4th should provide enough time to advertise the client releases that are mainnet compatible, and allow infrastructure providers [and] node operators to upgrade.
EIP-3554 messes with the miner’s difficulty bomb to ease the transition from PoW to PoS. Additionally, the upcoming fork will also feature EIP-3198: BASEFEE opcode, EIP-3529: reduction in refunds, and EIP-3541: reject new contracts starting with the 0xEF byte.
What do you think about the Ethereum London upgrade date? Let us know what you think about this subject in the comments section below.
Powered by WPeMatico