-
Notifications
You must be signed in to change notification settings - Fork 20.4k
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 rpc endpoint eth_callBundle #29862
Comments
Sina is working on an alternative of it, check out #27720 for more information |
Right I believe #27720 should be able to serve this use-case. From what I understand what you're proposing takes already mined transactions as input. eth_simulateV1 does not do that, it takes call args as in eth_call. But that's just a matter of doing |
great!
any valid transaction can be given as input to eth_callBundle, not only already mined ones. |
We will not add |
ack. for the record, the current work on eth_simulateV1 lives at ethereum/execution-apis#484 |
Rationale
It would be useful to add support for a new RPC endpoint
eth_callBundle
that supports speculatively study of the execution of a sequence of transactions.What are the use-cases?
eth_callbundle
Known existing implementations:
See a draft implementation at release/1.14...NaliFinance:mev-geth:release/1.14
Implementation of eth_callBundle
eth_callBundle
can be used to simulate a bundle of transactions against a specific block number, including simulating a bundle at the top of the next block. Theeth_callBundle
RPC has the following payload format:example:
example response:
The text was updated successfully, but these errors were encountered: