-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(protocol): trigger simultaneous recurring TKO snapshots #16715
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
feat(protocol): trigger simultaneous recurring TKO snapshots
🚨 Report Summary
For more details view the full report in OpenZeppelin Code Inspector |
Brechtpd
approved these changes
Apr 11, 2024
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
dantaik
changed the title
feat(protocol): force L1 and L2 to take TKO snapshot at the same time to avoid double voting
feat(protocol): force L1 and L2 to take TKO snapshot at the same time to avoid double voting [do not merge]
Apr 12, 2024
dantaik
changed the title
feat(protocol): force L1 and L2 to take TKO snapshot at the same time to avoid double voting [do not merge]
feat(protocol): trigger TKO snapshot regularly for both L1/L2 to avoid double voting [do not merge]
Apr 12, 2024
This reverts commit 0512cb3.
dantaik
changed the title
feat(protocol): trigger TKO snapshot regularly for both L1/L2 to avoid double voting [do not merge]
feat(protocol): trigger weekly TKO snapshot to avoid double voting
Apr 12, 2024
adaki2004
reviewed
Apr 17, 2024
adaki2004
approved these changes
Apr 18, 2024
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.
To allow voting on both L1 and L2, we need to prevent the same token from voting twice on both L1 and L2. Making sure snapshots of TKO are taken in the same time is one of the conditions to prevent double voting.