370b9e86e3
There are three defined unit tests for the light client sync protocol. They all follow a similar structure. However, there is an inconcistency how they pass the slot to compute_aggregate_sync_committee_signature. In one instance it is passed as `block.slot`. In the other two cases it is passed as `block_header.slot`. As the `block_header` is created from the `block`, they share the same value. This patch makes the way how the slot is passed consistent across all of the test cases. |
||
|---|---|---|
| .circleci | ||
| configs | ||
| presets | ||
| solidity_deposit_contract | ||
| specs | ||
| ssz | ||
| tests | ||
| .codespell-whitelist | ||
| .gitattributes | ||
| .gitignore | ||
| .gitmodules | ||
| LICENSE | ||
| Makefile | ||
| README.md | ||
| SECURITY.md | ||
| linter.ini | ||
| setup.py | ||
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.
The current features are:
Phase 0
- The Beacon Chain
- Beacon Chain Fork Choice
- Deposit Contract
- Honest Validator
- P2P Networking
- Weak Subjectivity
Altair
- Beacon chain changes
- Altair fork
- Light client sync protocol
- Honest Validator guide changes
- P2P Networking
Merge
The merge is still actively in development. The exact specification has not been formally accepted as final and details are still subject to change.
- Background material:
- An ethresear.ch post describing the basic mechanism
- ethereum.org high-level description of the merge here
- Specifications:
Sharding
Sharding follows the merge, and is divided into three parts:
- Sharding base functionality - In early engineering phase
- Custody Game - Ready, dependent on sharding
- Data Availability Sampling - In active R&D
- Technical details here.
- Core types and functions
- P2P Networking
- Fork Choice
- Sampling process
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/validateO(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.