-
Notifications
You must be signed in to change notification settings - Fork 11.9k
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
Governor, TimelockController, and similar, should be ERC721Holder #3174
Comments
I 100% agree this should be a thing. These contracts should be There is an issue however: |
Good point. We will have to include the logic without using ERC721Holder. |
@ashwinYardi Yes, and also |
No, the MinimalForwarder is completely unrelated. It's only supposed to forward call, not ever receive any assets. If it did receive assets, anyone could likely claim them (unless they are forwarder aware, but that is unlikely). We should NOT put these functions in the MinimalForwarder, as it might prevent someone from inadvertently sending assets to it. |
Ahh, all right! Will revert the changes I did in MinimalForwarder 😅 |
* add ERC721 and ERC1155 receiver support in Governor, Timelock and MinimalForwarder (#3174) * revert the nft receiver hooks from MinimalForwarder and linting updates * add ERC165 support & simplify test * add changelog entry Co-authored-by: Hadrien Croubois <[email protected]>
Contracts that can send arbitrary transactions through some protocol, like Governor and TimelockController, should contain the required hook to receive ERC721 tokens via
safeTransfer
(which we implement inERC721Holder
).I think there is a similar hook for ERC1155.
The text was updated successfully, but these errors were encountered: