Testnets, testnets, testnets!
tl;dr
Medalla testnet
Following the wonderful stability of Altona and primarily based on conversations with eth2 consumer groups, Medalla – the following multi-client testnet – may have a MIN_GENESIS_TIME of 1596546000 (or for these of you that do not suppose in unix time — August 4th, 2020, 1pm UTC)!
This can be a main step up from Altona within the sense that Medalla is a testnet constructed for and maintained by the neighborhood. The multi-client testnets previous to Medalla have been thought of “devnets”, run primarily by consumer groups and members of the EF (see the Altona part of my final publish for a extra full clarification), however with the launch of this community, the soundness and well being of the chain will probably be virtually solely locally’s arms (your arms ✋🤞🤟!).
Notice that MIN_GENESIS_TIME is the earliest the chain can begin, however the chain will not begin till the minimal validator rely has additionally been reached. With a view to keep devoted to the mainnet spec, Medalla will begin with no fewer than 16,384 validators (524,288 ETH). Within the occasion that minimal deposits (16,384 of them) aren’t met by 1pm UTC on August 2nd (48 hours previous to min genesis), the chain will begin later than MIN_GENESIS_TIME. That is okay.
In sum, genesis will occur 48 hours after each situations are met. We’ll all be on our toes, watching deposits, and when the genesis time is thought, we are going to make a bunch of noise about it 🎉
We’ll even be releasing a model of the validator “Launchpad” for Medalla — an academic interface for validators to make deposits. Extra particulars on this are imminent
We’ll haven’t any fewer than 4 purchasers absolutely working at genesis — lighthouse, nimbus, prysm, and teku. As regular, we strongly encourage consumer range so as to add power and resilience to the community (see dialogue of eth2’s many purchasers). Please do not hesitate to take a look at consumer docs, mess with compilation and configuration, and drop by their discord servers to ask questions 🙂
Along with the 4 purchasers listed above, I absolutely anticipate lodestar to be on net in some capability at first, and we would even have one other shock consumer be a part of the combination.
One other thrilling announcement: Medalla may have particular POAPs for many who take part within the launch! Keep tuned for extra particulars 🏅
Attacknets beta-0 launch
Calling all whitehat 1337 h4x0rz👩🍳!
Three attacknets have been launched this week (lighthouse-attack-0, prysm-attack-0, and teku-attack-0), every with a $5k bounty to carry it down (that’s, disrupt finality for at the least 16 steady epochs).
These preliminary attacknets are purposefully easy (1 consumer every) and small (4 nodes every) so that they ought to be fairly simple to take down. Try the README for extra particulars and notes on getting began, and be a part of the Eth R&D #attacknets channel for dicussion and suggestions.
Following the beta-0 attacknets, we’ll scale up the scale and complexity of attacknets in addition to add extra advanced challenges with bigger bounties.
Oh! and an honorable point out 🏆 goes out to Jonny (TXRX) for managing to take down lighthouse-attack-0‘s discovery. Though this didn’t crash the finality of the testnet, he found a essential bug! Thanks Age (Sigma Prime) for the fast repair.
eth1+eth2 merger progress replace
I wish to give a fast replace on the eth1+eth2 merger progress and to present a enormous shout-out to Mikhail (TXRX) and Guillaume (geth) for his or her wonderful work.
The present imaginative and prescient of the way forward for Ethereum is for the present chain to be built-in into the brand new eth2 consensus as a shard. That is the wedding of eth2 purchasers (consensus) with eth1 purchasers (extremely optimized consumer layer) right into a single system. The excessive degree on the consumer relationship could be discovered right here; a extra detailed scope of the merger mentioned by Mikhail is right here; and a dialogue of the structure of a geth primarily based eth1-engine (referred to as Catalyst) by Guillaume is right here.
Because the above posts have been written, Mikhail and Guillaume have been busy turning these ideas into actuality. Guillaume’s Catalyst — a model of geth which defers its consensus to RPC calls (i.e. an eth2 consumer) — is constructed and able to go; and Mikhail’s Part 1 implementation is working absolutely sharded eth2 simulations with choose shards deferring block manufacturing and validity calls to an area, stubbed eth1-engine.
The following step is to plug these two items collectively for an end-to-end eth1+eth2 simulation!
Once more, nice work Mikhail and Guillaume. I am extremely enthusiastic about this and the truth that it is occurring in parallel to the approaching launch of the beacon chain 🚀