Ethereum 2.0 Specifications

Go to file

Danny Ryan 9b21c0db93 add note aboutgenesis attestations		2019-11-07 12:06:23 -07:00
.circleci	make sure new config loader change is working	2019-07-27 00:28:47 +02:00
configs	further test bounce attack	2019-11-05 10:58:45 -07:00
deposit_contract	Deposit contract fixes (#1362 )	2019-09-03 18:59:18 +01:00
scripts	lint	2019-10-23 17:29:53 +09:00
specs	add note aboutgenesis attestations	2019-11-07 12:06:23 -07:00
test_generators	[reopen] Eth2 shorthand standardized (#1452 )	2019-10-28 15:53:10 +08:00
test_libs	Merge branch 'bounce-attack' into decoy-flip-flop	2019-11-06 17:20:59 -07:00
.codespell-whitelist	Add codespell whitelist	2019-08-19 13:06:21 +02:00
.gitignore	add mypy cache to gitignore	2019-06-18 21:54:00 +02:00
LICENSE	CC0 1.0 Universal for repo	2019-03-12 11:59:08 +00:00
Makefile	Merge branch 'dev' into vbuterin-patch-13	2019-08-24 02:37:19 +08:00
README.md	[reopen] Eth2 shorthand standardized (#1452 )	2019-10-28 15:53:10 +08: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 client validation can be found in specs/core. These are divided into phases. Each subsequent phase depends upon the prior. The current phases specified are:

Phase 0

Phase 1

Phase 2

Phase 2 is still actively in R&D and does not yet have any formal specifications.

See the Eth2 Phase 2 Wiki for current progress, discussions, and definitions regarding this work.

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: