mythril VS coreth

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

Subnet-EVM APIs are identical to Coreth APIs, except Avalanche Specific APIs starting with avax. Subnet-EVM also supports standard Ethereum APIs as well. For more information about Coreth APIs see here.

C-Chain runs a fork of go-ethereum called coreth that has the networking and consensus portions replaced with Avalanche equivalents. What's left is the Ethereum VM, which runs Solidity smart contracts and manages data structures and blocks on the chain. As a result, you get a blockchain that can run all the Solidity smart contracts from Ethereum, but with much greater transaction bandwidth and instant finality that Avalanche's revolutionary consensus enables.

Subnet EVM is the Virtual Machine (VM) that defines the Subnet Contract Chains. Subnet EVM is a simplified version of Coreth VM (C-Chain).

I just meant that the Avalanche C-chain is literally based off the Ethereum protocol (see https://github.com/ava-labs/coreth). It's a wrapper around Go Ethereum so that it works with Avalanche's consensus mechanism. Under this wrapper the C-chain still uses a blockchain the way Ethereum does, in contrast with Avalanche's X-chain.

No. C-chain EVM uses portions of geth as a plugin library to handle Solidity stuff, stripping out all the networking, consensus and all other functionality irrelevant to Avalanche. Avalanche node itself is a separate repo, and that is where all the exciting stuff actually happens.

Source: https://github.com/ava-labs/coreth/pull/114/files#diff-9a870b1572ea65697aea0a8f959e0ee20efa4ff3370c3e39dcc2f3ec436b4fc3R212