-
Notifications
You must be signed in to change notification settings - Fork 29
Feature/174 admin command #180
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
Feature/174 admin command #180
Conversation
hey @klingonaston just wondering why you closed this? The code looks good, would be happy to help w/ any merge conflicts. |
580b9a5
to
bc30acd
Compare
@zeroXbrock sorry for the inconvenience. I was confused about the conflicts. I need help with the merge conflicts. |
No problem, this one was kinda hairy, happy to handle the conflicts. Thanks for the PR! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
so happy to finally have this -- very helpful for debugging. Thanks again @klingonaston !
Motivation
This PR addresses Issue #174 in the Flashbots Contender repository. The issue pertained to [briefly describe the problem, e.g., "a race condition causing transaction misordering under high load"]. Resolving this ensures improved stability and performance of the Contender tool.
Solution
The implemented solution involves [briefly describe the solution, e.g., "introducing a mutex to synchronize access to shared resources, thereby preventing concurrent modifications that led to the race condition"]. This change ensures that [describe the outcome, e.g., "transactions are processed in the correct order without conflicts"].
PR Checklist