DOI: 10.57760/sciencedb.07518
title: DeFi development process
title: DeFi development process

description: 1、Attack_events.xlsx：This document shows all the attacks that occurred on DeFi and divides them into six categories according to the blockchain hardware hierarchy, and shows the distribution of events related to the attacks over the attack categories, as well as the discussion modes of these events.2、Attack_Instances_list.xlsx：This document contains all the attack instances we collected for this project from 2020 to early October 2022, as well as their sources.3、Paper_list.xlsx:This document shows a list of articles discussing attacks that occurred on blockchain, smart contracts, DeFi, and is the primary source for the list of attacks in this paper.4、Project_attack.xlsx:This table shows the overall situation of project-attack related events, which is not overly represented in this paper due to the excessive content and space limitation of the article, and may be used as a direction for future research to explore the association between different types of DeFi projects and events.5、Project_list.xlsx:We have collected some DeFi projects with high TVL from defillama and summarized them in this table. In this paper, we need to use issues and pull requests from github as analysis data, so we must filter out projects with github links and event data, and the filtering results are shown in the table, which is available for review.6、Supplement to Table.xlsx:This document is a supplement to TableVII and VIII in the paper and is attached due to space limitations.The supplement to TableVII shows all the examples of attacks we collected. The supplement to TableVIII shows the average resolution time of the incidents broken down by attack types. In addition to this, there are the results of our statistics on the day of the week on which the attack occurred.7、different_developers_match_results.xlsxThis file is used to record the results of different developers matching attack-related events.8、different_handle_ways.xlsxThis file is used to record the result of the developer matching the way the event was handled.————————1、attack_events.py:This .py file filters out the manually matched event information related to the attack and makes it easier to calculate the average resolution time.2、get_data.py:This .py file is used to crawl all events data of projects.3、raw_data.py:This .py file is used to pre-process the crawled down metadata to retain useful information.4、solved_info.py：This .py file is used to calculate the average resolution time.5、attack_events.zip:Inside this zip is the basic data we have filtered for events related to the attack.6、search_keywords:This folder contains our descriptions of each attack, as well as their literature sources. In addition, it includes the KeyBERT source code we used and the resulting keywords and corresponding scores obtained using KeyBERT.7、calculate_k.pyThis.py file is used to calculate the kappa value and confirm the consistency of manual matching.8、Kruskal-Wallis.pyThe.py file is used to calculate the p value of the Kruskal-Wallis test to confirm the difference.
description: 1、Attack_events.xlsx：This document shows all the attacks that occurred on DeFi and divides them into six categories according to the blockchain hardware hierarchy, and shows the distribution of events related to the attacks over the attack categories, as well as the discussion modes of these events.2、Attack_Instances_list.xlsx：This document contains all the attack instances we collected for this project from 2020 to early October 2022, as well as their sources.3、Paper_list.xlsx:This document shows a list of articles discussing attacks that occurred on blockchain, smart contracts, DeFi, and is the primary source for the list of attacks in this paper.4、Project_attack.xlsx:This table shows the overall situation of project-attack related events, which is not overly represented in this paper due to the excessive content and space limitation of the article, and may be used as a direction for future research to explore the association between different types of DeFi projects and events.5、Project_list.xlsx:We have collected some DeFi projects with high TVL from defillama and summarized them in this table. In this paper, we need to use issues and pull requests from github as analysis data, so we must filter out projects with github links and event data, and the filtering results are shown in the table, which is available for review.6、Supplement to Table.xlsx:This document is a supplement to TableVII and VIII in the paper and is attached due to space limitations.The supplement to TableVII shows all the examples of attacks we collected. The supplement to TableVIII shows the average resolution time of the incidents broken down by attack types. In addition to this, there are the results of our statistics on the day of the week on which the attack occurred.7、different_developers_match_results.xlsxThis file is used to record the results of different developers matching attack-related events.8、different_handle_ways.xlsxThis file is used to record the result of the developer matching the way the event was handled.————————1、attack_events.py:This .py file filters out the manually matched event information related to the attack and makes it easier to calculate the average resolution time.2、get_data.py:This .py file is used to crawl all events data of projects.3、raw_data.py:This .py file is used to pre-process the crawled down metadata to retain useful information.4、solved_info.py：This .py file is used to calculate the average resolution time.5、attack_events.zip:Inside this zip is the basic data we have filtered for events related to the attack.6、search_keywords:This folder contains our descriptions of each attack, as well as their literature sources. In addition, it includes the KeyBERT source code we used and the resulting keywords and corresponding scores obtained using KeyBERT.7、calculate_k.pyThis.py file is used to calculate the kappa value and confirm the consistency of manual matching.8、Kruskal-Wallis.pyThe.py file is used to calculate the p value of the Kruskal-Wallis test to confirm the difference.