Closed
Conversation
Member
|
I think this proposal is a good idea. I recommend as a next step requesting feedback on ACD. The next one is tomorrow! |
Member
|
@s1na is currently working on a very similar endpoint here: ethereum/go-ethereum#25743 |
Author
|
Sure thanks! |
Author
|
Closing in favor of PR #312. The return interface specified over there is array of |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The
eth_callexecutes every message call on the latest state and then discards the state. When someone wants to inspect a state that would be after a transaction would go through, currently it involves a non cheap way, i.e. using the mainnet fork (like ganache/hardhat network/anvil) to confirm the first tx and then query state on it, which makes a lot of rpc calls. This PR proposes addition ofeth_multicallto the JSON-RPC spec.This method enables following use cases:
eth_calls from frontends, similar to makerdao/multicall (more efficiently since it does not need to execute multicall contract code)Closes #267