Skip to content
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

[Certora] Check not liquidatable position equivalence #81

Closed
QGarchery opened this issue Oct 5, 2024 · 5 comments · Fixed by #89
Closed

[Certora] Check not liquidatable position equivalence #81

QGarchery opened this issue Oct 5, 2024 · 5 comments · Fixed by #89

Comments

@QGarchery
Copy link
Contributor

The requires computation was changed in de168dd, so now this is exactly the same as in Morpho Blue. But we could still verify that this is equivalent to checking that ltv <= LLTV.

Originally posted by @QGarchery in #77 (comment)

@QGarchery QGarchery mentioned this issue Oct 5, 2024
2 tasks
@MathisGD MathisGD changed the title Check not liquidatable position equivalence [Certora ]Check not liquidatable position equivalence Oct 6, 2024
@MathisGD MathisGD changed the title [Certora ]Check not liquidatable position equivalence [Certora] Check not liquidatable position equivalence Oct 6, 2024
@colin-morpho
Copy link
Contributor

colin-morpho commented Oct 7, 2024

Done in #37, if I'm not mistaken. See,

rule preLiquidatableEquivlLtvLTPreLltv() {

@QGarchery
Copy link
Contributor Author

Actually I'm talking about the other require-statement, where we want to show the equivalence ltv <= LLTV <=> borrowed <= collateralQuoted.wMulDown(LLTV)

@QGarchery
Copy link
Contributor Author

QGarchery commented Oct 17, 2024

Nice !

A similar proof, for the require (and it's comment) just next to it actually

@colin-morpho
Copy link
Contributor

colin-morpho commented Nov 4, 2024

This done in #89. See

rule borrowedLECollatQuotedTimesLLTVEqLtvLTEqLLTV {

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants