-
Notifications
You must be signed in to change notification settings - Fork 3
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
idle fix #581
Merged
Merged
idle fix #581
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
Hyperdrive Gas Benchmark
This comment was automatically generated by workflow using github-action-benchmark. |
jrhea
commented
Sep 22, 2023
jrhea
commented
Sep 22, 2023
jrhea
commented
Sep 22, 2023
jrhea
commented
Sep 22, 2023
jrhea
commented
Sep 22, 2023
jrhea
commented
Sep 22, 2023
jrhea
commented
Sep 22, 2023
jrhea
commented
Sep 22, 2023
jrhea
commented
Sep 22, 2023
jrhea
commented
Sep 22, 2023
jrhea
commented
Sep 22, 2023
jrhea
commented
Sep 22, 2023
jalextowle
reviewed
Sep 25, 2023
jalextowle
reviewed
Sep 25, 2023
jalextowle
reviewed
Sep 25, 2023
jalextowle
reviewed
Sep 25, 2023
jalextowle
reviewed
Sep 25, 2023
jalextowle
reviewed
Sep 25, 2023
jalextowle
reviewed
Sep 25, 2023
jalextowle
reviewed
Sep 25, 2023
jalextowle
approved these changes
Sep 25, 2023
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.
This is looking great! Nice job broski. Just a few nits, and then let's .
Co-authored-by: Alex Towle <[email protected]>
Co-authored-by: Alex Towle <[email protected]>
* make exposure updates more specific to close functions vs applyCheckpoint * Update test/integrations/hyperdrive/NonstandardDecimals.sol * address review comments
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.
idle fix
Fixes #367, #397.
A detailed explanation of the issue and fix is given in the issue, but the TL;DR is that the previous implementation of the conservation of present value dealt with excess idle funds only during
removeLiquidity
, which created situations in which the active LPs had control over idle funds that would ultimately go to the withdrawal pool. This PR fixes this issue by updating the logic used to pay out the withdrawal pool incloseLong
andcloseShort
.netting fix
In order for the idle fix to work properly, a modification was made to how we update the checkpoint exposure. the tl;dr is that we only zero out checkpoint exposure when: