[Certora] Simplify veirifcation configuration #466
Closed
+35
−19
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
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.
This PR closes #465.Following the observation that the specification Protected consists of a single parametric rule, we simplify the setup.
This configuration now targets a dummy contract and list all the contracts on which the parametric rule should be checked. This requires to have the spec to not depend on the current contract.
This simplifies the verification setup and eases maintenance as there's a single configuration.
This idea wouldn't work as the spec is fundamentally contract dependent, for instance the value of
initiator()is not independent of each contract.