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.
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.
In-development Specifications Accompanying documents can be found in specs and include: Additional specifications for client implementersAdditional specifications and standards outside of requisite client functionality can be found in the following repos:
The following are the broad design goals for the Ethereum proof-of-stake consensus specifications:
O(C)
resources to process/validate O(1)
shards (including any system level validation such as the beacon chain)Documentation on the different components used during spec writing can be found here:
Online viewer of the latest release (latestmaster
branch)
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.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4