I have an upgradeable proxy contract that looks like the below: pragma solidity 0.8.15; // SPDX-License-Identifier: MIT import {TransparentUpgradeableProxy} from "@openzeppelin/contracts/proxy/transparent/TransparentUpgradeableProxy.sol"; contract MyContract is TransparentUpgradeableProxy { con…

You're welcome! I think you do need to use the Upgradeable versions because those are the ones that are initializable. In reality, the upgradeability needs to be enabled by using a proxy (or manually adding the upgradeability functions with UUPS), so by using ERC20Upgradeable as an implementation f…

Hey @NethDote , if I'm understanding correctly, you're trying to make clones of a single implementation. This pattern is usually called a "Factory" and can be accomplished by using the Clones library with an upgradeable contract although it's not required to be upgradeable. The reason for using an u…

Hi Ernesto, Thanks, that's really helpful. Some clarifications: [image] ernestognw: you're trying to make clones of a single implementation No, the goal is to be able to make clones of different implementations, including implementations not written yet that may have different constructor/i…

No, the goal is to be able to make clones of different implementations, including implementations not written yet that may have different constructor/initialization requirements. Then I'd say the use case is the same but the code is even more simple, look: contract CloneFactory { event Clone…

Awesome, thanks Ernesto. And just so I am clear then: in the implementations, I can now safely use "Pausable.sol" and "ERC20.sol". I can stop using "PausableUpgradeable.sol" and "ERC20Upgradeable.sol" because they are only necessary when upgrades happen.

Hey Ernesto, Thanks for all your help so far, one more quick question. I have executed this factory code: address clone = Clones.clone(implementation); Address.functionCall(clone, initializationData); emit CloneCreated(clone); Then I go into Remix, and I paste in the source code of the imp…

Ignore above, it does work exactly as I described in Remix. (I was pasting in the wrong address)

Hey @eeshenggoh , perhaps the term "non upgradeable" proxy is not the best here, so let's refer to them as just Clones. The Clones is a special type of Proxy standardized in EIP-1167 and offered in OpenZeppelin Contracts . As any other proxy, its purpose is to forward all requests to an implementatio…

How to implement a non-upgradeable proxy with constructor/initializer calls that can have varying signatures?

Smart Contracts

eeshenggoh March 28, 2024, 5:59am 9

Hi, I need some help with my question, in regards to purpose of using non-upgradeable vs upgradeable proxies? Why would anyone wants to use non-upgradeable proxies?

Topic		Replies	Views
What's the difference between upgradable and non upgradable Initializable contracts? Aren't all proxies meant to be support upgradable implementation contract? Contracts proxies	5	281	April 1, 2024
Contract factory for upgradeable erc721 Contracts erc721 , proxies , design	13	4952	April 28, 2022
How do upgradeable Clones work? Upgrades	1	2245	June 29, 2021
Does a minimal proxy contract that creates clones need an upgradeable smart contract Contracts	2	1204	June 8, 2022
Clone smart contract upgradeable Upgrades proxies	0	638	August 31, 2021

How to implement a non-upgradeable proxy with constructor/initializer calls that can have varying signatures?

Related topics