OpenZeppelin / OpenZeppelin/openzeppelin-contracts
Add `deregisterInterface` to ERC165
Nobody has claimed this yet.
- Dominant language
- Solidity
- Stars
- 27.2k
- Forks
- 12.4k
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 33
Description
@Amxx suggested adding such a function to the Cairo version of the ERC165 module in case a smart contract stops supporting an interface after an upgrade. I'd like to open the discussion on whether such a feature would be desired.
I don't think i've seen much literature around smart contract interface compatibility across upgrades, so I'm not sure how such a feature would be received in the wider ecosystem. In Cairo-land at least, we're considering a massive interface change during network regenesis, where such a feature makes sense.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the proposed Cairo ERC165 change referenced in the linked pull-request comment and the network regenesis context. Determine whether deregistering an interface is desired for upgraded smart contracts; done would require a decided scope and an agreed feature specification, neither of which the issue currently provides.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- solidity
- Domain
- blockchain
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100