Timed out waiting for implementation contract deployment [RINKEBY]

Support Upgrades
1

Getting this error when deploying upgradeable contract to rinkeby:

Error: Timed out waiting for implementation contract deployment to address "0x756f30387E2B19d732bAF062D9A21a8076B7088e" with transaction "0x38717c906e16a7852211e8f558eade945387d43823777bcd7d89b6555e1bab6f"

Run the function again to continue waiting for the transaction confirmation. If the problem persists, adjust the polling parameters with the timeout and pollingInterval options.

The transaction has been pending for quite some time now.

Rinkeby etherscan is still saying:

" This txn hash was found in our secondary node and should be picked up by our indexer in a short while.

A curious thing to note is that my teammate in a European country was able to deploy it with ease using the same config and params; but I currently being in a South Asian country am facing this pending transaction.

The network config is as follows:

networkCheckTimeout: 999999,
      timeoutBlocks: 200,
      gas: 12400000,
      gasPrice: 1110000000,

The same has worked on kovan without any problems.

In addition, is there any way I can force redeploy the proxy+implementation via hardhat? As of now, running the deploy script continues waiting for the above transaction.

:1234: Code to reproduce

npx hardhat run scripts/deployUpgradeable.js --network rinkeby

:computer: Environment

Hardhat

Packages:

    "@nomiclabs/hardhat-etherscan": "^2.1.5",
    "@openzeppelin/contracts": "^4.5.0",
    "@openzeppelin/contracts-upgradeable": "^4.5.2",
    "@openzeppelin/hardhat-upgrades": "^1.17.0",
2

Perhaps try using a different RPC endpoint.

In addition, is there any way I can force redeploy the proxy+implementation via hardhat? As of now, running the deploy script continues waiting for the above transaction.

This isn't supported. If this is for testing only, then you can manually delete the entry that contains the txHash 0x38717c906e16a7852211e8f558eade945387d43823777bcd7d89b6555e1bab6f under the impls section of .openzeppelin/rinkeby.json. But you should avoid manually editing that file for production scenarios.

1 Like
3

What worked for me is manually overriding the max gas and priority gas values:

Does this mean Rinkeby is more gas hungry than other test nets?