OpenZeppelin Upgrades: Step by Step Tutorial for Hardhat

Smart Contracts Guides and Tutorials
,
44

Please do not ask the same questions everywhere, one time is enough. Thanks!

45

Great tutorial! However - in my case I deploy multiple contracts on multiple networks and thus I have multiple deploy scripts in different files. Before migrate all my contracts to upgradeable contracts I was using hardhat-deploy plugin and the way I was getting the addresses of the already deployed contracts was:
const contractAddress = await deployments.get("MyContract");
Is there a similar functionality on hardhat-upgrades plugin?

Other way around if to use hardhat-deploy for deploying upgradeable contracts, but the control over the deploy is not so good as well as I am getting some error that shows the hardhat-deploy adds for instance UUPSUpgradeable to my contract (I already have it and there is a collision).

46

We currently don't have a feature like deployments.get and our recommendation is to write this data to a JSON file or similar in your deployment scripts.

Can you elaborate and the error you see with hardhat-deploy?

47

5 posts were split to a new topic: How do function interactions work with a proxy

48

I've done this:

import { Box, Box__factory } from '../typechain-types';

let Box: Box__factory;
let box: Box;

// Start test block
describe('Box (proxy)', function () {
    beforeEach(async function () {
        Box = await ethers.getContractFactory("Box");
        box = await upgrades.deployProxy(Box, [42], { initializer: 'store' }) **as** Box;
    });
50

Hi @Dimitar_Stoyanov,
You can manage multiple deployments on multiple networks by using my UUPS Hardhat boilerplate: https://github.com/gabrielstoica/hardhat-upgrades. I've put together some scripts to easily interact with UUPS smart contracts using an Ownable or AccessControl role-based mechanism.