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

remove confusing note

This commit is contained in:
protolambda 2019-04-05 19:29:58 +11:00
parent 13fc498f7b
commit 4bf20a1208
No known key found for this signature in database
GPG Key ID: EC89FDBB2B4C7623
1 changed files with 0 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
specs/test_formats/README.md
View File

@ -124,9 +124,6 @@ A fork timeline is (preferably) loaded in as a configuration object into a clien
- we may decide on a slot number for a fork based on external events (e.g. Eth1 log event),
a client should be able to activate a fork dynamically.
Note that phases are considered to be "super forks",
i.e. they will just have a fork name, and be more heavy on changes.
## Config sourcing
The constants configurations are located in: