Halmos Test Properties migrated to Certora #747
Conversation
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
…lastUpdateCannotDecrease, irmCannotBeDisabled, lltvCannotBeDisabled, idToMarketParamsForCreatedMarketCannotChange
MathisGD
reviewed
Jan 6, 2026
MathisGD
reviewed
Jan 6, 2026
MathisGD
approved these changes
Jan 7, 2026
This was referenced Jan 7, 2026
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.
We intend to remove the halmos tests in Morpho Blue. This PR introduces certora rules for Halmos tested properties that were already not proved with Certora.
Interestingly, the properties
lastUpdateNonZeroandlastUpdateCannotDecreaseneeded an assumption that timestamp is <= max_uint128. Else, the explicit cast here can makelastUpdatedzero. Surprisingly, this was not required in Halmos. Time permitting, we can create a halmos bug report.