-
Notifications
You must be signed in to change notification settings - Fork 198
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
feat: add erc4337 endpoint methods to provider #1176
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cool, I think the only thing missing is serde rename all camelcase
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm, if you want you can add additional endpoints defined in the eip
Thanks for approving, the test that I have added is a filler one and needs some touchups. Okay, I will the additional endpoints. Thanks 🫡 |
this doesn't fully compile yet |
pushing fix |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please rename it from eip to erc
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
a more concrete set of changes needed - we need to distinguish that anything related to this is an erc. there is not an eip-4337. thanks for taking this on:)
Thank you for suggesting these changes. Actually, I saw a eip4337 file in the main branch and followed that naming. I have now renamed it as well. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm!
looks like the tests are failing - ptal |
I have run these tests on a different RPC to check if the responses in the tests are valid and they are! Hopefully, the tests pass in the CI, otherwise, we remove them? Because people will be connecting alloy provider to RPCs that support the operation? Let’s see! |
@mattsse Build working. |
great! thanks for this |
Motivation
Closes: #1111
Solution
PR Checklist