Skip to content
This repository was archived by the owner on Jul 29, 2026. It is now read-only.
This repository was archived by the owner on Jul 29, 2026. It is now read-only.

Explore shared mempool between multiple bundler instance #23

Description

@skypigr

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

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions