crytic/slither

Create detectors for semantic changes due to Solidity IR

Open

#1,169 创建于 2022年4月14日

在 GitHub 查看
 (2 评论) (1 反应) (0 负责人)Python (4,769 star) (886 fork)batch import
High Priorityhelp wanted

描述

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.

贡献者指南

技术栈
python
领域
securityblockchain
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
4
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
3-5 days
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
Familiarity with Solidity IR breaking changesKnowledge of Slither detector development
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
40
研究方向
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.