Create detectors for semantic changes due to Solidity IR
Open
help wanted
High Priority
- Dominant language
- Python
- Stars
- 6.4k
- Forks
- 1.1k
- PR merge metrics
- No 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
Start with the linked Solidity 0.8.13 IR semantic-only changes documentation and turn each documented risk into a detector scope. Define how the detectors should identify affected contracts and what public output and validation would demonstrate that the work is complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, solidity
- Domain
- compilers, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100