Mismatch between the repo and the ICSE paper #28
-
Hi, the authors of paper "Demystifying Exploitable Bugs in Smart Contracts", thank you for your solid work and I'm inspired by your contributions.
Thanks! |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Hi Gao, Thank you for your interest in our project. You are correct; there is indeed some data mismatch between the GitHub repo and the paper. For more informatoin, you can refer to our classification. In response to your specific questions:
Yes, you are right. This is because there are projects whose code is not accessible. Their bugs will be marked as O2 according to the Bug Labels.
As we are currently refining our classification standards and actively developing the dataset, the dataset has changed significantly. We are also incorporating new C4 projects into the dataset, which contributes to the mismatch. If you plan to use the dataset, I suggest using the most up-to-date version. It is also important to note that the observation of the prevalence of functional bugs still remains. You may have noticed that the repo has not been updated for a few days. This is because I am occupied with my Ph.D. defense and will resume work on the project later.
You are correct. We have not yet released the real-world exploits, but we will do so later. If you need a larger real-world exploit dataset, I recommend DeFiHackLabs, which contains nearly all real-world exploits from recent years. |
Beta Was this translation helpful? Give feedback.
Hi Gao,
Thank you for your interest in our project. You are correct; there is indeed some data mismatch between the GitHub repo and the paper. For more informatoin, you can refer to our classification.
In response to your specific questions:
Yes, you are right. This is because there are projects whose code is not accessible. Their bugs will be marked as O2 according to the Bug Labels.