-
Notifications
You must be signed in to change notification settings - Fork 39
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
Add mempool persistence logic using Redis #13
Comments
can this be done via rocksdb where its key-value pair? |
@mouseless-eth will be picking this up if this is still relevant change to be done |
@mouseless-eth is this still a priority item to be picked up? i have some time this & next week and can pick this up if this is needed |
This issue is still relevant and a feature that we will most likely implement in the future, let me know if anyone would like to give it a go. Happy to discuss further in dms at t.me/mouseless |
NOTE: Lower priority
Currently we don't persist incoming UserOperations in a mempool, and send them straight to be included on-chain. This is not a big problem right now because there isn't enough volume on-chain to justify waiting for multiple UserOperations until submission for inclusion, but this is required to be compliant with the spec.
Let's create a persistent mempool using Redis with
ioredis
The text was updated successfully, but these errors were encountered: