-
Notifications
You must be signed in to change notification settings - Fork 20.1k
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
Batch eth_call #24089
Comments
It seems like it would make sense to upstream |
Hello, I created feature request for it in 2021 AFAIR. Will try to do it using recent geth and mev code. Will you include it? |
This link is broken. |
This is up-to-date Flashbots docs link (as of today) And here is the mev-geth repo. Look at the It would indeed have been great to have the |
We are still waiting for the spec change to be made before shipping anything in geth. It is likely that a spec change requires a champion who will defend the change in an allcoredevs call. This is to allow other Ethereum client teams to comment on the proposed API. |
For the record, see add support for rpc endpoint eth_callBundle |
Can be closed via #27720. |
Multiple people have requested a variant of
eth_call
where multiple calls can be made in sequence, building up state.Previous requests:
#24025 (comment)
#22810
Implementation
If this is to be implemented, it should be a new RPC method. It could be named
eth_multiCall
oreth_batchCall
, for example.Any implementation of this feature needs to pay attention to the global gas cap: the combined gas usage of all chained calls should not be above this limit.
It's also an interesting question whether state overrides should be allowed per-call or just once.
The text was updated successfully, but these errors were encountered: