d1bedbfbec
Two main changes: 1. Inactivity scores are modified to decrease slowly for inactive validators when we are not in a leak, and quickly for active validators 2. The inactivity penalties are applied even not during a leak (note that inactivity _scores_ decrease when outside of a leak) This has the effect that the inactivity leak "overshoots" the target of finalizing again, and keeps leaking balances a bit more. For inactive validators, this PR sets post-leak recovery to happen 3x faster than the during-leak increase, so if a validator loses 3% during a leak, if they stay offline they should expect to lose another 1% until their score decreases back to zero. |
||
|---|---|---|
| .circleci | ||
| configs | ||
| solidity_deposit_contract | ||
| specs | ||
| ssz | ||
| tests | ||
| .codespell-whitelist | ||
| .gitattributes | ||
| .gitignore | ||
| .gitmodules | ||
| LICENSE | ||
| Makefile | ||
| README.md | ||
| linter.ini | ||
| setup.py | ||
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 clients 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
Altair
- Beacon chain changes
- Altair fork
- Light client sync protocol
- Honest Validator guide changes
- P2P Networking
Merge
The merge is still actively in R&D. The specifications outline a general direction for engineering work, while the details are in review and may 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 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: