ca be implemented using alloy support https://docs.rs/alloy-provider/latest/alloy_provider/struct.EthCall.html#method.overrides

Happy to do an implementation of this if there is some guidance as to what the interface/flags should look like from a core developer. I have a specific use case relating to balance overrides so wouldn't to propose something that fits only that.

Happy to do an implementation of this if there is some guidance as to what the interface/flags should look like from a core developer. I have a specific use case relating to balance overrides so wouldn't to propose something that fits only that.

thank you! probably best should be an --state-overrides to take the json with all balance, state, nonce, code overrides per address, same as the one passed to eth_call

thank you! probably best should be an --state-overrides to take the json with all balance, state, nonce, code overrides per address, same as the one passed to eth_call

Ok, there is no desire to parse individual overrides similar to other flags like --labels as outlined in my original post?

thank you! probably best should be an --state-overrides to take the json with all balance, state, nonce, code overrides per address, same as the one passed to eth_call

Ok, there is no desire to parse individual overrides similar to other flags like --labels as outlined in my original post?

I think I missed that but not part of state overrides we support in alloy https://docs.rs/alloy-rpc-types-eth/0.13.0/alloy_rpc_types_eth/state/struct.AccountOverride.html
can you pls detail where it goes in eth_call?

I am referring to if, instead of a json object, we want to pass in more CLI-friendly formatted arguments. For example the --labels argument on cast call uses a format of a list of address:label pairs rather that some structured data like JSON. If we were to follow this patten for override commands it might be more convenient as in most cases I assume people only wish to override one or two things.

Something like:

• --override-balance "0xAAAA:1234,0xBBBB:5678"
• --override-nonce "0xAAAA:5,0xBBBB:10"
• --override-code "0xAAAA:0xCODEBYTES"
• --override-state "0xAAAA:0xSLOT:1234,0xBBBB:0xSLOT:5678"
• --override-state-diff "0xAAAA:0xSLOT:1234,0xBBBB:0xSLOT:5678"

I am not entirely sure what move_precompile_to field does, but it would presumably just be --override-move-precompile-to "0xADDR".

To me this seems more CLI-friendly than a JSON blob as a single --state-overrides flag.

ah, I see, wasn't familiar with labels switch. For storage slots the format could become a little bit too much but I think makes sense overall. @zerosnacks @yash-atreya wdyt re proposed args?

Could always add both and have a --override flag that takes in a JSON object for people with large state overrides and such? All the args would be merged together at the end.

sgtm!

I made a PR for this, would really appreciate your help with a review. Main problem is that I'm not sure how to test this. I've added some basic tests, but I'm not satisfied with them.