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
There is a conflict with the @openzepplin/hardhat-upgrades library that requires using the nativeContractFactory object when deploying a beacon proxy if the tenderly automagic setup() is used.
Expected Behavior:
const{ ethers, upgrades }=require("hardhat");constcode=awaitethers.getContractProxy("someContract");constbeacon=awaitdeployBeacon(code);constbeaconProxy=awaitupgrades.deployBeaconProxy(beacon.address,code,[...])console.log("my beacon proxy has been deployed with tenderly!")
Instead this is the required modification for this to work:
const{ ethers, upgrades }=require("hardhat");constcode=awaitethers.getContractProxy("someContract");constbeacon=awaitdeployBeacon(code);constcode_native=code.nativeContractFactory;constbeaconProxy=awaitupgrades.deployBeaconProxy(beacon.address,code_native,[...])console.log("my beacon proxy has been deployed with tenderly!")
Would love to get that supported 🙏 BeaconProxies are amazing and something we utilize everywhere.
The text was updated successfully, but these errors were encountered:
The problem here is that hardhat-tenderly is overriding the ethers library used by the hardhat-upgrades library.
So deployBeacon returns our TdlyContractFactory instead of the ethers.ContractFactory.
And the workaround is as you have described.
We'll see to provide a proper solution for this so our users don't have to use these workarounds. 😢
Btw, we have implemented automatic verification of the proxy contracts that are deployed using the hardhat-upgrades library. So you can check that out!
There is a conflict with the
@openzepplin/hardhat-upgrades
library that requires using thenativeContractFactory
object when deploying a beacon proxy if the tenderly automagic setup() is used.Expected Behavior:
Instead this is the required modification for this to work:
Would love to get that supported 🙏 BeaconProxies are amazing and something we utilize everywhere.
The text was updated successfully, but these errors were encountered: