It is necessary to add support for upgradeable smart contracts

Question

It is necessary to add support for upgradeable smart contracts

Closed this issue 2 years ago · 6 comments

Answer 1 · 2022-11-08T16:04:43.000Z

I too think we need to support upgradeable smart contracts.

Answer 2 · 2022-11-08T17:22:57.000Z

Thanks for creating an issue! What problems are you encountering with integrating OperatorFilterer or DefaultOperatorFilterer into an upgradeable smart contract?
It's true that ExampleERC721 and ExampleERC1155 are not upgradeable, but they are intended only as examples of how to integrate the project into a new smart contract.

Answer 3 · 2022-11-08T17:29:23.000Z

when i try to use DefaultOperatorFilterer in UUPS proxy implementation, Hardhat shows error:

Error: Contract ... is not upgrade safe

contracts/DefaultOperatorFilterer.sol:9: Contract DefaultOperatorFilterer has a constructor
Define an initializer instead
https://zpl.in/upgrades/error-001

contracts/OperatorFilterer.sol:12: Contract OperatorFilterer has a constructor
Define an initializer instead
https://zpl.in/upgrades/error-001

Answer 4 · 2022-11-08T17:30:06.000Z

I want to use openzeppelin-upgrades.
There are some restrictions to do so.

https://github.com/OpenZeppelin/openzeppelin-upgrades

Answer 5 · 2022-11-09T18:35:05.000Z

Thank you - we will be adding contracts that follow OpenZeppelin's upgradeable pattern sometime today.

Answer 6 · 2022-11-09T20:50:49.000Z

This should be addressed with PR #13. Please reopen if you run into more issues.