This repository has been archived by the owner on Oct 25, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 139
Does AddMevBundle need to use global pool mutex ? #7
Comments
I think it's a good idea! |
awesome ty for heads up! will try and get a PR out this coming week |
Closed
avalonche
pushed a commit
that referenced
this issue
Feb 7, 2023
avalonche
pushed a commit
that referenced
this issue
Mar 9, 2023
avalonche
pushed a commit
that referenced
this issue
Mar 15, 2023
avalonche
pushed a commit
that referenced
this issue
Mar 17, 2023
avalonche
pushed a commit
that referenced
this issue
Mar 22, 2023
avalonche
pushed a commit
that referenced
this issue
Jul 6, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
AddMevBundle
surely needs to lock for atomicity of adding to the bundle pool (pool.mevBundles
), but as far as I can tell it doesn't interact with the rest of the txpool so should be okay to use something likepool.bundleMu.Lock()
? Happy to implement if so 😃The text was updated successfully, but these errors were encountered: