crytic / crytic/slither

Improve reentrancy detectors to highlight token-based reentrancy

Open
#933 1 comment 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
Python
Stars
6.4k
Forks
1.1k
PR merge metrics
No merged PRs in 30d

Description

There have been a couple of hacks due to reentrancies on tokens that were detected by Slither, but ignored by developers. We should improve the reentrancies detectors output to highlight if the risks are related to a token (transfer/transferfrom/+
safe versions).

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.