Skip to content

Built-in ERC-4337 tracer #30546

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

Closed
s1na opened this issue Oct 3, 2024 · 1 comment · Fixed by #31006
Closed

Built-in ERC-4337 tracer #30546

s1na opened this issue Oct 3, 2024 · 1 comment · Fixed by #31006
Assignees

Comments

@s1na
Copy link
Contributor

s1na commented Oct 3, 2024

ERC-4337 networks rely now on a JS tracer to protect bundlers from DoS attacks. Given this step has to be performed "for free" it is important for bundlers to have it optimized. Having it as a native tracer will go a long way in speeding up this validation.

@s1na s1na self-assigned this Oct 3, 2024
@noam-alchemy
Copy link
Contributor

Adding a bit more context here:

  • validation rules have been codified into (ERC-7562)[https://eips.ethereum.org/EIPS/eip-7562] which is shared between 4337 and other proposals like 7560.
  • An example native go tracer can be found here. Another example JS tracer can be found here.

s1na added a commit that referenced this issue May 20, 2025
This PR introduces a new native tracer for AA bundlers. Bundlers participating in the alternative
mempool will need to validate userops. This tracer will return sufficient information for them to
decide whether griefing is possible. Resolves #30546

---------

Co-authored-by: Sina M <[email protected]>
Dargon789 pushed a commit to Dargon789/go-ethereum that referenced this issue May 27, 2025
This PR introduces a new native tracer for AA bundlers. Bundlers participating in the alternative
mempool will need to validate userops. This tracer will return sufficient information for them to
decide whether griefing is possible. Resolves ethereum#30546

---------

Co-authored-by: Sina M <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants