-
Notifications
You must be signed in to change notification settings - Fork 6
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
OpenZeppelin Upgrade (ETH-1253) #248
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #248 +/- ##
=======================================
Coverage ? 95.15%
=======================================
Files ? 72
Lines ? 1694
Branches ? 229
=======================================
Hits ? 1612
Misses ? 27
Partials ? 55 ☔ View full report in Codecov by Sentry. |
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.
These look good, and the submodules seem to be pointing to the correct commits in the two repos which we updated: Thanks!
-fd81a96f01cc42ef1c9a5399364968d0e07e9e90 lib/openzeppelin-contracts
-3d4c0d5741b131c231e558d7a6213392ab3672a5 lib/openzeppelin-contracts-upgradeable
Description
The repository currently uses
v4.7.0
of OpenZeppelin's contract. Currently the OZ library is atv5.0.0
.There have been multiple updates, bug fixes & enhancements that have been shipped till now. So, it is optimal to upgrade the library to incorporate the changes and ensure safety.
Here are the contracts that are currently being used in the protocol & the updates that have been performed on them:
We have decided to upgrade from
v4.7.0
tov4.9.3
. We choose not to upgrade tov5.0.0
as it is released recently (Oct 5) and might have undiscovered bugs.Notice
Pull Request Type
Breaking changes (if applicable)
The following functions are not available as external function on TUPProxy. However, they can be called by passing the function call in data:
Testing
Additional comments
We had to change the inheritance order for the following files to satisfy the C3 linearisation criteria: