-
Notifications
You must be signed in to change notification settings - Fork 933
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Detector: Detect the use of low level calls #27
Comments
Issue Status: 1. Open 2. Started 3. Submitted 4. Done This issue now has a funding of 100.0 DAI (100.0 USD @ $1.0/DAI) attached to it as part of the Ethereum Community Fund via ECF Web 3.0 Infrastructure Fund fund.
|
In progress. |
PR opened: #36 |
Thanks for your contribution! |
PR #36 merged, thanks again @cryptomental ! @mkosowsk can you also validate the bounty? thx! |
Issue Status: 1. Open 2. Started 3. Submitted 4. Done Work has been started. These users each claimed they can complete the work by 7 months, 1 week from now. 1) cryptomental has been approved to start work. Hi. I would like to pick up this bounty as well together with variable names detector. Estimated time for the pull request: Friday EOD at the latest. Learn more on the Gitcoin Issue Details page. |
@cryptomental please submit your work via the the Gitcoin Issue Details page and I will send over bounty ASAP. Thanks! 👍 |
Thanks @cryptomental! But don't thank me, thank the Ethereum Community Fund 👍 See you on the next bounty! |
ECF rocks! See you! |
Low-level calls are more prone to errors
Hint: Use slithIR to detect if an operation is a LowLevelCall
The text was updated successfully, but these errors were encountered: