cryptarchia: Update epoch stabilization schedule to 334 (from 433) #79
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently the epoch stabilization schedule is only set in tests, we've defined the spec to allow any schedule when instantiated. This PR mostly updates the tests to reflect the new schedule:
The epoch stabilization schedule controls the order that epoch state data is stabilized and the duration of each stabilization period.
Previously ouroborous followed a 4 3 3 schedule (4k/f, 3k/f, 3k/f slots).
the first 4k/f + 3k/f = 7k/f slots were a buffer between when the stake distribution snapshot was taken and when the nonce snapshot is taken. The intention is to have a wide enough gap to prevent any adversary from having being able to influence the next epoch's nonce through coin grinding.
The move to 3 3 4 schedule means we have a gap of 6k/f slots between when the stake distribution snapshot and nonce snapshots are taken.
This new schedule gives more time for the nonce to stabilize before we enter the next epoch (entering a new epoch without a stable nonce would be quite chaotic, I don't think oroborous has contingencies in place for such an event)
This change in cardano / oroborous is here: IntersectMBO/ouroboros-consensus#927