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
Make ERC20Votes independent from ERC20Permit #3816
Make ERC20Votes independent from ERC20Permit #3816
Conversation
Co-authored-by: Francisco <frangio.1@gmail.com>
…es/openzeppelin-contracts into refactor/erc20-votes
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.
Need to add back numCheckpoints
and checkpoints
.
Co-authored-by: Francisco <frangio.1@gmail.com>
Co-authored-by: Francisco <frangio.1@gmail.com>
Co-authored-by: Francisco <frangio.1@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.
Thanks!
Congrats, your important contribution to this open-source project has earned you a GitPOAP! GitPOAP: 2022 OpenZeppelin Contracts Contributor: Head to gitpoap.io & connect your GitHub account to mint! Learn more about GitPOAPs here. |
Isn't it an issue that inheriting from both ERC20Permit and ERC20Votes would reuse same nonces for 2 different actions? I would suggest to refactor |
Proposed these changes here: #3848 |
Fixes #3160
This PR introduces a new contract,
Nonces
, to be used where keeping track of nonces is required. Also, ERC20Votes will now be inherited directly from EIP712 instead of using ERC20Permit.This is a breaking change due to the changes in the storage layout.
PR Checklist