feat: implement config option 'finalize' to specify when to stop processing blocks#75
Merged
Merged
Conversation
This file contains hidden or 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.
This implements a
finalizeconfiguration option similar to in Oura. You can use it to make Scrolls stop processing blocks after processing a block with a specified hash or the first block which was created on or after a specified absolute slot.For example you would include the following in your config to stop processing new blocks after processing the block with hash
fafd996ddd3d2fdb2bf2a5dd5a3b32d0827fc53634871c85c5441959d7dae795:Or to stop processing new blocks after processing the first block which was created on or after slot
1713945:Tested with N2N.