-
Notifications
You must be signed in to change notification settings - Fork 55
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
[pool] Explore local tracing with revm #840
Comments
This would be made obsolete if Geth (and other major node providers) offer a native tracer and major RPC providers offer access: ethereum/go-ethereum#30546 |
Potential issue here: a degenerate case UO that doesn't use a ton of gas, but reads a bunch of large contracts. This would be limited by gas usage, but that doesn't seem to scale correctly with the amount of data retrieved by the prestate. Same with doing a ton of SLOADs. We'd have to analyze the data retrieval costs for these degenerate cases. |
Hello, may I kindly ask a question regarding this thread? I am using the RIP-7212 in L2 like Arbitrum Sepolia or Optimism Sepolia, even these L2s support P256 precompiled, the Alchemy Bundler will return error for missing precompiled in validation step currently right? |
Rundler's validation tracer will allow RIP-7212 if the node that is doing the tracing supports it
|
Hello, I’m still encountering an error related to the RIP-7212 precompile when using
Could you please share when Rundler is expected to support this feature? Thanks a lot!
|
AA23 is coming directly from the entry point - so I don't believe this is a Rundler issue. It seems the validation step is trying to access a precompile that the node doesn't support. |
I am using the Alchemy Bundler directly instead of my local rundler. |
If you can replicate this with a local Rundler, please open a separate ticket with a way to replicate. If this is an Alchemy specific question, please use the Alchemy Discord. The "MissingPrecompile" error that you have above does not come from Rundler, but form some unknown smart contract - so please include those details in the separate ticket if you can replicate. |
Describe the feature
Tracing is by far our largest latency performance bottleneck. Due to the complexities of getting custom native tracers installed on nodes (especially when using 3rd party RPCs), Rundler always uses a javascript tracer, causing the latency issue.
A different approach to this would be to do tracing locally using revm.
How this would work:
prestateTracer
on the normal RPC. This should be supported by all 3rd party RPCs.Some caveats:
Another approach could be to attempt to use revm on top of alloydb and remove the prestate tracing, but that may require too many network calls to be high performance.
The text was updated successfully, but these errors were encountered: