-
Notifications
You must be signed in to change notification settings - Fork 15
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
program verification of smart contracts #9
Comments
The Certora Verification Language (often abbreviated CVL) isa language used to write specifications for smart contracts.: |
|
https://github.com/crytic/slither a static analyzer avaialable through a CLI and scriptable interface. resources: https://github.com/crytic/building-secure-contracts/blob/master/program-analysis/slither |
Manticore is a symbolic execution tool for the analysis of smart contracts and binaries. |
Evolution of Automated Weakness Detection in Ethereum Bytecode: a Comprehensive Study. |
https://github.com/crytic/building-secure-contracts/tree/master/program-analysis |
Awesome testing tools for Web3 and Blockchain |
The K Framework is a tool for designing and modeling programming languages and software/hardware systems K Semantics of the Ethereum Virtual Machine (EVM):
(written in Java) |
End-to-End Formal Verification of Ethereum 2.0 Deposit Contract in K (staking) |
Hi @monperrus, I’m trying to use the VerX client script to verify a Solidity contract. but I’m not sure how to obtain a username and password. Is this information available to all users, or is it restricted to certain members? |
don't know, this is not the official repo of VerX. best regards, --Martin
|
Design and Implementation of Static Analyses for Tezos Smart Contracts |
Deductive verification of smart contracts with Dafny
|
Towards benchmarking of Solidity verification tools compares SolCMC and Certora |
Solvent: liquidity verification of smart contracts |
Practical Verification of Smart Contracts using Memory Splitting |
Surveys:
A Survey of Smart Contract Formal Specification and Verification. ACM Comput. Surv. 2022
Awesome:
The text was updated successfully, but these errors were encountered: