Ethereum successfully postponed the difficulty bomb, the merged "blockers" and these
Original title: "Ethereum successfully postponed the difficulty bomb, there are still these "blockers" in the merger"
Original author: Ben Edgington, ConsenSys
Original compilation: Overnight porridge, the way of the metaverse
Ethereum successfully postponed the difficulty bomb, and the merged "blocker" is still There are these Note: Last week, Ethereum successfully completed the Gray Glacier (Gray Glacier) hard fork upgrade, delaying the difficulty bomb by about 100 days, and for the next merger of Ethereum, developers from ConsenSys Ben Edgington shared some information (translation has been abridged).
The seventh shadow fork of the main network
1. Erigon has some observation difficulties, which Related to the setup mechanism of the shadow fork, it was not a problem for the real mainnet fork, and the problem has been fixed.
2. The Besu node encountered a database corruption problem, which seems to be related to concurrency (multithreading at the same time update database), and this has also been found outside of merges. The team is urgently fixing this issue, it's not only related to the merge, it should be done within a week or two.
There is also a deadlock problem Happened to Nethermind and Teku, basically, both are waiting for each other. Anyway, Teku has been updated to retry more aggressively, which should fix the problem. Prysm will do the same update.
Digging into these edge cases is The reason we shadow fork! Next will be full steam ahead.
According to the plan, the mainnet The 8th shadow fork will take place on July 5th.
Sepolia Testnet Merge< /h3>
Sepolia testnet will be launched on 7 It will be merged around May 5th, you can follow bordel.wtf to check the time, the time of merging largely depends on the computing power of the network, sometimes some people will add a lot of computing power, so the specific time of merging is not Not sure.
Ropsten Sync Test
Synchronized by two independent clients Managing two blockchains presents some challenges, and this is probably the trickiest part of the merger that we have to consider. For this reason, the synchronization process between paired clients has received some additional scrutiny. To this end, the EF DevOps team is running a series of tests on the Merged Ropsten testnet and documenting their findings.
Staking (Pledge)< /h3>
17th Stakehouse Community Call The conference was held a few days ago, under the banner of "lowering the technical barriers to staking Ethereum Solo", these have become a very good resource.
I strongly encourage you to watch the live broadcast and even join the next conference call if you can, you will learn a lot.
When we move to Proof of Stake Isn't 99.95% power reduction good enough for you when it comes to PoS? Well, check out @jcrpt for his verification under 10 watts.
Research
In a recently published survey article, Vitalik talked about possibly limiting the validator set size on the topic, this is an interesting exploration of the various trade-offs we face.
Other progress
1. Flashbots has started to update the verifier's MEV-Boost implementation progress every week:< /p>
（1）June 17-24
< /p>
(2) June 24-30
2, Prysmatic Labs Community Update: June 2022
3. Ethereum Foundation’s Documentation on Staking Operators Made an interesting proposal request. Responses are due by July 8th, so please feel free to comment.
4. Coinbase has resumed their ETH2 update.
Welcome to join the official BlockBeats community:
Telegram Subscription Group: https://t.me/theblockbeats
Telegram Discussion Group: https://t.me/BlockBeats_App
Official Twitter Account: https://twitter.com/BlockBeatsAsia
Related Articles
