status-im
/
eth2.0-specs
mirror of https://github.com/status-im/eth2.0-specs.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity
Ethereum 2.0 Specifications
4,089 Commits 50 Branches 0 Tags 30 MiB
Python 98%
Makefile 2%
Go to file
Carl Beekhuizen e70863ca93
Bytes4 -> DomainType 		2019-12-30 06:52:00 +01:00
.circleci Merge pull request #1546 from ethereum/master 2019-12-20 21:25:50 +01:00
configs Merge pull request #1467 from ethereum/reduce-genesis-count 2019-11-18 13:30:04 -07:00
deposit_contract fix vyper custom build link and bump pycryptodome version 2019-12-18 16:36:28 -07:00
scripts PySpec SSZ Bytes instantiated from hex 2019-12-27 09:37:26 +01:00
specs Bytes4 -> DomainType 2019-12-30 06:52:00 +01:00
test_generators remove signing_root: see issue #1487 2019-12-03 21:10:19 +01:00
test_libs PySpec SSZ Bytes instantiated from hex 2019-12-27 09:37:26 +01: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 Makefile: Use codespell as intended 2019-12-16 14:18:34 +01:00
README.md PR feedback 2019-11-05 09:08:37 -07:00

README.md

Ethereum 2.0 Specifications

Join the chat at https://discord.gg/hpFs23p Join the chat at https://gitter.im/ethereum/sharding

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: