Skip to content
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

Explore shared mempool between multiple bundler instance #23

Open
skypigr opened this issue Apr 4, 2023 · 0 comments
Open

Explore shared mempool between multiple bundler instance #23

skypigr opened this issue Apr 4, 2023 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@skypigr
Copy link

skypigr commented Apr 4, 2023

Currently, we use AWS AppRunner to run bundler service.

The AppRunner can easily be set up to scale, for example, it can automatically bring up more instance when demand is high. One issue of this auto scale is that every bundler instance is isolated to each other and AppRunner doesn't provide a custom way to load balance the requests, this leads to problems like:

  1. Inconsistency on transaction override.
  2. Conflict on EOA nonce.

This Bug tracks the effort of solving problem (1), to see how things work out if all bundler instance share the same mempool, well technically, share the same userOp Queue.

A few high level steps going forwards:

  1. refactor current bundler implement to modulize the queue
  2. implement a queue server which contains the userOp and offer API to operate on them
  3. implement another queue module which use the remote queue as storage
  4. performance test
@skypigr skypigr added the enhancement New feature or request label Apr 4, 2023
@skypigr skypigr self-assigned this Apr 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant