You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This variation in PVG leads to instances where UserOps deemed valid by one bundle are rejected by another.
For instance, a UserOp processed by Skandha yields a PVG of 44668, while 44848 estimates the same operation at 44848, resulting in the rejection of the UserOp from the mempool.
To mitigate this issue, it may be necessary to standardize PVG values across bundler implementations or at least reach consensus on minimum PVG thresholds for a bundle of X to prevent fragmentation of the mempool.
We need a test for this added to the p2p spec test suite as well.
The text was updated successfully, but these errors were encountered:
@ch4r10t33r we're currently working on a standardized way to calculate gas fields for the bundlers. It's a complex issue, and we'll share it over our calls for some feedback.
Although most bundlers adhere to the reference implementation for determining the Pre-Verification Gas (PVG) of a bundle (https://github.com/eth-infinitism/bundler/blob/main/packages/sdk/src/calcPreVerificationGas.ts), discrepancies still arise across different bundler implementations.
This variation in PVG leads to instances where UserOps deemed valid by one bundle are rejected by another.
For instance, a UserOp processed by Skandha yields a PVG of 44668, while 44848 estimates the same operation at 44848, resulting in the rejection of the UserOp from the mempool.
To mitigate this issue, it may be necessary to standardize PVG values across bundler implementations or at least reach consensus on minimum PVG thresholds for a bundle of X to prevent fragmentation of the mempool.
We need a test for this added to the p2p spec test suite as well.
The text was updated successfully, but these errors were encountered: