I cannot deploy upgrade contract on matic with openzeppelin

Support Upgrades
1

maticupgrade
maticupgrade1296×1518 114 KB

I can successfully deploy on eth with the same code,but not on the matic mainnet,

2

Check that you're using the correct RPC node and that you have matic tokens in your deployer account.

3

matic-main-config-network
matic-main-config-network1786×372 44.6 KB

I use the default config,what tokens should i have?

4

You need matic tokens to deploy on matic.

5

Thank you,Where can I get tokens ?

6

If it's on mainnet, you have to buy it. If it's on their testnet https://faucet.matic.network/ but it seems like you're trying to deploy on mainnet.

7

I have matic tokens,I just cannot deploy upgrade contract,I can deploy normal contract successfully.

8

@pageone Can you confirm if you can run a non-upgradeable deployment against Matic? Just by using Ethers.js built in deploy.

9

I can deploy a non-upgradeable,I use truffle

10

Can you publish this in a repository so that I can try it?

11

1.truffle migrate --network mumbai -f 1 --to 1
then
2. truffle migrate --network mumbai -f 2 --to 2

12

I've found that the cause of the error is that the RPC endpoint is responding with this error, to one of the eth_getStorageAt requests:

{
  details: 'Internal RPC Error. Try again after some time..',
  code: -32005
}

The fact that this is not showing as an error in the console could be a problem in our Upgrades Plugin or in Truffle, it's not clear to me at this point.

But the underlying cause is this RPC response. I'll see if I can get any more information...