Ethereum 2.0 Specifications
Go to file
dapplion 23ad85e8bf Allow to switch to compounding validator on deposit 2024-03-27 00:31:09 +09:00
.circleci Rename `peerdas` to `eip7594` 2024-01-14 00:13:08 +08:00
.github/workflows Merge pull request #3557 from ethereum/polynomial-commitments-sampling 2024-01-15 16:16:49 +08:00
configs Add EIP-7251 spec 2024-03-08 12:37:35 +08:00
docker Update docker/README.md 2024-01-10 23:41:35 +08: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 Set MIN_SLASHING_PENALTY_QUOTIENT_EIP7251=4096 2024-03-21 17:32:03 +06:00
pysetup Merge branch 'dev' into eip-7251 2024-03-20 14:46:43 +06: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 Allow to switch to compounding validator on deposit 2024-03-27 00:31:09 +09:00
ssz Merge pull request #3506 from status-im/canonical-json-byte 2024-01-11 08:45:20 -07:00
sync Move `verify_and_notify_new_payload` to Bellatrix 2023-05-24 11:12:03 +08:00
tests fix broken pending deposits tests and typo 2024-03-25 15:26:50 +01: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 Merge branch 'dev' into eip-7251 2024-03-20 14:46:43 +06: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 Skip pylint check in CI 2024-01-09 01:37:50 +08:00
README.md Set official mainnet `DENEB_FORK_EPOCH` 2024-02-08 22:34:59 +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 Merge branch 'dev' into pr3563 2024-01-15 19:09:28 +08: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
4 Deneb 269568

In-development Specifications

Code Name or Topic Specs Notes
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.