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

[all] Dynamic bundle size priced PVG #978

Open
dancoombs opened this issue Jan 29, 2025 · 0 comments
Open

[all] Dynamic bundle size priced PVG #978

dancoombs opened this issue Jan 29, 2025 · 0 comments
Assignees
Labels
enhancement New feature or request prevent-stale Prevent an issue from closure due to being stale

Comments

@dancoombs
Copy link
Collaborator

Describe the feature
Currently all PVG calculations assume a bundle size of 1. This requires the user to pay for:

  • Intrinsic gas
  • Bundle calldata & DA cost
  • Shared aggregator cost

The bundler can often create bundles > size 1, and currently has no way of sharing those cost savings with the user.

This feature is around enabling users to take advantage of larger bundles resulting in lower cost

Additional context

High level:

  • PVG estimation can be done at different bundle sizes.
    • This is likely the hardest part of the feature, what bundle size should be used? Should the bundler suggest? Should the user choose?
  • Precheck should be lenient about the PVG
    • Choose a fixed bundle size to compare to
  • Pool eligibility should also be done at a certain bundle size - either fixed or suggested by the builder
  • Bundle building algo should include all UOs who have sufficient PVG for the bundle size and current DA costs
    • This is also difficult, what algo should be used here?

On the current signature-aggregator branch a few of the bundle size assumptions are tagged with // TODO(bundle) for quick lookup.

@dancoombs dancoombs added enhancement New feature or request prevent-stale Prevent an issue from closure due to being stale labels Jan 29, 2025
@dancoombs dancoombs self-assigned this Jan 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request prevent-stale Prevent an issue from closure due to being stale
Projects
None yet
Development

No branches or pull requests

1 participant