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,684 Commits 49 Branches 0 Tags 29 MiB
Python 98%
Makefile 2%
Go to file
Danny Ryan ab197d9784
Merge pull request #800 from ethereum/ci 
ci tests
 		2019-03-19 09:57:06 -06:00
.circleci reconfigure build a bit 2019-03-18 14:14:26 -06:00
scripts Fix linter 2019-03-19 11:39:19 +08:00
specs Merge pull request #755 from ethereum/dev 2019-03-14 15:49:49 -06:00
tests withdrwaal_key uses pubkey 2019-03-19 09:56:04 -06:00
utils ensure run verify-state root with block 2019-03-19 09:49:32 -06:00
.gitignore reconfigure build a bit 2019-03-18 14:14:26 -06:00
LICENSE CC0 1.0 Universal for repo 2019-03-12 11:59:08 +00:00
Makefile add comment to Makefile 2019-03-18 16:30:16 -06:00
README.md Add link to honest validator implementation doc to main readme 2019-01-28 12:01:51 -06: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)