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

[Hardhat] Fix No known hardfork for execution on historical block problem #57

Closed
Tracked by #70
acuarica opened this issue Oct 4, 2024 · 0 comments · Fixed by #64
Closed
Tracked by #70

[Hardhat] Fix No known hardfork for execution on historical block problem #57

acuarica opened this issue Oct 4, 2024 · 0 comments · Fixed by #64
Assignees
Labels
feature Enhancing an existing feature driven by business requirements. Typically backwards compatible.

Comments

@acuarica
Copy link
Contributor

acuarica commented Oct 4, 2024

When running a test against a "not" well-known forked network, Hardhat raises the following error

     ProviderError: No known hardfork for execution on historical block 10016755 (relative to fork block number 10016755) in chain with id 296. The node was not configured with a hardfork activation history.

Given the following issues, it looks like some sort of Hardhat regression

That's why we had to add hre.network.provider.send('hardhat_mine', ['0x001']) in our Hardhat tests as a workaround.

The issue for Optimism and Arbitrum was fixed here (as a temporary workaraound)

However, the definitive fix to this problem is being tracked here

In any case, for our purposes we need to setup a hardfork in the plugin so we free our users to do so. See https://hardhat.org/hardhat-network/docs/guides/forking-other-networks#using-a-custom-hardfork-history for more details.

We can think of sending a PR to Hardhat's repo so they can add Hedera chains as well in the future.

Note

I tried to setup the chains config for Hedera networks within extendProvider, but it didn't work. I guess we need to use extendConfig to fill in the hardfork chains early in the setup process.

@acuarica acuarica added the feature Enhancing an existing feature driven by business requirements. Typically backwards compatible. label Oct 4, 2024
@acuarica acuarica self-assigned this Oct 6, 2024
@acuarica acuarica moved this from Backlog to Sprint Backlog in Smart Contract Sprint Board Oct 6, 2024
@acuarica acuarica linked a pull request Oct 7, 2024 that will close this issue
2 tasks
@github-project-automation github-project-automation bot moved this from In Review to Done in Smart Contract Sprint Board Oct 8, 2024
@se7enarianelabs se7enarianelabs changed the title Fix No known hardfork for execution on historical block problem [Hardhat] Fix No known hardfork for execution on historical block problem Nov 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature Enhancing an existing feature driven by business requirements. Typically backwards compatible.
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

1 participant