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
5,554 Commits 49 Branches 0 Tags 29 MiB
Python 98%
Makefile 2%
Go to file
Danny Ryan c9ba641800
note penalties in hf1 list 		2021-02-15 11:22:11 -07:00
.circleci Bump `py_ecc` and `milagro_bls_binding` (#2169) 2021-01-05 21:00:52 +08:00
configs update penalty config values for hf1 2021-02-11 15:55:43 -07:00
solidity_deposit_contract Update solidity_deposit_contract/README.md 2020-09-14 15:10:18 +02:00
specs note penalties in hf1 list 2021-02-15 11:22:11 -07:00
ssz Minor update ToC 2020-12-07 11:10:19 +08:00
tests Fix the tests that use `MIN_SLASHING_PENALTY_QUOTIENT`. (The mainnet tests failed before this fix) 2021-02-13 23:02:06 +08:00
.codespell-whitelist Set codespell<3.0.0,>=2.0.0 version and add `ether` to whitelist 2020-12-07 11:08:54 +08:00
.gitattributes Update the docs and remove unused code 2020-08-18 00:58:08 +08:00
.gitignore executable light client patch: beacon-chain.md (#2141) 2020-12-15 13:18:20 +08:00
.gitmodules WIP: add solidity deposit contract CI workflow 2020-08-17 23:37:33 +08:00
LICENSE
…
Makefile Bump `py_ecc` and `milagro_bls_binding` (#2169) 2021-01-05 21:00:52 +08:00
README.md Updated Sharding technical details link in readme. 2020-12-27 00:20:08 +02:00
linter.ini
…
setup.py Bump `py_ecc` and `milagro_bls_binding` (#2169) 2021-01-05 21:00:52 +08:00

README.md

Ethereum 2.0 Specifications

Join the chat at https://discord.gg/qGpsxSA 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

Light clients

Sharding

The sharding spec is still actively in R&D; see the most recent available pull request here and some technical details here.

Merge

The merge is still actively in R&D; see an ethresear.ch post describing the proposed basic mechanism here and the section of ethereum.org describing the merge at a high level here.

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: