Skip to content
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

code coverage tracking during onchain fuzzing #50

Open
elizabethdinella opened this issue Apr 27, 2023 · 2 comments
Open

code coverage tracking during onchain fuzzing #50

elizabethdinella opened this issue Apr 27, 2023 · 2 comments

Comments

@elizabethdinella
Copy link

Hi, is it possible to track the code coverage percentage during onchain fuzzing as it progresses?

@shouc
Copy link
Contributor

shouc commented Apr 27, 2023

Unfortunately, there is not any elegant way to do this. We will implement a test coverage evaluator based on testcase before next Wednesday.

@shouc
Copy link
Contributor

shouc commented Apr 27, 2023

Nevertheless, coverage is not a good representation of the completeness of fuzzing for smart contracts, esp. for DeFi. During our research, we observe that most of the sequences of exploit (e.g., https://github.com/SunWeb3Sec/DeFiHackLabs/blob/main/src/test/AES_exp.sol#L45-L47 needs 37x same txns to increase one-side liquidity) do not end up increasing path/branch/instruction coverage over time. Likely due to path/branch/instruction coverage can not encode stateful transitions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants