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
dumpState/loadState only dumps/loads the EVM state. I'm working on a multi-nodal testing environment where I control block production (making Kurtosis not a candidate for this environment) and was hoping for dumpState/loadState be usable to cause one Anvil instance's blockchain to become another Anvil instance's.
Since dumpState/loadState only explicitly covers the EVM state, I now have one instance with a bunch of blocks, one instance with no blocks, and two indexers on my end with different results.
I'm not explicitly requesting a behavior change in dumpState/loadState and am fine if this is introduced as dumpChain/loadChain.
Additional context
No response
The text was updated successfully, but these errors were encountered:
Came here to request this feature for a different reason. I'd like to simulate a specific scenario of transactions and then run (non-foundry) scripts against them. The scenario uses cheats to advance the blocktime, and the script I'm testing is dependent on time passing. Of course I can execute all of the transactions every time to prepare the state / blocks, but this takes a while. LoadState doesn't work since the state is loaded, but the advances in block time are not accounted for.
zerosnacks
changed the title
Cheat to save/load the blockchain
feat(anvil): ability to dump / load state including the blockchain history, not just resulting state
Jul 16, 2024
Component
Anvil
Describe the feature you would like
dumpState/loadState only dumps/loads the EVM state. I'm working on a multi-nodal testing environment where I control block production (making Kurtosis not a candidate for this environment) and was hoping for dumpState/loadState be usable to cause one Anvil instance's blockchain to become another Anvil instance's.
Since dumpState/loadState only explicitly covers the EVM state, I now have one instance with a bunch of blocks, one instance with no blocks, and two indexers on my end with different results.
I'm not explicitly requesting a behavior change in dumpState/loadState and am fine if this is introduced as dumpChain/loadChain.
Additional context
No response
The text was updated successfully, but these errors were encountered: