-
Notifications
You must be signed in to change notification settings - Fork 91
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
Refactor to ERC20Ubiquity
#644
Comments
Could you provide a rough time estimate for implementation? I'm assuming it can be done within a day.
We wanted to preserve the ability to rename. Is there a way to prioritize this while not breaking the functionality of @zgorizzo69 what do you think about this proposal? |
All these tasks can indeed be accomplished within a day. However, i would recommend a separate task for the refactoring to use solmate. This should be addressed after initial refactor, and it could require additional time. |
@pavlovcik The |
this issue should be resolved before this refactor; |
Please feel free to create the bounty when you're ready. |
Yep valid points thanks @eugenioclrc |
/start |
1 similar comment
/start |
Skipping |
@pavlovcik @zgorizzo69 im having some issues here, with this refactor i have remove multiple lines, that means that coverage metrics will get lower (the ERC20Permit lib is excluded from coverage), thats why its not passing the coverage task in the github actions. |
nevermind, i solved, it seems that somehow the coverage thought that the method |
Do you have any updates @eugenioclrc? If you would like to release the bounty back to the DevPool, please comment |
@pavlovcik @zgorizzo69 the work is ready, why the bot is asking if I have finished? |
My apologies. Unfortunately @zgorizzo69 hasn't had the time to review yet and their review is required to merge pull requests on this repository. I sent them a message to check soon. Thanks for your patience! In the future the bot will check for the review status to not follow up with the bounty hunter unless needed. |
[ CLAIM 200 DAI ]
|
There are a few things to solve in
ERC20Ubiquity
ERC20Burnable
is not usedERC20Permit
implementation,ERC20Ubiquity
could use it to have a simpler contract_tokenName
and_symbol
is already set in theERC20
it should be redefinedname
andsymbol
should not change, also if the admin change it, it will create conflicts with theDOMAIN_SEPARATOR
see ERC20Ubiquity.sol#L64I would also recommend to implement solmate ERC20 implementation, is more gas efficient and it has
ERC20Permit
by default but you will have to do a deeper refactor.The text was updated successfully, but these errors were encountered: