-
Notifications
You must be signed in to change notification settings - Fork 5
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
Added a Morpho Blue integration #1094
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Pull Request Test Coverage Report for Build 9990193146Details
💛 - Coveralls |
jrhea
reviewed
Jul 17, 2024
contracts/src/deployers/morpho-blue/MorphoBlueTarget4Deployer.sol
Outdated
Show resolved
Hide resolved
mcclurejt
approved these changes
Jul 17, 2024
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, comments aren't blocking
lgtm! thanks for this 🙏 |
jrhea
reviewed
Jul 18, 2024
jrhea
reviewed
Jul 18, 2024
jrhea
reviewed
Jul 18, 2024
jrhea
reviewed
Jul 18, 2024
jrhea
reviewed
Jul 18, 2024
e2d415f
to
28110b3
Compare
jrhea
approved these changes
Jul 18, 2024
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.
great work
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Resolved Issues
Fixes: #1099.
Description
This PR adds a Morpho Blue integration. This was a relatively straightforward integration, but there were a few interesting quirks that are worth noting:
MorphoBalancesLib
. This adds a good amount of bytecode to our integrations, so I needed to make ourMorphoBlueConversions
library external.totalSupplyShares
is ~1 million times smaller thantotalSupplyAssets
, so the Morpho Blue vault share price is ~1e12. This results in the napkin math assertions inInstanceTest
that multiply and divide by the vault share price to convert from base to vault shares having large tolerances (1e15). This was somewhat concerning, so I added several additional tests and assertions to verify that our precision isn't negatively effected by the small vault share price. After some significant testing, it seems that the fix for [CRASH REPORT] fuzz invariant -- close long after maturity result is not as expected #697 is working like a charm.Review Checklists
Please check each item before approving the pull request. While going
through the checklist, it is recommended to leave comments on items that are
referenced in the checklist to make sure that they are reviewed. If there are
multiple reviewers, copy the checklists into sections titled
## [Reviewer Name]
.If the PR doesn't touch Solidity, the corresponding checklist can
be removed.
[[Reviewer Name]]
approve
calls useforceApprove
?transfer
calls usesafeTransfer
?transferFrom
calls usemsg.sender
as thefrom
address?token spend?
call
,delegatecall
,staticcall
,transfer
,send
)success
boolean checked to handle failed calls?delegatecall
, are there strict access controls on theaddresses that can be called? It shouldn't be possible to
delegatecall
arbitrary addresses, so the list of possible targets should either be
immutable or tightly controlled by an admin.
nonReentrant
?not a concern or how it's mitigated?
memory variables?
issues?
payable
functions restricted to avoid stuck ether?catch underflows?
Safe
functions are altered, are potential underflows andoverflows caught so that a failure flag can be thrown?
covering the full input space?