ethereum/consensus-specs

Ethereum Consensus Specifications

3,961

stars

11,476

commits

Python

primary language

Sep 10, 2026

updated

ethereum.github.io/consensus-specs/Browse cluster: Ethereum protocol implementation and specification

README

Ethereum Consensus Specifications

tests image image Discord

This repository hosts the Ethereum proof-of-stake specifications for consensus-layer clients. Design rationale and proposed changes are discussed in issues. Agreed-upon changes are made through pull requests. Specifications can be found in specs, arranged by upgrade. Each upgrade builds on the previous, specifying only what it changes. Individual features are developed in parallel and are folded into an upgrade when ready.

Stable specifications

Seq.Code NameFork EpochLink
0Phase00Spec
1Altair74240Spec
2Bellatrix144896Spec
3Capella194048Spec
4Deneb269568Spec
5Electra364032Spec
6Fulu411392Spec

Unstable specifications

Seq.Code NameFork EpochLink
7GloasTBDSpec
8HezeTBDSpec

Rendered viewers

Reference tests

Design goals

  • Minimize complexity, even at the cost of some losses in efficiency.
  • Remain live through major network partitions and mass node outages.
  • Select components that are quantum-secure or easy to swap out.
  • Use crypto and design techniques that support a large validator set.
  • Minimize hardware requirements such that a consumer laptop can participate.

External specifications

Useful resources

Contributors

(top 30 of 225)

djrtwo

2,806 commits

hwwhww

2,045 commits

protolambda

923 commits

jtraglia

894 commits

ethereum/consensus-specs

Ethereum Consensus Specifications

3,961

stars

11,476

commits

Python

primary language

Sep 10, 2026

updated

ethereum.github.io/consensus-specs/Browse cluster: Ethereum protocol implementation and specification

README

Ethereum Consensus Specifications

tests image image Discord

This repository hosts the Ethereum proof-of-stake specifications for consensus-layer clients. Design rationale and proposed changes are discussed in issues. Agreed-upon changes are made through pull requests. Specifications can be found in specs, arranged by upgrade. Each upgrade builds on the previous, specifying only what it changes. Individual features are developed in parallel and are folded into an upgrade when ready.

Stable specifications

Seq.Code NameFork EpochLink
0Phase00Spec
1Altair74240Spec
2Bellatrix144896Spec
3Capella194048Spec
4Deneb269568Spec
5Electra364032Spec
6Fulu411392Spec

Unstable specifications

Seq.Code NameFork EpochLink
7GloasTBDSpec
8HezeTBDSpec

Rendered viewers

Reference tests

Design goals

  • Minimize complexity, even at the cost of some losses in efficiency.
  • Remain live through major network partitions and mass node outages.
  • Select components that are quantum-secure or easy to swap out.
  • Use crypto and design techniques that support a large validator set.
  • Minimize hardware requirements such that a consumer laptop can participate.

External specifications

Useful resources

Contributors

(top 30 of 225)

djrtwo

2,806 commits

hwwhww

2,045 commits

protolambda

923 commits

jtraglia

894 commits

Languages

Python

99.6%