Skip to content

Commit b46a9df

Browse files
author
Erik Stenman
committed
Update to 5 epochs.
1 parent 16795d3 commit b46a9df

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

Periodically-Syncing-HyperChains.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -227,7 +227,7 @@ We implement part of the child chain by means of one or more smart contracts tha
227227
For example, there will be a staking contract that keeps track of the stakers at each height. Updates to these contracts is
228228
performed by contract calls, which makes the state of the contracts visible on-chain.
229229

230-
The main contract must be aware of the four staking cycles and keeps track of those four cycles independently.
230+
The main contract must be aware of the five staking cycles and keeps track of those five cycles independently.
231231
At the end of a child epoch, the state is updated and the epochs shift taking the correct parameters into account.
232232

233233
The epoch length can be adjusted within a cycle by having the last leader of the production epoch propose decrease or increase of the length.
@@ -552,7 +552,7 @@ if you have tokens at stake.
552552
#### Staking Cycle Structure
553553

554554
Each epoch needs a schedule of producers. These producers are randomly selected from registered stakers.
555-
We are concerned about the following:
555+
The election procedure has following goals:
556556
- To prevent stakers to influence the schedule, the staking distribution should be known before the seed of the random selection is known.
557557
- The seed should be final (that is it should be guaranteed not to disappear from the parent chain due to forking)
558558
- The seed should be known before the actual schedule needs to be computed, otherwise the child chain is stuck

0 commit comments

Comments
 (0)