chore(protocol): change bond amounts, proving windows, and cooldown windows #18371
+40
−41
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
davidtaikocha
approved these changes
Nov 2, 2024
chore(protocol): change bond amounts, proving windows, and cooldown windows
🚨 Report Summary
For more details view the full report in OpenZeppelin Code Inspector |
Comment on lines
15
to
17
| /// service may be paused if gas prices are excessively high. Since block proving is | ||
| /// asynchronous, this grace period allows provers to defer submissions until gas | ||
| /// prices become more favorable, potentially reducing transaction costs. |
There was a problem hiding this comment.
These comments of GRACE_PERIOD can also be removed?
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.
We can launch these changes alongside the ZK proofs. However, we’ll need to draft an announcement (@dantaik) and update the documentation afterward (@RogerLamTd).
@smtmfft, please review to confirm if these values align as expected.