---
# System prepended metadata

title: What's New in Eth2 - 3&nbsp;December&nbsp;2021
tags: [newineth2]

---

---
tags: newineth2
description: The latest update on Ethereum 2.0 development
image: https://benjaminion.xyz/f/favicon-96x96.png
---

<style>
a {text-decoration: underline;}
a {color: #0000ee;}
a:visited {color: #551a8b;}
.ui-infobar {visibility: hidden; padding-top: 0;}
.community-button {visibility: hidden;}
.markdown-body {padding-top: 0;}
</style>

# What's New in Eth2 - 3&nbsp;December&nbsp;2021

![My avatar](https://benjaminion.xyz/f/ms-icon-144x144.png =32x32) Ben Edgington (Eth2 at [ConsenSys](https://consensys.net/) — all views expressed are my own)

Edition 83 at [eth2.news](https://eth2.news/)

:::warning
<center>
<p>⚠ Stakers, be sure to update your Eth1 nodes ASAP! ⚠</p>
<p>The <a hef="https://blog.ethereum.org/2021/11/10/arrow-glacier-announcement/">Arrow Glacier</a> upgrade takes place at block 13,773,000.
</center>
:::

Etherscan has a handy [countdown timer](https://etherscan.io/block/countdown/13773000). As I write, it's showing Thu Dec 09 2021 18:34:47 GMT+0000. If your Eth1 node is not up to date, you may miss block proposals.

## Top picks

If there is one treat you give yourself this week, make it Vitalik's updated [roadmap diagram](https://twitter.com/VitalikButerin/status/1466411377107558402).

## The Beacon Chain

The beacon chain passed its one-year anniversary on Wednesday. It's been a pretty epic year, and, to a very good approximation indeed, incident free.

I was planning to write an appreciation of the beacon chain's first year, but others have done the work already:
  - Anthony Sassano has a nice write-up in [The Daily Gwei](https://thedailygwei.substack.com/p/beacon-me-up-scotty-the-daily-gwei), and
  - Here are some [stats](https://old.reddit.com/r/ethstaker/comments/r6lx1v/1_year_review_of_the_beacon_chain/) from EthStaker.

And we're not only celebrating one year of the beacon chain, but also [Lodestar's first mainnet block](https://twitter.com/dapplion/status/1464033020680224777) :tada:

Not everybody is partying, unfortunately. There have been a couple of slashings of genesis validators in the last few days, namely [1859](https://beaconcha.in/validator/1859) and [12697](https://beaconcha.in/validator/12697). No further info, but it's rather sad to get slashed after a whole year of successful participation. In other slightly tragic news, Lefteris stumbled upon one of several validators that have been [offline since genesis](https://twitter.com/LefterisJP/status/1462725215046221829). Here's [another one](https://beaconcha.in/validator/13872).

### Beacon chain spec things

Spec [version 1.1.6](https://github.com/ethereum/consensus-specs/releases/tag/v1.1.6) is out. This contains a fix for a very hard to exploit bug in the fork choice, and the proposer score-boosting defence against [various attacks](https://hackmd.io/@benjaminion/wnie2_211105#Fork-choice-vulnerabilities). These changes are not consensus-critical, so don't require a hard fork to be deployed in clients.

If you have noticed large increases in bandwidth and/or CPU usage in your beacon node recently, then it's probably due to a spec change [that we are now reverting](https://github.com/ethereum/consensus-specs/issues/2183#issuecomment-981232838). This applies to all clients. You should hopefully see an improvement as the reversion gets deployed.

In other networking news, Danny has proposed a [revamp](https://github.com/ethereum/consensus-specs/issues/2749) of our attestation subnets now that we have some experience of running such a large p2p network.

Also from Danny, some ideas and proposals around how to implement infrastructure for [weak subjectivity sync](https://notes.ethereum.org/@djrtwo/ws-sync-in-practice) in practice.

## The Merge

Tim Beiko published [How The Merge Impacts Ethereum’s Application Layer](https://blog.ethereum.org/2021/11/29/how-the-merge-impacts-app-layer/) to much acclaim, though I prefer my own [suggested title](https://twitter.com/benjaminion_xyz/status/1462780261939257355) for it. There is a version in [Chinese](https://mirror.xyz/ethereumcn.eth/kFzA6fZKF-qIjAOvOkJT03WizNea0Bo2Gx6tUDamFsY).

The [second community call](https://github.com/ethereum/pm/issues/419) on this topic took place today. I haven't seen video or notes yet, but keep an eye on the [EF YouTube](https://www.youtube.com/c/EthereumFoundation/videos) and something might appear in due course.

For reference, here's the Merge [mainnet readiness tracker](https://github.com/ethereum/pm/blob/master/Merge/mainnet-readiness.md).

### Kintsugi

Weekly Merge devnets are going pretty well. We put them up; we break them. Here's [Barnabé behaving badly](https://twitter.com/barnabemonnot/status/1466834138401591311) on Merge devnet-2. (Good news is that this is one of the things that spec v1.1.6 will fix.)

The plan is to start devnet-3 next week, and, all being well, a more public longer-lived Merge testnet around the 14th of December, which will be the Kintsugi testnet. Here's the [tracker](https://notes.ethereum.org/@djrtwo/kintsugi-milestones) of clients' progress towards being able to stand up Kintsugi.

For lovers of detail, the following are the specific releases and PRs related to Kintsugi that I lifted from an internal ConsenSys presentation by Mikhail Kalinin (hope you don't mind, bro!):
 - Kintsugi [merge-devnet-2](https://beaconchain.merge-devnet-2.wenmerge.dev/) has recently started
 - [Kintsugi spec v3](https://hackmd.io/@n0ble/kintsugi-spec) has been released
    - Consensus layer [#2728](https://github.com/ethereum/consensus-specs/pull/2728)
    - Execution layer [#4463](https://github.com/ethereum/EIPs/pull/4463), [#4465](https://github.com/ethereum/EIPs/pull/4465), [#4466](https://github.com/ethereum/EIPs/pull/4466), [#4482](https://github.com/ethereum/EIPs/pull/4482), [#4487](https://github.com/ethereum/EIPs/pull/4487), [#4493](https://github.com/ethereum/EIPs/pull/4493)
    - Engine API [#130](https://github.com/ethereum/execution-apis/pull/130), [#132](https://github.com/ethereum/execution-apis/pull/132), [#133](https://github.com/ethereum/execution-apis/pull/133), [#134](https://github.com/ethereum/execution-apis/pull/134), [#135](https://github.com/ethereum/execution-apis/pull/135)
 - Merge testing call has happened
    - [Agenda](https://github.com/ethereum/pm/issues/422)
    - [Test plan]( https://hackmd.io/@n0ble/merge-test-plan)

As noted above, there was a [Merge testing call](https://www.youtube.com/watch?v=69IXGROswBM) last week. This prompted a flurry of activity from Marius of the Geth team who is rallying an army of volunteers to work on testing The Merge. Here are some pointers:
  - Marius's [Merge testing programme](https://hackmd.io/WKpg6SNzQbi1jVKNgrSgWg)
  - [call to action](https://twitter.com/vdWijden/status/1465277163276488708)
  - over [300 people involved](https://twitter.com/vdWijden/status/1465996965653659649)!
  - Marius's own [progress](https://twitter.com/vdWijden/status/1466049345069985797)

For the brave, here are some [instructions](https://hackmd.io/dFzKxB3ISWO8juUqPpJFfw) for joining devnet-2.

One of the main challenges for client teams right now is implementing "optimistic sync", which is a way to coordinate the consensus client and execution client when joining an existing network. There's a plan to specify the optimistic sync process formally. Meanwhile, here are [some notes](https://hackmd.io/Ic7VpkY3SkKGgYLg2p9pMg) on it.

## Staking

Rocket Pool is now [fully live](https://twitter.com/superphiz/status/1462578544622645248), and it has a pretty [funky dashboard](https://www.rp-metrics-dashboard.com/dashboard/MAINNET).

Lido has published its [Q4/21 report](https://drive.google.com/file/d/1M9bOFalecnJf_pcYoxO7fWN4P1IH8PZ0/view?usp=sharing) on node and validator metrics.

## MEV

If you've been paying attention, you'll be aware that maximal extracted value (MEV) post-Merge is becoming a big topic.

Flashbots is at the centre of trying to find ways to democratise access to MEV so that it is not all hoovered up by a few large staking pools, creating a massive centralising force for validators. To that end, they have suggested a [network architecture](https://ethresear.ch/t/mev-boost-merge-ready-flashbots-architecture/11177?u=benjaminion) that client teams can implement, and are coordinating a [working group](https://twitter.com/thegostep/status/1465732252915191826) with a chunk list of stakeholders.

Part of the approach involves "proposer, builder separation" (PBS) in block production. In short, rather than building blocks themselves, validators propose blocks that specialist block builders (like Flashbots) build. The current approach is to implement this outside the consensus protocol, which involves a lot of trust assumptions. In future, there may be options to adopt something like this in-protocol, and ensure that it is fair and accessible to all.

Flashbots' [MEV Roast 15 - PBS on Ethereum Roadmap](https://github.com/flashbots/pm/issues/98) was a session today covering all these topics. Unfortunately I missed it - I was planning to catch up via a recording, but I am not able to find one, despite some [discussion](https://twitter.com/thegostep/status/1466556109913690112) of it on Twitter :cry: Will let you know if something turns up later.

One big concern around such PBS schemes is censorship resistance (especially while Flashbots has an effective monopoly on block production). Here are [some thoughts from Vitalik](https://notes.ethereum.org/@vbuterin/pbs_censorship_resistance) on the topic.

## Roadmap stuff

For the beacon chainiversary, Vitalik produced an updated Ethereum (2.0) [roadmap diagram](https://twitter.com/VitalikButerin/status/1466411377107558402). Also available [in Chinese](https://twitter.com/EthereumCN/status/1466731320537612296), though they didn't attempt to translate the titles for each part :slightly_smiling_face:

The new roll-up centric roadmap is hungry for data. Vitalik has outlined a plan to [gradually increase data availability](https://notes.ethereum.org/@vbuterin/data_sharding_roadmap) via calldata expansion and staged sharding roll-out. This would increase total Ethereum ecosystem TPS sooner than waiting for the sharding big-bang in a year or two.

If we want to increase the amount of data flowing through the system, at some point we might want to start forgetting it too. This is where [EIP-4444](https://eips.ethereum.org/EIPS/eip-4444) comes in. There was asn impromptu [AMA on history expiry](https://www.reddit.com/r/ethereum/comments/qzvsfq/impromptu_technical_ama_on_history_expiry/) with Vitalik on this last week. And Lightclients did an [explainer](https://twitter.com/lightclients/status/1462576116359569411) of the background to it all.

## The Great Explainers

Tim Beiko is everywhere this week. Here he is again, with [Understanding the Transition to Proof of Stake](https://www.youtube.com/watch?v=aH3Le-3v320). There are [slides](https://drive.google.com/file/d/1tXMTQdq_cjkwtqmtH-mzSvhVmlhGN-Vf/view).

Guillaume and Dankrad explain how a practical implementation of [Verkle trees](https://blog.ethereum.org/2021/12/02/verkle-tree-structure/) might be implemented in clients. Verkle trees are one of the steps towards making Ethereum stateless.

## Media and stuff

A couple of recent Bankless episodes are relevant. They're still on my playlist backlog, but I know they will both be great: (1) [Decentralized Ethereum 2.0 Staking with Rocket Pool](http://podcast.banklesshq.com/decentralized-ethereum-20-staking-with-rocket-pool-darren-langley-dave-rugendyke) with Darren Langley and Dave Rugendyke, and (2) [Layer Zero with Tim Beiko](http://podcast.banklesshq.com/tim-beiko-layer-zero).

Coin Telegraph, [Ethereum in full deflation mode as Eth2 merge gets closer](https://cointelegraph.com/news/status-check-ethereum-in-full-deflation-mode-as-eth2-merge-gets-closer):

> Focus is now “exclusively on The Merge,” says Ethereum community manager".

Chainsafe had a bunch of talks at [CSCON1](https://cscon.chainsafe.io/). It's kind of hard to track down the [videos](https://www.youtube.com/c/ChainSafeSystems/videos) right now as they are not indexed. But look out for:
  - Alex Stokes on [The Merge and beyond](https://twitter.com/ChainSafeth/status/1466793784650477576)
  - Lightclients on [Ethereum accounts of the future](https://twitter.com/ChainSafeth/status/1466845872000487426)
  - And, it's him again, with [a detailed update on the Ethereum roadmap](https://twitter.com/ChainSafeth/status/1466098877568847874)

## Regular Calls

### Implementers

Call #77 took place on the 2nd of December.

*   [Agenda](https://github.com/ethereum/pm/issues/429)
*   [Video](https://youtu.be/1fIg_t6hZ8U?t=58)
*   My [quick notes](https://hackmd.io/@benjaminion/S1trJ8UFK).

### All core devs

Call #127 took place on the 26th of November

* [Agenda](https://github.com/ethereum/pm/issues/416)
* [Video](https://www.youtube.com/watch?v=js4HLK4MyQI)
* [Notes](https://twitter.com/TimBeiko/status/1464262630139334658) from Tim Beiko

Tim's latest [All Core Devs update](https://twitter.com/TimBeiko/status/1466468433130934275) is an excellent read and summary.

## Upcoming events

  - December 9, 2021, 20:00 UTC: [Post-Merge MEV Breakout Room](https://github.com/ethereum/pm/issues/423)

## In other news

 - Lighthouse [Update 38](https://lighthouse.sigmaprime.io/update-38.html)
 - [Crushing Prysm's hasher](https://hackmd.io/@potuz/BJyrx9DOF) by Potuz
 - Danny's [Finalized no. 32](https://blog.ethereum.org/2021/11/22/finalized-no-32/)

## And finally...

For my own birthday gift to the beacon chain, I published my fully revised and updated [Altair annotated specification](https://eth2book.info/altair/annotated-spec). If you pop over there, you'll get a [strong hint](https://eth2book.info/altair/preface#work-in-progress) as to what I'm planning to be working on for the next six months, and beyond. (Alongside the day job: never fear, Teku is my first love!). Wish me luck!

* * *

[![[Twitter]](https://benjaminion.xyz/newineth2/img/twitter.svg =40x40)](https://twitter.com/benjaminion_xyz) Follow me on [Twitter](https://twitter.com/benjaminion_xyz) to hear when the next edition is out 🙌.

[![[RSS]](https://benjaminion.xyz/newineth2/img/rss.svg =32x32)](https://benjaminion.xyz/newineth2/rss_feed.xml) We also have an [RSS feed](https://benjaminion.xyz/newineth2/rss_feed.xml).

[Advertising](https://hackmd.io/@benjaminion/eth2_news/https%3A%2F%2Fhackmd.io%2F%40benjaminion%2Fadvertising) on this newsletter.

[Give Feedback](https://docs.google.com/forms/d/e/1FAIpQLSfkESc4CmNfRGHHjWfNeF3ceLwrXDvynetda4sKfJFJ71Oabw/viewform).