You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Go to file
Hsiao-Wei Wang 80ba16283c
Merge pull request #3237 from ethereum/sanity-test-hotfix
2 weeks ago
.circleci EIP-4844: Make the spec executable 7 months ago
.github/workflows adding install_test 4 weeks ago
configs Merge mainnet ttd and bellatrix values (#2969) 6 months ago
fork_choice Apply suggestions as per review 10 months ago
presets Update G2 trusted setup length to 65 2 months ago
scripts Update G2 trusted setup length to 65 2 months ago
solidity_deposit_contract Update solidity_deposit_contract/ 2 years ago
specs Merge pull request #3221 from benjaminion/fc-on-attester-slashing 2 weeks ago
ssz Update 2 years ago
sync Fix typos 3 months ago
tests hotfix: `transition_to_slot_via_block` only return unsigned block 2 weeks ago
.codespell-whitelist Set codespell<3.0.0,>=2.0.0 version and add `ether` to whitelist 2 years ago
.gitattributes Update the docs and remove unused code 3 years ago
.gitignore EIP-4844: Make the spec executable 7 months ago
.gitmodules WIP: add solidity deposit contract CI workflow 3 years ago
LICENSE CC0 1.0 Universal for repo 4 years ago
Makefile Merge branch 'dev' into lc-eph 1 month ago Merge branch 'dev' into lc-eph 4 weeks ago spelling 1 year ago
linter.ini Enable EIP4844 lint and fix Pylint 2 months ago Merge branch 'dev' into lc-eph 4 weeks ago

Ethereum Proof-of-Stake Consensus Specifications

Join the chat at Join the chat at

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.


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")

In-development Specifications

Code Name or Topic Specs Notes
Capella (tentative)
EIP4844 (tentative)
Sharding (outdated)
Custody Game (outdated) Dependent on sharding
Data Availability Sampling (outdated)

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:

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.