I have a logic contract which I have been able to deploy using @openzeppelin/hardhat-upgrades by following the instructions in the docs // scripts/create-box.js const { ethers, upgrades } = require("hardhat"); async function main() { const Box = await ethers.getContractFactory("Box"); const b…

The factory would provide an on-chain way of creating new instances, whereas deployBeaconProxy would need to be called through a script. It depends on your use case or how you want to deploy the new beacon proxies. In terms of ownership, you are correct that your address that you used to deploy th…

Thanks a lot @ericglau .. For anybody interested in how i went about this eventually. I used an hybrid solution.. I deployed a beacon and implementation using deployBeacon, but i wanted an on-chain solution for the factory. So my factory ended up looking like this // SPDX-License-Identifier: GPL-3.…

Thanks for the example here @gate3 as I'm also doing something similar. I haven't done a ton of testing yet, but I'm thinking the import "@openzeppelin/contracts/proxy/beacon/UpgradeableBeacon.sol"; in your factory contract is unnecessary, correct? Since "upgrades.deployBeacon" creates an Upgrad…

Right, that import doesn't look necessary.

Thanks for pointing this out @scoots .. I should have updated the code showing where I removed it. Will do that, thanks again.

I tried the same solution for my use case. But I am stuck in ownership of the proxy. In the case of the script, the owner is the sender, but in the case of the factory, the owner of the new proxy is the contract. I am still finding a way to transfer the ownership, the transferOwnership of BeaconProx…

@gawshinde There are two different contexts for ownership: the owner of your contract is set in the BeaconProxy, but the owner of the beacon (who has permission to upgrade the beacon) is set in UpgradeableBeacon. This example Deploying Upgradeable Proxies and Proxy Admin from Factory contract - #12…

Just posting this here for anybody that needs a solution in future. Here is a version of my implementation, still needs some update, but it contains testing and all of the basic things you will need to get started. I will update the README and put things in a better shape once I can find the time. S…

My use case is to create contracts for my daap users. When I am using a factory, the creator is the factory, not the sender. As my contract is Role-based, I am finding a way to make my user an owner, as the open sea will either take creator or ownable as owner. Hope I am able to explain. One way is…

@gawshinde Can you just pass in the desired owner (or the msg.sender from the factory) to the initializer, as per the link in my previous post? If you are using AccessControl, then you can use _grantRole in the initializer with the passed in sender.

@gawshinde Take a look at the repo I shared. I passed in the owner as suggested by @ericglau and I also wrote tests to prove it works. You can see here i'm passing the user I want to set as the owner . You just need to change that to the user you want, in my own case I want the factory deployer to s…

How to deploy new instances using beacon proxy from a factory when using @openzeppelin/hardhat-upgrades

Support Upgrades

Topic		Replies	Views
Deploying Upgradeable Proxies and Proxy Admin from Factory contract Upgrades	41	10206	May 17, 2022
How to use BeaconProxy with UpgradeableBeacon Upgrades	3	3142	July 19, 2021
Upgradable ProxyFactory (No CLI) Upgrades	1	1004	March 26, 2021
Upgradable Contracts Deployed By A Factory Contract Using BeaconProxy Review Wanted proxies	0	773	October 13, 2021
Using Beacon proxy pattern with API Contracts upgrades , upgrades-plugins	5	3282	May 31, 2022

How to deploy new instances using beacon proxy from a factory when using @openzeppelin/hardhat-upgrades

Related topics