crytic/slither

Create detectors for semantic changes due to Solidity IR

Open

#1,169 opened on Apr 14, 2022

View on GitHub
 (2 comments) (1 reaction) (0 assignees)Python (4,769 stars) (886 forks)batch import
High Priorityhelp wanted

Description

https://docs.soliditylang.org/en/v0.8.13/ir-breaking-changes.html#semantic-only-changes

0.8.13 allows to use of the new IR pipeline, but comes with risks due to semantics changes. We should create detectors to help developers to review if they can use the new version without impacting their contracts.

We can make these detectors directly public to help a larger audience.

Contributor guide

Tech stack
python
Domain
securityblockchain
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.
3-5 days
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
Familiarity with Solidity IR breaking changesKnowledge of Slither detector development
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Review the linked Solidity documentation (https://docs.soliditylang.org/en/v0.8.13/ir breaking changes.html#semantic only changes) to understand the semantic changes. Examine existing detectors in the Slither repository (e.g., in slither/detectors/) to understand the API and patterns. The issue comments may provide additional guidance. Implement detectors for each semantic change, ensuring they are properly tested and documented.
Create detectors for semantic changes due to Solidity IR · crytic/slither#1169 | Good First Issue