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 (886 forks)batch import
High Priorityhelp wanted

Repository metrics

Stars
 (4,769 stars)
PR merge metrics
 (Avg merge 54d 9h) (2 merged PRs in 30d)

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

Research direction
Study the IR breaking changes documentation and create detectors for each semantic only change listed.
Tech stack
python
Domain
security
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
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.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Needs investigation
Prerequisites
SolidityPython
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60