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,063 Commits 49 Branches 0 Tags 29 MiB
Python 98%
Makefile 2%
Go to file
Diederik Loerakker c82acc6970 change ci to not trigger gen building, since it is not committed anyway. See issue #928 (#947) 2019-04-17 11:49:49 +10:00
.circleci change ci to not trigger gen building, since it is not committed anyway. See issue #928 (#947) 2019-04-17 11:49:49 +10:00
configs update constants to match latest dev (#933) 2019-04-16 14:57:57 +10:00
py_tests Merge branch 'dev' into proto-merge-test-gen 2019-04-15 16:35:38 +10:00
scripts/phase0 Update scripts/phase0/function_puller.py 2019-04-16 13:32:28 +10:00
specs Update 1_shard-data-chains.md 2019-04-16 12:03:22 -05:00
test_generators implement assertion sanity check suggested in PR 2019-04-15 23:55:32 +10:00
test_libs fix argument typing for auxilary transition func 2019-04-15 23:37:28 +10:00
.gitignore rename pyspec pkg to eth2spec 2019-04-03 14:18:17 +11:00
LICENSE CC0 1.0 Universal for repo 2019-03-12 11:59:08 +00:00
Makefile generator running fixes 2019-04-11 19:25:00 +10:00
README.md Update README.md 2019-04-16 12:04:29 -05: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)

For spec contributors

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