---
# System prepended metadata

title: What's New in Eth2 - 3&nbsp;June&nbsp;2022
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;June&nbsp;2022

![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 94 at [eth2.news](https://eth2.news/)

## Top picks

This one is bigger than pick of the week - it's a decent candidate for pick of the year: Jon Charbonneau of Delphi Digital with [The Hitchhiker's Guide to Ethereum](https://members.delphidigital.io/reports/the-hitchhikers-guide-to-ethereum/).

Jon's article is a deep dive into the future of Ethereum. It's a solid read (an hour or so), and information dense, but entertainingly written, insightful, and well worth setting aside the time for. Vitalik [likes it](https://twitter.com/VitalikButerin/status/1529987598743007237)!

Two other ways you can ingest the alpha:

  - Bienvenido Rodriguez made a [tweet-form digest](https://twitter.com/0xb17z/status/1532039402234314752). Only 58 tweets long!
  - Jon himself did [a livestream walk through](https://www.youtube.com/watch?v=xuLyZaty9iI) with Bankless.

## The Beacon Chain

### The reorg

We had a flurry of excitement last week. On May the 25th the beacon chain underwent a [seven block reorg](https://twitter.com/ethnimbus/status/1529411195966472193) (re-organisation).

<div style="text-align:center;margin-bottom:2ex;">
    
  <img width="368" height="383" alt="Beacon chain explorer showing seven forked blocks." src="https://benjaminion.xyz/images/220525_reorg.jpg"/>

</div>

A reorg occurs when a block proposer ignores the most recent block or blocks and builds instead on an older block such as the parent or earlier ancestor of the most recent block. The intermediate blocks might then get kicked out of the chain so it's as if they were never produced. Reorgs happen naturally in proof of work chains, though are rarely more than 2-3 blocks deep.

The reorg can be visualised like this, with the beacon chain blocks numbered according to the slot they appeared in:

```graphviz
digraph{
rankdir="RL"
node[shape=box]
3887074 -> 3887073
3887075 -> 3887074 [style=invis]
3887081 -> 3887080 -> 3887079 -> 3887078 -> 3887077 -> 3887076 -> 3887075 -> 3887073
3887082 -> 3887081 [style=invis]
3887082 -> 3887074
}
```

Block 3887082 should have been built on 3887081, but the proposer went back eight generations to build instead on 3887074. The seven intermediate blocks were kicked out of the chain as a result.

This caused a certain amount of [concern](https://twitter.com/koeppelmann/status/1529458000011972610) on Twitter.

#### Analysis

I initially had a long explanation here, but Barnabé Monnot has [done it much better](https://barnabe.substack.com/p/pos-ethereum-reorg).

His article explains what happened, what the root causes were, and why we don't need to worry about it in future.

In short, we have been doing a gradual roll-out of a fix to the fork choice rule when we should probably have coordinated the fix more tightly. When the number of fixed nodes and unfixed nodes reached around half of each it compounded with another issue (also being fixed) leading to the reorg.

Ultimately, the only way to eliminate reorgs completely is to move to [single slot finality](https://notes.ethereum.org/@vbuterin/single_slot_finality). Our current beacon chain achieves finality only after 64 slots minimum, so reorgs will always be a possibility, although deep reorgs should be very rare unless the network comes under a powerful attack.

Others also wrote useful summaries: [@terencechain](https://twitter.com/terencechain/status/1529566839033933824), [@gakonst](https://twitter.com/gakonst/status/1530286751188672513), [@koeppelmann](https://twitter.com/koeppelmann/status/1529832225272897536).

### Deposit queue processing

In other beacon chain news, we all know that the activation of new validators is rate-limited to a few per epoch. It's not so well known that [this rate increases](https://eth2book.info/altair/part3/helper/accessors/#get_validator_churn_limit) as the validator set grows.

I only mention this as we hit [another milestone](https://www.reddit.com/r/ethfinance/comments/v042cb/daily_general_discussion_may_29_2022/iae9hqa/) last week, when the per-epoch limit increased from 5 to 6 as we blasted through 393,216 active validators. That equates to up to 1350 new validators per day being activated.

## Testing The Merge

Spec version [v1.2.0-rc.1](https://github.com/ethereum/consensus-specs/releases/tag/v1.2.0-rc.1) is a spec release candidate for The Merge. This is a big milestone! We will be putting this one through its paces through the upcoming testnet Merges.

### Ropsten beacon chain

We've been having some fun and games with the Ropsten testnet Merge. Having set a terminal total difficulty (TTD - the point at which the Merge event should happen), a [mischievous](https://twitter.com/TimBeiko/status/1529922974538534913) miner pushed up the Ropsten hash rate [by 100x](https://twitter.com/preston_vanloon/status/1529845340601565184), hitting the original TTD around two weeks early - before even the Ropsten beacon chain had been deployed, which is a problem. You can't Merge with something that isn't there.

[Tim Beiko](https://notes.ethereum.org/@timbeiko/ropsten-ttd-override) and [@functi0nZer0](https://twitter.com/functi0nZer0/status/1529954510810013703) have provided detailed write-ups of the issue.

On reflection, we were a little naive in assuming that something like this wouldn't happen. It's not a big deal -- changing the hash rate on mainnet like this is totally unfeasible -- but is a nuisance for planning.

As a quick response we [abandoned](https://twitter.com/vdWijden/status/1529895417881800714) the old TTD and made a [revised plan](https://twitter.com/TimBeiko/status/1530269946319474689) on the All Core Devs call.

Current status is that the Ropsten beacon chain is [now up](https://twitter.com/parithosh_j/status/1531298447797760000), it has undergone the [Bellatrix fork](https://twitter.com/terencechain/status/1532515981762867201) and we're all set with a revised TTD, still targeting the 8th of June for the Merge event.

If you are running a Ropsten node, you need to look out for the new TTD value ([update](https://blog.ethereum.org/2022/06/03/ropsten-merge-ttd/), it's `50000000000000000`) and use that to manually override the TTD setting in both your execution and consensus clients.

Separately, there have been delays processing validator deposits onto the beacon chain due to some [disagreement](https://hackmd.io/@benjaminion/BkmzqV8uq#Ropsten-deposit-tracking-issues) among clients as to details of the Eth1 voting process. These seem to be resolved now and new validators are becoming active on [the chain](https://ropsten.beaconcha.in/).

Here's the Ethereum Foundation's [announcement](https://blog.ethereum.org/2022/05/30/ropsten-merge-announcement/) of the Ropsten testnet Merge. Here's a guide for [how to run a node on Ropsten](https://notes.ethereum.org/@launchpad/ropsten). And here's Rémy and Yorick from EthStaker demonstrating [how to setup a Ropsten node with eth-docker](https://www.youtube.com/watch?v=LYiDkwLSDx4), with a further non-Docker [guide](https://github.com/remyroy/ethstaker/blob/main/merge-ropsten.md) from Rémy also available.

Remember that Ropsten will not be maintained for long post-Merge. Goerli and Sepolia will be your long-lived testnets.

### Mainnet shadow fork 6

Mainnet shadow forks have now become quite routine, passing almost unnoticed. MSF6 took place this week, and went smoothly, if not quite perfectly. You can keep tabs on progress with the [Shadow Fork Tracker](https://notes.ethereum.org/PhbNw_cGSQ-VKqzGl4bPcg?view).

### Other `#TestingTheMerge` news

The Kiln testnet is now [processing more transactions than mainnet](https://twitter.com/parithosh_j/status/1531639706563268608)!

Tim Beiko [shared some thoughts](https://twitter.com/TimBeiko/status/1528866058022494208) on Testing the Merge for users of Ethereum, the application layer. Don't sleep on this, all you application devs.

## Beyond the Merge

Momentum is gathering for implementing [EIP-4844](https://www.eip4844.com/) (proto-danksharding) as soon as possible after the Merge. This is a step towards a full data availability solution and will increase the amount of cheap data available to rollups.

A big boost to this effort comes from a recently identified [optimisation](https://github.com/ethereum/EIPs/pull/5088) that dramatically reduces the amount of work needed to validate data blob transactions.

## Staking

In his wonderfully named article, [The Risks of LSD](https://notes.ethereum.org/@djrtwo/risks-of-lsd), Danny Ryan enumerates the dangers associated with liquid staking derivatives. There's some useful discussion in the associated [Twitter thread](https://twitter.com/dannyryan/status/1531383030786314240). Remember, kids, centralisation is a drug and can lead to nasty addictions.

As they promised, Lido has instigated a thread on their governance forum to discuss whether they should [limit their percentage of total stake](https://research.lido.fi/t/should-lido-on-ethereum-be-limited-to-some-fixed-of-stake/2225). Discussion is lively and lengthy.

By contrast, Justin Drake has made an interesting [research proposal](https://ethresear.ch/t/liquid-solo-validating/12779?u=benjaminion) describing a way to implement a non-centralised liquid staking derivative. It would be accessible to solo-stakers, but is reliant on hardware enclave technology such as Intel's SGX.

## The Great Explainers

Beacon node checkpoint sync -- as pioneered by Teku -- is an immense win for user experience. But how can you trust the initial state that you download? Do you need blind faith in Infura? Adrian Sutton discusses the issues in [Checkpoint Sync Safety](https://www.symphonious.net/2022/05/21/checkpoint-sync-safety/).

Still wrestling with Danksharding? @The_ReadingApe [took notes on](https://twitter.com/The_ReadingApe/status/1531666573915672576) the recent Bankless episode [Dive into Danksharding](https://www.youtube.com/watch?v=N5p0TB77flM) with Vitalik, Dankrad, and Protolambda.

My wonderful (but soon to be ex) colleague Sajida Zouarhi recorded a PEEPanEIP session on Hyperledger Besu and The Merge with the Ethereum Cat Herders. Seems like the video is not yet up -- look out for it [here](https://www.youtube.com/channel/UCD9iiIwTRtLDYcEWONs2Q3A/videos) -- but Sajida's [slides](https://docs.google.com/presentation/d/1d1-2x1sWUkJz1Qx6gyzgr4K4ZJ5Y3HMms8sbOrD_Z10/edit#slide=id.g12d423b4a7a_0_179) are available.

## Media and stuff

For [Part 2](https://www.youtube.com/watch?v=8UPFwKyaQOE) of Uncommon Core's Merge podcast, Hasu, Danny and Tim were joined by Stephane Gosselin of Flashbots. This discussion was simply a pleasure to listen to. A great conversation between a group of knowledgeable, thoughtful people. Hasu is an excellent host. In this part they covered Lido, and MEV post-Merge. [Part 1](https://www.youtube.com/watch?v=zvODqTUAPN0) in case you missed it.

The video of the Bankless [Verge of the Merge](https://vimeo.com/713930942) panel that caused such [excitement](https://hackmd.io/@benjaminion/wnie2_220520#WenMerge) a couple of weeks ago is up. Separately, DefiDad did a short interview [with Preston Van Loon](https://www.youtube.com/watch?v=MrrDt9_06hc) at Permissionless. It's good. Love Preston.

## Research

Some new work on [validator anonymity](https://ethresear.ch/t/ethereum-consensus-layer-validator-anonymity-using-dandelion-and-rln-conclusion/12698?u=benjaminion). Unfortunately, it looks infeasible in its current form given the beacon chain's timing constraints. But it's good to see people continuing to attack this important problem.

Mário Havel is [Predicting TTD on Ethereum](https://ethresear.ch/t/predicting-ttd-on-ethereum/12742?u=benjaminion). This is going to be useful as we close in on The Merge, and includes a prediction [tool](https://github.com/taxmeifyoucan/predict_ttd/).

Dmitry Khovratovich [analysed](https://ethresear.ch/t/analysis-of-swap-or-not-ssle-proposal/12700?u=benjaminion) Vitalik's idea of applying the [swap-or-not shuffle](https://ethresear.ch/t/simplified-ssle/12315?u=benjaminion) to single secret leader election and found it wanting.

## Regular Calls

### All Core Devs

*   [Agenda](https://github.com/ethereum/pm/issues/528)
*   [Video](https://www.youtube.com/watch?v=5mMd-XHAv2Q)
*   Notes from [Tim Beiko](https://twitter.com/TimBeiko/status/1530265096156434432) and [Christine Kim](https://twitter.com/christine_dkim/status/1530351001051377664).

First, how to handle setting the Ropsten TTD for its Merge, give that difficulty is very easy to game on Ropsten.

#### Wen Merge?

Following that, we engaged in some initial skirmishes in the "Wen Merge?" battle. The Nethermind team is very keen to push back the Ethereum difficulty bomb by 3-4 months; others want to keep the pressure on.
               
For what it's worth, my view is as follows. Things only get done in a distributed development environment like ours when there is a collective sense of urgency - this is my observation over the years. For now the impending block time explosion due to the bomb provides that sense of urgency. If we delay the bomb, then we need to find our sense of urgency elsewhere, because if we don't we'll still be talking about the Merge next year. I regard every extra day we remain on proof of work as a scandal.

However, I don't really care if that sense of urgency comes from the bomb or from somewhere else. If we do delay the bomb, then I would argue strongly for simultaneously announcing a target date for the Merge to act as a substitute forcing function.

Assuming that the Ropsten Merge goes well next week :crossed_fingers: then this will be the main topic for discussion on the June 10th ACD call.

Here's the latest difficulty bomb [tracker](https://ethresear.ch/t/blocks-per-week-as-an-indicator-of-the-difficulty-bomb/12120/28?u=benjaminion) for reference.

### PoS Implementers

Call #88 took place on the 2nd of June.

*   [Agenda](https://github.com/ethereum/pm/issues/536)
*   [Video](https://youtu.be/JeWOqtQS-KE) - though it's currently been taken down "for violating YouTube's policy on spam, deceptive practices, and scams" :man-shrugging: (Update: the recording is now available [here](https://www.youtube.com/watch?v=4oI48BEijVw).)
*   My [notes](https://hackmd.io/@benjaminion/BkmzqV8uq).

No big news. Mostly updates on the testing that's going on (shadow for 6, the Ropsten deposit queue issue, the Ropsten TTD), and planning for the other testnet Merges (Goerli and Sepolia). The Nimbus team is doing some serious work on the light client spec.

Christine Kim has done a thorough [combined write-up](https://docsend.com/view/u4rb7vd5h35jtd4b) of both of these calls.

### Merge Community Call

Merge community call #4 took place today, the 3rd of June. Haven't had a chance to see it yet.

 - [Agenda](https://github.com/ethereum/pm/issues/532)
 - [Video](https://www.youtube.com/watch?v=qG-A5i6x6N8).

## In other news

  - Stereum [Under The Surface #008](https://stereum.net/under-the-surface-008/). The first Beta of v2.0 of Stereum's node installer is available.
  - Lido [Weekly Digest](https://twitter.com/LidoFinance/status/1532768980062154753): May 27 - June 03, 2022.
  - Jacek has made [full raw historical data](https://twitter.com/jcksie/status/1528986983900631040) of the beacon chain available in Nimbus's era file format. [The data itself](https://beacon.tennisbowling.com/eras/).
  - All the Big Beasts are coordinating around an [Ethereum Merge community call series](https://www.reddit.com/r/ethstaker/comments/v4631j/ethereum_merge_community_call_series/), covering the Ropsten and other testnet Merges, the pre-Merge upgrades, and of course the Event itself.

## And finally...

A reminder that Superphiz and I sometimes get together to [talk through the Eth2 news](https://www.youtube.com/watch?v=SS2Un8Bs044&list=PLOB9GGXGcc30i4lARcf9xSN3SvgaUf0O8&index=7). It is pretty much the highlight of my week. I love Phiz's insights and passion. We'll likely do a walk through of this edition on Monday, so look out for that.

* * *

[![[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).