Solver participation guard e2e test #3280
Open
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
mstrug
approved these changes
Feb 14, 2025
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.
Implements e2e tests for all the solver participation guards from #3263 and #3257. Simulates the settlement failures by altering the DB. Another alternative is to use a broken MEV blocker URL, which is considered less flexible since some of the solutions need to be successfully settled to test at least the statistic-based approach.
The approach is a bit awkward due to the async nature of the guards implementation. Thinking more about the sync approach, there will still be the same behavior since a new auction is being cut while the previous one is being settled, meaning the sync approach will also allow the non-settling solver to submit one more solution before getting a ban.