status-im/eth2.0-specs
2
0
Fork 0
mirror of https://github.com/status-im/eth2.0-specs.git synced 2025-01-11 19:24:15 +00:00
Code Issues Projects Releases Wiki Activity

list new Merge specs, update features descriptions

Browse Source
This commit is contained in:
protolambda 2021-03-27 01:10:13 +01:00
parent 29f78a7f06
commit d067237e30
No known key found for this signature in database
GPG Key ID: EC89FDBB2B4C7623
1 changed files with 17 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
README.md
View File

@ -11,7 +11,10 @@ This repository hosts the current Eth2 specifications. Discussions about design
[![GitHub release](https://img.shields.io/github/v/release/ethereum/eth2.0-specs)](https://github.com/ethereum/eth2.0-specs/releases/) [![PyPI version](https://badge.fury.io/py/eth2spec.svg)](https://badge.fury.io/py/eth2spec) [![GitHub release](https://img.shields.io/github/v/release/ethereum/eth2.0-specs)](https://github.com/ethereum/eth2.0-specs/releases/) [![PyPI version](https://badge.fury.io/py/eth2spec.svg)](https://badge.fury.io/py/eth2spec)
Core specifications for Eth2 clients be found in [specs](specs/). These are divided into phases. Each subsequent phase depends upon the prior. The current phases specified are: Core specifications for Eth2 clients be found in [specs](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 ### Phase 0
@ -29,19 +32,28 @@ Core specifications for Eth2 clients be found in [specs](specs/). These are divi
### Merge ### Merge
The merge is still actively in R&D; see an [ethresear.ch](https://ethresear.ch) post describing the proposed basic mechanism [here](https://ethresear.ch/t/the-eth1-eth2-transition/6265) and the section of [ethereum.org](https://ethereum.org) describing the merge at a high level [here](https://ethereum.org/en/eth2/docking/). 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](https://ethresear.ch) post [describing the basic mechanism](https://ethresear.ch/t/the-eth1-eth2-transition/6265)
* [ethereum.org](https://ethereum.org) high-level description of the merge [here](https://ethereum.org/en/eth2/docking/)
* Specifications:
* [Beacon Chain changes](specs/merge/beacon-chain.md)
* [Fork Choice changes](specs/merge/fork-choice.md)
* [Validator additions](specs/merge/validator.md)
### Sharding ### Sharding
Sharding follows the merge, and is divided into three parts: Sharding follows the merge, and is divided into three parts:
* Sharding base functionality * Sharding base functionality - In early engineering phase
* [Beacon Chain changes](specs/sharding/beacon-chain.md) * [Beacon Chain changes](specs/sharding/beacon-chain.md)
* [P2P Network changes](specs/sharding/p2p-interface.md) * [P2P Network changes](specs/sharding/p2p-interface.md)
* Proof of Custody * Proof of Custody - Ready, dependent on sharding
* [Custody Game](specs/proof_of_custody/custody-game.md) * [Custody Game](specs/proof_of_custody/custody-game.md)
* [Validator custody work](specs/proof_of_custody/validator.md) * [Validator custody work](specs/proof_of_custody/validator.md)
* Data Availability Sampling * Data Availability Sampling - In active R&D
* Technical details [here](https://hackmd.io/@HWeNw8hNRimMm2m2GH56Cw/B1YJPGkpD). * Technical details [here](https://hackmd.io/@HWeNw8hNRimMm2m2GH56Cw/B1YJPGkpD).
* [Core types and functions](specs/das/das-core.md) * [Core types and functions](specs/das/das-core.md)
* [P2P Networking](specs/das/p2p-interface.md) * [P2P Networking](specs/das/p2p-interface.md)