Uh oh!
There was an error while loading. Please reload this page.
fix: operator double signature - #1088
Merged
Merged
Conversation
MauroToscano
requested changes
Sep 26, 2024
MarcosNicolau
commented
Sep 26, 2024
CollaboratorAuthor
Fixed! We needed to wait for the receipt when depositing into the strategy contract. Tbh, I don't know why it was working with the rest of the configurations. |
entropidelic
approved these changes
Oct 1, 2024
MauroToscano
approved these changes
Oct 1, 2024
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Changes
Updates go eigensdk to version 0.1.12 which fixes the double signature err. All files using the SDK have been updated accordingly to the new version. Finally, our check has been removed since the SDK handles it now.
Test
When modifying the operator and sending two signed responses after verifying one batch, the aggregator should ignore the second one and the system should continue working as usual. See here for a more detailed testing #1097.