-
Notifications
You must be signed in to change notification settings - Fork 11.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Draft EIP 1820 #1677
Draft EIP 1820 #1677
Conversation
Gah I forgot to update how the test helpers are used when updating the version. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good!
Co-Authored-By: nventuro <nicolas.venturo@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Thanks!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👏!
Closes #1676.
I only added the interface for the registry itself (the contract can be deployed in a testing environment using
openzeppelin-test-helpers
), as well asIERC1820
andERC1820
, which are intended to be used by contracts that will be registered in the global registry.I chose those names to mimic the
ERC165
naming scheme we already have (where a contract inherits fromERC165
in order to indicate that it supports an interface, and contracts may cast addresses toIERC165
to query support).It'd also be nice to provide some sort of way to get an instance of the global registry without having the user hardcode its address, e.g. some sort of factory that returns
IERC1820Registry(0x1820b744B33945482C17Dc37218C01D858EBc714)
.