Our initial research suggests that a notable proportion of exploitable bugs in smart contracts are functional bugs, which cannot be detected using simple and general oracles like reentrancy. We aim to raise awareness about the significance of such bugs and encourage practitioners to develop more sophisticated and nuanced automatic semantical oracles to detect them.
Dataset Description Folder Structure The dataset is organized into four folders:
papers/: contains our ICSE23 paper summarizing our preliminary results, as well as the supplementary material for the paper. results/: contains the bug classification in bugs.csv and the description for each contest in contests.csv. contracts/: contains all the smart contracts that we examined, using the version at the time of the contest. reports/: contains all the reports provided by code4rena. Bug Labels We classify the surveyed bugs into three main categories based on their nature:
Out-of-scope bugs (denoted by O) Bugs with simple and general testing oracles (denoted by L) Bugs that require high-level semantical oracles (denoted by S)
Log in or sign up for Devpost to join the conversation.