Not able to use a different `from` account for upgrades.upgradeProxy
See original GitHub issueAccording to the documentation, one should be able to upgrade a Proxy contract to a new logic contract via:
const newProxy = await upgrades.upgradeProxy(proxy.address, newMain, { deployer })
However, I’ve tried changing deployer
to a different account, and the caller of the transaction is always the same.
I’m using hardhat, not truffle.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:2
- Comments:8 (7 by maintainers)
Top Results From Across the Web
Execute upgrade using different signer - OpenZeppelin Forum
Not able to use a different `from` account for upgrades.upgradeProxy ... According to the documentation, one should be able to upgrade a Proxy ......
Read more >plugin-hardhat upgradeProxy upgradeTo call doesnt await ...
I'm deploying a proxy contract and its implementation using "deployProxy" instruction but I get a "Timed out waiting for transaction" error. I ...
Read more >Using the UUPS proxy pattern to upgrade smart contracts
UUPS is a gas-efficient proxy pattern that allows underlying logic to be upgraded when needed, without losing previous data.
Read more >How to Make A Contract Upgradeable via OpenZeppelin Proxies
Learn how to use proxies to upgrade contracts! ... You will be able to deploy a version 1 contract, add new functionality and...
Read more >Web3 Tutorial: write upgradeable smart contract (proxy) using ...
If you transfer ProxyAmin ownership to a multi-sig account, the authority to upgrade the Proxy contract (link proxy to new implementation) is ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Yes, for example in
hardhat.config.js
:Closing in favor of https://github.com/OpenZeppelin/openzeppelin-upgrades/issues/85.