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.