force the reward pulser to completion sooner #2521
Merged
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
Some tools, such ad db-sync and the stake credential history tool rely on being able to inspect the ledger state for the reward update. If the pulser does not finish before the end of the epoch (which has happened on the Shelley-QA network, see IntersectMBO/cardano-db-sync#882) then the pulser is forced to completion at the moment it is applied, as is therefore invisible to downstream tools. To solve this problem, we force completion of the reward pulser by (2k/f)-many slots before the end of the epoch (one day on mainnet).
JaredCorduan
force-pushed
the
jc/force-reward-pulser-before-end-of-epoch
branch
from
3dd8080
to
4e43452
Compare
erikd
approved these changes
Oct 17, 2021
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.
Some tools, such as db-sync and the stake credential history tool, rely on being able to inspect the ledger state for the reward update. If the pulser does not finish before the end of the epoch (which has happened on the Shelley-QA network, see
IntersectMBO/cardano-db-sync#882) then the pulser is forced to completion at the moment it is applied, as is therefore invisible to downstream tools.
To solve this problem, we force completion of the reward pulser by
(2k/f)-many slots before the end of the epoch (one day on mainnet).