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
2,901 Commits 50 Branches 0 Tags 30 MiB
Python 98%
Makefile 2%
Go to file
Hsiao-Wei Wang 8b64f37d22
Make uint64 be `class` for type hinting 		2019-06-10 23:16:59 -04:00
.circleci fix 2019-06-07 23:01:10 -04:00
configs Adds review suggestions I missed 2019-06-06 11:45:22 +02:00
deposit_contract deposit_contract/venv 2019-06-07 22:41:50 -04:00
scripts Make uint64 be `class` for type hinting 2019-06-10 23:16:59 -04:00
specs Fix the Vyper contract link (#1154) 2019-06-08 23:48:34 +01:00
test_generators Make test generators work with phase 1 execution 2019-06-05 16:23:44 +02:00
test_libs Make uint64 be `class` for type hinting 2019-06-10 23:16:59 -04:00
.gitignore Implements parameterised phase1 tests 2019-05-16 12:10:08 +02:00
LICENSE CC0 1.0 Universal for repo 2019-03-12 11:59:08 +00:00
Makefile improve makefile: declare new targets as non-file 2019-06-08 13:30:47 +02:00
README.md Merge pull request #1069 from sigp/bn-vc-api-rfc 2019-05-28 16:07:51 -06:00

README.md

Ethereum 2.0 Specifications

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 Eth 2.0 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 Eth 2.0 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

Accompanying documents can be found in specs and include:

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)

For spec contributors

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