status-im/eth2.0-specs
2
0
Fork 0
mirror of https://github.com/status-im/eth2.0-specs.git synced 2025-02-02 22:03:37 +00:00
Code Issues Projects Releases Wiki Activity

Replace links to eth2.0-specs with consensus-specs (#3934)

Browse Source 
* Replace references to eth2.0

* Revert changes to the deposit contract dir
This commit is contained in:
Justin Traglia 2024-09-26 08:06:47 -05:00 committed by GitHub
parent dcdcf25d81
commit 72e9a319f1
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
3 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
README.md
View File

@ -8,7 +8,7 @@ This repository hosts the current Ethereum proof-of-stake specifications. Discus
## Specs
[![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/consensus-specs)](https://github.com/ethereum/consensus-specs/releases/) [![PyPI version](https://badge.fury.io/py/eth2spec.svg)](https://badge.fury.io/py/eth2spec)
Core specifications for Ethereum proof-of-stake clients can 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.

2
ssz/simple-serialize.md
View File

@ -263,7 +263,7 @@ We similarly define "summary types" and "expansion types". For example, [`Beacon
## Implementations
See https://github.com/ethereum/eth2.0-specs/issues/2138 for a list of current known implementations.
See https://github.com/ethereum/consensus-specs/issues/2138 for a list of current known implementations.
## JSON mapping

2
tests/core/pyspec/eth2spec/test/phase0/finality/test_finality.py
View File

@ -137,7 +137,7 @@ def test_finality_rule_2(spec, state):
def test_finality_rule_3(spec, state):
"""
Test scenario described here
https://github.com/ethereum/eth2.0-specs/issues/611#issuecomment-463612892
https://github.com/ethereum/consensus-specs/issues/611#issuecomment-463612892
"""
# get past first two epochs that finality does not run on
next_epoch_via_block(spec, state)