You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: README.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
# Ethereum 2.0 Specifications
2
2
3
-
[](https://discord.gg/hpFs23p)[](https://gitter.im/ethereum/sharding?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
3
+
[](https://discord.gg/qGpsxSA)[](https://gitter.im/ethereum/sharding?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
4
4
5
5
To learn more about sharding and Ethereum 2.0 (Serenity), see the [sharding FAQ](https://eth.wiki/sharding/Sharding-FAQs) and the [research compendium](https://notes.ethereum.org/s/H1PGqDhpm).
Copy file name to clipboardexpand all lines: configs/README.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,7 @@ Over time, the need to sync an older state may be deprecated.
15
15
In this case, the prefix on the new constant may be removed, and the old constant will keep a special name before completely being removed.
16
16
17
17
A previous iteration of forking made use of "timelines", but this collides with the definitions used in the spec (constants for special forking slots, etc.), and was not integrated sufficiently in any of the spec tools or implementations.
18
-
Instead, the config essentially doubles as fork definition now, e.g. changing the value for `PHASE_1_GENESIS_SLOT` changes the fork.
18
+
Instead, the config essentially doubles as fork definition now, e.g. changing the value for `PHASE_1_FORK_SLOT` changes the fork.
19
19
20
20
Another reason to prefer forking through constants is the ability to program a forking moment based on context, instead of being limited to a static slot number.
0 commit comments