Fix the inversion order in OracleRef#829
Merged
thomas-waite merged 4 commits intodevelopfrom Jun 1, 2022
Merged
Conversation
Contributor
|
LGTM, waiting for e2e tests to be fixed so we can merge with a green tick |
eswak
approved these changes
Jun 1, 2022
This file contains hidden or 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
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.
Summary
The inversion and scalingFactor in OracleRef are applied in the wrong order, which in a situation where
doInvert = trueandscalingFactory != 0would lead to an incorrect price. The issue was found by Elliott when he was developing a USDC PSM.Info below from his fix in the Volt repo: