-
Notifications
You must be signed in to change notification settings - Fork 9
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
Add support for debug_traceCall to EVM GW API #530
Comments
Can we get it estimated and prioritized as it is blocking Alchemy ERC-4337 bundler. Which then is blocking 2 integration P1 partners for us? |
@SeanRobb what is the expected tracer configuration they will want to use? the same one as we currently support for trace transaction? |
@franklywatson @AnukeG do we have an answer for @sideninja question? |
By tracer config are you referring to the Geth If so, we currently use Our usage is here (Rust): https://github.com/alchemyplatform/rundler/blob/7b5097f537b25b504951584df6f3bc18fdb29d68/crates/sim/src/simulation/v0_7/tracer.rs#L155 |
FYI this needs to include state_overrides to meet ERC-4337 integration requirements |
@franklywatson Can we have a sample JSON-RPC request with this, so we can try it out during development? |
Partner responded with:
Attached is a request/response payload example from another chain, however, bear in mind it won't run on Flow given it's for another network |
Thanks @franklywatson , I have made some working examples of JavaScript tracer with state overrides. |
Just to make sure this isn't forgotten, ERC-4337 also requires |
That's a good call out 👍 Currently |
This endpoint is required for ERC-4337 integration
https://geth.ethereum.org/docs/interacting-with-geth/rpc/ns-debug#debugtracecall
The text was updated successfully, but these errors were encountered: