building-secure-contracts VS mythril

I appreciate how organized the Consensys guide is laid out. It's pretty easy to read. Trail of Bits has a similar guide that is a little more in-the-weeds technically. It also covers, what we think is, essential background about certain automated analysis techniques like static analysis and how fuzzers work. Check it out!

https://secure-contracts.com/

We highly recommend using at least one of them if professional contract security review is not possible. A more comprehensive look into secure development practices can be found here.

If you need more reading about building secure smart contracts and auditing workflows, see here: https://github.com/crytic/building-secure-contracts

Fuzzing has been around for a while in traditional full-stack development, but a new class of tools is here that can apply fuzzing to smart contract testing in web3. Some of the fuzzing tools include the open source Echidna and MythX.

Mythril is part of the core tools of Consensys Mythx one of the biggest Smart Contract security services for Ethereum, which main goal is to ensure development teams avoid costly errors and make Ethereum more secure and trustworthy… or at least that is what their page says.

Other than audits and testing, there's automated security checking: https://github.com/ConsenSys/mythril I'm yet to try this in one of my projects

Mythril

MythX, Mythril, Manticore, and Echidna are other tools for security audits.

Smart Contract Weakness Classification and Test Cases: https://swcregistry.io/ OKO Contract Explorer: https://oko.palkeo.com/txview Slither: https://github.com/crytic/slither MythX: https://mythx.io/ Tenderly: https://tenderly.dev/ Spot check program: https://docs.google.com/document/d/16...

There are some paid tools and some free ones. A few that come to mind are ConsenSys MythX (based in part on the open-source Mythril), ShiftLeft, Oyente, Octopus… maybe best to just check out ETHSecurity’s list.

When you say "formal verification methods", what kind of techniques are you interested in? While using interactive theorem provers will most likely not become very widespread, there are plenty of tools that use formal techniques to give more correctness guarantees. These tools might give some guarantees, but do not guarantee complete functional correctness. WireGuard (VPN tunnel) is I think a very interesting application where they verified the protocol. There are also some tools in use, e.g. Mythril and CrossHair, that focus on detecting bugs using symbolic execution. There's also INFER from Facebook/Meta which tries to verify memory safety automatically. The following GitHub repo might also interest you, it lists some companies that use formal methods: practical-fm

- Audited by MythX.io

ability to run security analysis on contracts using for .e.g. https://github.com/ConsenSys/mythril