From 4bf20a1208438480b72b8ca920f31c381a383971 Mon Sep 17 00:00:00 2001 From: protolambda Date: Fri, 5 Apr 2019 19:29:58 +1100 Subject: [PATCH] remove confusing note --- specs/test_formats/README.md | 3 --- 1 file changed, 3 deletions(-) diff --git a/specs/test_formats/README.md b/specs/test_formats/README.md index 1173c06aa..d37b0b538 100644 --- a/specs/test_formats/README.md +++ b/specs/test_formats/README.md @@ -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: