Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Methods (e.g. eth_call, eth_getStorageAt) don't take transactionIndex, only blockNumber #466

Open
llllvvuu opened this issue Sep 6, 2023 · 1 comment

Comments

@llllvvuu
Copy link

llllvvuu commented Sep 6, 2023

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.

@s1na
Copy link
Contributor

s1na commented Sep 19, 2023

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants