Support eth_call state override set

[selimekim94]

Why should this feature exist?
state override set makes eth_call even more powerful and allows for deep code analyses.

Advantages of state override set (from geth docs):

• It can be used by DApps to reduce the amount of contract code needed to be deployed on chain. Code that simply returns internal state or does pre-defined validations can be kept off chain and fed to the node on-demand.
• It can be used for smart contract analysis by extending the code deployed on chain with custom methods and invoking them. This avoids having to download and reconstruct the entire state in a sandbox to run custom code against.
• It can be used to debug smart contracts in an already deployed large suite of contracts by selectively overriding some code or state and seeing how execution changes. Specialized tooling will probably be necessary.

[tclemos]

It's a pending feature, as mentioned here:

zkevm-node/docs/json-rpc-endpoints.md

Line 15 in cf79378

- `eth_call` _* doesn't support state override at the moment and pending block_

geth ref: https://geth.ethereum.org/docs/interacting-with-geth/rpc/ns-eth#3-object---state-override-set

[georgeroman]

Is there any ETA on this?

[tclemos]

@selimekim94 @georgeroman
We are discussing internally about this feature and we are going to start working on this now.
We will use this issue to track this feature.
The current plan is to have it available in the v0.5.0.

[txgyy]

@selimekim94 @georgeroman We are discussing internally about this feature and we are going to start working on this now. We will use this issue to track this feature. The current plan is to have it available in the v0.5.0.

Hi, have you supported it now?

[balqaasem]

Hi @tclemos , @selimekim94 , @georgeroman Is this still in the roadmap, if yes when are you planning to support it pls?

[Jongsic]

Hello!
The zkevm node implements most of the eth namespace functions, which is a remarkable achievement. However, I am very curious about when this state override feature, essential for running the Bundler component of the Ethereum EIP-4337(Account Abstraction), will be resolved. I know a big major update is being prepared, but it seems that a merge request for this issue (#2660) is also somewhat prepared. I would like to know if it could be provided through a minor update.