Ethereum 2.0 Specifications

Go to file

Hsiao-Wei Wang a0d646e1e0 Add decorators to diable testing with mainnet config		2020-09-04 21:50:21 +08:00
.circleci	Kick cache	2020-07-02 14:39:14 +08:00
configs	Update testing context	2020-08-12 21:50:14 +08:00
deposit_contract	Package eth2spec for tooling and experimentation	2020-01-25 01:57:11 +01:00
specs	Remove AttestationCustodyBitWrapper	2020-08-11 12:35:31 +08:00
ssz	Merge pull request #1934 from booleanfunction/clarify_ssz_pack_packbits_merkleise	2020-06-29 08:31:37 -06:00
tests	Add decorators to diable testing with mainnet config	2020-09-04 21:50:21 +08:00
.codespell-whitelist	Add codespell whitelist	2019-08-19 13:06:21 +02:00
.gitattributes	Rename vyper file from `.v.py` to `.vy`	2020-01-07 17:20:17 +08:00
.gitignore	revert local config settings from .gitignore	2020-06-16 15:34:01 -06:00
LICENSE	CC0 1.0 Universal for repo	2019-03-12 11:59:08 +00:00
Makefile	Use Milagro BLS in CI	2020-07-24 02:00:52 +08:00
README.md	Update sharding FAQs link	2020-07-23 16:35:21 -07:00
linter.ini	Set linter configs in `linter.ini`	2020-06-18 14:36:14 +08:00
setup.py	Update testing context	2020-08-12 21:50:14 +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 clients be found in specs. 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: