To learn more about sharding and Ethereum 2.0 (Serenity), see the sharding FAQ and the research compendium.
This repository hosts the current Eth2 specifications. Discussions about design rationale and proposed changes can be brought up and discussed as issues. Solidified, agreed-upon changes to the spec can be made through pull requests.
Core specifications for Eth2 clients be found in specs. These are divided into phases. Each subsequent phase depends upon the prior. The current phases specified are:
The sharding spec is still actively in R&D; see the most recent available pull request here and some technical details here.
The merge is still actively in R&D; see an ethresear.ch post describing the proposed basic mechanism here and the section of ethereum.org describing the merge at a high level here.
Accompanying documents can be found in specs and include:
Additional specifications and standards outside of requisite client functionality can be found in the following repos:
The following are the broad design goals for Ethereum 2.0:
- to minimize complexity, even at the cost of some losses in efficiency
- to remain live through major network partitions and when very large portions of nodes go offline
- to select all components such that they are either quantum secure or can be easily swapped out for quantum secure counterparts when available
- to utilize crypto and design techniques that allow for a large participation of validators in total and per unit time
- to allow for a typical consumer laptop with
O(C)resources to process/validateO(1)shards (including any system level validation such as the beacon chain)
Documentation on the different components used during spec writing can be found here: