Making upgrade proposal using defender.proposeUpgrade on GNOSIS chain returns ProviderError: VM execution error

Support Defender
,
1

I've reproduced example of upgrading contract by making upgrade proposal from this guide https://docs.openzeppelin.com/defender/guide-upgrades#propose-the-upgrade and faced with issue at GNOSIS chain, and the same code works well on RINKEBY

:computer: Environment
specially prepared project with installed packages from guide https://docs.openzeppelin.com/defender/guide-upgrades#propose-the-upgrade RINKEBY chain and GNOSIS chain

:memo:Details
after deployment proxy and implementation from the guide there are two examples:

defender.proposeUpgrade run successfully on rinkeby:

npx hardhat run --network rinkeby scripts/propose-upgrade.js

successfull result on rinkeby:

Preparing upgrading  0xa290667e309548e8dD15aF3ab43a84432055BC97  proposal...
Upgrade proposal created at: https://defender.openzeppelin.com...

Issue with defender.proposeUpgrade on gnosis chain:

npx hardhat run --network gnosis scripts/propose-upgrade.js

error on gnosis:

Preparing upgrading  0x8d01Cf3556FE12188FF565ECD0689Ec6A5D9C1b7  proposal...
ProviderError: VM execution error.
    at HttpProvider.request (/Users/.../DefenderUpgrade/node_modules/hardhat/src/internal/core/providers/http.ts:78:19)
    at LocalAccountsProvider.request (/Users/.../DefenderUpgrade/node_modules/hardhat/src/internal/core/providers/accounts.ts:188:34)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at getImplementationAddressFromBeacon (/Users/.../node_modules/@openzeppelin/upgrades-core/src/impl-address.ts:30:25)
    at isBeacon (/Users/.../node_modules/@openzeppelin/upgrades-core/src/beacon.ts:11:5)
    at Proxy.proposeUpgrade (/Users/.../node_modules/@openzeppelin/hardhat-defender/src/propose-upgrade.ts:48:16)
    at main (/Users/.../DefenderUpgrade/scripts/propose-upgrade.js:17:20)

Contracts in both network are transparentUpgradeable proxy and code verified:

gnosis proxy (TransparentUpgradeableProxy) 0x8d01Cf3556FE12188FF565ECD0689Ec6A5D9C1b7

rinkeby proxy (TransparentUpgradeableProxy) 0xa290667e309548e8dD15aF3ab43a84432055BC97

:1234: Code to reproduce
I've made demonstrating repository, showing good working upgrade proposal at RINKEBY and the error at GNOSIS chain https://github.com/KiselevMaxim/DefenderUpgrade

2

Hi @KiselevMaxim, thank you for reporting this issue. This is now fixed in the upgrades plugins. Please update the @openzeppelin/upgrades-core package to the latest version e.g.:

npm install --save-dev @openzeppelin/upgrades-core@latest
1 Like
3

Hi! Thank you very much, the problem been fixed!

1 Like