Open
Conversation
Verification
Reruns for fixes
Kel/cleanup
Bump to sui 1.65.2
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
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.
Add Certora formal verification specs and CI
This PR introduces Certora's formal verification of the Suilend liquid staking protocol, along with a GitHub Actions workflow to run verification automatically on PRs against main.
What's included
Formal Specification
Verification rules under
certora/spec/covering 10 property groups:For details on individual rules, assumptions, and running instructions, see
certora/README.mdfile.CI Integration
Contains a workflow file
.github/workflows/certora.ymlthats runs the full Certora verification suite on PRs targeting themain(and thecertorabranch), using the Certora/certora-run-action. Verification jobs are run in the Certora cloud and results are posted back to the PR viaGITHUB_TOKEN. Requires aCERTORAKEYrepository secret to be set to a valid Certora key.Note on munges
Verification requires patching the source code before running, mainly to widen the visibility of internal functions. These patches live in
certora/munges/and must be kept in sync with the source. If the patched files change, verification will fail to apply and CI will break. See the README for instructions on maintaining regenerating patches.