-
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
update rounding behavior in calculateSolvencyAfterShort
#1061
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
dpaiton
requested review from
jalextowle,
jrhea,
mcclurejt,
cashd and
sentilesdal
as code owners
June 17, 2024 22:37
dpaiton
changed the title
update rounding behavior in solvency check
update rounding behavior in Jun 17, 2024
calculateSolvencyAfterShort
Pull Request Test Coverage Report for Build 9555621955Details
💛 - Coveralls |
jalextowle
reviewed
Jun 17, 2024
jalextowle
reviewed
Jun 17, 2024
jalextowle
reviewed
Jun 17, 2024
jalextowle
reviewed
Jun 17, 2024
jalextowle
approved these changes
Jun 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 once the nits are addressed.
Pull Request Test Coverage Report for Build 9555779516Details
💛 - Coveralls |
Hyperdrive Gas Benchmark
This comment was automatically generated by workflow using github-action-benchmark. |
Pull Request Test Coverage Report for Build 9555912671Details
💛 - Coveralls |
Pull Request Test Coverage Report for Build 9555967822Details
💛 - Coveralls |
dpaiton
force-pushed
the
dpaiton/update-solvency-check
branch
from
June 17, 2024 23:24
aff8116
to
57240de
Compare
Pull Request Test Coverage Report for Build 9556234202Details
💛 - Coveralls |
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
working towards delvtech/hyperdrive-rs#29
Description
The solvency after short check used
divDown
to convert from base to shares, but the open short function usesdivUp
. Therefore it was possible to have the solvency check say "all good" and then open short reverts. This fixes that problem.I also added some intermediate checks so that the function fails gracefully in more situations.
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?