[Hardhat] Fix No known hardfork for execution on historical block
problem
#57
Labels
feature
Enhancing an existing feature driven by business requirements. Typically backwards compatible.
When running a test against a "not" well-known forked network, Hardhat raises the following error
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 withinextendProvider
, but it didn't work. I guess we need to useextendConfig
to fill in the hardforkchains
early in the setup process.The text was updated successfully, but these errors were encountered: