feat: random delay before opening a challenge #355
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
terencechain
force-pushed
the
random-delay-before-challenge
branch
from
4c0e448
to
25e5607
Compare
rauljordan
approved these changes
Jul 7, 2023
terencechain
added a commit
that referenced
this pull request
Jul 7, 2023
Co-authored-by: Raul Jordan <[email protected]>
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.
If every validator were to challenge an invalid assertion simultaneously, there would undoubtedly be races, many failed txs, and wasted gas. This PR implements a random delay that could be configured by the caller when initializing the challenge manager service. The random delay will be upper bounded by the parameter
maxDelaySeconds