I have an upgradable smart contract that I deploy on each chain with the same unused key pair in order to get the same deployment address on each chain.
The deployment is carried out using hardhat and the OZ library code
On Mumbai, due to the weird gas pricing, the first transaction took forever to be confirmed and timed out after the first contract was deployed. I have since verified the contract that was actually deployed.
Is there any way to complete the deployment of the other two contracts rather than starting over which would cause the contract address to be wrong?
You can see the contract at 0x1e8150050A7a4715aad42b905C08df76883f396F on
but looking at the deployer key on Mumbai you will see that only the business logic was deployed
If the implementation was already deployed, and you just want to deploy a proxy, you can use the useDeployedImplementation option when calling deployProxy to ensure that it does not redeploy the implementation.