Greeting the second roll-out fast eth2 update.
tldr;
- Specification Release v0.9.0 — Tonkatsu This is to make sure that progress is continued.
- On-going work to refine the details of the Phase 1 revised proposal
- Quiet but purposeful customer-centric development eth1-> eth2 Infrastructure, optimizations and general hardening in production.
Tonkatsu Release
As Promised in the last Call eth2We move things forward in order to launch v0.9.0 Release Tonkatsu. This Release greatly simplifies Phase 0. The The goal is to get rid of any part. Phase There are 0 people who have opinions on this topic. Phase 1 to guarantee that Phase Regardless of what, there is no way that 0 progress can be halted. Work in progress: Modified fragmentation proposal.
Read The Release notes For more information, please visit
Phase 1 Redesign in Progress
As Mentioned in the last fast eth2 updateWe’re nearly certain to be moving in a more logical route. Phase 1. The New proposal for fragmentation Facilitates “cross links” For all fragments in each slots. This Communication between fragments is greatly simplified, which will lead to a better developer/user experience. Phase 2.
Prior Communication between fragments (approximate).
New fragment design proposal
To Support this proposal. To begin with, the total fragment count should be reduced to 1024, and then to 64. This is with the intent to increase the number of fragments over the course of time (10 year), as the standard resources for them increase. consumer laptops. The The main reasons why total fragments must be reduced are:
- Each An attestation fee is imposed by shard on the network and beacon chain at each slot, instead of every epoch.
- Each Committee should be of a minimum insurance Number of validators If Due to the high shard count, there may be too many committees in an epoch. There may not enough 32-ETH validators available to assign each committee.
