Ethereum 2.0 Specifications
Go to file
Etan Kissling 05c2ce11db
Merge branch 'dev' into lc-branchtypes
2024-01-09 14:35:31 +01:00
.circleci clean-up todo 2023-10-10 14:17:45 +03:00
.github/workflows WIP: Update dockerisation (#3477) 2024-01-04 17:09:06 +01:00
configs Merge branch 'dev' into pr3034 2023-10-26 23:51:35 +08:00
docker WIP: Update dockerisation (#3477) 2024-01-04 17:09:06 +01:00
docs update doc 2023-12-15 19:12:57 +08:00
fork_choice Add docs about how to add a new feature proposal in consensus-specs and online viewer support (#3239) 2023-04-18 18:31:34 +08:00
presets Merge pull request #3442 from dapplion/whisk-tests 2023-12-08 18:56:03 +09:00
pysetup Merge pull request #3442 from dapplion/whisk-tests 2023-12-08 18:56:03 +09:00
scripts WIP: Update dockerisation (#3477) 2024-01-04 17:09:06 +01:00
solidity_deposit_contract Update solidity_deposit_contract/README.md 2020-09-14 15:10:18 +02:00
specs Use proper types when dealing with LC Merkle proofs 2023-12-27 13:59:31 +01:00
ssz Fix typing and delete the `signed_sidecar` 2023-10-30 18:28:12 +08:00
sync Move `verify_and_notify_new_payload` to Bellatrix 2023-05-24 11:12:03 +08:00
tests Add assertion to ensure eval usage is fine 2023-12-21 22:55:46 +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
.dockerignore WIP: Update dockerisation (#3477) 2024-01-04 17:09:06 +01:00
.gitattributes Update the docs and remove unused code 2020-08-18 00:58:08 +08:00
.gitignore WIP: Update dockerisation (#3477) 2024-01-04 17:09:06 +01:00
.gitmodules WIP: add solidity deposit contract CI workflow 2020-08-17 23:37:33 +08:00
LICENSE CC0 1.0 Universal for repo 2019-03-12 11:59:08 +00:00
Makefile WIP: Update dockerisation (#3477) 2024-01-04 17:09:06 +01:00
README.md Add link to Engine APIs 2023-06-06 18:24:36 +08:00
SECURITY.md Update disclosure page and email for reporting bugs 2023-03-09 23:06:30 +01:00
linter.ini Enable EIP4844 lint and fix Pylint 2022-11-28 20:01:50 +08:00
mkdocs.yml Add docs about how to add a new feature proposal in consensus-specs and online viewer support (#3239) 2023-04-18 18:31:34 +08:00
requirements_preinstallation.txt WIP: Update dockerisation (#3477) 2024-01-04 17:09:06 +01:00
setup.py Avoid Mypy error during lint 2023-12-27 13:58:36 +01:00

README.md

Ethereum Proof-of-Stake Consensus Specifications

Join the chat at https://discord.gg/qGpsxSA

To learn more about proof-of-stake and sharding, see the PoS documentation, sharding documentation and the research compendium.

This repository hosts the current Ethereum proof-of-stake 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 Ethereum proof-of-stake clients can be found in specs. These are divided into features. Features are researched and developed in parallel, and then consolidated into sequential upgrades when ready.

Stable Specifications

Seq. Code Name Fork Epoch Specs
0 Phase0 0
1 Altair 74240
2 Bellatrix
("The Merge")
144896
3 Capella 194048

In-development Specifications

Code Name or Topic Specs Notes
Deneb (tentative)
Sharding (outdated)
Custody Game (outdated) Dependent on sharding
Data Availability Sampling (outdated)
EIP-6110

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 the Ethereum proof-of-stake consensus specifications:

  • 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:

Online viewer of the latest release (latest master branch)

Ethereum Consensus Specs

Consensus spec tests

Conformance tests built from the executable python spec are available in the Ethereum Proof-of-Stake Consensus Spec Tests repo. Compressed tarballs are available in releases.