Closed bolpol closed 2 years ago
@SwaroopH I can confirm that Mumbai
works now.
Thanks @SwaroopH for fixing this bug, and everyone for helping!
I'm closing this issue now
Hi Everyone!
I just ran into the spoken issue on the polygon's MAINNET.
It worked correctly on the testnet, but I got the issue on the mainnet. Actually I was wondering if any of the other developers here deployed to MANINET. I would bet they did not, otherwise they would have gotten the same issue...
Should the solution not have been the same for both testnet(Mumbai) and MAINNET ?
All mumbai nodes behind MaticVigil RPC are on the new version. Can someone confirm by testing their mumbai endpoint?
If it works well, we'll deploy it to mainnet next week.
Has it been deployed to mainnet?
All mumbai nodes behind MaticVigil RPC are on the new version. Can someone confirm by testing their mumbai endpoint? If it works well, we'll deploy it to mainnet next week.
Has it been deployed to mainnet?
@whitenode32 Yes, it should be live on our mainnet nodes now. Also, best to ping us via a ticket - the team cannot track external Github issues.
The issue seems not to be fixed on the polygon mainnet, I still get a tx hash, but most of the time I can't even see that TX on polygonscan, but if I see it, the from is still the null address...
I just ran into this issue on Polygon mainnet as well. The same script works on Mumbai without flaw.
Going to make sure I've updated my NPM packages.
I cleared out my node_modules
folder and updated to the latest version of hardhat and ethers. Same result. Tried a different RPC URL. Same result.
Tried the patch above about getting the tx hash instead, but it just hangs for 5+ minutes doing nothing.
Going to attempt the deploy plugin.
The hardhat deploy plugin works!
Same here. Tried using infura and alchemy. Hardhat script finished successfully and returns a contract instance with an address but there's nothing on the chain explorer. Works just fine on Rinkeby.
Edit by @alcuadrado: This is an issue with https://rpc-mumbai.maticvigil.com and I have already reported it. In the meantime, using alchemy is a valid workaround.
Incorrect address calculation or set in contract instance. I got this bug only on mumbai test network from polygon.
Expected result: token.address - the same deployed address on block explorer.
Result: token.address - not equal to real deployed contract address.
./scripts/Deploy.ts
./contracts/ERC721Mock.sol
package.json
hardhat.config.ts