Consensus layer progress update (as of 2021/12/3)

The “Consensus Layer Progress Update” series of articles are the original “Eth2 Progress Update”

Stakeholders, please upgrade your Eth1 node as soon as possible!

The Arrow Glacier upgrade will be carried out at block height 13,773,000.

Etherscan has made a convenient upgrade countdown timer. As of the publication of this article, the estimated upgrade time is 03:59:54, December 10, 2021, Beijing time. If your Eth1 node is not upgraded to the latest version before then, you may lose the block proposal.

First recommendation

If readers want to entertain themselves with anything this week, then look at Vitalik ‘s updated roadmap! (Translator’s Note: ECN has produced a Chinese version of the roadmap, please check it out)

Beacon chain

Last Wednesday was the first anniversary of the creation of the Beacon Chain. This is truly an epic year, and there have been almost no accidents.

I originally planned to write an article about the first anniversary of the beacon chain, but others have already done this:

  • Anthony Sassano wrote a very good review article in his The Daily Gwei update
  • And some statistics from EthStaker

We are not only celebrating the first anniversary of the launch of the beacon chain, but also Lodestar’s proposal of the first mainnet block is also worth celebrating?

It is a pity that there are still two creation verifiers that were confiscated in the last few days, namely 1859 and 12697. There is no more information about them. They worked well all year, and they were fined and confiscated at the last minute, which was sad enough. There are other not-so-good news. Lefteris stumbled upon one of the validators who had been offline since creation. There is another verifier 13872.

Beacon chain specification related

Specification v1.1.6 has been released. This version includes a fix for a hard-to-attack vulnerability in the fork selection, and an increase in the Proposer Score-bosting to resist various attacks. These changes are not critical to the consensus, so there is no need to deploy a hard fork in the client.

If you have recently noticed that the bandwidth and/or CPU usage of your beacon node has increased significantly, it is probably caused by a specification change (we are restoring the original specification version). This specification change will be applied to all clients. After the recovery version is deployed, it is likely to see improvements.

Regarding other news, Danny proposed to modify our proof subnet because we already have some experience on how to run this large-scale p2p network.

It is also Danny, who has put forward some ideas and suggestions on how to implement the infrastructure of weakly subjective synchronization in practice.

The Merge

Tim Beiko published article, “How will the merger affect the etheric Square application layer”, get a lot of praise, even though I prefer my proposed title “Eth2 will affect Eth2”.

The second community conference call on this topic was held on December 3. I haven’t seen the meeting video or meeting notes, but please follow the Ethereum Foundation’s YouTube channel, there may be some content posted.

Here is a tracking document prepared for the mainnet merger, which you can use as a reference.

Kintsugi Testnet

The weekly merger of the developer testnet is progressing smoothly. We built and destroyed the test net. This case is about Barnabé’s poor performance in the Merged Developer Testnet 2. (The good news is that this problem will be fixed in v1.1.6 of the specification.)

It is planned to launch the Developer Testnet 3 next week, and if all goes well, a more public and longer-running merged developer testnet, the Kintsugi testnet, will be established around December 14. Here is a document to track the progress of the client to support Kintsugi.

For details lovers, here are the specific versions and PRs related to Kintsugi that I extracted from Mikhail Kalinin’s internal ConsenSys talk (hope you don’t mind!):

  • Kintsugi Merged Developer Testnet 2 has recently started

     

  • Kintsugi specification v3 has been released

    ⋄ Consensus layer #2728

    ⋄ Executive layer #4463, #4465, #4466, #4482, #4487, #4493

    ⋄ Engine API #130, #132, #133, #134, #135

     

  • The meeting to merge the testnet has started

    ⋄ Conference agenda

    ⋄ Test plan

As mentioned above, a merger testnet meeting was held last week. This triggered a series of activities by Marius of the Geth team, who is calling an army of volunteers to test the merger. Here are some tips:

  • Marius’ merger testnet plan
  • convene
  • More than 300 volunteers participated!
  • Marius’ own process

For participating volunteers, here are some instructions for joining the Developer Testnet 2.

One of the main challenges currently facing the client team is to implement “optimistic sync”, which is a method of coordinating consensus clients and executing clients when joining an existing network. There is a plan that specifies the optimistic sync process. At the same time, there are some notes here.

Pledge

Rocket Pool is now fully online, and it has a rather stylish dashboard.

Lido released its node and validator parameter report for the fourth quarter of 2021.

MEV

If readers have been paying attention to the ecology, then you will realize that the combined MEV (Maximal Extracted Value) is becoming a hot topic.

