You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Hi, is it possible to track the code coverage percentage during onchain fuzzing as it progresses?
The text was updated successfully, but these errors were encountered: