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

Implement submitBatch in the BundleBulker #2

Closed
kristofgazso opened this issue Dec 17, 2023 · 1 comment · Fixed by #3
Closed

Implement submitBatch in the BundleBulker #2

kristofgazso opened this issue Dec 17, 2023 · 1 comment · Fixed by #3

Comments

@kristofgazso
Copy link

Currently you can only submit 1 userop in the BundleBulker

It would be useful to be able to submit multiple userops, each with its own specified inflator (which can differ for ops in the same batch)

Maybe could also have another one for the case when all the ops in the batch have the same inflator, so you don't need to specify the inflator for each and you can save some calldata

@dcposch
Copy link
Member

dcposch commented Dec 18, 2023

BundleBulker is unopinionated and supports arbitrary bundles.

The example inflator is a proof-of-concept that makes bundles containing a single ERC20 transfer op.

I've added a second inflator that works the way you describe: you can submit n ops, each specifying their own per-op inflator. See #3

Why not make made BundleBulker always do that?

I want to support compression across ops, not just of individual ops. For example, an IInflator could use LibZip from Solady.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants