London Hard Fork is expected to be activated on Ethereum mainnet on August 4

London Hard Fork is expected to be activated on Ethereum mainnet on August 4

Golden Finance reported that the Ethereum core developer meeting ended in the early morning of the 10th Beijing time. Ethereum developer Tim Beiko tweeted that, as confirmed earlier this week, all clients reiterated that they were satisfied with the mainnet's London hard fork deployment block of 12965000. The London upgrade should land on the mainnet on August 4 (unless serious security issues are found as usual).

London Hard Fork is scheduled to be activated on Ethereum mainnet at block height 12965000

Golden Finance reported that Ethereum developer Tim Beiko said that his proposal for "London Hard Fork activated on the mainnet at block height 12965000" has been merged, and the client is expected to be released this weekend or early next week, and an appropriate announcement will be issued in early or mid-next week. Earlier, Ethereum developer Tim Beiko said that the proposal for London Hard Fork to be activated on the mainnet at block height 12965000 is expected to be between 13:00 and 17:00 UTC on August 4, 2021 (21:00 on August 4 to 1:00 on August 5, Beijing time).

Ethereum testnet Rinkeby has activated the London upgrade at block height 8897988

Ethereum testnet Rinkeby activated the London upgrade at block height 8897988 at 01:27:32 on July 8. This upgrade includes EIP-1559, which changes the Ethereum 1.0 Gas fee market, and postpones the difficulty bomb to December 1, 2021. The next step for the testnet Rinkeby to activate the London upgrade will be to deploy the London upgrade on the Ethereum mainnet. The final time for the mainnet upgrade will be announced at the Ethereum core developer meeting on July 9.

Ethereum 2.0 client Nimbus released version v1.4.1 to fix the problem that v1.4.0 may lose a small amount of proofs

Official news, Ethereum 2.0 client Nimbus released version v1.4.1, which is less urgent. Nimbus v1.4.0 users may have noticed that a small number of (seemingly random) proofs have been lost since the update. Investigations into this issue showed that due to the significant performance improvements in v1.4.0, Nimbus verification nodes occasionally sent their first proofs for a new era before some nodes were ready. These "slow" nodes eventually gave up early proofs because they were busy with epoch transitions. As a fix, v1.4.1 uses a larger sending delay. Nimbus v1.4.0 users who want to achieve the best proof effect are encouraged to upgrade as soon as possible. Other changes include log refreshes and indicator fixes. Earlier news, Ethereum 2.0 client Nimbus released version v1.4.0, which improved proof validity, CPU usage, RPC APIs, and prepared for the refactored verification node client.

Ethereum Developer: Etherscan can show transaction fees saved by using EIP-1559

Ethereum developer Tim Beiko tweeted that the current Etherscan page can already show the transaction fees that can be saved by using EIP-1559.