Skip to content

Commit f65c6aa

Browse files
committed
Update exit criteria when crossing Epoch boundary.
1 parent 75306bd commit f65c6aa

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

proposals/0046-optimistic-cluster-restart-automation.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -391,13 +391,13 @@ Because right now epoch stakes are calculated 1 epoch ahead of time, and we
391391
only handle outages spanning 7 hours, the local root bank should have the
392392
epoch stakes for all epochs we need.
393393

394-
* When aggregating `RestartLastVotedForkSlots`, for any epoch with at least one
395-
slot X having > 42% stake, calculate the stake of active validators in this
396-
epoch. Only exit this stage if all epochs reaching the above bar has > 80%
397-
stake. This is a bit restrictive, but it guarantees that whichever slot we
398-
select for HeaviestFork, we have enough validators in the restart. Note that
399-
the epoch containing local root should always be considered, because root
400-
should have > 42% stake.
394+
* When aggregating `RestartLastVotedForkSlots`, for any epoch with validators
395+
voting for any slot in this epoch having at least 33% stake, calculate the
396+
stake of active validators in this epoch. Only exit this stage if all epochs
397+
reaching the above bar has > 80% stake. This is a bit restrictive, but it
398+
guarantees that whichever slot we select for HeaviestFork, we have enough
399+
validators in the restart. Note that the epoch containing local root should
400+
always be considered, because root should have > 33% stake.
401401

402402
* When aggregating `RestartHeaviestFork`, use the stake weight of the slot
403403
selected in `RestartHeaviestFork`. If others don't agree with us on the same

0 commit comments

Comments
 (0)