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
1,921 Commits 49 Branches 0 Tags 29 MiB
Python 98%
Makefile 2%
Go to file
Alex Stokes b966041ddb formatting fix (#899) 2019-04-12 18:56:55 +10:00
.circleci reconfigure build a bit 2019-03-18 14:14:26 -06:00
configs include minimal testing constants from previous pytests 2019-04-07 16:17:42 +10:00
scripts fix a few bugs in testing compute_committee 2019-03-19 11:15:51 -06:00
specs formatting fix (#899) 2019-04-12 18:56:55 +10:00
tests replace signed_root with signing_root 2019-04-08 09:57:04 +08:00
utils replace signed_root with signing_root 2019-04-08 09:57:04 +08:00
.gitignore backport 839 into dev 2019-03-25 11:25:33 -06:00
LICENSE CC0 1.0 Universal for repo 2019-03-12 11:59:08 +00:00
Makefile Add dependencies to Makefile 2019-04-10 13:38:48 +01:00
README.md Broken link fix (#888) 2019-04-10 16:42:00 +10:00
requirements.txt add basic dependencies and build script for phase0 testing 2019-03-18 10:18:57 -06:00

README.md

Ethereum 2.0 Specifications

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

To learn more about sharding and eth2.0/Serenity, see the sharding FAQ and the research compendium.

This repo hosts the current eth2.0 specifications. Discussions about design rationale and proposed changes can be brought up and discussed as issues. Solidified, agreed upon changes to spec can be made through pull requests.

Specs

Core specifications for eth2.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:

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)