eth2 quick update number 13

Testnet, testnet, testnet!

tl;dr

Medal Testnet

Following Altona’s outstanding stability and based on conversations with the eth2 client team, medal – The next multi-client testnet is – MIN_GENESIS_TIME ~ Of 1596546000 (Or for those of you who don’t think in Unix time – August 4, 2020, 1:00 PM (UTC))!

This is a big improvement over Altona in that Medalla is a testnet. made for and maintained by community. Prior to Medalla, the multi-client testnet was considered a “devnet” run primarily by the client team and EF members (see: Altona section of my last post for a more complete explanation), but once this network is launched, the stability and health of the chain will be almost entirely in the hands of the community (your hands ✋🤞🤟!).

please refer to this MIN_GENESIS_TIME This is the fastest chain ~can do However, the chain will not start until the minimum number of validators is reached. To stay true to mainnet specifications, Medalla will launch with a minimum of 16,384 validators (524,288 ETH). If the minimum deposit amount (16,384) is not met by 1:00 PM UTC on August 2 (minimum 48 hours before creation), the chain will start later than the following date. MIN_GENESIS_TIME. this is great.

In summary, genesis occurs 48 hours after both conditions are met. We will all be nervously watching our deposits and making a fuss about it once the creation time is known 🎉

We will also be releasing a validator “Launchpad” version for Medalla, an educational interface for validators to deposit. More details on this will be announced soon.

We will not be less than yes A client that runs completely from scratch – Lighthouse, cloud, prismand ocean. As always, we strongly encourage diversity in our clients to add strength and resilience to our network (see: Discussion of many clients of eth2). Don’t hesitate to check out the client documentation, mess around with compilation and configuration, and stop by our discord server to ask questions 🙂

In addition to the four clients listed above, I lodestar At first, you will have some access to the network, and other surprise customers may join you.

Another interesting announcement: Medalla has a special POAP Those who participated in the launch! Stay tuned for more details 🏅

attack net beta-0 start

Call all white hackers 1337 h4x0rz👩‍🍳!

three attack net Released this week (lighthouse-attack-0, Prism-Attack-0and teku-attack-0), each offering a bounty of $5,000 to defeat them (i.e. disrupt their finality for at least 16 consecutive epochs).

These initial attack nets are intentionally simple (1 client each) and small (4 nodes each), so must You can take it down pretty easily. Please confirm Read on Get more details and notes on getting started and Ethereum research and development #attack channel For discussion and tips.

next beta-0 For attack nets, this will not only expand the size and complexity of attack nets, but also add more complex challenges with larger bounties.

oh! and honorable mention 🏆 It goes to Jonny (TXRX) to manage the takedown. lighthouse-attack-0‘s discovery. Although this did not crash the finality of the testnet, he discovered a critical bug! Thanks to Age (Sigma Prime) for the quick fix.

eth1+eth2 merger progress update

We would like to quickly inform you of the progress of the eth1+eth2 merger. giant Thanks to Mikhail (TXRX) and Guillaume (geth) for their excellent work.

The current vision for the future of Ethereum is for the current chain to be integrated into the new eth2 consensus as shards. It combines an eth2 client (consensus) and an eth1 client (a highly optimized user layer) into a single system. You will find a high level of customer relations here; Here is a more detailed scope of the merger discussed by Mikhail: here; A discussion of Guillaume’s geth-based eth1 engine (called Catalyst) architecture follows: here.

Since the above post was written, Mikhail and Guillaume have been busy turning these concepts into reality. Guillaume’s Catalyst, a version of geth that defers consensus on RPC calls (e.g. eth2 clients), is built and ready to use. Mikhail’s phase 1 implementation is running a fully sharded eth2 simulation using select shards that defer block creation and validation calls to a local stubbed eth1 engine.

The next step is to connect these two parts together for an end-to-end eth1+eth2 simulation!

Once again, great work by Mikhail and Guillaume. I’m very excited about this and the fact that it’s happening to coincide with the upcoming launch of the beacon chain 🚀