You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't know how hard this would be for implementers to support, but it would be nice to be able to simulate after e.g. the second transaction in a block.
Workaround is for the user to handle it: make a mainnet fork at height N, download block N+1, and then replay the first k transactions before doing analysis.
Well, maybe it could be a non-standard/optional feature like how some providers have nonstandard trace_* and debug_* methods.
The text was updated successfully, but these errors were encountered:
I think it makes sense. Geth's eth_call already has 2 optional (non-standard) parameters. I guess a 3rd one could be considered. But now's a good time to raise this for the coming eth_multicall #383.
I don't know how hard this would be for implementers to support, but it would be nice to be able to simulate after e.g. the second transaction in a block.
Workaround is for the user to handle it: make a mainnet fork at height N, download block N+1, and then replay the first k transactions before doing analysis.
Well, maybe it could be a non-standard/optional feature like how some providers have nonstandard trace_* and debug_* methods.
The text was updated successfully, but these errors were encountered: