eth2 fast update no. 13


Test nets, test nets, test nets!

tl; dr

Medal testnet

Following the excellent stability of Altona and based on conversations with eth2 customer teams, Medal – the next multi-client test network – will have a MIN_GENESIS_TIME of 1596546000 (or for those of you who don’t think in Unix time — August 4, 2020, 13:00 UTC)!

upload c6ac39ee6f5c0b87f0795c88ad9a8d87

This is an important step by Altona in the sense that Medalla is a test network built for and kept by the community The multi-client testnets before Medalla were considered “devnets”, run mainly by client teams and members of the EF (see the Altona section of my last post for a more complete explanation), but with the launch of this network, the stability and health of the chain will be almost entirely in the hands of the community (your hands ✋🤞🤟!).

Notice that MIN_GENESIS_TIME is the earliest the chain can start, but the chain will not start until the minimum validator count is also reached. To stay true to the mainnet type, Medalla will start with no less than 16,384 validators (524,288 ETH). In the event that minimum deposits (16,384 of them) are not met before 13:00 UTC on August 2nd (48 hours before min genesis), the chain will start after MIN_GENESIS_TIME. This is ok.

In sum, genesis will occur 48 hours after both conditions are met. We’ll all be on our toes, watching deposits, and when the genesis time is known, we’ll be buzzing about it 🎉

We will also release a version of the validator “Launchpad” for Medalla — an educational interface for validators to make deposits. More details on this are coming soon

We will have no less than four clients are fully functional at genesis — lighthouse, nimbus, prismand cover up. As usual, we strongly encourage client diversity to add strength and resilience to the network (see discussion of the many clients of eth2). Please don’t hesitate to check client docs, mess around with compilation and configuration, and drop by their discordant servers to ask questions 🙂

In addition to the four clients listed above, I fully expect lodestar to be on the web in some capacity at the start, and we might even have another surprise client join the mix.

Another exciting announcement: Medalla will have a special POAPs for those participating in the launch! Stay tuned for more details 🏅

Attacks beta 0 launch

Calling all white hats 1337 h4x0rz🍳‍👩!

Three attack networks were launched this week (beacon-attack-0, prysm-attack-0and teku-attack-0), each with a $5k prize for bringing it down (that is, interrupting finality for at least 16 continuous epochs).

These initial attack networks are purposefully simple (1 client each) and small (4 nodes each) so they should should be easy enough to take off. Look at the READ ME for more details and notes on getting started, and join the Eth R&D #attack networks channel for discussion and advice.

Following the beta 0 raid nets, we will increase the size and complexity of raid nets and add more complex challenges with bigger prizes.

Oh! and an honorable mention 🏆 goes to Jonny (TXRX) for a successful take down beacon-attack-0the discovery of. Although this didn’t crash the end of the testnet, he discovered a critical bug! Thanks Age (Sigma Prime) for the quick fix.

eth1+eth2 fusion progress update

I want to give a quick update on the progress of eth1+eth2 merging and give a huge shout out to Mikhail (TXRX) and Guillaume (geth) for their great work.

The current vision of Ethereum’s future is for the current chain to be integrated into the new eth2 consensus as a chip. This is the marriage of eth2 clients (consensus) with eth1 clients (highly optimized user layer) into a single system. The high level about the customer relationship can be found here; more detailed scope of the merger discussed by Mikhail is here; and a discussion of the architecture of a get-based eth1 engine (called Catalyst) by Guillaume is here.

Since the above posts were written, Mikhail and Guillaume have been busy making these concepts a reality. Guillaume’s Catalyst — a version of geth that defers its consent to RPC calls (ie eth2 client) — is built and ready to run; and Mikhail’s Phase 1 implementation runs fully sharded eth2 simulations with selected shards delaying block production and validity calls to a local, stubbed eth1 engine.

upload 2443f829516287e2c9ffcc2d96de2d3d

The next step is to connect these two pieces together for the ultimate eth1+eth2 simulation!

Again, great job Mikhail and Guillaume. I’m incredibly excited about this and the fact that it’s happening in parallel with the upcoming launch of the beacon chain 🚀



Please enter your comment!
Please enter your name here