That little change allows calling execute on an unknown address in a way hardhat-deploy defines.
Use-case: You have a factory contract that deploys a child contract. Currently, there is no way to interact with them unless you import ethers and use them. However though, I was receiving a REPLACEMENT_ERROR which I believe popped up due to nonce not being incremented in the hardhat-deploy instance.
Simply yet, this addition should drop the need for ethers for such use cases.
dalechyn
commented
1 year ago
That little change allows calling
executeon an unknown address in a wayhardhat-deploydefines.Use-case: You have a factory contract that deploys a child contract. Currently, there is no way to interact with them unless you import
ethersand use them. However though, I was receiving aREPLACEMENT_ERRORwhich I believe popped up due to nonce not being incremented in thehardhat-deployinstance.Simply yet, this addition should drop the need for
ethersfor such use cases.