crytic / crytic/building-secure-contracts

Highlight differences & strengths of echidna vs. other fuzzers (like foundry)

Open
#174 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Solidity
Stars
2.5k
Forks
391
PR merge metrics
No merged PRs in 30d

Description

Some things that could be covered:
- ease-of-use/difficulty in setting up the framework
- compatibility with solidity versions
- framework's areas of focus (echidna is e.g. better at property/invariant-testing whereas foundry is great for scripting/deployments & unit-tests)
- create a baseline of different fuzz/invariant tests that should be found and benchmark these

Contributor guide

Open the contributing guide

Research direction

No file or test is named. Start by locating the repository’s existing guidance on Echidna, Foundry, fuzzing, and invariant testing, then define the comparison scope and Solidity versions to cover. Done means a documented comparison plus a reproducible baseline of fuzz and invariant tests with benchmark results.

Written by the indexing model from the issue text.

Assessment

Tech stack
solidity
Domain
blockchain, documentation, testing
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.