Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hardhat: Upgradeable Proxy support for XDC #326

Closed
LogeswaranA opened this issue Sep 19, 2023 · 6 comments
Closed

Hardhat: Upgradeable Proxy support for XDC #326

LogeswaranA opened this issue Sep 19, 2023 · 6 comments

Comments

@LogeswaranA
Copy link

Unable to setup upgradeable proxy contract using Hardhat features. Setup is working fine with other evm compatible blockchain.

Erroring out with "ProviderError: too many arguments, want at most 1"

image

please try this : github.com/GoPlugin/hardhat-proxy

please check the README

@gzliudan
Copy link
Collaborator

gzliudan commented Sep 20, 2023

I reproduced this problem and will debug it later.

@gzliudan
Copy link
Collaborator

gzliudan commented Sep 26, 2023

There's same problem when I use hardhat-upgrades and ethers v6. But I can deploy upgradeable contract to apothem network without problem when I use hardhat-upgrades and ethers v5. So please try ethers v5, it seems that ethers v6 cause this problem.

@LogeswaranA
Copy link
Author

I have tried ethers version 5.7.0, it gives this error message
image

@gzliudan
Copy link
Collaborator

gzliudan commented Oct 7, 2023

Please refer to my PR: GoPlugin/hardhat-proxy#1, main changes:

package.json

    "@openzeppelin/hardhat-upgrades": "^1.28.0",
    "ethers": "^5.7.2",

scripts/deploy.js

  await v1contract.deployed();
  console.log("Contract deployed to:", await v1contract.address);

Below is my test result:

npx hardhat run scripts/deploy.js --network apothem
Deploying samlpe...
Contract deployed to: 0x40A7A3D4746bb459578ceb320fD3E2a6865A1Bb9

@LogeswaranA
Copy link
Author

Working fine now, this issue can be closed.

@gzliudan
Copy link
Collaborator

gzliudan commented Dec 5, 2023

This issue is fixed on testnet now. The patch will be applied on mainnet later.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants