We deployed a v5 TransparentUpgradeableProxy contract by passing an already created ProxyAdmin contract to the constructor. As v5 is creating a new ProxyAdmin in the constructor, we have now been ending up with our contract whose ProxyAdmin is owned by another ProxyAdmin who is in turn owned by another private key.
Is there a way to get out of this situation?
Hey @Quentin_Adam,
Sorry to hear this, if I'm correct, I don't see an easy workaround since the ProxyAdmin can't make custom calls to a target, therefore it can't call the transferOwnership on the recently created ProxyAdmin.