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
anvil feat: support forking at transaction level #5810
Comments
we already have this functionality in forge, which we could also enable in anvil
if you're using a local node without any rate limits, ptal at the |
@ChinW can you assign this issue to me |
@mattsse hi, I wonder if you know, when using |
good point, this currently does not use the no rate limit option foundry/crates/evm/src/executor/fork/multi.rs Lines 474 to 488 in cdba273
foundry/crates/evm/src/executor/fork/multi.rs Lines 276 to 279 in cdba273
and uses fixed values for some reason foundry/crates/evm/src/executor/fork/multi.rs Lines 235 to 237 in cdba273
we definitely want support for this, I think the easiest way would be to use the values of the foundry/crates/evm/src/executor/fork/multi.rs Line 262 in cdba273
via this would be an easy fix, do you want to take this @ChinW ? converting this into an issue |
Component
Anvil
Describe the feature you would like
hi team, like #3262
would like also have this feature in anvil project, also happy with some guidance to contribute back.
by the way, I would like to confirm my below understanding of forking:
I am forking eth network with block number by using private eth full node, found out multicall is very slow in this environment (couple minutes, > 5 minutes), while same calls on latest block number (no forking) is very very fast (<1 minute).
Is it because inside the box, the local forking node is actually requesting the remote full node with lots of
getStorageAt
request, so that make it slow. If true, I guess if I put the local forking test program into the full node machine, it should be much much faster. Is my understanding correct?Additional context
No response
The text was updated successfully, but these errors were encountered: