crytic/slither

Identify Functions that use delegatecall and msg.data for Echidna Printer

Open

#1,202 opened on May 9, 2022

View on GitHub
 (3 comments) (0 reactions) (0 assignees)Python (4,769 stars) (886 forks)batch import
echidnaenhancementgood first issue

Description

Describe the desired feature

Echidna should be able to access implementation contracts via a proxy contract that utilizes delegatecall with msg.data. This will allow easier fuzzing on proxy contracts. Currently, the user needs to create a wrapper for each of the functions that are in the implementation contract.

Ideally, the Slither printer would extract functions that use msg.data and associate the functions of the called contract into the calling contract.

Contributor guide

Tech stack
python
Domain
blockchaintooling
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Understanding of delegatecallSlither printer internalsProxy contractsSolidity static analysis
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
25
Research direction
First, review the existing Slither printers to understand the pattern. Then, analyze the Solidity AST for delegatecall and msg.data usage. Consider implementing a new printer that outputs functions using these patterns. Check the comments in the issue for additional details.