Empirical review of automated analysis tools on 47,587 Ethereum smart contracts
Abstract
Domain fit: AI-adjacent · Paper appears method- or tooling-adjacent to AI workflows with partial ecosystem coverage.
Over the last few years, there has been substantial research on automated\nanalysis, testing, and debugging of Ethereum smart contracts. However, it is\nnot trivial to compare and reproduce that research. To address this, we present\nan empirical evaluation of 9 state-of-the-art automated analysis tools using\ntwo new datasets: i) a dataset of 69 annotated vulnerable smart contracts that\ncan be used to evaluate the precision of analysis tools; and ii) a dataset with\nall the smart contracts in the Ethereum Blockchain that have Solidity source\ncode available on Etherscan (a total of 47,518 contracts). The datasets are\npart of SmartBugs, a new extendable execution framework that we created to\nfacilitate the integration and comparison between multiple analysis tools and\nthe analysis of Ethereum smart contracts. We used SmartBugs to execute the 9\nautomated analysis tools on the two datasets. In total, we ran 428,337 analyses\nthat took approximately 564 days and 3 hours, being the largest experimental\nsetup to date both in the number of tools and in execution time. We found that\nonly 42% of the vulnerabilities from our annotated dataset are detected by all\nthe tools, with the tool Mythril having the higher accuracy (27%). When\nconsidering the largest dataset, we observed that 97% of contracts are tagged\nas vulnerable, thus suggesting a considerable number of false positives.\nIndeed, only a small number of vulnerabilities (and of only two categories)\nwere detected simultaneously by four or more tools.\n
Results and benchmarks
Over the last few years, there has been substantial research on automated\nanalysis, testing, and debugging of Ethereum smart contracts.
Benchmark evidence is limited
Evidence graph: 3 refs, 3 links.
Utility signals: depth 70/100, grounding 75/100, status medium.
Implementation
No direct implementation yet
Maintained implementation evidence is not confirmed for this paper yet.
Use the implementation status and reproduction sections for the current action plan.
No verified maintained repo yet
There is no verified maintained implementation yet. Use this baseline plan to decide whether to prototype now or defer.
- No maintained paper-verified implementation was found; start with the closest related repositories below.
- Compare repo methods against the paper equations/algorithm before trusting metrics.
- Create a minimal baseline implementation from the paper and use adjacent repos as references.
Time to first repro: a few days
Developer-Y/cs-video-courses is the closest maintained adjacent implementation (Matches contextual method/domain keyword: computer science). It is not paper-verified; validate algorithm and evaluation setup against the paper before trusting reported metrics. Community adoption signal: 83170 GitHub stars.
- Adjacent implementations are not paper-verified
- Recommended repository is adjacent and not paper-verified.
Reproduction readiness
No repo
No verified implementation available
- No maintained repository has been identified for this paper. Check adjacent implementations or HF artifacts below.
Hardware requirements
- Expect multi-day setup/compute for meaningful reproduction based on current guidance.
Validation caveat
Repositories and ecosystem
Closest related implementations
These are not paper-verified. Use them as reference points when no direct implementation is available.
- Developer-Y/cs-video-courses Adjacent · Confidence: Medium · 83,170 stars
Matches contextual method/domain keyword: computer science
No additional verified repositories beyond the primary recommendation.
Hugging Face artifacts
No trustworthy direct or curated related Hugging Face artifacts were found yet. Use targeted searches to quickly locate candidate models, datasets, and demos.
Tip: start with models, then check datasets and spaces if you need evaluation data or demos.
Research context
394
Citations
40
References
Tasks
Solidity, Computer science, Debugging, False positive paradox, Software bug, Static analysis, Data mining
Methods
None detected
Domains
None detected
Related papers
- Research on source code safety defects based on static test toolsSearch on Paper2Code
2011 · Semantic similarity
- The False False Positives of Static AnalysisSearch on Paper2Code
2017 · Semantic similarity
- Where is the bug and how is it fixed? an experiment with practitionersSearch on Paper2Code
2017 · Semantic similarity
- Analyzing False Positive Source Code Vulnerabilities Using Static Analysis ToolsSearch on Paper2Code
2018 · Semantic similarity
- A Study of Debugging Sequence on Multi-Bug ProgramSearch on Paper2Code
2021 · Semantic similarity
- Towards Understanding the Value of False Positives in Static Code AnalysisSearch on Paper2Code
2016 · Semantic similarity
Open this paper in HFEPX to review benchmark signals, evaluation modes, and human-feedback protocol context.
Open in HFEPXJump to Paper2Code search queries derived from this paper's research context.