48317d8ac0
* remove `BLS_WITHDRAWAL_PREFIX` (it is not used in phase 1, not phase 0) * avoid inline comment (# Validate state root) * simplify header inequality check in `process_proposer_slashing` (using uniqueness of BLS signatures) * add `block = signed_block.message` helper variable for readability * (typo) clarify that the state transition function consumes a signed block (as opposed to a block) * generally make comments more consistent * consistent formatting of container instantiation for `DepositMessage` * avoid using three lines for `rewards[index] += Gwei(max_attester_reward // attestation.inclusion_delay)` * introduce `effective_balance` helper variable for readability, and to avoid multi-line statement * consistent ordering of `MIN_EPOCHS_TO_INACTIVITY_PENALTY` in the time parameters table * (typo) "Dequeued validators for activation up to churn limit" => Dequeue validators * "Save current block as the new latest block" => "Cache current block" (for consistent with `process_slot`) * (typo) "Verify the validator has not yet exited" => "Verify exit has not been initiated" * Use Pythonic `default=` for `max()` call in `initiate_validator_exit` |
||
---|---|---|
.circleci | ||
configs | ||
deposit_contract | ||
scripts | ||
specs | ||
test_generators | ||
test_libs | ||
.codespell-whitelist | ||
.gitignore | ||
LICENSE | ||
Makefile | ||
README.md |
README.md
Ethereum 2.0 Specifications
To learn more about sharding and Ethereum 2.0 (Serenity), see the sharding FAQ and the research compendium.
This repository hosts the current Eth2 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 Eth2 client validation can be found in specs/core. These are divided into phases. Each subsequent phase depends upon the prior. The current phases specified are:
Phase 0
Phase 1
Phase 2
Phase 2 is still actively in R&D and does not yet have any formal specifications.
See the Eth2 Phase 2 Wiki for current progress, discussions, and definitions regarding this work.
Accompanying documents can be found in specs and include:
- SimpleSerialize (SSZ) spec
- BLS signature verification
- General test format
- Merkle proof formats
- Light client syncing protocol
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 Ethereum 2.0:
- 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: