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,741 Commits 50 Branches 0 Tags 30 MiB
Python 98%
Makefile 2%
Go to file
Jacek Sieka 607e23949c
require blocks to be ordered consecutively in block range request 
Per the spec, if I request range 5-10, it is permissible for a client to
answer with block 7, 9 - even if the blocks 5, 6 and 8 exist.

Because blocks 7 and 9 cannot be validated as they arrive in such a
request, it seems better to close this gap - this update adds the spec
language that forbids well-behaving clients from answering this way.
 		2020-05-20 20:29:37 +02:00
.circleci add note about distributing bootnode ENRs prior to genesis 2020-04-22 14:33:57 -06:00
configs move MAX_ATTESTER_SLASHINGS to 2, add multiple slashings per block tests 2020-05-08 10:43:11 -06:00
deposit_contract Package eth2spec for tooling and experimentation 2020-01-25 01:57:11 +01:00
specs require blocks to be ordered consecutively in block range request 2020-05-20 20:29:37 +02:00
ssz Fix typo 2020-05-14 15:01:03 +08:00
tests hww feedback for finality rewards fix 2020-05-20 10:12:57 -06:00
.codespell-whitelist Add codespell whitelist 2019-08-19 13:06:21 +02:00
.gitattributes Rename vyper file from `.v.py` to `.vy` 2020-01-07 17:20:17 +08:00
.gitignore Package eth2spec for tooling and experimentation 2020-01-25 01:57:11 +01:00
LICENSE CC0 1.0 Universal for repo 2019-03-12 11:59:08 +00:00
Makefile Fixed target compile_deposit_contract 2020-04-10 17:38:37 +02:00
README.md Add release & pypi badges 2020-05-06 18:03:48 +08:00
setup.py remerkleable 0.1.16 2020-05-20 15:30:44 +02: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

GitHub release PyPI version

Core specifications for Eth2 clients be found in specs. 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: