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

Running hardhat trace --hash on arbitrum nova fails "block has a different hardfork than the vm" #46

Open
kasumi-1 opened this issue May 16, 2023 · 1 comment

Comments

@kasumi-1
Copy link
Contributor

I believe the fix is to add skipHardForkValidation: true, to the following two lines:

await vm.runTx({ tx: txWithCommon, block });

await vm.runTx({ tx: txWithCommon, block });

It looks like hardhat also skips this validation in some spots, but I am unfamiliar enough with codebase to not know if this could cause issues without some other check in place. The above change worked for me locally.

zemse added a commit that referenced this issue May 19, 2023
@zemse
Copy link
Owner

zemse commented May 19, 2023

Thanks for reporting, I've added the fix and published in 2.3.1. Do let me know if there are any issues with it.

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