Proxy admin is not the one registered in the network manifest

[megatower66]

Hi @abcoathup, thanks for your reply!

@abcoathup

I would add a step before.

0. Run unit tests on implementation contracts (v1 and v2 etc).
   Run higher level tests on the upgradeable contracts (interact via the proxy).
   See OpenZeppelin Upgrades: Step by Step Tutorial for Truffle for an example.

Step 0 is a nice touch, it's so basic and my fault I didn't write it down earlier!

@abcoathup

I would recommend after deployment to look at using a multi-sig to manage the upgrades.
See: https://docs.openzeppelin.com/learn/preparing-for-mainnet#set-admin

I actually wanted to use below in the migration script (post deployment) as mentioned here

await admin.transferProxyAdminOwnership(gnosisSafe);

But post migration of admin to a Gnosis safe address, how would one use upgradeProxy directly in the migration scrip? I guess that's not possible and one would have to rather use prepareUpgrade and then use OpenZeppelin app in the Gnosis web app? I'm referring to the full steps mentioned in OpenZeppelin Upgrades: Step by Step Tutorial for Truffle

I'd much rather change the admin back to my metamask wallet (how to do that using Gnosis?) , do the upgrade using upgradeProxy directly in migration in order not to copy paste address of the proxy (box.address, address of AdminUpgradeabilityProxy) and the address of the new implementation (boxV2.address, again address of new AdminUpgradeabilityProxy) in Gnosis safe web app.

But even if I was willing to manually copy-paste in the interest of security, how would I able to call another contract function from my Gnosis safe address? Is it possible?