status-im
/
eth2.0-specs
mirror of https://github.com/status-im/eth2.0-specs.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity
Ethereum 2.0 Specifications
5,120 Commits 49 Branches 0 Tags 29 MiB
Python 98%
Makefile 2%
Go to file
Jacek Sieka 6f7652d330
process_attestation: Validate epoch before using it 
`data.target.epoch` is used to count the active validator set.

Because `get_committee_count_per_slot` is extremely inefficient the way
the spec is written, clients cache it, or the underlying active
validator set.

Performing the checks in the given order leads to a (very unlikely)
security issue where the a cold and above all, distant value may get
used which may be costly - reordering the checks brings the value into a
more reasonable range before using it.
 		2020-07-24 07:26:37 +02:00
.circleci Kick cache 2020-07-02 14:39:14 +08:00
configs Merge branch 'dev' into phase1-validator 2020-06-16 16:07:20 -06:00
deposit_contract Package eth2spec for tooling and experimentation 2020-01-25 01:57:11 +01:00
specs process_attestation: Validate epoch before using it 2020-07-24 07:26:37 +02:00
ssz Merge pull request #1934 from booleanfunction/clarify_ssz_pack_packbits_merkleise 2020-06-29 08:31:37 -06:00
tests bump VERSION.txt to 0.12.2 2020-07-23 10:28:02 -06:00
.codespell-whitelist Add codespell whitelist 2019-08-19 13:06:21 +02:00
.gitattributes Rename vyper file from `.v.py` to `.vy` 2020-01-07 17:20:17 +08:00
.gitignore revert local config settings from .gitignore 2020-06-16 15:34:01 -06:00
LICENSE CC0 1.0 Universal for repo 2019-03-12 11:59:08 +00:00
Makefile Fix path 2020-06-18 19:03:40 +08:00
README.md Add release & pypi badges 2020-05-06 18:03:48 +08:00
linter.ini Set linter configs in `linter.ini` 2020-06-18 14:36:14 +08:00
setup.py Merge branch 'dev' into hwwhww/new_int_to_bytes_dev 2020-07-16 01:36:19 +08:00

README.md

Ethereum 2.0 Specifications

Join the chat at https://discord.gg/hpFs23p Join the chat at https://gitter.im/ethereum/sharding

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

GitHub release PyPI version

Core specifications for Eth2 clients be found in specs. 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:

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/validate O(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: