crytic / crytic/echidna

Feature request: Always show from address in fuzzing results

Open
#778 3 comments 0 reactions 0 assignees View on GitHub
Dominant language
Haskell
Stars
3.2k
Forks
432
Avg merge
1d 20h
Merged PRs (30d)
5

Description

I use echidna in `multi-abi` mode with a lot of addresses in the `sender` list. It seems like echina only shows the addresses if there are different addresses used in the call sequence. I'd like to always see the addresses

Perhaps you can add the address once at the top or the bottom somewhere. Having a setting in echidnas config to always show it beside every line would also work.

Example without addresses
```
testSomething(): failed!💥
Call sequence, shrinking (4301/5000):
incCounter()
incCounter()
incCounter()
testSomething()
```

Adding the address once (my suggestion)
```
testSomething(): failed!💥
from address: 0x6Ecbe1DB9EF729CBe972C83Fb886247691Fb6beb
Call sequence, shrinking (4301/5000):
incCounter()
incCounter()
incCounter()
testSomething()
```

Example with addresses (DVDeFi Unstoppable)
```
flashloan(): failed!💥
Call sequence:
transfer(0x1d7022f5b17d2f8b695918fb48fa1089c9f85401,157) from: 0x6Ecbe1DB9EF729CBe972C83Fb886247691Fb6beb Time delay: 27935 seconds Block delay: 50328
flashloan() from: 0xE36Ea790bc9d7AB70C55260C66D52b1eca985f84 Time delay: 39749 seconds Block delay: 5377
```

Thanks :)

Contributor guide

Open the contributing guide

Research direction

The issue does not identify a source file, test, or entry point. Start by locating the code and tests that render fuzzing call sequences in multi-abi mode, then verify that a from address is shown even when the sequence uses only one address; done means the requested output is covered without breaking existing address output.

Written by the indexing model from the issue text.

Assessment

Tech stack
haskell, solidity
Domain
security, testing-qa
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.