internal/ethapi: eth_multicall

[s1na]

This is a successor PR to #25743. This PR is based on a new iteration of the spec: ethereum/execution-apis#484.

eth_multicall takes in a list of blocks, each optionally overriding fields like number, timestamp, etc. of a base block. Each block can include calls. At each block users can override the state. There are extra features, such as:

• Include ether transfers as part of the logs
• Overriding precompile codes with evm bytecode
• Redirecting accounts to another address

Breaking changes

This PR includes the following breaking changes:

• Block override fields of eth_call and debug_traceCall have had the following fields renamed
  • coinbase -> feeRecipient
  • random -> prevRandao
  • baseFee -> baseFeePerGas

[wjmelements]

There's no reason to have a multicall interface. Either you can have one call do the multicalls or you can use batch jsonrpc.

Please reject this PR.

[s1na]

you can use batch jsonrpc.

No.

Either you can have one call do the multicalls

I believe you're referring to https://github.com/mds1/multicall. You're not able to set msg.sender to an arbitrary address there. eth_multicall simply provides much more flexibility for different simulation scenarios, allowing users to customize various EVM context fields.