Flashbots try to allow everyone to extract MEV democratically, rather than all of them being extracted by a few large staking pools, leading to the centralization of validators. To this end, they propose to introduce a network architecture that the client team can implement, and are coordinating to form a working group that includes a large number of stakeholders.

Part of this approach involves the “Proposer and Constructor Separation” (PBS) in block production. In short, the validator does not build blocks by himself, but is built by professional block builders (such as Flashbots), and then the validator proposes these blocks. The current approach is to achieve this outside of the consensus protocol, which involves many trust assumptions. In the future, there may be the option of adopting something similar in the agreement and ensuring that it is fair to everyone and accessible to everyone.

Flashbots’ MEV Roast 15-PBS on top of the Ethereum roadmap This conference was held today and covered all these topics. It’s a pity that I missed this meeting-I planned to watch the video to make up the lesson, but apart from some discussions on Twitter, I found nothing. ? If you find it later, you will be notified.

One major concern of this PBS mechanism is censorship resistance (especially when Flashbots have an effective monopoly on block production). Vitalik expressed some opinions on this topic.

route map

To celebrate the first anniversary of the beacon chain, Vitalik released an updated Ethereum (version 2.0) roadmap. ECN translated it into Chinese, although they did not translate each part of the title? (Translator’s Note: The Chinese version of the roadmap has been posted above, and while the four English titles are retained, ECN is also marked next to it. Chinese translation)

This new rollup-centric roadmap focuses on addressing data availability issues. Vitalik outlined a plan to gradually increase data availability by expanding calldata and rolling out sharding in stages. This will quickly increase the TPS (transactions per second) of the overall Ethereum ecosystem without having to wait until 1-2 years after the mass adoption of sharding.

If we want to increase the data traffic in the system, then at some point we may also want to start clearing this data. This is where EIP-4444 comes into play. Last week, Vitalik participated in an impromptu AMA on the expiration of historical data to discuss related topics. @lightclients posted a tweet to explain the background.

Paraphrase

Tim Beiko is really active everywhere this week. I have to talk about him again. He gave a speech on “Understanding the Transition from PoW to PoS” on Ethereum Cat Herders. Here is the slide.

Guillaume and Dankrad explained how to implement the actual implementation of Verkle trees in the client. Verkle trees are one of the steps to achieve stateless Ethereum.

Media and others

The most recent episodes of Bankless’s podcasts are related. They are still in the backlog of my pending playlist, but I know they are all great: (1) Darren Langley and Dave Rugendyke participated in an issue of “Using Rocket Pool to Decentralize Ethereum 2.0 Staking”, (2) Tim Beiko Participated in “Layer Zero”.

Coin Telegraph, “As the Eth2 merger approaches, Ethereum will enter a full-scale deflationary mode”:

The Ethereum community manager stated that the current focus of work is “completely focused on mergers.”

Chainsafe gave a series of lectures at CSCON1. It is difficult to track these videos now because they are not indexed. But pay attention to these live broadcasts:

  • “Merger and Roadmap for the Future” by Alex Stokes
  • “Future Ethereum Account” by Lightclients
  • Tim Beiko’s “Detailed Update of the Ethereum Roadmap”

Regular meeting

Implementer meeting

The 77th meeting was held on December 2.

  • Agenda
  • Conference video
  • My shorthand

Core Developer Conference

The 127th meeting was held on November 26.

  • Agenda
  • Conference video
  • Notes by Tim Beiko

Tim’s latest article, “Ethereum Core Developers Conference Update” has a great summary and is worth reading.

Upcoming Events

December 9, 2021, 20:00 UTC: post-merger MEV panel discussion

Other news

  • Lighthouse update #38
  • Potuz wrote an article decomposing the hasher mechanism of Prysm
  • Danny’s Finalized no. 32

finally

I prepared a birthday gift for the first anniversary of the creation of the Beacon Chain: I released a completely revised and updated Altair annotation specification. In this document, readers will receive strong reminders from me about what I plan to do in the next six months or even later. (My full-time job will not change: don’t be afraid, Teku is my first love!) Good luck!

Source | What’s New in Eth2

Author | Ben Edgington

Original link: https://consensuslayer.news/forward///https%3A%2F%2Fconsensuslayer.news%2Fnews%2F211203

Posted by:CoinYuppie,Reprinted with attribution to:https://coinyuppie.com/consensus-layer-progress-update-as-of-2021-12-3/
Coinyuppie is an open information publishing platform, all information provided is not related to the views and positions of coinyuppie, and does not constitute any investment and financial advice. Users are expected to carefully screen and prevent risks.

Like (0)
Donate Buy me a coffee Buy me a coffee
Previous 2021-12-06 10:48
Next 2021-12-06 10:53

Related articles