---
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;}
</style>

# What's New in Eth2 - 10 April 2021

 Ben Edgington (Eth2 at [ConsenSys](https://consensys.net/) — all views expressed are my own)

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

## Top picks

Easy decision this week: [The Eth 2.0 Merge](https://ethmerge.com/).

:::success
**Teku is hiring!**

If you are a Java dev who'd like to be a core dev then check out the [role description](https://consensys.net/open-roles/3040114/).

Feel free to drop me a line if you have questions or would just like to chat about the role: `[e-mail]` or ping me on [Twitter](https://twitter.com/benjaminion_xyz).

I can personally vouch for our wonderful team :grinning:
:::

## The Beacon Chain

There's been [a slashing](https://beaconcha.in/block/906882#attester-slashings)! After two entire months with no slashing events at all, there was a single, isolated slashing on April 6th. Unfortunately I don't have any further info on this one.

A [security advisory](https://github.com/supranational/blst/security/advisories/GHSA-x279-68rr-jp4p) was issued for the Blst cryptographic library, which I believe all four mainnet clients are using. It looks difficult to exploit, but all clients have now updated to a fixed version. There were also a few [other bug fixes](https://twitter.com/GuidoVranken/status/1377749057632927746). If you haven't updated your node recently, I recommend that you do so. (No release version of Teku used an affected version of Blst, but it's always good to keep up to date.)

There is a [new proposal](https://github.com/ethereum/eth2.0-specs/pull/2292) for fixing a potential [finality delay attack](https://github.com/ethereum/eth2.0-specs/pull/2292). We discuss this a little on the recent [devs' call](#Implementers): a coordinated fork would not be required to implement it, and we can decouple the roll-out from the Altair upgrade.

### Altair

Altair is the beacon chain upgrade due for mid-2021.

No huge updates from [last time](https://hackmd.io/@benjaminion/wnie2_210328#Altair), though an [alpha.3](https://github.com/ethereum/eth2.0-specs/releases/tag/v1.1.0-alpha.3) version of the spec is out. This is basically just a few fixes and clarifications. My [one-character](https://github.com/ethereum/eth2.0-specs/pull/2282/files) pull request made it in :tada: :joy:

Teams continue to plug away on implementation, with a planning goal of June or July for deployment.

### The Merge

The Merge is [the plan](https://github.com/ethereum/eth2.0-specs/tree/dev/specs/merge) to get Ethereum onto Proof of Stake as soon as possible. There is momentum among devs to get the Merge done [this year](https://twitter.com/drakefjustin/status/1379052831982956547). That is aspirational; a more realistic estimate might be Q1/2022.

Prysm [has joined](https://hackmd.io/@prysmaticlabs/prysm-catalyst-interop) the gang of clients that have demonstrated interoperability with the Eth1 Merge client, Catalyst. (Teku did this [last August](https://twitter.com/mkalinin2/status/1299038199591862274), and Lighthouse [last month](https://twitter.com/sigp_io/status/1374979655782989824)).

Mikhail Kalinin has written up [a detailed specification](https://hackmd.io/@n0ble/ethereum_consensus_upgrade_mainnet_perspective) of what needs to be done to current Eth1 Proof of Work clients to get them ready for the transition to Proof of Stake. It's really a limited set of changes, and I am hopeful that we will have several viable execution layer clients by the time the Merge is enacted.

Regular calls are being held to discuss the Merge. These are not live-streamed, but [agendas](https://github.com/ethereum/pm/issues/290), and [recordings](https://www.youtube.com/watch?v=b3hfgLa_GHw) are available.

As ever, the hardest thing about the whole effort is what to call stuff. Mikhail has nicely [summarised](https://hackmd.io/@n0ble/the-merge-terminology) hours of intense discussion in Telegram and Discord groups. In short, we are going for "Consensus layer" for the Beacon Chain side of things post-merge, and "Execution layer" for the EVM/Eth1 side of things post-merge. Lots more detail in [Mikhail's doc](https://hackmd.io/@n0ble/the-merge-terminology).

### Rayonism

[Rayonism](https://rayonism.io/) is a coordinated effort to build and demonstrate a merged, sharded devnet, with a stretch goal of putting the Optimism rollup on top of it all.

The effort is taking place under the umbrella of the month-long EthGlobal [Scaling Ethereum Hackathon](https://scaling.ethglobal.co/), with most if not all of the relevant Eth1 and Eth2 teams represented.

There was a [kick-off call](https://notes.ethereum.org/@protolambda/SyRnDjsHd) on April 7th, and a detailed [meta specification](https://notes.ethereum.org/@protolambda/rayonism) has been put together. To follow progress or get involved, you can join the [Rayonism Discord channel](https://discord.gg/B7YUqnKN9J).

Protolambda is hosting optional, informal "office hours" for participants via the Discord voice channel `#rayonism-calls` at the following times, and at the same times in subsequent weeks:

| PT (-7) | UTC | CET (+2) | AEST (+10) |
|---|---|---|---|
| 10:00 Mon | 17:00 Mon April 12 | 19:00 Mon | 03:00 Tue |
| 18:00 Wed | 01:00 Thu April 15 | 03:00 Thu | 11:00 Thu |
| 02:00 Fri | 09:00 Fri April 16 | 11:00 Fri | 19:00 Fri |

### Testnets

The Nimbus team wrote [a short thread](https://twitter.com/ethnimbus/status/1376497707263660034) nicely introducing the [Prater network](https://prater.beaconcha.in/). We are encouraging all test stakers on the Pyrmont network to migrate over to Prater in the coming weeks as we plan to use Pyrmont for some experiments and it could get a bit unstable. Here's the [Prater launchpad](https://prater.launchpad.ethereum.org/en/).

### Tooling

The deposit CLI has been [updated](https://github.com/ethereum/eth2.0-deposit-cli/releases/tag/v1.2.0) to support the new functionality that allows depositors to specify an Eth1 address for withdrawal rather than a BLS12-381 withdrawal key. This is a great usability simplification, and opens the way for properly trustless staking pools.

[Valid8r](https://github.com/pondron/valid8r), which is a kind of "linting system" for checking the configuration of your Beacon Chain staking set up, has had a [v1.0.0 release](https://github.com/pondron/valid8r/releases/tag/v1.0.0).

This is a potentially useful resource: Beaconcha.in's identification of [staking pools by Eth1 address](https://beaconcha.in/pools).

## The Great Explainers

[InsideTheSim](https://twitter.com/InsideTheSim) is [community-sourcing](https://twitter.com/InsideTheSim/status/1375922860703813639) an FAQ on [The Eth 2.0 Merge](https://ethmerge.com/). This already has a lot of quality content. Go and add some more!

Lots from Vitalik over the last couple of weeks. First, a braindump on [Proof of Stake vs Proof of Work](https://www.reddit.com/r/ethereum/comments/mf31ia/a_brain_dump_on_pos_vs_pow_arguments/), prompted by Justin Drake's [Bankless episode](https://www.youtube.com/watch?v=bWqhn1hXvVc). (I do recommend that episode&mdash;all two hours of it!&mdash;for some great not-too-technical insights into why Proof of Stake fundamentally provides better security than Proof of Work, among other things.)

Vitalik has also been posting some nice concise explainers of various Eth2 ideas and concepts to Reddit lately. Here's an idea about [shard block staggering for faster block times](https://www.reddit.com/r/ethereum/comments/mbksxt/shard_block_staggering_for_faster_block_times/) which he first suggested [on Ethresear.ch]( https://ethresear.ch/t/near-instant-transaction-confirmation-via-staggered-shard-block-production/5643?u=benjaminion) a couple of years ago. And there's one discussing [Single secret leader election protocols](https://www.reddit.com/r/ethereum/comments/m9j5cy/single_secret_leader_election_protocols/). Neither of these are yet in the protocol, but could make it into the roadmap at some point.

And something more substantial from Vitalik on [Why sharding is great](https://vitalik.ca/general/2021/04/07/sharding.html): demystifying the technical properties.

Protolambda has produced another of his [epic diagrams](https://github.com/protolambda/ethereum-scaling-diagram). Click on sections to expand. (The original and the best [is here](https://raw.githubusercontent.com/protolambda/beacon-schematic/master/beacon_chain.svg), though elements may be a little dated now, such as crosslinks.)

Pintail published an excellent deep dive into [staking rewards](https://github.com/pintail-xyz/validator_rewards/blob/main/validator_rewards.ipynb). If you want to know why some validators have loads of block proposals already, and some (like mine) very few, this is the place to look. Lakshman Sankar [added some comments](https://twitter.com/lakshmansankar/status/1380147158792380428), and linked to Pintail's simple [spreadsheet calculator](https://docs.google.com/spreadsheets/d/1RjOKfdaZzez6t5l6FbwHVIEITK1zBbTJDPhOsiosqmw/edit#gid=0) for rewards.

## Media and Stuff

Check out the progress of the Beacon Book at [Update 001](https://stateful.mirror.xyz/tNwN3gii-e1lBBK3RpgtG23kSry_J2GjeibxM8y3_9E). I have the pleasure of proof-reading this tomorrow, which I am looking forward to very much. There are contributions from 46 folk involved in delivering Ethereum&nbsp;2.0. It reminds me that we are doing something [important](https://twitter.com/benjaminion_xyz/status/1378321095544217604).

Continuing the theme of people-of-Eth2, Elias Simos of Bison Trails has published the fourth of his profiles: this one of [Jacek Sieka](https://bisontrails.co/eth2/jacek-sieka/) of Nimbus. I've enjoyed this series very much, if only for the different viewpoints each of the interviewees brought along. It's interesting that Jacek once worked on high-frequency trading; Adrian Sutton from the Teku team is also a HFT veteran.

And there's another terrific Eth2 update from Viktor Bunin, also of Bison Trails, [update 013](https://bisontrails.co/eth2/013/).

Danny Ryan, not of Bison Trails, published [Finalized no. 25](https://blog.ethereum.org/2021/04/02/finalized-no-25/) covering Rayonism, the Blst advisory, and a reminder about the open [Beacon Chain security+testing RfP](https://notes.ethereum.org/@lsankar/security-rfp).

Tim Beiko recently ceased being my colleague :cry:, and has moved over to the Ethereum Foundation :tada: where he wasted no time putting up an excellent defence of the [future of Ethereum](https://twitter.com/TimBeiko/status/1377354216558108673). Well worth a read through, and follow the links.

Coindesk's latest [Mapping out Eth2](https://www.coindesk.com/podcasts/mapping-out-eth-2-0) podcasts:
- [What Eth 2.0 Meant in 2014 and What It Means Today](https://www.coindesk.com/podcasts/mapping-out-eth-2-0/eth2-0-staking-long-term-market-value)
- [Education: The North Star of Navigating Ethereum](https://www.coindesk.com/podcasts/mapping-out-eth-2-0/staking-eth-2-0-young-developers) - we talk to Coogan Brennan about his excellent series of articles on setting up as a solo staker.

## Research

Elliptic curve gurus might like to take a look at Vitalik's [Request for cryptographic primitive](https://ethresear.ch/t/request-for-cryptographic-primitive-vector-commitment-for-elliptic-curve-points-with-algebraic-properties/9080): vector commitment for elliptic curve points with algebraic properties.

Also from Vitalik, a simplified proposal for [capping the number](https://ethresear.ch/t/simplified-active-validator-cap-and-rotation-proposal/9022?u=benjaminion) of validators active at any one time to, say, half a million. This is intended to maintain a high level of security, while not over-burdening nodes with having to process the activities of even more huge numbers of validators.

## Regular Calls

### Implementers

Call #61 took place on the 8th of April. There were technical problems getting the live stream up, but a recording was made and [uploaded](https://www.youtube.com/watch?v=XLB5HEWdZUE) after the meeting. You can't see who's there :sunglasses:

* [Agenda](https://github.com/ethereum/eth2.0-pm/issues/212)
* [Video](https://www.youtube.com/watch?v=XLB5HEWdZUE)
* My [quick notes](https://hackmd.io/@benjaminion/SkiD8Y3rd), and Alex Stokes's [Tweet thread](https://twitter.com/ralexstokes/status/1380209522447282176).

### The Merge

Call #1 took place on the 1st of April. The main goal was to run the proposed Merge specification past the Eth1 client maintainers and gather feedback. My impression is that people left the meeting quite positive about the state of play.

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

## Upcoming events

- April 20th, 2021 at 5pm PST: deadline for responses to the [Beacon chain security and testing RFP](https://notes.ethereum.org/@lsankar/security-rfp)
- April 16th - May 13th: [Scaling Ethereum](https://scaling.ethglobal.co/), including the [Rayonism](https://rayonism.io/) effort.

## In other news

I published some cheeky [performance comparisons](https://twitter.com/benjaminion_xyz/status/1377904793910448132) between Teku and the other clients. In truth, Teku's advantage is marginal, but I'm still proud of the team! [/u/torfbolt](https://www.reddit.com/user/torfbolt/) got similar results when comparing [client performance](https://www.reddit.com/r/ethstaker/comments/mo5580/client_performance_comparison_on_pyrmont_with_my/) in Rocketpool Beta 3.

## And finally...

Did I mention that [Teku is hiring](https://consensys.net/open-roles/3040114/)?

* * *

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