Ethereum 2.0 Specifications

Go to file

Jacek Sieka 4d1b487b21 move field last avoids changing "header" fields in state		2022-10-27 10:38:09 +02:00
.circleci	EIP-4844: Make the spec executable	2022-07-13 13:14:05 +03:00
configs	Merge mainnet ttd and bellatrix values (#2969 )	2022-08-15 08:00:14 -06:00
fork_choice	Apply suggestions as per review	2022-03-30 15:36:01 +06:00
presets	some capella sanity tests	2022-10-05 10:40:58 -06:00
solidity_deposit_contract	Update solidity_deposit_contract/README.md	2020-09-14 15:10:18 +02:00
specs	move field last	2022-10-27 10:38:09 +02:00
ssz	Update simple-serialize.md	2021-05-28 18:13:22 -07:00
sync	Add basic test case	2022-08-24 23:20:31 +08:00
tests	Fix bls test case file name	2022-10-26 11:03:16 -05: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	EIP-4844: Make the spec executable	2022-07-13 13:14:05 +03: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	Fix capella random & fork	2022-10-14 23:42:42 -05:00
README.md	Update Bellatrix fork epoch in README	2022-08-17 22:46:47 +08:00
SECURITY.md	spelling	2021-08-30 16:29:41 -06:00
linter.ini	Set linter configs in `linter.ini`	2020-06-18 14:36:14 +08:00
setup.py	Bump dep packages version and fix lint issues	2022-09-28 12:38:21 +08:00

README.md

Ethereum Proof-of-Stake Consensus Specifications

To learn more about proof-of-stake and sharding, see the PoS FAQ, sharding FAQ 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

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`	Core The beacon chain Deposit contract Beacon chain fork choice Additions Honest validator guide P2P networking Weak subjectivity
1	Altair	`74240`	Core Beacon chain changes Altair fork Additions Light client sync protocol (full node, light client, networking) Honest validator guide changes P2P networking
2	Bellatrix ("The Merge")	`144896`	Core Beacon Chain changes Bellatrix fork Fork choice changes Additions Honest validator guide changes P2P networking

In-development Specifications

Code Name or Topic	Specs	Notes
Capella (tentative)	Core Beacon chain changes Capella fork Additions Validator additions
EIP4844 (tentative)	Core Beacon Chain changes EIP-4844 fork Polynomial commitments Additions Honest validator guide changes P2P networking
Sharding (outdated)	Core Beacon Chain changes Additions P2P networking
Custody Game (outdated)	Core Beacon Chain changes Additions Honest validator guide changes	Dependent on sharding
Data Availability Sampling (outdated)	Core Core types and functions Fork choice changes Additions P2P Networking Sampling process	Dependent on sharding Technical explainer

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.