Ethereum 2.0 Specifications

Go to file

protolambda d28cac0e8f clean up test phase 1 testgen references		2021-03-29 15:38:43 +02:00
.circleci	Bump `py_ecc` and `milagro_bls_binding` (#2169 )	2021-01-05 21:00:52 +08:00
configs	rename to custody game	2021-03-27 01:58:39 +01:00
solidity_deposit_contract	Update solidity_deposit_contract/README.md	2020-09-14 15:10:18 +02:00
specs	rename to custody game	2021-03-27 01:58:39 +01:00
ssz	Minor update ToC	2020-12-07 11:10:19 +08:00
tests	clean up test phase 1 testgen references	2021-03-29 15:38:43 +02:00
.codespell-whitelist	Set codespell<3.0.0,>=2.0.0 version and add `ether` to whitelist	2020-12-07 11:08:54 +08:00
.gitattributes	Update the docs and remove unused code	2020-08-18 00:58:08 +08:00
.gitignore	LIGHTCLIENT_PATCH/HF1 -> ALTAIR	2021-03-11 21:32:00 +08:00
.gitmodules	WIP: add solidity deposit contract CI workflow	2020-08-17 23:37:33 +08:00
LICENSE	CC0 1.0 Universal for repo	2019-03-12 11:59:08 +00:00
Makefile	clean up more phase1 test references	2021-03-27 00:14:32 +01:00
README.md	rename to custody game	2021-03-27 01:58:39 +01:00
linter.ini	Set linter configs in `linter.ini`	2020-06-18 14:36:14 +08:00
setup.py	disable phase1 pyspec build	2021-03-26 22:37:32 +01:00

README.md

Ethereum 2.0 Specifications

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.

Specs

Core specifications for Eth2 clients be found in specs. These are divided into features. Features are researched and developed in parallel, and then consolidated into sequential upgrades when ready.

The current features are:

Phase 0

Altair

Merge

The merge is still actively in R&D. The specifications outline a general direction for engineering work, while the details are in review and may change.

Background material:
- An ethresear.ch post describing the basic mechanism
- ethereum.org high-level description of the merge here
Specifications:

Sharding

Sharding follows the merge, and is divided into three parts:

Sharding base functionality - In early engineering phase
- Beacon Chain changes
- P2P Network changes
Custody Game - Ready, dependent on sharding
- Custody Game
- Validator custody work
Data Availability Sampling - In active R&D
- Technical details here.
- Core types and functions
- P2P Networking
- Fork Choice
- Sampling process

Accompanying documents can be found in specs and include:

Additional specifications for client implementers

Additional specifications and standards outside of requisite client functionality can be found in the following repos:

Design goals

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/validate O(1) shards (including any system level validation such as the beacon chain)

Useful external resources

For spec contributors

Documentation on the different components used during spec writing can be found here: