Ethereum 2.0 Specifications

Go to file

vbuterin 53dd49167b Changes to inactivity leak * Fixes parameters and makes clear that the inactivity leak is on a per-epoch basis (before the leak was technically 64 times too weak as it was calculated per-slot but applied per-epoch) * Adds a `// 2` to the inactivity leak to compensate for it being applied twice * Changes how it is calculated (no inactivity leak for not being part of the head, only basic leak) * Separates out early inclusion incentives into a separate incentive component rather than being multiplicative with everything else	2018-12-20 12:41:17 -05:00
specs	Changes to inactivity leak	2018-12-20 12:41:17 -05:00
README.md	cleaning up README	2018-12-15 09:28:13 -05:00

* Fixes parameters and makes clear that the inactivity leak is on a per-epoch basis (before the leak was technically 64 times too weak as it was calculated per-slot but applied per-epoch)
* Adds a `// 2` to the inactivity leak to compensate for it being applied twice
* Changes how it is calculated (no inactivity leak for not being part of the head, only basic leak)
* Separates out early inclusion incentives into a separate incentive component rather than being multiplicative with everything else

2018-12-20 12:41:17 -05:00

specs

Changes to inactivity leak

2018-12-20 12:41:17 -05:00

README.md

cleaning up README

2018-12-15 09:28:13 -05:00

README.md

Ethereum 2.0 Specifications

To learn more about sharding and eth2.0/Serenity, see the sharding FAQ and the research compendium.

This repo hosts the current eth2.0 specifications. Discussions about design rationale and proposed changes can be brought up and discussed as issues. Solidified, agreed upon changes to spec can be made through pull requests.

Specs

Core specifications for eth2.0 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:

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/validate O(1) shards (including any system level validation such as the beacon chain)